Cumulus Integration Service
This integration is a subscription-based Professional Services engagement. Our Integration Services are offered as subscriptions in order to provide initial setup and ongoing compatibility and maintenance. All standard packages are renewable every 12 months from the date of purchase. Contact Zenoss to request more information regarding this or any other ZenPacks.
This ZenPack adds monitoring for Cumulus routers. Cumulus is a linux distribution, specialized for network routing, which can run on general purpose compute hardware.
|Product||Zenoss 6.4 or higher|
|Required ZenPacks||ZenPacks.zenoss.RoutingProtocols >= 1.7.0|
|ZenPacks.zenoss.ZenPackLib >= 2.1.1|
|ZenPacks.zenoss.PS.Util >= 1.10.0|
This ZenPack supports SNMP for collecting modeling data and metrics for the Cumulus devices.
SNMP polling is configurable with standard Zenoss functionality.
This ZenPack adds 5 new SNMP modeler plugins, and uses 5 standard SNMP modeler plugins. The new modeler plugins that are added are:
- zenoss.snmp.CumulusRouterMap Models most of the physical entities that make up the switch, including the chassis, fans, power supplies and temperature sensors
- zenoss.snmp.CumulusBGPNeighborMap Models the BGP neighbors. Mostly inherited from the RoutingProtocols ZenPack, but adjusted to use the Cumulus-specific BGP neighbor table
- zenoss.snmp.CumulusProcessorMap Models the processors (CPUs) in the physical chassis zenoss.snmp.CumulusInterfaceMapOverrides the existing InterfaceMap plugin to allow the interface speed to be editable.
- zenoss.snmp.CumulusInterfaceAliasMap Overrides the existing InterfaceAliasMap plugin to allow the interface speed to be editable.
Add devices as you normally would to the /Network/Cumulus device class. The SNMP credentials will need to be set on either the device or the device class.
There are status thresholds for Fans, Power Supplies, Temperature Sensors and Processors (CPUs). For Fans, Power Supplies and Temperature Sensors, the mapping from the SNMP value to event severity is:
- SNMP value: 1, Event severity: 0 (Clear)Indicates the component is working properly
- SNMP value: 2, Event severity: 3 (Warning)Indicates the status is unknown
- SNMP value: 3, Event severity: 5 (Critical)Indicates the component has failed
Processors have a different mapping:
- SNMP value: 1, Event severity: 3 (Warning)Indicates the status is unknown
- SNMP value: 2, Event severity: 0 (Clear)Indicates the processor is working properly
- SNMP value: 3, Event severity: 3 (Warning)Indicates that there has been an error reported by the OS, but the processor is still operational
- SNMP value: 4, Event severity: 3 (Warning)Indicates that the processor is in the testing state
- SNMP value: 5, Event severity: 5 (Critical)Indicates that the processor has failed
The monitoring template for interfaces is identical to the standard ethernetCsmaCd template, with the exception of the threshold for interface utilization. The default, used if the interface speed is unknown, is 2 ** 64 - 1, which is the largest possible value for a 64 bit integer, instead of the previous default of 1e9 (1 Gbps). Since these devices have 40Gbps physical interfaces, having logical interfaces breach the threshold of 1 Gbps would cause too many unneccesary events.
- SVC-3361 Prevent traceback when device doesn't report chassis info
- Initial release