Serviceguard Manager Version A.05.
© Copyright 2009 Hewlett-Packard Company Legal Notices Confidential computer software. Valid license from HP required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Table of Contents About This Document.........................................................................................................9 Publishing History..................................................................................................................................9 Typographic Conventions......................................................................................................................9 1 Serviceguard Manager Version A.05.02 Release Notes......................
JAGag00662 when adding two services in guided mode index number does not increment..............................................................................................................................37 JAGaf93917 Customer requests a native x86-64 version for Serviceguard Manager to be created...................................................................................................................................37 JAGaf92790: JRE security vulnerability in JRE 1.4.2_09 and earlier..........
JAGaf96075 - Illegal arg except when deleting a subnet with multiple NIC's.....................45 JAGag07974 - Problems after converting ctl script to ASCII style........................................46 JAGag08885 - HP-UX/Linux: typed target folder is ignored during save session...............46 Software Availability in Native Languages.....................................................................................
List of Figures 1-1 1-2 1-3 6 Serviceguard Manager: Tree and Map..........................................................................................13 Serviceguard Manager Admin menu............................................................................................14 Configuring Clusters with Serviceguard Manager (Nodes tab)...................................................
List of Tables 1-1 1-2 1-3 Accessing Serviceguard Manager.................................................................................................12 Capabilities of Session Servers on Target Clusters........................................................................20 Getting the Serviceguard Manager A.05.02 Software...................................................................
About This Document Publishing History Manufacturing Part Number Supported Operating Systems Supported Versions Publication Date B8325–90056 HP-UX 11.00 and greater, A.05.00 Linux, Windows 2000, 2003 October 2005 B8325–90061 HP-UX 11.00 and greater, A.05.01 Linux, Windows 2000 Service Pack 1 or later., 2003 February 2007 B8325–90066 HP-UX 11.
Enter The name of a keyboard key. Note that Return and Enter both refer to the same key. A sequence such as Ctrl+A indicates that you must hold down the key labeled Ctrl while pressing the A key. term Defined use of an important word or phrase. variable The name of an environment variable, for example PATH or errno. value A value that you may replace in a command or function, or information in a display that represents several possible values. An element used in a markup language.
1 Serviceguard Manager Version A.05.02 Release Notes Announcements Serviceguard Manager is the graphical user interface for the Serviceguard product. With it, you can monitor, administer, and configure clusters managed by Serviceguard, Serviceguard Extension for RAC, Metrocluster, Continentalclusters, and Serviceguard Extension for Faster Failover. NOTE: HP Serviceguard Manager has a web-based, (SIM) Systems Insight Management/System Management Homepage (SMH) application, version B.xx.
What's in Serviceguard Manager Version A.05.02 Two new features for version A.05.02 are: • • Serviceguard Manager Version A.05.02 now supports Windows Server 2008 Serviceguard Manager Version A.05.02 supports SIM 5.2 or later Depending on the number of clusters you want to manage at one time, as well as the version of the Serviceguard cluster node members, the appropriate version of Serviceguard Manager appears. Refer to table 1-1 for more information.
What You See The figure below shows an instance of Serviceguard Manager with two sessions. (Up to 10 sessions are supported.) The icon by the connection to both Session Servers show that the user's login is root. The Alerts button tells you there is information about serious alerts. We can see a red-bordered cluster is down. Also critical are the clusters that have a package icon with a red X, showing they have a package that is down.
You can issue common administrative commands on your clusters through Serviceguard Manager. (See below.) With Serviceguard A.11.16.xx and A.11.17.xx clusters, the administrator role is specified by configuring a non-root Admin Access Control Policy. Figure 1-2 Serviceguard Manager Admin menu Starting with Serviceguard Manager A.04.00 on HP-UX, you can configure clusters and failover packages on nodes with Serviceguard A.11.16.xx. Version A.05.0x, extends this to nodes with Serviceguard A.11.17.xx.
Figure 1-3 Configuring Clusters with Serviceguard Manager (Nodes tab) What You See 15
How it Works You can install Serviceguard Manager on a system running HP-UX, Linux, or Windows. From the system running Serviceguard Manager, you connect to a Serviceguard Node (HP-UX or Linux) to establish your management session. When you establish a Session Server connection, which is a cluster member node that the administrator connects to through Serviceguard Manager and displays the discovered clusters.
For information about Red Hat Linux, go to http://www.redhat.com For information about SUSE Linux, go to http://www.suse.com For information about HP OpenView Operations, IT/Operations, and Network Node Manager, refer to: http://www.docs.hp.com/hpux/netsys Further Information Additional information about Serviceguard and high-availability topics may be found on HP's web pages: http://www.docs.hp.com/hpux/ha (High Availability) and http://www.docs.hp.com/linux (Linux-specific).
Compatibility Information and Installation Requirements Before you begin an installation, read this entire document and any other Release Notes or READMEs you have. Compatibility This section summarizes the compatibility of this version of Serviceguard Manager with related products and their versions. For all versions (this and older), see the Serviceguard Manager Support Matrix posted on http://www.docs.hp.com/hpux/ha -> serviceguard -> white papers. Serviceguard Manager A.05.
Memory Requirements Running on HP-UX, these are the minimum requirements for Serviceguard Manager: • • • • • 256 MB of available memory 190 MB of available hard disk space under /opt 1 MB of available hard disk space under /usr 1 MB of available hard disk space under /etc/opt/OV if OpenView is installed. 315 MB of available hard disk space under /var for log files.
Requirements for Capabilities Starting with Serviceguard Manager version A.04.00, you can configure clusters and failover packages using nodes that have Serviceguard version A.11.16.xx. With Serviceguard Manager A.05.02, you can also configure clusters and packages on nodes with Serviceguard A.11.17.00 and A.11.17.01. Administration has changed from previous versions as well. Serviceguard version A.11.16.xx, A.11.17.00, and A.11.17.
Table 1-2 Capabilities of Session Servers on Target Clusters (continued) Session Server's Target cluster's Service- guard Service- guard version version To Monitor To Administer To Configure A.11.13.xx, A.11.16.xx, A.11.14.xx, and A.11.17.xx A.11.15.xx User can be any entry in Session Server's /etc/ passwd file Not supported Configuration menu available when an A.11.16.xx or A.11.17.xx object is selected User must supply root password for a cluster node User must log in to Session Server as root.
Each Serviceguard Manager node must allow these connections: • from the cluster nodes: — udp on port 162 • to the cluster nodes: — udp on port 161 Each Serviceguard node must allow these connections: • from the Serviceguard Manager node: — udp on port 161 • to the Serviceguard Manager node: — udp on port 162 • to the COM node: — tcp on port 5303 - and allow only packets with SYN flag.
• • • If you have an earlier version, uninstall it first before installing the new version. If you are on HP-UX and updating from A.03.00.01 or later, a prompt will offer to remove the earlier version for you, and then replace it with the new. 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 in A.03.00.01, and earlier settings cannot be carried over.
Before Installing Serviceguard Manager • • When deciding where to install Serviceguard Manager, plan for the security you want, and the access you will need. See the table Table 1-2 “Capabilities of Session Servers on Target Clusters” for more information. Consider the connections from users to the Session Server node, the connection from the Session Server to cluster nodes. Installing Serviceguard Manager on HP-UX You can install version A.05.
For more information about installation procedures and related issues, refer to the man page for swinstall.
Installing Serviceguard Manager on Linux You can install from two places: from the Distributed Components CD or from a browser • To install from the Serviceguard Distributed Components CD: 1. Insert the disk and mount the CD-ROM drive. Choose a name for your directory, for example . 2. From /SGManager/LINUX, enter: — For Red Hat Linux X86 and AMD64/Intel EM64T: rpm -i sgmanager-A.05.02.00-1.product.redhat.i386.rpm — For Red Hat Linux Integrity: rpm -i sgmanager-A.05.02.00-1.product.
changes in Serviceguard Manager Version A.03.00.01 and later. Your old preferences cannot be carried over. Installing Serviceguard Manager on Windows Install Serviceguard Manager on a computer that has Microsoft Windows 2000 Professional with Service Pack 1 or later, Windows XP Professional Edition, Windows 2003 Server or Windows Vista. NOTE: • If you currently have an older version of Serviceguard Manager, uninstall it first: Start -> Programs -> Serviceguard Manager -> Uninstall. 1.
NOTE: • Serviceguard Manager installs its own Java Runtime Environment (JRE) 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. • 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.
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.
Uninstalling Serviceguard Manager Before installing Serviceguard Manager A.05.02, uninstall any previous Serviceguard Manager versions. Uninstalling from HP-UX 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/).
1. 2. 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: — Syslog — SG_check_cmsnmpd — EMS SNMP Traps — HA Cluster SNMP Traps 3.
Setting up Serviceguard Manager Security, Logins, and Access Policies In version A.11.16.xx, Serviceguard changed its method of controlling and assigning logins, and roles. Therefore, the way you open Serviceguard Manager sessions and discover Serviceguard objects is quite different in versions A.11.16.xx and later than it is in earlier versions of Serviceguard. Logins and roles, Version A.11.16.xx and A.11.17.xx: Creating or modifying configuration still requires Root access (UID=0) on a cluster's nodes.
Bootstrapping a new A.11.16.xx or A.11.17.xx node If no cluster is configured, you can create a cmclnodelist file to act as a "bootstrap" for non-root access. Then other session server nodes have Monitor permission to access the node. Then you will be able to see it on the map and tree, and read its status and 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.xx or A.
If the user is logged in as root to a Session Server node with version A.11.15.xx 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.xx, A.11.14.xx, and A.11.15.xx.
Launching Serviceguard Manager from Linux 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.
— — — If you specify the -l option, you may also specify the -p option to give that user's password. The -c parameter specifies the clusters you want the Session Server to discover. (The Session Server can discover only the nodes on its subnets.) These clusters will be displayed on your map, under the Session Server's name. Repeat the -c option for several clusters in this session.
In non-English locales, when installing on HP-UX 11.11, install the TrueType Fonts patch: • HP-UX 11.11 — Japanese: PHSS_26971 — Korean: PHSS_26973 — Chinese-Simplified: PHSS_26975 — Chinese-Traditional: PHSS_24977 — Font Server: PHSS_25092 Before you use the Event Browser, install a patches on all HP-UX nodes in the clusters that will send the SNMP traps to your Serviceguard Manager Event Browser. The patch numbers are: • PHSS_27858 for HP-UX 11.
Known Problems and Workarounds The following lists known problems for Serviceguard Manager version A.05.02, at time of publication. This list is subject to change without notice. Contact your HP support representative for up-to-the-moment information. More recent information on known problems and workarounds may be available on the Hewlett-Packard IT Resource Center: http://www.itrc.hp.com .
JAGag47837 Launching interface of Serviceguard Manager needs to handle standalone/plug-ins What is the problem? When attempting to launch Serviceguard Manager from VSE Manager, a screen appears prompting you to select which Serviceguard Manager version you want to use. Typically you would use Serviceguard Manager A.05.02 for Serviceguard version A.11.17 and earlier or B.0x.xx for Serviceguard A.11.17.01 and higher. What is the workaround? There is no workaround.
What is the workaround? Use command line interface to re-name the package. Assuming XXX is the existing package name, and YYY is the new package name: 1. Log in to one of cluster nodes as root. 2) Create a temporary directory and cd to it. 3. Get package configuration:cmgetconf -p XXX >p.conf 4. Edit file p.conf: vi p.conf 5. Change the value ofPACKAGE_NAME from XXX to YYY. 6. Save the file. 7. Halt package XXX: cmhaltpkg XXX 8. Delete package XXX: cmdeleteconf -p XXX 9. Create package YYY: cmapplyconf p.
JAGaf43912 Cluster Properties: wrong lock info in older version of COM What was the problem? Versions of COM older than B.03.01 may display wrong information about the HP-UX cluster lock, because it may not support discovery of a Lock LUN. The COM (Cluster Object Manager) is a component of Serviceguard. What is the workaround? If you are using Lock LUN in a Linux cluster, upgrade COM to version B.03.01 or later. The COM (Cluster Object Manager) is a component of Serviceguard.
What is the workaround? To avoid permission problems, all interfaces for all authorized nodes must be defined in /etc/hostson all nodes within the cluster. All interfaces on all nodes that may be used as a Session Server, and all nodes that may be included in their session, must share all of each other's interface definitions. The name service switch policy for hosts must be set to files followed by any other sources used such as DNS, NIS or LDAP. Below is an example hosts file: 15.145.162.131 gryf.uksr.hp.
What is the workaround? The assertion error will create a log dialog window. You can click the continue button, and resume if this problem is encountered JAGaf32042 Standby LANs config does not work properly (See also JAGae87650) What is the problem? In the Serviceguard Manager A.04.00 and A.04.02 Cluster Configuration screens, once you deselect a standby interface, it will not allow you to reselect that standby interface. What is the workaround? There is no workaround.
What is the workaround? See JAGaf45963. All nodes that may be Session Server nodes, and all nodes that may be discovered in a Serviceguard Session, must have each other's networks in their /etc/hosts file. This includes private subnets. JAGaf11256 Serviceguard Manager won't discover nodes if another cluster has the same name. What is the problem? Once Serviceguard Manager discovers a cluster, it will ignore any others that have the same name.
JAGae50773 In non-English locales, installer shows "OK" in first panel What is the problem? When installing Korean, Simplified Chinese, and Traditional Chinese, the first panel in the installer gives the customer the local choice in a pull-down menu. The button beside the choose reads "OK" in all languages. This button should be localized, but is not. What is the workaround? To proceed with install, press "OK.
JAGag07974 - Problems after converting ctl script to ASCII style What is the problem? When a package is converted to ASCII style with the ctl script file name as /etc/cmcluster/pkg/pkg.sdf.sh. If a user edit the script, save changes, goes to another tab and then comes back to edit control script again, the control script name is automatically changed to /etc/cmcluster/pkg/pkg.sh. When user tries to apply the configuration, it fails saying cannot find /etc/cmcluster/pkg/pkg.sh on cluster nodes.
