<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Switch reboot after   Fatal exception: panic in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/switch-reboot-after-fatal-exception-panic/m-p/42332#M9944</link>
    <description>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.&lt;BR /&gt;
&lt;BR /&gt;
SBJ-EXT_AGREG.4 # show switch &lt;BR /&gt;
&lt;BR /&gt;
SysName:          SBJ-EXT_AGREG&lt;BR /&gt;
SysLocation:      &lt;BR /&gt;
SysContact:       &lt;A href="https://mailto:support@extremenetworks.com" target="_blank" rel="nofollow noreferrer noopener"&gt;support@extremenetworks.com&lt;/A&gt;, +1 888 257 3000&lt;BR /&gt;
System MAC:       00:04:96:99:83:24&lt;BR /&gt;
System Type:      X670G2-48x-4q&lt;BR /&gt;
&lt;BR /&gt;
SysHealth check:  Enabled (Normal)&lt;BR /&gt;
Recovery Mode:    All&lt;BR /&gt;
System Watchdog:  Enabled&lt;BR /&gt;
&lt;BR /&gt;
Current Time:     Sun Feb 11 11:55:59 2018&lt;BR /&gt;
Timezone:         [Auto DST Disabled] GMT Offset: -300 minutes, name is Lima.&lt;BR /&gt;
Boot Time:        Sun Feb 11 09:25:13 2018&lt;BR /&gt;
Boot Count:       19&lt;BR /&gt;
Next Reboot:      None scheduled&lt;BR /&gt;
System UpTime:    2 hours 30 minutes 46 seconds &lt;BR /&gt;
&lt;BR /&gt;
Current State:    OPERATIONAL             &lt;BR /&gt;
Image Selected:   primary                 &lt;BR /&gt;
Image Booted:     primary                 &lt;BR /&gt;
Primary ver:      22.3.1.4                &lt;BR /&gt;
                  patch1-4&lt;BR /&gt;
Secondary ver:    16.1.3.6    &lt;BR /&gt;
&lt;BR /&gt;
Config Selected:  primary.cfg                                          &lt;BR /&gt;
Config Booted:    primary.cfg                                          &lt;BR /&gt;
Config Automatic: NONE                     &lt;BR /&gt;
&lt;BR /&gt;
primary.cfg       Created by ExtremeXOS version 22.3.1.4&lt;BR /&gt;
                  2870004 bytes saved on Sun Feb 11 11:18:53 2018&lt;BR /&gt;
&lt;BR /&gt;
LAA MAC:          Locally Administered MAC Address Disabled&lt;BR /&gt;
&lt;BR /&gt;
SBJ-EXT_AGREG.5 # show log&lt;BR /&gt;
&lt;BR /&gt;
02/11/2018 09:25:35.32 &lt;I&gt; Starting hal initialization ....&lt;BR /&gt;
02/11/2018 09:25:34.85 &lt;NM.STRTPROC&gt; The Node Manager (NM) has started processing.&lt;BR /&gt;
02/11/2018 09:25:34.81 &lt;LOG.SERVERSTARTED&gt; The Event Management System logging server has started.&lt;BR /&gt;
02/11/2018 09:25:34.78 &lt;DM.NOTICE&gt; DM started&lt;BR /&gt;
02/11/2018 09:25:34.34 &lt;EPM.START&gt; EPM Started&lt;BR /&gt;
02/11/2018 09:25:34.33 &lt;EPM.UNEXPCTREBOOTDTECT&gt; Booting after System Failure.&lt;BR /&gt;
02/11/2018 09:25:33.15 &lt;EPM.WD_WARM_RESET&gt; Changing to watchdog warm reset mode&lt;BR /&gt;
02/11/2018 09:16:59.53 &lt;KERN.ALERT&gt; CPU 1: Kernel thread was stuck for 2.81 seconds, jiffies: 7692195870&lt;BR /&gt;
02/11/2018 09:16:59.53 &lt;KERN.EMERGENCY&gt; Fatal exception: panic in 5 seconds&lt;BR /&gt;
02/11/2018 09:16:59.53 &lt;KERN.ALERT&gt; CPU 3: Kernel thread was stuck for 2.17 seconds, jiffies: 7692195870&lt;BR /&gt;
02/11/2018 09:16:58.96 &lt;EAPS.SHAREDPORT.WARNING&gt; EAPS Shared-port 5 - Neighbor unreachable&lt;BR /&gt;
02/11/2018 09:16:56.94 &lt;KERN.ALERT&gt; CPU 1 Unable to handle kernel paging request at virtual address 0000000500000006, epc == ffffffff80342824, ra == ffffffff8052a724&lt;BR /&gt;
&lt;BR /&gt;
Thanks ind advanced for your help.&lt;/KERN.ALERT&gt;&lt;/EAPS.SHAREDPORT.WARNING&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.EMERGENCY&gt;&lt;/KERN.ALERT&gt;&lt;/EPM.WD_WARM_RESET&gt;&lt;/EPM.UNEXPCTREBOOTDTECT&gt;&lt;/EPM.START&gt;&lt;/DM.NOTICE&gt;&lt;/LOG.SERVERSTARTED&gt;&lt;/NM.STRTPROC&gt;&lt;/I&gt;</description>
    <pubDate>Sun, 11 Feb 2018 23:52:00 GMT</pubDate>
    <dc:creator>earroyo</dc:creator>
    <dc:date>2018-02-11T23:52:00Z</dc:date>
    <item>
      <title>Switch reboot after   Fatal exception: panic</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/switch-reboot-after-fatal-exception-panic/m-p/42332#M9944</link>
      <description>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.&lt;BR /&gt;
