<?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: X460G2 (Stack) - stack node crash in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/x460g2-stack-stack-node-crash/m-p/47627#M12295</link>
    <description>The GTAC support has answered the following:&lt;BR /&gt;
&lt;BR /&gt;
&lt;I&gt;&lt;BR /&gt;
Hello,&lt;BR /&gt;
&lt;BR /&gt;
My name is Christopher and this case has just been escalated to me.&lt;BR /&gt;
&lt;BR /&gt;
From the show tech information I can see that there was a process crash of process epm on slot 1 on the 7th of September at 19:24:02&lt;BR /&gt;
What I also can see are additional memory depletion messages due to process climaster following this process crash at 19:27:16, 19:27:22, and 19:27:29.&lt;BR /&gt;
&lt;BR /&gt;
I can see that you are having webhttp enabled, can you tell me, are you using the web-interface of this switch?&lt;BR /&gt;
&lt;BR /&gt;
Taken your comment that at this point you were running EXOS 15.7.1. there is a known issue (xos0062016) in this version of code that cause reboots due to memory depletion of process CliMaster, so (with having the web-interface enabled) I'm quite certain that this is the cause of your reboot. Process EPM is responsible for handling all the running processes, and I'm quite certain that it crashed due to not having sufficient memory left due to the known issue. This would explain the memory depletions showing up right after the process crash.&lt;BR /&gt;
&lt;BR /&gt;
xos0062016 has been fixed in EXOS 15.7.2, so coincidentally the version that you have already upgraded to.&lt;BR /&gt;
&lt;BR /&gt;
kind regards,&lt;BR /&gt;
&lt;BR /&gt;
Christopher Henrich&lt;BR /&gt;
EMEA TAC Sr. Escalation Support Engineer / Extreme Networks&lt;/I&gt;</description>
    <pubDate>Fri, 18 Sep 2015 12:50:00 GMT</pubDate>
    <dc:creator>Admin_ZML</dc:creator>
    <dc:date>2015-09-18T12:50:00Z</dc:date>
    <item>
      <title>X460G2 (Stack) - stack node crash</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/x460g2-stack-stack-node-crash/m-p/47624#M12292</link>
      <description>Today we had an crash of 1 node in a 2 node X460G2-48p-10G4 stacking configuration. things began to become unresponsive. After checking the chalet gui and checking true serial port i saw node 1 unresponsive.&lt;BR /&gt;
