Sunday, September 11, 2022
HomeHealthMigrating to 6GHz - Cisco Blogs

Migrating to 6GHz – Cisco Blogs


With greater than 18 billion gadgets in use and 4.2 billion extra to be transport in 2022, the sheer dimension of present Wi-Fi deployments worldwide is simply mind-boggling. In view of the brand new Wi-Fi 6E and 6GHz adoption push, it’s important to guage what are the most effective methods to do a migration from present Cisco on-prem legacy networks into the brand new world of 6GHz deployments.

For Cisco Enterprise prospects, there are a number of features that have to be evaluated for any profitable migration planning:

  • Current controller kind:

    • is it AireOS?
    • Mannequin? (Principally, can it  run 8.5 or 8.10?)
    • is it IRCM succesful (2504/wism2 can’t do mobility to 9800)

  • Entry level Stock:

    • Are there any 802.11n fashions nonetheless in use? (per instance, 2600, 3600, 1520, 1600, and so forth)
    • Are there any Wave1 APs? (final technology of IOS, per instance 1700, 2700, 3700)
    • Mesh deployments?

  • PoE assist:

    • What’s the most supported energy normal? (802.3bt, 802.3at, and so forth)
    • Any energy budged constraints per port?
    • Or APs are powered by energy injectors?

  • Present 5GHz TX energy

    • Is my community operating on common at energy stage 3-4?
    • or it’s round 1-2?

6GHz adoption is simply supported within the Catalyst 9800 IOS-XE controllers, operating 17.7 or increased. This imposes some further issues both on controller kind migration, or about legacy entry factors which will must both be migrated, or supported by way of Inter Launch Controller Mobility (IRCM) options

Legacy APs
Determine 1. Legacy APs


Legacy Entry Factors

Over time, it has all the time been potential to do co-existence of earlier generations of entry factors with the newly launched fashions, guaranteeing each clean community upgrades and capability enlargement. Including new APs is often not a problem till we hit the situation of inter-generation gaps.

If a community that for any purpose continues to be operating gadgets 2 generations away (for instance, a 2602 AP), and now wants to incorporate new 802.11ax fashions (for instance 9130)  or soar to the  9136  for 6GHz assist, it will want extra complicated migration paths, than merely including entry factors.

When there are a number of technology gaps, if the legacy controllers can assist IRCM to the IOS-XE 9800,  it’s completely potential to design a migration plan, with out the necessity to do a “forklift” set up.  This may guarantee little or no ache to customers, and preserve the community operating till the whole lot is migrated to the brand new {hardware} and requirements

Within the following desk, we are able to see a abstract of software program assist ranges and migration choices for many entry factors fashions from 11n technology fashions:

 




















Mannequin/Sequence Final AireOS Assist IOS-XE assist IOS-XE AP equal Migration Notes
700/700W Sequence 8.10 Not supported 9105 Migration by way of IRCM
1040 8.3 Not supported 9115 AP must be changed
1260 8.3 Not supported 9115 AP must be changed
1600 8.5 Not supported 9115 Both 8.5 IRCM, or {Hardware} changed
1700 8.10 17.3 9115 Migration by way of IRCM
2700 8.10 17.3 9120 Migration by way of IRCM
3700 8.10 17.3 9130 Migration by way of IRCM
1810/1810W 8.10 As much as 17.3 9105 {Hardware} changed or IRCM between IOS-XE variations
1830/1840/1850 8.10 Supported 9105 Straight supported
AP802/AP802H 8.5 Not Supported ISR10xx Migration by way of IRCM
2600 8.5 Not Supported 9120 Migration by way of IRCM
2800/3800/4800 8.10 Supported   Straight supported
1540 8.10 Supported   Straight supported
1550 8.5 Not supported   Migration by way of IRCM
1560 8.10 Supported   Straight supported
1570 8.10 As much as 17.3   Migration by way of IRCM


For an entire checklist, you’ll be able to verify the Cisco Wi-fi Options Software program Compatibility Matrix, alternatively, you’ll be able to run the Wi-fi Config Analyzer Categorical, to verify your migration readiness

 

AP Migration Decision Flow
Determine 2. AP Migration Resolution Move


AireOS 5508
Determine 3. Legacy Controller


