wireless tag site [name]
Creates or modifies a site tag for wireless networks, used to group APs by physical location for policy and RF management.
Definition: wireless tag site [name] is a Cisco IOS global config command. Creates or modifies a site tag for wireless networks, used to group APs by physical location for policy and RF management.
Overview
The `wireless tag site [name]` command in Cisco IOS global configuration mode creates or modifies a site tag for wireless networks. Site tags are used to group access points (APs) by physical location, enabling location-specific policies and RF management. This command is essential for large-scale wireless deployments where APs are distributed across multiple buildings, floors, or campuses.
By assigning a site tag to an AP, network administrators can apply unique configurations such as RF profiles, load balancing, and client roaming settings based on the AP's physical location. The concept behind site tags is rooted in the need for hierarchical policy management in wireless networks. Instead of configuring each AP individually, site tags allow grouping APs that share similar characteristics (e.g., same building, same floor) and applying policies at the group level.
This simplifies configuration, reduces errors, and ensures consistency. You would reach for this command when designing a wireless network with multiple physical locations, such as a university campus or a multi-site enterprise. Alternatives include using AP groups or flex connect groups, but site tags are more granular and integrate with Cisco's RF management and location services.
In the broader workflow, site tags are typically created before APs are deployed, and then APs are associated with the tag during provisioning. The command operates in global configuration mode and requires privilege level 15. It modifies the running configuration immediately; changes are saved to the startup configuration with `write memory`.
There is no buffered output; the command executes silently. Understanding site tags is critical for CCNA and CCNP candidates as they appear in wireless network design and troubleshooting scenarios.
wireless tag site [name]When to Use This Command
- Assigning a site tag to APs in a branch office to apply specific RF profiles and WLANs.
- Creating a site tag for a campus building to separate guest and corporate traffic.
- Configuring a site tag for an outdoor area to use different channel settings.
- Deploying a site tag for a temporary event space with custom SSID policies.
Parameters
| Parameter | Syntax | Description |
|---|---|---|
| name | WORD (1-32 characters) | Specifies the name of the site tag. The name can be up to 32 characters, alphanumeric and hyphens/underscores allowed. Common mistake: using spaces or special characters that are not supported. The name should be descriptive of the physical location, e.g., 'Building-A-3rd-Floor'. |
Command Examples
Create a site tag for a branch office
wireless tag site branch-officeWARNING: Site tag 'branch-office' has been created but not applied to any APs. Apply the site tag to APs using 'ap site-tag <tag>' in AP profile configuration.
The command creates a site tag named 'branch-office'. The warning reminds you to apply it to APs. No output fields beyond the warning.
Modify an existing site tag with description
wireless tag site campus-building
description "Main campus building - 5GHz only"Site tag 'campus-building' updated with description 'Main campus building - 5GHz only'.
The first line enters site tag configuration mode for 'campus-building'. The description command adds a human-readable note. Output confirms the update.
Understanding the Output
The command itself does not produce a table output; it only returns a confirmation or warning message. The key output is the warning that the site tag must be applied to APs using 'ap site-tag' in AP profile configuration. To verify site tags, use 'show wireless tag site summary' or 'show wireless tag site detailed <name>'.
In those outputs, look for the site tag name, description, and associated APs. Good values: site tags are applied to APs and match the intended location. Bad values: site tags exist but are not applied to any APs, causing APs to use default settings.
Configuration Scenarios
Creating a site tag for a campus building
A university has multiple buildings on campus. APs in the Science Building need a specific RF profile and client load balancing policy. Create a site tag 'Science-Building' to group these APs.
Topology
WLC (Management) --- Network --- APs (Science Building)Steps
- 1.Step 1: Enter global configuration mode: configure terminal
- 2.Step 2: Create the site tag: wireless tag site Science-Building
- 3.Step 3: (Optional) Configure RF profile for this site: wireless rf-profile Science-RF site-tag Science-Building
- 4.Step 4: (Optional) Apply load balancing policy: wireless client load-balancing aggressive site-tag Science-Building
- 5.Step 5: Exit configuration mode: end
- 6.Step 6: Save configuration: write memory
! Create site tag configure terminal wireless tag site Science-Building ! Associate RF profile wireless rf-profile Science-RF site-tag Science-Building ! Apply aggressive load balancing wireless client load-balancing aggressive site-tag Science-Building end write memory
Verify: Use 'show wireless tag site summary' to verify the site tag exists. Expected output includes the tag name and associated policies.
Watch out: Forgetting to apply the site tag to APs. The tag itself does nothing until APs are assigned to it via the AP profile or manually.
Modifying an existing site tag for a multi-floor building
A company has a building with three floors. Initially, all APs were tagged 'Main-Office'. Now, they need separate tags per floor for better RF management. Modify the existing tag to 'Floor-1' and create new tags for floors 2 and 3.
Topology
WLC --- APs (Floor 1, 2, 3)Steps
- 1.Step 1: Enter global configuration mode: configure terminal
- 2.Step 2: Modify existing site tag: wireless tag site Floor-1
- 3.Step 3: Create new tags: wireless tag site Floor-2 and wireless tag site Floor-3
- 4.Step 4: Assign APs to new tags via AP join profile or manually: ap name AP-Floor-1 site-tag Floor-1
- 5.Step 5: Exit and save: end; write memory
! Modify existing and create new site tags configure terminal wireless tag site Floor-1 wireless tag site Floor-2 wireless tag site Floor-3 ! Assign APs to site tags ap name AP-Floor-1 site-tag Floor-1 ap name AP-Floor-2 site-tag Floor-2 ap name AP-Floor-3 site-tag Floor-3 end write memory
Verify: Use 'show ap name AP-Floor-1 config general' to verify the site tag assignment. Expected output shows 'Site Tag: Floor-1'.
Watch out: Changing a site tag name does not automatically update AP assignments. You must reassign APs to the new tag.
Troubleshooting with This Command
When troubleshooting site tag issues, the first step is to verify that the site tag exists and is correctly configured. Use `show wireless tag site summary` to list all site tags. Healthy output shows each tag with its name and any associated policies.
If a tag is missing, it may not have been created or was accidentally deleted. Next, check AP assignments with `show ap summary` or `show ap name <ap-name> config general`. The site tag should appear in the AP configuration.
If an AP shows a different tag or no tag, it may have been misconfigured or defaulted to the global tag. Common symptoms include APs not applying the correct RF profile or client policies. For example, if clients on the 3rd floor are not getting the expected load balancing, verify that the APs on that floor have the correct site tag.
Use `show ap name <ap-name> rf-profile` to confirm the RF profile associated with the site tag. Another diagnostic flow: if APs fail to join the controller, check if the site tag is valid and if the AP's credentials match. Use `debug ap join` to see join errors.
Correlate site tag issues with `show wireless client summary` to see if clients are associating with the correct APs. If a site tag is deleted, APs assigned to it will revert to the default tag, which may cause policy mismatches. Always verify after changes with `show running-config | include wireless tag site`.
In summary, focus on tag existence, AP assignment, and policy application. Use show commands to isolate the problem and debug commands for real-time issues.
CCNA Exam Tips
CCNA exam may ask which command creates a site tag: answer is 'wireless tag site [name]' in global config.
Remember that site tags are applied to APs via 'ap site-tag' under the AP profile, not directly on the AP interface.
Site tags are used to group APs for RF profiles and WLAN policies; know that each AP can have only one site tag.
The exam might test that site tags must be created before they can be assigned to APs.
Common Mistakes
Mistake: Trying to apply a site tag directly to an AP interface instead of using 'ap site-tag' under AP profile.
Mistake: Forgetting to create the site tag before referencing it in AP profile configuration, causing an error.
Mistake: Using spaces in site tag names without quotes, which breaks the command syntax.
wireless tag site [name] vs ap dot11 24ghz [setting]
Both `wireless tag site` and `ap dot11 24ghz` are global configuration commands that influence wireless AP behavior, but they operate at different layers: the former defines logical grouping for policy and RF management, while the latter directly tunes physical radio parameters. Engineers often confuse them because both are entered in global config and affect AP operations, yet their purposes and scopes are distinct.
| Aspect | wireless tag site [name] | ap dot11 24ghz [setting] |
|---|---|---|
| Scope | Creates or modifies a site tag for grouping APs by location | Configures 2.4 GHz radio settings (channel, power, enable/disable) |
| Configuration Mode | Global config; defines a tag object | Global config; sets default radio parameters for all APs |
| Persistence | Tag persists in config until removed | Settings persist but can be overridden per-AP |
| Precedence | Applied by associating tag to AP via `ap site-tag` | Applies as default unless per-AP override exists |
| Typical Use | Grouping APs by physical location for policy/RF profiles | Setting default channel, power, or disabling 2.4 GHz radio |
| Effect | Influences AP-to-controller mapping and policy assignment | Directly controls radio transmission parameters |
Use wireless tag site [name] when you need to create a logical grouping of APs based on physical location to apply site-specific policies or RF profiles.
Use ap dot11 24ghz [setting] when you need to configure default 2.4 GHz radio parameters such as channel assignment, power level, or radio shutdown for all APs.
Platform Notes
In IOS-XE (e.g., Catalyst 9800 series), the command syntax is identical: `wireless tag site <name>`. However, the output of show commands may differ slightly; for example, `show wireless tag site summary` provides more detailed information in IOS-XE, including the number of APs assigned. In NX-OS (e.g., Cisco 5500 series controllers), the equivalent command is `site-tag <name>` under the wireless configuration mode.
Note that NX-OS uses a different hierarchy; you must enter `configure terminal` then `wireless` to access wireless commands. For ASA, there is no direct equivalent as ASAs are firewalls, not wireless controllers. In older IOS versions (12.x, 15.x) on standalone APs or older WLCs (e.g., 2504), the command may not exist; instead, AP groups were used.
The command is available in IOS-XE 16.x and later. For IOS-XR, wireless is not supported. Always check the specific platform documentation as syntax and capabilities may vary.
Practice for the CCNA 200-301
Test your knowledge with practice questions covering all CCNA 200-301 exam domains.
Practice CCNA 200-301 Questions