After upgrade to IOT 1.5 many AP's went to unregistered state on the IOT controller (TSB 2020-004)

Summary

After upgrading to IOT 1.5 Release from a previous version or installing a fresh image of IOT 1.5, AP’s can stay in unregistered state if IOT controller does not have sufficient licenses installed.

Question

Why IOT AP's are unregistered after upgrading IOT controller to 1.5

Customer Environment

Ruckus IOT Controller (vRIOT) running 1.5 firmware AP's, SZ/vSZ IOT Module IOT Devices.

Root Cause

AP capacity licenses on IOT controller are applied to AP's on first come first served basis and it is not dependent on whether APs have an IOT module installed.

Symptoms

After installing/upgrading to IOT 1.5 Release, APs can stay in unregistered state.
 

Troubleshooting Steps

See attached TSB.

Workaround

The work around is –
  1. Remove all AP’s from the IOT controller.
  2. Set IoT enable on the APs with installed IoT module.
  3. Add IoT Controller IP address manually on the APs with an IoT module
Please see the attached TSB for more details.  

Resolution

Purchase necessary licenses prior to RIoT 1.5 upgrade.
 
Ruckus IOT version 1.5 controller requires 3 distinct licenses for operation.

Performing a firmware upgrade Ruckus IOT controller from earlier version than IOT 1.5 or upon
installing a fresh instance of IOT 1.5 we require IOT controller to have licenses installed for RTU,
Instance and the AP capacity.

The AP capacity licenses are used to manage the IOT AP’s by the controller. However, these licenses
are assigned to the AP on first come first served basis and would not look for the IOT Dongles connected
to the AP’s.

This may lead to a situation where AP’s stay in unregistered state if IOT controller does not have enough
AP capacity licenses to support all AP’s.

Attachment 1

TSB2020-004-IOT-1.5 Licensing.pdf
application/pdf
Download
(392 KB)

Article Number:
000010131

Updated:
May 01, 2020 11:14 AM (2 months ago)

Answer Attachment 1
TSB2020-004-IOT-1.5 Licensing.pdf
application/pdf
Download
(392 KB)

Tags:
Known Issues and Workarounds, I100, vRIoT

Votes:
0

This article is:
helpful
not helpful

Working...Please wait

This is here to prevent you from accidentally submitting twice.

The page will automatically refresh.