topic 2 node X460-48p stack failed to connect to the collector in ExtremeSwitching (EXOS/Switch Engine)

2 node X460-48p stack failed to connect to the collector

DH1 — Tue, 11 Oct 2016 01:32:00 GMT

We had an issue this past weekend that caused our stack to reboot node 1. When I looked in the logs I saw the below a few times. What would cause the nodes to go out of sync? XOS is 15.5.4.2 patch1-5 10/08/2016 19:33:02.41 Slot-1: Booting after System Failure. 10/08/2016 19:33:02.05 Slot-1: Changing to watchdog warm reset mode 10/08/2016 19:16:46.86 Slot-1: Failed to connect to the collector 12.38.14.200:800 with SSL disabled (VLAN Mgmt does not have an IP address.) 10/08/2016 19:09:48.39 Slot-1: Failed to connect to the collector 12.38.14.200:800 with SSL disabled (VLAN Mgmt does not have an IP address.) 10/08/2016 19:07:40.66 Slot-1: BACKUP NODE (Slot-2) DOWN 10/08/2016 19:07:39.97 Slot-1: BACKUP is NOT in SYNC

RE: 2 node X460-48p stack failed to connect to the collector

Prashanth_KG — Wed, 12 Oct 2016 07:58:00 GMT

Hi,

The logs mentioned above are very generic and it would be difficult to identify the exact trigger for reboot with this limited information.

It would be good to collect the logs from the slot 2 as well to know why it rebooted.
You can collect the logs from the other nodes by telnetting to those slot numbers.

If the information available in slot 2 is not providing any leads,we may need to open a GTAC case with the show tech output from the stack.

Hope this helps!

RE: 2 node X460-48p stack failed to connect to the collector

DH1 — Wed, 12 Oct 2016 21:11:00 GMT

Thanks for the reply, here is a larger log sample from Slot 2

10/08/2016 19:34:47.10 Slot-2: Module in Slot-1 is operational
10/08/2016 19:34:41.12 Slot-2: Module in Slot-2 is operational
10/08/2016 19:34:35.89 Slot-2: Slot-1 being Powered ON
10/08/2016 19:34:31.42 Slot-2: System is stable. Change to warm reset mode
10/08/2016 19:34:19.47 Slot-2: Watchdog enabled
10/08/2016 19:33:43.50 Slot-2: Setting time to Sun Oct 9 02:53:43 2016
10/08/2016 19:33:39.38 Slot-2: Node State[3] = BACKUP
10/08/2016 19:33:24.91 Slot-2: DOS protect application started successfully
10/08/2016 19:33:23.35 Slot-2: snmpMaster process has been restarted.
10/08/2016 19:33:23.25 Slot-2: **** tftpd started *****
10/08/2016 19:33:22.62 Slot-2: Module in Slot-1 is inserted
10/08/2016 19:33:22.17 Slot-2: snmpMaster initialization complete
10/08/2016 19:33:22.04 Slot-2: Node State[2] = STANDBY
10/08/2016 19:33:22.04 Slot-2: Node INIT DONE ....
10/08/2016 19:33:21.92 Slot-2: Stacking port 1:2 link up at 10Gbps.
10/08/2016 19:33:21.92 Slot-2: Stacking port 1:1 link up at 10Gbps.
10/08/2016 19:33:20.96 Slot-2: **** telnetd started *****
10/08/2016 19:33:19.30 Slot-2: Slot-2 being Powered ON
10/08/2016 19:33:18.99 Slot-2: Node State[1] = INIT
10/08/2016 19:33:17.59 Slot-2: Hal initialization done.
10/08/2016 19:33:17.13 Slot-2: Module in Slot-2 is inserted
10/08/2016 19:33:16.94 Slot-2: Module in fan slot 8 is removed
10/08/2016 19:33:16.94 Slot-2: Module in fan slot 7 is removed
10/08/2016 19:33:16.94 Slot-2: Module in fan slot 6 is removed
10/08/2016 19:33:16.94 Slot-2: Module in fan slot 5 is removed
10/08/2016 19:33:16.94 Slot-2: Module in fan slot 4 is removed
10/08/2016 19:33:16.94 Slot-2: Module in fan slot 3 is removed
10/08/2016 19:33:16.63 Slot-2: Module in fan slot 2 is inserted
10/08/2016 19:33:16.54 Slot-2: Module in fan slot 1 is removed
10/08/2016 19:33:16.35 Slot-2: Stacking port 2:2 link up at 10Gbps.
10/08/2016 19:33:16.35 Slot-2: Stacking port 2:1 link up at 10Gbps.
10/08/2016 19:33:15.98 Slot-2: Starting hal initialization ....
10/08/2016 19:33:14.29 Slot-2: snmpSubagent initialization complete
10/08/2016 19:33:14.18 Slot-2: Network Login framework has been initialized
10/08/2016 19:33:06.78 Slot-2: telnetd listening on port 23

10/08/2016 19:32:59.65 Slot-2: DM started
10/08/2016 19:32:59.56 Slot-2: The Node Manager (NM) has started processing.
10/08/2016 19:32:58.95 Slot-2: EPM Started
10/08/2016 19:32:58.94 Slot-2: Booting after System Failure.
10/08/2016 19:32:58.58 Slot-2: Changing to watchdog warm reset mode
10/08/2016 19:13:12.49 Slot-2: Shutting down all processes
10/08/2016 19:13:12.49 Slot-2: Slot-2 FAILED (1) Not In Sync
10/08/2016 19:13:12.14 Slot-2: Node State[4] = FAIL (Not In Sync)
10/08/2016 19:13:12.14 Slot-2: NM: Old Primary's state is
10/08/2016 19:13:12.12 Slot-2: PRIMARY NODE (Slot-1) DOWN

RE: 2 node X460-48p stack failed to connect to the collector

Jeremy_Gibbs — Wed, 09 Nov 2016 06:18:00 GMT

I would go through this list:

https://gtacknowledge.extremenetworks.com/articles/Solution/Backup-node-goes-out-of-sync-with-the-ma...

Then open up a case with GTAC.