Pack Catalog

Pack Catalog: DPM Data Source Monitoring Script MP Sample (for OpsMgr)

Fri, 13 Aug 2010 16:22:06 GMT

by David Allen, This script is for use in a Operations Manager monitor and requires the DPM Server Name to be passed to it. For full details on how to use this script from the source, click Download at right.

Pack Catalog: Webmon - A Basic Web Monitoring MP

Sun, 08 Aug 2010 19:22:16 GMT

by Kris Bash, this pack seems to cover the basics of web site availability and performance in a simple interface, including an all-important RETRY COUNT. Worth a look if you want web monitoring that is a bit more simply maintained.

Click the Download button to read the technical details and download from the source.

Pack Catalog: IBM DB2 Management Pack

Tue, 03 Aug 2010 04:00:00 GMT

Overview
Efficiently monitor distributed IBM DB2 databases on Microsoft Windows from a central console.
The NiCE DB2 Management Pack (NiCE DB2 MP) helps you increase RDBMS availability and performance and to lower the overall cost of maintaining your DB2 databases. It enables you to perform service-oriented management as well as incident management in your DB2 environment, supporting your business critical processes.
To ensure always-on availability, the NiCE DB2 MP monitors key operational activities and events such as event logs and processes. Information from important system tables is collected to reflect DB2 activity.

Pack Catalog: Wake-on-LAN Sample Mgmt Pack for Essentials 2010

Tue, 06 Jul 2010 04:59:46 GMT

For more details on setup, functionality and limitations of this sample MP, see this blog post - Wake-on-LAN Management Pack for Essentials 2010.

This simple management pack augments Essentials 2010 functionality by adding one-click magic packet delivery using a custom task. The pack includes a custom view and custom task each targeting the 'Network Adapter (Client)' class.

Requirements

Requires the free Depicus wake-on-LAN command line utility (wolcmd.exe) extracted to c:\tools.
Also requires that wake-on-LAN functionality is available and enabled in your managed client computers.

For example, Dell makes a utility you can use to enable wake-on-LAN on your Dell desktop and laptop computers through a msi package created with the Dell Client Configuration Utility (DCCU).

Instructions available at http://www.delltechcenter.com/page/Enable+Wake+On+Lan+with+DCCU.
Download DCCU HERE.

Known Issues

Due to the way the IP addresses are stored on the Network Adapter class, this task will only work for client network adapters with a single IPv4 address. This means IPv6 should be disabled on the client network adapters in your environment. This should be doable for DHCP clients in most environments today.

Pack Catalog: Scheduled Resolution Update Management Pack

Tue, 29 Jun 2010 13:28:04 GMT

Are you looking for a way to automate the process of closing out or changing the resolution state of various alerts? Do you have lots of SQL Job Failure alerts, or Script or Executable failed alerts which are not recurring but you want to avoid manually closing them every day (or hour?) The Scheduled Resolution Update Management Pack provides scheduled rules to auto-close or to change the resolution state based upon a periodic basis. These rules are designed to run daily, hourly, or weekly and to auto-close all alerts which have not been updated in the last hour, day, or all alerts which match the name specified. This management pack also can auto-change the resolution states of alert names which are specified on a daily, hourly or weekly basis.

UPDATE: 6.0.0.1 version added to resolve issues with alert closing for alerts older than an hour or older than a day.

Pack Catalog: Maintenance Mode History Report Management pack

Mon, 28 Jun 2010 18:39:19 GMT

This MP includes a report that allows tracking of who is using maintenance mode to disable monitoring and reports the maintenance start, end, comment, user id and reason code.

Pack Catalog: HP EVA Management Pack V2

Mon, 28 Jun 2010 15:31:14 GMT

Management pack to monitor the performance of a HP EVA SAN. Provides disk group latency and controller CPU monitoring and alerting and performance collection.

Pack Catalog: Top Processes Identifier Management Pack for Operations Manager 2007 and Essentials 2010

Fri, 25 Jun 2010 04:00:00 GMT

The Top.Processes.Identifier.MP.zip download contains both the management pack and a comprehensive management pack guide.

Pack Catalog: System Up Time Monitoring

Wed, 23 Jun 2010 19:53:33 GMT

Introduction to the System Up Time Monitoring Management Pack for Operations Manager 2007

The System Up Time Monitoring Management Pack leverages the Windows ‘System Up Time’ performance counter and is designed to help System Administrators with monitoring and reporting on planned and unplanned system reboots.