&lt;BR /&gt;
The error was with extremexos 15.7.1.4 and now i have already have installed 15.7.2.9&lt;BR /&gt;
&lt;BR /&gt;
Event logs:&lt;BR /&gt;
&lt;BR /&gt;
2015-09-07 19:24:04.46 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Epm application wdg timer warning - 111 sec, kepc 0xffffffff805fa5f4(__cond_resched+0x20/0x44) uepc 0x2acdb150.2015-09-07 19:24:03.48 &lt;KERN.CARD.ALERT&gt; Slot-1: 2acdb164 00000000 nop&lt;BR /&gt;
2015-09-07 19:24:03.48 &lt;KERN.CARD.ALERT&gt; Slot-1: 2acdb160 8f8393ac lw v1,-27732(gp)&lt;BR /&gt;
2015-09-07 19:24:03.48 &lt;KERN.CARD.ALERT&gt; Slot-1: 2acdb158 7c03e83b Unknown at 0x2acdb158, 0x7c03e83b, op 31&lt;BR /&gt;
2015-09-07 19:24:03.48 &lt;KERN.CARD.ALERT&gt; Slot-1: 2acdb154 00408021 addu s0,v0,zero&lt;BR /&gt;
2015-09-07 19:24:03.48 &lt;KERN.CARD.ALERT&gt; Slot-1: 2acdb150 &amp;lt;10e00008&amp;gt;beq a3,zero,0x2acdb174&lt;BR /&gt;
2015-09-07 19:24:03.48 &lt;KERN.CARD.ALERT&gt; Slot-1: 2acdb14c 0000000c syscall 0&lt;BR /&gt;
2015-09-07 19:24:03.48 &lt;KERN.CARD.ALERT&gt; Slot-1: 2acdb15c 00601021 addu v0,v1,zero&lt;BR /&gt;
2015-09-07 19:24:03.42 &lt;KERN.CARD.ALERT&gt; Slot-1: 2acdb148 24020fa7&lt;BR /&gt;
2015-09-07 19:24:03.42 &lt;KERN.CARD.ALERT&gt; Slot-1: 2acdb144 02003021 addu a2,s0,zero&lt;BR /&gt;
2015-09-07 19:24:03.42 &lt;KERN.CARD.ALERT&gt; Slot-1: Code:&lt;BR /&gt;
2015-09-07 19:24:03.42 &lt;KERN.CARD.ALERT&gt; Slot-1:&lt;BR /&gt;
2015-09-07 19:24:03.42 &lt;KERN.CARD.ALERT&gt; Slot-1: Process epm pid 1141 died with signal 6&lt;BR /&gt;
2015-09-07 19:24:03.42 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Application watchdog killing process 1141(epm) in state 1.&lt;BR /&gt;
2015-09-07 19:24:03.41 &lt;KERN.CARD.CRITICAL&gt; Slot-1: App timer for index 0 app: (epm) expired, delta 12031 timeout: 120000&lt;BR /&gt;
2015-09-07 19:23:53.70 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Epm application wdg timer warning - 111 sec, kepc 0xffffffff802dcca8(do_wait+0x2d0/0x478) uepc 0x2acdb150.&lt;BR /&gt;
2015-09-07 19:23:43.62 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Epm application wdg timer warning - 101 sec, kepc 0xffffffff802dcca8(do_wait+0x2d0/0x478) uepc 0x2acdb150.&lt;BR /&gt;
2015-09-07 19:23:33.51 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Epm application wdg timer warning - 90 sec, kepc 0xffffffff802dcca8(do_wait+0x2d0/0x478) uepc 0x2acdb150.&lt;BR /&gt;
2015-09-07 19:23:23.36 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Epm application wdg timer warning - 80 sec, kepc 0xffffffff802dcca8(do_wait+0x2d0/0x478) uepc 0x2acdb150.&lt;BR /&gt;
2015-09-07 19:23:13.56 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Epm application wdg timer warning - 70 sec, kepc 0xffffffff802dcca8(do_wait+0x2d0/0x478) uepc 0x2acdb150.&lt;BR /&gt;
2015-09-07 19:23:03.34 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Epm application wdg timer warning - 60 sec, kepc 0xffffffff802dcca8(do_wait+0x2d0/0x478) uepc 0x2acdb150.&lt;BR /&gt;
2015-09-07 19:22:53.04 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Epm application wdg timer warning - 50 sec, kepc 0xffffffff802dcca8(do_wait+0x2d0/0x478) uepc 0x2acdb150.&lt;BR /&gt;
2015-09-07 19:22:42.90 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Epm application wdg timer warning - 40 sec, kepc 0xffffffff802dcca8(do_wait+0x2d0/0x478) uepc 0x2acdb150.&lt;BR /&gt;
2015-09-07 19:22:32.83 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Epm application wdg timer warning - 30 sec, kepc 0xffffffff802dcca8(do_wait+0x2d0/0x478) uepc 0x2acdb150.&lt;BR /&gt;
2015-09-07 19:22:22.68 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Epm application wdg timer warning - 20 sec, kepc 0xffffffff802dcca8(do_wait+0x2d0/0x478) uepc 0x2acdb150.&lt;BR /&gt;
2015-09-07 19:22:02.36 &lt;EPM.CPU&gt; Slot-1: CPU utilization monitor: process epm consumes 99 % CPU&lt;BR /&gt;
2015-09-07 19:21:57.60 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Epm application wdg timer warning - 60 sec, kepc 0xffffffff805fee1c(schedule_timeout+0x64/0xe0) uepc 0x2aaec2e8.&lt;BR /&gt;
2015-09-07 19:21:47.48 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Epm application wdg timer warning - 50 sec, kepc 0xffffffff805fee1c(schedule_timeout+0x64/0xe0) uepc 0x2aaec2e8.&lt;BR /&gt;
2015-09-07 19:21:37.35 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Epm application wdg timer warning - 40 sec, kepc 0xffffffff805fee1c(schedule_timeout+0x64/0xe0) uepc 0x2aaec2e8.&lt;BR /&gt;
2015-09-07 19:21:27.22 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Epm application wdg timer warning - 30 sec, kepc 0xffffffff805fee1c(schedule_timeout+0x64/0xe0) uepc 0x2aaec2e8.&lt;BR /&gt;
2015-09-07 19:21:17.09 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Epm application wdg timer warning - 20 sec, kepc 0xffffffff805fee1c(schedule_timeout+0x64/0xe0) uepc 0x2aaec2e8.&lt;BR /&gt;
2015-09-07 19:20:53.76 &lt;EPM.MSG.HELLO_RATE&gt; Slot-1: Process mrp sends hello too often, expected once in 5 secs&lt;BR /&gt;
2015-09-07 19:20:53.76 &lt;EPM.HELLO_RATE&gt; Slot-1: Received hellos from process mrp 2 more often then expected 3&lt;BR /&gt;
2015-09-07 19:20:53.76 &lt;EPM.MSG.HELLO_RATE&gt; Slot-1: Process elsm sends hello too often, expected once in 10 secs&lt;BR /&gt;
2015-09-07 19:20:53.76 &lt;EPM.HELLO_RATE&gt; Slot-1: Received hellos from process elsm 2 more often then expected 3&lt;BR /&gt;
2015-09-07 19:20:53.76 &lt;EPM.MSG.HELLO_RATE&gt; Slot-1: Process mcmgr sends hello too often, expected once in 10 secs&lt;BR /&gt;
2015-09-07 19:20:53.76 &lt;EPM.HELLO_RATE&gt; Slot-1: Received hellos from process mcmgr 2 more often then expected 3&lt;BR /&gt;
2015-09-07 19:20:47.92 &lt;EPM.MSG.HELLO_RATE&gt; Slot-1: Process mrp sends hello too often, expected once in 5 secs&lt;BR /&gt;
2015-09-07 19:20:47.92 &lt;EPM.HELLO_RATE&gt; Slot-1: Received hellos from process mrp 2 more often then expected 3&lt;BR /&gt;
2015-09-07 19:20:47.50 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Epm application wdg timer warning - 30 sec, kepc 0xffffffff805fee1c(schedule_timeout+0x64/0xe0) uepc 0x2aaec2e8.&lt;BR /&gt;
2015-09-07 19:20:37.34 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Epm application wdg timer warning - 20 sec, kepc 0xffffffff805fee1c(schedule_timeout+0x64/0xe0) uepc 0x2aaec2e8.&lt;BR /&gt;
2015-09-07 19:19:58.79 &lt;EPM.MSG.HELLO_RATE&gt; Slot-1: Process mrp sends hello too often, expected once in 5 secs&lt;BR /&gt;
2015-09-07 19:19:58.79 &lt;EPM.HELLO_RATE&gt; Slot-1: Received hellos from process mrp 2 more often then expected 3&lt;BR /&gt;
2015-09-07 19:19:24.23 &lt;EPM.MSG.HELLO_RATE&gt; Slot-1: Process mcmgr sends hello too often, expected once in 10 secs&lt;BR /&gt;
2015-09-07 19:19:24.23 &lt;EPM.HELLO_RATE&gt; Slot-1: Received hellos from process mcmgr 2 more often then expected 3&lt;BR /&gt;
2015-09-07 19:19:23.80 &lt;EPM.HELLO_RATE&gt; Slot-1: Received hellos from process elsm 2 more often then expected 3&lt;BR /&gt;
2015-09-07 19:19:23.80 &lt;EPM.MSG.HELLO_RATE&gt; Slot-1: Process elsm sends hello too often, expected once in 10 secs&lt;BR /&gt;
2015-09-07 19:19:08.82 &lt;EPM.HELLO_RATE&gt; Slot-1: Received hellos from process mrp 2 more often then expected 3&lt;BR /&gt;
2015-09-07 19:19:08.82 &lt;EPM.MSG.HELLO_RATE&gt; Slot-1: Process mrp sends hello too often, expected once in 5 secs&lt;BR /&gt;
2015-09-07 19:19:05.23 &lt;KERN.CARD.EMERGENCY&gt; Slot-1: Epm application wdg timer warning - 20 sec, kepc 0xffffffff802dcca8(do_wait+0x2d0/0x478) uepc 0x2acdb150.&lt;BR /&gt;
2015-09-07 19:18:31.06 &lt;EPM.HELLO_RATE&gt; Slot-1: Received hellos from process mrp 2 more often then expected 3&lt;BR /&gt;
2015-09-07 19:18:31.06 &lt;EPM.MSG.HELLO_RATE&gt; Slot-1: Process mrp sends hello too often, expected once in 5 secs&lt;BR /&gt;
2015-09-07 19:18:31.06 &lt;EPM.HELLO_RATE&gt; Slot-1: Received hellos from process mrp 2 more often then expected 3&lt;BR /&gt;
2015-09-07 19:18:31.06 &lt;EPM.MSG.HELLO_RATE&gt; Slot-1: Process elsm sends hello too often, expected once in 10 secs&lt;BR /&gt;
2015-09-07 19:18:31.06 &lt;EPM.HELLO_RATE&gt; Slot-1: Received hellos from process elsm 2 more often then expected 3&lt;BR /&gt;
2015-09-07 19:18:31.06 &lt;EPM.MSG.HELLO_RATE&gt; Slot-1: Process mcmgr sends hello too often, expected once in 10 secs&lt;BR /&gt;
2015-09-07 19:18:31.06 &lt;EPM.MSG.HELLO_RATE&gt; Slot-1: Process mrp sends hello too often, expected once in 5 secs&lt;BR /&gt;
2015-09-07 19:18:31.06 &lt;EPM.HELLO_RATE&gt; Slot-1: Received hellos from process mcmgr 2 more often then expected 3&lt;BR /&gt;&lt;/EPM.HELLO_RATE&gt;&lt;/EPM.MSG.HELLO_RATE&gt;&lt;/EPM.MSG.HELLO_RATE&gt;&lt;/EPM.HELLO_RATE&gt;&lt;/EPM.MSG.HELLO_RATE&gt;&lt;/EPM.HELLO_RATE&gt;&lt;/EPM.MSG.HELLO_RATE&gt;&lt;/EPM.HELLO_RATE&gt;&lt;/KERN.CARD.EMERGENCY&gt;&lt;/EPM.MSG.HELLO_RATE&gt;&lt;/EPM.HELLO_RATE&gt;&lt;/EPM.MSG.HELLO_RATE&gt;&lt;/EPM.HELLO_RATE&gt;&lt;/EPM.HELLO_RATE&gt;&lt;/EPM.MSG.HELLO_RATE&gt;&lt;/EPM.HELLO_RATE&gt;&lt;/EPM.MSG.HELLO_RATE&gt;&lt;/KERN.CARD.EMERGENCY&gt;&lt;/KERN.CARD.EMERGENCY&gt;&lt;/EPM.HELLO_RATE&gt;&lt;/EPM.MSG.HELLO_RATE&gt;&lt;/EPM.HELLO_RATE&gt;&lt;/EPM.MSG.HELLO_RATE&gt;&lt;/EPM.HELLO_RATE&gt;&lt;/EPM.MSG.HELLO_RATE&gt;&lt;/EPM.HELLO_RATE&gt;&lt;/EPM.MSG.HELLO_RATE&gt;&lt;/KERN.CARD.EMERGENCY&gt;&lt;/KERN.CARD.EMERGENCY&gt;&lt;/KERN.CARD.EMERGENCY&gt;&lt;/KERN.CARD.EMERGENCY&gt;&lt;/KERN.CARD.EMERGENCY&gt;&lt;/EPM.CPU&gt;&lt;/KERN.CARD.EMERGENCY&gt;&lt;/KERN.CARD.EMERGENCY&gt;&lt;/KERN.CARD.EMERGENCY&gt;&lt;/KERN.CARD.EMERGENCY&gt;&lt;/KERN.CARD.EMERGENCY&gt;&lt;/KERN.CARD.EMERGENCY&gt;&lt;/KERN.CARD.EMERGENCY&gt;&lt;/KERN.CARD.EMERGENCY&gt;&lt;/KERN.CARD.EMERGENCY&gt;&lt;/KERN.CARD.EMERGENCY&gt;&lt;/KERN.CARD.CRITICAL&gt;&lt;/KERN.CARD.EMERGENCY&gt;&lt;/KERN.CARD.ALERT&gt;&lt;/KERN.CARD.ALERT&gt;&lt;/KERN.CARD.ALERT&gt;&lt;/KERN.CARD.ALERT&gt;&lt;/KERN.CARD.ALERT&gt;&lt;/KERN.CARD.ALERT&gt;&lt;/KERN.CARD.ALERT&gt;&lt;/KERN.CARD.ALERT&gt;&lt;/KERN.CARD.ALERT&gt;&lt;/KERN.CARD.ALERT&gt;&lt;/KERN.CARD.ALERT&gt;&lt;/KERN.CARD.ALERT&gt;&lt;/KERN.CARD.EMERGENCY&gt;</description>
      <pubDate>Tue, 08 Sep 2015 00:27:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/x460g2-stack-stack-node-crash/m-p/47624#M12292</guid>
      <dc:creator>Admin_ZML</dc:creator>
      <dc:date>2015-09-08T00:27:00Z</dc:date>
    </item>
    <item>
      <title>RE: X460G2 (Stack) - stack node crash</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/x460g2-stack-stack-node-crash/m-p/47625#M12293</link>
      <description>From the looks of it you ran into a process crash. Can you paste the output for "ls" and "ls internal memory". We may be able to assist you here but ultimately a GTAC case may have to be opened to see what can be done.</description>
      <pubDate>Tue, 08 Sep 2015 17:17:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/x460g2-stack-stack-node-crash/m-p/47625#M12293</guid>
      <dc:creator>Patrick_Voss</dc:creator>
      <dc:date>2015-09-08T17:17:00Z</dc:date>
    </item>
    <item>
      <title>RE: X460G2 (Stack) - stack node crash</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/x460g2-stack-stack-node-crash/m-p/47626#M12294</link>
      <description>I have opened an GTAC case and will post the outcome if it is solved.</description>
      <pubDate>Fri, 11 Sep 2015 20:24:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/x460g2-stack-stack-node-crash/m-p/47626#M12294</guid>
      <dc:creator>Admin_ZML</dc:creator>
      <dc:date>2015-09-11T20:24:00Z</dc:date>
    </item>
    <item>
      <title>RE: X460G2 (Stack) - stack node crash</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/x460g2-stack-stack-node-crash/m-p/47627#M12295</link>
      <description>The GTAC support has answered the following:&lt;BR /&gt;
