Hello,
I am trying to test my HSRP setup I configured within GNS3. I kind of talked about that in my last question but I am facing now the issue and I am not sure what I need to do. I have configured HSRP on ESW1 and ESW2. Both ESW1 and ESW2 have SVI’s and are configured with IPsla with tracking of ASA1 and 2 and vice versa. My vlans, ipsla and routing is configured as below.
ESW1
interface Vlan1 ip address 192.168.100.1 255.255.255.0 standby 0 preempt standby 1 ip 192.168.100.5 standby 1 priority 250 standby 1 preempt!interface Vlan5 ip address 10.153.0.1 255.255.255.0 standby 0 preempt standby 1 ip 10.153.0.5 standby 1 priority 250 standby 1 preempt!interface Vlan6 ip address 10.153.6.3 255.255.255.0 standby 0 preempt standby 1 ip 10.153.6.5 standby 1 priority 150!interface Vlan7 ip address 10.153.7.3 255.255.255.0 standby 0 preempt standby 1 ip 10.153.7.5 standby 1 priority 150!interface Vlan8 ip address 10.153.1.1 255.255.255.0 standby 0 preempt standby 1 ip 10.153.1.5 standby 1 priority 250 standby 1 preempt!interface Vlan9 ip address 10.153.2.1 255.255.255.0 standby 0 preempt standby 1 ip 10.153.2.5 standby 1 priority 250 standby 1 preempt!interface Vlan10 ip address 10.153.3.1 255.255.255.0 standby 0 preempt standby 1 ip 10.153.3.5 standby 1 priority 250 standby 1 preempt ip sla 2 icmp-echo 10.153.0.2 source-interface FastEthernet1/0 timeout 1000 threshold 2 frequency 3ip sla schedule 2 life forever start-time now
IPsla works fine, when I turn off the ESW1 switch, everything gets routed to ESW2 and I get a ping back from 1.1.1.1 to hosts. The problem I am having is when I go to ESW1 and I shutdown one of the vlans like vlan 9 for example. I have a host 10.153.2.15 which is on vlan 9. When I shut off vlan 9 on ESW1, it will no longer ping ISP 1.1.1.1. As you can see I have HSRP configured. When I shutdown VLAN 9, ESW2 vlan 9 comes up as ACTIVE. I have the host configured with default-gateway as the virtual IP.
Here is host 10.153.2.15 (far left) ping and traceroute (should it be 10.153.2.1? Notice the first hope is not the virtual IP.
R7#show ip routeDefault gateway is 10.153.2.5Host Gateway Last Use Total Uses InterfaceICMP redirect cache is emptyR7#R7#traR7#traceroute 1.1.1.1Type escape sequence to abort.Tracing the route to 1.1.1.1 1 10.153.2.1 12 msec 20 msec 20 msec 2 66.238.#.# 252 msec 64 msec 48 msec 3 2.2.2.2 40 msec 68 msec 76 msec
ESW3 has ipsla with tracking of 192.168.100.1 vlan 1 on ESW1. If I shut off VLAN 1, I can ping 1.1.1.1 I am assuming becouse of IPSLA, does that mean I need IP sla for each vlan? That would be very messy, can anyone provide assistance or proper config? Please see attached image on the net. map. thank you all! image.jpg
RoutersSwitches / HubsNetwork Architecture
Last Comment
Predrag Jovic
8/22/2022 - Mon
Predrag Jovic
I already told you to to implement internal routing protocol, and not to use IP SLA inside your network.
:)
You created IP SLA, but did you create tracking?
ip sla 3
icmp-echo 10.153.6.2 source-interface FastEthernet1/10
timeout 1000
threshold 2
frequency 3
ip sla schedule 3 life forever start-time now
ip route 0.0.0.0 0.0.0.0 10.153.6.2 track 3
Track 3 is not equal IP sla 3.
Missing link in quoted part command (in the case you did not implement it) # track 3 ip sla 3
Shark Attack
ASKER
I did create tracking, I just didn't post it, I forgot, when I reached out to Cisco, they recommended using IPSLA with tracking and HSRP. I asked them first If I should use EIGRP or OSPF and they said no need.
Predrag Jovic
R7#traceroute 1.1.1.1
Type escape sequence to abort.
Tracing the route to 1.1.1.1
1 *
10.153.2.3 44 msec 16 msec
2 * * *
3 * *
This looks like problem with routing on ESW2 (missing default route, or next hop is not available).
Check default route in routing table on that switch.
PS
I would go with routing in your configuration.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
Shark Attack
ASKER
If I go with routing, I would need a IGRP within the switch network right? Do I extend over to ASA's and routers?
Predrag Jovic
No, you don't need IGRP within the switch network.
I guess that you need it on ESW1, ESW2, ASA ( if ASA is not in transparent mode) and on R1 and R2. Then you would need to set tracking on R1 and R2.
Shark Attack
ASKER
Ok, I changed it all to EGRP and removed IPSLA's and hsrp off the vlans. I dropped vlan 9 and I am not getting a reply back from the host 2.15 Since ESW3 has no EIGRP configured, what routing should I have on there and should I have ipsla with tracking on ESW3? When I do a traceroute form 2.15 I am not getting a next hop, I have no default gateway on ESW3/
Unlimited question asking, solutions, articles and more.
Shark Attack
ASKER
or do I need HSRP on ESW1 and 2?
Predrag Jovic
You need HSRP on ESW1 and 2 for your VLANs.
If links between switches ESW1, 2 and 3 are L2 then sure you don't need EIGRP there.
Shark Attack
ASKER
they're trunk links
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
Predrag Jovic
L2 links.
Shark Attack
ASKER
OK so I just need eigrp on asa's and routers and hsrp on esw1, 2 along with ipsla and tracking. on esw3 I need ipsla and tracking. correct?
Predrag Jovic
Problem is I am not expert for ASA, so I am not very familiar with it's capabilities.
You can implement it in a few ways.
If ASA can do IP SLA and tracking (the way to insert default route in routing table) you don't need EIGRP on R1 and R2 since there is only one path to reach those routers. So in that case that on ASA you can insert (and pull out) default route into EIGRP with IP SLA, you don't really need EIGRP on R1 & R2, otherwise you need it there. With implementing internal routing protocol in topology the only tricky part is elegant implementation of default route into routing table. The rest is really easy.
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
I was able to resolve the issue. I think it was a GNS3 error. The new GNS3 that came up recently is awful
Predrag Jovic
Nice.
:)
Few tips that I found somewhere on internet.
When you add switching module and creating vlans, sometimes it helps to add interface vlan on every switch, for every vlan, and then ping it. It worked for me more than once, other would be find image that works stable in GNS3, I am using c7200-adventerprisek9_sna-mz.150-1.M or c3725-adventerprisek9-mz.124-15.T10.
:)
You created IP SLA, but did you create tracking? Track 3 is not equal IP sla 3.
Missing link in quoted part command (in the case you did not implement it) # track 3 ip sla 3