ZenPacks

Cisco Monitor ZenPack

This ZenPack provides status and performance monitoring of Cisco routers and switches.

Releases

Version 5.8.1-Download
Released on 2017/06/08
Requires PythonCollector ZenPack, ZenPackLib ZenPack

Compatible with Zenoss Resource Manager 4.2.x, Zenoss Resource Manager 5.0.x, Zenoss Resource Manager 5.1.x, and Zenoss Resource Manager 5.2.x

Version 5.8.0-Download
Released on 2017/04/21
Requires PythonCollector ZenPack, ZenPackLib ZenPack

Compatible with Zenoss Resource Manager 4.2.x, Zenoss Resource Manager 5.0.x, Zenoss Resource Manager 5.1.x, and Zenoss Resource Manager 5.2.x

Version 5.7.3-Download
Released on 2016/11/11
Requires PythonCollector ZenPack

Compatible with Zenoss Resource Manager 4.2.x, Zenoss Resource Manager 5.0.x, and Zenoss Resource Manager 5.1.x

Version 5.6.3-Download
Released on 2016/03/11
Requires PythonCollector ZenPack

Compatible with Zenoss Resource Manager 4.2.x, Zenoss Resource Manager 5.0.x

Contents

Background

The CiscoMonitor ZenPack extends Zenoss Service Dynamics to provide additional support for monitoring faults and performance of a wide range of Cisco equipment, including virtual resources such as virtual firewalls, virtual load balancers, and virtual extensible LANs.

Features

Monitoring is supported for the following Cisco product lines.

  • Catalyst 2960 Series Switches
  • Catalyst 6500 Series Switches
  • Catalyst 6500 Series Virtual Switching Systems (VSS)
  • Application Control Engine (ACE) Modules for Catalyst 6500 Series
  • Firewall Services Modules (FWSM) for Catalyst 6500 Series
  • ASA Services Modules (ASA-SM) for Catalyst 6500 Series
  • ASA 5500 Series Adaptive Security Appliances
  • ASA 1000V Cloud Firewalls
  • Nexus 9000 Series Switches
  • Nexus 7000 Series Switches
  • Nexus 6000 Series Switches
  • Nexus 5000 Series Switches
  • Nexus 3000 Series Switches
  • Nexus 2000 Series Fabric Extenders
  • Nexus 1010 Series Virtual Services Appliances
  • Nexus 1000v Series Switches
  • Virtual Security Gateway (VSG) for Nexus 1000v Series Switches
  • ASR 9000 Series Aggregation Services Routers
  • ASR 1000 Series Aggregation Services Routers
  • CSR 1000V Cloud Services Routers
  • MDS 9000 Series Multilayer Switches
  • Wireless LAN Controllers (WLC)
  • TelePresence Codecs

The following common features are available across the supported products where available.

Discovery

  • Chassis
  • Supervisor Modules
  • Line Cards
  • Power Supplies
  • Fans
  • Temperature Sensors
  • Physical Ports and Interfaces
  • Port Channels and Bundles
  • Other Logical Interfaces
  • VLANs
  • VRFs
  • QoS Class Maps

Monitoring

  • Event collection from syslog and SNMP traps
  • CPU and memory utilization for chassis and supervisor modules
  • Memory buffer pool monitoring (optional)
  • Power consumption and status for chassis and FRUs
  • Power available and drawn for power supplies
  • Temperature for temperature sensors
  • Interface utilization, throughput, error rate and status for all physical Ethernet interfaces
  • Interface utilization, throughput and status for all logical Ethernet interfaces
  • Throughput and status for VLANs

Additional Features

The following additional features are supported for specific product lines:

Catalyst 6500 Features

  • Discovery and monitoring of virtual switching system (VSS)
  • Discovery and monitoring of service modules

ACE Features

  • Discovery and monitoring of virtual contexts
  • Discovery and monitoring of service policies
  • Discovery and monitoring of server farms
  • Discovery and monitoring of real servers

FWSM Features

  • Discovery and monitoring of security contexts
  • Discovery and monitoring of L4/L7 resources

Nexus 9000 Features

  • Discovery and monitoring of fabric cards
  • Discovery and monitoring of virtual device contexts (VDCs)
  • Discovery and monitoring of VXLAN Network Identifiers (VNIs)
  • Discovery and monitoring of Network Virtualization Endpoints (VNEs)

Nexus 7000 Features

  • Discovery and monitoring of fabric cards
  • Discovery and monitoring of virtual device contexts (VDCs)

