The routing table shows the routes known to the router and next hops. The MPLS LDP bindings show label bindings between local and remote routers for different prefixes. The neighbor information displays the LDP session details between routers.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
16 views4 pages
MPLS LDP Learning
The routing table shows the routes known to the router and next hops. The MPLS LDP bindings show label bindings between local and remote routers for different prefixes. The neighbor information displays the LDP session details between routers.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 4
ROUTING TABLE
C 1.1.1.1 is directly connected, Loopback0
O 2.2.2.2 [110/2] via 192.168.2.2, 01:30:19, GigabitEthernet1/0
O 3.3.3.3 [110/2] via 192.168.1.2, 01:24:25, GigabitEthernet0/0
O 4.4.4.4 [110/2] via 192.168.3.2, 01:15:52, GigabitEthernet2/0
O 5.5.5.5 [110/3] via 192.168.3.2, 01:11:46, GigabitEthernet2/0
[110/3] via 192.168.2.2, 01:11:36, GigabitEthernet1/0
C 192.168.1.0/30 is directly connected, GigabitEthernet0/0
L 192.168.1.1/32 is directly connected, GigabitEthernet0/0
C 192.168.2.0/30 is directly connected, GigabitEthernet1/0
L 192.168.2.1/32 is directly connected, GigabitEthernet1/0 192.168.3.0/24 is variably subnetted, 2 subnets, 2 masks C 192.168.3.0/30 is directly connected, GigabitEthernet2/0 L 192.168.3.1/32 is directly connected, GigabitEthernet2/0 192.168.23.0/30 is subnetted, 1 subnets O 192.168.23.0 [110/2] via 192.168.2.2, 01:30:36, GigabitEthernet1/0 [110/2] via 192.168.1.2, 01:24:25, GigabitEthernet0/0 192.168.25.0/30 is subnetted, 1 subnets O 192.168.25.0 [110/2] via 192.168.2.2, 01:30:36, GigabitEthernet1/0 192.168.34.0/30 is subnetted, 1 subnets O 192.168.34.0 [110/2] via 192.168.3.2, 01:15:52, GigabitEthernet2/0 [110/2] via 192.168.1.2, 01:24:25, GigabitEthernet0/0 192.168.45.0/30 is subnetted, 1 subnets O 192.168.45.0 [110/2] via 192.168.3.2, 01:15:52, GigabitEthernet2/0 R1#show mpls ldp bind lib entry: 1.1.1.1/32, rev 2 local binding: label: imp-null remote binding: lsr: 2.2.2.2:0, label: 200 lib entry: 2.2.2.2/32, rev 4 local binding: label: 16 remote binding: lsr: 2.2.2.2:0, label: imp-null lib entry: 3.3.3.3/32, rev 6 local binding: label: 17 remote binding: lsr: 2.2.2.2:0, label: 201 lib entry: 4.4.4.4/32, rev 8 local binding: label: 18 remote binding: lsr: 2.2.2.2:0, label: 202 lib entry: 5.5.5.5/32, rev 10 local binding: label: 19 remote binding: lsr: 2.2.2.2:0, label: 203 lib entry: 192.168.1.0/30, rev 12 local binding: label: imp-null remote binding: lsr: 2.2.2.2:0, label: 204 lib entry: 192.168.2.0/30, rev 14 local binding: label: imp-null remote binding: lsr: 2.2.2.2:0, label: imp-null lib entry: 192.168.3.0/30, rev 16 local binding: label: imp-null remote binding: lsr: 2.2.2.2:0, label: 205 lib entry: 192.168.23.0/30, rev 18 local binding: label: 20 remote binding: lsr: 2.2.2.2:0, label: imp-null lib entry: 192.168.25.0/30, rev 20 local binding: label: 21 remote binding: lsr: 2.2.2.2:0, label: imp-null lib entry: 192.168.34.0/30, rev 22 local binding: label: 22 remote binding: lsr: 2.2.2.2:0, label: 206 lib entry: 192.168.45.0/30, rev 24 local binding: label: 23 remote binding: lsr: 2.2.2.2:0, label: 207 R1#show mpls ldp neighbor Peer LDP Ident: 2.2.2.2:0; Local LDP Ident 1.1.1.1:0 TCP connection: 2.2.2.2.40508 - 1.1.1.1.646 State: Oper; Msgs sent/rcvd: 61/60; Downstream Up time: 00:40:31 LDP discovery sources: GigabitEthernet1/0, Src IP addr: 192.168.2.2 Addresses bound to peer LDP Ident: 192.168.25.1 192.168.2.2 192.168.23.1 2.2.2.2
R2#show mpls ldp neighbor
Peer LDP Ident: 1.1.1.1:0; Local LDP Ident 2.2.2.2:0 TCP connection: 1.1.1.1.646 - 2.2.2.2.40508 State: Oper; Msgs sent/rcvd: 105/107; Downstream Up time: 01:19:48 LDP discovery sources: GigabitEthernet1/0, Src IP addr: 192.168.2.1 Addresses bound to peer LDP Ident: 192.168.1.1 192.168.2.1 192.168.3.1 1.1.1.1 COMMENTS from the perspective of R1 Peer is R2 (correct), local Identity is own loopback address TCP Connection between FE_NE; IP and Port State: Operational, also no of messages
discovered on far-end with IF and IP
Interfaces configured on the R2 (Peer)
COMMENTS from the perspective of R2 Peer is R1 (correct), local Identity is own loopback address TCP Connection between FE_NE; IP and Port State: Operational, also no of messages