Juniper JUNOSE 11.0.X MULTICAST ROUTING, Configuration Manual

Page: 724 / 788

<# env.setResult("input-stat-epg", "vc-v4v6-in v4v6" ) #>
<# env.setResult("output-stat-epg", "vc-v4v6-out v4v6" ) #>
The <# env.setResult("secondary-input-stat-epg", "vc-v4v6-in v4v6") #>
command specifies that Service Manager track statistics associated with the external
parent group named vc-v4v6-in and the corresponding hierarchical policy named
v4v6, and that this external parent group is associated with the policy that is attached
at the input stage.
The <# env.setResult("output-stat-epg", "vc-v4v6-out v4v6") #> command
specifies that Service Manager track the output statistics associated with the external
parent group named vc-v4v6-out and the corresponding hierarchical policy named
v4v6, which is associated with the policy attached at the output stage.
The input and output statistics associated with the external parent group are collected
and forwarded to the Service Manager to be displayed in the Acct-Stop and
Interim-Acct messages.
Service Manager Performance Considerations
Like any application, Service Manager requires a certain amount of system resources.
Consider the following guidelines to maximize the performance of Service Manager
when delivering subscriber services:
■
Minimize service definitions—Use the minimum number of JUNOSe commands
in a service definition to specify a service.
■
Reference objects in service definitions—Referencing commonly used objects
is more resource-efficient than using unique objects for each subscriber (for
example, using a subscriber’s IP address as a match criteria in a classifier list).
■
Preprovision frequently used services— Preprovisioning saves resources by
requiring Service Manager to build a popular service only once. You then reuse
the original service when you activate future subscriber service sessions. See
“Preprovisioning Services” on page 674 for details.
■
Capture volume statistics when needed—Repeatedly capturing volume statistics
can waste resources.
Service Definition Examples
This section provides examples of service definition macro files. Commented text
explains the parameterized values in the examples. Each example is followed by
examples of RADIUS information and the CLI command that you might use to activate
a subscriber service session.
Tiered Service Example
This example creates a tiered service. A tiered service typically provides set
bandwidths for both inbound and outbound traffic for a subscriber. In this example,
the bandwidth values are parameterized. Also, this example assumes that QoS profile
triplePlayIP and QoS parameter maxSubscBW are configured.
684 ■
Service Manager Performance Considerations
JUNOSe 11.0.x Broadband Access Configuration Guide