Nexus 6000 Features

  • Discovery and monitoring of fabric extenders
  • Discovery and monitoring of virtual device contexts (VDCs)
  • Discovery and monitoring of fibre-channel ports
  • Discovery and monitoring of VSANs
  • Discovery and monitoring of storage zones
  • Discovery and monitoring of storage zone sets

Nexus 5000 Features

  • Discovery and monitoring of Nexus 2000 fabric extenders
  • Discovery and monitoring of fibre-channel ports
  • Discovery and monitoring of VSANs
  • Discovery and monitoring of storage zones
  • Discovery and monitoring of storage zone sets

Nexus 1010 Features

  • Discovery and monitoring of virtual services blades.

Nexus 1000V Features

  • Discovery and monitoring of virtual Ethernet modules (VEMs)
  • Discovery and monitoring of virtual Ethernet interfaces

VSG Features

  • Discovery and monitoring of virtual machine zones.

Virtual Security Gateway Features

  • Discovery and monitoring of security zones

ASR 9000 and 1000 Features

  • Discovery and monitoring of MPLS L3 VPNs

CSR 1000V Features

  • Similar to ASR 1000 without hardware components.

ASA 5500 Features

  • Discovery and monitoring of security contexts

ASA 1000V Features

  • Similar to ASA 5500 without hardware components.

MDS 9000 Features

  • Discovery and monitoring of fibre-channel ports
  • Discovery and monitoring of VSANs
  • Discovery and monitoring of storage zones
  • Discovery and monitoring of storage zone sets

Wireless LAN Controller Features

  • Discovery and monitoring of access points

TelePresence Codecs

  • Discovery and monitoring of TelePresence peripherals

Class-Based QoS Monitoring

Zenoss will model QoS class maps associated with network interfaces using CISCO-CLASS-BASED-QOS-MIB. You will be able find all modeled class maps for a device by clicking QoS Class Maps under Components in the device's left navigation pane.

Interface Class Maps

Interface Class Maps

Notes:

  • Since the QoS component require the associated interfaces to be already modeled via the cisco.snmp.Interfaces modeler, you may need to model your device twice initially for the QoS components to model. If QoS Class Maps is not shown it means no class maps were modeled.

  • If you believe service policies have been configured and Zenoss should have found them, verify that the cisco.snmp.QoSClassMaps modeler plugin is enabled, you have interface components, and then remodel the device.

To see just the class maps associated with a specific interface you can find the interface in question then choose QoS Class Maps in the Display drop-down instead of Graphs.

QoS Class Maps

QoS Class Maps

The following datapoints are monitored for all class maps:

  • Pre-Policy Throughput in bits/sec. (cbQosCMPrePolicyByte)
  • Pre-Policy Packet Rate in packets/sec. (cbQosCMPrePolicyPkt)
  • Post-Policy Throughput in bits/sec. (cbQosCMPostPolicyByte)
  • Drops in bits/sec. (cbQosCMDropByte)
  • Drops in packets/sec. (cbQosCMDropPkt)
  • Drops (no buffer) in packets/sec. (cbQosCMNoBufDropPkt)
  • Fragments in bits/sec. (cbQosCMFragmentByte)
  • Fragments in packets/sec. (cbQosCMFragmentPkt)

The following datapoints are monitored for class maps with queueing configurations:

  • Queue Depth (Current) in bytes. (cbQosQueueingCurrentQDepth)
  • Queue Depth (Maximum) in bytes. (cbQosQueueingMaxQDepth)
  • Queue Discards in bits/sec. (cbQosQueueingDiscardByte)
  • Queue Discards in packets/sec. (cbQosQueueingDiscardPkt)

The following datapoints are monitored for class maps with traffic shaping configurations.

  • Shaping Queue Depth in packets. (cbQosTSStatsCurrentQSize)
  • Delayed by Shaping in bits/sec. (cbQosTSStatsDelayedByte)
  • Delayed by Shaping in packets/sec. (cbQosTSStatsDelayedPkt)
  • Dropped by Shaping in bits/sec. (cbQosTSStatsDropByte)
  • Dropped by Shaping in packets/sec. (cbQosTSStatsDropPkt)

The following datapoints are monitored for class maps with policing configurations.

  • Policing Conformed in bits/sec. (cbQosPoliceConformedByte)
  • Policing Conformed in packets/sec. (cbQosPoliceConformedPkt)
  • Policing Exceeded in bits/sec. (cbQosPoliceExceededByte)
  • Policing Exceeded in packets/sec. (cbQosPoliceExceededPkt)
  • Policing Violated in bits/sec. (cbQosPoliceViolatedByte)
  • Policing Violated in packets/sec. (cbQosPoliceViolatedPkt)

