[c-nsp] MPLS issue on Cat5500-rsm

[Oliver Boehmer (oboehmer)]

Sean Watkins <> wrote on Friday, March 03, 2006 3:15 PM:

> Hi,
> 
> I'm trying to build a MPLS VPN across numerous Cat5 RSM bladess setup
> as P routers. Not exactly sure if its supported inside the 5505, tdp
> comes up and builds a map ok, but it appears frames with a label
> stack die when hitting the C5-RSM. I see this when doing a "debug
> mpls drop" 
> 
> 
> 00:56:02: rsp_tagswitch: Pkt drop -- rewrite incomplete, incg label 18
> hwinput Vl71
> 00:56:04: rsp_tagswitch: Pkt drop -- rewrite incomplete, incg label 18
> hwinput Vl71
> 00:56:06: rsp_tagswitch: Pkt drop -- rewrite incomplete, incg label 18
> hwinput Vl71
> 00:56:08: rsp_tagswitch: Pkt drop -- rewrite incomplete, incg label 18
> hwinput Vl71
> 00:56:10: rsp_tagswitch: Pkt drop -- rewrite incomplete, incg label 18
> hwinput Vl71
> 
> Any idea? The 18 is indeed in the forwarding table?
> 
> P-2#show mpls forwarding-table
> Local  Outgoing    Prefix            Bytes tag  Outgoing   Next Hop
> tag    tag or VC   or Tunnel Id      switched   interface
> 16     Pop tag     5.1.1.2/32        0          Vl71       10.1.2.1
> 17     Untagged    5.1.1.206/32      0          Vl72       10.1.3.1
> 18     Untagged    10.1.1.0/24       1840       Vl72       10.1.3.1
> 19     Untagged    5.1.1.1/32        0          Vl72       10.1.3.1
> 
> I've looked on CCO, for that above error message, nothing found?

can you check "show mpls forwarding label 18 detail" as well as "show
adjacency vlan172"? For a yet-to-be determined reason, the LFIB has an
incomplete adjacency. 

BUT: why do you have "Untagged" on vlan172? This breaks any MPLS-VPN..

Either way: I don't think we support MPLS on the Cat5500's RSM/RSFC, not
sure..

	oli