H3C Technologies H3C Intelligent Management Center - Manual (Page 178)

2. In the Configure Static CR-LSP section of the page, click the Modify icon to modify the basic
information of a node.
To delete a static CR-LSP node that you have added:
1. Click Service > MPLS TE Manager > MPLS TE Tunnel Mng from the tabular navigation system on the
top of the IMC main page.
2. In the Configure Static CR-LSP section of the page, click the Delete icon to delete the node.
Configuring an MPLS TE tunnel using dynamic signaling
protocol
Dynamic signaling protocol allows you to create an MPLS TE tunnel that can adapt to network changes
and implement redundancy, FRR, and other advanced features. Unlike the MPLS TE tunnel created using
static CR-LSP, the nodes along the tunnel created using dynamic signaling protocol are not necessarily
fixed. However, if you want to specify certain nodes for your tunnel to traverse, you can specify them in
an explicit path.
The following describes how to create an MPLS TE tunnel with a dynamic signaling protocol:
• Configure MPLS TE properties for links and advertise them through IGP TE extension to form a TEDB.
• Configure tunnel constraints.
• Use the CSPF algorithm to calculate a preferred path based on the TEDB and tunnel constraints.
• Establish the path using the signaling protocol RSVP-TE.
NOTE:
To form a TEDB, you must configure the IGP TE extension for the nodes on the network to send TE LSAs. If
the IGP TE extension is not configured, the CR-LSP is created based on IGP routing rather than computed
by CSPF.
Configuration prerequisites
Before making the configuration, do the following:
• Configure Static Routing or an IGP protocol to make sure that all LSRs are reachable.
• Configure MPLS basic capabilities.
• Configure MPLS TE basic capabilities.
You need to make sure that MPLS and MPLS TE basic capabilities are enabled on your devices before
you can manage your TE networks using MPLS TE Management. The configuration instructions for
enabling MPLS and MPLS TE basic capabilities may differ from device to device. For detailed
configuration instructions, see the configuration guide of your device.
168