&lt;BR /&gt;
SBJ-EXT_AGREG.4 # show switch &lt;BR /&gt;
&lt;BR /&gt;
SysName:          SBJ-EXT_AGREG&lt;BR /&gt;
SysLocation:      &lt;BR /&gt;
SysContact:       &lt;A href="https://mailto:support@extremenetworks.com" target="_blank" rel="nofollow noreferrer noopener"&gt;support@extremenetworks.com&lt;/A&gt;, +1 888 257 3000&lt;BR /&gt;
System MAC:       00:04:96:99:83:24&lt;BR /&gt;
System Type:      X670G2-48x-4q&lt;BR /&gt;
&lt;BR /&gt;
SysHealth check:  Enabled (Normal)&lt;BR /&gt;
Recovery Mode:    All&lt;BR /&gt;
System Watchdog:  Enabled&lt;BR /&gt;
&lt;BR /&gt;
Current Time:     Sun Feb 11 11:55:59 2018&lt;BR /&gt;
Timezone:         [Auto DST Disabled] GMT Offset: -300 minutes, name is Lima.&lt;BR /&gt;
Boot Time:        Sun Feb 11 09:25:13 2018&lt;BR /&gt;
Boot Count:       19&lt;BR /&gt;
Next Reboot:      None scheduled&lt;BR /&gt;
System UpTime:    2 hours 30 minutes 46 seconds &lt;BR /&gt;
&lt;BR /&gt;
Current State:    OPERATIONAL             &lt;BR /&gt;
Image Selected:   primary                 &lt;BR /&gt;
Image Booted:     primary                 &lt;BR /&gt;
Primary ver:      22.3.1.4                &lt;BR /&gt;
                  patch1-4&lt;BR /&gt;
Secondary ver:    16.1.3.6    &lt;BR /&gt;
&lt;BR /&gt;
Config Selected:  primary.cfg                                          &lt;BR /&gt;
Config Booted:    primary.cfg                                          &lt;BR /&gt;
Config Automatic: NONE                     &lt;BR /&gt;
&lt;BR /&gt;
primary.cfg       Created by ExtremeXOS version 22.3.1.4&lt;BR /&gt;
                  2870004 bytes saved on Sun Feb 11 11:18:53 2018&lt;BR /&gt;
&lt;BR /&gt;
LAA MAC:          Locally Administered MAC Address Disabled&lt;BR /&gt;
&lt;BR /&gt;
SBJ-EXT_AGREG.5 # show log&lt;BR /&gt;
&lt;BR /&gt;
02/11/2018 09:25:35.32 &lt;I&gt; Starting hal initialization ....&lt;BR /&gt;
02/11/2018 09:25:34.85 &lt;NM.STRTPROC&gt; The Node Manager (NM) has started processing.&lt;BR /&gt;
02/11/2018 09:25:34.81 &lt;LOG.SERVERSTARTED&gt; The Event Management System logging server has started.&lt;BR /&gt;
02/11/2018 09:25:34.78 &lt;DM.NOTICE&gt; DM started&lt;BR /&gt;
02/11/2018 09:25:34.34 &lt;EPM.START&gt; EPM Started&lt;BR /&gt;
02/11/2018 09:25:34.33 &lt;EPM.UNEXPCTREBOOTDTECT&gt; Booting after System Failure.&lt;BR /&gt;
02/11/2018 09:25:33.15 &lt;EPM.WD_WARM_RESET&gt; Changing to watchdog warm reset mode&lt;BR /&gt;
02/11/2018 09:16:59.53 &lt;KERN.ALERT&gt; CPU 1: Kernel thread was stuck for 2.81 seconds, jiffies: 7692195870&lt;BR /&gt;
02/11/2018 09:16:59.53 &lt;KERN.EMERGENCY&gt; Fatal exception: panic in 5 seconds&lt;BR /&gt;
02/11/2018 09:16:59.53 &lt;KERN.ALERT&gt; CPU 3: Kernel thread was stuck for 2.17 seconds, jiffies: 7692195870&lt;BR /&gt;
02/11/2018 09:16:58.96 &lt;EAPS.SHAREDPORT.WARNING&gt; EAPS Shared-port 5 - Neighbor unreachable&lt;BR /&gt;
02/11/2018 09:16:56.94 &lt;KERN.ALERT&gt; CPU 1 Unable to handle kernel paging request at virtual address 0000000500000006, epc == ffffffff80342824, ra == ffffffff8052a724&lt;BR /&gt;
&lt;BR /&gt;
Thanks ind advanced for your help.&lt;/KERN.ALERT&gt;&lt;/EAPS.SHAREDPORT.WARNING&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.EMERGENCY&gt;&lt;/KERN.ALERT&gt;&lt;/EPM.WD_WARM_RESET&gt;&lt;/EPM.UNEXPCTREBOOTDTECT&gt;&lt;/EPM.START&gt;&lt;/DM.NOTICE&gt;&lt;/LOG.SERVERSTARTED&gt;&lt;/NM.STRTPROC&gt;&lt;/I&gt;</description>
      <pubDate>Sun, 11 Feb 2018 23:52:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/switch-reboot-after-fatal-exception-panic/m-p/42332#M9944</guid>
      <dc:creator>earroyo</dc:creator>
      <dc:date>2018-02-11T23:52:00Z</dc:date>
    </item>
    <item>
      <title>RE: Switch reboot after   Fatal exception: panic</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/switch-reboot-after-fatal-exception-panic/m-p/42333#M9945</link>
      <description>I would suggest you open a ticket with the GTAC: &lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-contact-Extreme-Networks-Global-Technical-Assistance-Center-GTAC" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-contact-Extreme-Networks-Global-Tec...&lt;/A&gt;</description>
      <pubDate>Wed, 14 Feb 2018 00:01:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/switch-reboot-after-fatal-exception-panic/m-p/42333#M9945</guid>
      <dc:creator>Doug</dc:creator>
      <dc:date>2018-02-14T00:01:00Z</dc:date>
    </item>
    <item>
      <title>RE: Switch reboot after   Fatal exception: panic</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/switch-reboot-after-fatal-exception-panic/m-p/42334#M9946</link>
      <description>Hi Doug, We dont have free support anymore in thaqt switch, So i would appreciate if you or somebody can help me here,</description>
      <pubDate>Wed, 14 Feb 2018 00:01:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/switch-reboot-after-fatal-exception-panic/m-p/42334#M9946</guid>
      <dc:creator>earroyo</dc:creator>
      <dc:date>2018-02-14T00:01:00Z</dc:date>
    </item>
  </channel>
</rss>

