LDP connection between Cisco and Tellabs

mel_bs · ‎08-09-2007

Hi,

I am working with an InterOps between Cisco12410 and Tellabs8800. The two boxes were connected directly using its GigabitEthernet ports.

I was able to define the MPLS LDP on the Cisco and Tellabs (cisco is in ldp discovery mode), however the neighborship between the two boxes cannot establish connection. When I used the "targeted" mode the status went active but LFIB shows "untagged" on the Tellabs IP address. The Cisco display is shown below

Is there something else I need to configure over the Cisco to make the LDP establish connection to Tellabs. Or does anybody knows what to work over the Tellabs?

GSR#sh mpls inter

Interface IP Tunnel Operational

GigabitEthernet2/2 Yes (ldp) No Yes

GigabitEthernet2/3 Yes (ldp) No Yes

GSR#sh ip ospf neigh

Neighbor ID Pri State Dead Time Address Interface

10.220.4.25 1 FULL/DR 00:00:38 10.254.10.2 GigabitEthernet2/2

172.27.2.1 1 FULL/BDR 00:00:37 10.254.1.2 GigabitEthernet2/3

GSR#sh mpls ldp discovery

Local LDP Identifier:

1.1.1.1:0

Discovery Sources:

Interfaces:

GigabitEthernet2/2 (ldp): xmit/recv

LDP Id: 2.2.2.2:0

GigabitEthernet2/3 (ldp): xmit

Targeted Hellos:

1.1.1.1 -> 172.27.2.1 (ldp): active, xmit/recv

LDP Id: 172.27.2.1:0

GSR#sh ip route

Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP

D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP

i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2

ia - IS-IS inter area, * - candidate default, U - per-user static route

o - ODR

Gateway of last resort is not set

1.0.0.0/32 is subnetted, 1 subnets

C 1.1.1.1 is directly connected, Loopback0

2.0.0.0/32 is subnetted, 1 subnets

O 2.2.2.2 [110/2] via 10.254.10.2, 01:05:36, GigabitEthernet2/2

172.27.0.0/32 is subnetted, 1 subnets

O E2 172.27.2.1 [110/0] via 10.254.1.2, 01:05:36, GigabitEthernet2/3

10.0.0.0/30 is subnetted, 2 subnets

C 10.254.1.0 is directly connected, GigabitEthernet2/3

C 10.254.10.0 is directly connected, GigabitEthernet2/2

GSR#sh mpls forwarding-table

Local Outgoing Prefix Bytes tag Outgoing Next Hop

tag tag or VC or Tunnel Id switched interface

16 Untagged 172.27.2.1/32 0 Gi2/3 10.254.1.2

18 0 2.2.2.2/32 0 Gi2/2 10.254.10.2

Thanks,

Mel Sebastian

mheusing · ‎08-09-2007

Hi Mel,

the output means that there are no LDP hellos received on GigabitEthernet2/3.

So you have to check the Tellabs device, why it does not send hellos on the interface.

The targeted LDP session is good news, as it shows basic interoperability.

Can you also post "show mpls ldp neighbor 172.27.2.1"? It would be good to check the tellabs box, if the GigE to the GSR is MPLS enabled.

Regards, Martin

mel_bs · ‎08-10-2007

I have below the "show mpls ldp neighbor" command which you requested. The Tellabs ip address is 172.27.2.1

GSR#sh mpls ldp neigh

Peer LDP Ident: 172.27.2.1:0; Local LDP Ident 1.1.1.1:0

TCP connection: 172.27.2.1.1027 - 1.1.1.1.646

State: Oper; Msgs sent/rcvd: 482/418; Downstream

Up time: 02:18:59

LDP discovery sources:

Targeted Hello 1.1.1.1 -> 172.27.2.1, active

Addresses bound to peer LDP Ident:

10.254.1.2 172.27.2.1

Peer LDP Ident: 2.2.2.2:0; Local LDP Ident 1.1.1.1:0

TCP connection: 2.2.2.2.21799 - 1.1.1.1.646

State: Oper; Msgs sent/rcvd: 156/154; Downstream

Up time: 02:09:44

LDP discovery sources:

GigabitEthernet2/2, Src IP addr: 10.254.10.2

Targeted Hello 1.1.1.1 -> 2.2.2.2, active, passive

Addresses bound to peer LDP Ident:

2.2.2.2 10.254.10.2

Note: Tellabs is connected to Gi2/3. Cisco7609 is connected to Gi2/2. You might notice the neighborship status over the Gi2/2, config was changed having targeted connection over the GSR. Please focus only on Gi2/3 connection to Tellabs.

GSR#sh mpls ldp dis

Local LDP Identifier:

1.1.1.1:0

Discovery Sources:

Interfaces:

GigabitEthernet2/2 (ldp): xmit/recv

LDP Id: 2.2.2.2:0

GigabitEthernet2/3 (ldp): xmit

Targeted Hellos:

1.1.1.1 -> 172.27.2.1 (ldp): active, xmit/recv

LDP Id: 172.27.2.1:0

1.1.1.1 -> 2.2.2.2 (ldp): active/passive, xmit/recv

LDP Id: 2.2.2.2:0

>>>>>>>>>>>>>>>>>

Thanks,

Mel Sebastian

oldcreek12 · ‎08-10-2007

The information on GSR side all look OK, as Martin suggested, you need to check Tellabs side configuration to see why the interface which connects to GSR's gi2/3 is not sending LDP link hellos. I am sure Tellabs TMOS has something similar to IOS's sh mpls ldp neighbor and sh mpls ldp discover etch