Table of Contents
Advertisement
Service Manager Performance Considerations
Service Definition Examples
Copyright © 2010, Juniper Networks, Inc.
policy that allows classifier groups and parent groups within a policy to point to line
module global parent groups. Each reference to a policy parameter in a policy is
substituted with its value for all attachments of this policy at the interface.
For example, if v4v6 is the name of the hierarchical policy parameter and the external
parent group names are vc-v4v6-in and vc-v4v6-out, you must configure both the external
parent group names and the corresponding hierarchical policy parameter in the
env.setResult method for the external parent group statistics to be calculated.
<# 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.
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 661 for details.
Capture volume statistics when needed—Repeatedly capturing volume statistics can
waste resources.
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
Chapter 27: Configuring Service Manager
671
Advertisement
Table of Contents
Troubleshooting
