A
- access policy, examples 1
- action threshold, service schedules
- actions. See policy actions
- aggregate services 1
- adding
- before you configure
- fragment services
- infrastructure services
- mandatory services
- Python expressions
- redundancy
- sessions 1
- timers, configuring
- apply-groups statement, routers running Junos OS
C
- captive portal
- using with next-hop action
- classify-traffic condition 1
- application protocol
- application, setting
- application-group, setting
- configuring
- destination grouped network, configuring
- destination network, configuring
- expanded classifiers 1
- extended classifiers 1
- ICMP conditions, setting
- IGMP conditions, setting
- IPSec conditions, setting
- Junos OS filter conditions, setting
- JunosE secondary input policy conditions, setting
- match direction, setting
- multiple classifiers
- packet length, setting
- PCMM I02 and I03 1
- port definitions, overview
- protocol conditions with parameters, setting
- protocol conditions with ports, setting
- protocol conditions, setting
- route class, configuring
- source grouped network, configuring
- source network, setting
- TCP conditions, setting
- term-precedence, setting
- ToS byte conditions, setting
- color actions 1
- configuring
- color mark actions 1, 2
- controlled load service, FlowSpec
- conventions
- CoS (class of service)
- ToS byte, setting
- customer support 1
D
- Data-over-Cable Service Interface Specifications. See DOCSIS
- default policies
- example
- DHCP (Dynamic Host Configuration Protocol)
- access policy example
- Differentiated Services code point, ToS byte
- DOCSIS policy actions 1
- configuring
- documentation
- drop profile maps
- DSCP (Differentiated Services code point), ToS byte
E
- effective period, service schedules
- exclusions to service schedule 1
- defining
- expanded classifiers 1
- configuring
- expressions
- map, application protocol conditions
- parameter definitions
- extended classifiers, PCMM 1
- configuring
- external parent groups
- external parent groups,
- aggregate rate-limit
- configuration statements
- for JunosE policies
- hierarchical policy parameter
- JunosE
- rate-limit profiles
F
G
- gates, PCMM
- gateSpec actions 1
- configuring
- global parameters 1
- guaranteed service, FlowSpec
H
I
J
- Junos OS ASP policy rules 1
- Junos OS filter policy rules 1
- conditions, setting
- Junos OS policer policy rules 1
- policer actions 1
- Junos OS port mirror policy rules
- Junos OS scheduler policy rules 1, 2, See also drop profile maps
- actions 1
- QoS conditions, configuring
- Junos OS shaping policy rules
- JunosE IPv6 policy rules
- JunosE secondary input policy rules
- conditions, setting
L
M
- manuals
- map expressions
- application protocol conditions
- substitutions
- mark actions 1
- configuring
- multiple classifiers, policies
- multitask
- mutex group 1
- adding
N
- NAT (Network Address Translation) policies
- actions 1
- application protocol condition
- next-hop actions 1
- next-interface actions 1
- configuring
- next-rule actions 1
- configuring
- non-real-time polling service.
- notice icons
- NRTPS (non-real-time polling service)
O
P
- packet loss priority. See loss priority actions
- PacketCable Multimedia Specifications. See PCMM
- parameter names
- parameter value acquisition 1, 2, See also substitutions
- parameter values, setting in services
- parameters 1, See also substitutions
- defining
- definition
- fixing
- global. See global parameters
- local. See local parameters
- ranking sources
- runtime. See runtime parameters
- types
- parent groups 1, 2, 3, 4, 5
- PCMM policies
- classifiers
- client type 1 support
- conditions and actions supported
- DOCSIS parameters 1
- extended classifiers 1
- FlowSpec parameters
- gate
- gateSpec parameters, configuring
- I02 and I03 classifiers
- marking packets
- proxied QoS with policy push
- service class name
- service flow scheduling types
- SessionClassId
- traffic profiles
- permanent service 1
- configuring
- plug-ins
- policer actions 1
- configuring
- policies
- policing policies
- example
- policy actions 1
- color 1
- color mark 1, 2
- combining
- configuring
- DOCSIS 1
- dynamic profiles
- filter 1
- FlowSpec 1
- forward 1
- forwarding class 1
- forwarding instance
- gateSpec 1
- loss priority 1
- mark 1
- NAT 1
- next hop 1
- next interface 1
- next rule 1
- policer 1
- policy rules supported
- QoS profile attachment 1
- rate limit 1
- rate limit hierarchy
- rate limit types
- rate-limit hierarchy
- reject 1
- routing instance 1
- scheduler 1
- service class name 1
- stateful firewall 1
- template activation
- traffic class 1
- traffic mirror 1
- traffic-shape 1
- types
- user packet class 1
- policy components 1
- policy conditions 1, 2, See also classify-traffic condition
- policy engine
- policy examples
- policy folders 1
- configuring
- policy groups 1
- configuring
- policy lists 1
- configuring
- policy management
- policy objects
- policy overview
- actions. See policy actions
- conditions. See classify-traffic condition\
- policy object organization
- policy repository, description
- policy rules 1
- actions supported
- conditions supported
- configuring
- Junos Adaptive Services PIC (ASP). See Junos OS ASP policy rules
- Junos OS filter. See Junos OS filter policy rules
- Junos OS policer. See Junos OS policer policy rules
- Junos OS scheduler. See Junos OS scheduler policy rules
- Junos OS shaping. See Junos OS shaping policy rules
- precedence
- types
- PPP
- access policy example
- precedence
- policy rules
- premium service, example
- preparation time, service schedules
- proxied QoS with policy push
- PTSP actions
- PTSP actions, configuring
Q
R
- rate-limit actions 1
- rate-limit hierarchy actions
- rate-limit type actions
- configuring
- rate-limiting, with multiple classifiers
- real-time polling service. See RTPS
- reject actions 1
- configuring
- routers running Junos OS
- policy features
- routing instance actions 1
- configuring
- RTPS (real-time polling service) 1
- runtime parameters
S
- scheduleAuth plug-in
- scheduler actions 1, 2, See also drop profile maps
- configuring
- scopes. See service scopes
- script services 1
- service
- 3gpp attributes (Gx router driver)
- service class name actions 1
- configuring
- service flow scheduling types
- service schedules
- action threshold, setting
- authorization schedules, configuring
- configuring
- examples
- exclusions, defining
- guidelines
- overview 1
- planning
- preparation time, setting
- weekly-recur-freq
- service scopes 1, 2
- service-mgm-schedules-nonwork
- services
- activate-only
- adding aggregate
- adding infrastructure
- adding normal
- adding script services
- aggregate. See aggregate services
- assigning to service scopes
- automatic activation
- infrastructure. See infrastructure services
- mutually exclusive
- overview
- premium service example
- restricting availability
- restricting simultaneous activation
- script. See script services
- setting parameter values
- tiered Internet example
- SessionClassId, PCMM policies
- shaping rate. See traffic shaping
- stateful firewall policies
- actions 1
- application protocol conditions
- substitutions 1, See also parameters
- support, technical See technical support
T
- technical support
- template activation actions
- configuring
- text conventions defined
- tiered Internet service, example
- traffic mirror actions 1
- configuring
- traffic profiles, PCMM policies
- traffic shape actions
- configuring
- traffic shaping
- traffic-class actions 1
- configuring
- traffic-shape actions
U
V
- validating
- value acquisition for parameters
Download This Guide
Using Python Expressions in a Subscriber Reference Expression
You can compose Python expressions from one or more of the fields in Table 3 for the definition of a subscriber reference expression of a fragment service. You enter these expressions with the expression option of the services scope name service name aggregate fragment or edit services global service name aggregate fragment statement.
Table 3: Fields Used in Python Expressions for Aggregate Services
Field | Description |
---|---|
substitution.<xyz> | Value of the parameter <xyz>. Substitutions are acquired by means of the regular acquisition path for service sessions. The names of parameters are restricted to valid Python identifiers, such as ‘ALPHA/” _” *(ALPHA/ DIGIT/” _” )’, with the exception of keywords, such as for, if, while, return, and, or, not, def, class, try, exceptFor the full list of Python keywords, see https://docs.python.org/2/library/. |
loginType | The type of subscriber session, one of the following:
|
loginName | Login name provided by a subscriber |
userName | Username portion of the loginName |
domainName | Domain name portion of the loginName |
serviceBundle | Content of the vendor-specific RADIUS attribute for service bundle |
radiusClass | RADIUS class used for authorization |
virtualRouterName | Name of virtual router in the format vrname@hostname |
interfaceName | Name of the interface |
ifAlias | Description of the interface configured on the router |
ifDesc | Alternate name for the interface. This is the name used by the Simple Network Management Protocol (SNMP). On a router running JunosE Software, the format of the description is: ip<slot>/<port>.<subinterface> On a router running Junos OS, ifDesc is the same as interfaceName. |
interfaceType | Type of the interface. The values could be IP for IPv4; IPV6 for IPv6; IP,IPV6 for dual-stack interface. |
nasPortId | Port identifier of an interface, including the interface name and additional layer 2 information (for example, fastEthernet 3/1) |
macAddress | Text representation of the MAC address for the DHCP subscriber (for example. 00:11:22:33:44:55) |
retailerDn | Distinguished name of the retailer |
nasIp | Network access server IP address of the router |
dhcp | DHCP options. See Classification Scripts Overview. |
primaryUserName | PPP or DHCP username. This name does not change when the subscriber logs in through a portal. |
framedIpv6Prefix | Configures a condition that uses the IPv6 address prefix. framedIpv6Prefix is available for JunosE (COPS-PR), Junos OS (JSRC), as well as AAA (COA). |
delegatedIpv6Prefix | Delegated IPv6 prefix for the subscriber. Using the delegatedIpv6Prefix attribute, the NAS can receive a set of IPv6 prefixes that are delegated to subscribers. An IPv6 subscriber can be identified through multiple prefixes by using the delegatedIpv6Prefix attribute with the framedIpv6Prefix attribute. delegatedIpv6Prefix is available for Junos OS (JSRC), AAA (COA), and DHCPv6 subscribers on the JunosE router. |
Related Documentation
- Restricting and Customizing Services for Subscribers Overview
- SRC Aggregate Services Overview
- Configuring Fragment Services for an Aggregate Service (SRC CLI)