The System Up Time Monitoring Management Pack augments both the Windows Server Operating System Management Pack for Operations Manager 2007 and the

Windows Client 2000/XP/Vista Operating System Management Pack for Operations Manager 2007.

Three example scenarios are:

1. Run the System Up Time Report against a group of servers to validate they cycled as part of the required emergency security patch requiring a reboot.

2. Run the System Up Time Compliance Report against the ‘All Windows Computers’ group to show all computers not rebooting according to their daily, weekly, monthly, or quarterly reboot schedule.

3. Enable the System Uptime Weekly Reboot Monitor and receive an alert for a critical front end application server that didn’t complete a required system reboot after its backend system IPL completes on Sundays.

Document Version

This guide is based on the June 2010 System Up Time Monitoring Management Pack. Version 1.0.0.17

Supported Configurations

The System Up Time Monitoring Management Pack for Operations Manager 2007 is designed to monitor Windows Computers only and requires the prerequisite discovery of the Windows Computer base class.

The System Up Time Monitoring Management Pack supports all of the Windows platforms supported by System Operations Manager 2007 R2.

Getting Started

This section describes the actions you should take before you import the management pack, any steps you should take after you import the management pack, and information about customizations.

Note: All System Uptime Reboot Monitors are disabled by default. To enable Monitoring, please use overrides to enable monitoring for the systems desired.

Files to Download

To monitor System Up Time, you must first download the System Up Time Monitoring Management Pack. The System Up Time Monitoring Management Pack includes the files described in the following table. (Ideally, this MP should be sealed)

Filename	Description
System.Uptime.Monitoring.xml	System Up Time Monitoring (unsealed)
Or
System.Uptime.Monitoring.mp	System Up Time Monitoring (sealed)
OM2007_MP_SystemUpTime.doc	This management pack guide.

How to Import the System Up Time Monitoring Management Pack

