Switch Level VLAN Support

The RUCKUS One web interface supports VLAN configuration per RUCKUS ICX switch.
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.

Feature Overview

Using the Switch Level VLAN feature, you can configure VLAN settings at the switch level.

  • Allows users to create, update, and delete VLANs without forcing users to make changes in the Switch Configuration Profile
  • Applies VLAN settings to one RUCKUS ICX switch without affecting other switches

Following are the benefits:

  • User control and flexibility: Allows users to configure VLAN settings at the individual switch level. This means users have more control over the configuration of each switch, which can be beneficial in complex network environments.
  • Efficiency: Allows changes to be made directly at the switch level, saving time and resources compared to making changes at a higher level and having them propagate down to each switch.
  • Customization: Allows custom settings at the port level based on the specific switch model, providing a balance between automated management and user customization.
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

This feature has no special hardware or software requirements 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 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

This feature does not support spanning tree priority setting per VLAN from the RUCKUS One web interface.

Consider the following conditions of switch-level VLAN configuration:

  • Ports: If you change a VLAN’s status (tagged or untagged), this change will be applied to all corresponding ports. Similarly, if you change the status of a port, this change will be reflected in all VLANs that include this port. After the status update (tagged or untagged) on the ports in a VLAN, these ports become customized.
  • Link Aggregation Group (LAG) Interface: If a port is part of a LAG, you will not be able to change its tagged or untagged status in the VLAN to ensure the stability of the LAG.
  • Virtual Ethernet (VE) Interface: If a VE interface references a VE, you cannot delete that VE.

Consider the following system behavior changes for VLAN changes at the venue level:

  • If the same VLAN ID exists in the switch and the venue: The system will update the VLAN ID in the switch to match the VLAN ID of the venue. However, it will not change the tagged and untagged port settings unless the switch model matches that of the venue and the port is not marked as customized.
  • If the VLAN ID does not exist in the switch: The system will create a new VLAN in the switch with the same settings as the VLAN of the venue, except for the tagged and untagged ports. Again, the tagged and untagged port settings will only be applied if the switch model matches that of the venue and the port is not marked as customized.
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

This feature has no prerequisites to 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 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: Configuring a VLAN at the Switch Level