IT Blog

Cisco

UCS: F0382 thermal-problem

by on Feb.06, 2013, under Cisco, UCS

This is a quick post for simple error that you might see in Cisco UCSM.
t1
Affected object: sys/chassis-2/fan-module-1-2
Description: Fan module 1-2 in chassis 2 temperature: upper-critical
Cause: thermal-problem
Code: F0382

This may indicate that there is hardware problem with the fan and it needs to be replaced but quite often it indicates logical problem. There are a few bugs depending on the version that UCS is running that might cause this behaviour.
As we can see from the error the problem is with the fan in chassis 2.
If you click on the blue text it will open a new window and you’ll be able to see which fan it is.
t2

The first thing you can try is to reseat the fan and see if the error goes away. If it does not then it most likely hardware issue.
In this case the error has cleared.
This error might reappear in couple day/weeks or months or it could happen on the other fan. There is a known I2C bug in UCS. To clear i2c bus it is advised to reseat all fans, PSUs and IOmodules(one at a time).
The bug was fixed in late 1.4(3*) version but was reintroduced again in 2.0 version. It should be fixed in latest version.
I UCS system affected by this bug than you still need to reseat components as the upgrade alone will not clear the I2C bus.
IMO it would be best to reseat them before upgrading as at least you’ll be upgrading a healthy system.

1 Comment :, , , , , more...

UCS: Update firmware on Cisco UCS C200 server using Host Update Utility

by on Feb.06, 2013, under Cisco, UCS

Here is a simple procedure how to update firmware on UCS C200 M2 server. The procedure should be no different on the other models of C series servers as they use Host Update Utility(HUU).
1. First you need to download the firmware for the upgrade. In this instance the server will be upgraded to 1.4(3p)5

  • Go to Cisco.com, select Support and All Dowloads 
  • Choose Servers- Unified Computing and Cisco UCS C-Series Rack-Mount Standalone Server Software. Select your server model(in this case it is C200 M2)
  • From select Software type choose Unified Computing System (UCS) Server Firmware
  • Find the required version and download it(you’ll need to login). It will be iso file:

    1

2. Mount HUU iso in CIMC (continue reading…)

Leave a Comment :, , , , more...

UCS: FSM: Unable to find Storage Controller Device for sys/chassis-4/blade-2/board/storage-SAS-1 to perform Image update

by on Jan.30, 2013, under Cisco, UCS

Here is a strange error that popped up recently.
After server reboot the blade got stuck on 47% of associating service profile.
Here is the error:

Remote Result: Service Unavailable
Remote Error Code: 4106
Remote Error Description: Unable to find Storage Controller Device for sys/chassis-4/blade-2/storage-SAS-1 to perform Image update

1

 

When looking in the KVM Console for the blade I can see that it was sitting in the screen below:
2

Here are the things that I’ve tried to fix this and none of these worked:
1. As it was saying about the image update for Storage adapter I though I’ll remove Host firmware policy from the service profile.
2. Next I created a new Host firmware policy but only added firmware SAS storage controller and chose different version than it had.
3. Remove and add service profile back

Here is what worked though:
Removed service profile from blade, re-acknowledged the blade added service profile back. After this the error was gone and the blade was booting normally.
The last step was to add old Hast firmware policy to the service profile and check if that brakes it again, but all worked as expected.
So I’m happy that the blade is back but cannot explain how and why this has happened.

1 Comment :, , , , , more...

UCS: F999616 [FSM:FAILED] communication service configuration(FSM:sam:dme:CommSvcEpUpdateSvcEp)

by on Jan.12, 2013, under Cisco, UCS

In UCSM you see critical error:
Affected object: sys/svc-ext
Description: [FSM:FAILED] communication service configuration(FSM:sam:dme:CommSvcEpUpdateSvcEp)
Cause: fsm-failed
Code: F999616

ntp

The error itself is not very descriptive, so in order to find out what the problem is best it to look at UCSM show-tech support logs.To do that select Admin tab, select All and click on Create and Download Tech support.

ntp1
(continue reading…)

1 Comment :, , , , , more...

I’m now CCNA Data Center

by on Jan.11, 2013, under Cisco

This week I’ve passed 640-911 and 640-916 and now holding CCNA Data Center certification.
Next is CCNP Data Center :)

1 Comment :, , , more...

UCS: flashing cursor after installing Linux (RedHat, Suse), server would not boot

by on Jan.04, 2013, under Cisco, UCS

