12-23-2014 12:29 AM - edited 03-07-2019 09:59 PM
Hi,
I have two 6509 interconnected with a trunk interface. On this interface, with other vlan, is active the vlan 120.
The vlan 120 is configured in HSRP:
6509 Primary
interface Vlan120
description "LAN 120"
ip address 192.168.120.2 255.255.255.0
ip access-group XBSCENTRAL-120-in in
ip flow ingress
standby 120 ip 192.168.120.1
standby 120 priority 90
standby 120 preempt
end
6509 Backup
interface Vlan120
description description "LAN 120"
ip address 192.168.120.3 255.255.255.0
ip access-group XBSCENTRAL-120-in in
ip flow ingress
standby 120 ip 192.168.120.1
standby 120 priority 110
standby 120 preempt
end
This is the output of the "sh standby vlan 120"
6509 Primary
core1-pr#sh standby vlan 120
Vlan120 - Group 120
State is Active
8 state changes, last state change 00:36:40
Virtual IP address is 192.168.120.1
Active virtual MAC address is 0000.0c07.ac78
Local virtual MAC address is 0000.0c07.ac78 (v1 default)
Hello time 3 sec, hold time 10 sec
Next hello sent in 0.320 secs
Preemption enabled
Active router is local
Standby router is unknown
Priority 90 (configured 90)
IP redundancy name is "hsrp-Vl120-120" (default)
6509 Backup
core1-bk#sh standby vlan 120
Vlan120 - Group 120
State is Active
11 state changes, last state change 00:23:19
Virtual IP address is 192.168.120.1
Active virtual MAC address is 0000.0c07.ac78
Local virtual MAC address is 0000.0c07.ac78 (v1 default)
Hello time 3 sec, hold time 10 sec
Next hello sent in 0.480 secs
Preemption enabled
Active router is local
Standby router is unknown
Priority 110 (configured 110)
IP redundancy name is "hsrp-Vl120-120" (default)
The vlan 120 is active on both 6509 and also the interfaces are active. I can reach without problem the phisycal interfaces of the 6509.
For examples: with extended ping command I can reach 192.168.120.3 from 192.168.120.2, and viceversa.
Other vlan configured like the vlan 120 are working without this problem.
I don't understand why the HSRP protocol in vlan 120 can'nt detect the stand-by router.....
Solved! Go to Solution.
12-23-2014 12:34 AM
Hi Fabrizio,
Can you also paste configuration of access list which you have in there.
Br.
Mohseen Patel
12-23-2014 12:42 AM
Hi Fabrizio,
Could you please show the access-list XBSCENTRAL-120-in configuration on both nodes
Thanks,
M
12-23-2014 12:34 AM
Hi Fabrizio,
Can you also paste configuration of access list which you have in there.
Br.
Mohseen Patel
12-23-2014 12:42 AM
Hi Fabrizio,
Could you please show the access-list XBSCENTRAL-120-in configuration on both nodes
Thanks,
M
12-23-2014 01:32 AM
Hi, thank you for both answers.
I resolved the issue... I don't know why in the ACL only IP traffic was open.
I added the rule: permit udp 192.168.120.0 0.0.0.255 host 224.0.0.2
and now the HSRP works very well.
Thank you.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide