Patches and Fixes in this Version

What is the problem? Do not hide the tree. If you click the box to remove the “Tree” check from the View menu, the map and the tree become blank, and cannot be re-enabled.

What is the workaround? Do not hide the tree. If you do, you have to close Serviceguard Manager and open a new instance.

What is the problem? After Serviceguard Manager is uninstalled, it is still on the menu. If you click on it, it says “Error 404 not found.”

What is the workaround? There is no workaround.

What is the problem? When installing SGMgr on a linux machine with SIM (Systems Insight Manager) already installed, user may see the following errors:

# rpm -Uvh sgmanager-A.04.00.00-1.product.redhat.i386.rpmPreparing... ########################################### [100%]
file /opt/hpwebadmin/lib/sgmgrLauncher.properties from install of sgmanager-A.04.00.00-1 conflicts with file from package hpsim-C.04.01.00.00R41_QA9-1 
file /opt/hpwebadmin/lib/sgmgrLauncher_ja.properties from install of sgmanager-A.04.00.00-1 conflicts with file from package hpsim- C.04.01.00.00R41_QA9-1 
file /opt/hpwebadmin/webapps/sgmgr/WEB-INF/web.xml from install of sgmanager-A.04.00.00-1 conflicts with file from package hpsim-C.04.01.00.00R41_QA9-1 
file /opt/hpwebadmin/webapps/sgmgr/sgmgrLauncher.jsp from install of sgmanager-A.04.00.00-1 conflicts with file from package hpsim-C.04.01.00.00R41_QA9-1

The Serviceguard Manager files are meant to replace the hpsim package files

What is the workaround? Force replacement files, regardless of the warnings.

rpm -i --replacefiles sgmanager-A.04.00.00-1.product.redhat.i386.rpm

What is the problem? System Insight Manger supports Windows 2003 server, but Serviceguard Manager does not.

What is the workaround? Install Serviceguard Manager on one of the platforms it supports.

What is the problem? Serviceguard Manger does not completely integrate with OVO 8.0. The tools are missing, although you can manually install the other functionality is there. OVO 8.0 includes NNM 7.1, and the NNM 7.1 functionality does install without problem. (This does not happen with OVO 6.0 or 7.0.)

What is the workaround? When using swinstall to install Serviceguard Manager a user sees that NNM-UX (and/or NNM-JPN-UX) fileset(s) are installed, if OVO 8.0 is installed on the machine. SG mib and SG snmp event templates will be available in OVO 8.0. The following steps need to be performed manually for SGMgr icon and launcher menu item to appear in OVO:

Register the SGMgr application with the user opc_adm.

cd /etc/opt/OV/share/conf/OpC/mgmt_sv/ui/registration/C/ opc_adm/
sbin/ln -fs ../../../../../../../registration /C/sgmgr.arf ./sgmgr.arf

And if you have Japanese version of OVO 8.0:

cd /etc/opt/OV/share/conf/OpC/mgmt_sv/ui/registration /ja_JP.SJIS/opc_adm/
sbin/ln -fs ../../../../../../../ registration/ja_JP.SJIS/sgmgr.arf ./sgmgr.arf

However, the SG OVO tools are not avaiable for OVO 8.0. There is currently no workaround ways of installing them for this release.

What is the problem? Using Serviceguard Manager, you cannot create a cluster with the pound (#) character in the name. One example is the name “cluster#27.” Other non-alphanumeric characters may not be accepted.

When you click Apply, you will get an internal error, “Null pointer exception.” In the Operations Log, after Operation Completed”, you may see a message like this: “Error: Missing ‘{’ in Component definition.”

What is the workaround? Try to create clusters with alpha-numeric characters in the name. If you use other keyboard characters, check the log file carefully.

What is the problem? Some accessibility short-cut keys do not work in traditional Chinese, simplified Chinese, Korean, or Japanese.

What is the workaround? There is no workaround. If you require short-cut keys, install the English version.

What is the problem? If a configuration uses a wild card to set node membership to all nodes, you will have trouble adding a new node to the cluster.

What is the workaround? On the package configuration screen, remove the “all nodes” star wildcard. Select all the nodes in the list, adding them one at a time. Then add the new node. Be sure the configuration and control script are added to the new node before you do any more changes.

What is the problem? All alphanumeric characters are accepted as package names. However, you cannot use most of the other characters on a keyboard. (For the exact list, see the Help topic for Configuring Packages.)

The packages appear to be added. However, if you select one in the tree or map, you will get a connection error. You will also get an error if you try to open the properties for the package or its cluster.

What is the workaround? In package names, do not use any of the special characters listed. If you have an existing package with these special characters, you will not be able to configure it through Serviceguard Manager unless you change its name.

What is the problem? This happens if a node in the cluster has a lan card that has more than one IP address, and the addresses are for different subnets. If the subnet of one of the IP addresses is specified as monitored, both subnets may show up in the list of monitored subnets. This is especially likely with IPv6 addresses

What is the workaround? There is no workaround.

What is the problem? There are two problems:

What is the workaround? There are two workarounds:

What is the problem? This happens when you are using Guided Mode and letting Serviceguard Manager create your control script automatically. If you enter a service command with quotes in it, such as /usr/bin/X11/xclock -title "My Xclock", your quotes will be ignored when they are transferred.

After the script is Applied, the target control script in /etc/cmcluster/<pkgName>/<pkgName>.sdf.sh contains something like this: SERVICE_CMD[0]="/usr/bin/X11/xclock -title My Xclock"

What is the workaround? Do not use quotes in service commands if you are creating the control script through Guided Mode.

What is the problem? The timeout for checking storage status may not work. When you open Properties, Serviceguard issues an ioscan to find status of the disks. If you have a bad disk in your cluster, you may see “Please wait” on the network tab for a very long time, perhaps more than an hour. It appears that Serviceguard Manager has hung; actually, it is not timing out when the status request is not returned. This can also happen when you do a Save As command.

What is the workaround? If you wait a long time after a Save As or on the Network Tab of properties, check the disks from the command line, using ioscan or through SAM. If they have zero length, your disk is bad.

What is the problem? Serviceguard Manager will allow you to configure conflicting or redundant roles. This is especially likely when using wild-cards. For example, you may be able to configure an Admin role for ANY_USER from node1 and then a Monitor role for user1 from node1. Since user1 is included in ANY_USER, this should not be allowed.

What is the workaround? Check your roles to be sure none are redundant or conflicting.

What is the problem? Once Serviceguard Manager discovers a cluster, it will ignore any others that have the same name. For example, imagine that one subnet has a cluster named node1 and node2. Now imagine that another subnet has a cluster named clus1, whose members are nodeX and nodeY.

The situation is not common because Serviceguard insists that the cluster name must be unique in its environment. However, the Session Server may be able to see clusters that cannot see each other. If it does, it will display the first clus1 that it encounters during discovery, and ignore the other.

What is the workaround? There is no workaround.

What is the problem? Serviceguard Manager does not stop you from opening two configuration screens at the same time. If you enter changes in both screens, thinking there is only one, you may not Apply the configuration that you expected

What is the workaround? There is no workaround.

What is the problem? If you enter a string of two or more s’s (ss, sss, etc), in the Help Search window, you get an error. This is a known defect in Javahelp. It causes a NullPointerException.

What is the workaround? There is no workaround.

What is the problem? Because of extensive changes to Serviceguard Manager version A.04.00, preferences are not carried over from version A.03.00.

What is the workaround? There is no workaround.

What is the problem? In Japanese and Korean versions, Serviceguard Manager will freeze if you type local characters into the Index tab of Help and then type enter.

What is the workaround? Use the Search tab instead.

What is the problem? Occasionally, an exception happens when using ReflectionX to remotely start Serviceguard Manager on SuSE Linux. (SuSE Linux is supported for English only.)

What is the workaround? This is related to a problem in the Java Runtime Environment. There is no workaround. Often it will work if you try again.

What is the problem? A timing problem cause unsynchronized behavior of the Options-> Dialog box settings. Here is one scenario:

What is the workaround? There is no workaround.

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.

What is the problem? In the installer, the Licence Agreement window shows a radio button to check, confirming that the user agrees with the license terms. The text is too small to be easily read in Chinese.

What is the workaround? Remember that the first button says “I accept the terms of the license agreement” and is checked by default. The other button says “I do NOT accept the terms of the license agreement.”

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.”

What is the problem? When running non-English versions of SGMgr on HP-UX, typed non-English characters are invisible in the input text boxes. The characters can be read by the program, but not seen by the user. This occurs in the text fields of Alerts: Search and Help: search.

What is the workaround? The computer is printing white characters on a white background, making them invisible. Set the system colors of the CDE Style Manager from the HP-UX toolbar. Choose a color set with a black foreground color, like Alpine or Wheat.

What is the problem? In non-English interfaces, the keyboard mnemonics are indicated by underlining a letter in parentheses. This indicates that the item can be accessed by holding the alt key while pressing that letter. In some translations, the underline is misplaced.

What is the workaround? Use the letter in parentheses for the alt-key short-cut, even if the underline has moved into a word.

What is the problem? If you try to connect with a user name, but leave the password field empty, the connect button stays greyed out.

What is the workaround? There is no workaround. Do not use blank password.

What is the problem? You cannot use the Enter key to activate the Apply button in the Alerts dialog box.

What is the workaround? Use the mouse to click the button, or tab to it to select it, then use the Return key to activate it.

What is the problem? The Alert icon on the toolbar and the Status title bar reflect the Show Clusters filter in the Alert page, but not the Search filter.

What is the workaround? There is not workaround.

What is the problem? Serviceguard Manager displays progress messages directly from Serviceguard as administration commands are processed. Serviceguard does not localize these messages and Serviceguard Manager can only translate the start and end messages for every admin operation. The intermediate messages are only in English.

What is the workaround? There is no workaround.