Serviceguard Manager Version A.05.02 Release Notes, March 2009

Installing with HP OpenView
When you install Serviceguard Manager, it looks to see if you have installed one of these OpenView products:
• NNM (Network Node Manager) Version 7.0, 6.31, 6.3, and 6.2.
• OpenView Operations Version 7.0 and 8.0. (OVO includes NNM.)
• VPO Version 6.0. Serviceguard Manager does not support VPW (Vantage Point for Windows) or
Operations for Windows.
If you have installed any of these, the install process automatically does these things:
• Adds a menu item and a button on the toolbar of NNM or OVO to start Serviceguard Manager
("Serviceguard Mgr Launcher").
• Sends Serviceguard events to be logged in the Event Log. The Serviceguard subagent is responsible
for notifying the management station when status or configuration changes. By default, it is installed in
/usr/lbin/cmsnmpd.
• Adds Serviceguard messages to the OVO Message Browser if assigned, and in the NNM Alarm
Browser.
• Modifies the Event Configuration Tool so you can set up automatic actions and filter Serviceguard
messages.
• Lets you configure the data collection to get historical MIB data from network nodes, including data
stored in Serviceguard MIB objects. The Serviceguard subagent services the Serviceguard MIB objects.
By default, it is installed in /usr/lbin/cmsnmpd.
NOTE: OpenView and NNM both support the Japanese language variables C and ja_JPSJIS. NNM
also supports ja_JP.eucJP, but OpenView does not support eucJP.
Then the installation process looks to see if you have OVO Version 7 or later, or VPO 6.0 or later. If you
do, it checks to see if you also have ClusterView.
If you do have ClusterView installed, no files will be overwritten. The launcher will be installed, so you can
open an instance of Serviceguard Manager from the OpenView menu.
If you do not have ClusterView, but you do have OVO, tools are added to the Tool Bank, ready for an
OpenView administrator to assign them. These tools are listed below.
Assign these tools carefully. Some require root access to the Serviceguard nodes, and some can grant it
indirectly.
• Serviceguard Mgr launcher: You can launch Serviceguard Manager from OpenView. Serviceguard
Manager is independent of OpenView. It does not use the OV daemons or object database to discover
the configuration or status of clusters. Instead, it gets information by connecting to Serviceguard Version
A.11.13.xx and later; then Serviceguard goes out on its subnets and gathers the information.
• Installs these Tools to work on a selected cluster node:
HA Info Tools:•
• Query Cluster Conf: uses cmquerycl to gather configuration information
• Scan Cluster: uses cmscancl to display information about cluster configuration, LAN cards,
disks, and file systems.
• View Cluster Binary Config: uses cmviewconf to see an ASCII extraction of the binary
configuration file.
• View Cluster Config: uses cmviewcl to see cluster configuration and status of running clusters.
• View System Log: opens vi editor to view /var/adm/syslog/syslog.log
• HA Admin Tools:
Run Cluster: uses the cmruncl command to start a cluster from the node you selected•
• Halt Cluster: uses the sghaltcl command (a variant of the cmhaltcl command) to halt
the cluster of the node you selected
26 Serviceguard Manager Version A.05.02 Release Notes