CISCO Device Example

Note

Note

You must configure the Appliance Platform before configuring Infrastructure Management.

For this example, a CISCO device and a static IP address are used.

  1. This is critical for Cisco AP ADSP Management. Validate supported firmware: Cisco 1230 Thick AP 12.3.8-JEC2(ED) or Cisco 1130 Thick AP 12.4-10b(JDA).
  2. Collect all the passwords on the device to be managed. For example, for a Cisco device, you need the enable password and a login.
  3. Enable SSH/Telnet if it is not enabled on the Cisco device.
  4. Make sure that Cisco devices have at least a RSA modulus of 768 bits or higher or your server will not talk to it via SSH.
  5. Make sure that you have a supported TFTP or FTP server set up so that both the ADSP and the managed device 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.
  6. 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 device. To verify SNMP connectivity, from the server, run the following command against your target device: snmpwalk -v2c -c <community string> <IP Addr>.
  7. Add a CLI profile using the default Cisco Autonomous 12x0/11x0 device type (or other device type) as a template.
    1. Go to Configuration > Infrastructure Management > CLI Configuration.
    2. Select Cisco Autonomous 12x01/11x0 from the CLI Configuration drop-down menu.
    3. Click the New Profile button.
    4. Enter a name for your profile.
    5. Update the CLI commands, if necessary.
    6. Click OK. Your newly created profile should now be available in the list of profiles.
    7. Select a floor for the device.
      Note

      Note

      The floor should already exist. If it does not, use tree setup to create it (Configuration > Appliance Platform > Tree Setup).
    8. Select Override settings.
    9. Select your newly created profile by clicking its radio button.
      Note

      Note

      If your profile is the only available profile, it will be selected automatically.
    10. 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.

  8. Create a Channels profile and apply it to the floor the device is placed as follows:
    1. Go to Configuration > Infrastructure Management > Channel Settings.
    2. Select the floor.
    3. Select Override settings.
    4. Select the proper settings.
    5. Click Apply.
  9. Configure Device Access as follows:
    1. Go to Configuration > Infrastructure Management > Device Access.
    2. Select the floor.
    3. Select Override settings.
    4. Enter the enable password for Cisco (Cisco).
    5. Enter the User ID (Cisco) and Password (Cisco).
    6. Go to the Interfaces tab.
    7. Enable SSH.
    8. Enable SNMP and enter passwords for the Read/Write community. Then, enter password for a Trap Destination including your server IP address.
      Note

      Note

      You must also add the Trap Community and destination to get traps on your server. This can be done from the server CLI: ADSPadmin > Config > SNMP Enable.
    9. Click Apply.
  10. Ensure that the device firmware is current. (Configuration > Infrastructure Management > Device Firmware). If firmware is not current, update it.
  11. Create a Radio Settings configuration for the device and apply it to the floor the device is placed. You must include some data rates.
    1. Go to Configuration > Infrastructure Management > Radio Settings.
    2. Select the floor.
    3. Select Override settings.
    4. Select the proper settings.
    5. Click Apply.
  12. Configure RF-Domain and apply to by selecting the scope where the floor is placed on as follows:
    1. Go to Configuration > Infrastructure Management > RF-Domain.
    2. Select the floor.
    3. Select Override settings.
    4. Enter RF-Domain information.
    5. Click Apply.
  13. Create WLAN profile and apply it by associating the profile with the location that contains the managed device.
    1. Go to Configuration > Infrastructure Management > WLAN Profiles.
    2. Click New Profile.
    3. Enter information for the WLAN Profile in the General and Security tabs.
    4. Click OK.
    5. Ensure that the appliance is selected in the network tree and select Enable configuration.
    6. Select the floor.
    7. Select Override settings.
    8. Select the WLAN Profile.
    9. Click Apply.

    The profile is now complete but ADSP cannot communicate with the Cisco device.

  14. If you have not already done so during the Appliance Platform configuration, import the device into your network using SNMP discovery using a single IP address. This can be done with Configuration > Appliance Platform > Import/Discover Devices.
    Note

    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.
  15. Set automatic status polling and automatic data collection for 3 minutes, and turn on automatic configuration correction (Configuration > Appliance Platform > Polling).
  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.
    1. Go to Configuration > Appliance Platform > Communication Settings.
    2. Select the floor.
    3. Select Override settings.
    4. Enter SNMP information.
    5. Enter Console information.
    6. 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.

9037079-00