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, the event browser version 5.0 does not display SNMP traps, because this bug is fixed. If users are not aware that version 4.0 had a problem, then they may erroneously assume that the switch is not sending these traps. In this case, you can view the ASCII trap log file:
/var/opt/OV/share/log/trapd.log
In doing so, 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 is the process that receives the trap. HP OpenView then passes the trap to Device Manager. In a sense, it intercepts the trap message. If Device Manager displays a trap, HP OpenView has also received the trap.
To display standard SNMP traps in the event browser for HP OpenView 5.0: