3com S7906E 설치 설명서

 

1-23 

z

 

If Hello adjacency exists between two peers, no remote adjacency can be established between 
them. If remote adjacency exists between two peers, you can configure local adjacency for them. 
However, the local adjacency can be established only when the transport address and keepalive 
settings of the two peers match respectively, in which case  the remote adjacency will be removed. 
That is, only one remote session or local session can exist between two LSRs, and the local 
session takes precedence over the remote session. 

z

 

The remote peer IP address to be configured must be different from all existing remote peer IP 
addresses. Otherwise, the configuration fails. 

z

 

The IP address specified as the LDP transport address must be the IP address of an interface on 
the device. 

 

You can specify the routes that are allowed to trigger the establishment of LSPs:  

z

 

All static and IGP routes. 

z

 

Static and IGP routes permitted by an IP address prefix list. 

Follow these steps to configure the policy for triggering LSP establishment: 

Enter system view 

— 

Enter MPLS view 

— 

Configure the LSP 
establishment triggering policy 

 [ vpn-instance 

 ] { all | 

 prefix-name } 

Optional 
By default, only local loopback 
addresses with 32-bit masks 
can trigger LDP to establish 
LSPs. 

 

z

 

For an LSP to be established, an exactly matching routing entry must exist on the LSR. With 
loopback addresses using 32-bit masks, only exactly matching host routing entries can trigger LDP 
to establish LSPs. 

z

 

If the vpn-instance vpn-instance-name combination is specified, the command configures an LSP 
establishment triggering policy for the specified VPN instance; otherwise, the command configures 
an LSP establishment triggering policy for the public network routes. 

z

 

For information about IP address prefix list, refer to Routing Policy Configuration in the IP Routing 

. 

 

Follow these steps to configure the LDP label distribution control mode: