UCS chassis PSU error

Hi team ,
We are getting error on PSU for Cisco UCS chassis.
Its showing NA under performance & voltage tab.
We tried resetating PSU as well as removing power cable & connecting it back.
PSU is power-on & operational.
Can anyone suggest why this issue is & how to get rid of this.

Hi Ashish ,
It is possible that you are hitting I2C issues. I recommend to open a TAC case to have an engineer look at your environment and confirm that the I2C bus is congested.
Here are your options to clear the i2c bus:
1.You can reseat the IOMs you will need to reseat one IOM at a time starting with the IOM connected to the subordinated fabric, This should not cause a complete outage. However, you should perform this during a maintenance window. Please note, this method does not always clear the i2c bus 100% of the time. You may have to use option 2 if this is the case.
2.The second option is to power down then power back up the chassis. This method clears the i2c bus 100% of the time. However, the down side is it is service impacting and will need to be done during a maintenance window.

Similar Messages

Chassis-seeprom errors

We have two different UCS systems that show chassis-seeprom errors (one is a brand new production system). E.g.,
cnat-pod1-ucs6248-A# show cluster state
Cluster Id: 0xde5abc12999911e1-0xb8c9547fee4ca524
A: UP, PRIMARY
B: UP, SUBORDINATE
HA READYDetailed state of the device selected for HA storage:Chassis 1, serial: FOX1326G5KD, state: active with errors
Fabric A, chassis-seeprom local IO failure:FOX1326G5KD READ_FAILED, error: TIMEOUT, error code: 10, error count: 37503
Fabric B, chassis-seeprom local IO failure:
FOX1326G5KD READ_FAILED, error: TIMEOUT, error code: 10, error count: 37504
Warning: there are pending SEEPROM errors on one or more devices, failover may not complete
UCSM seems blissfully unaware of the error. It does occasionally log events:
cnat-pod1-ucs6248-A# show event | include shared-storage
2012-05-12T15:28:14.547     78004 E4196535 device FOX1326G5KD, error accessing shared-storage
2012-05-12T15:28:14.546     78002 E4196535 device FOX1326G5KD, error accessing shared-storage
2012-05-11T05:43:14.544     77962 E4196535 device FOX1326G5KD, error accessing shared-storage
2012-05-10T16:43:14.544     76405 E4196535 device FOX1326G5KD, error accessing shared-storage
2012-05-09T20:43:14.544     74748 E4196535 device FOX1326G5KD, error accessing shared-storage
2012-05-09T13:28:14.544     67198 E4196535 device FOX1326G5KD, error accessing shared-storage
        or in the GUI --
But at least in my case, the error counters keep going up every few seconds, but there hasn't been an event for 3 weeks. Cisco's message/fault guide indicates that this event is very serious error and that TAC should be contacted. If that's the case, how come these are logged as events and not faults? How come there is no call-home trigger for this condition?
-Craig

Zaira,
Is your advice true if the error count is constantly increasing? Below is a related TAC note that one of my colleagues received:
Q: Why the error accessing shared-storage fault can happen and why it is not harmful.
A: In UCS chassis design, we build in a chip called, SEEPROM, on the backplane. SEEPROM is a permanent memory and used to store SAM DB version to avoid the case of SAM DB being overwritten by old version when failover happens. The communication between IO module and SEEPROM through a wiring on backplane is not repliable. To overcome this difficulty, we store the identical SAM DB version in three chassises rather than in one (so called three chassises redundancy). Because the communication between IO module and SEEPROM is not repliable, the error accessing shared-storage fault can happen sometimes - this is system behavior per specification and design. So, as long as one SEEPROM is readable, the UCS works normally. In your reported case, one chassis SEEPROM has read problem and the other two work. So, the error accessing shared-storage fault is not harmful and does not affect the system operability.
It seems that this isn't harmful if the error happens periodically. But what if the SEEPROM error count is increasing every minute? Doesn't that indicate that the SEEPRM can never be read? Wouldn't that be very serious if the UCS system had only one or two chassis?

QoS on the UCS Chassis

