[c-nsp] MPLS issue on Cat5500-rsm

[Oliver Boehmer (oboehmer)]

Sean Watkins <mailto:sean at northrock.bm> wrote on Friday, March 03, 2006
3:54 PM:

> \
>>> 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
> 
> P-2#show mpls forwarding-table labels 18 detail
> Local  Outgoing    Prefix            Bytes tag  Outgoing   Next Hop
> tag    tag or VC   or Tunnel Id      switched   interface
> 18     Untagged    10.1.1.0/24       4668       Vl72       10.1.3.1
>         MAC/Encaps=0/0, MRU=1528, Tag Stack{}
>         No output feature configured
>     Per-packet load-sharing
> P-2#
> 
> I take it the no outbound label, is the issue?

well, no, it lacks the CEF rewrite, you should see something like
MAC/Encaps=14/14 and a rewrite string..
But the fact that you don't see any outgoing labels over this interface
points to a problem as well. Does the neighbor advertise any label
bindings for those prefixes? How does the LIB look like?

Which MTU are you using on the links? Looks like "tag mtu 1524". I'm not
sure if you can get those large packets through the RSM (can't dive deep
into this at the moment), can you try with an increased "ip mtu" and a
large IP packet?

>> as "show adjacency vlan172"? For a yet-to-be determined
>> reason, the LFIB has an incomplete adjacency.
> 
> P-2#show adjacency vlan72
> Protocol Interface                 Address
> TAG      Vlan72                    10.1.3.1(7)
> IP       Vlan72                    10.1.3.1(19)

Hmm, so we have a tag adjacency to the neighbor.. 

>> Either way: I don't think we support MPLS on the Cat5500's
>> RSM/RSFC, not sure..
>> 
> 
> Software advisor says its in all the IOS for the RMS.. Mpls in every
> other way appears to work?

Interesting.. I thought I heard otherwise.

	oli