Summary

Question

How to fix 'ping failed; host 192.168.0.x is not alive' error during the Software Recover process?

Customer Environment

Symptoms

In Figure 1, you can see the highlighted error message:

FIGURE 1: “ping failed; host 192.168.0.x is not alive” error

Root Cause

Troubleshooting Steps

Step 1: Disable Firewall

1. Refer to this link Windows Security Settings on your PC.

2. Navigate to Firewall & Network Protection.

3. Turn OFF the Firewall for all profiles:

• Domain Network
• Private Network
• Public Network

FIGURE 2: Firewall & Network Protection Settings

Important: Ensure the firewall is turned off for all profiles before proceeding.

4. Close PuTTY (or whichever terminal program you are using).

5. Restart PuTTY and begin the Software Recovery process again, starting from the setenv IP configuration step in the official recovery guide.

Workaround

Step 2: Manually Load Software (if error persists after Step 1)

If you still encounter the same error even after turning off the firewall, continue the process manually by entering the following commands in order.

Load Image into Primary Partition:

setenv image_name SPS08090k.bin

update_primary

(Replace SPS08090k.bin with the correct image filename you are using)

FIGURE 3: Primary Image Update Command

Load Image into Secondary Partition:

setenv image_name SPS08090k.bin

update_secondary

FIGURE 4: Secondary Image Update Command

Load Boot Code:

setenv uboot mnz10115.bin

update_uboot

(Replace mnz10115.bin with the correct boot file name provided in your recovery package)

FIGURE 5: Boot Code Update Command

Final Reset Command

reset

This will reload the unit and complete the recovery process.

FIGURE 6: Final Reset Command

Expected Result

After successfully completing the Software Recovery process:

• Both SYST and PWR lights on the Switch should turn Green.
• The Switch should boot normally and operate as expected.

Resolution

• Disable the Firewall on your PC to allow communication during Software Recovery.

• Restart PuTTY (or the terminal app) and retry the Software Recovery steps from the beginning.

• Manually load the firmware image using the setenv image_name and update_primary commands if the error continues.

• Manually load the secondary image using update_secondary.

• Manually update the boot code using setenv uboot and update_uboot.

• Reboot the switch using the reset command to complete recovery.