I bought a UCS chassis with two blades that are 'qualified' for Cisco Voice products (cm, ccx, etc).... i decided to not buy the $20,000 worth of VMWARE enterprise pro licenses and the v1000 switch... since the ROI is simply not there (I'd rather have 4 separate pieces of hardware then spend that much money on software)... anyway... so now my questions are:
1. What QoS options are available (if any) on the uplink from the chassis to the 6120s and from the 6120s to my 4500 switch.
2. What Qos options are available (if any) on individual hosts inside my vmware.
3. Can I buy the v1000 switch (which i believe is a few grand) and get some QoS without buying the stupid expensive vmware enterprise pro?
...or do i just return the chassis?
Thanks!

Terry,
1. UCS traffic will maintain is CoS markings on the egress of the UCS system. It's then up to the upstream switch to honor these marking accordingly. All CoS markings between the Chassis and FI will be honored on the IOM to prioritze traffic accoridngly in the event of congestion using PFC. Have a read on tha attached paper about UCS & QoS, should help you get an understand on the system handling of QoS/CoS.
2. VMware 5 does offer some new auto quality of service options. Have a read through:
What's new in vSphere 5 Networking
3. No. Any Distributed Switch (VMware vDS or Cisco 1000v DVS) requires the Enterprise Plus license. This includes both the Cisco 1000v and VN-Link in Hardware (PTS with Palo M81KR adaptor).
Regards,
Robert

Ucs chassis qos support

I bought a UCS chassis with two blades that are 'qualified' for Cisco Voice products (cm, ccx, etc).... i decided to not buy the $20,000 worth of VMWARE enterprise pro licenses and the v1000 switch... since the ROI is simply not there (I'd rather have 4 separate pieces of hardware then spend that much money on software)... anyway... so now my questions are:
1. What QoS options are available (if any) on the uplink from the chassis to the 6120s and from the 6120s to my 4500 switch.
2. What Qos options are available (if any) on individual hosts inside my vmware.
3. Can I buy the v1000 switch (which i believe is a few grand) and get some QoS without buying the stupid expensive vmware enterprise pro?
...or do i just return the chassis?
Thanks!

Terry,
UC on UCS deployment design considered the hardware features and UC software requirements
and concluded that there will be no congestion for the IP traffic until it leaves Fabric Interconnect.
So for the following traffic flow, we do not need additional QoS ( L2 COS ) configuration.
UC App > vSwitch > physical adapter > IOM > FI > upstream switch
However, if you have other virtual machines in the blade that contends for the bandwidth, then you environment might need Nexus 1000v or QoS configuration on the UCS.
Please refer following doc for additional information
http://docwiki.cisco.com/wiki/QoS_Design_Considerations_for_Virtual_UC_with_UCS#QoS_Design_Considerations_for_VMs_with_Cisco_UCS_B-Series_Blade_Servers
HTH
Padma

UCS Chassis Not Recognized

Hello,
I am having a strange issue with a new UCS environment that we just brought online. One of the four UCS chassis had an issue with its firmware upgrade, specifically the IO module. All of the other componants on all of the other UCS chassis upgraded just fine but these two IO modules hung during the firmware upgrade. I tried to downgrade the firmware on all of the other componants to match the hung IO modules to see if they would come back online and they did not. I also moved the IO modules into a known working chassis and they worked after an auto-upgrade of the firmware! I then swapped them back to their original chassis thinking that they would be ok but they went down again, stating a communication problem and the 6140 reported them as being link-down. I restarted the entire chassis and also swapped the uplink cables and still they show offline. As a last ditch effort I deleted the entire chassis and went back to re-add it and now it will not even detect the chassis.
I know that the IO modules are fine because I can put them in another chassis and they will come up but as soon I put them back in their original chassis, the 6140's report the link as being down and it will not recognize the chassis. Does this sound like a hardware issue with the chassis itself? Any ideas?

Can you try using the cables from your "good" Chassis on the failing one?
I'd suggest you completely power down the bad chassis. Take the cables from a good chassis, move them over, then power the bad Chassis back up.
If this doesn't work let me know. Also ensure your Chassis discovery policy is set to 1 link for now.
Robert

UCS Chassis 5108 both IOMs inaccessible

Dear forum users,
Problem description: Sometime our UCS Chassis 5108 and both IOM are suddenly INACCESSIBLE. This happens frequently (Happend 5 times in just a month)
Temporary Solution: To unplug and re-plug Chassis power cords twice, then the Chassis back to normal
Once the Chassis is inaccessible state, below are what we witness on the Chassis:
- All the blades LEDs on chassis-1 shows amber lit
- 8 ports on IOM A and IOM B shows NO LED lit (Not even amber lit)
- Sudden increased in Fan speed on chassis-1
- FI ports which connected to Chassis-1, shows NO LED it
- Please find attached (Chassis-1_Fault.jpg) Fault message on chassis-1
We had tried the following:
- Tried re-sit the uplink cable
- Tried replacing the uplink cable, the port is still down
- Reboot FI
- Decommission the chassis-1
- Recommission the chassis-1
Below is our setup environment:
- 2x UCS 6248UP
- 2x UCS 5108
- 4x UCS 2208XP (2 IOM per chassis)
- 2x UCS B200 M2
- 5x UCS B250 M2
- Firmware 2.0(3b)
- Each IOM has 4 Uplink cables connect to FI
- Chassis Discovery Policy
1. Action (4 Links)
2. Link Grouping Preference (Port Channel)
We hope, someone should have experience with the same problem or have some advise to be shared.
Please let me know should you need any further details of the problem or other information.
Look forward to a positive reply.

Hello Mohamed,
Please open a TAC service request with UCSM and Chassis tech support log files.
Also, include approximate date & time of the event.
Padma

Chassis power error and time

major,F0408,117295,sys/chassis-1/fault-F0408,power-problem,2012-08-08T13:45:12,Power   state on chassis 1 is redundancy-failed
what does this mean? Both the power cables are connected, and they have status "Operable" in Chassis Power GUI.
Other than that, no faults.
Is it possible to set the time without using NTP? Do I have to set time from NX-OS command-line?

Hi Atle,
I have seen that kind of issues here and there is something you can try in order to correct this problem:
A workaround to clear the I2C faults is to reseat fan trays, PSUs, and IOMs. Here is how to do it:
1.            Reseat the fans from fan 1 to fan 8.
2.            Reseat the PSUs from PSU 1 to PSU 4.
Pull the components out one at a time from 1 to the last, leave it out for at least 3 minutes before reinsert it back, observe the light to make sure all return to green before pulling the next one.
3.            If the above does not work, pull out the IOM that is
flashing amber. Leave it out for 5 minutes and reinsert. Make sure
everything comes up and the lights turn green.
4.            Monitor the system while reseating components by issuing
# show tech-support chassis 1 iom 1 brief
5.            May have to reseat the second IOM if amber lights shifted.
6.            If reseating the IOM does not solve the problem, we may
need to reacknowledge the chassis. This is disruptive to network
connections of the blades. You need a set a downtime to do it.
7.            Repeat these steps on all chassis that are having amber lights.
I strongly recommend you upgrade the firmware to 1.4(3q) and above when
you are able to set a downtime. The errors will need to be clear before
the upgrade. Otherwise the message may remain until you reseat the
components.
This is just a cosmetic issue on the UCS environment.
Hope this helps!
David

UCS Chassis I/O problems

: Anyone else having Cisco UCS 6140/5108 chassis problems that cause the fans to act up and the I/O card to have power and temp alarms ver1.3.0 even when the environmental conditions are OK?

FYI there are a couple of fixes in this release for these problems. I believe the problem you are describing is related to this, which is part of the release discussed.
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtl43716

Cisco UCS Management Pack Error

Hello,
I'm trying to configure the UCS Management pack for SCOM but when I try to configure in the Authoring pane, the IP + Username password, I have this error:
Data at the root level is invalid. Line 1, position 1.
I'm using the last version of the management pack, 3.0.2.
Any idea?
Thank you.
Regards,
Florent

Hello,
Check this below links
Release Notes for Cisco UCS Manager Management Pack for Microsoft SCOM MP 2.6.1:
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/msft_tools/scom/scom_2.6/scom_2.6_release_notes/scom_releasenotes_2_6.html
User Guide for Cisco UCS Manager Management Pack for Microsoft SCOM MP 2.6.1:
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/msft_tools/scom/scom_2.6/scom_2.6_user_guide/scom_2_6_userguide.html
https://communities.cisco.com/community/technology/datacenter/ucs_management/cisco_ucs_developed_integrations/blog/2013/10/18/cisco-ucs-manager-management-pack-for-microsoft-scom-version-261
Regards
keshav

UCS chassis uplinks recommendation

Hi All,
We currently have a UCS B chassis with 4 blades & 4 uplinks to the FI 6124 (2 from each FEX). We are now looking to populate the chassis with 4 additional blades & was wondering if there is a best practise/guidance document on how many uplinks one should have with a fully populated chassis.
Thanks
Kassim

Kassim
It all depends on the environment and what degree of oversubscription are you comfortable with between the IOM and the FI.
As you are already running UCS, I would start by looking at the current utilization to begin with.
The 2104 is characterized by 8 downlinks (server facing or HIFs) and up to 4 uplinks (FI facing or NIFs).
A starting config can be either 1, 2 or 4 links i.e 2^x number of links for static pinning.
Within UCS QoS can be configured so you can specify min bandwith guarantee at the time of congestion.
If you just want to get a feel for whats out there, most of the time I have come across 2 links per side.
Again, what I have seen most and not a best practise/guidance by any stretch.
Thanks
--Manish

Chassis View error

We have the "typical" error (LMS 3.0.1+CV 6.1.7):
Cannot find applicable device package for x.x.x.x:
This error could be due to one of the following:
- The device package for this device type is not installed.
- Device support for this device type is not available.
- You are trying to open a component inside a device.
To correct the problem, either install a device package for the device type, or open the
parent device to manage the component."
Looking through support, we have found:
Shutdown Daemon Manager, then copy all of the .zip files from NMSROOT/www/classpath/com/cisco/nm/xms/psu/pkgs/cvw to NMSROOT/MDC/tomcat/webapps/CVng/WEB-INF/classes/com/cisco/nm/cvw/devpkgs. then restart Daemon Manager
We have problem with a SW6503, 6509 and 6513, but files are quite strange, i think

They are:
.1.3.6.1.4.1.9.1.282
.1.3.6.1.4.1.9.1.283
.1.3.6.1.4.1.9.1.400
They say it has been working till they deleted and added nodes again.
I have tried to delete package, and intall it again, and always the same error :-(
For Product(s) : CiscoView
Install Invoked by user : admin
The Package(s) Selected for Install :
Cat6000, Cat6000IOS
Successfully installed packages (2):
Cat6000(9.1) ,Cat6000IOS(30.0)
Installation Completed for : CiscoView
After deinstall/install packages, in www folder, only appear:
Cat6000.cv50.v9-1.zip
Cat6000IOS.cv50.v30-0.zip
So, i have to copy Cat6000.zip and Cat6000IOS.zip from MDC folder again!!!
Thanks in advance

LMS 4.2 and PSU Error, Rtr2900 package

Hallo,
WARNING : Rtr2900(5.1):Consistency check failed for base package NGMARShare(1.27)
i get this error by installing Rtr2900 package,
but in the notes for this package NGMARShare 1.26 dependent,
and this is already installed,
is the Rtr package defect or where could i get NGMARShare 1.27 ?
best regards
Alex

You would normally be able to find the NGMARShare 1.27 via navigating to it in the downloads section of cisco.com:
Downloads Home > Products > Network Management and Automation > Routing and Switching Management > Network Management Solutions > CiscoWorks CiscoView > CiscoWorks CiscoView 6.1
However, it appears that 1.26 is the latest version currently posted (release date 23-Jan-2012).

Fault error Code on UCS 6140 Cluster

Hi all,
I'm running a UCS 6140 Cluster with 1.4(3q) UCSM Version.
I've a Critical Fault.
The fault code is F999590. This fault code have no correspondance in the "Cisco UCS Faults and Error Messages Reference" doc.
By searching with fault description, i found:
fsmFailSwFcSanBorderDeploy
Fault Code:F999789
Message
[FSM:FAILED]: sam:dme:SwFcSanBorderDeploy
Explanation
None set.
Recommended Action
Copy the message exactly as it appears on the console or in the system log. Research and attempt to
resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the
Release Notes for Cisco UCS Manager and the Cisco UCS Troubleshooting Guide. If you cannot resolve
the issue, execute the show tech-support command and contact Cisco Technical Support.
Fault Details
Severity: critical
Cause: fsm-failed
mibFaultCode: 999789
mibFaultName: fsmFailSwFcSanBorderDeploy
moClass: sw:FcSanBorder
Type: fsm
How can i investigate more ?
Thanks a lot.
Florent

Hi all,
Here, you will find console output:
fi1-A# sh fault detail
Severity: Critical
Code: F999590
Last Transition Time: 2011-10-10T09:56:12.953
ID: 1509485
Status: None
Description: [FSM:FAILED]: Uplink fc port configuration on B(FSM:sam:dme:SwFcSanBorderDeploy)
Affected Object: sys/switch-B/border-fc
Name: Fsm Deploy Fsm Fail
Cause: Fsm Failed
Type: Fsm
Acknowledged: Yes
Occurrences: 1
Creation Time: 2011-10-10T09:56:12.953
Original Severity: Critical
Previous Severity: Critical
Highest Severity: Critical
fi1-A /fc-uplink # sh int
Interface:
Fabric ID Slot Port Admin State Oper State    State Reason
A              2     5 Enabled      Sfp Not Present
                                                  SFP not present
A              2     6 Enabled      Sfp Not Present
                                                  SFP not present
B              2     5 Enabled      Sfp Not Present
                                                  SFP not present
B              2     6 Enabled      Sfp Not Present
                                                  SFP not present
fi1-A(nxos)# sh san-port-channel summary
U-Up D-Down B-Hot-standby S-Suspended I-Individual link
summary header
Group Port-      Type     Protocol Member Ports
       Channel
100    Spo100               FC      PCP      (U) FC       fc2/1(P) fc2/2(P) fc2/3(P) fc2/4(P)
fi1-A(nxos)#
fi1-B(nxos)# sh san-port-channel summary
U-Up D-Down B-Hot-standby S-Suspended I-Individual link
summary header
Group Port-      Type     Protocol Member Ports
       Channel
200    Spo200               FC      PCP      (U) FC       fc2/1(P) fc2/2(P) fc2/3(P) fc2/4(P)
fi1-B(nxos)#
Thanks for helping
Florent

Unable to load driver for Storage for Windows 2008 UCS B230 M2

I am trying to Boot from SAN windows 2008 R2. I have configured and connected the Cisco UCS Chassis and FI to our Network & Storage .I am having problem to install Windows 2008 R2 Server on Blades as it is not able to see Storage LUN while installation .I downloaded drivers from Cisco Support Site.
I tried drivers from ISO ucs-bxxx-drivers.2.1.3 latest version but Windows is showing driver is available but not installing the driver I am getting the following error and not showing the LUN hard disk to select the installation.
Windows is unabe to locate storage LUN. I am able to LUN while booting process.
I am not sure where I am doing wrong.or I am chosing wrong driver.

I don't see the error message either, but to install W2008 on a boot lun, you must
1) do the zoning of the vhba (initiator) to the pwwn of the storage subsystem port (target)
2) the lun masking / mapping has to be setup
3) fnic driver has to be installed
Therefore, if you don't see your boot lun, either 1) and or 2) has to be fixed
then
4) only one path should be configured (e.g. fabric a), because no multipathing is available during installation, this is very important, and necessary for W2003, 2008 and 2012
and
5) if you see the boot lun, and can install, but the boot fails, the problem is the boot policy !
Very easy ! Good luck !

