Juniper JUNOSE 11.1.X - BROADBAND ACCESS CONFIGURATION GUIDE 6-4-2010, Configuration Manual

Page: 744 / 794

ipv6 policy secondary-input pl6-v4v6-<# genericName #>-in statistics enabled merge
<# env.setResult("activate-profile", profileName) #>
<# env.setResult("service-interface-type", "ipv4-ipv6") #>
<# env.setResult("secondary-input-stat-epg", "vb-v4v6-"$ uid $"-in v4v6-"$ uid $"") #>
<# env.setResult("output-stat-epg", "vb-v4v6-"$ uid $"-out v4v6-"$ uid $"") #>
<# endtmpl #>
In the service definition macro, a hierarchical policy parameter for the rate limit is
created with an aggregation node value. The aggregation node stores a single rate-limit
instance and statistics for this rate-limit. An external rate-limit aggregation node can
be defined by the 4-tuple (slot, direction, external parent group name, parameter
value). Each reference to a policy parameter in a policy is substituted with its value
for all attachments of this policy at the interface.
Two rate-limit profiles are created, one each for the ingress and egress interfaces.
Rate limiters are implemented using a dual token bucket scheme: a token bucket for
conformed (yellow) packets and a token bucket for committed (green) packets. The
following are the attributes configured in the rate-limit profile applied to ingress and
egress interfaces:
■
The committed rate for the rate-limit profile is entered as a specified value.
■
The committed action, which specifies the action for packets conforming to the
committed rate and committed burst size and conforming to the exceed rate
and exceed burst size for a rate-limit profile is set to receive transmit
unconditional.
■
The conformed action, which sets the action for packets not conforming to the
committed rate and committed burst size, but conforming to the peak rate and
peak burst size for a rate-limit profile is set to receive transmit unconditional.
Two external parent groups, one each for the ingress and egress interfaces, that
reference the rate-limit profiles created for incoming and outgoing traffic, are created
and specified in the service definition.
Classifier control lists for ingress IPv4 and IPv6 traffic, and for egress IPv4 and IPv6
traffic, are also created. These classifiers classify traffic based on source and
destination addresses.
The input and output classifier lists for IPv4 traffic are used in IP policy lists that are
attached to the ingress and egress IPv4 interfaces respectively. The input and output
classifier lists for IPv6 traffic are used in IPv6 policy lists that are attached to the
ingress and egress IPv6 interfaces respectively. The
external parent-group keyword
creates an external parent group in a rate-limit hierarchy for IPv4 and IPv6. All packets
matching the classifier are sent to the parent group for further processing.
The policy lists for voice-over-IP traffic are configured in the service definition macro
file that creates a combined IPv4/IPv6 service to be applied to the ingress IPv4 and
IPv6 interfaces.
A profile is created that you want to attach to the service session. The IPv4 and IPv6
policies for voice-over-IP traffic arriving at the IPv4 and IPv6 interfaces respectively
704 ■
Service Definition Examples
JUNOSe 11.1.x Broadband Access Configuration Guide