<?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 RE: Summit X450-48t suddenly reboots with Crit:Kern:Alert in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/summit-x450-48t-suddenly-reboots-with-crit-kern-alert/m-p/55595#M16082</link>
    <description>The Switch was running with 15.3.1.4 patch 1-7 for 900 days, now the Switch runs with 15.3.1.4 patch 1-19.</description>
    <pubDate>Mon, 30 Nov 2015 21:24:00 GMT</pubDate>
    <dc:creator>HarrySo</dc:creator>
    <dc:date>2015-11-30T21:24:00Z</dc:date>
    <item>
      <title>Summit X450-48t suddenly reboots with Crit:Kern:Alert</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/summit-x450-48t-suddenly-reboots-with-crit-kern-alert/m-p/55590#M16077</link>
      <description>In the last days i had a Problem with a suddenly reboot of one X450-48t Switch.&lt;BR /&gt;
&lt;BR /&gt;
Is this a Problem with the Firmware? The Switch was running about 900 days without Problems. We are using the  ExtremeXOS version 15.3.1.4 v1531b4-patch1-19.&lt;BR /&gt;
&lt;BR /&gt;
Is an Upgrade required?&lt;BR /&gt;
&lt;BR /&gt;
Thx for your Help&lt;BR /&gt;
&lt;BR /&gt;
The Log&lt;BR /&gt;
&lt;BR /&gt;
11/27/2015 13:17:37.61 &lt;I&gt; Loaded Policy: snmp number of entries 1&lt;BR /&gt;
11/27/2015 13:17:37.61 &lt;I&gt; Loading policy snmp from file /config/snmp.pol&lt;BR /&gt;
11/27/2015 13:17:36.30 &lt;EPM.SYSTEM_STABLE&gt; System is stable. Change to warm reset mode&lt;BR /&gt;
11/27/2015 13:17:26.60 &lt;I&gt; Watchdog enabled&lt;BR /&gt;
11/27/2015 13:17:12.05 &lt;I&gt; snmpMaster initialization complete&lt;BR /&gt;
11/27/2015 13:17:11.95 &lt;I&gt; DOS protect application started successfully&lt;BR /&gt;
11/27/2015 13:17:11.13 &lt;I&gt; **** tftpd started *****&lt;BR /&gt;
11/27/2015 13:17:11.12 &lt;I&gt; **** telnetd started *****&lt;BR /&gt;
11/27/2015 13:17:03.84 &lt;DM.NOTICE&gt; Node State[3] = OPERATIONAL&lt;BR /&gt;
11/27/2015 13:17:00.34 &lt;DM.NOTICE&gt; Node State[2] = STANDBY&lt;BR /&gt;
11/27/2015 13:17:00.34 &lt;I&gt; Node INIT DONE ....&lt;BR /&gt;
11/27/2015 13:16:59.05 &lt;DM.NOTICE&gt; Node State[1] = INIT&lt;BR /&gt;
11/27/2015 13:16:58.66 &lt;I&gt; Hal initialization done.&lt;BR /&gt;
11/27/2015 13:16:56.94 &lt;I&gt; Network Login framework has been initialized&lt;BR /&gt;
11/27/2015 13:16:56.67 &lt;I&gt; snmpSubagent initialization complete&lt;BR /&gt;
11/27/2015 13:16:49.75 &lt;I&gt; Starting hal initialization ....&lt;BR /&gt;
11/27/2015 13:16:45.25 &lt;I&gt; telnetd listening on port 23&lt;BR /&gt;
&lt;BR /&gt;
11/27/2015 13:16:37.75 &lt;DM.NOTICE&gt; DM started&lt;BR /&gt;
11/27/2015 13:16:37.62 &lt;NM.STRTPROC&gt; The Node Manager (NM) has started processing.&lt;BR /&gt;
11/27/2015 13:16:36.90 &lt;EPM.START&gt; EPM Started&lt;BR /&gt;
11/27/2015 13:16:35.51 &lt;EPM.WD_WARM_RESET&gt; Changing to watchdog warm reset mode&lt;BR /&gt;
11/27/2015 13:15:10.23 &lt;DM.WARNING&gt; Switch FAILED (1) Process Failure&lt;BR /&gt;
11/27/2015 13:15:10.19 &lt;EPM.ALL_SHUTDOWN&gt; Shutting down all processes&lt;BR /&gt;
11/27/2015 13:15:09.56 &lt;DM.ERROR&gt; Process snmpMaster Failed&lt;BR /&gt;
11/27/2015 13:15:09.56 &lt;DM.ERROR&gt; Process snmpMaster Failed&lt;BR /&gt;
11/27/2015 13:15:09.55 &lt;DM.ERROR&gt; Node State[4] = FAIL (Process Failure)&lt;BR /&gt;
11/27/2015 13:15:09.55 &lt;EPM.REBOOT&gt; Rebooting with reason&lt;BR /&gt;
11/27/2015 13:15:09.55 &lt;EPM.CRASH_RATE&gt; Process snmpMaster exceeded pre-configured or default crash rate&lt;BR /&gt;
11/27/2015 13:15:09.46 &lt;CM.DATABASE&gt; Configuration database locked&lt;BR /&gt;
11/27/2015 13:15:09.45 &lt;EPM.PROC_CONN_LOST&gt; Connection lost with process snmpMaster&lt;BR /&gt;
11/27/2015 13:15:06.63 &lt;KERN.ALERT&gt; 2ab79170  8f998490 lw     t9,-31600(gp)&lt;BR /&gt;
11/27/2015 13:15:06.63 &lt;KERN.ALERT&gt; 2ab7916c  8e04004c lw     a0,76(s0)&lt;BR /&gt;
11/27/2015 13:15:06.63 &lt;KERN.ALERT&gt; 2ab79168  8fbc0018 lw     gp,24(sp)&lt;BR /&gt;
11/27/2015 13:15:06.63 &lt;KERN.ALERT&gt; 2ab79164  8c440000 lw     a0,0(v0)&lt;BR /&gt;
11/27/2015 13:15:06.63 &lt;KERN.ALERT&gt; 2ab79160  0320f809 jalr   t9&lt;BR /&gt;
11/27/2015 13:15:06.63 &lt;KERN.ALERT&gt; 2ab7915c &amp;lt;8c450004&amp;gt;lw     a1,4(v0)&lt;BR /&gt;
11/27/2015 13:15:06.63 &lt;KERN.ALERT&gt; 2ab79158  8c620048 lw     v0,72(v1)&lt;BR /&gt;
11/27/2015 13:15:06.63 &lt;KERN.ALERT&gt; 2ab79154  8f99823c lw     t9,-32196(gp)&lt;BR /&gt;
11/27/2015 13:15:06.63 &lt;KERN.ALERT&gt; 2ab79150  8fa300e0 lw     v1,224(sp)&lt;BR /&gt;
11/27/2015 13:15:06.63 &lt;KERN.ALERT&gt; Code:&lt;BR /&gt;
11/27/2015 13:15:06.63 &lt;KERN.ALERT&gt;&lt;BR /&gt;
11/27/2015 13:15:06.63 &lt;KERN.ALERT&gt; Process snmpMaster pid 9557 died with signal 11&lt;BR /&gt;
11/27/2015 13:14:57.51 &lt;CM.SYS.ACTIONERR&gt; Error while loading "snmpTargetAddrEntryCLI": Source IP address does not belong to the switch&lt;BR /&gt;
11/27/2015 13:14:57.51 &lt;CM.SYS.ACTIONERR&gt; Error while loading "snmpTargetAddrEntryCLI": Source IP address does not belong to the switch&lt;BR /&gt;
11/27/2015 13:14:55.40 &lt;CM.DATABASE&gt; Configuration database unlocked&lt;BR /&gt;
11/27/2015 13:14:54.93 &lt;CM.DATABASE&gt; Configuration database locked&lt;BR /&gt;
11/27/2015 13:14:54.92 &lt;EPM.PROC_CONN_LOST&gt; Connection lost with process snmpMaster&lt;BR /&gt;
11/27/2015 13:14:51.73 &lt;KERN.ALERT&gt; 2ab79170  8f998490 lw     t9,-31600(gp)&lt;BR /&gt;
11/27/2015 13:14:51.73 &lt;KERN.ALERT&gt; 2ab7916c  8e04004c lw     a0,76(s0)&lt;BR /&gt;
11/27/2015 13:14:51.73 &lt;KERN.ALERT&gt; 2ab79168  8fbc0018 lw     gp,24(sp)&lt;BR /&gt;
11/27/2015 13:14:51.73 &lt;KERN.ALERT&gt; 2ab79164  8c440000 lw     a0,0(v0)&lt;BR /&gt;
11/27/2015 13:14:51.73 &lt;KERN.ALERT&gt; 2ab79160  0320f809 jalr   t9&lt;BR /&gt;
11/27/2015 13:14:51.73 &lt;KERN.ALERT&gt; 2ab7915c &amp;lt;8c450004&amp;gt;lw     a1,4(v0)&lt;BR /&gt;
11/27/2015 13:14:51.73 &lt;KERN.ALERT&gt; 2ab79158  8c620048 lw     v0,72(v1)&lt;BR /&gt;
11/27/2015 13:14:51.73 &lt;KERN.ALERT&gt; 2ab79154  8f99823c lw     t9,-32196(gp)&lt;BR /&gt;
11/27/2015 13:14:51.73 &lt;KERN.ALERT&gt; 2ab79150  8fa300e0 lw     v1,224(sp)&lt;BR /&gt;
11/27/2015 13:14:51.73 &lt;KERN.ALERT&gt; Code:&lt;BR /&gt;
11/27/2015 13:14:51.73 &lt;KERN.ALERT&gt;&lt;BR /&gt;
11/27/2015 13:14:51.71 &lt;KERN.ALERT&gt; Process snmpMaster pid 1655 died with signal 11&lt;BR /&gt;
&lt;BR /&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/EPM.PROC_CONN_LOST&gt;&lt;/CM.DATABASE&gt;&lt;/CM.DATABASE&gt;&lt;/CM.SYS.ACTIONERR&gt;&lt;/CM.SYS.ACTIONERR&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/KERN.ALERT&gt;&lt;/EPM.PROC_CONN_LOST&gt;&lt;/CM.DATABASE&gt;&lt;/EPM.CRASH_RATE&gt;&lt;/EPM.REBOOT&gt;&lt;/DM.ERROR&gt;&lt;/DM.ERROR&gt;&lt;/DM.ERROR&gt;&lt;/EPM.ALL_SHUTDOWN&gt;&lt;/DM.WARNING&gt;&lt;/EPM.WD_WARM_RESET&gt;&lt;/EPM.START&gt;&lt;/NM.STRTPROC&gt;&lt;/DM.NOTICE&gt;&lt;/I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/DM.NOTICE&gt;&lt;/I&gt;&lt;/DM.NOTICE&gt;&lt;/DM.NOTICE&gt;&lt;/I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/EPM.SYSTEM_STABLE&gt;&lt;/I&gt;&lt;/I&gt;</description>
      <pubDate>Mon, 30 Nov 2015 01:11:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/summit-x450-48t-suddenly-reboots-with-crit-kern-alert/m-p/55590#M16077</guid>
      <dc:creator>HarrySo</dc:creator>
      <dc:date>2015-11-30T01:11:00Z</dc:date>
    </item>
    <item>
      <title>RE: Summit X450-48t suddenly reboots with Crit:Kern:Alert</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/summit-x450-48t-suddenly-reboots-with-crit-kern-alert/m-p/55591#M16078</link>
      <description>It's clearly indicate that snmpMaster process died. You may need to look for the know bug in that software. &lt;BR /&gt;