The 64bit versions of all of the above counters will be used if Zenoss is monitoring the device with SNMPv2c or greater, and if the device supports them. Otherwise, the 32bit versions of the counters will be used.

Usage

Choosing the Proper Device Class

To ensure that the most appropriate discovery and monitoring is being performed for a device it must be placed into the appropriate device class. The following table maps the type of Cisco device to the device class to which it should be assigned.

  • Note: It is not always necessary to manually assign devices to device classes. When adding devices using the Add Multiple Devices wizard, you will have a reduced set of choices that are intuitive based on the type of device.
Cisco Device TypeZenoss Device Class
Catalyst 6500/Network/Cisco/6500
Catalyst 6500 VSS/Network/Cisco/6500/VSS
ACE/Network/Cisco/ACE
FWSM/Network/Cisco/FWSM
Nexus 9000/Network/Cisco/Nexus/9000
Nexus 7000/Network/Cisco/Nexus/7000
Nexus 6000/Network/Cisco/Nexus/6000
Nexus 5000 + 2000/Network/Cisco/Nexus/5000
Nexus 3000/Network/Cisco/Nexus/3000
Nexus 1010/Network/Cisco/Nexus/1010
Nexus 1000V/Network/Cisco/Nexus/1000V
VSG/Network/Cisco/VSG
ASR 9000/Network/Cisco/ASR/9000
ASR 1000/Network/Cisco/ASR/1000
ASA/Network/Cisco/ASA
ASA-SM/Network/Cisco/ASA
MDS 9000/Network/Cisco/MDS/9000
WLC/Network/Cisco/WLC
TelePresence Codec/Network/Cisco/Codec
Other IOS/Network/Cisco
Other CatOS/Network/Cisco/CatOS

Configuring Credentials

Zenoss uses different network protocols to monitor different types of Cisco devices. In many cases Zenoss will use multiple protocols for the same device. The following table describes the supported device types and the protocol(s) are used to discover and monitor them:

Cisco Device TypeDiscovery and Monitoring Protocol(s)
Catalyst 6500ICMP, SNMP, Telnet or SSH
Catalyst 6500 VSSICMP, SNMP, Telnet or SSH
ACEICMP, SNMP, API (XML over HTTPS: 443/tcp)
FWSMICMP, SNMP
Nexus 9000ICMP, NX-API (XML over HTTP)
Nexus 7000ICMP, SNMP, Netconf (XML over SSH)
Nexus 6000ICMP, SNMP, Netconf (XML over SSH)
Nexus 5000 + 2000ICMP, SNMP, Netconf (XML over SSH)
Nexus 3000ICMP, SNMP, Netconf (XML over SSH)
Nexus 1010ICMP, SNMP, Netconf (XML over SSH)
Nexus 1000VICMP, SNMP, Netconf (XML over SSH)
VSGICMP, SNMP, SSH, Netconf (XML over SSH)
ASR 9000ICMP, SNMP, Telnet or SSH
ASR 1000ICMP, SNMP
ASAICMP, SNMP
ASA-SMICMP, SNMP
MDS 9000ICMP, SNMP
WLCICMP, SNMP
TelePresence CodecICMP, SNMP
Other IOSICMP, SNMP
Other CatOSICMP, SNMP

The following configuration properties should be set to provide the necessary credentials for the management protocols listed above:

ProtocolConfiguration PropertiesNotes
SNMPv1 and SNMPv2czSnmpCommunities, zSnmpCommunitySNMPv1 will only be used if SNMPv2c tests fail.
SNMPv3zSnmpSecurityName, zSnmpAuthType,
zSnmpAuthPassword, zSnmpPrivType,
zSnmpPrivPassword
SNMPv3 must be specified using zSnmpVer.
Telnet, SSH, NetconfzCommandProtocol, zCommandPort,
zCommandUsername, zCommandPassword
Protocol and port control whether
SSH or telnet will be used.
ACE XML over HTTP APIzCommandUsername, zCommandPassword,
zCiscoACEUseSSL
NX-API over HTTP APIzCommandUsername, zCommandPassword,
zCiscoNXAPIUseSSL, zCiscoNXAPIPort

Firewall Access

The firewall access to and from the Zenoss collector server to the monitored devices can depend on the type of device being monitored. The following table provides a consolidated view of all required network access.

