22.05.2017 Views

nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

Nexus Switching 2nd Edition

Nexus Switching 2nd Edition

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

N7k-1(config)# router <strong>os</strong>pf 1<br />

N7k-1(config-router)# mpls ldp sync<br />

Example 12-14 shows several useful LDP operational comm<strong>and</strong>s. The first comm<strong>and</strong>, show<br />

mpls ldp bindings, shows the IP prefixes with their corresponding MPLS labels, which is<br />

called the Label Information Base (LIB). The local binding shows the label assigned by the<br />

router, which is, in turn, advertised to neighbors. The remote binding refers to a label-prefix<br />

learned via LDP from a neighbor. The comm<strong>and</strong> show mpls ldp discovery enables the<br />

network administrator to easily verify if LDP is running correctly. This comm<strong>and</strong> lists the<br />

interfaces in which LDP is running <strong>and</strong> also verifies that the interfaces are transmitting <strong>and</strong><br />

receiving LDP Hello packets. Lastly, the comm<strong>and</strong> show mpls ldp neighbor displays useful<br />

information about the status of LDP peers, including the neighborship state <strong>and</strong> operation<br />

LDP discovery sources.<br />

Example 12-14. Important LDP Operational Comm<strong>and</strong>s<br />

Click here to view code image<br />

N7k-1# sh mpls ldp bindings<br />

lib entry: 1.1.1.1/32, rev 2<br />

local binding: label: imp-null<br />

remote binding: lsr: 2.2.2.2:0, label: 16<br />

lib entry: 2.2.2.2/32, rev 6<br />

local binding: label: 16<br />

remote binding: lsr: 2.2.2.2:0, label: imp-null<br />

N7k-1# sh mpls ldp discovery<br />

Local LDP Identifier:<br />

1.1.1.1:0<br />

Discovery Sources:<br />

Interfaces:<br />

Ethernet10/18 (ldp): xmit/recv<br />

LDP Id: 2.2.2.2:0<br />

N7k-1# sh mpls ldp neighbor<br />

Peer LDP Ident: 2.2.2.2:0; Local LDP Ident 1.1.1.1:0<br />

TCP connection: 2.2.2.2.56735 - 1.1.1.1.646<br />

State: Oper; Msgs sent/rcvd: 8/10; Downstream<br />

Up time: 00:02:50<br />

LDP discovery sources:<br />

Ethernet10/18, Src IP addr: 192.168.0.2<br />

Addresses bound to peer LDP Ident:

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!