[c-nsp] Eigrp redistabution of static routes into iBGP

[Oliver Boehmer (oboehmer)]

Scott,

don't really understand the info you've provided, don't know which
router plays which role in your topology. In your 2nd post, you
indicated that the prefix is injected somewhere else. This could point
to the way EIGRP treats backdoors using the cost community (see
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwf
t/release/122s25/fsbgpcce.htm). Can you please do a "show ip bgp vpnv4
vrf ... 63.123.149.37" on all the PEs which receive the prefix from a
CE? 

	oli

Scott Ingram <mailto:SIngram at clayton.com> wrote on Monday, October 01,
2007 3:03 PM:

> The route is being advertised from Eigrp
> S       63.123.149.37/32 [1/0] via 172.18.44.1
> DEN-6509-1#
> D EX    63.123.149.37/32 [170/281856] via 172.18.44.2, 2d10h, Vlan44
> S*   0.0.0.0/0 [1/0] via 172.18.44.254
> 
> DEN-7206-1#sh ip route vrf 63.123.149.37
> % IP routing table 63.123.149.37 does not exist
> 
>    Network          Next Hop            Metric LocPrf Weight Path
> *> 63.239.161.112/30
>                     172.18.44.1         220928         32768 ?
> 
> 
> 
> -----Original Message-----
> From: Oliver Boehmer (oboehmer) [mailto:oboehmer at cisco.com]
> Sent: Monday, October 01, 2007 2:17 AM
> To: Scott Ingram; cisco-nsp at puck.nether.net
> Subject: RE: [c-nsp] Eigrp redistabution of static routes into iBGP
> 
> Scott Ingram <> wrote on Sunday, September 30, 2007 9:28 PM:
> 
>> I'm having an issue with a static route to that wont redistribute
>> into my MPLS iBGP.  The local subnet can see the device.
> 
> can you please describe the PE-CE topology, show the VRF/MP-iBGP and
> interface configuration, and post "show ip route vrf ... x.x.x.x",
> "show 
> ip eigrp vrf ... topology x.x.x.x y.y.y.y" and "show ip bgp vpnv4 vrf
> ... x.x.x.x"
> 
>> Once I do an extended trace from the MPLS serial port it times out.
> 
> what do you mean? Which source address are you using? Is this address
> reachable from the VRF/CE?
> 
> 	oli
> IMPORTANT NOTICE:
> 
> This message is intended only for the use of the individual or entity
> to which it is addressed and may contain information that is
> privileged, confidential and exempt from disclosure under applicable
> law.  If you have received this message in error, you are hereby
> notified that we do not consent to any reading, dissemination,
> distribution or copying of this message.  If you have received this
> communication in error, please notify the sender immediately and
> destroy the transmitted information.