[nsp] MPLS -- EGP vs. IGP problem?

[Oliver Boehmer (oboehmer)]

> I've got an MPLS testbed setup with several cisco 2500s running
> c2500-p-l.tag.  There is no problem in getting packets to be
> tag-swithched if the destination is known via the IGP.  BGP learned
> destinations, however, don't get tag-switched, and thus can't get
> across the (non BGP enabled) core P routers.
> 
> I thought that the only requirement was that the BGP next-hop had
> to able to be tag-switched.  I'm obviously missing something - but is
> it due to the unsupported IOS version I'm running, or am I missing
> something more fundamental?  (Prefix length msimatches?)

Make sure your BGP next-hops are visible as /32 throughout your entire
MPLS network, any summarization of your network addresses can break your
end-to-end LSP.  
I'm mentioning this because I see your BGP-NH 192.168.2.2 visible as /24
in your routing table

	oli