Switch reboot after Fatal exception: panic

  • 0
  • 1
  • Problem
  • Updated 3 months ago
  • Not a Problem
  • (Edited)
Hi, We have an unexpected reboot in our switch Extreme Networks X670G2, these are the show switch and show logs, the switch before the reboot has the firmware 16.1.3.6.

SBJ-EXT_AGREG.4 # show switch 

SysName:          SBJ-EXT_AGREG
SysLocation:      
SysContact:       support@extremenetworks.com, +1 888 257 3000
System MAC:       00:04:96:99:83:24
System Type:      X670G2-48x-4q

SysHealth check:  Enabled (Normal)
Recovery Mode:    All
System Watchdog:  Enabled

Current Time:     Sun Feb 11 11:55:59 2018
Timezone:         [Auto DST Disabled] GMT Offset: -300 minutes, name is Lima.
Boot Time:        Sun Feb 11 09:25:13 2018
Boot Count:       19
Next Reboot:      None scheduled
System UpTime:    2 hours 30 minutes 46 seconds 

Current State:    OPERATIONAL             
Image Selected:   primary                 
Image Booted:     primary                 
Primary ver:      22.3.1.4                
                  patch1-4
Secondary ver:    16.1.3.6    

Config Selected:  primary.cfg                                          
Config Booted:    primary.cfg                                          
Config Automatic: NONE                     

primary.cfg       Created by ExtremeXOS version 22.3.1.4
                  2870004 bytes saved on Sun Feb 11 11:18:53 2018

LAA MAC:          Locally Administered MAC Address Disabled


SBJ-EXT_AGREG.5 # show log

02/11/2018 09:25:35.32 <Info:HAL.Sys.Info> Starting hal initialization ....
02/11/2018 09:25:34.85 <Noti:NM.StrtProc> The Node Manager (NM) has started processing.
02/11/2018 09:25:34.81 <Noti:log.serverStarted> The Event Management System logging server has started.
02/11/2018 09:25:34.78 <Noti:DM.Notice> DM started
02/11/2018 09:25:34.34 <Noti:EPM.start> EPM Started
02/11/2018 09:25:34.33 <Warn:EPM.UnexpctRebootDtect> Booting after System Failure.
02/11/2018 09:25:33.15 <Noti:EPM.wd_warm_reset> Changing to watchdog warm reset mode
02/11/2018 09:16:59.53 <Crit:Kern.Alert> CPU 1: Kernel thread was stuck for 2.81 seconds, jiffies: 7692195870
02/11/2018 09:16:59.53 <Crit:Kern.Emergency> Fatal exception: panic in 5 seconds
02/11/2018 09:16:59.53 <Crit:Kern.Alert> CPU 3: Kernel thread was stuck for 2.17 seconds, jiffies: 7692195870
02/11/2018 09:16:58.96 <Warn:EAPS.SharedPort.Warning> EAPS Shared-port 5 - Neighbor unreachable
02/11/2018 09:16:56.94 <Crit:Kern.Alert> CPU 1 Unable to handle kernel paging request at virtual address 0000000500000006, epc == ffffffff80342824, ra == ffffffff8052a724

Thanks ind advanced for your help.
Photo of earroyo

earroyo

  • 120 Points 100 badge 2x thumb

Posted 3 months ago

  • 0
  • 1
Photo of Doug Hyde

Doug Hyde, Technical Support Manager

  • 20,054 Points 20k badge 2x thumb
Photo of earroyo

earroyo

  • 120 Points 100 badge 2x thumb
Hi Doug, We dont have free support anymore in thaqt switch, So i would appreciate if you or somebody can help me here,