MPLS addresses bound to peer LDP Ident output
In an MPLS implementation, the show
mpls ldp neighbor command can be used to view the details of an LDP peering. The following is an example of the output from this command:
P#show mpls ldp neighbor Peer LDP Ident: 220.127.116.11:0; Local LDP Ident 18.104.22.168:0 TCP connection: 22.214.171.124.646 - 126.96.36.199.55065 State: Oper; Msgs sent/rcvd: 10/11; Downstream Up time: 00:02:39 LDP discovery sources: FastEthernet0/0, Src IP addr: 192.168.23.2 Addresses bound to peer LDP Ident: 192.168.12.2 192.168.23.2 188.8.131.52 Peer LDP Ident: 184.108.40.206:0; Local LDP Ident 220.127.116.11:0 TCP connection: 18.104.22.168.52817 - 22.214.171.124.646 State: Oper; Msgs sent/rcvd: 10/11; Downstream Up time: 00:02:02 LDP discovery sources: FastEthernet0/1, Src IP addr: 192.168.34.4 Addresses bound to peer LDP Ident: 192.168.34.4 192.168.45.4 126.96.36.199
The section headed
Addresses bound to peer LDP Ident: lists the address that might appear as the “next hop” addresses in the local routing table. These are used to maintain the Label Forwarding Information Base (LFIB).
There doesn’t seem to be any noticeable order in which these addresses are listed. This particular output comes from a topology where all of the listed IP addresses for both LDP peers are addresses that exist on the neighbors themselves.
It is simply a list, with seemingly no significance to the order in which those addresses appear.