ExtremeSwitching (EXOS)

i have x440-48T Switch stacks in my Local LAN, over the last 6 months the LAN has been brought to a standstill because of a failure on a stack, both times it was a different stack. No one can connect from external the whole Network is down. We have LACP enabled on all stacks.

The error what i see is this, anfter a reboot of the stack ist is good again but i dont understand why one failed Switch will bring the whole Network to a standstill.

09/11/2017 09:07:07.74 [i] Slot-2: perfTimer Execution time of Timer Thread select (38): Min: 0.0 sec Avg: 0.868 sec Max: 1.10 sec
09/11/2017 09:07:07.74 [i] Slot-2: perfTimer Execution time of Timer Thread select (38): Last Execution: 1.10 sec
09/11/2017 09:06:45.35 [i] Slot-2: snmpMaster initialization complete
09/11/2017 09:06:44.01 [i] Slot-2: **** telnetd started *****
09/11/2017 09:06:41.60 [i] Slot-2: DOS protect application started successfully
09/11/2017 09:06:41.49 [i] Slot-2: **** tftpd started *****
09/11/2017 09:06:37.55 [i] Slot-2: snmpSubagent initialization complete
09/11/2017 09:06:37.44 [i] Slot-2: Network Login framework has been initialized
09/11/2017 09:06:34.83

Hi Steven,

Few things to consider there.

The stack seems to have detected a loop and ELRP seems to have disabled the port#1:48 in the stack.

05/15/2017 17:29:10.14

sorry i copied earlier log Messages that have nothing to do with this issue, the logs for this issue start here.

Like i said in my previous post why would this stack take all the Network down?

09/11/2017 09:06:19.52

Hi Steven,

From the above available logs, there is nothing substantial to arrive at a conclusion for the stack freeze state.

Did you have the opportunity to check the Master switch CLI over console? Does that also not respond?
What is the EXOS version in the stack?

And you have mentioned that the issue seems to resolve after a reboot, are you referring to a power cycle of the stack units or you are rebooting the stack over CLI?

Thank You,