Switch Crash
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-06-2022 11:46 AM
I've had one member of a two member virtual chassis crash/reboot. A few logs:
<Noti:DM.Notice> Slot-1: Slot-2 being Rebooted
<Noti:DM.Notice> Slot-1: Slot-2 being Rebooted
<Info:DM.Info> Slot-1: nodemgr setting Slot-2 state to REBOOTING (Slot is stuck in failed state.)
<Info:DM.Info> Slot-1: nodemgr setting Slot-2 state to REBOOTING (Slot is stuck in failed state.)
<Warn:DM.Warning> Slot-2: BACKUP is NOT in SYNC
There isn't a core dump per the 'show debug system-dump' command. Is there anything that I may be missing as far as getting more information on why the switch crashed?
<Noti:DM.Notice> Slot-1: Slot-2 being Rebooted
<Noti:DM.Notice> Slot-1: Slot-2 being Rebooted
<Info:DM.Info> Slot-1: nodemgr setting Slot-2 state to REBOOTING (Slot is stuck in failed state.)
<Info:DM.Info> Slot-1: nodemgr setting Slot-2 state to REBOOTING (Slot is stuck in failed state.)
<Warn:DM.Warning> Slot-2: BACKUP is NOT in SYNC
There isn't a core dump per the 'show debug system-dump' command. Is there anything that I may be missing as far as getting more information on why the switch crashed?
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎07-07-2022 08:22 AM
Hi B,
From slot 1 you can telnet to slot 2("telnet slot 2") to see if there are any relevant logs local to Slot-2.
Thanks,
Chris Thompson
From slot 1 you can telnet to slot 2("telnet slot 2") to see if there are any relevant logs local to Slot-2.
Thanks,
Chris Thompson
