(Optional) Blocking LDP-IGP Synchronization on an Interface

If you do not want to run LDP-IGP synchronization on some interfaces, you can block the function on these interfaces.

Context

After the ldp-sync enable command is run in an IGP process, the following situations occur:

On a P2P network, the interfaces with the neighbor status of Up implement LDP-IGP synchronization.
On a broadcast network, if OSPF is used as an IG, the interfaces (with the neighbor status of Up) connecting the DR to a non-DR (or BDR) implement LDP-IGP synchronization. If IS-IS is used as an IGP, the interfaces (with the neighbor status of Up) connecting the DIS to a non-DIS implement LDP-IGP synchronization.

For the interfaces on a device bearing key services, ensure that this device is not on the backup path. You can block LDP-IGP synchronization on a specified interface of the NetEngine 8000 F.

Procedure

If OSPF is used, perform the following steps on the interfaces on both ends of the link between the node where the primary LSP and the backup LSP diverge from each other and its LDP peer on the primary LSP.
1. Run system-view
  The system view is displayed.
2. Run interface interface-type interface-number
  The view of an OSPF interface is displayed.
3. Run ospf ldp-sync block
  LDP-IGP synchronization is blocked on the interface.
  
  To block LDP-OSPF synchronization on a multi-area adjacency interface, run the ospf ldp-sync block multi-area area-id command.
4. Run commit
  The configuration is committed.
If IS-IS is used, perform the following steps on the interfaces on both ends of the link between the node where the primary LSP and the backup LSP diverge from each other and its LDP peer on the primary LSP.
1. Run system-view
  The system view is displayed.
2. Run interface interface-type interface-number
  The view of an IS-IS interface is displayed.
3. Run isis ldp-sync block
  LDP-IGP synchronization is blocked on the interface.
4. Run commit
  The configuration is committed.