SourceDestinationPort & Protocol
Zenoss CollectorMonitored DeviceICMP (ping)
Zenoss CollectorMonitored Device161/udp (SNMP)
Zenoss CollectorMonitored Device22/tcp (SSH)
Zenoss CollectorMonitored Device23/tcp (telnet)
Zenoss CollectorMonitored Device443/tcp (HTTPS)
Zenoss CollectorMonitored Device80/tcp (HTTP)
Monitored DeviceZenoss CollectorICMP (ping)
Monitored DeviceZenoss Collector162/udp (SNMP trap)
Monitored DeviceZenoss Collector514/udp (syslog)

Monitoring Logical Contexts

Several of the supported device types have the ability to create logical contexts of various kinds. In these cases, Zenoss has the ability to identify the logical contexts and associate them with the admin or parent context. The following is a list of device types that support logical contexts and how Zenoss refers to them.

  • ACE: ''Virtual Contexts''
  • FWSM: ''Security Contexts''
  • ASA: ''Security Contexts''
  • Nexus 9000: ''VDCs''
  • Nexus 7000: ''VDCs''
  • Nexus 6000: ''VDCs''

For Zenoss to be able to discover and associate these types of logical contexts with the admin or parent context, the management IP address of each logical context must itself be discovered as a separate device in Zenoss. The logical contexts should be placed into the same device class as the device they're a context of. For example, a Nexus 7000 VDC should be placed in the /Network/Cisco/Nexus/7000 device class.

Controlling Automatic Remodeling

Certain SNMP traps will cause Zenoss to schedule an immediate remodeling of the device from which the trap was sent. The traps that will cause this automatic remodeling by default are:

  • ccmCLIRunningConfigChanged
  • cefcFRUInserted
  • cefcFRURemoved
  • cefcModuleOperStatus
  • cefcModuleStatusChange
  • ceSensorExtThresholdNotification
  • cesRealServerStateChangeRev1
  • ciscoSlbExtMIBConform
  • ciscoSlbVServerStateChange
  • entConfigChange
  • vtpVlanCreated
  • vtpVlanDeleted

This list can be modified by using changing the ''zCiscoRemodelEventClassKeys'' configuration property.

Monitoring Memory Buffer Pools

Monitoring detailed memory buffer pool statistics is not enabled. When enabled, the following statistics can be monitored on any Cisco devices that support OLD-CISCO-MEMORY-MIB.

Memory Buffers

  • Allocation of Max
  • Usage of Total
  • Failures
  • Hits
  • Misses
  • Creates
  • Trims

Buffer elements and small, medium, big, large and huge buffer pools are included for each of these categories.

To enable memory buffer pool monitoring you must bind the ''Memory Buffer Pools'' monitoring template to the desired device class or device. You will then find the associated graphs on the ''Graphs'' screen for each device to which the monitoring template has been bound.

Monitoring CPUs

While extensive CPU monitoring is done by default for most Cisco devices and applicable modules on those devices, it can sometimes be desirable to monitor CPUs directly using CISCO-PROCESS-MIB. If Zenoss isn't already capturing CPU information you know exists in CISCO-PROCESS-MIB, you can enable further support by enabling the cisco.snmp.CPUs modeler plugin.

Monitoring Memory Pools

If you want Zenoss to model and monitor all memory pools on your Cisco device using the CISCO-MEMORY-POOL-MIB, enable the cisco.snmp.MemoryPools modeler plugin.

Limitations

The following potential limitations should be noted.

  • This ZenPack does not provide support for UCS. Instead, UCS is supported in ZenPacks.zenoss.CiscoUCS.
  • This ZenPack does not provide support for Cisco CallManager. Instead, Cisco CallManager is supported in ZenPacks.zenoss.CallManagerMonitor.
  • In Zenoss 5.x, graph points from same graph cannot be used in calculations for other points. (ZEN-18541)
  • In Zenoss 5.x, Custom graph point with Type COMMENT is not supported. (ZEN-18540)

Appendix A: Included MIBs

