Not able to see traps as alarms in Live Exceptions (Legacy KB ID CNC TS15486 )
Article ID: 52101
Updated On:
Products
Issue/Introduction
In the current version of TrapEXPLODER, the correct line that should be in use in the trapexploder.cf file is:
filter * * * * * * tcpbuff <IP.Of.eHealth.Server>:5058 2000 900
The trapexploder.cf file is located by default on a Windows system in:
C:\WINNT\System32
The trapexploder.cf file is located by default on a Unix system in:
/etc
Once the change has been made, restart the eHealth server and the TrapEXPLODER service.
When all the above has been completed, when traps begin to arrive in TrapEXPLODER, they should now be passed to the eHealth server and the $NH_HOME/log/trapLog.*.*.bin file should begin to fill up with traps.
For more information regarding assistance getting the traps received displayed as alarms in Live Exceptions, please see Knowledgebase Solution titled,"Trap(s) sent by outside source ( event source ) do not appear in the Live Exceptions browser"
Related Issues/Questions:
Not able to see traps as alarms in Live Exceptions
$NH_HOME/log/trapLog.*.*.bin files are not populated with traps
Traps alarms are not appearing in Live Exceptions
eHealth is receiving traps as seen with a TrapEXPLODER log filter statement that creates and populates a log file with traps
TrapEXPLODER is not forwarding traps to eHealth
$NH_HOME/log/trapLog.*.*.bin files are all 0 (zero) bytes in size
Problem Environment:
TrapEXPLODER
Fault Manager
eHealth
Causes of this problem:
A correct filter statement is not set in the trapexploder.cf file to enable trap forwarding to the eHealth server
(Legacy KB ID CNC TS15486 )
Environment
Component:
Feedback
