SCOM: Updates to the Cisco Management Pack
September 17, 2009 3 Comments
I have uploaded version 1.01.27 of the Cisco Management Pack. This minor update includes a few fixes and some new features added in response to some helpful comments from readers who have tried this MP out. The changes in this version are:
- Group Population rules have been fixed so that they can be edited in the GUI
- Performance data collection has been modified to not collect data when the interface is in a partially discovered state. This should prevent duplication of performance counters for interfaces going forward. Because the Interface discovery occurs in two parts: 1) discovering the interfaces and 2) discovering the interface properties, I added a property to the Interface class named: Discovered. When the Interface discovery runs (which just discovers the index), the discovered property will be set to False. Once the Interface Property discovery runs, this property will be set to True. The performance collection rules have been modified to only collect data if this property is set to true.
- Index discovery can now be filtered with a RegEx expression for a device via an override (create the override on the Discover Cisco Interfaces discovery). By default, the RegEx expression: (.|..|…) will be used to discover interfaces, which will discover all interfaces with indexes with 1, 2, or 3 digits in length. To filter by interface index, the expression can be modified to: (1|2|3|10|15) where the numbers are the index values for the interfaces to be discovered, separated by pipe characters. The override for this filter can be targeted at all Cisco devices, a group, or specific devices.
- I have added a new property to the Interface class named: “Speed – Override.” This property allows for manually defining a speed value for the interface to be used in utilization calculations. There are two scenarios where this is useful: 1) sometimes the value reported in the RFC-1213 ifTable for an interface’s speed isn’t accurate, and 2) if an Ethernet port is the last monitored hop before a lower bandwidth wide-area connection (i.e. the vendor equipment is not monitored), it can be useful to monitor the Ethernet port as if its speed were equivalent to the wide-area connection bandwidth. For example, if a switch is the last monitored device before connecting to a vendor-managed MetroE connection with a maximum bandwidth of 500Mbit, monitoring utilization on the gigabit switch port will be more accurate if the speed were overridden to 500Mbit. This property can be set with an override on the Discover Cisco Interface Properties object discovery, by setting the OverrideIFSpeed value to the desired speed, in bits per second.