This page contains sample policies (for use with ovpmutil cfg pol upl convention) that you can work with.
| Policy ZIP file name | Description |
|---|---|
| NTP Compare | Policy that compares local system time to an authoritative NTP server. Multiplatform. |
| Multiple Directory File Count | Multiplatform policy that counts the number of files in a configured set of subdirectories. |
| MultiServiceCheck | Windows-only policy that checks if a group of services specified is running concurrently. Alerts if any group member isn't running. |
| FileCompare | Detects if two files on a system are the same or different, uses policy parameters for easy config |
| CriticalToNormalDetector | Detects when a message is changed from Critical status to Normal status. A good example of the OV_Message_SeverityChangeEvent. |
| DirectorySizeMonitor | Monitors the size of a directory and contents thereof. Works for UNIX, Windows and Linux |
| FileTimeStamp | Monitors if a file gets updated between samples (and alerts if it does not get updated). |
| Registry Change | Detects changes in a defined Registry Key - and notifies you when it changes. Sub-keys and values are monitored as well. |
| OVICPUCount | Discovers Intel Physical/Core/Logical (HyperThreading) CPUs and logs the inventory to the CODA DATASOURCE INTEL Object CPUTOPOLOGY - for Linux and Win32 systems using Genuine Intel CPU's only. This requires you install the included exe's into the appropriate instrumentation directories. |
| DiskSpaceMonitor-MultiPlatform | Farily sophisticated disk-space checker that uses the advanced policy objects and a perl script to monitor for a % of disk space used or a minium number of MB free. Also allows for filtering (include & exclude) of instances - uses the Policy "Script Parameters" editor for configuration. |
| Linux Process Monitor | Uses a perl script that calls top -b, then logs the resulting data to the CODA datasource LINUX object PROCESS. Includes a second sample policy to threshold process CPU Usage. |
| PortPing | TCP Port Connectivity Checker, uses the new policy parameter feature of OVOW 7.5 with path 210. This is a Perl policy that uses the Socket Perl module. |
| WebCheck | Web URL Checker, using the new policy parameter feature of OVOW 7.5 with patch 210 |
| Dell Storage Manager | Intercept SNMP Traps from Dell's Storage Management MIB |
| Adaptive Thresholds | Updated November, 2006 - now supports multi-instance CODA data collections. Automate thresholds to historical baselines using the advanced monitor capabilities of the OVO agent. Requires OVOW 7.5 with patch 210 and agent version 7.32 or higher. |
| NNM SPI | Monitors critical NNM Processes in a single policy. Requires OVOW 7.5 and agent version 7.31 or higher. |
| FileCount | Monitors the count of files in a specified folder. Utilizes the OVOW_000210 patch enhancement delivering policy parameters. You no longer have to edit the source script to change parameters of the policy. |
| HeartbeatRepeat | Repeats
"Heartbeat Polling" events that are active - making sure they
continually "nag" you. For OVOW 7.5, this will
increment the "duplicate" counter. You can add
an automatic action to call cdosend for this policy if you want e-mail
repeated.
ONLY INSTALL ON THE MANAGMENT SERVER. IMPORTANT NOTE: The management server agent must be reconfigured to avoid a message concatination problem with this policy - in the nodeinfo or opcinfo file, please specify the configuration parameter OPC_TRUNCATE_ORIG_TEXT 0 and RESTART the agent before using this policy. |
| AutoStartSvcMon.zip | Watches all auto-start services for state changes (running-> stopped, stopped->running) and sends correlated message when the state changes *only* |
| Liebert.zip | Converted Liebert
enterprise-specific SNMP Traps from the Liebert MIB's into an OVOW SNMP
Trap Interceptor policy. You must: a) Create an SNMP device that matches the liebert device's IP address and host name *exactly* in OVOW. b) Configure the Liebert management card to forward traps to an OVO Agent with this policy installed. |
| ReparseMon | Enumerates all local drives (C:\, D:\, etc) as well as locally mounted "Reparse" points. Instrumentation application driveenum.exe and a corresponding policy that calls driveenum and sends messages whenever a drive or Reparse point has less than a configured amount of free space. |
| DiskSpace.ZIP | Use the CODA FS_ objects to alarm on file system utilization. This means you don't need to use the LogicalDisk object anymore, removing a massive hassle from your configuration effort. Additionally, this approach will work with unix managed nodes as well |
| IntruderDetect.zip | Detect for a configurable number of failed logon attempts within a configurable time period. Utilizes a pattern match of the security log '529' events. Note: You must enable logging of logon failures in Windows for this policy to work. In other words, you have to log the event to catch the event. |
| Snapshots.zip | Excellent policies that monitor CPU usage and virtual memory usage. That's cool - but these go the extra mile to report the TOP 5 cpu users (for cpu usage) and the TOP 10 virtual memory users (for memory usage). New policy added to snapshots that monitors physical memory available, and reports the top 10 working set users. |
| OvTrapFwd.zip | Policy to take inbound Active Messages and send them to an snmp manager defined. The package includes an ole-automation trap sender (ovsendtrap.dll), an encoded cscipt file to retrieve the message details, and a sample policy. Read the readme.txt for instructions on how to install - this is not just a policy, but also a dll and a script that must be installed properly! |
| MS-03-039.zip | Measurement Threshold policy that verifies that the KB824146 hotfix is applied to Windows 2000 and 2003 systems. This script will ONLY work on Windows 2000 and Windows 2003 systems. |
| SvcMon.zip | Measurement Threshold policy
that detects Windows service failures - you specify the service to monitor
in the script, and the policy does the rest. This policy requires Windows 2000 or 2003 managed nodes (it will NOT work on NT4). Added bonus - this policy will detect "hung" services. |
| Heartbeat Failures.zip | WMI Policy to detect heartbeat failure messages sent by the Message Action Server "Health Checking" subsystem. These policies are logged directly to the management consoles. Modify this policy to add an automatic action to take when Heartbeat Polling failures are detected... add the automatic action of your choice - and BE SURE to check "send message only if the action is not successful". |
| Dell.zip | SNMP Interceptor (Not an event log policy, as ships with the product) for Dell servers. Based on OpenManage 4.3. Note, you must set "localhost" as the destination for traps on your snmp service, and deploy this policy to the server. |
| IBM.zip | SNMP Interceptor for IBM Director MIB - very simple implementation that generically handles the events by severity. Note, you must set "localhost" as the destination for traps on your snmp service, and deploy this policy to the server. |
| Lost and Found.zip | Monitors the Active Directory "Lost and Found" container. Tells you when you have lost and found items (conflicting change objects). |
| SourceCollection.zip | Demonstrates how to retrieve historical data from CODA to do time-series evaluations of performance data at the agent. This is a sample only, you will have to do the legwork! |
| ProcessMonitor.zip | Generic process monitoring policy that uses WMI, and a scheduled task policy with an embedded vbScript. Change the variable strProcName value to represent the full process name (with .exe extension) - and the number of expected processes to find (nExpected). If the policy doesn't find the expected number of processes, a Major alert message is created. The policy implements good/bad message correlation utilizing message keys |
| MissingProcess.Zip | This policy checks for a named process running on a Windows NT, 2K or 2k3. The policy does *not* utilize WMI, rather it utilizes the built-in real time performance measurement collections. It scans the list of active processes on the node, and if it does not find the process running, it will send a message to the active message browser. When the process appears, the message will be removed from the active message browser utilizing message key correlation. |
| Helpsystems-ROBOT.zip | SNMP Trap Interceptor policies for HelpSystems/ROBOT AS400 agents. Verified with ROBOT/V7. This provides basic event integration with AS400 systems. See www.helpsystems.com for more information. |
| FileSize.zip | This policy collects a single file, or multiple files, size and stores the result in CODA for graphing/reporting. This policy is currently set up to monitor "outlook.pst" but it can monitor any file or files you like. The files monitored MUST be local to the system where this policy runs (you cannot monitor files on network drives with this policy). This policy uses the FileSystemObject, as well as the StoreCollection mechanism provided by OVOW. |
| WinOSSPITopLogging.zip | New version of Win2K logging policy that only logs the top 10 processes to the performance component. This can reduce the reporter overhead for the WINOSSPI_Process table by as much as 80%. This will reduce network traffic, database size and the coda datafile size significantly on your managed nodes. This policy is *only* for windows 2000/2003 systems. It will not work for NT4 systems. This policy REPLACES the WINOSSPI-WINOS_Win2K_Logging policy, and will only work with OVOW 7.20 agents or higher. The version number is 9.4. |
| ExtServiceMon.zip | Generic Service
Monitoring policy. Tired of editing VBScript or command lines to identify the Service that you want to monitor? These sample policies use the POLICY NAME to specify the name of the Windows Service that you want to monitor. Note that the SERVICE NAME is used, this is different to the DISPLAY NAME (which is what you see in the services.msc applet). SERVICE NAMES do not normally include spaces...easier to handle in the script. |
| NetApp.zip | Policy that consumes known NetApp traps from NetApp NAS devices. Many thanks to DaveD for this contribution. |
| ProcessCreate.zip | Uses WMI "Intrinsic" event to detect the creation of a process within a 30 second sample period. To change the process name, change the condition in the policy - the default is "notepad.exe". |
| FindFiles.zip | Policy that looks for all files with a given extension (.csv by default, could be .bad, .err, .whatver) in a given folder (c:\temp by default). Sends a message to the active browser when it finds one or more files with the configured extension. If files are found, but then deleted/cleared, the message is automatically acknowledged. Uses the Start and End Actions, a Session variable, and the scripting.filesystemobject to find the files. |
| Brocade.zip | SNMP Interceptor Policies for Brocade MIB's version 3.1. We don't have a Brocade switch or a SAN (want to send us one? ;) ), so we were unable to test them directly! Instructions: Configure the brocade switch to send traps to an OpenView agent, deploy these policies to the same agent you send the traps to. |
| sqlsizemon.zip | Monitors all MS SQL Servers on a given system (excluding cluster virtual nodes). The policy monitors the overall database size as well as individual file group sizes. See the readme file for more information. |
| MultiPath.zip | Efficient policy that can monitor multiple processes (even processes with the same name) that start at different times throughout the day. Name, path, start and stop time can be specified to allow full customization. The default policy monitors three different processes independently with different schedules to check if they are supposed to be running, and if so send out an alert if the process goes down. Severity levels can also be set for "process down" alert. This policy runs as a scheduled task and can be ran throughout the day or at certain intervals. You can add additional processes to the script very easily - there really isn't a limit to the number of processes that can be monitored. |
| NNMTrapdLogger.zip | A set of policies for a simple (but very effective) NNM event feed to OVOW. The mainstay policy scrapes the NNM Trapd.log, a corresponding policy matches the IF up/down events and does message key (good/bad) correlation against them. You *MUST* create the snmp nodes in OVOW to match the hostnames seen in NNM - this is required - see the CreateSNMP tool in the node management section of OVInternls.com |