H3C Technologies H3C SR8800 - Manual (Page 31)

20
Step Command Remarks
3. Configure a label acceptance
control policy. accept-label peer peer-id ip-prefix
ip-prefix-name Optional.
Not configured by default.
4. Configure a label
advertisement control policy.
advertise-label ip-prefix
ip-prefix-name [ peer
peer-ip-prefix-name ]
Not configured by default.
NOTE:
For two neighboring LSRs, configuring a label acceptance control policy on the upstream LSR and
configuring a label advertisement control policy on the downstream LSR can achieve the same effect. To
reduce the network load, H3C recommends configuring only label advertisement control policies.
Maintaining LDP sessions
This section describes how to detect communication failures between remote LDP peers and reset LDP
sessions.
Configuring BFD for MPLS LDP
MPLS itself cannot detect a neighbor failure or link failure in time. If communication between two remote
LDP peers fails, the LDP session will be down, and as a result, MPLS forwarding will fail. By cooperating
with bidirectional forwarding detection (BFD), MPLS LDP can be quickly aware of communication failures
between remote LDP peers, improving performances of existing MPLS networks.
NOTE:
•
For more information about BFD, see High Availability Configuration Guide.
• An LSP can be bound to only one BFD session.
To configure BFD for MPLS LDP:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter MPLS LDP remote peer
view.
mpls ldp remote-peer
remote-peer-name
N/A
3. Enable BFD for MPLS LDP. remote-ip bfd Disabled by default
NOTE:
The cooperation of MPLS LDP and BFD can be used to detect communication failures between remote LDP
peers only. For related configuration examples, see the chapter “Configuring VPLS.”
Resetting LDP sessions
If you change LDP session parameters when some LDP sessions are up, the LDP sessions will not be able
to function normally. In this case, you need to reset the LDP session so that the LDP peers renegotiate
parameters and establish new sessions.