Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

HSRP Bad Authentication

Hi,

I'm having the following message almost continously:

%STANDBY-3-BADAUTH: Bad authentication from 103.226.1.249, remote state Init

I have double checked the config and there's no authentication configured in neither of the switches of this HSRP group. Config is the following:

SWITCH1:

interface Vlan2

ip address 31.226.1.249 255.255.255.0 secondary

ip address 200.4.163.249 255.255.255.0 secondary

ip address 103.226.1.249 255.255.255.0

ip helper-address 103.197.4.3

ip helper-address 47.193.27.3

no ip redirects

standby 2 ip 103.226.1.1

standby 2 ip 31.226.1.1 secondary

standby 2 ip 200.4.163.1 secondary

standby 2 priority 120

SWITCH 2:

interface Port-channel1.2

encapsulation dot1Q 2

ip address 31.226.1.246 255.255.255.0 secondary

ip address 200.4.163.246 255.255.255.0 secondary

ip address 103.226.1.246 255.255.255.0

ip helper-address 103.197.4.3

ip helper-address 47.193.27.3

no ip redirects

no ip directed-broadcast

standby 2 priority 130 preempt

standby 2 ip 103.226.1.1

standby 2 ip 31.226.1.1 secondary

standby 2 ip 200.4.163.1 secondary

This is the result of sh standby brief for switch 2:

Po1.2 2 130 P Active local 103.226.1.249 103.226.1.1

And this for switch 1:

Interface Grp Prio P State Active Standby Virtual IP

Vl2 2 120 Standby 103.226.1.246 local 103.226.1.1

The device which complains of this error is cisco Cat4232L3 with IOS 12.0(7)W5(15b). Despite I'm pretty sure this is a bug, I have found nothing in the Bug Toolkit...

What do you think?

Regards,

Ruben

1 REPLY
Hall of Fame Super Silver

Re: HSRP Bad Authentication

Ruben

I do not see a problem with the part of the config that you posted. And the show standby indicates that HSRP is working (at least switch 2 knows that it is active and switch 1 knows that it is standby). I do not know if the full output of show standby would show anything else useful.

If standby is working and you are getting these error messages then it does sound like a bug. If you want to investigate further, it might be helpful to run debug for HSRP and see if it indiates anything. And of course opening a case with TAC is the ultimate way to find if it is a bug.

HTH

Rick

691
Views
0
Helpful
1
Replies
CreatePlease to create content