Table 32: Differentiated Services Mapping
Traffic Class/Color6-bit PHB IDPHB IDPHBEXP
best-effort/green000x0000BE000
af1/green100x2800AF11001
af1/yellow120x3000AF12010
af1/red140x3800AF13011
af2/green180x4800AF21100
af2/yellow200x5000AF22101
af2/red220x5800AF23110
ef/green460xb800EF111
NOTE: This example includes both MPLS and policy configuration commands, and
assumes that you are thoroughly familiar with the information and commands
presented in the JUNOSe Policy Management Configuration Guide.
The four traffic classes are configured to allocate fabric resources and allow global
synchronization of the three segments of the data path through an E Series router:
ingress, fabric, and egress. The JUNOSe software automatically creates the best-effort
traffic class, with a default weight of eight. You must define the remaining three
classes, af1, af2, and ef. In this example, the af1 class has twice as much fabric
bandwidth as the best-effort class, and the af2 class has twice as much fabric
bandwidth as the af1 class. The expedited forwarding traffic (the ef class) requires
strict-priority queuing.
host1(config)#traffic-class af1
host1(config-traffic-class)#fabric-weight 16
host1(config)#traffic-class af2
host1(config-traffic-class)#fabric-weight 32
host1(config)#traffic-class ef
host1(config-traffic-class)#fabric-strict-priority
Define two scheduler profiles for the af1 and af2 classes on the egress line modules:
host1(config)#scheduler-profile af1-scheduler-profile
host1(config-scheduler-profile)#weight 16
host1(config)#scheduler-profile af2-scheduler-profile
host1(config-scheduler-profile)#weight 32
Create queue profiles to define how queues are instantiated to implement the
corresponding traffic classes and PHBs. The JUNOSe software automatically creates
the best-effort queue profiles.
host1(config)#queue-profile af1-queues
Example Traffic Class Configuration for Differentiated Services â– 309
Chapter 3: Configuring MPLS
To Next Page
Loading...
Need help?
General
