You are not required to configure the traffic engineering classes. Table 8 shows the default values for everything in the traffic engineering class matrix. The default mapping is expressed in terms of the default forwarding classes defined in the CoS configuration.
Table 8: Default Values for the Traffic Engineering Class Matrix
|
Traffic Engineering Class |
Class Type |
Queue |
Priority |
|---|---|---|---|
|
te0 |
ct0 |
0 |
7 |
|
te1 |
ct1 |
1 |
7 |
|
te2 |
ct2 |
2 |
7 |
|
te3 |
ct3 |
3 |
7 |
|
te4 |
ct0 |
0 |
0 |
|
te5 |
ct1 |
1 |
0 |
|
te6 |
ct2 |
2 |
0 |
|
te7 |
ct3 |
3 |
0 |
You can override the default mapping by configuring other values for the traffic engineering classes. You can configure traffic engineering classes 0 through 7. For each traffic engineering class, you configure a class type (or queue) from 0 through 3. For each class type, you configure a priority from 0 through 7.
To configure traffic engineering classes explicitly, include the te-class-matrix statement:
-
te-class-matrix {
-
- tenumber {
- priority priority;
-
- traffic-class {
- ctnumber priority priority;
- }
- }
- }
You can include this statement at the following hierarchy levels:
The following example shows how to configure traffic engineering class te0 with class type ct1 and a priority of 4:
- [edit protocols mpls diffserv-te]
- te-class-matrix {
- te0 traffic-class ct1 priority 4;
- }
 |
Note: If you explicitly configure a value for one of the traffic engineering classes, all the default values in the traffic engineering class matrix are dropped. When you explicitly configure traffic engineering classes, you must also configure a bandwidth model; otherwise, the configuration commit operation fails. See Configuring the Bandwidth Model. |
 | Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |