15454 TCC2P cards resetting - any ideas?

[rayframe1]

In a CISCO 15454 ONS we recently had several resets of the TCC2P cards, more than once a day.

The alarm description said "automatic system reset" and the TCC2P cards would change protection. We have some ethernet on a ETH-100 in the shelf which sees a brief hit. The 15454 is running version 7.23. Part number 800-24766-02, HW Rev A1, Bootrom Rev 57-5444-04

Could this be power related?  Another 15454 in the same location also had a TCC2P reset, but not at the same time and only one switch

We have lots of 15454's and 15327's and see a few resets, usually never more than once a month at the same site. Some sites are worse than others. Anyone know what causes these resets?

Any advice would be appreciated

Ray Presky, CCNP

[Michael Dooley]

Ray,

Are you seeing a MEM-LOW or MEM-GONE alarm associated with the auto-reset?

Mike

[rayframe1]

No alarms and nothing in the Shelf History

Is there a way to check the Memory, is it in CTC or TL1?

Thanks for the suggestion

[rayframe1]

There were no other alarms before the restart, nothing in the Shelf History before the restarts.

midooley  - Is there a way to see the Memory usage that you are referring to?

The node that restarted is used as a gateway node for CTC. We are looking into if it was heavily used when the resets happened

Does anyone know how much CTC activity is too much?

[Michael Dooley]

Ray,

Well, there is no way to check memory usage.  The TCC will let you know when it is low with the MEM-LOW and gone (followed by an auto-reset) with MEM-GONE.  If you are not seeing either of these alarms then it is something else.

One thought was an issue where noise on the data bus from the Fan Tray would cause the TCC to auto-reset occasionally.  Take a look at FN 62545 and see if the Fan Tray you have fits the list their.  Here's a link:

http://www.cisco.com/en/US/ts/fn/620/fn62545.html

Or you can log into www.cisco.com and search for FN 62545 to find it.

Mike

[restrickland]

I think my ONS is having the same issue and I believe this field notice may help.

http://www.cisco.com/en/US/ts/fn/631/fn63148.html