HP OpenView versions 4.0 and 5.0 contain bugs that do not affect the integrity of the product when it stands alone. However, when combined with Device Manager, unexpected results occur.
The "Log only" event categorization bug in HP OpenView 4.0 causes traps to be written to the ASCII trap log file and to be displayed in the event browser.
The default category for SNMP traps, such as "link up" and "link down," happens to be "Log only." The correct procedure for an event (trap) with a "Log only" categorization is that it should only be written to the ASCII trap log file.
In version 4.0, standard SNMP traps are displayed in the event browser when the default category of "Log only" is selected. However, SNMP traps are not displayed in the event browser version 5.0, because this bug is fixed. If you were not aware that version 4.0 had a problem, then you may have erroneously assumed that the switch was not sending these traps. In this case, you can view the ASCII trap log file. Enter:
/var/opt/OV/share/log/trapd.log
When you view the log, you can verify that the switch is sending the traps. In fact, when both HP OpenView and Device Manager are running on a machine, and that machine is configured on the switch as a trap receiver, HP OpenView receives the trap. HP OpenView then passes the trap to Device Manager. If Device Manager displays a trap, HP OpenView has also received the trap.
To have standard SNMP traps displayed in the event browser for HP OpenView 5.0:
| Your choices are Error Events, Threshold Events (normally used for RMON alarms), Status Events, Configuration Events, or Application Alert Events. |