Serviceguard Manager Version A.04.02 Release Notes, February 2005

Serviceguard Manager Version A.04.02 Release Notes
Patches and Fixes in this Version
Chapter 152
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. Bring up Set Trap dialog for the managed node.
2. Type in something in the text field to force trap setting.
3. The status should now be Trap Set.
The backend logic is:
— Step 1: Use the community name supplied to set trap (Success or
Failure)
— Step 2: Query the status of the trap destination. Since the trap
destination is already set in the backend, Step 1 will not unset
the trap, even if the community name is not correct. Step 2 will
then display the updated status.
Note: If the status is already Trap Set, unsetting the trap destination
in the backend will not be visible in the front-end GUI. In this case,
please disconnect and then reconnect.
Serviceguard Manager uses both snmp event notification and polling
to ensure the most up-to-date data is available for the user. Even if a
snmp agent dies on the backend, the polling should be able to refresh
the data with a slight delay, depending on the polling interval setting
which can be customized by the user.
JAGaf44451 (JAGaf43912) Cluster Properties: wrong lock info in
older version of COM
• What is 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.