Legacy Controllers

Relying on the prevailing controller kind, the migration could take totally different paths. Some eventualities will probably be easy, permitting a clean transition. Others might have further steps to efficiently migrate right into a Wi-Fi 6E community

What to anticipate:

  • “Era 1” controllers: 5508, 8510. They’ll assist as much as 8.5 AireOS model, which is able to permit mobility eventualities between them and new IOS-XE 9800 controllers (Inter-release Controller Mobility, IRCM assist).  Additionally, they’ll assist  each IOS and AP-COS entry factors, from 1700 to 3800 fashions (Wave1, Wave2 802.11ac )
  • “Era 2” controllers: 5520, 8540, 3504 . All of those can assist as much as 8.10 AireOS, additionally permitting IRCM eventualities with 9800. AP assist will moreover embody 802.11ax fashions, like the brand new Catalyst 9105, 9120, and 9130. and so forth.
  • “Era 1” controllers with out IRCM: 2504, WiSM2, vWLC, 7510. No mobility is feasible between them and IOS-XE, so further steps with totally different migration eventualities are wanted

 

Controller Migration Decision Flow
Determine 4. Controller Migration Resolution Move


Migration Situations

Typically, we should always attempt to migrate “per RF blocks”, defining it as a roaming space or area the place purchasers can transfer usually between entry factors, earlier than hitting idle timeout. Principally, transfer these RF blocks utterly, into the brand new APs, and IOS-XE controllers. For instance, both transfer a constructing or a whole ground into the brand new {hardware} and software program.  We must always keep away from “salt & pepper” deployments, mixing APs on totally different controllers on the similar time. Not as a result of it isn’t supported, however as a result of mobility will probably be extra complicated, and it could result in points in the end (only a downside prevention motion)

For eventualities the place it’s not possible to interrupt the RF setting into differentiated blocks (for instance a really giant constructing like an airport, or a totally open area workplace), we should both arrange synthetic boundaries primarily based on roaming frequency and utilization or do a forklift improve

Example of RF area/building migration
Determine 5. Instance of RF space/constructing migration


What occurs if the AP mannequin will not be supported in any IRCM model?

This could possibly be the situation of a legacy controller, nonetheless working in 8.3, with some AP fashions that aren’t supported past that model. For instance, the situation of 20 APs of 2700 Sequence, and 10 APs of 1042 Sequence.

The 1040s aren’t supported in 8.5. On this case, the popular choice is to prioritize the substitute of these APs first, shifting the impacted space into 9800 as step one. Generally, prospects have combined fashions throughout a given constructing. For instance, the combo of 2700 and 2600. In these eventualities, the best choice is to consolidate fashions per supported model, shifting all APs of a given kind collectively, so they’re contained in a particular RF area  in an effort to facilitate migration in blocks

State of affairs 1: Legacy Controller helps IRCM

This would be the commonest situation, the place we now have both 8.5  (5508/8510) or 8.10 (5520/3504/8540) AireOS controller.  The migration image will begin with the creation of  IRCM setup between AireOS and 9800 controllers, then both exchange APs in RF areas connecting them to the brand new controller, permitting mobility to behave when a consumer must roam between legacy and new RF areas.

This methodology permits the sleek coexistence of each controllers, with RF areas migrated as wanted, with none in a single day switchover.

Issues to remember:

  • If the controller is proscribed to eight.5 (5508, 8510), we are going to want a particular IRCM model (8.5.182.104), to attach them to IOS-XE
  • Typically, it’s best to separate the RF community into totally different areas, configuring totally different RF group names between the legacy and IOS-XE controllers. This manner every group can do the most effective calculations that their respective model permits. We must always make it possible for “Keep away from International AP Interference” is enabled on RRM/DCA configuration (it’s by default)
  • All the time configure the first/secondary controller identify in entry factors. The brand new controllers will reject unsupported APs, but when any AP may work in each controller varieties, it will keep away from APs becoming a member of the incorrect one, or flip-flopping between them, till the migration is able to proceed

State of affairs 2: Legacy Controller not supporting IRCM

