Non-stop rebooting, bad address in epc, kernel panic

  • 0
  • 2
  • Problem
  • Updated 1 year ago
  • Solved
  • (Edited)
summit x350-24t, constantly rebooting.
From console (manually rewrite general lines):
- code: (bad address in epc);
- fatal exception: panic in 5 seconds
- kernel panic - not syncing: fatal exception;
- reboot

In Bootstrap, Test memory with command 'mt', result:
-1 test itterations passed with no errors.

Is switch dead? What I can do? 
I'm not previously debug extreme switches...
Photo of modris bernands

modris bernands

  • 610 Points 500 badge 2x thumb

Posted 1 year ago

  • 0
  • 2
Photo of Pascal Lurquin

Pascal Lurquin

  • 970 Points 500 badge 2x thumb

Try to upload a new image or simply test the other image (you have two images when booting)

Try to load default settings ...

Photo of Jacob, Praveen

Jacob, Praveen, Employee

  • 1,022 Points 1k badge 2x thumb
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 : https://gtacknowledge.extremenetworks.com/articles/Solution/Kernel-panic-not-syncing-Fatal-exception 
Photo of modris bernands

modris bernands

  • 610 Points 500 badge 2x thumb
In BootStrap I try:
BootStrap> boot 1
Unknown Image Selection 1
usage: boot [loader option]
and 
BootStrap> 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?

I also try boot default configuration:
BootStrap> config none
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.
* switch4.6 # show switch
System Type:      X350-24t
Primary ver:      12.6.2.10
Secondary ver:    12.4.2.17
Config Booted:    primary.cfg
primary.cfg       Created by ExtremeXOS version 12.4.2.17
                  126949 bytes saved on Mon Feb 29 23:57:39 2016
And in this situation my next step is  to try "Use the BootROM Menu to Download and Install a New Image", correct?
Photo of Pascal Lurquin

Pascal Lurquin

  • 970 Points 500 badge 2x thumb
Type "h" to get help and commands available in the bootstrap
Photo of Pascal Lurquin

Pascal Lurquin

  • 970 Points 500 badge 2x thumb

Be aware : You have two boot : bootstrap AND bootrom !

You have to wait the POST message before using the space bar to enter in the bootroom

Try both ... and type "h" or help to get commands

Photo of modris bernands

modris bernands

  • 610 Points 500 badge 2x thumb
Thank You for note about bootrsap AND bootrom. That is what I need...
In Bootrom > "Boot 1" and "Boot 2" fail with previous Kernel panic.

Now I try download and install new/other image.
(Edited)
Photo of modris bernands

modris bernands

  • 610 Points 500 badge 2x thumb
Now I try download/install new image on Summit x350-24t by following https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-Use-the-Boot-Rom-Menu-to-Download-a...

AFTER
BootRom> configip ipaddress 192.168.1.155/255.255.255.0 gateway 192.168.1.3
NOTICE: No network interface available, rc=-1
ioctl (SIOCAIFADDR:) File exists BootRom>

And now Q: What physical port I need to use for download image (connect to tftp)?

All my 24 Ethernet ports are without any activity (leds is off).
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.

What You suggest for me to do next?
Photo of Pascal Lurquin

Pascal Lurquin

  • 970 Points 500 badge 2x thumb
Try 192.168.1.155/24 and not 192.168.1.155/255.255.255.0
Photo of modris bernands

modris bernands

  • 610 Points 500 badge 2x thumb
informative - I try both method and both of them is working,
My mistake was on cable/VLAN outside summit and it not depend from input IP/mask form....
Photo of Pascal Lurquin

Pascal Lurquin

  • 970 Points 500 badge 2x thumb

Management port Ethernet is used for ... management like tftp

try to ping first

Photo of modris bernands

modris bernands

  • 610 Points 500 badge 2x thumb
I successfully download image "summitX-12.6.2.10-patch1-15.xos" - file from last/only my summit upgrade.
.... then standard process... installing 12.6.2.10... clearing vnram .... press ENTER to reboot...

AND after restart

"kernet panic" like bottom in this topic :-(

Is this the end of the day for this switch?
Photo of Pascal Lurquin

Pascal Lurquin

  • 970 Points 500 badge 2x thumb

May be the ram in this partition is corrupted ?

Try both (loader 1 or 2 - boot 1 or 2) to choose

https://gtacknowledge.extremenetworks.com/articles/Solution/Switch-boots-up-in-the-BootRom-mode-with...

cross fingers + some time to test

Photo of modris bernands

modris bernands

  • 610 Points 500 badge 2x thumb
memory test was successful - test itterations passed with no errors.
baddly, but no one of these "loader 1 or 2 - boot 1 or 2" commands unable get out of non-stop rebooting switch.

For now, for me - it is dead  :(
Photo of Pascal Lurquin

Pascal Lurquin

  • 970 Points 500 badge 2x thumb

Have you tried another image ? an oldest one ?

Or RMA ...

Photo of modris bernands

modris bernands

  • 610 Points 500 badge 2x thumb
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.
For my logic - try older or other image is time waste. There is some technical damage...

About RMA - I dont knowing this process, but switches was purchased ~7+ years ago.
Last firmware version for us was 12.6.2.10. If I understand correct, then warranty for this device is ended.

AnyWay, thank You Pascal for support!
Photo of Pascal Lurquin

Pascal Lurquin

  • 970 Points 500 badge 2x thumb

OK :)

Try to contact the TAC ... may be some new ideas ...