---
title: Troubleshooting Residual Issues on Non-GW Switches
slug: troubleshooting-residual-issues-on-non-gw-switches
createdAt: 2025-12-03T11:54:19.325Z
---

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

:::BlockQuote
**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:

:::Paragraph{indent="1"}
**Issue A - Stale bringup.json on the switch**
:::

:::Paragraph{indent="2"}
A leftover bringup.json file may block cloud connectivity during first bring-up.
:::

:::Paragraph{indent="1"}
**Issue B - NSW1000 HW 3.1: ICOS not booting**
:::

:::Paragraph{indent="2"}
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

:::Paragraph{indent="1"}
**1. Detect stale bringup.json**
:::

:::Paragraph{indent="1"}
Run the **“Switch – Cleanup Sequence 9 (clear GW config)”** command via Nva Troubleshooting.
:::

:::Paragraph{listStyleType="disc" indent="2"}
This check completes within \~5 seconds. 
:::

:::Paragraph{listStyleType="disc" listStart="2" indent="2"}
A **TRUE** output indicates a stale file exists. 
:::

:::Paragraph{indent="1"}
**2. Remove stale bringup.json**
:::

:::Paragraph{indent="1"}
If detection returns TRUE, run **“Switch - Cleanup Sequence 9 (clear GW config)”** again to perform the cleanup action.
:::

:::Paragraph{listStyleType="disc" indent="2"}
Safe to run anytime. 
:::

:::Paragraph{listStyleType="disc" listStart="2" indent="2"}
A device reboot is recommended after cleanup. 
:::

:::Paragraph{indent="1"}
**3. Reboot the device**
:::

:::Paragraph{indent="1"}
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**

:::Paragraph{indent="1"}
Check the switch:
:::

:::Paragraph{listStyleType="disc" indent="2"}
Pull-out asset tag, or 
:::

:::Paragraph{listStyleType="disc" listStart="2" indent="2"}
Run BLE “HW Version” command
 If version = 0x15, device is HW 3.1. 
:::

**  Step 2 - Verify ICOS status**

:::Paragraph{indent="1"}
Run the **“Verify ICOS Status”** command.
:::

:::Paragraph{listStyleType="disc" indent="2"}
If ICOS status = **active** → no fix needed; continue activation 
:::

:::Paragraph{listStyleType="disc" listStart="2" indent="2"}
If ICOS status ≠ active → proceed to Step 3 
:::

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

:::Paragraph{indent="1"}
Run the command **“NSW1000: Fix ICOS HW 3.1”** (updated command name).
:::

:::Paragraph{listStyleType="disc" indent="2"}
This updates the ICOS launcher condition  
:::

:::Paragraph{listStyleType="disc" listStart="2" indent="2"}
Required only on HW 3.1 units 
:::

:::Paragraph{listStyleType="disc" listStart="3" indent="2"}
This automatically reboots the device as well
:::

**Step 5 - Re-verify ICOS after reboot**

:::Paragraph{indent="1"}
Run the **“Verify ICOS Status”** command again.
:::

:::Paragraph{listStyleType="disc" indent="2"}
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.