Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
ContentIndex
  
[+] Expand All
[-] Collapse All

 A  C  D  E  F  G  H  I  J  L  M  N  O  P  Q  R  S  T  U  V

 

A

access policy, examples    1
DHCP    
SRC CLI
PPP    
SRC CLI
action threshold, service schedules    
overview
setting    
SRC CLI
actions.     See policy actions    
aggregate services    1
adding    
SRC CLI
before you configure    
SRC CLI
fragment services
infrastructure services
mandatory services
Python expressions
redundancy
sessions    1
activation
attributes
deactivation
modification
monitoring
timers, configuring    
SRC CLI
apply-groups statement, routers running Junos OS
 

C

captive portal    
using with next-hop action    
SRC CLI
classify-traffic condition    1
application protocol    
defining, SRC CLI
map expressions, SRC CLI
application, setting    
SRC CLI
application-group, setting    
SRC CLI
configuring    
SRC CLI
destination grouped network, configuring    
SRC CLI
destination network, configuring    
SRC CLI
expanded classifiers    1
configuring, SRC CLI
extended classifiers    1
configuring, SRC CLI
ICMP conditions, setting    
SRC CLI
IGMP conditions, setting    
SRC CLI
IPSec conditions, setting    
SRC CLI
Junos OS filter conditions, setting    
SRC CLI
JunosE secondary input policy conditions, setting    
SRC CLI
match direction, setting    
SRC CLI    12
multiple classifiers
packet length, setting    
SRC CLI
PCMM I02 and I03    1
configuring, SRC CLI
port definitions, overview    
SRC CLI
protocol conditions with parameters, setting    
SRC CLI
protocol conditions with ports, setting    
SRC CLI
protocol conditions, setting    
SRC CLI
route class, configuring    
SRC CLI
source grouped network, configuring    
SRC CLI
source network, setting    
SRC CLI
TCP conditions, setting    
SRC CLI
term-precedence, setting    
SRC CLI
ToS byte conditions, setting    
SRC CLI
color actions    1
configuring    
SRC CLI
color mark actions    12
controlled load service, FlowSpec
conventions    
notice icons
text
CoS (class of service)    
ToS byte, setting    
SRC CLI
customer support    1
contacting JTAC
 

D

Data-over-Cable Service Interface Specifications.     See DOCSIS    
default policies    
example    
SRC CLI
DHCP (Dynamic Host Configuration Protocol)    
access policy example    
SRC CLI
Differentiated Services code point, ToS byte    
SRC CLI
DOCSIS policy actions    1
configuring    
SRC CLI
documentation    
comments on
drop profile maps    
configuring    
SRC CLI
drop probability, setting    
SRC CLI
fill level, setting    
SRC CLI
DSCP (Differentiated Services code point), ToS byte    
SRC CLI
 

E

effective period, service schedules
exclusions to service schedule    1
defining    
SRC CLI
expanded classifiers    1
configuring    
SRC CLI
expressions    
map, application protocol conditions    
SRC CLI
parameter definitions
extended classifiers, PCMM    1
configuring    
SRC CLI
external parent groups    
JunosE    
overview    12
external parent groups,    
aggregate rate-limit    
configuring
configuration statements
for JunosE policies    
configuration statements
configuring
hierarchical policy parameter    
configuring
JunosE    
creating
rate-limit profiles    
configuring
 

F

filter actions    1
configuring    
SRC CLI
FlowSpec actions    1
configuring    
SRC CLI
forward actions    1
configuring    
SRC CLI
forwarding class actions    1
configuring    
SRC CLI
fragment services    1
configuring    
SRC CLI
 

G

gates, PCMM
gateSpec actions    1
configuring    
SRC CLI
global parameters    1
configuring    
SRC CLI
predefined    1
viewing with SRC CLI
runtime
types
guaranteed service, FlowSpec
 

H

hierarchical policies    
overview    
1
hierarchical rate-limiting    
JunosE    
1
 

I

infrastructure services    123
 

J

