Since a reload "solved" the problem it's hard to troubleshoot now and this is probably not the problem but last week I got a call from a customer whose core was down and they were seeing the same message on their 6500. What I did was connected to the MSFC that was configured with the duplicate address and changed it to an address in the same subnet that we knew was not in use. I then tried connecting to the duplicate address that was in the error log and sure enough another router had the same address.
Dave Casey Fahey wrote: > > Hard to say without looking at your configs, but I would guess that you > might have some inconsistant HSRP configs on VLAN 25. > > I suggest that you 'sh vlan 25' on your switches to make sure that you are > aware of all VLAN 25 ports and then post the interface configs (especially > HSRP configs) for all router interfaces on VLAN 25. > > It seems to me that your problem is most likely network layer, so you will > likely find the problem on a router or MSM/MFSC. > > HTH, > > Casey > > ""Han Chuan Alex Ang"" wrote in message > news:200210290422.EAA04769@;groupstudy.com... > > hi, I have been having this problems recently, Wonder if anyone could > > > > help me out on this one > > > > I am running a Collapsed Core Model with two Catalyst 6000 running on > > > > HSRP for redundancy , all link connect to the Access switches are > > > > Catalyst 3500 series with redundancy link and PVST Plus implemented > > > > (The two Catalyst 6000 are defined as primary and secondary Root for > > > > all vlan except for VLAN 25. > > > > However, one direct link from the Core Bridge's port is connected > > > > without redundancy link)VLAN25 to 7206 Router interface(Root Bridge). > > > > Recently , the Router interface seem to be faulty and the whole > > > > network was town (affecting other Vlan) my understanding is that it > > > > should not affect other VLAN. > > > > Error message as follow was given > > > > Oct 12 13:15:41: %STANDBY-3-DUPADDR: Duplicate address 10.25.0.1 > > on Vlan25, sourced by 0000.0c07.ac19 > > Oct 13 16:25:41: %STANDBY-3-DUPADDR: Duplicate address 10.25.0.1 > > on Vlan25, sourced by 0000.0c07.ac19 > > Oct 15 22:31:02: %STANDBY-3-DUPADDR: Duplicate address 10.25.0.1 > > on Vlan25, sourced by 0000.0c07.ac19 > > Oct 15 22:41:01: %STANDBY-3-DUPADDR: Duplicate address 10.25.0.1 > > on Vlan25, sourced by 0000.0c07.ac19 > > > > > > A reload on the Gigabit module was needed in order to solve the > > > > problems. I am not quite sure what could have cause this problems , > > > > anyone care to enlighten me , thank > > > > > > My guess is that the faulty interface cause a recalculation for STP as the > > Root is gone and that cause the link to be lost between the two catalyst > and > > thus resulting in a loop -- David Madland CCIE# 2016 Sr. Network Engineer Qwest Communications 612-664-3367 "You don't make the poor richer by making the rich poorer." --Winston Churchill Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=56457&t=56431 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
