Migration of ZoneDirector AP Radio and Channel Configuration to RUCKUS One
When a ZoneDirector-managed AP is migrated
to RUCKUS One, the related AP radio and channel configuration is migrated.
General Notes for Concept Topics:
- Where does the feature fit within the taxonomy? (What is the taxonomy group and sub-group? This information is important for categorizing the feature documentation and incorporating it into the existing document sets.) This is also important in deciding where to place all conceptual topics in your publication.
- Optional sections are to be used with discretion based on the feature characteristics.
Migration Overview
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?)
- General introduction to feature
- 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? (Recommended)
- 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.)
You can view the migrated radio and channel configuration settings from the Venue and menus.
Refer to the following table to determine the scope of radio and channel configuration migration from ZoneDirector to RUCKUS One:
Migration of ZoneDirector Radio and Channel Configuration to RUCKUS One
Considerations
Only when the following options are enabled or configured in ZoneDirector, will they be migrated to RUCKUS One.
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 likely to be part of seperate task/reference templates (to be developed).