Open TAC case, they will help you out in order to narrow down the issue.&lt;BR /&gt;</description>
      <pubDate>Mon, 30 Nov 2015 01:29:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/summit-x450-48t-suddenly-reboots-with-crit-kern-alert/m-p/55591#M16078</guid>
      <dc:creator>Sumit_Tokle</dc:creator>
      <dc:date>2015-11-30T01:29:00Z</dc:date>
    </item>
    <item>
      <title>RE: Summit X450-48t suddenly reboots with Crit:Kern:Alert</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/summit-x450-48t-suddenly-reboots-with-crit-kern-alert/m-p/55592#M16079</link>
      <description>Hi HarrySo,&lt;BR /&gt;
      Yes, Like Sumit said please open a case with GTAC along with "show tech" and core dump which is expected to be available in internal memory with extension ".gz"&lt;BR /&gt;
&lt;BR /&gt;
Thanks,Syed&lt;BR /&gt;</description>
      <pubDate>Mon, 30 Nov 2015 10:18:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/summit-x450-48t-suddenly-reboots-with-crit-kern-alert/m-p/55592#M16079</guid>
      <dc:creator>Rahmathullah__S</dc:creator>
      <dc:date>2015-11-30T10:18:00Z</dc:date>
    </item>
    <item>
      <title>RE: Summit X450-48t suddenly reboots with Crit:Kern:Alert</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/summit-x450-48t-suddenly-reboots-with-crit-kern-alert/m-p/55593#M16080</link>
      <description>thx guys! I open a case at our Distributor</description>
      <pubDate>Mon, 30 Nov 2015 13:47:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/summit-x450-48t-suddenly-reboots-with-crit-kern-alert/m-p/55593#M16080</guid>
      <dc:creator>HarrySo</dc:creator>
      <dc:date>2015-11-30T13:47:00Z</dc:date>
    </item>
    <item>
      <title>RE: Summit X450-48t suddenly reboots with Crit:Kern:Alert</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/summit-x450-48t-suddenly-reboots-with-crit-kern-alert/m-p/55594#M16081</link>
      <description>What version of code are you running? Process crashes are almost always software related. If you are running on unsupported code the recommendation is going to be upgrade to a supported version.</description>
      <pubDate>Mon, 30 Nov 2015 21:11:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/summit-x450-48t-suddenly-reboots-with-crit-kern-alert/m-p/55594#M16081</guid>
      <dc:creator>Patrick_Voss</dc:creator>
      <dc:date>2015-11-30T21:11:00Z</dc:date>
    </item>
    <item>
      <title>RE: Summit X450-48t suddenly reboots with Crit:Kern:Alert</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/summit-x450-48t-suddenly-reboots-with-crit-kern-alert/m-p/55595#M16082</link>
      <description>The Switch was running with 15.3.1.4 patch 1-7 for 900 days, now the Switch runs with 15.3.1.4 patch 1-19.</description>
      <pubDate>Mon, 30 Nov 2015 21:24:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/summit-x450-48t-suddenly-reboots-with-crit-kern-alert/m-p/55595#M16082</guid>
      <dc:creator>HarrySo</dc:creator>
      <dc:date>2015-11-30T21:24:00Z</dc:date>
    </item>
  </channel>
</rss>

