Re: [c-nsp] MPLS L3VPN - EIGRP routes not being advertised to CE router
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 t...@bobbroadband.com 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 1 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 cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] MPLS L3VPN - EIGRP routes not being advertised to CE router
Does the customer know that the service he's running on is a beta/an experimental one, i.e. never been tested for production backbone, operations and maintenance have no or very little knowledge about and thus no SLAs apply? You should have explained to the customer that you do only BGP and Static. Now you got yourself in all sorts of problems what if there are some severe bugs involved with running EIGRP on your software version? adam ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] MPLS L3VPN - EIGRP routes not being advertised to CE router
The customer knows that he's the 'guinea pig' for this service. It was all set up and configured as L3VPN w/BGP until the customer changed his mind a couple days ago. When you are a start-up, you sometimes don't get to say 'no' to the customer... -- Tim Huffman -Original Message- From: Adam Vitkovsky [mailto:adam.vitkov...@swan.sk] Sent: Wednesday, June 12, 2013 2:00 AM To: Tim Huffman; cisco-nsp@puck.nether.net Subject: RE: [c-nsp] MPLS L3VPN - EIGRP routes not being advertised to CE router Does the customer know that the service he's running on is a beta/an experimental one, i.e. never been tested for production backbone, operations and maintenance have no or very little knowledge about and thus no SLAs apply? You should have explained to the customer that you do only BGP and Static. Now you got yourself in all sorts of problems what if there are some severe bugs involved with running EIGRP on your software version? adam ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] MPLS L3VPN - EIGRP routes not being advertised to CE router
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Brisson wrote: Right, in IP Base an eigrp device can only function in stub mode which means it won't pass on any dynamically learned routes. Static routes would fix this problem but I doubt u want to go down that road. Since it's stub, it should be able to send default and summary routes. Generate a default and use the eigrp summary-address command on the CE facing interface to generate a summarized EIGRP route toward the CE. - -- = bep -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlG4lf0ACgkQE1XcgMgrtyaAggCgpUTxS0OLMOPCREJ2jaHD+iTt rcUAoLdg0VgPFSDyFOnQ1h/TXgL1vASC =wdrr -END PGP SIGNATURE- ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] MPLS L3VPN - EIGRP routes not being advertised to CE router
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 1 1 255 1 1500 no auto-summary autonomous-system 65002 eigrp stub connected summary exit-address-family eigrp stub connected summary router bgp 1234 no synchronization bgp log-neighbor-changes bgp deterministic-med bgp maxas-limit 50 redistribute connected redistribute static neighbor 10.10.10.1 remote-as 1234 neighbor 10.10.10.1 description Route Reflector neighbor 10.10.10.1 update-source Loopback0 neighbor 10.10.10.1 next-hop-self maximum-paths ibgp 2 distance bgp 200 200 200 no auto-summary ! address-family vpnv4 neighbor 10.10.10.1 activate neighbor 10.10.10.1 send-community extended exit-address-family ! address-family ipv4 vrf CustomerA redistribute eigrp 65002 no auto-summary no synchronization exit-address-family Here is the output showing the EIGRP neighbor up: #sh ip eigrp vrf CustomerA 65002 neighbors IP-EIGRP neighbors for process 65002 H Address Interface Hold Uptime SRTT RTO Q Seq (sec) (ms) Cnt Num 0 10.3.63.2 Gi1/11.89814 22:31:388 450 0 36 And the EIGRP topology: #sh ip eigrp vrf CustomerA 65002 topology IP-EIGRP Topology Table for AS(65002)/ID(10.3.63.1) Routing Table: CustomerA Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply, r - reply Status, s - sia Status P 10.3.19.0/30, 1 successors, FD is 2816 via VPNv4 Sourced P 10.3.18.0/30, 1 successors, FD is 28160 via VPNv4 Sourced P 10.3.63.0/30, 1 successors, FD is 25856 via Connected, GigabitEthernet1/11.898 P 10.3.49.4/30, 1 successors, FD is 2816 via VPNv4 Sourced P 172.17.58.4/32, 1 successors, FD is 156160 via VPNv4 Sourced P 172.17.58.8/32, 1 successors, FD is 153856 via 10.3.63.2, GigabitEthernet1/11.898 Here's the routing table, showing routes learned from the customer (via EIGRP), as well as routes learned from PE2: #sh ip route vrf CustomerA Routing Table: CustomerA Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route Gateway of last resort is not set 172.17.0.0/32 is subnetted, 2 subnets B 172.17.58.4 [200/156160] via 10.10.10.3, 22:05:23 ==This is the loopback from CE2 D 172.17.58.8 ==This is the loopback from CE1 [90/153856] via 10.3.63.2, 22:06:01, GigabitEthernet1/11.898 10.0.0.0/30 is subnetted, 4 subnets B 10.3.18.0 [200/0] via 10.10.10.3, 4d22h ==This is the VRF interface from PE2 C 10.3.63.0 is directly connected, GigabitEthernet1/11.898 ==This is the VRF interface on PE1 And this is what the customer side looks like: Interface GigabitEthernet2/0/6 ip address 10.3.63.2 255.255.255.252 interface Loopback10 ip address 172.17.58.8 255.255.255.255 router eigrp 65002 default-metric 1 1 255 1 1500 no auto-summary network 10.3.63.0 0.0.0.3 network 172.17.58.0 0.0.0.255 ! ! ! ! CE1#sh ip eigrp 65002 neigh EIGRP-IPv4:(65002) neighbors for process 65002 H Address Interface Hold Uptime SRTT RTO Q Seq (sec) (ms) Cnt Num 0 10.3.63.1
Re: [c-nsp] MPLS L3VPN - EIGRP routes not being advertised to CE router
-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 1 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 cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] MPLS L3VPN - EIGRP routes not being advertised to CE router
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 1 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 cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] MPLS L3VPN - EIGRP routes not being advertised to CE router
That restriction is a licensing one, so you'll have to see if you have high enough software for EIGRP to be allowed to function, or if its a bug. -Blake On Tue, Jun 11, 2013 at 6:34 PM, Tim Huffman t...@bobbroadband.com 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 1 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 cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] MPLS L3VPN - EIGRP routes not being advertised to CE router
Right, in IP Base an eigrp device can only function in stub mode which means it won't pass on any dynamically learned routes. Static routes would fix this problem but I doubt u want to go down that road. -dan Sent from a mobile phone with a tiny keyboard On Jun 11, 2013, at 8:32 PM, Blake Dunlap iki...@gmail.com wrote: That restriction is a licensing one, so you'll have to see if you have high enough software for EIGRP to be allowed to function, or if its a bug. -Blake On Tue, Jun 11, 2013 at 6:34 PM, Tim Huffman t...@bobbroadband.com 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 1 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 cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