&lt;BR /&gt;
&lt;I&gt;&lt;BR /&gt;
Hello,&lt;BR /&gt;
&lt;BR /&gt;
My name is Christopher and this case has just been escalated to me.&lt;BR /&gt;
&lt;BR /&gt;
From the show tech information I can see that there was a process crash of process epm on slot 1 on the 7th of September at 19:24:02&lt;BR /&gt;
What I also can see are additional memory depletion messages due to process climaster following this process crash at 19:27:16, 19:27:22, and 19:27:29.&lt;BR /&gt;
&lt;BR /&gt;
I can see that you are having webhttp enabled, can you tell me, are you using the web-interface of this switch?&lt;BR /&gt;
&lt;BR /&gt;
Taken your comment that at this point you were running EXOS 15.7.1. there is a known issue (xos0062016) in this version of code that cause reboots due to memory depletion of process CliMaster, so (with having the web-interface enabled) I'm quite certain that this is the cause of your reboot. Process EPM is responsible for handling all the running processes, and I'm quite certain that it crashed due to not having sufficient memory left due to the known issue. This would explain the memory depletions showing up right after the process crash.&lt;BR /&gt;
&lt;BR /&gt;
xos0062016 has been fixed in EXOS 15.7.2, so coincidentally the version that you have already upgraded to.&lt;BR /&gt;
&lt;BR /&gt;
kind regards,&lt;BR /&gt;
&lt;BR /&gt;
Christopher Henrich&lt;BR /&gt;
EMEA TAC Sr. Escalation Support Engineer / Extreme Networks&lt;/I&gt;</description>
      <pubDate>Fri, 18 Sep 2015 12:50:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/x460g2-stack-stack-node-crash/m-p/47627#M12295</guid>
      <dc:creator>Admin_ZML</dc:creator>
      <dc:date>2015-09-18T12:50:00Z</dc:date>
    </item>
    <item>
      <title>RE: X460G2 (Stack) - stack node crash</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/x460g2-stack-stack-node-crash/m-p/47628#M12296</link>
      <description>Thanks for coming back to update the thread.  I've marked this post as "solved."&lt;BR /&gt;</description>
      <pubDate>Fri, 18 Sep 2015 20:42:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/x460g2-stack-stack-node-crash/m-p/47628#M12296</guid>
      <dc:creator>Drew_C</dc:creator>
      <dc:date>2015-09-18T20:42:00Z</dc:date>
    </item>
  </channel>
</rss>

