AP Management VLAN at the Venue Level

You can configure all the APs within a specific venue to utilize the same AP Management VLAN setting. By default, the AP management VLAN ID for a venue is set to 1.
To provide an overview of a feature and its benefits. May require several Concept topics to keep content in short, manageable, and reusable chunks of content.

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 seperate task/reference templates (to be developed).

General Notes for Concept Topics:
  • Optional sections are to be used with discretion based on the feature characteristics.

Overview

The AP Management VLAN setting allows users to use the same AP Management VLAN at the venue level.

  • Overwrites or modifies the AP management VLAN settings for all APs associated with an existing venue.
    Note: The configuration setting at the venue level applies only to the APs using venue setting specific to this venue.
  • Displays a confirmation message whenever the AP management VLAN ID on a specific venue is changed.
  • Displays a confirmation message whenever an AP is moved to a venue with a different AP management VLAN ID.
  • Displays the Management VLAN column for all APs in the AP List table (by default, this column is hidden).
This section is required. Providing detailed and accurate information in the feature overview is crucial as it helps users understand the functionality, benefits, and usage of the feature. Moreover, it ensures consistency in communication across all platforms, enhancing user experience and product perception.
  • 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.)

Requirements

The uplink switch connected to the AP must be capable of identifying and forwarding VLAN-tagged traffic.

This section is required. Including this section, even when there is no impact, lets SMEs and customers know that the associated information was not forgotten.

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

  • Changing the AP management VLAN setting may lead to possible network disconnections as altering the VLAN can impact the network path. It is the customers’ responsibility to correctly adjust their own network environment settings in order to reconnect the APs. The RUCKUS One web interface displays a confirmation message to let users know about the possible disconnections when they attempt to change AP management VLAN on a specific venue.
  • Moving an AP to a target venue that has different AP management VLAN setting may also result in APs getting disconnected from the network. It is the customers’ responsibility to correctly adjust their own network environment settings in order to reconnect the APs. The RUCKUS One web interface displays a confirmation message to let users know about the possible disconnections before changing the AP venue.
  • AP Management VLAN ID value is limited to a positive integer between 1 through 4094. The default value is 1.

Here are the system behaviors for both existing and new venues, as well as existing and new APs:

  • Existing Venue: A venue created in the RUCKUS One web interface prior to the release of the "AP Management VLAN at the Venue Level" feature. In the existing venues, there is no change to the AP's Management VLAN setting. The existing venue will transition into a fully functional new venue only if the user modifies the AP Management VLAN settings of the current venue from the RUCKUS One web interface.
  • New Venue: A venue created in the RUCKUS One web interface after the release of the "AP Management VLAN at the Venue Level" feature. The management VLAN across the entire venue defaults to a value of 1, and the APs associated with this new venue will automatically inherit the VLAN setting of the venue.
  • Existing AP: An AP added using the RUCKUS One web interface prior to the release of the "AP Management VLAN at the Venue Level" feature. If an AP already has a custom VLAN that was configured using the AP CLI, then RUCKUS One will honor and utilize the customized AP-level management VLAN. The existing AP will transition into a fully functional new AP only if the user modifies the AP Management VLAN settings of the current AP from the RUCKUS One web interface.
  • New AP: An AP added using the RUCKUS One web interface after the release of the "AP Management VLAN at the Venue Level" feature. The new AP will inherit the Management VLAN setting of the venue.
  • If an AP with a specific VLAN configured is moved to a new venue, the AP will align to the AP Management VLAN configuration of the new venue.

Case 1: AP Using Venue Setting

Target Venue Existing Venue New Venue
Existing AP Align to venue setting Align to venue setting
New AP Align to venue setting Align to venue setting

Case 2: AP Using Custom Setting

Target Venue Existing Venue New Venue
Existing AP No change, retains customized AP setting Align to venue setting
New AP Align to venue setting Align to venue setting
This section is required. Including this section, even when there is no impact, lets SMEs and customers know that the associated information was not forgotten.

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).

Note: A separate section on Limitations may sometimes be needed.
  • 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.

This section is required. Including this section, even when there is no impact, lets SMEs and customers know that the associated information was not forgotten.

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).

  • Brief list of RUCKUS recommendations on product use to optimize performance.

Prerequisites

Ensure that the corresponding VLAN is configured on all switches connected to all APs in the venue. Also, verify that the switch ports connected to all the APs are set to the correct VLAN.

This section is required. Including this section, even when there is no impact, lets SMEs and customers know that the associated information was not forgotten.

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).

Note: This section is sometimes part of a general overview and sometimes part of a configuration overview.
  • What are the task prerequisites that the user must ensure are met,for configuration? (For example, must you be running certain protocols, or must you configure other features first?)
Parent topic: Advanced Settings