Node Management

Node Creation tools

ZIP Archive Name Description
CreateSNMP.ZIP Updated 3/26/04: Application that creates SNMP node objects in OVOW.  This tool runs on the management server and creates SNMP managed nodes with a simple UI, or if you wish, a command line interface.   See the readme file for installation instructions
ClusterXML.ZIP Updated 7/24/04 Application that creates an appropriate apminfo.xml file for Microsoft Clusters.  This app utilizes the cluster api set to connect to the Microsoft Cluster, and get the Group and Network names for all of the configuration groups.  At this point, the app only supports Microsoft SQL server as a clustered app.  If you want more, select the OVInternals output and send the contents of the dialog to tools@ovinternals.com.  This tool should only be used with MSSQL Server clusters at this point.
MaintMode.ZIP Set of script-based tools to disable policies/monitoring on a given node when maintenance is performed.  Read the readme for implementation details.
OVIOutage.zip New!  A service to maintain nodes in an "Outage" state.   The runtime is a native Windows .NET service that registers with the WMI providers of OVOW.  When nodes are marked "IN OUTAGE", incoming messages are automatically reclassified to unknown, owned, and acknowledged from those nodes.   This solution has multiple components.  As a sign of things to come, this solution REQUIRES the Microsoft .NET runtime to work.  If you can't do that, it isn't the solution for you.   See the readme.rtf for installation instructions.   

Updated August 26th, 2004 with a more efficient thread pool to handle message reclassification and acknowledgement.  We strongly suggest upgrading to this version (uninstall the previous version, re-install the new)

Updated August 2, 2005 with an enhanced caching mechanism for determining outage status.   This decreases overhead significantly for nodes not in outage.
OVBootup.zip Cleans out an existing agent configuration when the node it's on is renamed or sysprepped (which is a rename) the script cleans out all of the local configuration items for the agent, and then sets the notification up so the newly named node appears in "unmanaged nodes with agents" on the OVOW server.  The agent must be STOPPED when this script is run for it to work properly.  Then, when the agent starts, it notifies the server of it's new name and leaves the agent in an uninitialized state (no policies, etc) 

Download the scripts here:  nodescripts.zip

Use these scripts to list OpenView managed nodes & groups with various programmatic approaches. 

These scripts MUST be run with cscript.exe to display properly.   To make cscript.exe your default script engine, run cscript.exe /h:cscript.

The Scripts

Script Name (<mandatory parameters>) Description
UnMgdNodeList List all of the "Unmanaged Nodes with Agents" currently known to the management server.
LinkNode.vbs <node ID> <Group ID> Make an existing node a member of a specified node group.  The script works with the node ID (GUID) and the Group ID (GUID), so you must know these to utilize the script.
ListGroups.vbs List all of the node groups on the server, with member nodes.  This script recursively walks all of the node groups/sub groups configured.
ListGroupsMsgs.vbs List all of the node groups on the server, with member nodes.  Additionally, list the message count for each node.  This is handy to see where your messages are coming from.
NodeList.vbs List all of the configured nodes, using the WMI Instances_ collection
OvGrpNodeSync.vbs Verify that all managed nodes are in the appropriate OpenView Defined Groups for policy auto-deployments, etc.   When bulk importing nodes, this script will correctly locate nodes in the proper OpenView defined groups.
OvListNodes.vbs List all of the configured nodes, with all of the properties of an OV_ManagedNode object.   This is similar to NodeList, but more verbose.  Shows how to use the Properties_ collection to walk all available properties of an object.
NodeGroupsPolAssoc.vbs List all node folders, and prints out associated policy group depoloyment settings.  New and improved version correctly handles nested folders, and enhances speed.
GetNode.vbs Gets the node primary node name for a passed in Node ID.  Useful for looking up the nodename field from OV_Message.
GetNodeID.vbs Gets the node ID for a given primary node name.  Useful if you want to get the nodeID when you know the node name (primary node name).
RestartAgent.vbs <nodeid> Uses the opcRagt (OVOWRmtAgt) automation object to restart a remote agent based on its NODE ID... so now you can automatically restart a remote agent with a WMI policy.
The out-of-box opcragt requires the input of a DNS name.. this requires the input of the node ID instead.