Hi,

I once faced this issue. I changed the standby group id (on both cores)and the issue was solved. If all your Vlan are using id 1 and a particular Vlan is giving you DUP error, just try to change the standby Id for that Vlan. It worked for me.

But what cisco says is its because of some "route leaking".

Hi Sonu,

Thanks alot for your reply..

As you can see my output i am getting the duplicate error from almost all of my VLAN configured for HSRP, i have changed the vlan 3 to the different group (Group 3) but still i am getting the error on that also. below given is the output.

.Jan 3 04:53:42.513 SA: %STANDBY-3-DUPADDR: Duplicate address 10.1.16.2 on Vlan

21, sourced by 0000.0c07.ac00

.Jan 3 04:58:39.309 SA: %STANDBY-3-DUPADDR: Duplicate address 10.28.16.2 on Vla

n28, sourced by 0000.0c07.ac00

.Jan 3 05:11:46.537 SA: %STANDBY-3-DUPADDR: Duplicate address 10.0.48.2 on Vlan

4, sourced by 0000.0c07.ac00

.Jan 3 05:15:16.585 SA: %STANDBY-3-DUPADDR: Duplicate address 10.0.32.2 on Vlan

3, sourced by 0000.0c07.ac03

.Jan 3 05:20:59.941 SA: %STANDBY-3-DUPADDR: Duplicate address 10.1.48.2 on Vlan

23, sourced by 0000.0c07.ac00

.Jan 3 05:23:25.609 SA: %STANDBY-3-DUPADDR: Duplicate address 10.0.32.2 on Vlan

3, sourced by 0000.0c07.ac03

.Jan 3 05:51:44.973 SA: %STANDBY-3-DUPADDR: Duplicate address 10.0.112.2 on Vla

n8, sourced by 000d.2822.f57f

.Jan 3 06:00:54.193 SA: %STANDBY-3-DUPADDR: Duplicate address 10.28.16.2 on Vla

n28, sourced by 0000.0c07.ac00

.Jan 3 06:22:45.377 SA: %STANDBY-3-DUPADDR: Duplicate address 10.0.128.2 on Vla

check if the standby group configured are same for other switches..

Hi Arun,

Yes both the switches are having the same HSRP Groups configured. this setup is running from last 4 Years. We did not face any problem & as well did not do any changes on the core switch.From January first 2008 we are getting this errors.

How can we check the switch if it is malfunctioning (4507)

Hi Friend,

Can you check the logs from both the switch and confirm if there are any other logs then the one you have posted? I mean any host flapping or port channel flapping etc.?

Is any thing is changed in config from the time you started observing these error messages?

Regards,

Ankur

Hi

As u mentioned this logs comes only when STP looping is there.Did u find anything form the link posted above..

Lets hear more from experts abt this....

Hello,

I ran into a similar thing and the solution came from adding UDLD config to my ports. This prevented the Spanning-Tree loops that were occuring as a result of poor cables (Mine were fiber). Do you have any UDLD config on your interfaces?

Hi,

As I mentioned I have two core switches (4507-R) Core Switch 01 is the Root for Vlan 1-6,11,21-26,28-29,40,57-59,132,137 & Core Switch 02 is the Root for vlan 7-10,134-136.

STP Type is PVST. VLAN 8 sourcing MAC is the virtual MAC for the VLANs 7-10,134-136.

I have checked for the STP Loops but could not find. There is one more problem noticed in my Access Switches, the Switch Port which is cascaded to the Switch Connected to my core Switch that port is getting Error Disable.

Regards,

Hi All,

I experienced this issue today. It happened to both my core switches [Cat6509, CatOS 8.3(4), MSFC IOS 12.2(17d)SXB6].

HSRP is configured for many VLAN segments but only VLAN 1 was affected. The issue lasted momentarily, for about half hour.

I strongly suspect occurrence of a bridging loop may have caused this issue. Checking all the connected switches, I found no sign of a bridging loop. STP converges normally and as per design for VLAN 1. Redundant links are correctly blocked.

Can anyone shed some light on the issue?

Thank you.

B.Rgds,

Lim TS

I have the same issue and it started Dec 3.

I have confirmed that the problem is not on our core switches(where the messages are logged). I have enabled bpduguard on every interface and none of them went error-disbaled. I was asked by Cisco tech to apply access list denying the hsrp packet that is causing the problem on every port of the switch.This temp fixed it but haven't found who is sending the packet. The log command on the access-list didn't log any hits but the errors stopped occuring. I started removing the access-list off the ports on port-by-port basis and did a tcpdump on the rx side on the port and found the packet coming in and still don't know from where since it is a layer 1 100 M MAN link. I have asked the carrier to troublshoot and didn't find any problem. I am still working on it and i have a tac case opened. I will let you know what i find