This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
RUCKUS Self Help |   ASK the Pack
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

How to perform a Software recovery on an ICX7150 switch

Yarenis
Moderator
Moderator

‎11-01-2022 01:08 PM - last edited on ‎06-23-2025 01:39 PM by Moderator

How to perform a Software recovery on an ICX7150 switch

 

 Issue Description

Due to a power outage or power spike, the RUCKUS ICX-7150-C12P Switch has entered a state known as boot mode, where it is unable to start normally. This typically indicates a corrupted image flash. To resolve this, a software recovery is required to reinstall the firmware and restore normal operation.

Software recovery is like giving a fresh start when the system doesn’t work. The recovery involves starting the switch in a recovery mode and reinstalling a valid software image to resolve the issue and returning the switch to boot up properly.

Environment:

  • Product(s)                                   :  RUCKUS ICX-7150-C12P Switch
  • Hardware requirement        : A Windows computer or MAC, USB to Type- C cable and an ethernet cable.

 Root cause:

  • Corrupted image flash due to a power outage/power spike.

Symptoms:

  • The Switch will not supply power to any PoE devices, including the doorbell, cameras, and Access Points.
  • Devices connected to the Switch will not have network connectivity.
  • Console access will be the only available method to access the Switch.
  • The SYST light will display a yellow/orange (amber) light.

 

Steps to perform Software recovery:

A)  Gain console access to the Switch:

The Switch can be accessed via the console following the mentioned article:

Establishing Console CLI Access on the RUCKUS ICX-7150-C12P Switch

 

The software recovery process typically requires two cables.

USB to Type- C cable where one end of the cable has a USB Type-C connector, while the other end has a standard USB (Type-A) connector and an ethernet cable with both ends of RJ-45 plugs.

 Use a console cable to connect your computer to the USB Type-C console port on the ICX 7150 Switch. The cable should be a USB-to-Type-C cable, with the USB end connected to your computer and the Type-C end plugged into the Switch’s Type-C console port (Port 1 in the figure 3) as shown in the figure 1:

pinky_ruckus_12-1750710373673.pngFigure 1: Type C to USB connector

Next, connect an Ethernet cable from the out-of-band management port on the Switch to the Ethernet port on your computer as shown in the figure 2. (Out of band management port is the port number 13 in figure 3).

pinky_ruckus_1-1750708586759.png

Figure 2: RJ-45 connector



pinky_ruckus_2-1750708586774.pngFigure 3: Port side view of the Switch

 Now, we have access to the Switch through the console cable.

 

B) Configuring the Switch with the Console:

              As we get access to the Switch command line interface (CLI) using the console cable, the next step is to configure the Switch with the Command Line Interface (CLI).

This lets you access the Switch even if it’s not turning on properly or if you don’t know its IP address.

Once you have access to console CLI; while opening PuTTY, you will see a prompt that says ‘boot>’, indicating the device is in boot mode.

pinky_ruckus_3-1750708586775.pngFigure 4: Putty in boot mode

Configuring the Computer’s IP address: Let's proceed with configuring a static IP address on your computer to establish connectivity with the switch. Since the computer is connected to the switch's management port via an Ethernet cable, the IP address must be set within the same subnet as the switch to enable proper communication.

  • Click on Start, then type and open Control Panel.
  • Go to Network and Sharing Center > Change adapter settings.
  • Right-click on your Ethernet connection and select Properties.
  • Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
  • Choose Use the following IP address, then enter the IP information provided.
  • Click OK to apply the settings.

pinky_ruckus_4-1750708586801.pngFigure 5: Configuring the IP address

Now, as a part of configuring the Switch with the console, we need to assign an IP address to the Switch, default gateway server for your network, subnet mask of the network along with the IP address of the TFTP server.

  • setenv ipaddr 192.168.0.3 to assign an IP address to the Switch.
  • setenv gatewayip 192.168.0.2 to configure the default gateway IP address for your network. This should match the IP address assigned to your computer when accessing the Switch via console.
  • setenv netmask 255.255.255.0; the subnet mask should correspond to the one associated with your network, matching the value found using the CMD command on your computer.
  • setenv serverip 192.168.0.2 to enter the IP address    of the TFTP server, which refers to the computer connected to the Switch via the management port.
  • Printenv to double-check the values just changed for accuracy.
  • Once the values are verified, we can save the changes using the command saveenv.

      pinky_ruckus_5-1750708586807.pngFigure 6: Configuring Switch with the console

 C)   Testing connectivity to network IP

We have configured the Switch to work on your network with the computer.
Next, we need to check if the Switch and the computer can connect to each other.
This will help us make sure they can communicate each other.

Making sure they are connected is important for the Switch to work as expected using the command   ‘ping 192.168.0.2’

pinky_ruckus_6-1750708586811.pngFigure 7: Testing connectivity to network IP

 The ping response should indicate "alive" to confirm successful connectivity. If it returns "is not alive", it means there is no communication between your computer and the Switch.
Ensure the Windows firewall is turned off, ethernet cable is properly connected from the Out-of-Band (OOB) management port on the Switch to your computer’s Ethernet port.

The Ping not alive error can be fixed by following the mentioned article: Fixing “host 192.168.0.x is not alive” (not alive) error during the Switch Software Recovery Process

pinky_ruckus_7-1750708586835.png

Figure 8: Computer’s IP address and configuration of the Switch

D)   Performing Software Recovery:

Now that the Switch has been configured and there is connectivity to the computer/server, we can proceed with the software recovery. This process essentially involves performing a software upgrade while the Switch is in boot mode. This process is typically used to restore the device when it fails to boot normally.

1)  Use the command setenv image_name SPS08090k.bin to enter the correct firmware image file name.

2)  The entered image file name should be uploaded to the primary partition using the command update_primary.

pinky_ruckus_8-1750708586839.pngFigure 9: Entering image filename to Primary partition

3)  The saved firmware image file name should be entered and uploaded to the secondary partition as well using the commands:

  • setenv image_name SPS08090k.bin
  • update_secondary

pinky_ruckus_9-1750708586843.pngFigure 10: Entering image filename to Secondary partition

 4)  Once the images are loaded to both partitions; the boot file name also should be entered and the boot code needs to be entered using the following commands:

  • setenv uboot mnz10115.bin
  • update boot            

pinky_ruckus_10-1750708586849.pngFigure 11: Boot code is loaded

5)   Once the boot code is loaded, the unit should be reloaded using the command: reset pinky_ruckus_11-1750708586852.pngFigure 12: Rebooting the Switch

After the unit reloads, the SYS light should turn green, indicating that the system has booted up successfully.

 

 

 

 

 

 

 

 

 

Labels:
Reply
0 REPLIES 0
Labels
Copyright © 2025 Khoros, LLC