Use the information in the following tables to learn about all possible backup and restore alerts that are raised by Fault Management.
31070 | System Backup Initiated |
---|---|
Description | Send an alert when a backup is initiated. |
Preconditions | None |
Requirements |
Alert shows the following data:
The following example shows an alert when a system backup is
initiated:
<118>1 2003-10-11T22:14:15.003Z xco.machine.com FaultManager - - [meta sequenceId=”47”] [origin ip=”10.20.30.40” enterpriseId=”1916” software=”XCO” swVersion=”3.2.0”] [alert@1916 resource=”” alertId=”31070” cause=”operationInitiated” type=”communicationsAlarm” severity=”info”] [alertData@1916 user=”extreme” version=”3.2.0-backup” backup_type=”FabricName” fabric_name=”nonclos” fabric_all=”” device_ips=””] BOMSystem backup type "FabricName" initiated for fabric "nonclos" for efa version "3.2.0-backup" by user "extreme". |
Health Response | Health resources are not associated with system backup. |
31071 | System Backup Success |
---|---|
Description | Send an alert when backup is successful. |
Preconditions | You initiated a system backup or a periodic backup. |
Requirements |
Alert shows the following data:
The following example shows an alert when a system backup is
successful::
<118>1 2003-10-11T22:14:15.003Z xco.machine.com FaultManager - - [meta sequenceId=”47”] [origin ip=”10.20.30.40” enterpriseId=”1916” software=”XCO” swVersion=”3.2.0”] [alert@1916 resource=”” alertId=”31071” cause=”operationSuccess” type=”communicationsAlarm” severity=”info”] [alertData@1916 user=”extreme” version=”3.2.0-backup” backup_type=”FabricAll” fabric_name=”” fabric_all=true device_ips=”” filename="/apps/efa_logs/backup/XCO-3.2.0-backup-2022-12-07T19-05-31.719.tar”] BOMSystem backup type "FabricAll" completed successfully for efa version "3.2.0-backup" by user "extreme" located at "/apps/efa_logs/backup/XCO-3.2.0-backup-2022-12-07T19-05-31.719.tar". |
Health Response | Health resources are not associated with system backup. |
31072 | System Backup Failure |
---|---|
Description | Send an alert when the backup operation fails. |
Preconditions | You initiated a system backup or a periodic backup. |
Requirements |
Alert shows the following data:
The following example shows an alert when backup fails for a
device:
<114>1 2003-10-11T22:14:15.003Z xco.machine.com FaultManager - - [meta sequenceId=”47”] [origin ip=”10.20.30.40” enterpriseId=”1916” software=”XCO” swVersion=”3.2.0”] [alert@1916 resource=”” alertId=”31072” cause=”operationFailure” type=”processingErrorAlarm” severity=”major”] [alertData@1916 user=”extreme” version=”3.2.0-backup” backup_type=”DeviceIP” fabric_name=”” fabric_all=”” device_ips=”10.24.80.55,10.24.80.57” error=” Config backup Failed for device: [10.24.80.55,10.24.80.57], Reason: Devices do not exist”] BOMSystem backup type "DeviceIP" failed for device ips "10.24.80.55,10.24.80.57" for efa version "3.2.0-backup" by user "extreme" due to " Config backup Failed for device: [10.24.80.55,20.24.80.57], Reason: Devices do not exist ". |
Health Response | Health resources are not associated with system backup. |
31075 | System Backup Restore Initiated |
---|---|
Description | Send an alert when the backup restore operation is initiated. |
Preconditions | None |
Requirements |
Alert shows the following data:
The following example shows an alert when a system restore is
initiated from a backup:
<118>1 2003-10-11T22:14:15.003Z xco.machine.com FaultManager - - [meta sequenceId=”47”] [origin ip=”10.20.30.40” enterpriseId=”1916” software=”XCO” swVersion=”3.2.0”] [alert@1916 resource=”” alertId=”31075” cause=”operationInitiated” type=”communicationsAlarm” severity=”info”] [alertData@1916 user=”extreme” version=”3.2.0-backup” filename=” XCO-3.2.0-backup-2022-12-05T15-48-54.920.tar”] BOMSystem restore initiated with "XCO-3.2.0-backup-2022-12-05T15-48-54.920.tar" on XCO version "3.2.0-backup" by user "extreme". |
Health Response | Health resources are not associated with system restore. |
31076 | System Backup Restore Success |
---|---|
Description | Send an alert when the restore operation is successful |
Preconditions | You initiated a system restore. |
Requirements |
Alert shows the following data:
The following example shows an alert when a system restore is
successful:
Syslog RFC-5424 Example: <118>1 2003-10-11T22:14:15.003Z xco.machine.com FaultManager - - [meta sequenceId=”47”] [origin ip=”10.20.30.40” enterpriseId=”1916” software=”XCO” swVersion=”3.2.0”] [alert@1916 resource=”” alertId=”31076” cause=”operationSuccess” type=”communicationsAlarm” severity=”info”] [alertData@1916 user=”extreme” version=”3.2.0-backup” filename=” XCO-3.2.0-backup-2022-12-05T15-48-54.920.tar”] BOMSystem restore completed successfully with "XCO-3.2.0-backup-2022-12-05T15-48-54.920.tar" on XCO version "3.2.0-backup" by user "extreme" |
Health Response | Health resources are not associated with system restore. |
31077 | System Backup Restore Failure |
---|---|
Description | Send an alert when a system restore fails. |
Preconditions | You initiated a system restore. |
Requirements |
Alert shows the following data:
The following example shows an alert when the system retire fails
from a backup:
<114>1 2003-10-11T22:14:15.003Z xco.machine.com FaultManager - - [meta sequenceId=”47”] [origin ip=”10.20.30.40” enterpriseId=”1916” software=”XCO” swVersion=”3.2.0”] [alert@1916 resource=”” alertId=”31077” cause=”operationFailure” type=”processingErrorAlarm” severity=”major”] [alertData@1916 user=extreme”” version=”3.2.0-backup” filename=” XCO-3.2.0-backup-2022-12-05T15-48-54.920.tar” error=”reason for failure”] BOMSystem restore failed with "XCO-3.2.0-backup-2022-12-05T15-48-54.920.tar" on XCO version "3.2.0-backup" by user "extreme" |
Health Response | Health resources are not associated with system restore. |
31078 | System Backup Restore Out of Order Sequence ID |
---|---|
Description | Send an alert when the sequence number is out of order due to
system backup and restore. The alert indicates that the existing sequence number is out of order, and a new sequence number from the backup tar file takes effect. |
Preconditions | Backup tar file already has the alerts. |
Requirements |
Alert shows the following data:
The following example shows an alert when the sequence number
goes out of order for backup and restore:
<118>1 2003-10-11T22:14:15.003Z xco.machine.com FaultManager - - [meta sequenceId=”47”] [origin ip=”10.20.30.40” enterpriseId=”1916” software=”XCO” swVersion=”3.2.0”] [alert@1916 resource=”” alertId=”31078” cause=”informationOutOfSequence” type=”integrityViolation” severity=”info”] BOMAlert sequence number can go out of order. |
Health Response | Health resources are not associated with out of order system sequence. |