Smart Monitor
Feature Overview
- 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.)
The Smart Monitor feature regularly monitors the uplink connectivity status of RUCKUS APs, whether connected through an Ethernet port or STA WLAN. Based on the default gateway reachability, Smart Monitor manages the WLANs on a per-venue and per-AP basis as follows:
- Enables WLAN automatically when the AP default gateway is reachable
- Configures heartbeat interval and sets the maximum number of retries (before considering a connection is lost)
- Disables WLAN automatically when the AP default gateway is unreachable
Smart Monitor provides the following benefits:
Requirements
This feature has no special hardware or software requirements for feature enablement or usage.
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
- Smart Monitor uses
arpingto periodically check the AP connectivity to the default gateway. If it does not receive any response after the set number of retries, then Smart Monitor disables the WLANs. By default, Smart Monitor is set to OFF at both the venue and AP levels. - Before Smart Monitor is configured at the AP level, an AP uses the Smart Monitor configuration set at the venue level. You can override the venue settings by enabling Smart Monitor at the AP level and configuring the Heartbeat Interval and Max Retries fields.
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
This feature has no prerequisites to feature enablement or usage.
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 seperate task/reference templates (to be developed).