If the legacy community is operating on a controller mannequin WiSM2, 2504, 7510, vWLC, it isn’t potential to determine an IRCM connection between the outdated controller to the brand new 9800 dealing with the 6E APs. This limits considerably the choices which might be out there, and it forces a extra aggressive migration course of

Migration options:

  • Hold the 2 networks separated, and migrate bodily RF areas as new APs are added, changing the outdated ones. No roaming is feasible, and it is extremely vital to maintain consumer VLANs totally different between controllers, to keep away from ARP proxy points between each controllers. Throughout this course of, we should take care on stopping roaming occasions as consumer identification, tackle, and so forth, will probably be misplaced on the change between controller varieties.  For instance, the perfect situation is to maneuver a whole constructing from one controller to the brand new one, doing a forklift AP substitute in a single day.
  • Keep away from migrations “per ground”, as in most constructing varieties, it’s regular to see purchasers roaming between APs on totally different flooring
  • Briefly, exchange the legacy controller with one which helps IRCM

State of affairs 3: AP is supported as much as 17.3 however not in later variations

This may occur when “Wave1” APs are nonetheless current, for instance, 1700/2700/3700 AP fashions. For this sort of migration, it’s potential to maneuver all APs into IOS-XE, with the 17.3 launch, then add a secondary wlc to host the brand new Wi-Fi 6E APs, utilizing 17.9, and set up an IRCM hyperlink between each controllers.

On this feature, it’s potential to do a swish AP substitute from Wave1, into Wi-Fi 6E fashions, all the time making an attempt to do the expertise migration, per bodily roaming RF space as described (per constructing, ground, and so forth). As soon as all APs are migrated, the 17.3 controllers could be decommissioned

In some situations, the shopper could deploy a 9800-CL in 17.3 as a brief controller to host the legacy APs

6GHz RF Protection vs 5GHz. AP substitute eventualities

One frequent dialogue level is: How totally different goes to be the cell protection, in 6GHz, when in comparison with a 5GHz AP?

Individuals will wish to take a 5GHz AP and do a 1:1 substitute with a 6GHz supported AP, this may occasionally appear affordable, however there are some features to think about:

  • As WiFi-6E makes use of the next frequency, the propagation traits are totally different, the sign drops barely quicker in 6 than in 5GHz. The distinction ought to be round 2 dBm on measurements over the identical distance. Materials absorption will probably be totally different as nicely.
  • 6GHz has totally different regulatory energy constraints than 5GHz. Presently, most deployments will probably be utilizing Low Energy APs (for simplicity sake’s, let’s say 24dBm in FCC, 23 dBm in ETSI). Which means relying on the present community AP radio’s energy ranges,  utilizing 6GHz could lead to a barely decrease energy output

Rule of thumb:

  • In case your energy stage common is round 3-4, it’s potential to do a 1:1 AP substitute, and have an identical protection stage in 5 and 6 GHz
  • If the ability stage is in 1-2, then it’s possible you’ll want round 10 to twenty% further entry factors

The best option to know the common energy stage per web site is to make use of WCAE instrument and verify the “Channel Stats 5GHz” tab. This may current a abstract per channel, both at controller, or web site tag stage, of the common energy ranges (amongst different info).  For instance, it is a community the place migration to 6GHz might have further entry factors:

 

Example of site with low 5GHz coverage
Determine 6. Instance of web site with low 5GHz protection


Versus this different one, the place the deployment is operating on low energy, so becoming with out points into 6GHz necessities:

 

Example of site with good  5GHz coverage
Determine 7. Instance of web site with good 5GHz protection


For those who use the most recent model (0.9.11) of WCAE, you may as well get a “6GHz predictive” view of how the ability distribution, Close by relationships, and RSSI for purchasers would look, in case you changed your present APs with 6GHz succesful {hardware}. The instrument will match ETSI or FCC regulatory necessities, adapting powers and variations as wanted. That is helpful to get a style of how the community would look, doing a direct migration, with out including any APs.

6GHz  Predictive RRM modeling
Determine 8. 6GHz Predictive RRM modeling

For complicated or demanding deployment eventualities, the advice will all the time be: do a web site survey

 

For basic info on Wi-Fi 6E merchandise


 

Further Sources

For 6GHz troubleshooting and modeling instrument go to WCAE

Share:

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments

%d bloggers like this: