DFE with Initialization Failure and "tRdy2Swtch" / "tDSrecv3" Errors

  • 0
  • 1
  • Article
  • Updated 5 years ago
Article ID: 11183 

Products
Matrix N-Series DFE 

Changes
A module was slot-inserted into a running system. 

Symptoms
The module attempted to initialize, then rebooted itself, with these Fault Log (5101) messages: 
"Syslog Message, <0>Rdy2swch[<slot#>.tRdy2Swtch]Initialization failed to complete(300 seconds allotted, 305 seconds elapsed). DistServ:[13], incomplete." 
"Stack Trace, Syslog Message initiated reset, Thread Name: tRdy2Swtch" 

One of the modules in the running system then rebooted itself, with these Fault Log (5101) messages: 
"Syslog Message, <1>DistServ[<slot#>.tDSrecv3]moveToReadyWait.3 client 3 not ready in 18019" 
"Stack Trace, SYSLOG message initiated reset, Thread Name: tDSrecv3" 

Cause
Rarely, a DFE System has problems synchronizing the modules, either during insertion or reboot of a module, or during a cold reboot. 

If a module fails to initialize within a certain period of time, it will reboot. Sometimes other, running modules may do the same. 

Solution/Workaround
Functions as Designed (FAD).
Contact Enterasys Networks Technical Services for further assistance, as necessary.
Photo of FAQ User

FAQ User, Official Rep

  • 13,620 Points 10k badge 2x thumb

Posted 5 years ago

  • 0
  • 1

There are no replies.

This conversation is no longer open for comments or replies.