800 Series Alarm Messages

Alarm Severities

One or more of the following severity levels is associated with each alarm.

Critical

Indicates that a platform service affecting condition has occurred and immediate corrective action is required. (A mandatory platform service has become totally out of service and its capability must be restored.)

Major

Indicates that a platform service affecting condition has developed and urgent corrective action is required. (A mandatory platform service has developed a severe degradation and its full capability must be restored.)

- or -

An optional platform service has become totally out of service and its capability should be restored.

Minor

Indicates that a platform non-service affecting fault condition has developed and corrective action should be taken in order to prevent a more serious fault. (The fault condition is not currently impacting / degrading the capability of the platform service.)

Warning

Indicates the detection of a potential or impending service affecting fault. Action should be taken to further diagnose and correct the problem in order to prevent it from becoming a more serious service affecting fault.

---

Alarm ID: 800.001	Storage Alarm Condition: 1 mons down, quorum 1,2 controller-1,storage-0
Entity Instance	cluster=<dist-fs-uuid>
Degrade Affecting Severity:	none
Severity:	[‘critical’, ‘major’]
Proposed Repair Action	If problem persists, contact next level of support.
Management Affecting Severity	warning

---

Alarm ID: 800.010	Potential data loss. No available OSDs in storage replication group.
Entity Instance	cluster=<dist-fs-uuid>.peergroup=<group-x>
Degrade Affecting Severity:	none
Severity:	[‘critical’]
Proposed Repair Action	Ensure storage hosts from replication group are unlocked and available. Check if OSDs of each storage host are up and running. If problem persists, contact next level of support.
Management Affecting Severity	warning

---

Alarm ID: 800.011	Loss of replication in peergroup.
Entity Instance	cluster=<dist-fs-uuid>.peergroup=<group-x>
Degrade Affecting Severity:	none
Severity:	[‘major’]
Proposed Repair Action	Ensure storage hosts from replication group are unlocked and available. Check if OSDs of each storage host are up and running. If problem persists, contact next level of support.
Management Affecting Severity	warning

---

Alarm ID: 800.103	Storage Alarm Condition: [ Metadata usage for LVM thin pool <VG name>/<Pool name> exceeded threshold and automatic extension failed, Metadata usage for LVM thin pool <VG name>/<Pool name> exceeded threshold ]; threshold x%, actual y%.
Entity Instance	<hostname>.lvmthinpool=<VG name>/<Pool name>
Degrade Affecting Severity:	none
Severity:	critical
Proposed Repair Action	Increase Storage Space Allotment for Cinder on the ‘lvm’ backend. Consult the System Administration Manual for more details. If problem persists, contact next level of support.
Management Affecting Severity	major

---

Alarm ID: 800.104	Storage Alarm Condition: <storage-backend-name> configuration failed to apply on host: <host-uuid>.
Entity Instance	storage_backend=<storage-backend-name>
Degrade Affecting Severity:	none
Severity:	critical
Proposed Repair Action	Update backend setting to reapply configuration. Consult the System Administration Manual for more details. If problem persists, contact next level of support.
Management Affecting Severity	major

---