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
‎01-18-2017 01:45 PM
If you could also provide a "show version" output.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-18-2017 01:45 PM
-> show version
Slot-1 : 800324-00-10 1xxxN-4xx5 Rev 10.0 BootROM: 2.0.1.7 IMG: 15.3.3.5
Slot-2 : 800324-00-10 xxxN-40xx4 Rev 10.0 BootROM: 2.0.1.7 IMG: 15.3.3.5
Slot-3 : 800307-00-01 xxxx-80xx2 Rev 1.0 BootROM: 1.0.5.5 IMG: 15.3.3.5
Slot-4 : 800324-00-10 xxxxxN-xx919 Rev 10.0 BootROM: 2.0.1.7 IMG: 15.3.3.5
Slot-5 : 800190-00-07 xxxxx-xx140 Rev 7.0 BootROM: 1.0.5.5 IMG: 15.3.3.5
Slot-1 : 800324-00-10 1xxxN-4xx5 Rev 10.0 BootROM: 2.0.1.7 IMG: 15.3.3.5
Slot-2 : 800324-00-10 xxxN-40xx4 Rev 10.0 BootROM: 2.0.1.7 IMG: 15.3.3.5
Slot-3 : 800307-00-01 xxxx-80xx2 Rev 1.0 BootROM: 1.0.5.5 IMG: 15.3.3.5
Slot-4 : 800324-00-10 xxxxxN-xx919 Rev 10.0 BootROM: 2.0.1.7 IMG: 15.3.3.5
Slot-5 : 800190-00-07 xxxxx-xx140 Rev 7.0 BootROM: 1.0.5.5 IMG: 15.3.3.5
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-18-2017 01:45 PM
Can I get the full "show version" output?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-18-2017 01:45 PM
version 15.3.3.5 v1533b5-patch1-2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-18-2017 01:43 PM
Mykhaylo,
Did you get a chance to review the logs from Slot-1? (during that time-stamp around 4:52)
Copy paste the output of "show debug system dump" to see if there is any process crash?
Also, check if there are any process crash files in the internal-memory? "ls internal-memory"
Did you get a chance to review the logs from Slot-1? (during that time-stamp around 4:52)
Copy paste the output of "show debug system dump" to see if there is any process crash?
Also, check if there are any process crash files in the internal-memory? "ls internal-memory"
