User's Guide

16. If necessary, configure the Communication Settings so what ADSP can communicate with the
device. HTTP is only used for Airwave and WLSE devices so this is not needed for Cisco devices. On
the General tab, enable data collection and enable configuration. For SNMP, set version to v2c with
proper read/write community information. Under Console tab, add the same user you have for
device access and enable password information so that ADSP can talk to the CISCO device. Now
ADSP can communicate with the CISCO device.
a. Go to Configuration > Appliance Platform > Communication Settings.
b. Select the floor.
c. Select Override settings.
d. Enter SNMP information.
e. Enter Console information.
f. Click Apply.
17. Verify that changes made to your applicable profiles are now being pushed out to the Cisco device.
The relay server should have a copy of the rendered profile and it should match what is on the Cisco
device.
• A simple test to verify changes are being pushed to the is to change the WLAN profile that is
applied to the AP. This change will be immediately pushed if everything is working.
• A console connection can be used to watch the profile being pushed to the AP.
• Checking the relay server ftp/tftp root directory will allow you to look at the configuration that is
rendered and pushed to the device.
• Looking at /usr/local/smx/log/device-mgmt.log, you can watch as the server configures the
device.
• Alarms will be present if the configuration is incomplete.
• Alarms will be present if the Relay server cannot be reached.
Changes are pushed immediately to the device in the following circumstances:
• The device is managed already and something in its profile changes.
• The device is moved to another location that is configured.
Changes are NOT pushed when a device is discovered; this will happen during polling.
CLI Variable Scenarios
When making changes to CLI on a device the following occurs:
• If the value for the variable is an empty string (no spaces, new lines, tabs, text, anything), then the
variable is not saved for the CLI Variable Profile.
• If the variable value is populated, it will be saved.
When sending variables to the device or displaying variables in the GUI, the CLI Profile variables and
CLIVars Profile variables are merged (with CLIVars Profile variables taking precedence).
Scenario A
ProfileX is defined at the folder level as follows:
1. HOSTNAME=Test-Hostname
2. GATEWAY=172.17.1.1
Configuration
Examples Configuration Tab
732 Extreme AirDefense User Guide for version 10.5.