cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2369
Views
0
Helpful
6
Replies

Gets Faults on 1 chassis when i config or boots a blade

Sandemann
Level 1
Level 1

Hi

I gets this faults when I associate a new blade or boots a blade in one of my UCS Chassis:

<faultInst

ack="no"

cause="thermal-problem"

changeSet=""

code="F0411"

created="2013-05-24T08:11:52"

descr="Thermal condition on chassis 3 cause:Local IOM:IOM unable to get thermal sensor reading from blades(6);Peer IOM:Thermal sensor reading not available from blades(6);"

dn="sys/chassis-3/fault-F0411"

highestSeverity="critical"

id="1127612"

lastTransition="2013-05-24T08:11:52"

lc=""

occur="1"

origSeverity="critical"

prevSeverity="critical"

rule="equipment-chassis-thermal-threshold-non-recoverable"

severity="critical"

status="created"

tags="server"

type="environmental">

</faultInst>

<faultInst

ack="no"

cause="thermal-problem"

changeSet=""

code="F0410"

created="2013-05-24T08:12:47"

descr="Thermal condition on chassis 3 cause: Local IOM:Threshold crossing of thermal sensor reading on blades(1);Peer IOM:Thermal sensor reading not available from blades(6);"

dn="sys/chassis-3/fault-F0410"

highestSeverity="minor"

id="1127621"

lastTransition="2013-05-24T08:12:47"

lc=""

occur="1"

origSeverity="minor"

prevSeverity="minor"

rule="equipment-chassis-thermal-threshold-non-critical"

severity="minor"

status="created"

tags="server"

type="environmental">

</faultInst>

<faultInst

ack="no"

cause="thermal-problem"

changeSet=""

code="F0411"

created="2013-05-24T08:11:52"

descr="Thermal condition on chassis 3 cause:Local IOM:Threshold crossing of thermal sensor reading on blades(1);Peer IOM:Thermal sensor reading not available from blades(6);"

dn="sys/chassis-3/fault-F0411"

highestSeverity="critical"

id="1127612"

lastTransition="2013-05-24T08:12:47"

lc=""

occur="1"

origSeverity="critical"

prevSeverity="critical"

rule="equipment-chassis-thermal-threshold-non-recoverable"

severity="cleared"

status="created"

tags="server"

type="environmental">

</faultInst>

It fix it self, but I wonder if it's something I should do with it?

6 Replies 6

abbharga
Level 4
Level 4

Hi Stig,

Can you get the UCSM version / firmware on the IOM on chassis 3 and the CIMC versions for blades 1 and 6 on chassis 3?

This looks like a communication issue between the IOM and the blades on chassis 3.

./Abhinav

Hi.

UCSM version is 2.0.5a

IOM on Chassis is 2.0.5a

All blade in the Chassis have version 2.0.5a

Is this what you need to find out more?

Hi Stig,

I would recommend opening a TAC case for this and we can take a look at this in more details.

I was suspecting a bug, but that is fixed in the version you running.

./Abhinav

Hi.

This started after I put 3 new servers in slot 6 - 8 in this chassis.

Blade number 6 seems not to work as it should, because I can't connect to any network from this server, but the other new servers have no problems.

So I think that this server may have som issues, that causes this.

What do you think about this? Can this be the case?

/StigS

Stig,

I agree with Abhi, you better open a case so that we can have a deeper look at the environment and diagnose faster/better.

-Kenny

Hi Stig,

There can be multiple things contributing to this, once you have the TAC case we can take a more closer look at those.

Abhinav

Review Cisco Networking products for a $25 gift card