Here is an interesting thing that happens during Linux installation on Cisco UCS blade.
After installing Suse on Cisco UCS blade, the server would not boot and only flashing cursor is seen. Tried other version of Suse and even RHEL, still the same. This looked strange because I had installed Linux on UCS without any problems before.
There is a small thing that you need to be aware when doing installation. Make sure to add CD-rom in boot order in the the service profile and after you mount your ISO let the sever to pick it up itself. Do not press F6 and choose for it as this is where interesting thing happens.
When you let the server to pick the boot device it makes Linux installer to think that this server is running in UEFI mode.
When you press F6 and choose the boot device the installer thinks it is BIOS mode and when partitions are created, it messes things up there for after reboot you see flashing cursor.

Leave a Comment :, , , , , , , more...

UCS: waiting for flogi

by on Dec.04, 2012, under Cisco, Storage, UCS

Here is one very common error that you can see in  UCS Manager. I’ve observed it in multiple UCS firmware versions and all times it was cosmetic and had no impact.

On the blade you’ll see a major error similar to this:
Description: fc VIF 6 /R A-1095 down, reason: waiting for flogi
Cause: link-down
Code: F0283 

If you go to VIF paths on the blade you’ll see  error ‘waiting for flogi’ on vHBA that has the problem.

Now as I mentioned already this is most likely cosmetic issue. So first you need to verify that this is really the case. (continue reading…)

3 Comments :, , , , , , more...

UCS: Warning: there are pending SEEPROM errors on one or more devices, failover may not complete

by on Dec.03, 2012, under Cisco, UCS

In UCS CLI after issuing command ‘show cluster state‘ a warning is received on one of the chassis.

UCS-B # show cluster state
Cluster Id: 0xf122a7f83dba11e0-0x9a4c123573c4f1c4

B: UP, PRIMARY
A: UP, SUBORDINATE

HA READY
Detailed state of the device selected for HA storage:
Chassis 1, serial: FOX1234567A, state: active
Chassis 2, serial: FOX1234567B, state: active
Chassis 5, serial: FOX1234567C, state: active with errors

Fabric B, chassis-seeprom local IO failure:
FOX1234567C READ_FAILED, error: TIMEOUT, error code: 10, error count: 7
Warning: there are pending SEEPROM errors on one or more devices, failover may not complete

In sam_techsupportinfo  log you’ll see the following message
Creation Time: 2012-10-12T01:12:21.217
ID: 2712562
Description: device FOX1234567C, error accessing shared-storage
Affected Object: sys/mgmt-entity-B
Trigger: Oper
User: internal
Cause: Device Shared Storage Io Error
Code: E4196537

This is known Cisco Bug CSCtu17144 and here is what needs to be done

If the fault condition stays on or keeps being cleared and re-raised, try the following workarounds:
1. Reboot the IO module.
2. Remove and re-seat the IO module. Make sure the module is in contact with the backplane firmly.

I’ve had this problem couple times and resetting IO module was enough in both cases

2 Comments :, , , , , more...

UCS: configuration-failed; Code: F0170; connection-placement; There are not enough resources overall

by on Dec.02, 2012, under Cisco, UCS

Here is an interesting issue that I ran into with Cisco UCS blade.
I needed to move service profile from one blade to another. This is a process that should not give any problems but it did. Dissociation worked fine, but when I tried to associate the same profile with diferent blade I ran into problems.

The first thing I noticed is Config Failure error in Status:

The Configuration error was:
connection-placement
There are not enough resources overall

Not enough vHBAs available
Not enough cNICs available (continue reading…)

1 Comment :, , , , , , , , more...

UCS: After installing or replacing DIMMs shown as disabled in UCS Manager(invalid FRU)

by on Nov.29, 2012, under Cisco, UCS

Here is a problem that you can see when replacing or installing new DIMMs in UCS Blades.
Although the blade will boot but the newly installed DIMMs might show as disabled with invalid FRU error:
Error codes F0844 and F0502 are logged:

When you check inventory of the blade and go into Memoery you’ll see that Capacity and Clock are Unspecified.

SSH into UCSM IP.
Type:
scope server x/y  (where x is your chassis id and y is server id of the server that is having problems.)
show memory  (this list memory information of the blade)
Server 1/1:
Array 1:
DIMM Location Presence Overall Status Type Capacity (MB) Clock

—- ———- —————- ———————— ———— ————- —– (continue reading…)
3 Comments :, , , , , more...