04-25-2006 06:24 AM - edited 03-03-2019 02:56 AM
I have two 837s running HSRP. Both routers are connected to a 2960.
Router_1:
interface Ethernet0
ip address 192.168.0.2 255.255.255.0
no ip redirects
standby 1 ip 192.168.0.1
standby 1 timers 254 255
standby 1 priority 111
standby 1 preempt
hold-queue 100 out
Router_2:
interface Ethernet0
ip address 192.168.0.3 255.255.255.0
no ip redirects
standby 1 ip 192.168.0.1
standby 1 timers 254 255
standby 1 priority 222
standby 1 preempt
hold-queue 100 out
I have noticed the following:
A) when I ping from Router_2 to the Switch all the packets come back fine BESIDES when I the Router is receiving HSRP messages. This is causing the Router loose one packet and that is why I have modified the Standby timer to send as little as possilbe...i.e.
Router_2#ping 192.168.0.4
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.4, timeout is 2 seconds:
*Apr 4 22:49:18.774: HSRP: Et0 Grp 1 Hello out 192.168.0.3 Active pri 222 vIP 192.168.0.1
*Apr 4 22:49:19.790: HSRP: Et0 Grp 1 Hello in 192.168.0.2 Standby pri 111 vIP 192.168.0.1.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 1/1/1 ms
_______________________________________
The same happens when this message is received, but I don't quite understand what the message is about
Router_2#ping 192.168.0.4
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.4, timeout is 2 seconds:
*Apr 4 22:49:08.338: HSRP: Et0 REDIRECT adv in, Passive, active 0, passive 1, from 192.168.0.2.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 1/1/4 ms
____________________________________
in both cases I don't understand why these messages are affecting my pinging???
B) when I ping from the Switch to the virtual ip address the results are totally random...
Switch#ping 192.168.0.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Switch#ping 192.168.0.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.1, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 1/2/8 ms
Switch#ping 192.168.0.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.1, timeout is 2 seconds:
....!
Success rate is 20 percent (1/5), round-trip min/avg/max = 1/1/1 ms
Switch#ping 192.168.0.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/8 ms
Switch#ping 192.168.0.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.1, timeout is 2 seconds:
....!
Success rate is 20 percent (1/5), round-trip min/avg/max = 1/1/1 ms
Switch#ping 192.168.0.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.0.1, timeout is 2 seconds:
01:04:31: IP: s=192.168.0.4 (local), d=192.168.0.1 (Vlan1), len 100, sending
01:04:31: IP: s=192.168.0.4 (local), d=192.168.0.1 (Vlan1), len 100, sending full packet.
01:04:33: IP: s=192.168.0.4 (local), d=192.168.0.1 (Vlan1), len 100, sending
01:04:33: IP: s=192.168.0.4 (local), d=192.168.0.1 (Vlan1), len 100, sending full packet.
01:04:35: IP: s=192.168.0.4 (local), d=192.168.0.1 (Vlan1), len 100, sending
01:04:35: IP: s=192.168.0.4 (local), d=192.168.0.1 (Vlan1), len 100, sending full packet.
01:04:37: IP: s=192.168.0.4 (local), d=192.168.0.1 (Vlan1), len 100, sending
01:04:37: IP: s=192.168.0.4 (local), d=192.168.0.1 (Vlan1), len 100, sending full packet.!
Success rate is 20 percent (1/5), round-trip min/avg/max = 1/1/1 ms
01:04:39: IP: s=192.168.0.4 (local), d=192.168.0.1 (Vlan1), len 100, sending
01:04:39: IP: s=192.168.0.4 (local), d=192.168.0.1 (Vlan1), len 100, sending full packet
01:04:39: IP: s=192.168.0.1 (Vlan1), d=192.168.0.4, len 100, rcvd 1
any ideas on what is happening???
thank you
04-25-2006 08:06 AM
I think I have solved the problem....
All the way along it seemed that it was the Switch who was getting confused when trying to forward the packets due to the fact that both routers were using the same virtual MAC address...so I've added the "standby use-bia" command on one of the routers so that one of them gets the "burnt-in" MAC address...this seems to have solved all the problems even after setting the timers back to 5 15
I hope this will help someone else too... cheers
Router_2:
interface Ethernet0
ip address 192.168.0.3 255.255.255.0
no ip redirects
no cdp enable
standby use-bia
standby 1 ip 192.168.0.1
standby 1 timers 5 15
standby 1 priority 222
standby 1 preempt
hold-queue 100 out
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: