Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - BROADBAND ACCESS CONFIGURATION GUIDE 2010-10-12 Configuration Manual page 734

JunosE 11.3.x Broadband Access Configuration Guide
696
<# env.setResult("secondary-input-stat-epg", "vb-v4v6-"$ uid $"-in v4v6-"$ uid $"") #>
<# env.setResult("output-stat-epg", "vb-v4v6-"$ uid $"-out v4v6-"$ uid $"") #>
The <# env.setResult("secondary-input-stat-epg", "vb-v4v6-"$ uid $"-in v4v6-"$ uid
$"") #> command specifies that Service Manager track statistics associated with the
external parent group named vb-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", "vb-v4v6-"$ uid $"-out v4v6-"$ uid $"")
#> command specifies that Service Manager track the output statistics associated with
the external parent group named vb-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.
If you use the secondary-intput-stat-clacl and output-stat-clacl objects in the service
macro to track Service Manager statistics, the values returned in the output of the show
service-management command do not accurately reflect the packets that are
rate-limited. In this case, although some of the packets that were classified by the classifier
lists are dropped by the rate-limiter on the external parent group, the Service Manager
statistics collection application counts all the packets that were classified without
excluding those that were dropped by the rate limiter. As a result, the values returned by
the output-stat-clacl and secondary-input-stat-clacl objects represent more packets
than those sent to the subscriber and core interfaces respectively.
Using the macro that has been described here, you can configure the following combined
service, for example:
combined_service(64000, 64000, 10.0.0.1, 2001::1, vlan)
where
64000—Bandwidth for outbound traffic, denoted as outBw in the macro
64000—Bandwidth for inbound traffic, denoted as inBw in the macro
10.0.0.1—Host IP address for IPv4 subscribers, denoted as VBG1 in the macro
2001::1—Host IP address for IPv6 subscribers, denoted as VB6G1 in the macro
vlan—Interface on which the service is configured, denoted as NODE in the macro
Copyright © 2010, Juniper Networks, Inc.