Comments on: SCOM: Updates to the Cisco Management Pack (R2) v1.0.2.6 http://operatingquadrant.com/2009/09/26/scom-updates-to-the-cisco-management-pack-r2-v1-0-2-6/ Living in the I.T. Operating Quadrant. Useful articles on real world solutions involving Monitoring (System Center Operations Manager), Virtualization, Reporting, Scripting (PowerShell), and much more. Tue, 31 Jan 2012 01:50:45 +0000 hourly 1 http://wordpress.com/ By: François Dufour http://operatingquadrant.com/2009/09/26/scom-updates-to-the-cisco-management-pack-r2-v1-0-2-6/#comment-437 Thu, 21 Jan 2010 09:54:51 +0000 http://operatingquadrant.com/?p=255#comment-437 Hi Kris,

You just Rock ! :)

]]> By: Kristopher Bash http://operatingquadrant.com/2009/09/26/scom-updates-to-the-cisco-management-pack-r2-v1-0-2-6/#comment-435 Thu, 21 Jan 2010 04:04:05 +0000 http://operatingquadrant.com/?p=255#comment-435 Thanks for your comment. The 32bit counter rollover is a real problem with 10GbE interfaces and can be a problem with 1Gb interfaces too. The challenge in a monitoring scenario is detecting which interfaces support the 64bit counters in the IF-MIB as some vendors/versions don’t support 64bit octet counters on 1Gb interfaces and others don’t. I am happy to say that this issue is fully addressed in the xSNMP management pack which I will post for public beta testing this week. In this MP, I configured support for both 32 and 64 bit IF Octet counters by discovering whether each interface supports 64bit counters, and then passing the correct OID (32 or 64 bit octect counter) as an overridable parameter to the utilization monitors/rules.

]]> By: François Dufour http://operatingquadrant.com/2009/09/26/scom-updates-to-the-cisco-management-pack-r2-v1-0-2-6/#comment-434 Wed, 20 Jan 2010 20:56:16 +0000 http://operatingquadrant.com/?p=255#comment-434 Hi Kristopher,

That is some great work ! Really appreciated.

I have just one remark, the Cisco switch I’m monitoring has some 10Gbits ports and these are the ones I precisely want to monitor. Indexfilter parameter works fine. The problem I see now is that the ifInOctets value is limited to 4294967295 as it is a Counter32. With 10Gbits bandwidth the counter is reset almost every 5 mins which makes the inpct calculation false. I found there http://www.cisco.com/en/US/tech/tk648/tk362/technologies_q_and_a_item09186a00800b69ac.shtml that there were some 64bits counters that provide the values. So I have two questions: Is it possible to query such snmp 64bits counters in SCOM ?

]]> By: Pierre-Emmanuel http://operatingquadrant.com/2009/09/26/scom-updates-to-the-cisco-management-pack-r2-v1-0-2-6/#comment-345 Wed, 09 Dec 2009 19:43:12 +0000 http://operatingquadrant.com/?p=255#comment-345 Hi Kris,

This is a great job you have done so far, I am currently inspecting the nooks and crannies of the mp and I have a question right off the bat:

In the data source module for discovering cisco devices, you have an OID Filter module which, from what I understand, filters off any network devices which do not have an OID containing, 1.3.6.1.4.1.9., then in the final mapper module, you use the FilteredClassSnapshotDataMapper, in this module there is an expression that filters again on the OID, 1.3.6.1.4.1.9.. Is this really necessary? wouldn’t the ClassSnapshotDataMapper module be sufficient since the OID is previously filtered? The way I see it, if an OID doesn’t match the first OID filter, the workflow stops there and therefor further filter isin’t necessary.

Best regards!

Pierre-Emmanuel

]]> By: Alex Fischer http://operatingquadrant.com/2009/09/26/scom-updates-to-the-cisco-management-pack-r2-v1-0-2-6/#comment-344 Wed, 09 Dec 2009 13:49:56 +0000 http://operatingquadrant.com/?p=255#comment-344 Hi Kristopher,

I’m working with the 1.0.2.7 build (SCOM 2007 R2 under W2K8). What could be the reason that Cisco 6500 (Supervisor 720) are just visible and you’re able to see the integrity of the chassis but not being able to see the status of the devices?

Alex

]]> By: Chris Taylor http://operatingquadrant.com/2009/09/26/scom-updates-to-the-cisco-management-pack-r2-v1-0-2-6/#comment-341 Sat, 05 Dec 2009 21:35:52 +0000 http://operatingquadrant.com/?p=255#comment-341 First, nice work. =) This is extremely useful.

A couple things that I’ve noticed though (I’m testing monitoring with an ASA5505).

1) Interface DMZ is administratively down, there is no cable plugged in. It is healthy (since it’s admin status is 2). If I change this to up (1) it shows up in a critical state (since the line protocol is down). If I shut the interface back down it doesn’t automatically return to healthy. If I reset the health it does show up correctly.

2) The same thing seems to happen if the device being managed is offline longer than the Discover Cisco Device discovery interval the device drops out of the Cisco Devices group.

]]> By: mats http://operatingquadrant.com/2009/09/26/scom-updates-to-the-cisco-management-pack-r2-v1-0-2-6/#comment-331 Fri, 27 Nov 2009 09:27:34 +0000 http://operatingquadrant.com/?p=255#comment-331 Yes it is. Its a Catalyst 4705R with 180 ports.

]]> By: Kristopher Bash http://operatingquadrant.com/2009/09/26/scom-updates-to-the-cisco-management-pack-r2-v1-0-2-6/#comment-330 Thu, 26 Nov 2009 16:26:53 +0000 http://operatingquadrant.com/?p=255#comment-330 Are the errors related to a device with a high number of interfaces?

]]> By: mats http://operatingquadrant.com/2009/09/26/scom-updates-to-the-cisco-management-pack-r2-v1-0-2-6/#comment-329 Thu, 26 Nov 2009 10:18:55 +0000 http://operatingquadrant.com/?p=255#comment-329 Kristopher.
Did you and Marnix get any further on this issue? I’m having the same at a customer site.

Best regards
Mats

]]> By: Kristopher Bash http://operatingquadrant.com/2009/09/26/scom-updates-to-the-cisco-management-pack-r2-v1-0-2-6/#comment-328 Wed, 25 Nov 2009 21:44:51 +0000 http://operatingquadrant.com/?p=255#comment-328 Thanks for your comment. That is an issue that I will need to correct. I’ll try to get it updated soon.

]]>