-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tim Huffman 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?


- -- 
=========
bep

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlG3pNEACgkQE1XcgMgrtyYhYwCdFes+3iaeqtT2PrNlxaDXFnyG
P68An3JfZtcBMIoY012Gj60YdRACvd+l
=qzg6
-----END PGP SIGNATURE-----
_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to