Downgrading APs from SmartZone 6.1 to 5.2.2 or 6.0 Before Connecting to RUCKUS IoT Controller 1.8.2.0 MR

Complete the following steps to downgrade APs from SmartZone 6.1 to 5.2.2 or 6.0, and connect to RUCKUS IoT Controller 1.8.2.0 MR.
Note: If the AP is in SmartZone 5.2.2, proceed with steps 3 to 6.
  1. Make sure that the AP is running and is in the approved state.
  2. Downgrade the AP from SmartZone 6.1 to 5.2.2 or 6.0.
  3. Connect the AP to RUCKUS IoT Controller 2.0.0.0.

    You must wait untill the AP comes online and the RUCKUS IoT Controller AP page does not show the caution symbol.

  4. Shut down RUCKUS IoT Controller 2.0.0.0 and connect to RUCKUS IoT Controller 1.8.2.0 MR.
  5. Configure the broker IP adress of the AP to point to RUCKUS IoT Controller 1.8.2.0 MR.

Gateway Recovery

If the rollback does not complete properly from RUCKUS IoT Controller 2.0.0.0 to 1.8.2.0 MR, the following issues can occur immediately after the rollback or after a mode change in version prior to RUCKUS IoT Controller 2.0.0.0:

  • The radios do not initialize when you connect to the version prior to RUCKUS IoT Controller 2.0.0.0.
  • The radios are Unavailable (NA) in the RUCKUS IoT Controller interface.

Recovering the Gateway

If the radios do not initialize after a rollback, complete the following steps to recover the gateway.

  1. Connect the RUCKUS IoT Controller gateway to RUCKUS IoT Controller 2.0.0.0.
  2. Run and do not disturb the setup until the version mismatch indication is no longer displayed in the RUCKUS IoT Controller interface.

    You must wait untill the radios are displayed on the RUCKUS IoT Controller AP page.

  3. Migrate from RUCKUS IoT Controller 2.0.0.0 to 1.8.2.0 MR. Refer to RUCKUS IoT Controller 2.0.0.0 to 1.8.2.0 MR Rollback.
Parent topic: RUCKUS IoT Controller 2.0.0.0 to 1.8.2.0 MR Gateway Connections for APs in SmartZone 6.1 or 5.2.2