This ZenPack installs the following MIBs. Any SNMP traps defined in these MIBs will be decoded by Zenoss.

  • BRIDGE-MIB
  • CISCO-CONFIG-MAN-MIB
  • CISCO-ENHANCED-SLB-MIB
  • CISCO-ENTITY-FRU-CONTROL-MIB
  • CISCO-ENTITY-SENSOR-EXT-MIB
  • CISCO-ENTITY-SENSOR-MIB
  • CISCO-ENVMON-MIB
  • CISCO-FC-FE-MIB
  • CISCO-FLEX-LINKS-MIB
  • CISCO-HSRP-MIB
  • CISCO-IF-EXTENSION-MIB
  • CISCO-L2-TUNNEL-CONFIG-MIB
  • CISCO-LINK-ERROR-MONITOR-MIB
  • CISCO-MAC-NOTIFICATION-MIB
  • CISCO-MODULE-AUTO-SHUTDOWN-MIB
  • CISCO-NS-MIB
  • CISCO-OSPF-MIB
  • CISCO-OSPF-TRAP-MIB
  • CISCO-RTTMON-MIB
  • CISCO-SLB-EXT-MIB
  • CISCO-SLB-HEALTH-MON-MIB
  • CISCO-SLB-MIB
  • CISCO-SMI
  • CISCO-ST-TC
  • CISCO-STP-EXTENSIONS-MIB
  • CISCO-TC
  • CISCO-VLAN-MEMBERSHIP-MIB
  • CISCO-VSAN-MIB
  • CISCO-VTP-MIB
  • CISCO-ZS-MIB
  • ENTITY-MIB
  • ENTITY-SENSOR-MIB
  • HC-ALARM-MIB
  • IF-MIB
  • OLD-CISCO-INTERFACES-MIB
  • OLD-CISCO-SYSTEM-MIB
  • OLD-CISCO-TCP-MIB
  • OLD-CISCO-TS-MIB
  • P-BRIDGE-MIB
  • Q-BRIDGE-MIB
  • RMON2-MIB
  • SNMPv2-MIB
  • TOKEN-RING-RMON-MIB

Appendix B: IP-SLA (RTTMON) Monitoring

IP-SLA refers to Cisco IOS IP Service Level Agreement monitoring. This ZenPack provides limited IP-SLA support for IP-SLA Probes found in the component grid for devices that support the CISCO-RTTMON-MIB MIB. RTTMON refers to Round Trip Time Monitor.

Templates that use IP-SLA are all in the /Network/Cisco device class:

  • RTTProbeGeneric
  • RTTProbeICMPJitter
  • RTTProbeJitter

We discuss each of these templates in order.

RTTProbeGeneric

Provides generic metrics round time packet traversal.

Data Points

Data SourceData PointDescription
operSenseoperSenseA sense code for the completion status of
the latest RTT operation.
rttMonLatestRttOperTablerttMonLatestRttOperTableThe completion time of the latest RTT
operation successfully completed.

Graphs

GraphGraph PointsDescription
Round TriprttMonLatestRttOperTableGeneric round-trip time probe

RTTProbeICMPJitter

This template provides stats, for ICMP Jitter rrtType probes.

Data Points

Data SourceData PointDescription
rttMonLatestIcmpJitterAvgJitterrttMonLatestIcmpJitterAvgJittersThe average of positive and negative
jitter values in Source-to-Destination
and Destination-to-Source direction.
rttMonLatestIcmpJitterNumOWrttMonLatestIcmpJitterNumOWThe number of successful one way trip
time measurments.
rttMonLatestIcmpJitterNumRTTrttMonLatestIcmpJitterNumRTTThe number of RTT's that were
successfully measured.
rttMonLatestIcmpJitterPktLossrttMonLatestIcmpJitterPktLossThe number of packets lost.

Graphs

GraphGraph PointsDescription
JitterrttMonLatestIcmpJitterAvgJitterJitter
Packet LossrttMonLatestIcmpJitterPktLossPacket Loss
Success StatsrttMonLatestIcmpJitterNumOW
rttMonLatestIcmpJitterNumRTT
Successful measurements

RTTProbeJitter

Jitter metrics from CISCO-RTTMON-MIB

Data Points

