Comments on: SCOM: Advanced SNMP Monitoring Part III: The Completed Cisco Management Pack

By: Randall Sindlinger

Randall Sindlinger — Wed, 10 Aug 2011 14:16:45 +0000

We’ve had problems with running xSNMP in our environment, where (in a tight nutshell) it has caused Gateways to get corrupted Event Logs.

Is the Cisco Management Pack still viable, or are there any other options for doing network device interface monitoring? We don’t really have the resources right now to troubleshoot xSNMP further, and have uninstalled that MP.

-Randall

By: sailorimc

sailorimc — Fri, 01 Jul 2011 15:19:56 +0000

Hi
Great work with this MP. The only thing which annoys me is that i cant get monitored interfaces of CISCO switches.
Is there any way to enforce monitoring of the interfaces?
Thanks,

By: Faris

Faris — Tue, 27 Apr 2010 18:11:44 +0000

Merci de m’indiquer le lien ou je pourrais télécharger le MP xSNMP qui me permettra de monitorer les équipements Cisco

Merci pour votre aide

By: Yohann

Yohann — Tue, 13 Apr 2010 15:49:37 +0000

excellent travail, merci

By: Kristopher Bash

Kristopher Bash — Sat, 27 Feb 2010 15:22:13 +0000

Allen, if you are on SCOM R2, I would highly recommend looking to replace this Cisco MP with the xSNMP Management Packs, also available from my blog site.

By: Allen

Allen — Thu, 25 Feb 2010 08:02:47 +0000

A question from our Network team…

“Would it be possible to get the Cisco interface monitor to pull in/report IF-MIB::ifDescr (1.3.6.1.2.1.2.2.1.2.x)? It would make it far easier to understand what was going on if we could see the interface name. User-friendly reporting of the administrative/operational status in the health explorer would be nice too – having to decode both the OIDs and their values is a bit nerdy.”

Any ideas what he is on about?

By: Tim

Tim — Tue, 22 Dec 2009 22:00:56 +0000

Hi Kristopher,
I just installed your MP on our test network and I am a newbie to cisco. I have about 15 adminstatus is up alerts. Could you please explain this alert. I few of the prots are empty but the rest are in use and seem to be working fine.

Thanks,

Tim

By: Kristopher Bash

Kristopher Bash — Wed, 16 Dec 2009 01:48:06 +0000

This is corrected in the xSNMP Management Packs (which I have made a couple of posts about this week). The xSNMP MP’s address this issue by doing the following:
1) Discovering each interface’s support for 64 bit counters
2) For interfaces that support 64 bit counters, an override is automatically used to override the OID’s for IF octets to use the IF-MIB 64 bit counters in the calculations.

This way 32 bit counters can still be used for low-speed interfaces, but if the agent supports 64 bit counters, they will automatically be used. For agents that don’t support 64 bit counters on high speed interfaces, I also configured the calculation script in these MP’s to discard the calculation if the delta is negative, which will at least prevent negative utilization values from being logged when a counter does rollover.

By: michel kamp

michel kamp — Tue, 15 Dec 2009 08:17:55 +0000

hi Kristopher,

Nice work!. But how do you address the octet counter overflow issue.? In most of the routers/switches the OS is 32Bits so if you have a polling time of lets say 5 minutes the change is big the counter value will reset from 2^32 to 0 . This reset has to be addressed in the utilization calculation, otherwise you can have a in correct utilization when the reset has occurred between T0 and T1.

Michel Kamp

By: SCOM: Advanced SNMP Monitoring Part III: The Completed Cisco Management Pack « Operating-Quadrant - Rod Trent at myITforum.com

Mon, 23 Nov 2009 13:07:41 +0000

[...] SCOM: Advanced SNMP Monitoring Part III: The Completed Cisco Management Pack « Operating-Quadrant Filed under: System Center, OpsMgr 2007, Management Packs [...]