[Contents] [Prev] [Next] [Index] [Report an Error]

Example Traffic Class Configuration for Differentiated Services

The commands in this example illustrate a partial network configuration that supports four differentiated service classes on a particular tunnel: a best-effort class, two assured forwarding classes, and an expedited forwarding class. Table 30 presents the mapping between EXP bits, PHB, PHB ID, and traffic class/color combination.

Table 30: Differentiated Services Mapping

EXP	PHB	PHB ID	6-bit PHB ID	Traffic Class/Color
000	BE	0x0000	00	best-effort/green
001	AF11	0x2800	10	af1/green
010	AF12	0x3000	12	af1/yellow
011	AF13	0x3800	14	af1/red
100	AF21	0x4800	18	af2/green
101	AF22	0x5000	20	af2/yellow
110	AF23	0x5800	22	af2/red
111	EF	0xb800	46	ef/green

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 

[Queue configuration omitted]
host1(config)#queue-profile af2-queues 

[Queue configuration omitted]
host1(config)#queue-profile ef-queues 

[Queue configuration omitted]

The scheduler and queue profiles are referenced in QoS profiles. For example, you can create a QoS profile for port-based per-class queuing or for LSP-level per-class queuing (configuration omitted).

You must map the PHB IDs to the appropriate traffic class/color combinations:



host1(config)#mpls diff-serv phb-id standard
0 traffic-class best-effort color green 

host1(config)#mpls diff-serv phb-id standard
10 traffic-class af1 color green 

host1(config)#mpls diff-serv phb-id standard
12 traffic-class af1 color yellow 

host1(config)#mpls diff-serv phb-id standard
14 traffic-class af1 color red 

host1(config)#mpls diff-serv phb-id standard
18 traffic-class af2 color green 

host1(config)#mpls diff-serv phb-id standard
20 traffic-class af2 color yellow 

host1(config)#mpls diff-serv phb-id standard
22 traffic-class af2 color red 

host1(config)#mpls diff-serv phb-id standard
46 traffic-class ef color green

[Contents] [Prev] [Next] [Index] [Report an Error]