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

[Oliver Boehmer (oboehmer)]

> 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  <---- ??
 

you've configured vlan-based EoMPLS (i.e. xconnect on the SVI). In order
for this to work on Cat65xx/Sup720, you need OSM/SIP as core-facing
linecard, something which isn't possible on the fixed-configuration
ME6524..
So you need to move xconnect to the physical port.

	oli