<?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: Non-stop rebooting, bad address in epc, kernel panic in ExtremeCloud IQ- Site Engine Management Center</title>
    <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20329#M1081</link>
    <description>OK &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;
&lt;BR /&gt;
Try to contact the TAC ... may be some new ideas ...&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Mon, 16 Oct 2017 12:05:00 GMT</pubDate>
    <dc:creator>Pascal_Lurquin</dc:creator>
    <dc:date>2017-10-16T12:05:00Z</dc:date>
    <item>
      <title>Non-stop rebooting, bad address in epc, kernel panic</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20313#M1065</link>
      <description>summit x350-24t, constantly rebooting.&lt;BR /&gt;
From console (manually rewrite general lines):&lt;BR /&gt;
- code: (bad address in epc);&lt;BR /&gt;
- fatal exception: panic in 5 seconds&lt;BR /&gt;
- kernel panic - not syncing: fatal exception;&lt;BR /&gt;
- reboot&lt;BR /&gt;
&lt;BR /&gt;
In Bootstrap, Test memory with command 'mt', result:&lt;BR /&gt;
-1 test itterations passed with no errors.&lt;BR /&gt;
&lt;BR /&gt;
Is switch dead? What I can do? &lt;BR /&gt;
I'm not previously debug extreme switches...</description>
      <pubDate>Mon, 02 Oct 2017 17:42:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20313#M1065</guid>
      <dc:creator>modris_bernands</dc:creator>
      <dc:date>2017-10-02T17:42:00Z</dc:date>
    </item>
    <item>
      <title>RE: Non-stop rebooting, bad address in epc, kernel panic</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20314#M1066</link>
      <description>Try to upload a new image or simply test the other image (you have two images when booting)&lt;BR /&gt;
&lt;BR /&gt;
Try to load default settings ...&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Mon, 02 Oct 2017 19:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20314#M1066</guid>
      <dc:creator>Pascal_Lurquin</dc:creator>
      <dc:date>2017-10-02T19:19:00Z</dc:date>
    </item>
    <item>
      <title>RE: Non-stop rebooting, bad address in epc, kernel panic</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20315#M1067</link>
      <description>Execute the steps mentioned by Pascal from the Bootrom. If the switch still fails then it's time to raise a case to process an RMA. For your reference : &lt;A href="https://gtacknowledge.extremenetworks.com/articles/Solution/Kernel-panic-not-syncing-Fatal-exception" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/Solution/Kernel-panic-not-syncing-Fatal-exception&lt;/A&gt;</description>
      <pubDate>Tue, 03 Oct 2017 05:23:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20315#M1067</guid>
      <dc:creator>Jacob__Praveen</dc:creator>
      <dc:date>2017-10-03T05:23:00Z</dc:date>
    </item>
    <item>
      <title>RE: Non-stop rebooting, bad address in epc, kernel panic</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20316#M1068</link>
      <description>In BootStrap I try:&lt;BR /&gt;
BootStrap&amp;gt; boot 1  Unknown Image Selection 1  usage: boot [loader option]and &lt;BR /&gt;
BootStrap&amp;gt; boot 2  Unknown Image Selection 2  usage: boot [loader option]Is possible that image has different name (not 1 or 2) or it's just count number for images?&lt;BR /&gt;
&lt;BR /&gt;
I also try boot default configuration:&lt;BR /&gt;
BootStrap&amp;gt; config none&lt;BR /&gt;
config: Command not found. Try 'h' for help!Possible, my switch version is too old and not compatible with these commands. Bellow are notes from last upgrade processes in 2016.&lt;BR /&gt;
* switch4.6 # show switch&lt;BR /&gt;
System Type:      X350-24t&lt;BR /&gt;
Primary ver:      12.6.2.10&lt;BR /&gt;
Secondary ver:    12.4.2.17&lt;BR /&gt;
Config Booted:    primary.cfg&lt;BR /&gt;
primary.cfg       Created by ExtremeXOS version 12.4.2.17&lt;BR /&gt;
                  126949 bytes saved on Mon Feb 29 23:57:39 2016And in this situation my next step is  to try "Use the BootROM Menu to Download and Install a New Image", correct?&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 03 Oct 2017 13:00:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20316#M1068</guid>
      <dc:creator>modris_bernands</dc:creator>
      <dc:date>2017-10-03T13:00:00Z</dc:date>
    </item>
    <item>
      <title>RE: Non-stop rebooting, bad address in epc, kernel panic</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20317#M1069</link>
      <description>Type "h" to get help and commands available in the bootstrap</description>
      <pubDate>Tue, 03 Oct 2017 13:07:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20317#M1069</guid>
      <dc:creator>Pascal_Lurquin</dc:creator>
      <dc:date>2017-10-03T13:07:00Z</dc:date>
    </item>
    <item>
      <title>RE: Non-stop rebooting, bad address in epc, kernel panic</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20318#M1070</link>
      <description>Be aware : You have two boot : bootstrap AND bootrom !&lt;BR /&gt;