Data SourceData PointDescription
echoNumPacketsechoNumPacketsThis uses the rttMonEchoAdminNumPackets
object. This value represents the number
of packets that need to be transmitted.
This value is currently used for Jitter
probe. This object is applicable to
jitter probe only.
jitterNumRTTjitterNumRTTThis uses the rttMonLatestJitterOperNumOfRTT
object. The number of RTT's that were
successfully measured.
jitterPktLossDSjitterPktLossDSThis uses the rttMonLatestJitterOperPacketLossDS
object. It is the number of packets lost
when sent from destination to source.
jitterPktLossSDjitterPktLossSDThis uses the rttMonLatestJitterOperPacketLossSD
object. The number of packets lost when sent
from source to destination.
jitterRTTSumjitterRTTSumThis uses the rttMonLatestJitterOperRTTSum
object. The sum of Jitter RTT's that are
successfully measured (low order 32 bits).
operSenseoperSenseThis uses the rttMonLatestRttOperSense object.
A sense code for the completion status of
the latest RTT operation.
rttMonLatestJitterOperMOSrttMonLatestJitterOperMOSThe MOS value for the latest jitter operation
in hundreds.
rttMonLatestJitterOperMaxOfNegativesDSrttMonLatestJitterOperMaxOfNegativesDSThe maximum of all negative jitter values
from packets sent from destination to
source.
rttMonLatestJitterOperMaxOfNegativesSDrttMonLatestJitterOperMaxOfNegativesSDThe maximum of absolute values of all
negative jitter values from packets sent
from source to destination.
rttMonLatestJitterOperMaxOfPositivesDSrttMonLatestJitterOperMaxOfPositivesDSThe maximum of all positive jitter
values from packets sent from
destination to source.
rttMonLatestJitterOperMaxOfPositivesSDrttMonLatestJitterOperMaxOfPositivesSDThe maximum of all positive jitter
values from packets sent from source
to destination.
rttMonLatestJitterOperMinOfNegativesDSrttMonLatestJitterOperMinOfNegativesDSThe minimum of all negative jitter
values from packets sent from
destination to source.
rttMonLatestJitterOperMinOfNegativesSDrttMonLatestJitterOperMinOfNegativesSDThe minimum of absolute values of all
negative jitter values from packets
sent from source to destination.
rttMonLatestJitterOperMinOfPositivesDSrttMonLatestJitterOperMinOfPositivesDSThe minimum of all positive jitter
values from packets sent from
destination to source.
rttMonLatestJitterOperMinOfPositivesSDrttMonLatestJitterOperMinOfPositivesSDThe minimum of all positive jitter
values from packets sent from source
to destination.

Graphs

GraphGraph PointsDescription
Average JitterrttMonLatestJitterOperMaxOfNegativesDS
rttMonLatestJitterOperMaxOfNegativesSD
rttMonLatestJitterOperMaxOfPositivesDS
rttMonLatestJitterOperMaxOfPositivesSD
rttMonLatestJitterOperMinOfNegativesDS
rttMonLatestJitterOperMinOfNegativesSD
rttMonLatestJitterOperMinOfPositivesDS
rttMonLatestJitterOperMinOfPositivesSD
Average Jitter Metrics
MOS ScorerttMonLatestJitterOperMOSMean Open Score (VoIP)
Packet LossechoNumPackets
jitterPktLossDS
jitterPktLossSD
Packet Loss
Round-Trip TimejitterNumRTT
jitterRTTSum
Round Trip

Known Issues

  • Ethernet Interface components are missing from Nexus 9000 NX-OS 6.1(2)I3(3a).
    • Solution: Upgrade the firmware version on Nexus 9000, 6.1(2)I3(5b) is not affected by the issue.

Changes

5.8.1

  • Fix ciscoEnvMonTempStatusChangeNotif Transform error. (ZPS-1638)

  • Add unit test for SNMP event summary after transforms.

5.8.0

  • Add FEX support for Nexus 9000 via NX-API. (ZPS-740)
  • Use SSL for NX-API connections. (ZPS-785)
  • Add CiscoWLC graphs and CiscoWLC.CiscoAP status events. (ZPS-238)
  • Model missing version property of power supplies. (ZPS-1132)
  • ifOperStatus datasource and status threshold were added to ethernetCsmacd monitoring template under /Network/Cisco device class. (ZEN-21742)
  • Quiet Netconf plugin connection errors for Nexus. (ZEN-18532)
  • Fix Cisco SNMP model fails if sysdescr doesn't return. (ZPS-1171)
  • Fix unhandled KeyError exceptions in QoSClassMap modeler plugin. (ZPS-901)
  • Fix Supervisor modules detection in modeler. (ZPS-1164)
  • Fix inconsistent graph labels for Memory and CPU. (ZPS-1220)
  • Fix unit tests for card modules. (ZPS-805)
  • Make unique analytics aliases for SupModule and MemPool components. (ZPS-1228)
  • Prevent NX-API authentication spam by using auth token. (ZPS-926)
  • Add Port Channel to member interface relations to Analytics. (ZPS-1236)
  • Fix average value calculation for packet loss. (ZPS-1168)
  • Require ZenPackLib >= 2.0.5 to ensure backups get created. (ZPS-1310)
  • Fix "AttributeError" message after adding a default "status" threshold to a Graph Definition. (ZPS-1298)
  • The VSANs field was removed from Network Interfaces Display drop-down. (ZPS-1261)
  • Add missing fields to components in Analytics Cisco Devices Domain (ZPS-19093)
  • Reorganize Zone and Zone Sets in Analytics Cisco Devices Domain (ZPS-19113)
  • Expand Interface Types in Analytics Bundle (ZPS-19112)
  • 'zCiscoNXAPIPort' and 'zCiscoNXAPIUseSSL' options were added to Cisco Nexus 9000 on the 'Add Device' page. (ZPS-1325)
  • Remove an extra Graphs entry in Display drop-down. (ZPS-1340)

