10-12-2012 09:34 AM - edited 07-03-2021 10:49 PM
Hi, we are planning to do an AP migration, but there is a doubt for this.
Actually we have a 4402 controller with 1120 APs both of which are marked as EoL products, we want to jump over the new 2600 APs and 5508 Controller for increase signal coverage but we have the following deals:
Last firmware for 4402 controller is 7.0
Firmware needed for 5508 to support 2600 APs is 7.3
Is it possible to configure mobility between 4402 and 5508 even with different firmware branch?
Solved! Go to Solution.
10-12-2012 09:44 AM
Table 10 lists the inter-release Controller Mobility (IRCM) compatibility matrix.
CUWN Service | 4.2.x.x | 5.0.x.x | 5.1.x.x | 6.0.x.x | 7.0.x.x | 7.2.x.x | 7.3.x.x |
---|---|---|---|---|---|---|---|
Layer 2 and Layer 3 Roaming | X | - | - | X | X | X | X |
Guest Access/Termination | X | X | X | X | X | X | X |
Rogue Detection | X | - | - | X | X | X | X |
Fast Roaming (CCKM) in a mobility group | X | - | - | X | X | X | X |
Location Services | X | - | - | X | X | X | X |
Radio Resource Management (RRM) | X | - | - | X | X | -1 | - |
Management Frame Protection (MFP) | X | - | - | X | X | X | X |
AP Failover | X | - | - | X | X | X | X |
1 In the 7.2.x.x release, RF Groups and Profiles were introduced. RRM for 7.2.x.x and later releases is not compatible with RRM for any previous release. |
__________________________________________________________________________________________
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
10-12-2012 09:42 AM
Personally,
If the locations are connected and you can roam between 2 controllers on different codes, you dont want to do that.
If you are looking for anchoring, yes its supported.
__________________________________________________________________________________________
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
10-12-2012 09:44 AM
Table 10 lists the inter-release Controller Mobility (IRCM) compatibility matrix.
CUWN Service | 4.2.x.x | 5.0.x.x | 5.1.x.x | 6.0.x.x | 7.0.x.x | 7.2.x.x | 7.3.x.x |
---|---|---|---|---|---|---|---|
Layer 2 and Layer 3 Roaming | X | - | - | X | X | X | X |
Guest Access/Termination | X | X | X | X | X | X | X |
Rogue Detection | X | - | - | X | X | X | X |
Fast Roaming (CCKM) in a mobility group | X | - | - | X | X | X | X |
Location Services | X | - | - | X | X | X | X |
Radio Resource Management (RRM) | X | - | - | X | X | -1 | - |
Management Frame Protection (MFP) | X | - | - | X | X | X | X |
AP Failover | X | - | - | X | X | X | X |
1 In the 7.2.x.x release, RF Groups and Profiles were introduced. RRM for 7.2.x.x and later releases is not compatible with RRM for any previous release. |
__________________________________________________________________________________________
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
10-14-2012 10:11 AM
It is highly recommended to Test Mobility(L2, L3 roaming) before implementing between 7.0.x.x and 7.3, Same for auto-anchor.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide