Management VLAN for APs
Feature Overview
The AP Management VLAN parameter in the AP configuration allows you to customize the VLAN settings for APs through the RUCKUS One web interface. This feature provides flexibility in network management by allowing specific VLAN configurations at the AP level. You can change the management VLAN ID from the default VLAN 1 to another VLAN from the RUCKUS One web interface, allowing AP management traffic to be routed through a VLAN other than VLAN 1.
- What is the name of the
feature? (What do users call the feature? If the feature is referred to by
an acronym, what is the acronym expansion? What is the formal name to be
used in documentation?)
Note: Typically, the name is used as part of the section titles, such as the overview title and the configuration section titles.
- Where does the feature fit within our taxonomy? (What are the taxonomy group and sub-group? This information is important for categorizing the feature documentation and incorporating it into the existing document sets.)
- What standard or standards govern the feature? (Sometimes needed.)
- Is the feature a new feature or an enhancement to an existing feature?
- Does the feature replace another feature?
- What does the feature do? (General description)
- How does the feature benefit the user?
- What set of terms do the writer and reader need to know to understand the feature and its use?
- How does the feature work? (Detailed description, if needed.)
Limitations
When an AP’s management interface VLAN is changed, it can lead to temporary disconnection from the network. The AP will need to re-establish connectivity with the network after the VLAN change. Adjust your network environment settings as described in Prerequisites to reconnect the AP. The RUCKUS One web interface provides a confirmation message about the potential disconnections so you can make informed decisions when changing the AP’s management VLAN.
After changing the AP Management VLAN, the AP will reboot automatically.
Requirements
The upper link switch that connects to the access point (AP) must be capable of handling tagged traffic. This ensures proper communication between the AP and the switch.
If there are no requirements, use the following default wording:
This feature has no special hardware or software requirements for feature enablement or usage.
If there are requirements, include the applicable below points (depending on product line):
- What releases support the
feature?
Note: Typically, this is not documented in the configuration guides; however, we need to know where to include the information.
- What hardware models support the feature?
- Does the feature require specific modules?
- Does the feature run only on certain ports?
- Does the feature have special memory requirements?
- In an integrated system, can the feature be managed or configured from another device? What are the related release and system requirements?
- Does the feature introduce new user requirements?
- Does the feature introduce physical or location-based requirements?
Considerations
When displaying VLAN IDs in the RUCKUS One web interface, the following priorities are considered:
- VLAN ID in the AP Configuration: The VLAN ID specified in the AP configuration takes precedence. This means that if you have explicitly set a VLAN ID for a specific access point (AP), it will be used for that AP.
- VLAN ID in the Venue Configuration: If the AP configuration does not specify a VLAN ID, the system will fall back to the VLAN ID defined in the venue configuration. The venue configuration provides global settings that apply to all APs within that venue.
The AP Management VLAN ID value is limited to a positive integer from 1 to 4094. The default value is 1.
If there are no considerations, use the following default wording:
This feature has no special considerations or limitations pertaining to feature enablement or usage.
If there are considerations, include the applicable below points (depending on product line).
- Does the feature replace an existing feature?
- Does the feature work only with a certain protocol or with a limited set of protocols?
- Is the feature meant to be used in combination with another feature or a set of features?
- Is the feature incompatible with any features?
- What happens when the feature is enabled?
- What happens when the feature is disabled?
- Does enabling/disabling the feature enable/disable another feature?
- What system behavior changes, if any, does the feature introduce?
- Are performance issues associated with the feature? How can these be mitigated?
Best Practices
This feature has no special recommendations for feature enablement or usage.
If there are no best practices (recommendations), use the following default wording:
This feature has no special recommendations for feature enablement or usage.
If there are considerations, include the applicable below points (depending on product line).
Prerequisites
Ensure that the corresponding VLAN is configured on the switch where the AP is connected. Also ensure that the switch port connected to the AP is set to the correct VLAN.
If there are no prerequisites, use the following default wording:
This feature has no prerequisites to feature enablement or usage.
If there are prerequisites, include the applicable below points (depending on product line).
The intention of this new template is to outline the information that you will need to collect from SMEs and provide to readers.
NOTE: Feature Configuration / Troubleshooting are *not* part of the Feature Concept template. These templates are likely to be part of separate task/reference templates (to be developed).