&lt;BR /&gt;
You have to wait the POST message before using the space bar to enter in the bootroom&lt;BR /&gt;
&lt;BR /&gt;
Try both ... and type "h" or help to get commands&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 03 Oct 2017 13:11:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20318#M1070</guid>
      <dc:creator>Pascal_Lurquin</dc:creator>
      <dc:date>2017-10-03T13:11:00Z</dc:date>
    </item>
    <item>
      <title>RE: Non-stop rebooting, bad address in epc, kernel panic</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20319#M1071</link>
      <description>Thank You for note about bootrsap AND bootrom. That is what I need...&lt;BR /&gt;
In Bootrom &amp;gt; "Boot 1" and "Boot 2" fail with previous Kernel panic.&lt;BR /&gt;
&lt;BR /&gt;
Now I try download and install new/other image.</description>
      <pubDate>Tue, 03 Oct 2017 13:11:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20319#M1071</guid>
      <dc:creator>modris_bernands</dc:creator>
      <dc:date>2017-10-03T13:11:00Z</dc:date>
    </item>
    <item>
      <title>RE: Non-stop rebooting, bad address in epc, kernel panic</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20320#M1072</link>
      <description>Now I try download/install new image on Summit x350-24t by following &lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-Use-the-Boot-Rom-Menu-to-Download-and-Install-a-New-Image-to-the-Switch" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-Use-the-Boot-Rom-Menu-to-Download-a...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
AFTER&lt;BR /&gt;
BootRom&amp;gt; configip ipaddress 192.168.1.155/255.255.255.0 gateway 192.168.1.3&lt;BR /&gt;
NOTICE: No network interface available, rc=-1&lt;BR /&gt;
ioctl (SIOCAIFADDR:) File exists  BootRom&amp;gt;&lt;BR /&gt;
And now Q: What physical port I need to use for download image (connect to tftp)?&lt;BR /&gt;
&lt;BR /&gt;
All my 24 Ethernet ports are without any activity (leds is off).&lt;BR /&gt;
When I plug cable in management port (I never use it - fully newbie about it), It has activity, but from BootRom I can NOT ping GW or tftp server on this subnet.&lt;BR /&gt;
&lt;BR /&gt;
What You suggest for me to do next?</description>
      <pubDate>Thu, 05 Oct 2017 13:12:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20320#M1072</guid>
      <dc:creator>modris_bernands</dc:creator>
      <dc:date>2017-10-05T13:12:00Z</dc:date>
    </item>
    <item>
      <title>RE: Non-stop rebooting, bad address in epc, kernel panic</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20321#M1073</link>
      <description>Try 192.168.1.155/24 and not 192.168.1.155/255.255.255.0</description>
      <pubDate>Thu, 05 Oct 2017 15:53:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20321#M1073</guid>
      <dc:creator>Pascal_Lurquin</dc:creator>
      <dc:date>2017-10-05T15:53:00Z</dc:date>
    </item>
    <item>
      <title>RE: Non-stop rebooting, bad address in epc, kernel panic</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20322#M1074</link>
      <description>informative - I try both method and both of them is working, &lt;BR /&gt;
My mistake was on cable/VLAN outside summit and it not depend from input IP/mask form....</description>
      <pubDate>Thu, 05 Oct 2017 15:53:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20322#M1074</guid>
      <dc:creator>modris_bernands</dc:creator>
      <dc:date>2017-10-05T15:53:00Z</dc:date>
    </item>
    <item>
      <title>RE: Non-stop rebooting, bad address in epc, kernel panic</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20323#M1075</link>
      <description>Management port Ethernet is used for ... management like tftp&lt;BR /&gt;
