HSRP unknown Peer

macazarpros · ‎06-09-2015

My router failed over and i havent figured out why.. they are using HSRP.. please assist... both are showing active with an unknown peer.. and the backup is being accessed when using telnet to the virtual IP..please assist.. see config several vlans are configured but i'll put the information for one.. both routers are connected to a stacked switch 3760G and the port connected to router 1 is flapping up and down. the cable is good connecting the router to the switch

Primary router

GigabitEthernet0/2.10 - Group 10
State is Active
1 state change, last state change 3d16h
Virtual IP address is 2.10.1.23
Active virtual MAC address is 0000.0c07.ac0a
Local virtual MAC address is 0000.0c07.ac0a (v1 default)
Hello time 1 sec, hold time 3 sec
Next hello sent in 0.320 secs
Authentication MD5, key-string
Preemption enabled
Active router is local
Standby router is unknown
Priority 255 (configured 255)
Group name is "hsrp-Gi0/2.10-10" (default)

secondary router

HSB_RT02#sh standby
GigabitEthernet0/2.10 - Group 10
State is Active
136 state changes, last state change 11w3d
Virtual IP address is 2.10.1.23
Active virtual MAC address is 0000.0c07.ac0a
Local virtual MAC address is 0000.0c07.ac0a (v1 default)
Hello time 1 sec, hold time 3 sec
Next hello sent in 0.736 secs
Authentication MD5, key-string
Preemption enabled
Active router is local
Standby router is unknown
Priority 254 (configured 254)
Group name is "hsrp-Gi0/2.10-10" (default)

debug on router 1

og Buffer (8192 bytes):
Grp 45 Active: h/Hello rcvd from lower pri Active router (254/172.31.255.28)
*Jun 8 23:24:03.893: HSRP: Gi0/2.450 Grp 45 Coup out 172.31.255.29 Active pri 255 vIP 172.31.255.30
*Jun 8 23:24:03.893: HSRP: Gi0/2.450 Grp 45 Hello out 172.31.255.29 Active pri 255 vIP 172.31.255.30
*Jun 8 23:24:03.901: HSRP: Gi0/2.10 Grp 10 Hello out 2.10.1.250 Active pri 255 vIP 2.10.1.23
*Jun 8 23:24:04.037: HSRP: Gi0/2.10 Grp 10 Hello in 2.10.1.251 Active pri 254 vIP 2.10.1.23
*Jun 8 23:24:04.037: HSRP: Gi0/2.10 Grp 10 Active: h/Hello rcvd from lower pri Active router (254/2.10.1.251)
*Jun 8 23:24:04.037: HSRP: Gi0/2.10 Grp 10 Coup out 2.10.1.250 Active pri 255 vIP 2.10.1.23
*Jun 8 23:24:04.037: HSRP: Gi0/2.10 Grp 10 Hello out 2.10.1.250 Active pri 255 vIP 2.10.1.23
*Jun 8 23:24:04.229: HSRP: Gi0/2.175 Grp 175 Hello in 192.168.175.251 Active pri 254 vIP 192.168.175.1
*Jun 8 23:24:04.229: HSRP: Gi0/2.175 Grp 175 Active: h/Hello rcvd from lower pri Active router (254/192.168.175.251)
*Jun 8 23:24:04.229: HSRP: Gi0/2.175 Grp 175 Coup out 192.168.175.250 Active pri 255 vIP 192.168.175.1
*Jun 8 23:24:04.229: HSRP: Gi0/2.175 Grp 175 Hello out 192.168.175.250 Active pri 255 vIP 192.168.175.1
*Jun 8 23:24:04.469: HSRP: Gi0/2.20 Grp 20 Hello in 192.168.2.251 Active pri 254 vIP 192.168.2.1
*Jun 8 23:24:04.469: HSRP: Gi0/2.20 Grp 20 Active: h/Hello rcvd from lower pri Active router (254/192.168.2.251)
*Jun 8 23:24:04.469: HSRP: Gi0/2.20 Grp 20 Coup out 192.168.2.250 Active pri 255 vIP 192.168.2.1
*Jun 8 23:24:04.469: HSRP: Gi0/2.20 Grp 20 Hello out 192.168.2.250 Active pri 255 vIP 192.168.2.1
*Jun 8 23:24:04.553: HSRP: Gi0/2.176 Grp 176 Hello out 192.168.176.250 Active pri 255 vIP 192.168.176.1
*Jun 8 23:24:04.645: HSRP: Gi0/2.176 Grp 176 Hello in 192.168.176.251 Active pri 254 vIP 192.168.176.1
*Jun 8 23:24:04.645: HSRP: Gi0/2.176 Grp 176 Active: h/Hello rcvd from lower pri Active router (254/192.168.176.251)
*Jun 8 23:24:04.645: HSRP: Gi0/2.176 Grp 176 Coup out 192.168.176.250 Active pri 255 vIP 192.168.176.1
*Jun 8 23:24:04.645: HSRP: Gi0/2.176 Grp 176 Hello out 192.168.176.250 Active pri 255 vIP 192.168.176.1

spanning tree on the switch shows both ports are fowarding

David_Che · ‎06-09-2015

Can you show the backup router log like on the primary? I suspect that unidirectional connection cause one direction packet flow okay, but not okay in the another direction. In this case, primary router can send&receive HSRP packet, but if the backup can not receive primary's HSRP hello, it would suppose the primary has been down, so it will act as the active.

if UDLD has been configured, which can avoid such issue.

macazarpros · ‎06-10-2015

yes david.. the primary router appears to be bad.. visual inspection shows all the router ports blinking even if no cable is plugged in

InayathUlla Sharieff · ‎06-10-2015

Agree with David, When HSRP Hello's are missed between the 2 devices you will end up in Active Active scenario.

You are now in ACtive/ACtive scenario. Were there is no communication between the switches.

1- Can you check logging the device and pinging between each other?

2- I mean to say ping the same subnet ip address between each other?

3- Can you check the cable connected to it is working good? If possible try changing the cable and ports.

4- Check the CPU on the box.

HTH

Regards

Inayath

macazarpros · ‎06-10-2015

thanks for you response.. the cable is good.. but cant ping the primary... upon closer inspection all the ports on the router a blinking even if no cable is connected... so it appears the router itself is bad... i got the commands pasted above from the console....

InayathUlla Sharieff · ‎06-10-2015

Next Actoin:-

What device is this?

If this is modular Switch then try to re-seat the card and check?

If non-modular Switch try rebooting it once and check the LED.

Once the LED are stable (Mean its on off the port which has the link) then

Try to change the cable and port and update us the result.

Regards

Inayath

macazarpros · ‎06-10-2015

Cisco IOS Software, C2900 Software (C2900-UNIVERSALK9-M), Version 15.0(1)M4,

http://images10.newegg.com/ProductImage/A1K0_1_2014120394233814.j

macazarpros · ‎06-11-2015

replaced the router.. got the got the config via usb.. since the ports dont work... man i didnt now these usb ports work

Charles Hill · ‎06-10-2015

What is the router model and IOS?

May not be relative, but throwing it out there just in case.

Bug CSCeb36935 references a router port flapping, which results in active active state.

ine protocol between 7200 and switch is flapping so both router are in active state.

Workaround:

Workaround
---------------
* Ensure that there are no packet storms on the network (IPX is prone to do this).

* Changing the duplex setting of the switch. Try setting it to "auto".

* Configure "set spantree portfast enable" on the switch ports

Hope this helps,

Please rate helpful posts.

Thanks.