Junos OS ASP policy rules    1
NAT actions    1
configuring, SRC CLI
network, specifying    1
SRC CLI    12
stateful firewall actions, configuring    
SRC CLI
Junos OS filter policy rules    1
conditions, setting    
SRC CLI
Junos OS policer policy rules    1
policer actions    1
configuring, SRC CLI
Junos OS port mirror policy rules    
traffic mirror actions
Junos OS scheduler policy rules    12,  See also drop profile maps    
actions    1
configuring, SRC CLI
QoS conditions, configuring    
SRC CLI
Junos OS shaping policy rules
JunosE IPv6 policy rules    
network, specifying    
SRC CLI    12
JunosE secondary input policy rules    
conditions, setting    
SRC CLI
 

L

local parameters    1
configuring    
SRC CLI
types
loss priority actions    1
configuring    
SRC CLI
 

M

manuals    
comments on
map expressions    
application protocol conditions    
SRC CLI
substitutions
mark actions    1
configuring    
SRC CLI
multiple classifiers, policies
multitask
mutex group    1
adding    
SRC CLI
 

N

NAT (Network Address Translation) policies    
actions    1
configuring, SRC CLI
application protocol condition    
defining, SRC CLI
map expressions, SRC CLI
next-hop actions    1
captive portal feature    
SRC CLI
configuring    
SRC CLI
next-interface actions    1
configuring    
SRC CLI
next-rule actions    1
configuring    
SRC CLI
non-real-time polling service.
notice icons
NRTPS (non-real-time polling service)
 

O

operators in substitution expressions
 

P

packet loss priority.     See loss priority actions    
PacketCable Multimedia Specifications.     See PCMM    
parameter names    
substitutions
parameter value acquisition    12,  See also substitutions    
example
multiple subscriptions
single subscriptions
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    12345
PCMM policies    
classifiers
client type 1 support
conditions and actions supported
DOCSIS parameters    1
configuring, SRC CLI
extended classifiers    1
configuring, SRC CLI
FlowSpec parameters    
configuring, SRC CLI
controlled load service
guaranteed service
request specification (RSpec)
traffic specification (TSpec)
gate
gateSpec parameters, configuring    
SRC CLI
I02 and I03 classifiers
marking packets
proxied QoS with policy push
service class name    
configuring, SRC CLI
service flow scheduling types
SessionClassId
traffic profiles
permanent service    1
configuring    
SRC CLI
plug-ins    
authorization
policer actions    1
configuring    
SRC CLI
policies    
defining parameters in repository
policing policies    
example    
SRC CLI
policy actions    1
color    1
configuring, SRC CLI
color mark    12
combining
configuring
DOCSIS    1
configuring, SRC CLI
dynamic profiles    
configuring, SRC CLI
filter    1
configuring, SRC CLI
FlowSpec    1
configuring, SRC CLI
forward    1
configuring, SRC CLI
forwarding class    1
configuring, SRC CLI
forwarding instance    
configuring, SRC CLI
gateSpec    1
configuring, SRC CLI
loss priority    1
configuring, SRC CLI
mark    1
configuring, SRC CLI
NAT    1
configuring, SRC CLI
next hop    1
configuring, SRC CLI
next interface    1
configuring, SRC CLI
next rule    1
configuring, SRC CLI
policer    1
configuring, SRC CLI
policy rules supported
QoS profile attachment    1
configuring, SRC CLI
rate limit    1
configuring, SRC CLI
rate limit hierarchy    
overview
parent-group reference, SRC CLI
rate limit types    
configuring, SRC CLI
rate-limit hierarchy    
configuring, SRC CLI    12
reject    1
configuring, SRC CLI
routing instance    1
configuring, SRC CLI
scheduler    1
configuring, SRC CLI
service class name    1
configuring, SRC CLI
stateful firewall    1
configuring, SRC CLI
template activation    
configuring, SRC CLI
traffic class    1
configuring, SRC CLI
traffic mirror    1
configuring, SRC CLI
traffic-shape    1
configuring, SRC CLI
types
user packet class    1
configuring, SRC CLI
policy components    1
policy decision point, description
Policy Editor
policy enforcement point, description
policy engine
policy repository
policy conditions    12,  See also classify-traffic condition    
policy rules supported
types
policy engine
policy examples    
access policy    
SRC CLI
premium service    
SRC CLI
tiered Internet service    
SRC CLI
policy folders    1
configuring    
SRC CLI
policy groups    1
configuring    
SRC CLI
policy lists    1
configuring    
SRC CLI
policy management    
bandwidth management
overview
packet logging
packet mirroring
packet tagging
policy routing
QoS classification and marking
RADIUS support
security
policy objects    
organization
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    
SRC CLI
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    
SRC CLI
types
PPP    
access policy example    
SRC CLI
precedence    
policy rules    
SRC CLI
premium service, example    
SRC CLI
preparation time, service schedules    
overview
setting    
SRC CLI
proxied QoS with policy push
PTSP actions    
PTSP actions, configuring    
SRC CLI
 

Q

QoS (quality of service)    
condition    1
configuring, SRC CLI
PCMM cable networks.     See PCMM policies    
QoS parameters, configuring    
SRC CLI
QoS profile attachment actions    1
configuring, SRC CLI
QoS profile, configuring    
SRC CLI
QoS condition    12
 

R

rate-limit actions    1
configuring    
SRC CLI
example    
SRC CLI
rate-limit hierarchy actions    
configuring    
SRC CLI    12
overview
rate-limit type actions    
configuring    
SRC CLI
rate-limiting, with multiple classifiers
real-time polling service.     See RTPS    
reject actions    1
configuring    
SRC CLI
routers running Junos OS    
policy features    
rate-shaping
routing instance actions    1
configuring    
SRC CLI
RTPS (real-time polling service)    1
configuring    1
SRC CLI
runtime parameters    
viewing with SRC CLI
 

S

scheduleAuth plug-in
scheduler actions    12,  See also drop profile maps    
configuring    
SRC CLI
scopes.     See service scopes    
script services    1
adding    
SRC CLI
example    
ScriptService SPI in Java
ScriptService SPI in Jython
ScriptService interface
service    
3gpp attributes (Gx router driver)    
configuring, SRC CLI
service class name actions    1
configuring    
SRC CLI
service flow scheduling types
service schedules    
action threshold, setting    
SRC CLI
authorization schedules, configuring    
SRC CLI
configuring    
SRC CLI
examples    
SRC CLI    1234
exclusions, defining    
SRC CLI
guidelines
overview    1
action threshold
authorization schedules
configuring
effective period
event-based schedules
exclusions
one-time events
preparation time
recurring events
state-based schedules
planning
preparation time, setting    
SRC CLI
weekly-recur-freq
service scopes    12
adding    
SRC CLI
assigning services    
SRC CLI
assigning subscribers    
SRC CLI
assigning VRs    
SRC CLI
configuring    
SRC CLI
example    
SRC CLI
multiple scopes, defining    
SCR CLI
service-mgm-schedules-nonwork
services    
activate-only
adding aggregate    
SRC CLI
adding infrastructure    
SRC CLI
adding normal    
SRC CLI
adding script services    
SRC CLI
aggregate.     See aggregate services    
assigning to service scopes    
SRC CLI
automatic activation
infrastructure.     See infrastructure services    
mutually exclusive
overview
premium service example    
SRC CLI
restricting availability
restricting simultaneous activation
script.     See script services    
setting parameter values
tiered Internet example    
SRC CLI
SessionClassId, PCMM policies
shaping rate.     See traffic shaping    
stateful firewall policies    
actions    1
configuring, SRC CLI
application protocol conditions    
defining, SRC CLI
map expressions, SRC CLI
substitutions    1,  See also parameters    
aggregate services, configuring
comments    1
adding
definition
exceptions, raising
expressions    12
IPv4 addresses
keywords
lists, formatting
maps, formatting
numbers, formatting
operators
parameter names, specifying
ranges
separators
strings, formatting
subordinate expressions
syntax
formatting
map expressions
mathematical expressions
parameter names
validation
support, technical     See technical support    
 

T

technical support    
contacting JTAC
template activation actions    
configuring    
SRC CLI
text conventions defined
tiered Internet service, example    
SRC CLI
traffic mirror actions    1
configuring    
SRC CLI
traffic profiles, PCMM policies
traffic shape actions    
configuring    
SRC CLI
traffic shaping    
actions
policy rules
traffic-class actions    1
configuring    
SRC CLI
traffic-shape actions
 

U

