Using Serviceguard Manager

Monitoring with Serviceguard Manager

From a management station, connect to a Serviceguard node to be your session server. You can request to see all the clusters the server can reach, or you can list specific clusters. You can also request to see all the unused nodes on the subnet - that is, all the Serviceguard nodes that are not currently configured in a cluster.

Figure 1-3 Monitoring with Serviceguard Manager

Administering with Serviceguard Manager

You can also administer clusters, nodes, and packages if you have the appropriate access permissions (Serviceguard A.11.14 and A.11.15) or access control policies (Serviceguard A.11.16 and A.11.17):

Figure 1-4  Serviceguard Manager Package Administration

Configuring with Serviceguard Manager

With Serviceguard version A.11.16, you can also configure clusters and packages. Both the server node and the target cluster must have Serviceguard version A.11.16 or later installed, and you must have root (UID=0) login to the cluster nodes.

Figure 1-5  Configuring with Serviceguard Manager

Serviceguard Manager Help

To see online help, click on the “Help” menu item at the top of the screen.

The following help topics under “Using Serviceguard Manager” are especially valuable for new users of the interface:

How Serviceguard Manager Works

Serviceguard Manager from a Unix, Linux, or PC.

To start Serviceguard Manager on a Unix or Linux management station, type the sgmgr command. You can enter the options on the command line, or in a dialog box after the interface opens. For command syntax and options, enter man sgmgr on the command line.

To start Serviceguard Manager on a Windows management station, double-click the icon on your desktop. To see or change the actual command used, right click the icon and choose Properties. See online Help -> Troubleshooting for command syntax and options.

To open a saved “snapshot” cluster file, specify a filename with the .sgm extension; you must have view permission on the file and its directory. viewing the example files is a good way to get acquainted with Serviceguard Manager.

To see “live” clusters, connect to a Serviceguard node’s Cluster Object Manager (COM) daemon. (The COM is automatically installed with Serviceguard.) This node becomes the session server. It goes out over its subnets, and establishes connections with the COMs on other Serviceguard nodes. The session server relays commands from the management station to the target nodes, and relays the target nodes’ configuration and status data back to the management station. It also relays operation messages from the target nodes to the management station.

If the Session Server node is running Serviceguard versions A.11.13 through A.11.17, it will not be possible for the Session Server node to connect to cluster nodes running A.11.17 unless the server node has the Serviceguard Security Patch installed; the Security must also be enabled on that node. Also, refer to “Editing Security Files ” for access requirements.

To connect, you need to specify a valid username and password from the session server’s /etc/passwd file. List the cluster or clusters you want to see. Click “unused nodes” to see nodes that are not currently configured into a cluster, but do have Serviceguard installed.

For the session server to get information from a cluster, the target cluster must allow it access. The target node will resolve the session server’s hostname through /etc/hosts or DNS. Access method and non-root roles changed in Serviceguard Version A.11.16:

For information on access policies, refer to “Editing Security Files ”.

Using Serviceguard Manager, you can create or modify cluster and package configuration for clusters with Serviceguard Version A.11.16 or later, if you give the root (UID=0) password for a cluster’s node.