Anchor Group
Location in GUI: Design » Network Settings » Wireless » Anchor Groups
Diagram
Section titled “Diagram”Classes
Section titled “Classes”wireless (catalyst_center)
Section titled “wireless (catalyst_center)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| anchor_groups | List | [anchor_groups] | No |
anchor_groups (catalyst_center.wireless)
Section titled “anchor_groups (catalyst_center.wireless)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | max: 32 | Yes | |
| mobility_anchors | List | [mobility_anchors] | Yes |
mobility_anchors (catalyst_center.wireless.anchor_groups)
Section titled “mobility_anchors (catalyst_center.wireless.anchor_groups)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| device_name | String | Yes | ||
| ip_address | IP | Yes | ||
| anchor_priority | Choice | PRIMARY, SECONDARY, TERTIARY | Yes | |
| managed_anchor_wlc | Boolean | true, false | Yes | |
| peer_device_type | Choice | IOS-XE, AIREOS | No | |
| mac_address | String | No | ||
| mobility_group_name | String | max: 31 | No | |
| private_ip | IP | No |
Anchor Groups are used in non-SDA-fabric (traditional/FlexConnect) deployments for guest traffic tunneling via the foreign-anchor WLC architecture. In SDA fabric deployments, guest traffic is handled natively by the fabric and anchor groups are not needed. Anchor Groups are referenced by Wireless Profiles via the anchor_group_name field in ssid_details — see Wireless Network Profiles.
Examples
Section titled “Examples”Example 1: Anchor group with a single managed anchor WLC (controller managed by Catalyst Center):
catalyst_center: wireless: anchor_groups: - name: AG_Guest mobility_anchors: - device_name: C9800-CL-WLC ip_address: 10.0.0.1 anchor_priority: PRIMARY managed_anchor_wlc: trueExample 2: Anchor group with multiple managed anchors for redundancy:
catalyst_center: wireless: anchor_groups: - name: AG_Guest_HA mobility_anchors: - device_name: WLC-ANCHOR-1 ip_address: 10.0.0.1 anchor_priority: PRIMARY managed_anchor_wlc: true - device_name: WLC-ANCHOR-2 ip_address: 10.0.0.2 anchor_priority: SECONDARY managed_anchor_wlc: trueExample 3: Anchor group with an external (unmanaged) anchor WLC requiring additional mobility fields:
catalyst_center: wireless: anchor_groups: - name: AG_External mobility_anchors: - device_name: EXT-WLC-ANCHOR ip_address: 172.16.0.1 anchor_priority: PRIMARY managed_anchor_wlc: false peer_device_type: IOS-XE mac_address: "aa:bb:cc:00:00:01" mobility_group_name: defaultNote: Anchor groups support up to 3 mobility anchors per group. When
managed_anchor_wlcisfalse(external anchor), the fieldspeer_device_type,mac_address, andmobility_group_nameare required by the API. For managed anchors, thedevice_namecan be the short hostname — the module automatically resolves it to the FQDN from the Catalyst Center inventory.