 |
» |
|
|
|
|  | |
Installing
Software | |
You can install ServiceGuard Manager on an HP-UX workstation
(with or without ServiceGuard), on a Linux workstation (with or
without ServiceGuard), or on a PC with Windows XP Professional Edition, Windows
NT, or Windows 2000 Professional. If a previous version of ServiceGuard Manager is already installed, uninstall
it before installing the new version. See information about uninstalling
below. Before
Installing ServiceGuard ManagerWhen deciding where to install ServiceGuard Manager, consider
the connections from users to the server nodes, the connection from
the server nodes to cluster nodes, and creating the security you
want. Which operators will use the interface,
and on which computers? To view a cluster, the ServiceGuard Manager
operator needs a logon and password on at least one server on the
cluster’s subnets. The server is a node with ServiceGuard
A.11.12 or later. To administer clusters on the map, these
three things must be true: The user is logged in to the server
node as root The server has ServiceGuard, Version A.11.14 or
later installed, with patches. The server node has Cluster Object Manager, Version
A.01.03.01 or later. The server node must be allowed to interact with
the target nodes.
Security Considerations If you are an experienced ServiceGuard user, you may notice
that the way a ServiceGuard Manager user gets information about
remote clusters is similar to the way a ServiceGuard command-line
user can issue the cmviewcl command to get information about a remote cluster. Using
ServiceGuard Manager, certain users can also relay the most common
administrative commands to ServiceGuard clusters, and the effect
is the same as logging into the node and issuing the command on
the command line. Please notice, however, that the permissions and access mechanisms are not the
same. The ServiceGuard Manager user’s permissions depend
on his login to the server, not the cluster
node. It is the server that interacts with the cluster nodes on
the user’s behalf, through the Cluster Object Manager,
a ServiceGuard API. A ServiceGuard Manager user does not need any direct access
to the target nodes that are displayed in the map. The configuration
and status information is collected by his server node and sent
back to the management station. The server node always accesses other ServiceGuard nodes as user=root.
The server needs access to the nodes. The recommended access mechanism
is to include the server name or IP address in the target nodes’ cmclnodelist file. A less secure way is to include the server node
in a target node’s .rhosts file. Listing in cmclnodelist limits contact to ServiceGuard; a listing in .rhosts grants wider access. If the user is logged in to the server node as root, the server
node will also display certain common administrative commands in
the menu. The server relays these commands to the clusters in the
session for the users. If you are updating from an earlier version, think about permissions on
your HP-UX nodes with ServiceGuard Version A.11.13 or later, with
Cluster Object Manager Version A.01.03.01 or later. Any person who
can log in to that node as root may be able to do administrative commands
on any cluster objects on that node’s subnets. If you do
not want access, you can limit the root logins on that node, or
limit that node’s access to particular clusters on its
subnets.
You can install ServiceGuard Manager on three platforms: HP-UX, Linux,
or Windows. The methods are slightly different for each. Use the section
below that is appropriate for your type of installation. There are two ways to install ServiceGuard Manager: from the
HP ServiceGuard Distributed Components disk, or from this web site: http://www.software.hp.com. You can choose the English, Japanese, Korean, Simplified
Chinese, or Traditional Chinese version. ServiceGuard Manager installs its own JRE (Java Runtime Environment™),
and can not use any other JRE that may already be installed. If you are updating from an earlier version, first uninstall
the earlier version. If you update from an earlier version of ServiceGuard Manager,
your user preference files will be replaced with default settings.
The new preference files are compatible with architecture changes
in ServiceGuard Version A.03.00 and A.03.00.01. Earlier preferences cannot
be carried over. | | | |  | NOTE: ServiceGuard Manager supports system default colors
for all platforms. Most system settings work, but a custom color
setup could cause problems. For example, you may see what seems
to be an empty box. However, when you drag the mouse to highlight
it, you may discover that your system is displaying white font on
a white background. If you restore the system to default colors,
you will be able to see things as they were designed. | | | | |
Installing
ServiceGuard Manager on HP-UX You can install Version A.03.00 or A.03.00.01 of ServiceGuard
Manager on a computer with bundles specifically for HP-UX Version
11.0 or 11.11. On 11.23 (11iv2), you can install ServiceGuard Manager A.03.00.01. Versions A.03.00 and A.03.00.01 of ServiceGuard Manager are
not supported on HP-UX 11iv 1.6 (11.22). The ServiceGuard Manager
depot for 11iv6 (on the HP Distributed Components Disk or http://software.hp.com) automatically installs ServiceGuard Manager Version
A.02.01. The Release Notes for version A.02.01 are on the HP Distributed
Components Disk, and at http://docs.hp.com -> high availability. For 11iv2, you can only install from the web. For other configurations, you
can install from two places: To install from the HP ServiceGuard
Distributed Components disk: Mount the CD-ROM directory, choosing
/SD_CDROM for your mount directory. Enter the swinstall command. When the window opens, set Source Depot Type to: LocalCDROM. For Source Depot Path, fill in the appropriate release name.
For example, if you have HP-UX 11.22, use: SD_CDROM/SGManager/HP-UX/11.22/sgmanager.depot swinstall allows you to select: B8325BA A.03.00 ServiceGuard Manager or B8325BA A.03.00.01 ServiceGuard Manager for HP-UX 11.00 and HP-UX 11.11. (For HP-UX 11.22,
select B8325BA A.02.01 ServiceGuard Manager). Select the appropriate platform, then start
the install.
To install from the web, go to http://www.software.hp.com. Click High Availability, then ServiceGuard Manager for
HP-UX. Fill out the information form. A download window opens. Select your operating system from the “Software
Specification” pull-down list. (To see the version of HP-UX,
use the uname command.) Available versions are HP-UX 11.00, 11.11,
11.22, and 11.23 (11iv2). The 11.22 build will install ServiceGuard Manager
A.02.01, the only version available for 11.22. The 11.0, 11.11,
and 11.23 (11iv2) build can install ServiceGuard Manager A.03.00
or A.03.00.01. The 11.23 (11iv2) build can install A.03.00.01. Download the depot, and
store it on your disk, perhaps in the /tmp directory. To save disk space, you can remove this depot from
your disk when you have finished installing. Run the swinstall command on this depot. The user interface will lead you
through the installation (mark, analyze, install). Select the B8325BA ServiceGuard Manager product. Depending on your operating system, choose B8325BA_11.00, B8325BA_11.11, B8325BA_11.22 or B8325BA_11.23.
After swinstall completes, verify the installation: Is the man page installed? (Enter: man sgmgr) Was the directory created for log files? (Enter: ll /var/opt/sgmgr) Are all the program files in the installation directory?
If you install in the default directory, you should see the following
when you enter ll /opt/sgmgr/* : OV (if HP OpenView is installed)
ServiceGuard Manager installs its own JRE (Java™ Runtime Environment)
and cannot use any other JRE on the computer. If you are updating from an earlier version of ServiceGuard
Manager, your user preference files are replaced with default settings.
The new preference files are compatible with architecture changes
in ServiceGuard Manger Version A.03.00. Your old preferences cannot
be carried over. If you have Network Node Manager or OpenView Operations installed on
this computer, also see the section below, Installing
with HP OpenView. For more information about installation procedures and related
issues, refer to the man page for swinstall. Also see the manual Managing HP-UX Software
with SD-UX , which can be viewed or printed from http://www.docs.hp.com
-> HP-UX 11.0 Operating System -> System Administration. Installing
ServiceGuard Manager on LinuxInstall ServiceGuard Manager on a computer that has one of
these versions of Linux: Red Hat Linux, version 7.1 or later,
with kernel version 2.4.2 or later. SuSE Linux, SLES (Linux Enterprise Server), version
8, United Linux version 1.0, with kernel version 2.4.19-64GB-SMP.
(SuSE is available only in English.)
You can install from two places: from a disk or from a browser To install from the ServiceGuard Distributed
Components CD: Insert the disk and mount the CD-ROM
drive. Choose a name for your directory, for example </SGM_ROM>. From </SGM_ROM>/SGManager/LINUX, enter: rpm -i sgmanager-A.03.00-1.product.redhat.i386.rpm or rpm -i sgmanager-A.03.00.01-1.product.redhat.i386.rpm rpm -i sgmanager-A.03.00.01-1.product.suse.i386.rpm
To install from the web: Go to http://www.software.hp.com Click High Availability. Click ServiceGuard Manager in
the alphabetical list. Save the sgmanager-A.03.00-1.product.redhat.i386.rpm file to your disk. (To save disk space, you can remove
the rpm file when installation is done.) From the directory where you saved the file, run
the install process with this command: rpm -i sgmanager-A.03.00-1.product.redhat.i386.rpm For SuSE Linux
(English only):
rpm -i sgmanager-A.03.00-1.product.suse.i386.rpm
After rpm completes, verify the installation: Is the man page is installed? (Enter: man sgmgr) Are all the program file directories in the installation
directory? By default, the Red Hat default directory is /usr/local/sgmgr/. By default, the SuSE install directory is /opt/sgmgr/.
ServiceGuard Manager installs its own JRE (Java Runtime Environment™)
and cannot use another JRE already installed on the computer. If you are updating from an earlier version of ServiceGuard
Manager, your user preference files are replaced with default settings.
The new preference files are compatible with architecture changes
in ServiceGuard Version A.03.00 and A.03.00.01. Your old preferences cannot
be carried over. Installing
ServiceGuard Manager on WindowsInstall ServiceGuard Manager on a computer that has Microsoft
Windows XP Professional Edition, NT 4.0 (or later), or 2000 Professional
installed. If you currently have an older version of ServiceGuard
Manager, uninstall it first: Start -> Programs -> ServiceGuard
Manager -> Uninstall. You can install from two places: To install from the ServiceGuard Distributed
Components CD: Insert the disk in the PC’s
drive Click the Start menu in lower left corner of your
screen. Choose Settings -> Control Panel. Double-click
Add/Remove Programs. Click on Install. Navigate to SGManager\Windows. Select sgmanager.exe. Click Finish and follow installation directions.
To install from the web: Go to http://www.software.hp.com. Click
High Availability, then ServiceGuard Manager. Click on the link under Download Software (sgmanager.exe). You can store the file on your system, or run it
directly from the website. If you download to your system, you can
remove it after installation. On your PC, run sgmanager.exe (or double-click the sgmamager.exe
file in Explorer). Choose a language option. The default install directory
is: C:\Program Files\Hewlett Packard\ServiceGuard
Manager\ but you can choose a custom installation directory.
The ServiceGuard Manager icon will appear on your desktop. Using Windows Explorer, verify that these folders are installed: ov (if OpenView Network Node Manager is already
installed on the PC)
ServiceGuard Manager installs its own JRE (Java Runtime Environment™)
and cannot use any other JRE already on the computer. If you have Network Node Manager installed on this computer,
see Installing with OpenView, below. Verify that the name ServiceGuard Manager is listed in Start
-> Programs ->. Verify that a ServiceGuard Manager
icon is on your desktop. If you are updating from an earlier version of ServiceGuard
Manager, your user preference files are replaced with default settings.
The new preference files are compatible with architecture changes
in ServiceGuard Manager Version A.03.00 and A.03.00.01. Your old preferences
cannot be carried over Installing
with HP OpenViewWhen you install ServiceGuard Manager, it looks to see if
you have installed one of these OpenView products: NNM (Network Node Manager) Version
6.x or later ITO (IT/Operations) Version 5.3 or later (ITO includes
NNM.) OpenView Operations Version 6.0. (OVO includes
NNM.) ServiceGuard Manager does not support VPW (Vantage Point 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, ITO, 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 ITO or 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.
Then the installation process looks to see if you have OVO
or ITO Version 5.3 or later. If so, 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 ITO or 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.12
or greater; 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: Cluster Admin: opens SAM to the ServiceGuard
cluster administration section Cluster Config: opens SAM to the ServiceGuard cluster configuration
section Package Admin: opens SAM to the ServiceGuard package administration
section Package Config: opens SAM to the ServiceGuard package configuration
section 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 Run Node: uses the cmrunnode command to join the selected node to its cluster Halt Node: uses the cmhaltnode command to make the selected node inactive in its cluster
Net Diag Tools View Interface Config: displays LAN
interface configuration parameters LAN Diag and Admin: launches the program lanadmin, which administers and tests the local area network. Scan LAN interfaces: uses lanscan to display information about each LAN device that has
software support on the system. IP Interface Stat: uses netstat to display statistics for network interfaces and protocols,
as well as the contents of various network-related data structures.
(Choose options to filter output.)
LVM tools. View Logical Volumes: displays the
logical volumes currently configured View Volume Groups: uses vgdisplay to show information about the volume groups configured.
Uninstalling
ServiceGuard ManagerOn HP-UX, uninstall ServiceGuard Manager by running this command: swremove B8325BA After uninstalling ServiceGuard Manager, you can remove the ServiceGuard
Manager logs; if you are not going to re-install, you can remove
the entire directory (by default, /var/opt/sgmgr/). If you are not going to re-install, you can also remove
the preferences that are stored in the user’s home directory,
under the .sgmgr directory. On Linux, uninstall ServiceGuard Manager by running this command: rpm -e sgmanager-A.03.00-1 or: rpm -e sgmanager-A.03.00.01-1 After uninstalling, you can remove the ServiceGuard Manager
logs; if you are not going to re-install, you can remove the entire
directory (by default, /user/local/sgmgr on Red Hat and /opt/sgmgr on SuSE). If you get a message about “unable
to remove.” you can ignore the ones about error messages.
If you are not going to reinstall, you can remove the preferences
that are stored in the user’s home directory, under the .sgmgr
directory. Uninstalling
from Windows On Windows, there are two ways to uninstall ServiceGuard: From the Start menu, choose Programs
-> ServiceGuard Manager -> Uninstall. From the Start menu, choose Settings -> Control
Panel -> Add/Remove Programs. Select ServiceGuard Manager
from the list.
After uninstalling ServiceGuard Manager, you can delete the
log files; if you are not going to re-install, you can remove the
entire directory: C:\Program Files\Hewlett-Packard\ServiceGuard Manager\log folder. If you are not going to re-install, you can also
remove the user preferences folder. By default, preferences are
in: C:\Program Files\Hewlett-Packard\ServiceGuard Manager\users Removing
ServiceGuard Manager - OpenView IntegrationIn addition to doing the swremove of ServiceGuard Manager, you need to manually do the
following things if you integrated ServiceGuard Manager into OpenView. If you have NNM only (not OVO): Remove event templates: Go to the NNM
or ITO menu and select Options -> Event Configuration.
From the list, delete the following event groups: Remove SGMgr MIBs: Go to the NNM or ITO menu and
select Options -> Load/Unload MIBs:SNMP. Unload the following MIBs:
If you have OVO (which includes NNM): Remove messaging: Go to the Message
Group Bank, and delete Message Group HA. Remove templates and monitors: Open the Message
Source Templates window. By default, the following are visible on
the top level. Remove them: Remove Application Tools: From the Application Bank,
remove these tool groups:
Uninstalling:
Removing SNMP Trap DestinationsIf you are not going to re-install, and you do not wish to
receive SNMP traps anymore, you need to “unset” the
trap destinations on the sending nodes. First get a list of the nodes that
are sending traps to your computer. Select Event Browser from the
View menu. Click the Configuration tab. Make a note of the nodes
and IP addresses. Notice that the configuration tab shows only the nodes in
your current map. If you have several subnets, connect to a server (Cluster
Object Manager) in each, and use the Discover All option. Log in to each node and edit the /etc/snmpd.conf
file to remove your computer from the list. Stop and re-start the SNMP Master Agent on the node. Find the process ID number, using: ps -ef | grep snmp. The master agent will show as snmpd, and the subagent will show as cmsnmpd. Stop that process, using: kill <pid> Restart the agents. Use: /sbin/init.d/SnmpMaster start for the master agent Use: /sbin/lbin/cmsnmpd for the subagent.
Setting
up ServiceGuard Manager | |
Making
a Highly Available ConnectionIf you wish, you can create a ServiceGuard package that will
keep the connection between your monitoring station and the server
highly available. If there is a failure in the connection, you might
see the “Connection Dropped” message flash momentarily,
but ServiceGuard will maintain your connection. It will fail the
connection over from one node in a ServiceGuard cluster to another
node in the same cluster. ServiceGuard Manager gets its information by connecting to
a server with ServiceGuard A.11.12 or later. A component of ServiceGuard,
the Cluster Object Manager, polls the available subnets to discover
other ServiceGuard objects. It collects status and configuration
information, and sends the information back to ServiceGuard Manager. To set up the highly-available connection between ServiceGuard Manager
and server nodes in a cluster, follow these steps: Create the package in a cluster with ServiceGuard. For viewing,
use ServiceGuard A.11.12 or later. For administration commands use ServiceGuard
A.11.14 or later. See “Creating the Package Configuration” chapter
in the ServiceGuard manual. All ServiceGuard manuals are posted
on the web and you can view or print them there. Go to http://www.docs.hp.com and click High Availability; the products are listed alphabetically. Get an IP address to use as the package’s
relocatable address. You can use nslookup to be sure the package name and IP address are correctly
associated in your DNS table. When naming the package, choose one that your users
will recognize, such as Clus3Srvr. The first time a user opens ServiceGuard Manager they
will see the Connect dialog box. They can type this name in for
Server. After that, the name will appear in a list every time that
user opens ServiceGuard Manager. Make only these two modifications to the package
configuration file template, and leave the defaults for the other
fields: List the package nodes. For high-availability,
it is best to list all the nodes in the cluster. For the run and halt scripts pathname, specify the
control script name and path for the run and halt script. (The default
path is in the documentation.)
Open the control script template. Make just two
modifications. These will allow the connection between your client
(ServiceGuard Manager station) and the server (ServiceGuard A.11.12
cluster): Insert the IP address associated with
your package (the package’s relocatable address). Insert the address of the subnet.
Assigning
and Configuring New OpenView OVO/ITO ToolsWhen you install ServiceGuard Manager, it checks to see if
you have OpenView OVO installed. If you do, it checks to see if
you have the tools listed in “Installing with HP OpenView” above.
If you do not have those tools, it installs them for you. The ITO tools are installed like other OpenView applications:
SD control scripts place the files on the system and register both
the back end and the front end with OpenView. The OpenView configuration
is customized for user opc_adm only. The ITO Administrator is responsible for assigning
access privileges and responsibilities. To
Restore Default ConfigurationIf the ServiceGuard Manager configuration gets lost or corrupted,
follow these steps to restore the default configuration that came
with ServiceGuard Manager: Exit all ITO user sessions. Stop the ITO server process with the /opt/OV/bin/ovstop opc command. Go to /opt/sgmgr/OV and untar the configurations files in with the tar -xvf ito-ux.tar command. Go to /opt/OV/bin/OpC and upload the new configuration with the opccfgupld -replace -subentity /opt/sgmgr/OV/SGOpC command. Stop and restart the ITO package with the /opt/OV/bin/OpC/opcsv -stop and /opt/OV/bin/OpC/opcsv -start commands.
Launching
ServiceGuard Manager | |
You can starting ServiceGuard Manager directly from HP-UX,
Linux, and from Windows. You can also start ServiceGuard Manager
from within the HP OpenView and ServiceControl Manager applications. Launching
ServiceGuard Manager from HP-UXTo launch ServiceGuard Manager, standalone, in HP-UX, go to
the ServiceGuard Manager directory (by default, /opt/sgmgr/bin) and enter the sgmgr or ./sgmgr command, plus any options you want. To see the full command,
enter man sgmgr. The options are also listed below in sgmgr
Command Syntax. You can also create a script or alias that includes the options
you want. Launching
ServiceGuard Manager from LinuxTo launch ServiceGuard Manager in Linux, go to the ServiceGuard Manager
directory (by default, Red Hat is /usr/local/sgmgr/bin and SuSE is /opt/sgmgr/bin). (SuSE is available only in English.) Enter the sgmgr or ./sgmgr command, plus any options you want. To see the full command,
enter man sgmgr. The options are also listed below in sgmgr Command
Syntax Launching
ServiceGuard Manager from WindowsHere are 3 ways to launch ServiceGuard Manager in Windows: By default, a shortcut icon is placed
on your desktop (labelled SG Manager A.03.00 or SG Manager A.03.00.01).
Click it to launch the program. When installed, it has the simple
command without options. You will be prompted to enter the options
once the program opens. You can modify the icon’s properties
to use any of these options: your name, password, server to connect
to, and clusters to discover. If you want to modify it follow the
steps below: Right-click on the icon, then choose
Properties from the popup menu. Add options to the command in “Target.” The
options are listed below in sgmgr Command Syntax. It is best to put quotes around command and file path names; Windows
allows spaces and other characters in directories, and that could
cause parsing errors.
From the Start menu, select
Programs -> ServiceGuard Manager. This launches the simple
command, with no options. Open a DOS window. At the DOS
prompt, enter the SGMgrDOS.exe command. Depending on your system path setup, you may
have to enter the SGMgr directory (by default C:\Program Files\Hewlett-Packard\ServiceGuard
Manager\bin). You can also enter options, as listed below
in sgmgr Command Syntax. It is best to put quotes around command and file path names.
Launching
ServiceGuard Manager from HP OpenView Within OpenView, you can launch SGMgr from the menu bar or
by clicking the SGMgr icon. Launching
ServiceGuard Manager from ServiceControl ManagerIf you have ServiceControl Manager installed, you will find
a ServiceGuard Manager tool. Click this tool icon to launch the
interface. The basic command to launch ServiceGuard Manager in Linux
or HP-UX is sgmgr. In Windows, it is SGMgr.exe or SGMgrDOS.exe. The options are listed below. If you do not mention
an option with the command, you will be prompted to specify it in
a window after the interface opens. To open a saved (static) file: The -f <filename> option opens a saved .sgm file. Enter the pathname
of the saved file, in quotes. This option is not used with any other
options.
To open a server connection
and see a map that you can update; repeat these options for each
session: The -s <servername> option specifies a node with ServiceGuard A.11.12
or later. Your ServiceGuard Manager session will connect to ServiceGuard
on this node. ServiceGuard will start an Object Manager process
to discover the other clusters on its subnet, and report back their
configuration and status information. If you specify the -s option, you may also specify
the -l <username> option to give the logon name of a user on
that server. If you specify the -l option, you may also specify
the -p <password> option to give that user’s password. The -c <clustername> option specifies the clusters you want the server
to discover. (The server can discover only the nodes on its subnets.)
These clusters will be displayed on your map, under the session
with the COM server’s name. Repeat the -c option for several
clusters in this server’s session. Specify -un TRUE to see the unused nodes discovered
by this server on the server’s subnets. These are nodes
that have ServiceGuard installed, but are not currently configured
in any cluster.
To open another session, repeat these steps.
When the interface opens, you will see what you have chosen,
and you will be given a chance to fill in any options you have not
yet chosen. Using
the Interface | |
When ServiceGuard Manager opens, you have a chance to choose Connect
or Open (unless you have already specified one in the command line). To get acquainted with the program, Open a supplied Example
file. To see your own clusters, use Connect. You need to have a
logon for a node that is running ServiceGuard A.11.12 or later.
This will be your server. It can discover clusters on its subnets,
if it has node access permission, as root, in cmclnodelist or .rhosts. If you want to also do administrative commands, you
need to log on, as root, to an HP-UX server node that is running
ServiceGuard A.11.14 or later. (See “Required and Recommended
Patches” in this document.) Once you have a map in place, open Help. Open the Getting
Started topic from the Help window’s Table of Contents
in the left pane. Open the Map Legend topic to interpret the colors. There are Help topics about troubleshooting clusters and troubleshooting ServiceGuard
Manager itself. Right click on a tree or map object, and choose “Properties
of <object>” from the popup menu. Each
tab in Properties has its own Help button. that briefly describes
each property. Right click a tree or map object and look at the popup menu
again. You will see which administration commands can be done on
this cluster object at this time if you have root permission on
an HP-UX server with ServiceGuard A.11.14 or later. (See “Required
and Recommended Patches” in this document.) |
Printable version
