H3C Technologies H3C S7500E Series Switches - Manual (Page 102)

3-20
To do… Use the command... Remarks
Enable IS-IS TE
traffic-eng [ level-1 | level-2 |
level-1-2 ]
Required
Disabled by default
z
For more information about IS-IS, see IS-IS Configuration in the Layer 3 - IP Routing
Configuration Guide .
z
IS-IS TE does not support secondary IP address advertisement. With IS-IS TE enabled on an
interface configured with multiple IP addresses, IS-IS TE advertises only the primary IP address
of the interface through the sub-TLV of IS reachability TLV (type 22). You are recommended to
avoid enabling IS-IS TE on an interface configured with secondary IP addresses.
Configuring an MPLS TE explicit path
An explicit path is a set of nodes. The relationship between any two neighboring nodes on an explicit
path can be either of the following:
z
Strict: where the two nodes are directly connected.
z
Loose: where the two nodes have devices in between.
When inserting nodes to an explicit path or modifying nodes on it, you may configure the include
keyword to have the established LSP traverse the specified nodes or the exclude keyword to have the
established LSP bypass the specified nodes.
Follow these steps to configure an MPLS TE explicit path:
To do… Use the command... Remarks
Enter system view system-view ––
Create an explicit path for MPLS
TE tunneling and enter its view
explicit-path path-name [ disable
| enable ]
Required
Add a node to the explicit path
add hop ip-address1 [ include
[ loose | strict ] | exclude ] { after |
before } ip-address2
Optional
By default, the include keyword
and the strict keyword apply. In
other words, the explicit path
traverses the specified node and
the next node is a strict node.
Specify a next hop IP address on
the explicit path
next hop ip-address [ include
[ loose | strict ] | exclude ]
Required
The next hop is a strict node by
default.
Repeat this step to define a
sequential set of the hops that the
explicit path traverses.