UGS (unsolicited grant service)    1
configuring    
SRC CLI
UGS-AD (unsolicited grant service with activity detection)    1
configuring    
SRC CLI
unsolicited grant service.     See UGS    
unsolicited grant with activity detection.     See UGS-AD    
user packet class actions    1
configuring    
SRC CLI
 

V

validating    
substitutions
value acquisition for parameters    
multiple subscriptions
single subscriptions

SRC Aggregate Services Overview

Combining services lets the SRC software treat the services within an aggregate service as a unit. When an aggregate service becomes active, it tries to activate all the services within it.

An aggregate service can distribute the activation of a number of services within the aggregate across one or more SAEs in an SRC network. This specialized service is ideal for supporting voice over IP (VoIP) and video on demand. To deliver these types of features to subscribers, you can configure bidirectional or unidirectional quality of service (QoS) services based on policies provisioned across a number of interfaces on one or more SAE-managed network devices in an SRC network. Figure 1 shows a sample aggregate service that provides end-to-end QoS for video on demand, with QoS service 1 and QoS service 2 activated on Juniper Networks routers in the path between the video server and the subscriber.

Figure 1: Sample Configuration of an Aggregate Service

Sample Configuration of an Aggregate
Service

The services included in an aggregate service manage policies in the usual manner. The aggregate service does not directly manage any policies on a network device.

Fragment Services

The services that make up an aggregate service are referred to as fragment services. This term provides a way to distinguish between services that are included in an aggregate service and those that are not. The fragment services can be any type of service that the SAE supports, except another aggregate service.

Subscriber Reference Expressions for Fragment Services

The configuration for each fragment service includes a subscriber reference expression, a phrase that identifies the subscriber sessions that activate the fragment service. The subscriber reference expression defines the subscriber session by subscriber IP address, assigned IP address, distinguished name (DN), interface name, login name, or associated virtual router.

To use aggregate services requires that the network information collector (NIC) be configured. Use a configuration scenario that provides a key for the type of subscriber reference expression defined for the fragment service. For example, if the subscriber reference expression is a DN, the NIC key is also a DN. In this case, you could use the NIC configuration scenario OnePopDnSharedIp, which uses a DN as a key.

For more information about the NIC configuration scenarios and the types of resolutions performed by these scenarios, see NIC Configuration Scenarios.

Mandatory Services

A fragment service that must be active for an aggregate service to become active is called a mandatory service. When you configure an aggregate service, you specify which services, if any, are mandatory. For example, you could specify that rate-limiting services for a video-on-demand connection be mandatory to ensure call quality.

Redundant Services

When you configure an aggregate service, you can configure fragment services to provide redundancy for each other. Fragment services that share the same redundancy group name provide redundancy.

For an aggregate service to become active, at least one fragment service from each redundancy group must become active. For example, if you configure two services, S1 and S2, and assign the same redundancy group name to each of these services, S1 and S2 provide redundancy for each other if one becomes disabled.

While an aggregate service is active, the SAE tries to keep all fragment services within it active. An aggregate service and any of its active fragment services become inactive if a mandatory fragment service or an entire redundancy group becomes inactive.

Aggregate Service Sessions

An aggregate service session coordinates the activation of the services within it. It runs on the same SAE where it starts. The aggregate service session is created in the router driver that hosts the subscriber session that starts the service. An individual service session for a fragment service can be activated in the same SAE or another SAE on the SRC network.

Understanding how aggregate service sessions are managed can help you troubleshoot service activation or service deactivation issues that might arise. The SRC software provides a set of configurable timers that helps control session management.

For information about the timers that you can use to troubleshoot aggregate services, see Configuring Timers for Aggregate Services (SRC CLI).

While activating an aggregate service session, you can specify different activation attributes. Some of these attributes are propagated to the fragments of the aggregate service session.

Session Activation

An aggregate service becomes active when:

  • All mandatory services are active.

    If a mandatory service does not start, the SAE deactivates any fragment services that are active.

  • If there are no mandatory services, the aggregate service is still active and trying to activate fragment services.

If any fragment services that are not mandatory services do not become active, the aggregate service continues to try to start them. How long the aggregate service tries to activate fragment services depends on the settings for activation-deactivation time.

