Not sure if it's available in IP Base but you can still allow dynamically learned routes to be propagated out of stub with leak-map - 'eigrp stub leak-map bla'.
On Wed, Jun 12, 2013 at 1:34 AM, Tim Huffman <[email protected]> wrote: > >> Although we've done several MPLS VPNs in the past, we've always used > BGP as the PE-CE routing protocol. Now, I have a new customer that wants to > use EIGRP instead. The configuration doesn't seem too hard, but something > isn't working correctly: > >> > >> > >> - We are learning routes from the customer at each location (2 > currently, with more to follow) > >> > >> - PE1 and PE2 both learn routes from their respective CE1 and > CE2 > >> > >> - Those routes get passed onto our Route Reflector > >> > >> - PE2 knows routes in the VRF from PE1, and vice versa > >> > >> - Neither CE1 nor CE2 are learning any routes, other than > connected ones > >> > >> The customer is getting antsy, and from the documentation I can find, > we should be set up correctly. Any help you guys can provide would be > GREATLY appreciated! Now the details: > >> > >> PE1=====RR======PE2 > >> | | > >> | | > >> CE1 CE2 > >> > >> Our Route Reflector is a Catalyst 6503 w/SUP720-3BXL running > 12.2(33)SXH5. The two PEs are ME-C6524GT-8S running 12.2(18)ZU2. Below is > the config from the PE routers (IPs and ASNs changed to protect the > innocent): > >> > >> ip vrf CustomerA > >> description L3VPN for CustomerA > >> rd 65002:10 > >> route-target export 65002:10 > >> route-target import 65002:10 > >> > >> router eigrp 65002 > >> auto-summary > >> ! > >> address-family ipv4 vrf CustomerA > >> redistribute bgp 1234 > >> network 10.3.63.0 0.0.0.3 > >> default-metric 10000 1 255 1 1500 > >> no auto-summary > >> autonomous-system 65002 > >> eigrp stub connected summary > >> exit-address-family > >> eigrp stub connected summary > >> > > > You have it set up as EIGRP Stub with Summary. What routes are you > expecting to see at each of the respective CE's? > > That command was put in by default, and when we try to remove it, we get > this error "EIGRP is restricted to stub configurations only." It looks like > this may be related to bug CSCeh58135. Unfortunately, I have very little > experience with EIGRP. Do you think that's the likely source of the problem? > > -- > Tim Huffman > > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
