69
You need to create a bi-directional MPLS TE tunnel and enable forwarding adjacency at both ends of the
tunnel to make forwarding adjacency take effect.
To configure forwarding adjacency:
To do…
Use the command...
Remarks
Enter system view
system-view
––
Enter MPLS TE tunnel interface view
interface tunnel
tunnel-number
––
Enable IGP to advertise the route of
the MPLS TE tunnel to IGP
neighbors.
mpls te igp advertise
[
hold-time
value
]
Required
Routes of MPLS TE tunnels are not
advertised to IGP neighbors by
default.
Assign a metric to the MPLS TE
tunnel
mpls te igp metric
{
absolute
|
relative
}
value
Optional
The metrics of TE tunnels equal the
metrics of their corresponding IGP
routes by default.
Submit current tunnel configuration
mpls te commit
Required
Exit to system view
quit
––
Enter OSPF view
ospf
[
process-id
]
––
Enable forwarding adjacency
enable traffic-adjustment
advertise
Required
Disabled by default
NOTE:
If you use automatic route advertisement, you must specify the destination address of the TE tunnel as the
LSR ID of the peer and advertise the tunnel interface address to IGPs, such as OSPF and ISIS.
Configuring traffic forwarding tuning parameters
In MPLS TE, you may configure traffic forwarding tuning parameters such as the failed link timer and
flooding thresholds to change paths that IP or MPLS traffic flows traverse or to define type of traffic that
may travel down a TE tunnel.
Configuration prerequisites
The configurations described in this section are used in conjunction with CSPF and a dynamic signaling
protocol, such as RSVP-TE.
Configuration procedure
Configuring the failed link timer
A CSPF failed link timer starts once a link goes down. If IGP removes or modifies the link before the timer
expires, CSPF will update information about the link in TEDB and stops the timer. If IGP does not remove
or modify the link before the timer expires, the state of the link in TEDB will change to up.
To configure failed link timer: