Reset Search
 

 

Article

XSR Reboots Intermittently

« Go Back

Information

 
TitleXSR Reboots Intermittently
Symptoms
XSR Reboots Intermittently
Environment
XSR-1805
XSR-1850
XSR-3020
XSR-3150
XSR-3250
All Firmware Revisions
Cause
An XSR that is rebooting frequently is crashing.  This behavior can be from a wide variety of causes too numerous to list.
Resolution
At first awareness that the XSR has rebooted for no known cause the system administrator should follow either of these procedures:

Procedure A
1. Download a copy of the XSRadmintool from Extreme Networks Diagnostic Tools at this URL:
http://www.extremenetworks.com/support/software#diagnosticTools

or for direct download click here:
http://extrcdn.extremenetworks.com/wp-content/uploads/2014/02/xsradmin.zip

2. Unzip XSRadmintool.zip to an empty directory
3. Double-click on the executable "xsradmintool.exe"
4. A command window will open and prompt for the IP address of the router, type in the address and press ENTER
5. A prompt requesting the admin account password will appear, type in the password and press ENTER
6. The program will run a series of "show" commands saving the response from each in a text file and accumulate each text file into a zippoed archive.  This archive will have the router name and the current date and time.
7. When the program has completed its run the command window will close.
8. Examine the zipped archive to see if there is a fault report (fault.txt)  If you do not find a fault report check the router command line with the command "show fault".  Save this to a text file and manually add it to the zipped archive that was created by the XSRadmintool.exe.
9. If there is a fault report then the fault report must be cleared manually, see additional notes below. 
10. Contact the Extreme Networks GTAC to log a service case and provide the GTAC technician with a copy of the zipped archive for analysis
 
  • Use of the XSRadmintool requires telnet access and an admin account in the configuration of the router.  If telnet is blocked or disabled, or the admin account has been replaced by any other username then you will need to use Procedure B below.

Procedure B

Use procedure B only if the XSR admintool described above cannot be run or fails to run:

Log in to the CLI while logging all session output to a text file
  1. At minimum capture the router response to all of the following commands:
XSR# show fault
XSR# show version
XSR# show buffers
XSR# show limits
XSR# show running-config
XSR# show ip routes
XSR# show logging history

2. Contact the Extreme Networks GTAC to log a service case and provide the Extreme Networks technician a copy of the CLI log.  The technician may request other information from the router.
 
 
Additional notes
If a fault report was generated and displayed, then after it has been captured in a text file it must be cleared manually:

XSR# clear fault

If the fault report is not cleared then the router will not be able to log a new fault report if there is any subsequent crash.  This is of great importance because it often takes examination of several subsequent fault reports to determine the root cause of the crash!
 

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255