Adding a notifications policy
When you add a notifications policy, you inform administrators of alerts, policy violations and the status changes of job executions. Using SNMP traps, the notification system also allows you to send traps to SNMP-enabled third-party applications. Perform the following steps to add a notifications policy and assign it a name.
Procedure
- Click on the Policies tab.
- Click the New Policy link at the bottom left of the screen and give the policy a name.
- In the Notify When row, select a level and system. Be sure the SNMP checkbox under the Notify section is checked.
- Click Save.
Example
Header | Header | Header |
---|---|---|
Network | Warning | Automatically added hostname to /etc/hosts, see "net show etchost." |
Hardware | Warning | Fan is not functional. Fan: {0} Current Speed: {1} rpm Min Required Speed: {2} rpm Max Allowed Speed: {3} rpm Machine ID: {4} |
Hardware | Info | Fan is functional. Fan: {0} Current Speed: {1} rpm Min Required Speed: {2} rpm Max Allowed Speed: {3} rpm Machine ID: {4} |
Hardware | Critical | Temperature is out of range. Temperature sensor: {0} Current temperature: {1} degrees C Minimum: {2} degrees C Maximum: {3} degrees C Machine ID: {4} |
Hardware | Info | Temperature is restored. Temperature sensor: {0} Current temperature: {1} degrees C Minimum: {2} degrees C Maximum: {3} degrees C Machine ID: {4} |
Hardware | Warning | Power has been interrupted. Machine ID: {1} |
Hardware | Info | Power has been restored. Machine ID: {1} |
Hardware | Warning | The Integration Appliance {0} has been opened. Machine ID: {1} |
Hardware | Info | The Integration Appliance {0} has been closed. Machine ID: {1} |
Hardware | Critical | RAID Array {0} is offline. Machine ID: {1} |
Hardware | Severe | RAID Array {0} is degraded, probably because of a disk failure. Machine ID: {1} |
Hardware | Info | RAID Array {0} is optimal. Machine ID: {1} |
Hardware | Critical | RAID Disk {0} on array {1} has failed. Machine ID: {2} |
Hardware | Info | RAID disk {0} on array {1} is rebuilding. Do not remove the disk until the rebuild is completed. Machine ID: {2} |
Hardware | Info | RAID disk {0} on array {1} is online. Machine ID: {2} |
Hardware | Warning | High Availability System Failover successful |
Hardware | Info | Network Interface Link Up. Network Interface {0} is now up Machine ID: {1} |
Hardware | Warning | Network Interface Link Down. Network Interface {0} is now down Machine ID: {1} |
Hardware | Critical | Incorrect number of CPUs: expected {0} but found {1} |
Resources | Info | Swap space monitoring errors encountered. |
Resources | Info | Suspending swap space monitoring for {0} seconds. |
Resources | Info | Swap space usage is now below the {0}% warning threshold - current usage is {1}.{2}% |
Resources | Info | Swap space usage is now below the {0}% critical threshold - current usage is {1}.{2}% |
Resources | Warning | Swap space usage has exceeded the {0}% warning threshold - current usage is {1}.{2}% |
Resources | Critical | Swap space usage has exceeded the {0}% critical threshold - current usage is {1}.{2}% |
Resources | Info | Disk space monitoring errors encountered. |
Resources | Info | Suspending disk space monitoring for {0} seconds. |
Resources | Info | {0} disk space usage is now below the {1}% warning threshold - current usage is {2}.{3}% |
Resources | Info | {0} disk space usage is now below the {1}% critical threshold - current usage is {2}.{3}% |
Resources | Warning | {0} disk space usage has exceeded the {1}% warning threshold - current usage is {2}.{3}% |
Resources | Critical | {0} disk space usage has exceeded the {1}% critical threshold - current usage is {2}.{3}% |
Resources | Critical | HA peers are running different versions of CIOS! |