SCOM: Updates to the Cisco Management Pack

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:

  1. Group Population rules have been fixed so that they can be edited in the GUI
  2. 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. 
  3. 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.
  4. 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.
Advertisements

About Kristopher Bash
Kris is a Senior Program Manager at Microsoft, working on UNIX and Linux management features in Microsoft System Center. Prior to joining Microsoft, Kris worked in systems management, server administration, and IT operations for nearly 15 years.

3 Responses to SCOM: Updates to the Cisco Management Pack

  1. Jaroslav says:

    Hi,

    are there some requiremnets for this MP ?

    We can see only Cisco Devices, no interface, no fans are discovered…

    Can you give us some advice, where is a problem ?

    Our Cisco Device Description:

    Cisco SAN-OS(tm) m9500, Software (m9500-sf2ek9-mz), Version 3.2(2c), RELEASE SOFTWARE (fc2) Copyright (c) 2002-2005 by Cisco Systems, Inc. Compiled 11/16/2007 12:00:00

    Thanks a lot.

    Jaroslav

    • Kristopher Bash says:

      Well, the MP is intended for internetworking devices (ethernet switches, routers, firewalls, etc). I didn’t include any storage networking components in it. The interfaces should still be discovered though, because that is within the ifTable of the RFC-1213 MIB. Can you walk this table with an snmp browser and make sure that it is working properly? The OID for the table is: .1.3.6.1.2.1.2.2.

      The good news is that the Cisco storage switches implement the FC-MGMT mib, which means that a single management pack could be created to monitor sensors, ports, and events on FC switches from multiple vendors (e.g. Brocade, Cisco, etc). I’ll try to work out an MP that makes use of the FC-MGMT MIB in the very near future.

  2. Paul B says:

    Just want to say thanks for taking your time to create this MP. I just installed it yesterday and it is working without a flaw and I did not have to lose and arm and a leg for a MP.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: