Alarm Information
When a device fault occurs or the device cannot work properly, the edge management system generates an alarm and log information based on the fault type and the faulty module. If an NMS is configured, alarms will be sent to the NMS (such as FusionDirector). The sensors on the device check the device operating environment, and generate alarms if the environmental conditions do not meet the device operating requirements.
Events and Alarms
Based on the impact on the device, the alarms are classified into the following types:
- An event records a key event that occurs during device operating. It generally has no impact on the device.
- An alarm indicates a fault that may affect device operating.
Alarm Severity
Alarms are classified into the following types by severity:
- A minor alarm has a minor impact on the system, but you need to take corrective actions as soon as possible to prevent a more severe alarm.
- A major alarm has a major impact on the system. It affects the normal operating of the system or may cause service interruption.
- A critical alarm may power off the device, and even interrupt system services. You must take corrective actions immediately.
Alarm Format
Take a certificate alarm supported by the edge management system as an example. The alarm content is "00180000@cert warning@CERT@1866989008@1@aabb", where @ is used for separation. The meaning of each part is as follows:
- 00180000: alarm ID
- cert warning: alarm name
- CERT: alarm object
- 1866989008: alarm timestamp
- 1: alarm severity. The value ranges from 0–2. 0 indicates a critical alarm, 1 indicates a major alarm, and 2 indicates a minor alarm.
- aabb: fixed terminator
Alarm Configuration Reserved for the OM SDK
The preset alarm configurations of the OM SDK include alarms on the temperature, power, storage, NFS, port, NPU, and Wireless_Module. For details about the alarm configuration, see Reserved Alarm Configuration for the OM SDK.