cancel
Showing results for 
Search instead for 
Did you mean: 

How to migrate APs from XCC to VX900

How to migrate APs from XCC to VX900

EF
Contributor

Hi team,

We have APs onboarded over XCC running rel 4.X and we´ll replace XCC by VX9000 cluster.

I dont know if there is any procedure, compatible releases, etc.. or if it´s so simple as adopt the APs on the new VX9000 cluster.

NOTE: the AP model is supported on the VX9000 rel.

Thanks in advance for any information given.

EF

1 ACCEPTED SOLUTION

Adam_Minowski
Contributor

Usable article is here:

https://extremeportal.force.com/ExtrArticleDetail?an=000077265&q=xcc%20to%20wing 

D - To switch the AP personality from Identify to WiNG please follow these steps:

1. SSH into the AP
2. Run the following commands:

#cset personality distributed
#AP personality successfully set. Please factory default the AP
#cset factory

3. Once reset, the AP will boot straight up into WiNG

Whether APs would conenct to VX depends on situation and VX config. If your VX cluster would be in the same VLAN, APs should find it automatically for you to adopt. If you would like to use IP adoption (VX and APs are in different VLANS/subnets), use either:
1. DHCP discovery option 191 (https://extremeportal.force.com/ExtrArticleDetail?an=000086612&q=wing%20dhcp%20options)
2. DNS discovery - add IN A record with name wing-wlc.<domainname> pointing to your VX cluster.

Helpful document is:
https://documentation.extremenetworks.com/WiNG/Implementation_Guides/WING5X_How_To_Centralized_Deplo... 

I'd suggest DHCP discovery as with that you can use Level2 MINT. DNS works only with Level1. 
To understand what Levels are and what MINT is you have to read some technical documents around MINT. But in general MINT is proprietary protocol for Wing to communicate between Wing devices (control plane) based on ISIS protocol.

I'd suggest to use auto-provisioning-policy in Wing cluster from the beginning - to make your life easier. Everything would work automagically - meaning APs will upgrade Wing firmware, adopt and configure themselves based on respective profile (config template).

View solution in original post

1 REPLY 1

Adam_Minowski
Contributor

Usable article is here:

https://extremeportal.force.com/ExtrArticleDetail?an=000077265&q=xcc%20to%20wing 

D - To switch the AP personality from Identify to WiNG please follow these steps:

1. SSH into the AP
2. Run the following commands:

#cset personality distributed
#AP personality successfully set. Please factory default the AP
#cset factory

3. Once reset, the AP will boot straight up into WiNG

Whether APs would conenct to VX depends on situation and VX config. If your VX cluster would be in the same VLAN, APs should find it automatically for you to adopt. If you would like to use IP adoption (VX and APs are in different VLANS/subnets), use either:
1. DHCP discovery option 191 (https://extremeportal.force.com/ExtrArticleDetail?an=000086612&q=wing%20dhcp%20options)
2. DNS discovery - add IN A record with name wing-wlc.<domainname> pointing to your VX cluster.

Helpful document is:
https://documentation.extremenetworks.com/WiNG/Implementation_Guides/WING5X_How_To_Centralized_Deplo... 

I'd suggest DHCP discovery as with that you can use Level2 MINT. DNS works only with Level1. 
To understand what Levels are and what MINT is you have to read some technical documents around MINT. But in general MINT is proprietary protocol for Wing to communicate between Wing devices (control plane) based on ISIS protocol.

I'd suggest to use auto-provisioning-policy in Wing cluster from the beginning - to make your life easier. Everything would work automagically - meaning APs will upgrade Wing firmware, adopt and configure themselves based on respective profile (config template).

GTM-P2G8KFN