UCSM unable to monitor storage on blade after Firmware update

Unanswered Question
Oct 13th, 2014
User Badges:

I'm getting the following fault on two of my B200-M3 blades after doing a firmware infrastructure autoinstall from 2.2(1d) to 2.2(3b).  Firmware update was successful on everything, so I'm not sure why something happened to the blades.

The UCSM is claiming it can't talk to the SAS card, however the card is indeed working fine, blade boots up and works no problem.  Any ideas?  It seems it just can't monitor the disks for some reason, and I don't get why it's only on two of the blades...

<faultInst
 ack="no"
 cause="equipment-inoperable"
 changeSet=""
 
 code="F1004"
 created="2014-10-12T19:14:14"
 descr="Controller 1 on server 1/6 is inoperable. Reason: CIMC did not detect storage controller"
 dn="sys/chassis-1/blade-6/board/storage-SAS-1/fault-F1004"
 highestSeverity="critical"
 id="1335505"
 lastTransition="2014-10-12T19:14:14"
 lc=""
 occur="1"
 origSeverity="critical"
 prevSeverity="critical"
 
 rule="storage-controller-inoperable"
 severity="critical"
 status="created"
 tags="server"
 type="equipment">
 </faultInst>

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Walter Dey Mon, 10/13/2014 - 13:14
User Badges:
  • Red, 2250 points or more
  • Cisco Designated VIP,

    2017 Unified Computing, Storage Networking

What version CIMC, BIOS does your server run ?

Did you try a CIMC reset ?

john.paul.albe Tue, 10/14/2014 - 07:17
User Badges:

Name

ModelRunning Version
Adapters  
Adapter 1Cisco UCS VIC 12402.2(1d)
BIOSCisco UCS B200 M3B200M3.2.2.1a.0.111220131105
Board ControllerCisco UCS B200 M311
CIMC ControllerCisco UCS B200 M32.2(1d)
john.paul.albe Tue, 10/14/2014 - 07:21
User Badges:

I disassociated the server and pulled it out of the chassis and then plugged it back in.  Not sure if that would have the same effect as CIMC reset...

john.paul.albe Tue, 10/14/2014 - 09:26
User Badges:

Answer was to disassociate server from profile, remove server from default pool, yank it out of the chassis, put it back in, re-add to default pool, re-associate with service profile.

As they say on the IT Crowd, "Did you try forcing an unexpected reboot?"

Ssathevai75 Fri, 11/07/2014 - 16:13
User Badges:

Try CIMC reset and if that didn't work Disassociate and reassociate the Service profile should clear the error.

UCS-A# scope server 2/4

UCS-A /chassis/server # scope CIMC

UCS-A /chassis/server/cimc # reset

UCS-A /chassis/server/cimc* # commit-buffer

UCS-A /chassis/server/cimc #  

Actions

This Discussion