ServiceGuard Manager Version A.03.00 Release Notes, Third Edition, September 2003

ServiceGuard Manager Version A.03.00 Release Notes, Third Edition
Patches and Fixes in this Version
Chapter 1 47
• What is the workaround? There is no workaround. Realize that when
you halt a node, the progress dialog box will report it is halting the
cluster, even though it is halting the node as requested. Message
fixed in ServiceGuard Manager A.03.00.01, but not in A.03.00.
JAGae55465 - sgmgr core dumps when executed by non-root user
(JRE directory permission problem) (Fixed in A.03.00.01)
• What is the problem? On some HP-UX systems, a JRE file permission
problem causes ServiceGuard Manager to core dump when a
non-root user opens the interface.
• What is the workaround? Have an administrator log on to the HP-UX
system, as root. Go to the /opt/sgmgr/jre/lib directory. Change
permissions: chmod 555 PA_RISC2.0
JAGae45299 - Printing Help pages may use 100% CPU
• What is the problem? When trying to print a Help topic, CPU usage
may suddenly jump to 100% of capacity, and stay there.
• What is the workaround? This is a known problem with Java (ID=
4768427).
JAGae51034 Event notification not supported by SG 11.12 Object
Manager (Fixed in A.03.00.01)
• What is the problem? In A.03.00, if you connect to a server with
ServiceGuard 11.12, you will not be able to receive SNMP event
messages. Fixed in A.03.00.01‘
• What is the workaround? If you want SNMP events, connect to a
node that has a later version of ServiceGuard.
JAGae50988 - Trap status is “trap Setting” if IP address is
unresolved (Fixed in A.03.00.01)
• Whatis the problem? Wrongmessage is given in A.03.00 if IP address
is unresolved.
• What is the workaround? There is no workaround. Message fixed in
ServiceGuard Manager A.03.00.01, but not in A.03.00.