[c-nsp] EoMPLS VC up on one side, not on the other.

Stephen Fulton sf at lists.esoteric.ca
Fri Nov 14 23:16:05 EST 2008


I've got an EoMPLS VC between two devices.  Device A is a Cisco 3750 Metro, 
Device B is a ME6524.  There are some intermediary devices in between.

The VC is up on the 3750M.  The VC is down on the ME6524.  There is a targeted 
LDP session configured on both sides, both are up.

Both hosts are in OSPF Area 0, and each's /32 Loopback is seen in both the FIB 
and RIB.

I'm curious why the VC would be seen as up on the 3750M, but down on the ME6524. 
  The only clue I have found is in the following snippet, the Next hop is listed 
as an Invalid ADDR.

ME6524#sh mpls l2transport vc 655 detail
Local interface: Vl655 up, line protocol up, Eth VLAN 655 up
   Destination address: 10.200.1.8, VC ID: 655, VC status: down
     Output interface: none, imposed label stack {1491 69}
     Preferred path: not configured
     Default path: active
     Next hop: Invalid ADDR  <---- ??
   Create time: 00:39:19, last status change time: 00:19:19
   Signaling protocol: LDP, peer 10.200.20.1:0 up
     MPLS VC labels: local 311, remote 69
     Group ID: local 0, remote 0
     MTU: local 1500, remote 1500
     Remote interface description: *Redacted*
   Sequencing: receive disabled, send disabled
   VC statistics:
     packet totals: receive 1130, send 0
     byte totals:   receive 76832, send 0
     packet drops:  receive 0, send 0

However, the 3750M's /32 is listed in the proper CEF adjacency, pointing to the 
correct cross-connect VLAN.  The RIB entry is fine.

The ME6524 is running SXH 3a, the 3750M is running 12.2(44)SE2.

Ideas?

-- Stephen


More information about the cisco-nsp mailing list