The alarm inventory contains a list of system default alarms.
The following tables describe various parameters in alarm inventory.
| Severity | Enum | Description |
|---|---|---|
| Critical | 6 | Service-affecting condition which requires an immediate corrective action. |
| Major | 5 | Service-affecting condition which requires an urgent corrective action. |
| Minor | 4 | Non-service-affecting condition which requires a corrective action. |
| Warning | 3 |
Potential service-affecting fault which requires further diagnosis to prevent serious consequences. |
| Indeterminate | 2 |
Severity level cannot be determined. Note: This severity must be avoided.
|
| Cleared | 1 |
Alarm is cleared by the system. Note: This severity level is only applicable to the “StatusChange” list
severity.
|
| Types | Enum | Description |
|---|---|---|
| Other | 1 |
Indicates a catch-all category for alarms. Note: Avoid this alarm type if other alarm types are applicable.
|
| Communications | 2 | Indicates a communication related issue |
| QualityOfService | 3 | Indicates a quality related issue |
| Processing | 4 | Indicates a software processing issue |
| Equipment | 5 | Indicates faulty equipment |
| Environmental | 6 | Indicates an issue related to the enclosure housing the equipment |
| Integrity | 7 | Indicates duplicate, missing, modified, unexpected, or out of sequence information |
| Operational | 8 | Indicates that the provisioning of the requested service was not possible due to unavailability or malfunction of the service |
| Physical | 9 | Indicates cable tampering or intrusion |
| Security | 10 | Indicates a security violation such as authentication failure or unauthorized access attempt |
| TimeDomain | 11 | Indicates that an event has occurred at an unexpected or prohibited time |
| Fabric | 12 | Indicates a fabric-service related issue |
| Tenant | 13 | Indicates a tenant-service related issue |
| Policy | 14 | Indicates a policy-service related issue |
| Alarm Name | ID | Type | Max Alarm Instances | Description | Associated Alerts | Severity | Will Clear | Raise or Clear Conditions (Status Change) | Action |
|---|---|---|---|---|---|---|---|---|---|
| Certificate Expiration | 32000 | Security | 7 (application certificate types) | Raise an alarm to notify that an XCO certificate is about to expire or has expired. | XCO
3.2.0: CertificateExpiryNoticeAlert CertificateExpiredAlert CertificateRenewalAlert XCO 3.3.0: CertificateUnreadableAlert |
Warning / Critical | True | Warning: Expiration of an XCO certificate within 90 days
(Certificate Expiry Notice Alert) or Error reading the certificate
during component polling (Certificate Unreadable
Alert) Critical: XCO certificate has expired (Certificate Expired Alert) Cleared: XCO certificate renewal (Certificate Renewal Alert) |
Notify APP_ALARMS syslog / webhook |
| Device Certificate Expiration | 32001 | Security | Number of Devices * 3 (device certificate types) | Raise an alarm to notify that a device certificate is about to expire or has expired. | XCO
3.2.0: DeviceCertificateExpiryNoticeAlert DeviceCertificateExpiredAlert DeviceCertificateRenewalAlert XCO 3.3.0: DeviceCertificateUnreadableAlert DeviceCertificateDeviceRemovedAlert |
Warning / Critical | True | Notify APP_ALARMS syslog / webhook | |
| Login Authentication | 32010 | Security | Number of Users* *This Includes existing and non-existing application users. |
Raise an alarm to notify suspicious login activity. | LoginFailureAlert | Warning | False | Warning: 5 successive failed login attempts within 1 minute System will not clear the alarm. |
Notify APP_ALARMS syslog / webhook |
| LDAP Server Connectivity | 32030 | Communication | 4 (number of supported LDAP servers) | Raise an alarm and notify an LDAP server is no longer reachable. | LDAPServerConnectivityFailureAlert LDAPServerConnectivitySuccessAlert LDAPServerConfigurationRemovedAlert |
Major | True | Major: LDAP server connectivity
failure. Cleared: LDAP server connectivity restored or LDAP server configuration removal. |
Notify APP_ALARMS syslog / webhook |
| Storage Utilization | 32040 | Processing | Number of Nodes * 2 (monitored mount points) | Raise an alarm to notify storage utilization for XCO installation has reached a certain threshold or it is full. | StorageUtilizationThresholdAlert StorageUtilizationFullAlert StorageUtilizationCheckAlert |
Warning - Critical (All severities between Warning and Critical are possible) |
True | Warning: File system utilization is 75% - 84% (Storage Utilization Threshold Alert) Minor: File system utilization is 85% - 94% (Storage Utilization Threshold Alert) Major: File system utilization is 95% - 96% (Storage Utilization Threshold Alert) Critical: File system utilization is 97% - 100% (Storage Utilization Threshold Alert or Storage Utilization Full Alert) Cleared: File system utilization is below 75% (Storage Utilization Check Alert) |
Notify APP_ALARMS syslog / webhook |
| Device Connectivity | 32500 | Communications | Number of Devices | Raise an alarm and notify a registered device has lost connectivity either due to the configured device health setting or during a device inventory update. | DeviceConnectivityFailureAlert DeviceConnectivitySuccessAlert DeviceConnectivityDeviceRemovedAlert |
Major | True | Major: Device connectivity failure. Cleared: Device connectivity restored or Device registration removal. |
Notify APP_ALARMS syslog / webhook |
| HA Service Redundancy | 32050 | Operational | 1 (single HA service alarm) | Raise an alarm and notify a loss of redundancy and/or failover has occurred. | HAServiceNonRedundantAlert HAServiceFullyRedundantAlert HAServiceNewActiveAlert |
Major | True | Major: HA redundancy is lost Cleared: HA redundancy is restored |
Notify APP_ALARMS syslog / webhook |
| Node Service | 32051 | Operational | 1 (single node service alarm) | Raise an alarm and notify the nodes‘ services are not all running and degraded. | ServiceDegradedAlert ServiceRestoredAlert |
Warning | True | Major: Nodes‘ services are not all
running. Cleared: Nodes‘ services are all running |
Notify APP_ALARMS syslog / webhook |
| Fabric Health | 33000 | FabricService | Number of fabrics | Raise an alarm and notify that fabric health is changed. Note: The fabric alarm and
fabric alarm status update notifications indicate that the fabric
alarm is cleared when it should remain raised, but quickly updated
to the proper raised state.
|
FabricStateDegradedAlert
FabricStateHealthyAlert FabricPhysicalTopologyDegradedAlert FabricPhysicalTopologyHealthyAlert FabricDeviceAppStateDegradedAlert FabricDeviceAppStateHealthyAlert FabricDeviceProvisioningStateDegradedAlert FabricDeviceProvisioningStateHealthyAlert FabricDeviceMctDegradedAlert FabricDeviceMctHealthyAlert FabricDevicePhysicalTopologyDegradedAlert FabricDeviceUnderlayTopologyDegradedAlert FabricDeviceOverlayTopologyDegradedAlert FabricDevicePhysicalTopologyHealthyAlert FabricDeviceUnderlayTopologyHealthyAlert FabricDeviceOverlayTopologyHealthyAlert FabricHealthDegradedAlert FabricHealthRestoredAlert FabricDeviceRemovedAlert FabricDeletedAlert |
Major | True | Major: Fabric health Degraded Cleared: Fabric Health Restored |
Notify APP_ALARMS syslog / webhook |
The maximum alarm instance calculation is as follows:
CertificateExpiration Instances) + (DeviceCertificateExpiration Instances) + (LoginAuthentication Instances) + (StorageUtilization Instances) = (7) + (20 * 3) + (10) + (2 * 2) = 81