topic Re: Migrate R700 Firmare version 3..6.2.0.695 to new Virtual SmartZone in SmartZone and Virtual SmartZone

Migrate R700 Firmare version 3..6.2.0.695 to new Virtual SmartZone

Icky — Mon, 20 May 2024 02:44:27 GMT

There are 6 models in my Virtual SmartZone controller (5.2.2.0.1563) which are list below.
Frimware version 3.6.2.0.695 ==> R700 and the total q'ty are 237 pcs
Firmware version 5.2.2.0.2069 ==> R500, R550, R600, R610,R650, T610 and the total q'ty is aroud 5,200 pcs

Recently we rebuild the VSz to active the IPV6 and there is a problem to migrate the R700 to the new build cluster.
For the R500,R550,R600,R610,R650 and T610, I can use switchover cluster command and success to migrate the AP to new VSz.
For R700 always fail to switchover no matter to migrate 1AP at a time or 1 batch in the same time.
Is there any step I missed before I start to migrate the R700?

Thanks

MIchael Chen

Re: Migrate R700 Firmare version 3..6.2.0.695 to new Virtual SmartZone

Vineet_nejwala — Mon, 20 May 2024 13:56:35 GMT

Hi @Icky

When you say rebuild the vSZ does that mean you also have uploaded config or cluster back up from old one on to this new one ? R700 would only be supported with code 5.1.x and below so if these APs by any chance are trying to go to default zone which I assume is on 5.2.2 it wont come up. You would need to create an AP registration rule to let the AP know to go on specific zone which belongs to 3.x or 5.1.x code.

Best Regards

Vineet

Re: Migrate R700 Firmare version 3..6.2.0.695 to new Virtual SmartZone

Icky — Tue, 21 May 2024 05:26:56 GMT

Does the AP registration rule create at the new vSZ or old one?

Thanks,
Icky

Re: Migrate R700 Firmare version 3..6.2.0.695 to new Virtual SmartZone

sanjay_kumar — Tue, 21 May 2024 05:48:01 GMT

Hi @Icky
The Registration rule should be on the new vSZ. Below are the steps:

To create an AP registration rule:
1. Go to Network > Wireless > AP Settings > AP Registration.
NOTE
For SmartZone 5.2.1 or earlier releases, select System > AP Settings>AP Registration.
2. Click Create, the AP Registration Rule form appears.
3. Enter a Rule Description.
4. Select the Zone Name to which this rule applies.
5. In Rule Type, click the basis upon which you want to create the rule. Options include:
• IP Address Range: If you select this option, enter the From (starting) and To (ending) IP address that you want to use.
• Subnet: If you select this option, enter the IP address and subnet mask pair to use for matching.
• GPS Coordinates: If you select this option, type the GPS coordinates to use for matching. Access points that have been assigned the
same GPS coordinates will be automatically assigned to the AP zone that you will choose in the next step.
You can choose the Rule Type as GPS coordinates, wherein you must provide information about the latitude, longitude and distance
to determine if the AP is within the defined area.
• Provision Tag: If the access points that are joining the controller have been configured with provision tags, click the Provision Tag
option, and then type a tag name in the Provision Tag box. Access points with matching tags will be automatically assigned to the AP zone that you will choose in the next step.
NOTE
Provision tags can be configured on a per-AP basis from the access point’s command line interface.
6. Click OK.

IP Range and the subnet are the easiest method, but if the problematic APs are not in a specific IP range or subnet, then you can choose the Provisional tag:
Once done creating the Registration rule on the new vSZ, For the old vSZ where the problematic APs (R700 I believe) are still connected, please set the Provisional tag using the AP CLI script. This tag will be used while connecting to the new vSZ and will move to the specific zone when you click on Switch over cluster.

For example, if you are creating a Registration rule on the new vSZ with the provisional tag as "AX", then you need to set the provisional tag on the R700 APs (from old vSZ) as below

From the AP we used the below command to set the provision tag.
set provisioning-tag "AX"