HELP! Stack unexpected reboot
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-18-2017 01:34 PM
XOS: ExtremeXOS version 15.3.3.5 v1533b5-patch1-2
One of our extreme x460/x450 stacks rebooted unexpectedly this morning (at 04:52 ) Logs suggests the following:
2017-01-18 04:57:14.33 Stacking port 1:1 link up at 10Gbps.
2017-01-18 04:57:13.99 Starting hal initialization ....
2017-01-18 04:57:12.29 telnetd listening on port 23
2017-01-18 04:57:06.18 The stack MAC address is not correctly configured on this node. The stack can not operate properly in this condition. Please correct and reboot.
2017-01-18 04:57:03.16 DM started
2017-01-18 04:57:02.95 The Node Manager (NM) has started processing.
2017-01-18 04:57:02.15 EPM Started
2017-01-18 04:57:01.83 Changing to watchdog warm reset mode
2017-01-18 04:52:20.87 Slot-1 FAILED (1) Backup lost
2017-01-18 04:52:20.83 Shutting down all processes
2017-01-18 04:52:20.53 Node State[4] = FAIL (Backup lost)
2017-01-18 04:52:20.53 MASTER decided that I am not BACKUP anymore
2017-01-18 04:52:20.53 BACKUP NODE (Slot-1) DOWN
has anyone had a similar problem?
Thx,
Mykhaylo
One of our extreme x460/x450 stacks rebooted unexpectedly this morning (at 04:52 ) Logs suggests the following:
2017-01-18 04:57:14.33 Stacking port 1:1 link up at 10Gbps.
2017-01-18 04:57:13.99 Starting hal initialization ....
2017-01-18 04:57:12.29 telnetd listening on port 23
2017-01-18 04:57:06.18
2017-01-18 04:57:03.16
2017-01-18 04:57:02.95
2017-01-18 04:57:02.15
2017-01-18 04:57:01.83
2017-01-18 04:52:20.87
2017-01-18 04:52:20.83
2017-01-18 04:52:20.53
2017-01-18 04:52:20.53
2017-01-18 04:52:20.53
has anyone had a similar problem?
Thx,
Mykhaylo
27 REPLIES 27
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-13-2017 06:56 PM
Sukwinder Gill, if the stack is still in a master / standby configuration and daisy chain. The assumption is that there is only 1 stack cable connecting the nodes. This means if standby looses connection to its master for any reason (in this case disconnecting the stack cable) it will reboot because it is not master capable and relies on communication to a master.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-08-2017 09:26 AM
the stack config is Master/Standby:
* Slot-1 Stack.9 # sh stackingStack Topology is a Daisy-Chain
Active Topology is a Daisy-Chain
Node MAC Address Slot Stack State Role Flags
------------------ ---- ----------- ------- ---
*00:04:96:9b:ba:06 1 Active Master CA-
00:04:96:9b:ba:24 2 Active Standby CA-
Please advice
* Slot-1 Stack.9 # sh stackingStack Topology is a Daisy-Chain
Active Topology is a Daisy-Chain
Node MAC Address Slot Stack State Role Flags
------------------ ---- ----------- ------- ---
*00:04:96:9b:ba:06 1 Active Master CA-
00:04:96:9b:ba:24 2 Active Standby CA-
Please advice
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-08-2017 09:22 AM
is it having any conduit error , than it means it lost communication with master and assumes as a single node in stack and am suspecting its a dual master situation in stack,.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-08-2017 08:22 AM
I also have a problem with an unexpected reboot.
X440-G2-24t. 21.1.1.4 Patch 1-5.
All works but then backup switch reboots when one of the stack cables are disconnected.
X440-G2-24t. 21.1.1.4 Patch 1-5.
All works but then backup switch reboots when one of the stack cables are disconnected.