When an aggregate service becomes active, it monitors the services that are part of the aggregate service.

Note: Depending on your implementation, accounting software could detect that a fragment service session became active even though the associated aggregate service did not become active, resulting in the fragment services being deactivated.

You can configure your accounting software to ignore the activation of the fragment session when an aggregate service session fails. This way, a customer is not billed for an aggregate service that was not received.

Attributes Used to Activate an Aggregate Service Session

The following attributes are propagated from an aggregate service session to its fragments:

  • aggregateServiceName
  • aggregateSessionName
  • aggregateVr
  • aggregateLoginName
  • aggregateUserIdType
  • aggregateUserDn
  • aggregateUserIp
  • aggregateSessionId
  • aggregateAccountingId
  • aggregateAuthUserId
  • requireAggregateSubscription
  • aggregateFragmentIsLocal
  • aggregateFragmentSessionId
  • aggregateUserSessionId
  • upStreamBandwidth
  • downStreamBandwidth
  • interimTime
  • properties
  • sessionVolumeQuota
  • sessionTag
  • substitutions

    Note: When a fragment session is activated from an aggregate service session, the substitutions attribute has the following behaviors:

    • The substitutions attribute is used when an aggregate session is activated.
    • The substitutions attribute is defined in the fragment service. You can define a list of substitution names. The values are acquired from an acquisition path.

The following attributes are not propagated from an aggregate service session to its fragments:

  • acctSessionId
  • sessionTimeout
  • subscriptionUsername
  • subscriptionPassword

Session Deactivation

When the SAE deactivates an aggregate service, the aggregate service session tries to deactivate the services within it. The SAE deactivates an aggregate service when all fragment services stop. If one of these services remains active, the aggregate service stays in memory until the service session ends. The SAE periodically tries to stop the active fragment session until the maximum retry time is reached, at which time it deactivates the aggregate service. As a result, the aggregate service session can remain in memory after the associated subscriber session ends.

Session Modification

The aggregate service session propagates the following modified attributes to the fragments:

  • substitutions
  • upStreamBandwidth
  • downStreamBandwidth
  • interimTime
  • properties
  • sessionVolumeQuota
  • sessionTag

The modify service session does not support the modification of substitutions used in the subscriber reference expression, which results in the activation and deactivation of the fragments.

The aggregate service session triggers the modify functionality to its fragments. When you publish an authentication event, you can deny the modification for the fragment. This leads the modify functionality to split into the following steps:

  • The aggregate service session must receive an approval from all the fragments when you publish the service authentication event.
  • The specified modify functionality is performed. For example, for a policy service session, provisioning objects are updated. This step occurs only if an aggregate service session received an approval from all the fragments in the previous step.

Session Monitoring

An aggregate service session exchanges keepalive messages with a session management process for remote fragment services. This way, if a service session is removed from a router while the SAE is not managing the router, such as when the Common Open Policy Service (COPS) client stops on a router running JunosE Software or the configuration database is reset on a router running Junos OS, the SAE associated with the router receives notification that the keepalive message failed.

Service Activation

Aggregate services are activated in a way similar to any other service, but with the additional requirement of activating the associated fragment services. Figure 2 shows a sample service activation for a video-on-demand service.

Figure 2: Aggregate Service Activation

Aggregate Service Activation

The following process describes the service activation for a video-on-demand service, with Steps 1–4 illustrated in Figure 2.

  1. A subscriber requests a video-on-demand service through a residential portal.
  2. The residential portal requests the service through the SAE.
  3. The SAE activates a subscription for the associated aggregate service, and a session for the aggregate service becomes active.
  4. The aggregate service coordinates with the SAE, and the SAE tries to activate the fragment services that have been configured for the aggregate service.

The aggregate service becomes active when:

  • All mandatory services are active.
  • If there are no mandatory services, at least one fragment service is active.
  • For redundant fragment services, at least one fragment service configured for a redundancy group becomes active.

The aggregate service initiates accounting, if accounting has been configured.

After the aggregate service becomes active, it monitors fragment services to ensure that they are still active. When the subscriber or the video server ends the video-on-demand session, the aggregate service tries to terminate active fragment services.

Related Documentation

Modified: 2015-06-19