5.7.4

  • Add Catalyst 2960 support.

5.7.3

  • Add support for more TelePresence peripherals. (ZEN-25993)

5.7.2

  • Fix isProjection template copying error. (ZEN-23332)
  • Set event class mapping sequences to 1000. (ZEN-23103)
  • Fix ciscoEnvMonSuppStatusChangeNotif trap handler. (ZEN-24123)
  • Fix ObjectNotFound zones modeling error.
  • Fix broken "|" eventKey on NX-API events. (ZEN-21247)
  • Add common datapoint aliases. (ZEN-24619)

5.7.1

  • Fix StatCountInUse and StatCountPeak OID's. (ZEN-12336)

5.7.0

  • Add port-channel monitoring for Nexus 9000. (ZEN-22018)

5.6.3

  • Indicate NX-API for Nexus 9000 in Add Infrastructure Wizard. (ZEN-21165)
  • Associate cefcPowerStatusChange events with Ethernet interfaces. (ZEN-21726)

5.6.2

  • Fix "isProjection" error when creating local templates. (ZEN-21691)

5.6.1

  • Improve name of fabric extenders in some cases. (ZEN-17538)
  • Disable monitoring of admin-down MPLS L3 VPNs. (ZEN-18463)

5.6.0

  • Honor zInterfaceMapIgnore(Names|Types) for VLAN modeling.
  • Fix memory utilization graph for Nexus switches on Zenoss 5. (ZEN-19253)
  • Make QoS class map modeling tolerant of bad data. (ZEN-19326)
  • Add units to supervisor module memory utilization graph. (ZEN-19500)
  • Minor updates to Dynamic View relationships. (ZEN-19289)

5.5.0

  • Added support for modeling/monitoring Nexus 9000 series switches via the NX-API.

5.4.1

  • Fixed Layer2 integration for Nexus switches. (ZEN-17290)
  • Disable monitoring of QoS class maps on disabled interfaces. (ZEN-17291)
  • Fix misreporting of temperature sensor value in some cases. (ZEN-11440)

5.4.0

  • Improved class-based QoS monitoring.

5.3.5

  • Fix to allow Cisco devices to work with Layer2 ZenPack. (ZEN-13859)
  • Fix potential 'interfaceTypes' modeling error. (ZEN-8991)

5.3.4

  • Fix "Unable to cleanup" warning on first install. (ZEN-16895)
  • Fix VRF relationship for FastEthernet interfaces. (ZEN-16896)

5.3.3

  • Fix potential installation failure. (ZEN-16307)
  • Fix HSRPMap modeler plugin for Cisco devices. (ZEN-15427)

5.3.2

  • Fix potential traceback in Interfaces modeler plugin. (ZEN-15619)
  • Fix auto-classification of 3560 devices. (ZEN-16026)
  • Change Netconf authentication failure to warnings. (ZEN-16112)

5.3.1

  • Fix potential traceback in CPUs modeling plugin.

5.3.0

  • Add optional support for modeling and monitoring CPUs and memory pools.

5.2.0

  • Add optional support for monitoring memory buffers.

5.1.16

  • Fix modeling of IP address on Nexus VLAN (SVI) interfaces.

5.1.15

  • Remove pointless CSR device-level CPU graph.
  • Fix display of administrative and operational status for IP-SLA probes.
  • Updated custom graphs to be compatible with Zenoss 5.
  • Updated VRF graphs to be compatible with Zenoss 5.
  • Fix handling of SNMP traps with multiple values for same varbind.

5.1.14

  • Set zCredentialsZProperties for Nexus device classes.

5.1.13

  • Fix conflict with SolarisMonitor 2.2.0.
  • Properly fix combining of VLAN L2 and L3 data.

5.1.12

  • Improve linking of ASA security contexts.
  • Add zCiscoACEUseSSL property. Defaults to true.

5.1.11

  • Add fan and temperature sensor discovery for devices that only support CISCO-ENVMON-MIB.
  • Add voltage sensor discovery and monitoring.
  • Revert problematic VLAN naming change in 5.1.8 release.

