![Note](images/note.png)
Note
You must configure the Appliance
Platform before configuring Infrastructure Management.
For this example, the AP7131 and a static IP address are used.
-
Collect all the passwords for
the AP7131 to be managed.
-
Enable SSH/Telnet if it is not
enabled on the AP7131.
-
Make sure that you have a
supported TFTP or FTP server set up so that both the ADSP and the managed
AP-7131 can reach it. ADSP recommends FTP:IIS Win2k and TFTP 3C Daemon. Both
methods have to allow for overwriting the configuration file because when a
configuration is changed, the server creates a new file with the same name and
will again push it to the relay server.
-
Enable SNMP on the device and
verify that you can execute snmpwalk from the server. You will need the IP
address and community string for the AP7131. To verify SNMP connectivity, from
the server, run the following command against your target device: snmpwalk -v2c
-c <community string> <IP Addr>.
-
Add a CLI profile using the
default AP7131 device type (or other device type) as a template and apply the
profile to the floor the device is located on.
- Go to .
- Select WiNG v5.x
from the CLI
Configuration drop-down menu.
- Select a floor for the
device.
![Note](images/note.png)
Note
The floor
should already exist. If it does not, use tree setup to create it
().
- Select Override
settings.
- Select your newly
created profile by clicking its radio button.
![Note](images/note.png)
Note
If your profile is
the only available profile, it will be selected
automatically.
- Click Apply.
Since the profile is incomplete right now, the system will not apply it. Only
complete profiles are delivered to the device. So, in this example, the full
set of profiles will not be applied until the very last step. When
Device
Access and Communication
Settings are configured and have a valid relay server set up
and running, the profile will be applied. The device-mgmt.log
file in /usr/local/smx/log can be used to verify what is going
on.
-
Create a Channels profile and
apply it to the floor the AP-7131 is placed on as follows:
![Note](images/note.png)
Note
ADSP automatically sets up
a default Channels profile. Only follow these steps, if you want to use your
own settings.
- Go to .
- Select the floor.
- Select Override
settings.
- Select the proper
settings.
- Click Apply.
-
Configure Device Access as
follows:
- Go to
- Select the floor.
- Select Override
settings.
- Enter the User ID and
Password.
- Go to the Interfaces tab.
- Enable SSH.
- Enable SNMP and enter
passwords for the Read/Write community. Then, enter password for a Trap
Destination including your server IP address.
![Note](images/note.png)
Note
You must also add the
Trap Community and destination to get traps on your server. This can
be done from the server CLI: .
- Click Apply.
-
Ensure that the device firmware
is current. (). If firmware is not current, update it.
-
Create a Radio Settings
configuration for the AP-7131 and apply it to the floor the device is placed.
You must include some data rates.
![Note](images/note.png)
Note
ADSP automatically sets up
a default Radio Settings profile. Only follow these steps, if you want to
use your own settings.
- Go to
- Select the floor.
- Select Override
settings.
- Select the proper
settings.
- Click Apply.
-
Configure RF-Domain and apply
to by selecting the scope where the floor the AP-7131 is placed as follows:
- Go to .
- Select the floor.
- Select Override
settings.
- Enter RF-Domain
information.
- Click Apply.
-
Create WLAN profile and apply
it by associating the profile with the location that contains the managed
device.
- Go to .
- Click New Profile.
- Enter information for
the WLAN Profile in the General
and Security tabs.
- Click OK.
- Ensure that the
appliance is selected in the network tree and select Enable
configuration.
- Select the floor.
- Select Override
settings.
- Select the WLAN Profile.
- Click Apply.
The profile is now complete but ADSP cannot communicate with the
AP-7131.
-
If you have not already done so
during the Platform configuration, import the AP-7131 into your network using
SNMP discovery using a single IP address. This can be done with .
![Note](images/note.png)
Note
Select SNMP discovery with a
target folder of a floor created in the Appliance Platform configuration.
You can use the
Device Import Rules or manually select the
floor.
-
Set automatic status polling
and automatic data collection for 3 minutes, and turn on automatic configuration
correction ().
-
If necessary, configure the
Communication Settings so that ADSP can communicate with the AP-7131. HTTP is
only used for Airwave and WLSE devices so this is not needed for the AP-7131. In
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 AP-7131 . Now ADSP can
communicate with the AP-7131.
- Go to .
- Select the floor.
- Select Override
settings.
- Enter SNMP information.
- Enter Console
information.
- Click Apply.
-
Verify that changes made to
your applicable profiles are now being pushed out to the AP-7131. The relay
server should have a copy of the rendered profile and it should match what is on
the AP-7131.
- A simple test to verify
changes are being pushed to the AP-7131 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-7131.
- Checking the relay server
ftp/tftp root directory will allow you to look at the configuration that
is rendered and pushed to the AP-7131.
- Looking at the in
i
, you can watch as the server
configures the AP-7131.
- 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 AP-7131 in the following
circumstances:
- The is managed already
and something in its profile changes.
- The is moved to another
location that is configured.
Changes are NOT pushed when a device is discovered; this will happen during
polling.