Skip navigation
Currently Being Moderated

27.5 Extended Capabilities for Cisco Devices

VERSION 4  Click to view document history
Created on: Oct 11, 2011 6:15 PM by Zenoss API - Last Modified:  Oct 11, 2011 6:28 PM by Zenoss API

 5. Extended Capabilities for Cisco Devices

 5.1. IOS

You should place Cisco devices running IOS in the /Devices/Network/Cisco device class. This lets them benefit from these extended monitoring capabilities:

  • Modeling of hardware serial number. This information can be found in the details information for Cisco IOS devices.

  • Monitoring of CPU and memory utilization. This information can be found on the Graph page for Cisco IOS devices.

  • Modeling and monitoring of IP-SLA (RTTMON). This information can be found by navigating to the device, and then selecting Cisco Details from the left panel. menu.

  • Modeling of stacked switch modules. This information can be found by navigating to the device, and then selecting Cisco Details from the left panel.

 5.2. CatOS

You should place Cisco Catalyst devices running CatOS in the /Network/Cisco/CatOS device class. The only difference in this class is that the CPU and memory performance monitoring is done by using a different configuration. Otherwise, the devices are treated the same as IOS devices.

 5.3. ASA, FWSM and PIX

You should place Cisco ASA, FWSM, and PIX devices in the /Network/Cisco/ASA device class. The only difference in this class is that the CPU and memory performance monitoring is done by using a different configuration. Otherwise, the devices are treated the same as IOS devices.

Zenoss can encounter problems when querying Cisco PIX, ASA, and FWSM devices using SNMP. This is because, by default, Zenoss tries to fit forty requests into a single SNMP packet when using SNMP v2c. This improves performance and reduces network and processing overhead on Zenoss and the monitored device.

Common symptoms of this problem include:

  • DEBUG level /Perf/Snmp events with a summary field of Error reading value for "???"

  • Missing performance graphs.

  • Errors similar to this that appear in the Cisco device log:

    incoming SNMP request (? bytes) from IP address ?.?.?.? Port ? Interface
        "inside" exceeds data buffer size, discarding this SNMP request.

 5.4. Wireless LAN Controllers

You should place Cisco Wireless LAN Controllers in the /Network/Cisco/WLC device class. This lets them benefit from the following extended monitoring capabilities:

  • Modeling of hardware model, serial number and operating system. This information can be found on the device Overview page.

  • Modeling of individual access points controller by the wireless LAN controller. This information can be found by navigating to the wireless LAN controller device, and then selecting Wireless in the left panel.

 5.5. ACE Load Balancers

You should place Cisco ACE (Application Control Engine) devices in the /Network/Cisco/ACE device class. This lets them benefit from the following extended monitoring capabilities:

  • Modeling and monitoring of individual load balanced virtual servers. This information can be found by navigating to the device, and then selecting Cisco Details in the left panel.

 5.6. Telepresence Codecs

You should place Cisco Telepresence Codec devices in the /Network/Cisco/Codec device class. This lets them benefit from the following extended monitoring capabilities:

  • Modeling of hardware model, serial number and operating system. This information can be found on the overview page for Telepresence Codec devices.

  • Modeling of all peripherals controlled by the codec. This information can be found by navigating to the Telepresence Code device, and then selecting Telepresence from the left panel.

Comments (0)