There was some concern that Prognosis may not have alerted on AEP events, and whether it was just due to the network outage at that time or if there is a more permanent problem stopping us getting these alerts. How can we test it to be sure that we should receive an alert from Prognosis?
Solved! Go to Solution.
By sending a test trap , which can be triggered manually at will from the AEP web interface.
But if we want to look at further detail of the work flow inside Prognosis to break it down by 'did Prognosis receive the trap' , 'trap severity Critical, Major or Minor' and 'was an alert triggered' here is a short video on how to do that.
Steps in this video:
1. Send test traps from AEP by manually triggering them from teh AEP web interface;
2. Run a display, or the attached display in the Prognosis client to view the AEPTRAP record, to see Prognosis received the trap.
3. Also display the PROBSUM and PROBSUMC records with appropriate where clauses to show the alerts triggered by the AEP.
4. Repeat viewing these Prognosis records after sending a trap if each different severity. The AEP web interface allows changing teh trap severity of the test trap so that all trap severities can be tested.
Here is a link to anothe rway to test snmp traps from porgnosis by using a 3rd party SNMP trap receiver.
Having looked at the planning phase in session one of this series, we will turn our focus to the readiness phase. The all important technical capabilities assessment, ensuring the network, endpoints and users are adequately prepared for the move.
Hear first hand from IR's Global Head of Information Systems and Technology, Jason Schwendinger, on how he has been tackling these issues.Join webinar