5.1.10

  • Enable auto-discovery for 6500 switches.
  • Add support for zCredentialsZProperties.

5.1.9

  • Restore fan cooling capacity monitoring for some 6500 switches.

5.1.8

  • Improve Analytics support.
  • Improve combining of monitoring for L2 and L3 VLANs.

5.1.7

  • Add Nexus 6000 support.

5.1.6

  • Widen support for 6500 fan monitoring.

5.1.5

  • Add Nexus 9000 support. NX-OS mode only.

5.1.4

  • Fix for missing Nexus 7000 VDC components.

5.1.3

  • Fix vslIndexID error when modeling some devices.

5.1.2

  • Add CISCO-PROCESS-MIB. Fix trap handling.
  • Add active SNMP monitoring for VRF status.
  • TelePresence Codecs: Improve modeling and monitor memory usage.
  • Fix bug in component display for Nexus 7000 VDC devices.

5.1.1

  • Add zCiscoRemodelEventClassKeys configuration property. SNMP trap types listed in this property will cause an immediate remodel of the originating device.

5.1.0

  • Add QoS monitoring.

5.0.6

  • Support CISCO-PAGP-MIB for port-channel association.

5.0.5

  • Add ASA 1000V and CSR 1000V support.
  • Model more sub-interface types as sub-interfaces.
  • Fix bug in display of RTT probe threshold.
  • Fix "interfaceTypes" error bug that could occur after upgrade.
  • Fix bug that would model non-existent "allowed" VLANs on Nexus 1000V.
  • Fix bug in display of logical contexts for some Cisco devices.

5.0.4

  • Add SNMPv3 support for ISDN and IP-SLA monitoring.
  • Use EthernetInterface monitoring template for all Ethernet interfaces.

5.0.3

  • Stop automatic remodeling when cHsrpStateChange traps occur.
  • Add "monitor" field fo "cannot be remodeled" events.
  • Add CISCO-PROCESS-MIB support for modeling total memory.
  • Fix bug that prevented monitoring control for some components.
  • Fix bug that broke group membership for some Cisco devices.

5.0.2

  • Zenoss version compatibility changed from >=4.1 to >=4.2.
  • Interfaces: Use ifType instead of entPhysicalDescr for type.
  • Improve modeling performance.
  • Support getting HA status for ACE 4710 admin contexts.
  • Support monitoring connection rate(s) on ACE 4710.
  • Stop showing data-less graph for ACE power supplies.
  • Prefer ifName to ifDescr for redundantly-named ACE interfaces.
  • Better handling of cefcFRURemoved and cefcFRUInserted traps.
  • Better handling of cefcPowerStatusChange trap.
  • Better handling of ceSensorExtThresholdNotification trap.
  • Add many MIBs to support SNMP trap handling.
  • Better classification of common ASA interface types.
  • Add support for ACE 30.
  • Fix scaling bug in power supply current graphs.
  • Fix bug in handling of blank hardware model names.
  • Fix bug in handling of invalid RTT jitter and packet loss data.
  • Fix bug that caused lengthy data migration during upgrade.
  • Fix bug in handling of interfaces with no name.
  • Fix bug in handling of buggy ACE VLANs with "Index" names.
  • Fix bug in handling of multi-value responses from ACE.
  • Fix confusing error when discovering Nexus 700 with no VDCs.
  • Fix bug in association of ACE real servers to farms.
  • Fix bug in display of outbound packetloss for RTT echo probes.

5.0.1

  • Support VRF modeling on older IOS versions.
  • Model unknown interfaces types.
  • Disabled incomplete Nexus 1000V Impact support.

5.0.0

  • Support for Nexus 1010.
  • Support for ASA Service Module (ASA-SM).
  • Support for Nexus FabricPath cards.
  • Support for Nexus 3000.

4.0.0

  • Added support for Catalyst 6500 and VSS.
  • Added support for FWSM.
  • Added support for Nexus 5000 and 2000.
  • Added support for Nexus 1000V.
  • Added support for VSG.
  • Added support for ASR 9000.
  • Added support for ASR 1000.
  • Added support for MDS 9000.
  • Extended support for ACE.
  • Extended support for Nexus 7000.
  • Extended support for ASA.
  • Extended support for other IOS and Nexus devices.
Commercial

This ZenPack is developed and supported by Zenoss Inc. Commercial ZenPacks are available to Zenoss commercial customers only. Contact Zenoss to request more information regarding this or any other ZenPacks. Click here to view all available Zenoss Commercial ZenPacks.