Configuring MPLS TE tunnel constraints
Perform this task on the ingress node of the MPLS TE tunnel.
Configuring bandwidth constraints for an MPLS TE tunnel
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter MPLS TE tunnel interface view. | interface tunnel tunnel-number [ mode mpls-te ] | N/A |
3. Configure bandwidth required for the tunnel, and specify a CT for the tunnel's traffic. | mpls te bandwidth [ ct0 | ct1 | ct2 | ct3 ] bandwidth | By default, no bandwidth is assigned, and the class type is CT 0. |
Configuring the affinity attribute for an MPLS TE tunnel
The associations between the link attribute and the affinity attribute might vary by vendor. To ensure the successful establishment of a tunnel between two devices from different vendors, correctly configure their respective link attribute and affinity attribute.
To configure the affinity attribute for an MPLS TE tunnel:
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter MPLS TE tunnel interface view. | interface tunnel tunnel-number [ mode mpls-te ] | N/A |
3. Set an affinity for the MPLS TE tunnel. | mpls te affinity-attribute attribute-value [ mask mask-value ] | By default, the affinity is 0x00000000, and the mask is 0x00000000. The default affinity matches all link attributes. |
Setting a setup priority and a holding priority for an MPLS TE tunnel
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter MPLS TE tunnel interface view. | interface tunnel tunnel-number [ mode mpls-te ] | N/A |
3. Set a setup priority and a holding priority for the MPLS TE tunnel. | mpls te priority setup-priority [ hold-priority ] | By default, the setup priority and the holding priority are both 7 for an MPLS TE tunnel. |
Configuring an explicit path for an MPLS TE tunnel
An explicit path is a set of nodes. The relationship between any two neighboring nodes on an explicit path can be either strict or loose.
Strict—The two nodes must be directly connected.
Loose—The two nodes can have devices in between.
When establishing an MPLS TE tunnel between areas or ASs, you must perform the following tasks:
Use a loose explicit path.
Specify the ABR or ASBR as the next hop of the path.
Make sure the tunnel's ingress node and the ABR or ASBR can reach each other.
To configure an explicit path for a MPLS TE tunnel:
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Create an explicit path and enter its view. | explicit-path path-name | By default, no explicit paths exist. |
3. Enable the explicit path. | undo disable | By default, an explicit path is enabled. |
4. Add or modify a node in the explicit path. | nexthop [ index index-number ] ip-address [ exclude | include [ loose | strict ] ] | By default, an explicit path does not include any node. You can specify the include keyword to have the CRLSP traverse the specified node or the exclude keyword to have the CRLSP bypass the specified node. |
5. Return to system view. | quit | N/A |
6. Enter MPLS TE tunnel interface view. | interface tunnel tunnel-number [ mode mpls-te ] | N/A |
7. Configure the MPLS TE tunnel interface to use the explicit path, and specify a preference value for the explicit path. | mpls te path preference value explicit-path path-name [ no-cspf ] | By default, MPLS TE uses the calculated path to establish a CRLSP. |