STP topology change

[Praveen AR]

Hi all,

I got below error  form HP network node manager

Duplicate Correlation for STPTopologyChange: STP Topology Change.

Do anyone have idea  what error this related to?

Thanks in advance

[InayathUlla Sharieff]

Praveen,

Meaning of this message is that it was more likely caused by the link flap.

Anyhow to confirm further just login to the switch and check if there is any STP loops occuring.

HTH

Regards

Inayath

**Plz rate if this info is helpfull.

[Praveen AR]

Hi Inayath,

Below is the  only logg i can see  in switch at the time of error generated.All are ntp  logg's

checked stp loop not found anything

Mar  1 04:03:25.510: NTP Core (INFO): peer 172.21.203.243 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014)

*Mar  1 04:03:25.510: NTP Core (INFO): synchronized to 172.21.203.243, stratum 4

*Sep 10 10:26:28.360: %SYS-6-CLOCKUPDATE: System clock has been updated from 04:03:25 UAE Mon Mar 1 1993 to 10:26:28 UAE Tue Sep 10 2013, configured from NTP by 172.21.203.243.

*Sep 10 10:26:28.360: NTP Core (NOTICE): time reset 0.000000 s

*Sep 10 10:26:52.356: NTP Core (INFO): peer 172.21.203.243 event 'event_reach' (0x84) status 'unreach, conf, 2 events, event_reach' (0x8024)

*Sep 10 10:26:52.356: NTP Core (INFO): synchronized to 172.21.203.243, stratum 4

*Sep 10 10:26:52.356: NTP Core (NOTICE): Clock is synchronized.

[Praveen AR]

Hi Shaja.

Please let me know wht does this Duplicate crorrelation means and also how we can  find the  exact reason for this error

Regards

praveen

[shajakhan85]

Hi Praveen,

Not to worry more about this. This is the trap for STP topology change. Duplicate correlation occurs for multiple reasons.

[InayathUlla Sharieff]

Agree with Shaja.

Please feel free to let us know if you have any further queries else please mark this thread as answered and rate all usefull posts.

HTH

Regards

Inayath

[Praveen AR]

Hi,

There was no link flap on ay of the port's int he switch , What can be the other reason's.

Regards,

Praveen

[n_schloemer · Accepted solution]

Hi Praveen,

It sounds like a TCN BPDU was generated and was received multiple times by the same switch.  If you state there have not been any logged link flaps the TCN could have been generated by a switch reboot, new switch being powered on which started sending TCN's or Superior BPDUs which caused the STP infrastructure to converge due to new bridge priority. 

Are you aware of where your current STP root bridge is?  Has it changed at all.  Also, are you running PVST anywhere in the infrastructure which an access port may have been disconnected by an end user causing the TCN to be produced on that access vlan?

Have you had any of these infrastructure events?  Could a user have plugged in a smaller 4-port switch or anything like it?

This can also be produced by failing fiber if UDLD is not configured correctly to catch the symetrical traffic.

Thanks.