Scenario 1
A custom policy tag is shared between multiple sites with no site overrides and all sites are managed by the same Cisco Wireless Controller.
Site
|
Site Override
|
Policy Tag and AP Zone
|
Primary wireless controller
|
Building 1/Floor 1
|
None
|
Custom Policy Tag 1, default-zone
|
wireless controller 1
|
Building 1/Floor 2
|
None
|
Custom Policy Tag 1, default-zone
|
wireless controller 1
|
In this scenario, the custom policy tags can be shared between the sites and the APs can be successfully provisioned to these
sites using the same custom policy tag.
Scenario 2
A custom policy tag is shared between multiple sites where some sites have site overrides for SSID and all the sites are managed
by the same wireless controller.
Site
|
Site Override
|
Policy Tag and AP Zone
|
Primary wireless controller
|
Building 1/Floor 1
|
Site Override
|
Custom Policy Tag 1, default-zone
|
wireless controller 1
|
Building 1/Floor 2
|
None
|
Custom Policy Tag 1, default-zone
|
wireless controller 1
|
In this scenario, the custom policy tag cannot be reused because the same tag has two different WLAN profile and policy profile
mappings for the same SSID. If you provision APs to these sites using the same custom policy tag, a validation error occurs
during provisioning.
Note
|
The AP provisioning for the first site in this site hierarchy (Building 1/Floor 1) will be successful but a validation error is shown during the second AP provisioning at Building 1/Floor 2, which is attempting to reuse the custom policy tag.
|
Scenario 3
A custom policy tag is shared between multiple sites where some sites have site overrides for SSID and the sites are managed
by different primary wireless controllers.
Site
|
Site Override
|
Policy Tag and AP Zone
|
Primary wireless controller
|
Building 1/Floor 1
|
Site Override
|
Custom Policy Tag 1, default-zone
|
wireless controller 2
|
Building 1/Floor 2
|
None
|
Custom Policy Tag 1, default-zone
|
wireless controller 1
|
In this scenario, the custom policy tags can be reused and the APs can be successfully provisioned to these sites using the
same custom policy tag.
Scenario 4
A custom policy tag is shared between sites which have different policy profile (learned from pre-existing infrastructure)
and all the sites are managed by the same wireless controller.
Site
|
Site Override
|
Policy Profile
|
Policy Tag and AP Zone
|
Primary wireless controller
|
Building 1/Floor 1
|
None
|
Profile 1 (learned from pre-existing infrastructure)
|
Custom Policy Tag 1, default-zone
|
wireless controller 1
|
Building 1/Floor 2
|
None
|
Profile 2 (learned from pre-existing infrastructure)
|
Custom Policy Tag 1, default-zone
|
wireless controller 1
|
In this scenario, the custom policy tag cannot be reused because the same tag is mapped to two different policy profiles for
the same SSID on the same wireless controller. If you provision APs to these sites using the same custom policy tag, a validation error occurs during provisioning.
Note
|
The AP provisioning for the first site in this site hierarchy (Building 1/Floor 1) will be successful but a validation error is shown during the second AP provisioning at Building 1/Floor 2, which is attempting to reuse the custom policy tag.
|
Scenario 5
A custom policy tag is shared between multiple sites where some sites have no site overrides for the primary wireless controller and some sites have overrides for the secondary wireless controller. All the sites are managed by the same primary wireless controller and have N+1 HA configured.
Site
|
Site Override
|
Policy Tag and AP Zone
|
Primary wireless controller
|
Secondary wireless controller
|
Building 1/Floor 1
|
No Override from Global level
|
Custom Policy Tag 1, default -zone
|
wireless controller 2
|
-
|
Building 2
|
Site Override
|
Custom Policy Tag 1, default -zone
|
wireless controller 1
|
wireless controller 2
|
Building 2/Floor 1
|
No Override from Building 2
|
Custom Policy Tag 1, default -zone
|
wireless controller 1
|
wireless controller 2
|
Building 2/Floor 2
|
No Override from Building 2
|
Custom Policy Tag 1, default -zone
|
wireless controller 1
|
wireless controller 2
|
In this scenario, since all the sites are managed by the same N+1 wireless controller, the custom policy tag cannot be reused for wireless controller 2 because the same tag has two different WLAN profile and policy profile mappings for the same SSID on the same wireless controller (wireless controller 2). A validation error occurs when you provision wireless controller 2. However, there's no error expected while provisioning the wireless controller 1.
Note
|
Validation is done independently for each of the wireless controllers.
|
Scenario 6
A custom policy tag is shared across areas with the same network profile.
Site
|
Site Override
|
Policy Tag and AP Zone
|
Primary wireless controller
|
Area 1/Building 1/Floor 1
|
None
|
Custom Policy Tag 1, default-zone
|
wireless controller 1
|
Area 2/Building 2/Floor 1
|
None
|
Custom Policy Tag 1, default-zone
|
wireless controller 1 or 2
|
In this scenario, custom policy tags can be shared across wireless controllers managing different areas under the same network profile.
Scenario 7
A custom policy tag is shared across areas with multiple network profiles.
Example 1
Site
|
Network Profile
|
Site Override
|
Policy Tag and AP Zone
|
Primary wireless controller
|
Area 1/Building 1/Floor 1
|
Profile 1
|
None
|
Custom Policy Tag 1, default-zone
|
wireless controller 1
|
Area 2/Building 2/Floor 1
|
Profile 2
|
None
|
Custom Policy Tag 1, default-zone
|
wireless controller 1 or 2
|
In the above example, custom policy tag can be reused across areas with different network profiles.
Example 2
Site
|
Network Profile
|
Site Override
|
Policy Tag and AP Zone
|
Primary wireless controller
|
Area 1/Building 1/Floor 1
|
Profile 1
|
None
|
Custom Policy Tag 1, default-zone
|
wireless controller 1
|
Area 2/Building 2/Floor 1
|
Profile 2
|
Site Override in Area 2
|
Custom Policy Tag 1, default-zone
|
wireless controller 1 or 2
|
In the above example, the custom policy tag cannot be reused due to site override in Area 2.
Scenario 8
A custom policy tag is shared across multiple AP zones.
Example 1
Site
|
Site Override
|
Policy Tag and AP Zone
|
Primary wireless controller
|
Area 1/Building 1/Floor 1
|
None
|
Custom Policy Tag 1, workarea (SSID 1)
|
wireless controller 1
|
Area 2/Building 2/Floor 1
|
None
|
Custom Policy Tag 1, corridor (SSID 1)
|
wireless controller 1
|
In the above example, the same custom policy tag can be reused across two AP zones (workarea, corridor) when they have the same set of SSID (SSID 1)).
Example 2
Site
|
Site Override
|
Policy Tag and AP Zone
|
Primary wireless controller
|
Area 1/Building 1/Floor 1
|
None
|
Custom Policy Tag 1, workarea (SSID 1, SSID 2)
|
wireless controller 1
|
Area 2/Building 2/Floor 1
|
None
|
Custom Policy Tag 1, corridor (SSID 1)
|
wireless controller 1
|
In the above example, the custom policy tag cannot be reused because the AP zones do not have the same set of SSIDs.
Note
|
Reconfiguring a shared custom policy tag (for example, swapping the AP zone for a policy tag with another tag) results in
conflicting configurations for existing APs on different floors that are yet to be reprovisioned. This prevents provisioning
because the APs that are yet to be provisioned are still using the old configuration. However, reconfiguration of a shared
custom policy tag is allowed in cases where all the APs that share the tag are on the same floor. The APs are updated with
the latest configuration when you reprovision the APs of all the zones.
|