Understanding XML alert lifecycle of UCS Manager

[gbbhat]

My question is specifically around how to tell if a call home xml alert is cleared or not.

I have noticed that in an alert,

there are several values which point to alert severity.

1. in the envelop body:

<soap-env:Body>
<aml-block:Severity>5</aml-block:Severity>

Here the number 5 is telling the alert severity. It is at major level from the document page 3.

However,

2. In the Attachment section,

<aml-block:Attachments>
<aml-block:Attachment type="inline">
<aml-block:Name>sam_content_file</aml-block:Name>
<aml-block:Data encoding="plain">
<![CDATA[
<failureDetail>
<faultInst
ack="no"
cause="thermal-problem"
changeSet=""
code="F0409"
created="2019-05-23T01:16:36.797"
descr="Thermal condition on chassis 5 is upper-critical"
dn="sys/chassis-5/fault-F0409"
highestSeverity="major"
id="11690744"
lastTransition="2019-05-23T03:19:16.874"
lc=""
occur="22"
origSeverity="major"
prevSeverity="major"
rule="equipment-chassis-thermal-threshold-critical"
sacl="addchild,del,mod"
severity="cleared"
status="modified"
tags="server"
type="environmental"/>
</failureDetail>]]>
</aml-block:Data>
</aml-block:Attachment>
</aml-block:Attachments>

there are 3 more severity related values,

highestSeverity="major"

origSeverity="major"
prevSeverity="major"

severity="cleared"

Does that mean the alert is cleared or still a major?

[josoneal · Accepted solution]

Hello gbbhat,

Yes, severity="cleared" Means that the fault has been cleared from the UCS.
If the fault was still being seen it would look something like this

origSeverity="major"
prevSeverity="major"
rule="equipment-chassis-thermal-threshold-critical"
sacl="addchild,del,mod"
severity="major"

-Josh