!2 Testvorbereitung

Alle Alarme entfernen

!|test.util.CallPhp|
|php interface|AlarmManagement|
|php procedure|deleteCacs|
|execute action|

Log leeren

!|test.util.CallScript|
|call script|sudo bash -c 'echo "" > /var/log/sysal.log'|

Set Alarm

!|test.util.CallPhp|
|php interface|AlarmManagement|
|php procedure|processAlarm|
|set parameter|InstanceAddress|IPv4/1.2.3.4|
|set parameter|EventTime|2012-05-05|
|set parameter|EventSpecification|oid_number/1.2.3.4|
|set parameter|ServiceInfluence|serv_aff|
|execute action|

Check Alarm

!|test.util.CallPhp|
|php interface|AlarmManagement|
|php procedure|getMonitorAlarms|
|set parameter|ABM_ID|1|
|execute action|

!|test.util.CallPhp|
|result contains|oid_number/1.2.3.4|1|
|result contains|</alarm>|1|

!|test.util.CallScript|
|call script|wget http://localhost/sysal/gui/|
|call script|grep critical index.html|
|call script|rm index.html|

!|test.util.CallScript|
|call script|grep critical /var/log/sysal.log|
Anmerkung: Wenn es hier zu einem Fehler kommt, kann das daran liegen, dass der Nutzer nicht in der adm-Gruppe ist.

Reset Alarm

!|test.util.CallPhp|
|php interface|AlarmManagement|
|php procedure|processAlarm|
|set parameter|InstanceAddress|IPv4/1.2.3.4|
|set parameter|EventTime|2012-05-05|
|set parameter|EventSpecification|oid_number/1.2.3.4|
|set parameter|AlarmSeverity|cleared|
|execute action|

Check Alarm

!|test.util.CallPhp|
|php interface|AlarmManagement|
|php procedure|getMonitorAlarms|
|set parameter|ABM_ID|1|
|execute action|

!|test.util.CallPhp|
|result contains|oid_number/1.2.3.4|0|
|result contains|</alarm>|0|

!contents -R2 -g -p -f -h