|
|
United States-English | |
|
|
 |
|
Serviceguard Manager Version A.04.00 Release Notes > Chapter 1 Serviceguard
Manager Version A.04.00 Release Notes
Installing and Running Serviceguard Manager |
|
|
You can install Serviceguard Manager on an HP-UX workstation, on an HP-UX server (with or without Serviceguard), on a Linux workstation (with or without Serviceguard), or on a PC with Windows XP Professional Edition or Windows 2000 Professional. If a previous version of Serviceguard Manager is already installed, stop any instances of Serviceguard Manager running on a node before installing the new version there. See information about uninstalling below. When deciding where to install Serviceguard Manager, consider the connections from users to the Session Server node, the connection from the Session Server to cluster nodes, and creating the security you want. Which operators will use the interface, and which capabilities do you want them to have? Which management stations will they sit at, and which computer will they log into to begin a Serviceguard session? See the table Table 1-1 “Capabilities of Session Servers on Target clusters” for help in planning this. Serviceguard version 11.16 has a new way to setting up access. 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 a version of Serviceguard Manager earlier than A.03.00, your user preference files will be replaced with newer default settings. Preference files changed inA.03.00.01, and earlier settings cannot be carried over.
You can install version A.04.00 of Serviceguard Manager on a computer with bundles specifically for HP-UX Version 11.x
After swinstall completes, verify the installation:
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 Serviceguard Manager Version A.03.00.01 and later. Preferences from earlier versions 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. Install Serviceguard Manager on a computer that has one of these versions of Linux:
You can install from two places: from the Distributed Components CD or from a browser
After rpm completes, verify the installation:
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 Manager Version A.03.00.01 and later. Your old preferences cannot be carried over. Install Serviceguard Manager on a computer that has Microsoft Windows XP Professional Edition or Windows 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:
The SG Manager A.04.00 icon will appear on your desktop. Using Windows Explorer, verify that these folders are installed:
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 ServiceGuardManager is listed in Start -> Programs ->. Verify that a SG Manager A.04.00 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.01 and later. Your old preferences cannot be carried over. When you install Serviceguard Manager,it looks to see if you have installed HP Systems InsightManager, version C.04.01.00 or later. If you have, the ServiceguardManager install process automatically registers with InsightManager, and you can launch Serviceguard Manager from within InsightManager. If you want to install Insight Manager after you have Serviceguard Manager installed, no registration is done. In this situation, uninstall Serviceguard Manger, and then re-install it. When you install Serviceguard Manager, it looks to see if you have installed one of these OpenView products:
If you have installed any of these, the install process automatically does these things:
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.
On 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 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, /usr/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/users directory. On Windows, there are two ways to uninstall Serviceguard:
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. In Windows, by default, preferences are in: C:\Program Files\Hewlett-Packard\ServiceGuard Manager\users In 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 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.
In version A.11.16, Serviceguard changed its method of controlling and assigning logins, and roles. Therefore, the way you open Serviceguard sessions and discover Serviceguard objects is quite different in version A.11.16 and later than it is in earlier versions. Creating or modifying configuration still requires Root access (UID=0) on a cluster’s nodes. Starting in Serviceguard version A.11.16, however, a root user can configure clusters and packages using Serviceguard Manager or on the command line. In addition, there are four possible non-root roles that can be defined in the cluster’s configuration files. These can be specified as Access Control Policies in the cluster and package configuration files. Each Access Policy has three parts:
For more information about access control policies, see the online help for Configuring Clusters: Roles. If you upgraded a cluster to Serviceguard A.11.16, its cmclnodelist has been migrated into Access Control Policies. With A.11.16, cmclnodelist is gone. If your previous cmclnodelist file listed the pair <sess.server><user> your cluster configuration now has an Access Control Policy that lists this triplet:
If your old cmclnodelist had the wildcard +, the configuration file now has an Access Control Policy with wildcards in triplet:
Only a root user can modify configuration to change Access Control Policies. You do not have to halt the cluster, or any packages, to add, modify, or delete an Access Control Policy. If you have a cluster on an A.11.16 node, be sure to configure at least one Access Control Policy if you want to see the cluster and its nodes in Serviceguard Manager. Once a cluster is configured, Serviceguard will only check access in the cluster’s configuration files. It will ignore the .rhosts file and the cmclnodelist file. If no cluster is configured, you can create a cmclnodelist file to act as a “bootstrap” for access. Once done, you will be able to see information about the node on the Serviceguard Manager map and tree, and in Properties. If it is not a part of a cluster now, it will still show up in the Unused Nodes list. To configure it later, you can connect to a Session Server with Serviceguard version A.11.16, select the node from Unused Nodes, and select Configuration from the Actions menu. To create a bootstrap file:
Now you will be able to see your new A.11.16 node in a Serviceguard Manager session. If the Session Server also has version A.11.16, you can configure this node into a cluster. You will be prompted for the node’s root password. If you are an experienced Serviceguard user, you may think there is a similarity between the command-line user’s cmviewcl command and the way Serviceguard Manager user gets information about remote clusters with Serviceguard version A.11.15 and earlier. Using Serviceguard Manager, certain users can also relay the most common administrative commands to these Serviceguard clusters, and the effect seems 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. In version A.11.15 and earlier, the Serviceguard Manager user’s permissions depend on his login to the Session Server, not the cluster node. It is the Session 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 to directly access target nodes to do configuration of Serviceguard version 11.16. Users can log into a Session Server as any user. However, before the user can configure any object they see in the map or tree they must give a root password for at least one of the cluster nodes. If the target node has version A.11.15 or earlier, the Session Server node must always use user= root to access it. The recommended access mechanism is to include the Session Server name or IP address in the target nodes’ cmclnodelist file. A less secure way is to include the Session Server node in a target node’s .rhosts file. Listing in cmclnodelist allows contact to Serviceguard alone; a listing in .rhosts grants wider access. If the user is logged in as root to a Session Server node with version A.11.15 or earlier, the Session Server node will also display certain common administrative commands in the menu. The Session 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, A.11.14, and A.11.15. 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. If you wish, you can create a Serviceguard package that will keep the connection between your monitoring station and the Session 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 Session Server with Serviceguard A.11.13 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 Session 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.13 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.
When 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. If the Serviceguard Manager configuration gets lost or corrupted, follow these steps to restore the default configuration that came with Serviceguard Manager:
You can starting Serviceguard Manager directly from HP-UX, Linux, and from Windows.You can also start Serviceguard Manager from within HP Sytems Insight Manager or HP OpenView. To 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. To 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). 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 Here are 3 ways to launch Serviceguard Manager in Windows:
Within Insight Manager or OpenView, you can launch SGMgr from themenu bar or by clicking the SGMgr icon. When Serviceguard Manager installs, it checks to see if HP Insight Manager or OpenView are installed. If either are present, Serviceguard registers itself with the program. Therefore, if you have both, you want to install Serviceguard Manager after you installInsight Manager or OpenView. If you already have Insight Manager or OpenView installed, simply de-install Serviceguard Manager, then re-install it. 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.
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. When Serviceguard Manager opens, you have a chance to choose Connect or Open (unless you have already specified one of them in the command line). Use Open to see any saved “snapshot” file (one with .sgm extension). To get acquainted with the program, Open a supplied Example file. To see your own clusters “live”, use Connect. You need to have a logon for a node that is running Serviceguard A.11.13 or later. This will be your Session Server. It can discover clusters on its subnets, if they have granted it access. For the rules about access for admin capability, see Table 1-1 “Capabilities of Session Servers on Target clusters” Once you have a session open, open Help from the toolbar. Open the Getting Started topic from the Help window’s Table of Contents. Using Serviceguard is a good place to start. Map Legend explains status, colors, and symbols on the map. Select a tree or map object, and choose Properties from the Actions menu. Select a tree or map object and look at Actions. You will see Administration if you have permission. If you select an object with Serviceguard A.11.16, you will also see Configuration. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 Printable version |
|
|
|
|
|
|||||||||||||||
|
|||||||||||||||
