Antonio Perez

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
======WIRELESS SWITCH HANGS DURING REBOOTING PROCESS FOLLOWING UPGRATE TO PRE 4.0.20 SOFTWARE======
 
**Problem:** 

  * Switch hangs during rebooting process following upgrade to pre-4.0.20 software 
  * Wireless Switch hangs during rebooting 
  * Wireless Switch hangs after being reset
  * Wireless Switch hangs after upgrading from 3.2.x software to 4.0.x firmware. 
  * When the console is attached, the following boot messages are displayed when the unit is hung:



=====Wireless Switch Bootstrap/Bootloader=====


  
                    Version  3.2.17  Release 
  
      Compiled on Tue Mar 29 19:39:02 PST 2005 by build
    
   
  
         Bootstrap version:          3.22     Active
  
      Bootloader 0 version:        3.2.17     Active
  
      Bootloader 1 version:        3.2.17 
  
   
  
      Mainboard Revision:    1.
  
  FPGA Controller Revision:    8.
  
  \
   
      BOOT Index:   1
      BOOT TYPE:    c  
      DEVICE:       boot1:  
      FILENAME:     default  
      FLAGS:        00000000
  
      OPTIONS:      
  
   
   
  
  Autoboot flag set, enter  followed by ENTER to abort...1
  
  Compact Flash load from boot1:default matches WXB04019.REL.
  
  unzip: Inflating wxb04019.rel OK
  
  unzip file len 19353076 OK
  
   
  
**At this point the booting process hangs**
 
**Problem:**
  * After tftp'ing a 4.0.x build to the WX1200, changing the boot partition and booting the WX1200, the booting fails when attempting to inflate the 4.0.x build
  * Switch stops responding 
  * Switch is not working
  * Switch stops working after reboot 

 
**Fact:** 

  * Wireless LAN Switches and Controllers 
  * Wireless LAN Switch WX1200 
 
**Cause:** Starting in July of 2005, there was a limited production run of WX1200  main boards built with the Disk-On-Chip programmed for the operation in the WXR100 which will eventually lead to WX1200  3.x to WX1200  4.x upgrade issues in the field.


While many units will upgrade without issue initially, subsequent upgrades may experience the issue until the unit is upgraded to 4.0.20 software or later.

 

Production units pre-loaded with WX1200  4.x do not appear to experience this problem. These units never ran a WX1200 3.x build, so this 3.x to 4.x upgrade failure would have never occurred. 
 
 
**Fix:** If the WX1200 is to be upgraded to software earlier than version 4.0.20, implement the following steps prior to the upgrade.  

 

=====Disk-on-chip recovery steps=====

  * Backup the switch to a tftp server with the “backup system” command:

  backup system tftp://<tftp-server-IP>/<filename

Execute a **“dir”** command from the CLI and look for any **“core”** files or any image files which are not contained in the “Boot0” or **“Boot1”** areas.  

If there are any present delete them with the “delete <filename>” command.

Execute the following commands to correct the formatting on the Disk-on-chip.:

  doc-upgrade old
  doc-upgrade new
  
  Upgrade to the 4.0.x software.
 
 
**Fix:** If the WX1200 has already been upgraded to a 4.0.x version of software that precedes version 4.0.20, then only upgrade to version 4.0.20 or later if at all possible.  The later version will automatically make the appropriate updates. 
 
**Fix:** If the unit is hung in the boot process, the WX1200 will be required to execute a network boot.  The network boot recovery is a 2 phase process.  The first phase loads the operational image into RAM and executes the code.  At that point the WX1200 will boot and will be manageable.  The second phase is to TFTP the operational code to the WX1200 at which time the code will be saved to flash.  Unless the network code to be installed is 4.0.20 or later, the network boot image used must be version 3.2.2. Use the steps discussed above in “Disk-on-chip” recovery after successfully installing the 3.2.2 software.


=====The network boots steps are outlined below:=====


  * Go to boot prompt by pressing q key while the switch is booting and then press enter.

 

From the boot> prompt enter these commands:



  change (return)
  
  BOOT TYPE:    [c]> n (return)
  
  DEVICE:       [boot1]> emac1
    
  Enter 'emac1-emac8' (where each no. represents a single port on the switch). 
  
  FILENAME:     [default]> wxb03202.rel (the filename which is been shared on TFTP Server)
  
  HOST IP:      [0.0.0.0]> 192.168.1.10 (TFTP Server IP address)
  
  LOCAL IP:     [0.0.0.0]> 192.168.1.8 (Switch IP address)
  
  :   [0.0.0.0]> 192.168.1.1 (Your Default gateway, Enter ip if you don’t have default gateway)
  
  IP MASK:      [0.0.0.0]> 255.255.255.0 (subnet mask of you network)
  
  FLAGS:        [0x00000000]> (default)
  
  OPTIONS:      [run=nos;root=md0a;[update]]> (default)
  
   

Press Enter to display the changed values.

    BOOT Index:   1
    BOOT TYPE:    n
    DEVICE:       emac1
    FILENAME:     wxb03202.rel
    HOST IP:      192.168.1.10
    LOCAL IP:     192.168.1.8
    GATEWAY IP:   192.168.1.1
    IP MASK:      255.255.255.0
    FLAGS:        00000000
    OPTIONS:      run=nos;root=md0a;[update]reset

 

  * Type  reset to boot the switch from TFTP Server
  * The Switch will boot from the network (tftp Ser ver)
  * And you will enter into the normal prompt 


Once the WX1200 has booted, login and initiate the steps to formally install the 3.2.2 software.  The installation of the 3.2.2 software can be accomplished using the command line interface or from 3WXM software image distribution services.  
 
 
 
   New Search 
  Product FAQ's 
  Send Feedback 
  Print Solution 
  Email Solution 
  Back To Solution List 
  Self Help Links  
  Product Support Page 
  3Com eSupport 
  3Com Home 

  
  Did this solution document 
  help you solve your problem? 
   100%  75% 
   50% 25% 
              0% 

 
 --- //[[nce@itclatam.com|David Gonzalez]] 2021/03/31 17:15//