HP Serviceguard Version A.11.17 Release Notes, March 2006 (revised)

Serviceguard Version A.11.17 Release Notes
Fixed in This Version
Chapter 1 45
JAGaf35681 (SR8606375378): snmpwalk shows empty
hpmcClusterPrimaryNode
What was the problem? DUPLICATE. See JAGaf31114: cl_run_node
failed due to snmp walk failure
In a stressed environment, the cmsnmpd may become unresponsive and
log
***Error: get_all_status() failed in /var/adm/SGsnmpsuba.log.
When this happens, Serviceguard SNMP traps and mib table will no
longer be maintained and the subagent may yield incorrect data about
the cluster
What was the resolution? Added a 0.5 second time interval between
query retries.
JAGaf34971 (SR8606374657): 11.23pi ic1r Incorrect
num of hpmcSGNodeHalted traps received
What was the problem? Serviceguard SNMP Subagent may send
hpmcSGNodeFailed trap instead of hpmcSGNodeHalted trap when node
halted successfully and did not actually fail.
What was the resolution? Drain all the events in the subagent API event
queue before cmcld exits when a node halts.
JAGaf33299 (SR8606372896): cmsnmp sends wrong
trap for local lan failover
What was the problem? DUPLICATE. See JAGaf46724: Fix for
JAGaf33299 breaks working traps
The cmsnmpd subagent will send a hpmcSGLocalSwitch trap with
incorrect LAN names when there are multiple LANs with different
length names. For example, if LAN4 fails over to LAN11, the trap
message sent may show: lan4 failed over to lan1.
What was the resolution? First compare the string lengths of the lan
names, and if they match then do a "strncmp" of the actual lan name
strings.