&lt;BR /&gt;
try to ping first&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 05 Oct 2017 15:55:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20323#M1075</guid>
      <dc:creator>Pascal_Lurquin</dc:creator>
      <dc:date>2017-10-05T15:55:00Z</dc:date>
    </item>
    <item>
      <title>RE: Non-stop rebooting, bad address in epc, kernel panic</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20324#M1076</link>
      <description>I successfully download image "summitX-12.6.2.10-patch1-15.xos" - file from last/only my summit upgrade.&lt;BR /&gt;
.... then standard process... installing 12.6.2.10... clearing vnram .... press ENTER to reboot...&lt;BR /&gt;
&lt;BR /&gt;
AND after restart&lt;BR /&gt;
&lt;BR /&gt;
"kernet panic" like bottom in this topic &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;BR /&gt;
&lt;BR /&gt;
Is this the end of the day for this switch?</description>
      <pubDate>Thu, 05 Oct 2017 17:16:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20324#M1076</guid>
      <dc:creator>modris_bernands</dc:creator>
      <dc:date>2017-10-05T17:16:00Z</dc:date>
    </item>
    <item>
      <title>RE: Non-stop rebooting, bad address in epc, kernel panic</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20325#M1077</link>
      <description>May be the ram in this partition is corrupted ?&lt;BR /&gt;
&lt;BR /&gt;
Try both (loader 1 or 2 - boot 1 or 2) to choose&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/Solution/Switch-boots-up-in-the-BootRom-mode-without-being-able-to-initialize-EXOS-firmware/?l=en_US&amp;amp;#38;fs=RelatedArticle" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/Solution/Switch-boots-up-in-the-BootRom-mode-with...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
cross fingers + some time to test&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 05 Oct 2017 17:58:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20325#M1077</guid>
      <dc:creator>Pascal_Lurquin</dc:creator>
      <dc:date>2017-10-05T17:58:00Z</dc:date>
    </item>
    <item>
      <title>RE: Non-stop rebooting, bad address in epc, kernel panic</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20326#M1078</link>
      <description>memory test was successful - test itterations passed with no errors.&lt;BR /&gt;
baddly, but no one of these "loader 1 or 2 - boot 1 or 2" commands unable get out of non-stop rebooting switch.&lt;BR /&gt;
&lt;BR /&gt;
For now, for me - it is dead  </description>
      <pubDate>Thu, 05 Oct 2017 17:58:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20326#M1078</guid>
      <dc:creator>modris_bernands</dc:creator>
      <dc:date>2017-10-05T17:58:00Z</dc:date>
    </item>
    <item>
      <title>RE: Non-stop rebooting, bad address in epc, kernel panic</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20327#M1079</link>
      <description>Have you tried another image ? an oldest one ?&lt;BR /&gt;
&lt;BR /&gt;
Or RMA ...&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 13 Oct 2017 18:48:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20327#M1079</guid>
      <dc:creator>Pascal_Lurquin</dc:creator>
      <dc:date>2017-10-13T18:48:00Z</dc:date>
    </item>
    <item>
      <title>RE: Non-stop rebooting, bad address in epc, kernel panic</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20328#M1080</link>
      <description>I install exactly that image (and exactly that file) who I use in last switch upgrade last year (for 3 pieces of x350-24t). And all three upgrades was successful. &lt;BR /&gt;
For my logic - try older or other image is time waste. There is some technical damage...&lt;BR /&gt;
&lt;BR /&gt;
About RMA - I dont knowing this process, but switches was purchased ~7+ years ago.&lt;BR /&gt;
Last firmware version for us was 12.6.2.10. If I understand correct, then warranty for this device is ended.&lt;BR /&gt;
&lt;BR /&gt;
AnyWay, thank You Pascal for support!&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 13 Oct 2017 18:48:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20328#M1080</guid>
      <dc:creator>modris_bernands</dc:creator>
      <dc:date>2017-10-13T18:48:00Z</dc:date>
    </item>
    <item>
      <title>RE: Non-stop rebooting, bad address in epc, kernel panic</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20329#M1081</link>
      <description>OK &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;
&lt;BR /&gt;
Try to contact the TAC ... may be some new ideas ...&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Oct 2017 12:05:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq-site-engine/non-stop-rebooting-bad-address-in-epc-kernel-panic/m-p/20329#M1081</guid>
      <dc:creator>Pascal_Lurquin</dc:creator>
      <dc:date>2017-10-16T12:05:00Z</dc:date>
    </item>
  </channel>
</rss>

