notifd-tests.txt

opennms得相关源码 请大家看看

Notifd Test Checkoff List

Test Intialization
[ ] Run the initialize.sh script. WARNING, THIS WILL OVERWRITE YOUR EXISTING CONFIG FILES AND DATABASE TABLES. 
    PLEASE BACK UP IF THESE FILES ARE NEEDED. TAKE CAUTION NOT TO COMMIT THE NOTIFD TEST CONFIG FILES INTO CVS!
[ ] Start at least the Eventd and Notifd services.

==================================================================================================================

Test #1 - Normal notice with a 15 minute escalation

This test signals a node lost service event which triggers the Page-Network/Systems/Management path.
Normally a page-email-pemail would be sent, but the users are set up only with emails. The notifd-user10 user
has a duty schedule of Sa600-630 and should not be notified (unless you are running this test between 6am and 6:30
on a Saturday morning). 

Be sure each of the following conditions are true before the test has been run.
[ ] All emails from the notifd account are deleted
[ ] Eventd and Notifd are running

Be sure each of the following conditions are true after the test has been run.
[ ] Three emails, one to each member of the Network/Systems group has been recieved. They should all
    be very close in their respective send times.
    [ ] email to notifd-user1 stating that FTP on 192.168.0.189 is down
    [ ] email to notifd-user2 stating that FTP on 192.168.0.189 is down
    [ ] email to notifd-user3 stating that FTP on 192.168.0.189 is down
    [ ] no email received for notifd-user10
    
[ ] Fifteen minutes after the above emails are received (give or take a minute or so) the notifd-managment
    user received escalation email.

[ ] All event expansion parameters are expanded in the email subject and text (nothing that looks like %xxx%).

==================================================================================================================

Test #2 - Automatic Acknowledgement

Similar test to #1, but a node regained service event will arrive before the escalation to management.

Be sure each of the following conditions are true before the test has been run.
[ ] All emails from the notifd account are deleted
[ ] Test #1 passed
[ ] Eventd and Notifd are running

Be sure each of the following conditions are true after the test has been run.
[ ] Three emails, one to each member of the Network/Systems group has been recieved. They should all
    be very close in their respective send times.
    [ ] email to notifd-user1 stating that FTP on 192.168.0.189 is down
    [ ] email to notifd-user2 stating that FTP on 192.168.0.189 is down
    [ ] email to notifd-user3 stating that FTP on 192.168.0.189 is down
    [ ] no email received for notifd-user10
[ ] About a minute after the above emails are received the next three emails below are received
    [ ] email to notifd-user1 stating that FTP on 192.168.0.189 is back UP
    [ ] email to notifd-user2 stating that FTP on 192.168.0.189 is back UP
    [ ] email to notifd-user3 stating that FTP on 192.168.0.189 is back UP

[ ] After 5 minutes from previous emails the notifd-managment user SHOULD NOT have received his email.
    (or ever, for that matter!)

==================================================================================================================

Test #3 - User Acknowledgement

Similar test to #1, but a user will acknowledge the notice before the escalation to management.
You will need to log into the Web UI and acknowledge the most recent notice for one of the following
users prior to the 15m escalation to management. Acknowledge the most recent notice for
notifd-user1, notifd-user2 or notifd-user3. Log in to the Web UI with username: admin password: admin

Be sure each of the following conditions are true before the test has been run.
[ ] All emails from the notifd account are deleted
[ ] Test #1 passed
[ ] Eventd and Notifd are running

Be sure each of the following conditions are true after the test has been run.
[ ] Three emails, one to each member of the Network/Systems group has been recieved. They should all
    be very close in their respective send times.
    [ ] You acknowledged one of the three user's most recent notice

[ ] After 5 minutes from previous emails the notifd-managment user SHOULD NOT have received his email.
    (or ever, for that matter!)

==================================================================================================================

Test #4 - Node, Interface, or Service not in the rule of a notification.

This ensures that the rule mechanisms are working properly to constrain against different sets of
interfaces (nodes, and services). Instead of sending this notification to the Page-Network/Systems/Management path
it should go to the EmailAll-Reporting and the Reporting group that consists of notifd-user4 and notifd-user5. 
There is no escalation on this test.

Be sure each of the following conditions are true before the test has been run.
[ ] All emails from the notifd account are deleted
[ ] Test #1 passed
[ ] Eventd and Notifd are running

Be sure each of the following conditions are true after the test has been run.
[ ] Two emails, one to each member of the Reporting group has been recieved. They should both
    be very close in their respective send times.
    [ ] email to notifd-user4 stating that FTP on 192.168.0.189 is down
    [ ] email to notifd-user5 stating that FTP on 192.168.0.189 is down

==================================================================================================================

Test #5 - Notices turned off for a given Interface and Service

This test ensures that notices can be turned off for specific interface/service combinations.

Be sure each of the following conditions are true before the test has been run.
[ ] All emails from the notifd account are deleted
[ ] Test #1 passed
[ ] Eventd and Notifd are running

Be sure each of the following conditions are true after the test has been run.
[ ] No emails are recieved for this test run.