Troubleshooting Residual Issues on Non-GW Switches

8 min

Guidance for customers & partners when activation fails on non-GW switches

Scope: This guide applies only to non-GW switches. GW devices are automatically handled by the Nav Device Update Flow and do not require manual action.

Overview of Known Residual Issues (Non-GW Only)

Some non-GW switches may not complete cloud activation automatically due to:

Issue A - Stale bringup.json on the switch

A leftover bringup.json file may block cloud connectivity during first bring-up.

Issue B - NSW1000 HW 3.1: ICOS not booting

Certain NSW1000 units with hardware version 3.1 may fail to start the ICOS subsystem, leading to activation failure.

Issue A: Old bringup.json exists on the switch

Symptoms

If a device fails to connect to cloud on its first bring-up, a stale bringup.json may be the cause.

How to Diagnose & Resolve

1. Detect stale bringup.json

Run the “Switch – Cleanup Sequence 9 (clear GW config)” command via Nva Troubleshooting.

This check completes within ~5 seconds.

A TRUE output indicates a stale file exists.

2. Remove stale bringup.json

If detection returns TRUE, run “Switch - Cleanup Sequence 9 (clear GW config)” again to perform the cleanup action.

Safe to run anytime.

A device reboot is recommended after cleanup.

3. Reboot the device

Use the "6.1.1.12 - Switch: Cleanup Sequence 12 - reboot" command sequence to reboot the device

Expected Result

After cleanup and reboot, the switch should be free to re-attempt cloud connectivity normally.

Issue B: NSW1000 HW 3.1 - ICOS not booting

Symptoms

Device not connecting to cloud during activation

LED blinking blue continuously

Fans running at full speed

Usually observed on HW version 3.1

Caused by a mismatch in SW/HW expectations

How to Diagnose & Resolve

Run all commands via the Nav Troubleshooting.

Step 1 - Confirm hardware version

Check the switch:

Pull-out asset tag, or

Run BLE “HW Version” command If version = 0x15, device is HW 3.1.

Step 2 - Verify ICOS status

Run the “Verify ICOS Status” command.

If ICOS status = active → no fix needed; continue activation

If ICOS status ≠ active → proceed to Step 3

Step 3 - Apply ICOS fix (only if ICOS not active)

Run the command “NSW1000: Fix ICOS HW 3.1” (updated command name).

This updates the ICOS launcher condition

Required only on HW 3.1 units

This automatically reboots the device as well

Step 5 - Re-verify ICOS after reboot

Run the “Verify ICOS Status” command again.

Expected state = active

Expected Result

After verifying ICOS status as active and reboot, the switch should be free to re-attempt cloud connectivity normally.

Quick Action Summary

Action	Command Name	When to Use	Expected Outcome
Detect stale bringup.json	Switch – Cleanup Sequence 9 (clear GW config)	Activation failing on first bring-up	Returns TRUE if stale file exists
Remove stale bringup.json	Switch – Cleanup Sequence 9 (clear GW config)	If detection returned TRUE	Stale file removed; reconnect after reboot
Verify ICOS status	Verify ICOS Status	NSW1000 activation failure symptoms	Confirms whether ICOS is active
Fix ICOS on HW 3.1	NSW1000: Fix ICOS HW 3.1	ICOS status not active on HW 3.1	Fix applied; device reboots and ICOS initializes
Reboot Device	6.1.1.12 - Switch: Cleanup Sequence 12 - reboot	Reboot Device after applying both updates	Reboots the device

Please contact Nile Support in case of any further issues.