Specifications

My Network Configuration
Extreme Networks Wireless Management Suite Reference Guide74
● Templates on page 80
● Backup Restore on page 87
Compliance
Compliance is achieved by detecting device configuration changes and alerting the WMS about the
configuration deviation from the last WMS saved configuration.
NOTE
Device compliance checks can be conducted on multiple devices simultaneously, instead of just a single device at a
time
A controller has two default configurations: A Saved Config and Running Config. The Saved Config
resides in a controller persistent file within the controller’s file system.The controller runs with the
Saved Config after a restart. The Running Config resides in controller memory. The Running Config is
equal to the Saved Config just after a restart. Any changes made to the Running Config are lost in the
event of a controller restart (if changes are not saved).
A WMS saved configuration is the master (or desired) config for a controller. The WMS compliance
mechanism looks for changes in the controller’s Running Config or Saved Config with respect to the
WMS saved config.
After a configuration update is conducted using WMS, the controller’s Saved Config is retrieved and
stored as a WMS saved config. For a newly discovered controller, the Saved Config is retrieved and
saved as an initial WMS configuration.
NOTE
Compliance checks can be conducted immediately (see “Checking a Device’s Compliance Now” on page 76) or
automatically, as WMS checks for device compliance every 4 hours
To display device compliance attributes and assess a device’s compliance:
1 Select the Configuration tab from within the My Networks menu item.
The Compliance tab displays by default.