For instructions about importing a management pack, see How to Import a Management Pack in Operations Manager 2007 (http://go.microsoft.com/fwlink/?LinkID=98348).

Note

Import the Windows Core Library before importing the System Up Time Monitoring Management Pack (System.Uptime.Monitoring.xml or System.Uptime.Monitoring.xml ).

Create a New Management Pack for Customizations

Below is Microsoft’s stated Best Practice:

Most vendor management packs are sealed so that you cannot change any of the original settings in the management pack file. However, you can create customizations, such as overrides or new monitoring objects, and save them to a different management pack. By default, Operations Manager 2007 saves all customizations to the default management pack. As a best practice, you should instead create a separate management pack for each sealed management pack you want to customize.

Creating a new management pack for storing overrides has the following advantages:

· It simplifies the process of exporting customizations that were created in your test and pre-production environments to your production environment. For example, instead of exporting a default management pack that contains customizations from multiple management packs, you can export just the management pack that contains customizations of a single management pack.

· It allows you to delete the original management pack without first needing to delete the default management pack. A management pack that contains customizations is dependent on the original management pack. This dependency requires you to delete the management pack with customizations before you can delete the original management pack. If all of your customizations are saved to the default management pack, you must delete the default management pack before you can delete an original management pack.

· It is easier to track and update customizations to individual management packs.

For more information about sealed and unsealed management packs, see Management Pack Formats (http://go.microsoft.com/fwlink/?LinkId=108355). For more information about management pack customizations and the default management pack, see About Management Packs in Operations Manager 2007 (http://go.microsoft.com/fwlink/?LinkId=108356).

Security Considerations

You may need to customize your management pack. Certain accounts cannot be run in an environment with minimal privileges or the account must have minimum permissions. Note: If you have imported the Microsoft Active Directory Management Pack, then the System Up Time performance counter is already being collected from Domain Controllers.

Computer Groups

You can use the following built in computer groups for leveraging the monitoring and reporting within this management pack. Or you can create your own groups (e.g. – Production IIS Servers). Groups must contain objects that are based on the Windows Computer class.

Computers Rebooted Groups

Group	Contents
Computers Rebooted Daily	This group can be populated either explicitly or by using dynamic rules to contain systems that have planned scheduled daily reboots. (86400 seconds or 1 day)
Computers Rebooted Weekly	This group can be populated either explicitly or by using dynamic rules to contain systems that have planned scheduled weekly reboots. (604800 seconds or 7 days)
Computers Rebooted Monthly	This group can be populated either explicitly or by using dynamic rules to contain systems that have planned scheduled Monthly reboots. (2592000 seconds or 30 days)
Computers Rebooted Quarterly	This group can be populated either explicitly or by using dynamic rules to contain systems that have planned scheduled Quarterly reboots. (7776000 seconds or 90 days)

Understanding Management Pack Operations

This section provides information about the types of objects the System Up Time Monitoring Management Pack for Operations Manager 2007 discovers, information about classes, how health rolls up, and monitoring scenarios.

Object Discovery

The System Up Time Monitoring Management Pack requires no discovery. However, the System Up Time Monitoring Management Pack depends on the Windows Computer Base class.

Key Monitoring Scenarios

The following table provides a summary of the monitors to be created for System Up Time and under which group they are configured.

Windows Computer Monitors

Name	Enabled	Type	Description
System Uptime Daily Reboot Monitor	False	Performance	This monitor checks the status of the System Up Time based on the Windows performance counter System: System Up Time. By default, this monitor is disabled. This monitor is configured with a threshold of 1 Day (86400 seconds) and is targeted towards computers in the ‘Computers Rebooted Daily’ group.
System Uptime Weekly Reboot Monitor	False	Performance	This monitor checks the status of the System Up Time based on the Windows performance counter System: System Up Time. By default, this monitor is disabled. This monitor is configured with a threshold of 7 Days (604800 seconds) and is targeted towards computers in the ‘Computers Rebooted Weekly’ group.
System Uptime Monthly Reboot Monitor	False	Performance	This monitor checks the status of the System Up Time based on the Windows performance counter System: System Up Time. By default, this monitor is disabled. This monitor is configured with a threshold of 1 month (30 Days or 2592000 seconds) and is targeted towards computers in the ‘Computers Rebooted Monthly’ group.
System Uptime Quarterly Reboot Monitor	False	Performance	This monitor checks the status of the System Up Time based on the Windows performance counter System: System Up Time. By default, this monitor is disabled. This monitor is configured with a threshold of 1 Quarter (90 days or 7776000 seconds) and is targeted towards computers in the ‘Computers Rebooted Quarterly’ group.

Windows Computer Rules

Name	Enabled	Type	Description
System Uptime Collection Rule	True	Performance	This rule collects the 'System Up Time' performance counter. By default it is configured to collect hourly.

Placing Monitored Objects in Maintenance Mode

Note: The System Up Time Monitoring and Reports may be affected when the System Uptime Collection Rule is unloaded. It may take up to an hour for the system up time value to be reflected correctly after the workflow is restarted.

When a monitored object, such as a computer or distributed application, goes offline for maintenance, Operations Manager 2007 detects that no agent heartbeat is being received and, as a result, might generate numerous alerts and notifications. To prevent alerts and notifications, place the monitored object into maintenance mode. In maintenance mode, alerts, notifications, rules, monitors, automatic responses, state changes, and new alerts are suppressed at the agent.

For instructions about placing a monitored object in maintenance mode, see How to Put a Monitored Object into Maintenance Mode in Operations Manager 2007 (http://go.microsoft.com/fwlink/?LinkId=108358).

Appendix: Reports

The following table summarizes the reports that are included in the System Up Time Monitoring Management Pack.

Reports

Name

Description

System Up Time Report

A general system up time report, chosen by computer group, containing computer name and system up time in descending order by longest up time. Best viewed as an excel spreadsheet.

Name

Description

System Up Time Compliance Report

Chosen by computer group like ‘All Windows Computers’, this report shows computers that have a system up time greater than desired. Best viewed as an excel spreadsheet.

Appendix: Views

The following table lists the views that should be created for the management pack.

Name

Type

Description

System Up Time Alerts

Alert

All alerts generated from the System Up Time Monitoring Management Pack

Name

Type

Description

System Up Time Performance

Performance

All System Up Time performance counters on all Windows Computers

Just a standard performance view.

Pack Catalog: SCC Health Check Management Pack Version 2

Tue, 22 Jun 2010 04:00:00 GMT

The version 2 of the MP contains 27 Reports!!! Which are required to run on the Datawarehouse or the Operational Database. There is documentation accompanied how to set up the solution and import the MP.

Please first read the documentation otherwise the MP will fail…..as you already know as SCOM Experts ;-)

If you have Feedback or addons to the MP please feel free to send them in!

Pack Catalog: SQL Server DB Mirroring Management Pack

Fri, 04 Jun 2010 04:00:00 GMT

The SQL Server DB Mirroring Management Pack discovers database mirroring components and provides probe based monitors to verify that database mirrors are operational. Optionally it verifies the roles and operating modes of mirrored databases against a Desired Configuration setting.

Currently Microsoft SQL Server 2008 (any edition) is supported. Support for SQL Server 2005 is planned for a future release if demand justifies the effort.

Use the SQL Server DB Mirroring Management Pack for:

Monitoring the availability state of mirrored databases and witnesses.
Monitoring if the mirrors are operating in line with a Desired Configuration definition.
View mirrored DBs as a service components and use them for Distributed Application designs.
Report on SQL database mirroring configuration.
Use the objects and groups discovered to add SQL database mirroring specific rules, monitors or overrides.

The Management Pack download contains a comprehensive guide that carefully lists all prerequisites. As a supplement it also contains an override MP that works in conjunction with the Extended Microsoft SQL Server MP hosted on OpsManJam. It shows how to use the discovered objects of the SQL Server DB Mirroring MP to parameterise existing or now MPs to support DB mirrors.

Download the SQL Server DB Mirroring Management Pack by clicking on the Download button in the upper right corner (bust be logged in - registration is free).

Pack Catalog: Windows Admin Tasks Management Pack

Tue, 01 Jun 2010 04:56:10 GMT

The Windows Admin Tasks Management Pack is designed to augment the Windows Base OS Management Pack by adding a number of useful and powerful tasks to the console. To make this easy, the tasks are all targeted to the Microsoft.Windows.Computer (Windows Computer) class, so you can use the Windows Computer view in the Default MP, which is also near the top of View tree in the Monitoring space of the console.

With that in mind, the tasks presented should work on about any OS that supports an OpsMgr agent.

For a full list and description of the tasks included, see the MP report and MP guide included in the zip file download.

Pack Catalog: Windows 2008 Active Directory Security Audit MP (for SCE 2010 and OpsMgr 2007 R2)

Sun, 18 Apr 2010 20:09:19 GMT

Update 6/30/2010 - Uploaded RTM version which includes a detailed management pack guide.

This management pack contains more than 40 audit rules (+ views and a report) designed to alert administrators to various changes in Windows 2008 Active Directory related to users, groups, group policies (GPOs), OUs and physical topology (sites, site links and subnets). Care has been taken to avoid the use of wildcards on description fields for better performance.

In fact, I made several design decisions to help scale and database space utilization.

It contains a seed base class (called Windows 2008 Active Directory Audit Target) so you can limit agents that load these workflows
Uses alert rules instead of event collection rules resulting in less space consumed in the operational and data warehouse data
Contains separate alert views for User, Group, OU, GPO, and Physical Topology events
Uses rules instead of monitors - audit events should NOT affect health of AD in my opinion! These are more for catching unauthorized changes.
Only DELETE operations generate critical alerts...all other generate warning alert
Currently contains a linked report for audit alerts. Will likely add custom reports to later versions.

NOTE: This is the official release, which includes a detailed management pack guide.

Pack Catalog: Logical Disk Extension Management Pack

Thu, 15 Apr 2010 04:00:00 GMT

22/06/10 - Version 1.2 Released

The download has been updated with the latest version of the MP. A number of people had reported issues with both reports which should now be resolved.

I have also had to change the certificate used to seal the management pack so if you were using the sealed version of the MP, you will need to export it before importing the new version. If you were using the unsealed version, you should be able to upgrade.

David

-----

This management pack is an extension management pack the collects detailed logical disk data, has a task that analyzes logical disks and contains views and reports to consume all the information collected.

Click the download button to download the ZIP file contains a sealed and unsealed copy of this MP. The ZIP file also contains documentation for the management pack which details what is in the MP and how it works. So full for details, download now :-)

Feel free to post any thoughts/comments/issues you have regarding this MP !

David

Pack Catalog: SQL Admin Extensions Sample Management Pack for OpsMgr 2007 and Essentials 2010

Tue, 13 Apr 2010 23:14:50 GMT

This management pack, which extends SQL monitoring to include identification of databases that have never been backed up, contains a script-based monitor, two views and a linked alert report that incorporates the class filter for the object picker.

For more information on the contents of this pack, see

SQL Admin Extensions Sample MP for OpsMgr 2007 and Essentials 2010

Pack Catalog: Free VMware ESX Monitoring (via vCenter / vSphere) from Quest

Sat, 06 Mar 2010 00:06:13 GMT

Quest is now offiering their QMX VMware extension is now free for vCenter and vSphere. You do need to install the QMX Base Framework first. Go to the QMX for Quest page by clicking the Download links to get the QMX Base Framework and QMX VMware extension

Pack Catalog: Free Cisco Catalyst 2950 Series Switch Management Pack from JAXMP

Mon, 22 Feb 2010 21:20:06 GMT

Cisco Catalyst switch monitoring and management directly from System Center Operations Manager is a reality with the Cisco Catalyst 2950 Series Switch Management Pack. Monitor all critical components of any Cisco Catalyst 2950 Series switch including Interfaces, Memory, Processor, Fan and Power Supply.

Absolutely no CLI or WMI is used to retrieve performance values from the switch. The Rules and Monitors are Native SCOM implementations and use SNMP to collect all performance and switch health data. Once the device has been discovered in SCOM, the Management Pack takes over and performs the specific switch discovery. After discovery, a native SNMP module is used within SCOM to collect values directly from the switch. You will never configure a login and password to access the switch. You will never have to import MIB files into WMI. All access performance data collection is through SCOM.

Polling interval and thresholds can also be overridden in SCOM to provide a more tailored environment. Click the Download button to get it from the source!

Pack Catalog: System.Performance.ConsecutiveSamplesCondition

Wed, 17 Feb 2010 05:00:00 GMT

System Performance ConsecutiveSampleCondition Management Pack Sample

This is a simple Management Pack the displays the use of System.Performance.ConsecutiveSamplecCondition module with the use of Microsoft.Windows.TimedScript.PerformanceProvider to create a custom script based counter.

A class with the name of TestConsecutiveSamples.Class.Servers was created to contain all windows servers which is populated with a registry based discovery named TestConsecutiveSamples.Discovery.Servers that used the registry key Software\Microsoft to find all objects that have Microsoft software installed. This discovery is targeted to Microsoft.Windows.Server.Computer to discover all servers. This discovery can be changed to suit different environments.

A Datasource is then created using the module Microsoft.Windows.TimedScript.PerformanceProvider. A simple script is added to create the custom counter.

Const SCRIPT_NAME = "Treshold.vbs"
Const EVENTNO_SCRIPT_STARTED = 8801
Const EVENTNO_SCRIPT_ENDED = 8899
Const EVENTNO_THRESHOLD = 8802
Const EVENTNO_SUBMITTING_DATA = 8898
 
Const EVENT_LEVEL_ERROR = 1
Const EVENT_LEVEL_WARNING = 2
Const EVENT_LEVEL_INFO = 4
 
Dim sComputer, IThreshold, bDebug
Dim oAPI, objFSO, sMessage, FileCount
 
sComputer = WScript.Arguments(0)
iThreshold = WScript.Arguments(1)
bDebug = CBool(WScript.Arguments(2))
 
Set oAPI = CreateObject("MOM.ScriptAPI")
 
sMessage = "Script started with following parameters: " & VbCrLf & _
                                                            "Computer Name: " & sComputer & vbcrlf & _
                                                            "Threshold : " & iThreshold
Call LogDebugEvent(EVENTNO_SCRIPT_STARTED,sMessage)
 
Call LogDebugEvent(EVENTNO_THRESHOLD,SCRIPT_NAME & vbCr & "Threshold " & iThreshold)
Set oBag = oAPI.CreatePropertyBag ()
CALL oBag.AddValue("Threshold",iThreshold)
 
Call oAPI.AddItem(oBag)
CALL oAPI.Return(oBag)
 
Call LogDebugEvent(EVENTNO_SUBMITTING_DATA,"Submitting Threshold PropertyBag data.")
 
Call LogDebugEvent(EVENTNO_SCRIPT_ENDED,"Process Threshold script ended.")
 
Sub LogDebugEvent(EventNo,Message)
 
                    Message = VbCrLf & "Calling MP Element ID: $MPElement$" & vbcrlf & Message
                    If bDebug = True Then
                    Call oAPI.LogScriptEvent(SCRIPT_NAME,EventNo,EVENT_LEVEL_INFO,Message)
                    End If
                   
End Sub

This script takes 3 parameters.

1. TargetComputer. This is not used.

2. SetThreshold. This parameter is used to populate a property bag to simulate a a custom Counter.

3. Debug. This is a bool parameter that allows you to switch on debugging so that you can see what the script is doing.

SetThreshold and Debug are both overridable properties.

The properties of the module are set as following.

The first 6 properties are standard for most script based modules so I won’t go into these. The next 3 you can give names appropriate to the custom counter you are creating. The last property, Value is the important one. This is the value that is compared to in the ConsecutiveSamplesCondition module. Complete the rest of the Datasource as required.

I then added a monitor type called TestConsecutiveSamples.MonitorType.ConsecutiveSampleCondition and to this I added to module that I had previously created and set the properties as required. Then I added the module System.Performance.ConsecutiveSamplecCondition. The properties were set as following.

Threshold is set to the default threshold that comes from the monitor, Direction is whether the custom counter must be less or greater than the default.

2 System.ExpressionFilter’s are then added to check the number of samples and according to the number of times overthreshold is detected the state of the object will be set. The rest of the monitor type is set as required.

A monitor is then created based on the monitor type just created and targeted to the class that was created.

To test the samples you can then override the SetThreshold property to above or below the threshold property.

Pack Catalog: NetApp Management Pack for SCOM 2007 R2

Wed, 27 Jan 2010 20:33:02 GMT

NetApp Management pack for System Center Operations Manager 2007 R2.

The management pack contains the discovery of NetApp components as well as some availability and disk space monitoring all being done by the use of SNMP.

For detailed information on the Management Pack see the series:

SNMP Management Pack example: NetApp Management Pack for System Center Operations Manager 2007 R2 – Part 1

SNMP Management Pack Example: NetApp Management Pack for SCOM 2007 R2 part 2

SNMP Management Pack Example: NetApp Management Pack for SCOM 2007 R2 part 3

SNMP Management Pack Example: NetApp Management Pack for SCOM 2007 R2 part 4

I have tested the MP in different areas and as soon as the filers are getting bigger the more probes are being send and the heavier the workload is going to be on both sides! Although the MP is more tuned then described in this series always be careful when importing management packs in you environments especially when it is production. If available always use a test environment to be sure you understand the management pack and it’s impact! Closely monitor your environment before, during and after to be sure no problems arise.

Regards,
Oskar Landman

(the Download includes both a sealed and unsealed version)

Pack Catalog: xSNMP Management Packs – Beta Version 1.0.8 Release

Tue, 26 Jan 2010 12:59:57 GMT

By Kris Bash, The latest beta of the xSNMP packs are available for download. The included documentation covers recommendations for deployment and configuration as well as the details of the management packs. Additional information about performance considerations in large SNMP monitoring environments can be found in this previous post. At present, the following management packs are included in this suite, and more are currently in the works.

xSNMP Management Pack – Implements filtered discovery and monitoring of SNMP devices and interfaces that support the standard RFC1213 MIB, IF-MIB, and EtherLike-MIB. This management pack is the core of the xSNMP Suite and contains public datasources that are utilized in the other optional management packs.
xSNMP Overrides Management Pack – This unsealed management pack can be used as a container for overrides, but also provides preconfigured groups and overrides for easily controlling interface monitoring through groups of network interfaces.
xSNMP APC Managment Pack – Implements monitoring for APC Rackmount PDU, UPS, Automatic Transfer Switch, and Environmental Monitor devices.
xSNMP Brocade Management Pack – Implements chassis monitoring for Brocade Fibre-Channel switch devices (Fibre-Channel ports are monitored as network interfaces with the xSNMP MP).
xSNMP Check Point Secure Platform Management Pack – Implements module health and firewall HA failover monitoring for Check Point Secure Platform firewall devices.
xSNMP Cisco Management Pack – Implements additional monitoring for Cisco devices, primarily including chassis hardware moniotring for devices that support the EnvMon MIB, Entity-MIB, or Cisco-Stack MIB.
xSNMP Data Domain Management Pack – Implements monitoring for the performance, hardware status, and replication status of Data Domain Restorer storage appliances.
xSNMP HP ProCurve Management Pack – Implements component health monitoring for HP ProCurve switches and wireless access points.
xSNMP HP Proliant Management Pack – Implements hardware health monitoring for SNMP-enabled HP servers that support the Proliant Insight Management Agents.
xSNMP Net-SNMP Management Pack – Implements operating system monitoring for Net-SNMP agent devices, such as UNIX/Linux servers through the UCD and Host-Resources MIBs.
xSNMP Syslog Management Pack – Provides warning and critical alert generating rules that can be enabled and filtered with overrides to alert on incoming syslog messages from discovered SNMP devices.