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................................
JAGaf73681: Creating "ASCII" style pkg fails with "no script found" error.....................................35 JAGaf83497: Serviceguard Manager tooldef for SIM needs tag.....................................35 Known Problems and Workarounds...............................................................................................35 QXCR1000898799 SMH SSO section not rendered in SIM content frame on FireFox.....................
List of Figures 1-1 1-2 1-3 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, Linux, Windows 2000, 2003 A.05.00 October 2005 B8325–90061 HP-UX 11.00 and greater, Linux, Windows 2000 Service Pack 1 or later., 2003 A.05.01 February 2007 B8325–90066 HP-UX 11.
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.
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. 14 Serviceguard Manager Version A.05.
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 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). Support information is available from the Hewlett-Packard IT Resource Center at: http://itrc.
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.
Session Server's Service- guard version Target cluster's Service- guard version To Monitor To Administer To Configure A.11.16.xx, A.11.17.xx A.11.13.xx, A.11.14.xx, and A.11.15.xx User can be any entry in Session Server's /etc/passwd file User must log in to Session Server as root. not supported Target must have in cmclnodelist file. Target must have root in cmclnodelist file. A.11.16.xx, A.11.17.xx User can be any entry in Session Server's /etc/passwd file A.11.
The node running the COM must allow these connections: ▲ from Serviceguard Manager to the COM node: • ▲ from cluster nodes to the COM: • ▲ tcp on port 5303 - and allow only packets with the SYN flag tcp and udp on port numbers 49152-65535 from the cluster nodes to the cluster nodes • tcp on port 5302 - and allow only packets with the SYN flag • udp on port 5302 Each cluster node should allow SNMP connections between it and the Serviceguard Manager node.
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.
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.
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. Decide from where to get the Serviceguard Manager A.05.02 software: Table 1-3 Getting the Serviceguard Manager A.05.
Installing with HP OpenView When you install Serviceguard Manager, it looks to see if you have installed one of these OpenView products: • NNM (Network Node Manager) Version 7.0, 6.31, 6.3, and 6.2. • OpenView Operations Version 7.0 and 8.0. (OVO includes NNM.) • VPO Version 6.0. Serviceguard Manager does not support VPW (Vantage Point for Windows) or Operations for Windows.
• • • 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.
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/).
3. • EMS SNMP Traps • HA Cluster SNMP Traps Remove Application Tools: From the Application Bank, remove these tool groups: • HA Info • HA Admin • LVM • Net Diag Uninstalling: Removing SNMP Trap Destinations 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. 1. First get a list of the nodes that are sending traps to your computer. Select Event Browser from the View menu.
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.
Making a Highly Available Connection 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.
1. 2. Right-click on the icon, then choose Properties from the popup menu. Add options to the command in "Target." The options are listed 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.
Using the Interface 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 a sgm extension). To get acquainted with the program, open a supplied Example file. Use Connect to see your own clusters "live." You need to have a logon for a node that is running Serviceguard A.11.13.00 and later. Name this node to be your Session Server.
Fixed in this Version JAGaf13947 NPE while trying to save after gui was up for 24 hours (Java problem) What was the problem? After Serviceguard Manager had been running for 24 hours, Java gave a Null Pointer Exception when user tried to Save. JAGag00662 when adding two services in guided mode index number does not increment What was the problem? When using Serviceguard Manager 5.00 to configure packages, the SERVICE index number did not get incremented.
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.
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.conf 10. Run package YYY: cmrunpkg YYY 11. Delete the temporary directory created in step 2. 12. Make sure that Auto Run is set correctly for the package. You can do this in Serviceguard Manager.
JAGaf48460 Event browser displays wrong status of snmp subagent What is the problem? The event browser may incorrectly say that the SNMP subagent is down, and the trap is not set, even when they are active and reporting new events. What is the workaround? Follow these steps: 1. 2. Bring up Set Trap dialog for the managed node. Type in something in the textfield to force trap setting. The status should now be Trap Set.
What is the workaround? There is no workaround. JAGaf44056 Traditional-Chinese font size too small on HP-UX client What is the problem? On Serviceguard Manager A.04.02 on HP-UX, the Traditional Chinese font is small and difficult to read. What is the workaround? To increase the font size for Serviceguard Manager in Traditional Chinese on HP-UX systems, please follow the instructions below.
type application/x-java-jnlp-file handled by application /javaws.exefont=symbol charset=fontspecific code=183 descr='[bull]' • Second: When updating, you need to manually clear the Java Web Start cache on the SIM client side. It contains the .jar files downloaded from the server. Before installing the new Serviceguard Manager, clear the cache and the server will automatically download the new .jar files. JAGaf15152 Package with all nodes (*) causes problem when adding node to cluster.
JAGae50775 In Traditional Chinese locale, in HP-UX, need to use Java OOB tool prior to install What is the problem? Java performance is bad on HP-UX in the Traditional Chinese. What is the workaround? Before installing Serviceguard Manager on Traditional Chinese version of HP-UX, HP recommends running the Java Out-Of-The-Box tool to modify kernel parameters. Please refer to http://www.hp.com/products1/unix/java/java2/outofbox/ infolibrary/release_notes_java_oob.html.
JAGaf96074 - Cannot change network interface configuration during modify cluster What is the problem? Cluster configuration could encounter problems after changing a standby LAN to an active LAN and then using it for a heartbeat or monitored subnet in the cluster configuration. What is the workaround? There is no workaround.
