Managing Serviceguard 11th Edition, Version A.11.16, Second Printing June 2004

Serviceguard at a Glance
Using Serviceguard Manager
Chapter 1 31
• “Menu and Toolbar Commands”
• “Navigating Serviceguard Manager”
•“Map Legend”
How Serviceguard Manager Works
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, check online Help -> Troubleshooting, or 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.
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 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: