Thanks Randy and sorry for delay. Actually we are using eigrp topology on each location and connected each offices with DMVPN. So there were two things went wrong during installing new switches on our location.
There was a mismatched subnet mask on SWX-03 for VLAN 100 - it had a /25, but should be a /24. The EIGRP neighbor between these switches was bouncing, so by changing the subnet to a /24, this solved the EIGRP neighbor between SWX-03 and SWX-01. There were duplicate IP addresses on VLAN 500 on SWX-42-E and SWX-41-E - both had .2 configured on VLAN 500. I changed SWX-42-E VLAN500 to .3, and a new EIGRP neighbor formed. EIGRP was getting confused between the same IP address from two different switches. So after fixing these subnets on new swx's we were able to resolved the eigrp delay. Thanks everyone for your assistance. Regards, Khizer Rehman > CC: [email protected] > From: [email protected] > Subject: Re: [OSL | CCIE_RS] DMVPN EIGRP ROUTES UPDATE WITH DELAY > Date: Mon, 14 Jan 2013 07:16:28 -0800 > To: [email protected] > > Please share what was done to correct the issue. > > -Randy > > On Jan 12, 2013, at 5:33 AM, Khizer Rehman <[email protected]> wrote: > > > > > I didn't get any update from this group. But i have fixed this issue. Now > > the dmvpn failover is timeless, even our RDP session wasn't disconnect > > during failover. > > > > > > > > > > Regards, > > > > Khizer Rehman > > 0300 8113462 > > > > > > > > > > > > > > > > From: [email protected] > > To: [email protected]; [email protected] > > CC: [email protected] > > Subject: RE: [OSL | CCIE_RS] DMVPN EIGRP ROUTES UPDATE WITH DELAY > > Date: Mon, 7 Jan 2013 10:37:02 +0000 > > > > > > > > > > Please let em know if anyone have idea about why the eigrp update is slow. > > Here are the detail about DMPVN Setup. > > > > > > Tunne1 - 172.10.1.1/24 & Tunnel2 - 172.10.2.1/24 > > We have two HUB Routers. HUB-A and HUB-B. > > Both Hub routes have setup the tunnel1 and tunnel2 on it. HUB-A have > > tunnel1 172.10.1.1 and tunnel2 172.10.2.1 and HUB-B have tunnel1 172.10.1.2 > > and tunnel2 172.10.2.2. > > These all four tunnels are active with remote office. We have two tunnels > > T1 and T2 on each romote offices. > > We have two routers on one location, where we are having the issue. > > Router-A and Router-B. Both are connected with 3750 switch Switch-3750. > > We have data and voice network. Data Network 172.22.20.0/24 and Voice > > Network 172.30.90.0/24. > > We have data traffic preferable on T1 and voice traffic preferable on T2. > > Incase T1 goes down T2 shoud have the route. > > offset-list MakeThesePreferableThroughVoiceTunnel out 10000 Tunnel1 > > offset-list MakeThesePreferableThroughDataTunnel out 10000 Tunnel2 > > > > > > > > But when we shutdown the T1 ISP. The Routes updated for Data on HUB-A, > > HUB-B and Router-B but Router-A still showing the route from tunnel1. Which > > takes almost 1min and 40 seconds or less then 2 mins to update for T2. > > > > HUB-A Configuration > > > > interface Tunnel1 > > description HQ Data Preferred Tunnel > > bandwidth 1000 > > ip address 172.10.1.1 255.255.255.0 > > no ip redirects > > ip mtu 1400 > > no ip next-hop-self eigrp 765 > > ip nhrp authentication @auth > > ip nhrp map multicast dynamic > > ip nhrp network-id 63 > > ip tcp adjust-mss 1360 > > no ip split-horizon eigrp 765 > > delay 500 > > tunnel source 216.100.69.200 > > tunnel mode gre multipoint > > tunnel key 63 > > tunnel protection ipsec profile CoverTunnels > > ! > > ! > > interface Tunnel2 > > description HQ Voice Preferred Tunnel > > bandwidth 1000 > > ip address 172.10.2.1 255.255.255.0 > > no ip redirects > > ip mtu 1400 > > no ip next-hop-self eigrp 765 > > ip nhrp authentication @auth > > ip nhrp map multicast dynamic > > ip nhrp network-id 88 > > ip tcp adjust-mss 1360 > > no ip split-horizon eigrp 765 > > delay 500 > > tunnel source 216.100.69.201 > > tunnel mode gre multipoint > > tunnel key 88 > > tunnel protection ipsec profile CoverTunnels > > > > > > router eigrp 765 > > network 172.10.1.0 0.0.0.255 > > network 172.10.2.0 0.0.0.255 > > network 172.22.8.0 0.0.7.255 > > network 192.168.200.200 0.0.0.0 > > offset-list MakeThesePreferableThroughVoiceTunnel out 10000 Tunnel1 > > offset-list MakeThesePreferableThroughDataTunnel out 10000 Tunnel2 > > > > > > HUB-B Configuration > > > > interface Tunnel1 > > description COLO Data Preferred Tunnel > > bandwidth 500 > > ip address 172.10.1.2 255.255.255.0 > > no ip redirects > > ip mtu 1400 > > no ip next-hop-self eigrp 765 > > ip nhrp authentication @auth > > ip nhrp map multicast dynamic > > ip nhrp map 172.10.1.1 216.100.69.200 > > ip nhrp map multicast 216.100.69.200 > > ip nhrp network-id 63 > > ip nhrp nhs 172.10.1.1 > > ip tcp adjust-mss 1360 > > no ip split-horizon eigrp 765 > > delay 1000 > > tunnel source 216.30.100.200 > > tunnel mode gre multipoint > > tunnel key 63 > > tunnel protection ipsec profile CoverTunnels > > ! > > ! > > interface Tunnel2 > > description COLO Voice Preferred Tunnel > > bandwidth 500 > > ip address 172.10.2.2 255.255.255.0 > > no ip redirects > > ip mtu 1400 > > no ip next-hop-self eigrp 765 > > ip nhrp authentication @Auth > > ip nhrp map multicast dynamic > > ip nhrp map 172.10.2.1 216.100.69.201 > > ip nhrp map multicast 216.100.69.201 > > ip nhrp network-id 88 > > ip nhrp nhs 172.10.2.1 > > ip tcp adjust-mss 1360 > > no ip split-horizon eigrp 765 > > delay 1000 > > tunnel source 216.30.100.201 > > tunnel mode gre multipoint > > tunnel key 88 > > tunnel protection ipsec profile CoverTunnels > > > > > > > > Remote Site Router. We have two router on one location let say Location NJ. > > > > Router-A > > > > interface Tunnel1 > > description Primary TW1 Data Tunnel > > bandwidth 2000 > > ip address 172.10.1.25 255.255.255.0 > > no ip redirects > > ip mtu 1400 > > ip nhrp authentication Auth > > ip nhrp map multicast 216.30.100.200 > > ip nhrp map 172.10.1.2 216.30.100.200 > > ip nhrp map 172.10.1.1 216.100.69.200 > > ip nhrp map multicast 216.100.69.200 > > ip nhrp network-id 63 > > ip nhrp nhs 172.10.1.1 > > ip nhrp nhs 172.10.1.2 > > ip tcp adjust-mss 1360 > > delay 500 > > tunnel source GigabitEthernet0/1 > > tunnel mode gre multipoint > > tunnel key 63 > > tunnel protection ipsec profile CoverTunnels > > > > interface Tunnel2 > > no ip address > > shutdown > > end > > > > > > > > router eigrp 765 > > distribute-list LocalRangesToAdvertiseOverDMVPN out Tunnel1 > > distribute-list LocalRangesToAdvertiseOverDMVPN out Tunnel2 > > default-metric 1000000 100 255 1 1500 > > network 172.10.1.0 0.0.0.255 > > network 172.10.2.0 0.0.0.255 > > network 172.25.0.0 > > network 172.25.4.0 0.0.0.255 > > network 172.26.0.0 > > network 172.30.90.0 0.0.0.255 > > network 192.168.25.0 > > network 192.168.211.0 > > redistribute static > > offset-list MakeThesePreferableThroughVoiceTunnel out 10000 Tunnel1 > > offset-list MakeThesePreferableThroughDataTunnel out 10000 Tunnel2 > > > > > > > > Router-B > > > > interface Tunnel1 > > no ip address > > ! > > interface Tunnel2 > > description backup Nayatel Data Tunnel > > bandwidth 2000 > > ip address 172.10.2.25 255.255.255.0 > > no ip redirects > > ip mtu 1400 > > ip nhrp authentication @Auth > > ip nhrp map multicast 216.30.100.201 > > ip nhrp map 172.10.2.2 216.30.100.201 > > ip nhrp map 172.10.2.1 216.100.69.201 > > ip nhrp map multicast 216.100.69.201 > > ip nhrp network-id 88 > > ip nhrp nhs 172.10.2.1 > > ip nhrp nhs 172.10.2.2 > > ip tcp adjust-mss 1360 > > delay 500 > > tunnel source GigabitEthernet0/0 > > tunnel mode gre multipoint > > tunnel key 88 > > tunnel protection ipsec profile CoverTunnels > > > > > > router eigrp 765 > > redistribute static metric 10000 10000 100 100 1500 > > offset-list MakeThesePreferableThroughVoiceTunnel out 10000 Tunnel1 > > offset-list MakeThesePreferableThroughDataTunnel out 10000 Tunnel2 > > network 172.10.1.0 0.0.0.255 > > network 172.10.2.0 0.0.0.255 > > network 172.25.4.0 0.0.0.255 > > network 172.25.0.0 > > network 172.26.0.0 > > network 172.30.90.0 0.0.0.255 > > network 192.168.211.0 > > default-metric 1000000 100 255 1 1500 > > distribute-list LocalRangesToAdvertiseOverDMVPN out Tunnel1 > > distribute-list LocalRangesToAdvertiseOverDMVPN out Tunnel2 > > no auto-summary > > > > > > > > > > > > Regards, > > > > Khizer Rehman > > 0300 8113462 > > > > > > > > > > > > > >> From: [email protected] > >> To: [email protected]; [email protected] > >> Date: Sun, 6 Jan 2013 17:03:38 +0000 > >> CC: [email protected] > >> Subject: Re: [OSL | CCIE_RS] DMVPN EIGRP ROUTES UPDATE WITH DELAY > >> > >> > >> Thanks. The EIGRP Convergence is slow. Before it was fast but now it's > >> slow. Although we have tunnel2 for those routes. Here are the > >> configuration for Tunnel > >> > >> The bandwidth of the ISP is 12mb and tunnel bandwidth is configured for > >> 2000. > >> > >> Current configuration : 562 bytes > >> ! > >> interface Tunnel1 > >> description Primary TW1 Data Tunnel > >> bandwidth 2000 > >> ip address 172.18.1.25 255.255.255.0 > >> no ip redirects > >> ip mtu 1400 > >> ip nhrp authentication AUTH@1 > >> ip nhrp map multicast 200.40.170.200 > >> ip nhrp map 172.18.1.2 200.40.170.200 > >> ip nhrp map 172.18.1.1 200.19.169.200 > >> ip nhrp map multicast 200.19.169.200 > >> ip nhrp network-id 63 > >> ip nhrp nhs 172.18.1.1 > >> ip nhrp nhs 172.18.1.2 > >> ip tcp adjust-mss 1360 > >> delay 500 > >> tunnel source GigabitEthernet0/1 > >> tunnel mode gre multipoint > >> tunnel key 63 > >> tunnel protection ipsec profile CoverTunnels > >> end > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> Regards, > >> > >> Khizer Rehman > >> 0300 8113462 > >> > >> > >> > >> > >> > >>> CC: [email protected]; [email protected] > >>> From: [email protected] > >>> Subject: Re: [OSL | CCIE_RS] DMVPN EIGRP ROUTES UPDATE WITH DELAY > >>> Date: Sun, 6 Jan 2013 11:53:40 -0500 > >>> To: [email protected] > >>> > >>> I experienced a similar issue a while back. I believe the default > >>> bandwidth on the tunnel interface was 56k. Eigrp gets 50% of that for > >>> updates. So, in our case this resulted I'm extremely slow convergence. > >>> > >>> Sent from my iPad > >>> > >>> On Jan 6, 2013, at 11:24 AM, Scott Sierra <[email protected]> wrote: > >>> > >>>> Is it not updating at all or is it just not updating fast? You memtioned > >>>> both. > >>>> > >>>> -------- Original message -------- > >>>> From: Khizer Rehman <[email protected]> > >>>> Date: > >>>> To: Khizer Rehman <[email protected]> > >>>> Cc: [email protected] > >>>> Subject: [OSL | CCIE_RS] DMVPN EIGRP ROUTES UPDATE WITH DELAY > >>>> > >>>> > >>>> Hello Everyone. > >>>> > >>>> We have setup DMVPN for connectivity between HQ and Remote Offices. We > >>>> have two hub routers setup tunnel1 and tunnel2 on both routers. The > >>>> dmvpn eigrp routes was working fine but just few month ago the fail over > >>>> is not working fine. > >>>> > >>>> We have two tunnels configured on each remote site, lets say DATA > >>>> traffic route on Tunnel1 and Voice traffic route on Tunnel2, we did it > >>>> by offset-list to prefer the traffic on each tunnel. Both tunnels are > >>>> configured with different ISP and both tunnel are on different router. > >>>> Like we have two routers A and B. On A we have Tunnel1 and B have > >>>> Tunnel2. Both are connected with Core switch and configured EIGRP > >>>> between them. > >>>> > >>>> When we shutdown the Tunnel1 ISP. The routes Update on B rotuer for Data > >>>> but A route still show route for Data on Tunnel1. Which change the route > >>>> within 1min and 40 seconds. Which are enough for generate alerts and > >>>> application goes down. > >>>> > >>>> Router A COnfiguration > >>>> > >>>> router eigrp 700 > >>>> distribute-list LocalRangesToAdvertiseOverDMVPN out Tunnel1 > >>>> distribute-list LocalRangesToAdvertiseOverDMVPN out Tunnel2 > >>>> default-metric 1000000 100 255 1 1500 > >>>> network 172.18.1.0 0.0.0.255 > >>>> network 172.18.2.0 0.0.0.255 > >>>> network 172.25.0.0 > >>>> network 172.25.4.0 0.0.0.255 > >>>> network 172.26.0.0 > >>>> network 172.30.90.0 0.0.0.255 > >>>> network 192.168.25.0 > >>>> network 192.168.211.0 > >>>> redistribute static > >>>> offset-list MakeThesePreferableThroughVoiceTunnel out 10000 Tunnel1 > >>>> offset-list MakeThesePreferableThroughDataTunnel out 10000 Tunnel2 > >>>> > >>>> > >>>> > >>>> PLease can someone share why the route on A doesn't update fast, which > >>>> was doing good before. > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> Regards, > >>>> > >>>> Khizer Rehman > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> For more information regarding industry leading CCIE Lab training, > >>>> please visit www.ipexpert.com > >>>> > >>>> Are you a CCNP or CCIE and looking for a job? Check out > >>>> www.PlatinumPlacement.com > >>>> > >>>> http://onlinestudylist.com/mailman/listinfo/ccie_rs > >>>> _______________________________________________ > >>>> For more information regarding industry leading CCIE Lab training, > >>>> please visit www.ipexpert.com > >>>> > >>>> Are you a CCNP or CCIE and looking for a job? Check out > >>>> www.PlatinumPlacement.com > >>>> > >>>> http://onlinestudylist.com/mailman/listinfo/ccie_rs > >> > >> _______________________________________________ > >> For more information regarding industry leading CCIE Lab training, please > >> visit www.ipexpert.com > >> > >> Are you a CCNP or CCIE and looking for a job? Check out > >> www.PlatinumPlacement.com > >> > >> http://onlinestudylist.com/mailman/listinfo/ccie_rs > > > > _______________________________________________ > > For more information regarding industry leading CCIE Lab training, please > > visit www.ipexpert.com > > > > Are you a CCNP or CCIE and looking for a job? Check out > > www.PlatinumPlacement.com > > > > http://onlinestudylist.com/mailman/listinfo/ccie_rs _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com http://onlinestudylist.com/mailman/listinfo/ccie_rs
