IoT/vRIOT Migration process from 1.8.2 to 2.0 or 2.1 or 2.2

Summary

This document outlines the procedure for migrating an existing RUCKUS IoT Controller license to RUCKUS IoT Controller 2.0.0.0 RUCKUS IoT Controller 2.0.0.0 is a fresh install. There is no direct upgrade path from 1.8.2.. MT for new subscription/license

Question

IoT-Migration-from-1-8-2-to-2-0-0

Customer Environment

IoT/vRIoT 1.8.2.0.44 IOT/vRIOT 2.0.0.0.82 IOT/vRIOT 2.1.0.0 IOT/vRIOT 2.2.1

Resolution

Licensing Model Prior to the 2.0.0.0 release
Prior to RUCKUS IoT Controller 2.0.0.0, an AP-based licensing model was supported, in which licenses were used by approved APs.
Types of licenses in AP-based licensing model:
1. RTU license, temporary trail licenses
2. AP capacity licenses
3. Support Contract/ licenses
The licenses were either perpetual licenses or limited to customized expiration dates.

Licensing Model from 2.0.0.0 release
Beginning with RUCKUS IoT Controller 2.0.0.0, support for Device-based licensing model instead of AP-based licensing. The Device-based licensing model features the following benefits:
• The Device-based licenses are used by the connected devices instead of APs.
• You can add an unlimited number of APs, but you must purchase a license for each device.
• During the initial 90-day trial period, you can add an unlimited number of devices, APs, and plugins.
• The Device-based model is based on subscription and you can purchase a license for 1, 3, or 5 years.
Types of license in Device based licensing model are of three types Core, Instance & Device Capacity details below:

Core - Core license is the basic (or primary) license that must be purchased to obtain the authority to access the features of the RUCKUS IoT Controller. The Core license is a perpetual license bound to the serial number of the controller.
Instance - Depending on your requirements, after installing a Core license, you can purchase an Instance license. The Instance license is based on a subscription and maintains a tenure of 1, 3, or 5 years. Instance licenses are offered in three types.

Insights: An Insights license allows you to enable plugins, add connected devices, and use IoT Insight features.
Premium: A Premium license allows you to enable plugins and add connected devices.
Base: A Base license allows you to enable plugins, but connected devices will be in the decommissioned mode.

?????? 3. Device Capacity - To access the connected devices, after installing a Core license, you can purchase a Device Capacity license. The Device Capacity license is based on a subscription and maintains a tenure of 1, 3, or 5 years.

Note:
1. Each Device Capacity license consists of 250 devices. Therefore, if you purchase three Device Capacity licenses, you will be able to add 750 devices (3 x 250) to the RUCKUS IoT Controller.
2. If you have two device capacity license 250+250, and only one gets expired then only 250 devices will be de-commissioned.
3. If a new license is uploaded after the devices are de-commissioned then you can commission the devices by selecting the devices, and clicking on batch action-->commission

Licensing Model from 2.2.0.0 release
With the launch of RUCKUS IoT Controller 2.2.0.0, the RUCKUS Container per Access Point (RCAP) licensing model takes precedence over the previous device-based licensing structure.
Types of licensing:
1. Core
A Core (RTU) license is a primary license, this is perpetual license, activated against the vRIoT SN)
2. RCAP
The RCAP licensing model operates on a subscription basis providing the flexibility to procure licenses for duration spanning 1, 3, or 5 years, which includes Watch Dog support.
One RCAP license is required for each Access Point or IoT Gateway connected to the RUCKUS IoT Controller.
3. Solution (Optional for Insights)
IoT Solutions are deployed on the “IoT Insights” platform this as an optional feature for users wishing to visualize and interact with IoT Sensors directly rather than through external Services/Clouds or Platforms.

Criteria for Migrating from Version 1.8.X IoT Licenses to Version 2.0
To be eligible for the migration of pre-2.0 IoT licenses to the version (2.0), customers must meet the following criteria.
• License Snapshot: Customers are required to take a snapshot of the LICENSE page on their pre-2.0 IoT Controller. This snapshot should clearly display all the licenses (RTU) that are installed on the controller.
If any of the above criteria are not met, the customer may not be eligible for a free upgrade to the latest version (2.0).

License Migration Process:

An existing user of RUCKUS IoT Controller is already using a perpetual license, L09-INT1-WW00(RTU) and L09-INT1-AP00(AP capacity licenses).
RUCKUS offers one year of subscription based licenses for customers who have purchased perpetual AP licenses and RTU and want to install RUCKUS IoT Controller 2.0.0.0.
After one year, customers must purchase renewal licenses based upon their requirements.
If your RUCKUS IoT Controller has an active support period that extends beyond one year, RUCKUS will align the validity of the subscription-based licenses with the duration of the active support period.
This offer ends effective March 2024 and only the customers with an active perpetual license and support will be migrated after that due date
An RTU/core license L09-INT1-WW00 supports the new (2.0.0.0) RUCKUS IoT Controller serial number
To migrate RTU licenses we/customers should create IOTC-RMA for the 1.8.X version serial number.
IoT-RMA article - https://support.ruckuswireless.com/articles/000004883
The eligible Licenses and SKUs for migration or transfer are as below:
1 x IOT-SOPM-PREM-MSP1- IOT Sub Premium Spp 1yr MSP
1x IOT-SOPM-0250-MSP1 -- IOT Sub 250 Devices Spp 1yr MSP (Or) IOT-SOPM-050-MSP1
Customers/Partners must Contact Ruckus Support for this process. An estimated duration of migration for the subscription based license is 48 hours.

Criteria for Migrating from Version 1.8.X IoT Licenses to Version 2.2
For each Access Point (AP) licensed and supported on the 1.x IoT controller with a valid support contract , the following provisions will be made:
1. Two IOT-SOPM-RCAP-MSP1 Licenses will be provided.
2. A Right to Use (RTU) for the new IoT controller will be granted on a one-to-one basis for the existing IoT Controllers.
3. Additionally, the duration of RCAP License will be extended based on the support contract's status on the 1.x IoT platform to ensure continuity of availability.

Criteria for Migrating from Version 2.x IoT Licenses to Version 2.2

For each AP onboarded onto the IoT controller, the following provisions will be made:
1. Two IOT-SOPM-RCAP-MSP1 Licenses will be provided.
2. A screenshot demonstrating the licensed controller and its associated APs onboarded and provisioned, along with the License page displaying a minimum of one device per AP onboarded, must be provided.
3. The new RCAP licenses will cover the duration of the existing term of the device licenses installed, and license coverage will extend beyond the current Controller Device License Termination Date.

Frequently Asked Questions (Q&A)
To address common questions and scenarios that customers may encounter, we've included a Q&A section
• Q1: I have an existing support contract that expires on a specific date. How much of the license or subscription am I eligible for?
• A1: If the existing support contract extends beyond one year of validity, the migrated license and s†bscrbr?on will match the end date of the older (1.8) controller.
• Q2: I have a 1.8 controller with expired support licenses. Can I still upgrade?
• A2: As part of the migration to 2.0, RUCKUS will provide customers with a one-year license subscription to support 2.0. At the end of the one-year period, customers must renew licenses or subscription based on their requirements.

000012202

Article Number:
000012195

Updated:
August 29, 2024 02:12 PM (3 months ago)

Tags:
Support License Activation, Registration, vRIoT

Votes:
1

This article is:
helpful
not helpful