How do I get Alerts/Events configured in NFA to show up in NetOps Portal as Events?
Release:
Component: NQRACO
NFA x PC Integration
Configure Alerts based on various thresholds and filters in the "Adminstration->Alerts" page shown below.
In the NFA "Adminstration->Appplication Settings" page set the "Trap Destinations" field to the IP address of the NFA console and NOT the NetOps Portal server.
The way this works is the Alerts are generated from NFA as Traps, and NetOps Portal's Event Manger does not listen for Traps, but the NFA Console does. So the trap is redirected back to itself on the NFA Console and the then the events are pushed up to the CAPC server.
Once traps start to be generated they will be logged in the NFA console server's 'TrapReceiverLog*.log' file, you can check here to verify traps are being sent.
Verify the Threshold Alerts in NFA are now showing up as Threshold Events in NetOps Portal's "Event Display" view.
Check the configuration in mysql NFA Console
Take a look this example:
PC ip address xx.xx.xx.xx1
NFA Console ip address xx.xx.xx.xx2
select * from reporter.parameter_descriptions where parameter='watchdogTrapDestination';
update reporter.parameter_descriptions set DefaultValue='xx.xx.xx.xx1' where parameter='watchdogTrapDestination';
select * from reporter.parameter_descriptions where parameter='trapDestination';
update parameter_descriptions set DefaultValue='xx.xx.xx.xx2' where parameter='trapDestination';
select * from reporter.parameter_descriptions where Parameter = 'trapsHaveUniqueDomain';
update reporter.parameter_descriptions set DefaultValue = 'True' where Parameter = 'trapsHaveUniqueDomain';
select * from harvester.parameter_descriptions where parameter='RealtimeReaper_RunAlarms';
update harvester.parameter_descriptions set defaultValue='0' where parameter='RealtimeReaper_RunAlarms';
select * from harvester.parameter_descriptions where parameter='Reaper_RunAlarms';
update harvester.parameter_descriptions set defaultValue='1' where parameter='Reaper_RunAlarms';
Recycle all NFA services
Check the TrapReceiverLog*.log file
Also see:
Article ID: 31309 - How do Traps and Thresholds work in NFA and what are the different types of Alerts for configuration
https://knowledge.broadcom.com/external/article?articleId=31309