Ethernet controller driver not installing after Windows Server 2008 installation on Cisco UCS blade

I am using MDT 2010 to deploy Windows Server 2008 to a Cisco UCS B200 blade. The OS and hotfixes install with no problem. The system reboots and attempts to connect to the deployment share to continue with the task sequence and I receive an error stating
"A connection to the deployment share could not be made. The following networking device did not have a driver installed. PCI\VEN_1137&DEV_0043&SUBSYS_00481137&REV_A2"
The driver in question is the driver for the Ethernet controller for the UCS blade. More specifically, it is the network driver for the Palo card in the UCS Chassis. When I Ignore or Abort the install, I am able to manually install the driver and restart the
task sequence. The build then completes successfully with no further issue. I just cannot seem to automate the driver install. Has anyone dealt with this type of issue?

Vik and stealthfield - thank you for your responses.
I was preparing a script to manually move the driver into the c:\windows\inf location when I had to stop to create a new task sequence for a different build. It was while building this task sequence that I found the soulution to the problem.
In the Post Install -> Inject Drivers step of the Task Sequence, I noticed that it was executing a command of type "Inject Drivers" with a selection profile of "All Drivers" and "Install only matching drivers
from the selection profile" selected.
I changed this to run a command of type "Run Command Line" and specified that it execute "%Scriptroot%\ZTIdrivers.wsf". I noticed that this was selected in one of my other builds that was working properly, so I thought I'd
give it a try. - IT WORKED.
So to sum up, the solution was to change the type of command being executed in the "Post Install -> Inject Drivers" step of the task sequence. After this change, the machine came up and continued the task sequence with no further issues.
Thanks again for the responses - They were helpful and I do appreciate it.

UCS chassis PSU error

Similar Messages

Maybe you are looking for