Use the information in the following tables to learn about all possible upgrade alerts in detail that are raised by Fault Management.
31060 | XCO Upgrade Initiated |
---|---|
Description | Send an alert when XCO upgrade is initiated. |
Preconditions | None |
Requirements |
Alert shows the following data:
The following example shows an alert when an XCO upgrade 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=”31060” cause=”operationInitiated” type=”communicationsAlarm” severity=”info”] [alertData@1916 deployment_suite=”fabric” deployment_type=”multi-node” deployment_platform=”TPVM” original_version=”3.2.0-v1” new_version=”3.2.0-v2”] BOMDeployment Suite "fabric" upgrade initiated for type "multi-node" on Platform "TPVM" with Original Version "3.2.0-v1" to New Version "3.2.0-v2". |
Health Response | Health resources are not associated with upgrade. |
31061 | XCO Upgrade is successful |
---|---|
Description | Send an alert when XCO upgrade is successful. |
Preconditions | None |
Requirements |
Alert shows the following data:
The following example shows an alert when an XCO upgrade 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=”31061” cause=”operationSuccess” type=”communicationsAlarm” severity=”info”] [alertData@1916 deployment_suite=”fabric” deployment_type=”multi-node” deployment_platform=”TPVM” original_version=”3.2.0-v1” new_version=”3.2.0-v2”] BOMDeployment Suite "fabric" upgrade successfully completed for type "multi-node" on Platform "TPVM" with Original Version "3.2.0-v1" to New Version "3.2.0-v2". |
Health Response | Health resources are not associated with upgrade. |