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

Similar Messages

  • 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

  • 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 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.

  • 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

  • UCS XML API Query Problem

    Currently I am attempting to power up and down a blade that is un-attached to a profile using a UCS XML API Query.
    Current progress:
    I have come up with this query that will power down a blade from a call from an attached profile...
    <configConfMo cookie="<SomeCookie>" inHierarchical="false">
    <inConfig>
    <lsPower dn="org-root/ls-profile1/power" state="down" status="modified"/>
    </inConfig>
    </configConfMo>
    This works for a server that is attached to a profile <profile1>, but I want to power down a server that is un-attached. I am currently using  UCS emulator 2.2 for testing these querys.

    There are a few options here that occur to me:
    Go to either the web interface of one of your UCSMs or the emulator with something like:
       http:///visore.html  or https:///visore.html
    traverse the objects or search for what you want and follow the '?' link to the right of the Class name.
    You could also try to find what you need here: http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/api/VScgIX.html

  • UCS SAN LUN access problem

    Hi All
    i have UCS manger 4.3q, 2xFI 6140 and connected to Cisco MDS 9509 v4.2( 4 FC link from FIA to MDS A, and 4 FC uplink from FIB to MDS B) and connected to SUN SAN storagetek 6140(one FC port to MDS A from SP1 and one FC port to MDS B from SP2), i created service profile with 2 VHBA for FIA and FIB (with different VSAN), after that we installed ESXi 4.1 on local disk but when we tried to brows LUN created on SAN we can not.
    from both FI we can see WWPn:WWPN for each VHBA in created server, from MDS also i can see floggi output for SAN (WWN,WWPN) as target and Server VhBA as initiater.
    i make all possible isolation even i disbaled FC of FI B, and till now we can not access LUN on  SAN, as per SAN admin LUNS created and mapped correctly, so appreciate your support to solve this.
    Many thanks.

    Hi
    From your statement, I understand that you are using SUN SAN storagetek as disk array storage. Cisco does not list the SUN SN storagetek in their interoperablity matix and this could be one of the reason. Pleas go through the link below.
    http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/Matrix8.html#wp323848
    Ram

  • Ucs question about major code F0283 and dce interfac and chassis number?

    dear,
    Introductions:
    one 6120 connect  chassis 1 one 2104-1 and   chassis 2 one 2104-1
    chassis 1 have sever 3/4/5/6/7/8  (all sever is B200 M3,two 2104)
    chassis 2 have sever 1/2/3/4/5/7 (sever 1/2/3/4 is B200 M3,two 2104)
    question
    1.major code F0283
    all server have  major code F0283 ,but all sever  still can use.what this? How I did it?
    affected object:sys/chassis-1/blade-6/fabric-A/path-1/vc-722
    description: ether vif 1/6 a-722 down,reason: unknown
    chassis 1 have sever 3/4/5/6/7/8
    chassis 2 have sever 1/2/3/4/5/7
    i shutdown all ,and start the problem is also.
    affected 
    i shutdown all ,and start the problem is also.
    2.on chassis 1 sever-1 adapter 1 dce interface (dce interfac 1 and dce interface 5)
    ony one use? 
    3.
    chassis 1 have sever 3/4/5/6/7/8
    chassis 2 have sever 1/2/3/4/5/7
    but i reboot ,
    chassis 2 have sever 3/4/5/6/7/8
    chassis 1 have sever 1/2/3/4/5/7
    so the profile is disorder
    i shtdown all,and start chassis 1 ok ,later chassis 2
    the problem is ok..what this ?

    Hi Hailing,
    The transport VIF for server is down.The Cisco UCS Manager raises this fault when any of the following scenario occur:
    •Endpoint(switch/fabric  interconnect) reports the connectivity state on virtual interface as  one of: a.down, b.errored, c.unavailable.
    Verify  that the blade discovery was completed successfully. Check the states  on all of the communicating ports in an end to end manner.
    If connectivity seems correct, recommision the server.
    Also, please make sure you are using the correct drivers of the OS installed in the server as Padma recommended you.
    I hope this helps.
    David

  • Windows 2008 r2 ethernet problem on UCS

    i have installed windows 2008 R2 on a B440 M2 and having issues with the network. not able to ping even the default gateway or any other servers on the same network/vlan
    an esx server in the same VLAN works fine.
    i know this is only partial information, but was wondering if there was some config off the top that i am missing
    p.s. my chassis has the palo card

    The most common issue I see in this instance is that the servrice profile associated with Windows does not have the associated vlan marked as native.
    - Confirm the service profile has the appropiate vlan
    - Confirm the vlan is marked as native
    - Can the windows OS ping other hosts on the same subet in the same UCS chassis
    - Is there an impact if you force traffic over fabric A or B.
    HTH,
    Dan

  • Linux 2.6 kernel VM problem on UCS SP with linux KVM

                       Hi,
    IHAC who configured  3 service profiles running the Linux-KVM virtualisation solution (ubuntu serveur 12.04 LTS).
    He migrated Linux VMs from HP servers running the same Linux-KVM version to the service profiles.
    Everything is OK with all linux VMs running a kernel version 3 (Freebsd 9.0 ou Ubuntu 12.04).
    All VMs with a linux kernel version 2.6 (Freebsd 9.0 ou Ubuntu 12.04) have network problem on the Service Profiles (but work OK as-it on HP servers).
    These VMs can only ping the VMs on the same Srvice Profile and the Linux-KVM server they are tied to.
    They cannot ping the VMs on other SPs or machines out of the UCS solution (arp resolution problem)
    If the customer updates a such VM to a kernel version 3 it works fine.
    Unfortunatly he cannot do this update for all the VMs he's got.
    Any idea ?

    I assume since you mentioned 'SP', you are using Service Profiles and this is some UCS B-Series or C-Series integrated solution.  Advise your customer they are implementing unsupported OSes and most likely denied supported from TAC.
    http://www.cisco.com/en/US/docs/unified_computing/ucs/interoperability/matrix/r_hcl_B_rel2.04.pdf
    Operating System Interoperability Matrix
    Novell, Oracle, Redhat are the supported linux variants in the current release.
    Ubuntu claims not to support 12.04 on cisco hardware at this time.
    http://www.ubuntu.com/certification/server/make/Cisco%20UCS/?csrfmiddlewaretoken=2bad1e15c5be00d90385920e85177fa6&query=&release=12.04+LTS&level=Any
    It seems that earlier versions of Unbuntu is stated to be supported on Cisco hardware but not listed on Cisco support docs.  We can review that further if needed.
    Feel free to check out the PDI Helpdesk and what services we can offer qualified Cisco partners.
    http://www.cisco.com/go/pdihelpdesk
    Thank You,
    Dan Laden

  • 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.

  • Connect to a CIMC of a UCS blade

    Hi togheter,
    we are having a UCS environment (firmware 1.4j) with 6 chassis. It is all configured and already operatable. It is configured that a service profile gets his managment ip pooled and the same belongs to the CIMC ip. All blades get their ip with no problems. But when I want to connect to a CIMC ip via browser (http://CIMC-ip) I get no answer. I am able to ping the CIMC ip and I am able to connect via ssh to the ip but there I have no idea about the username/password.
    Has anyone an idea where the problem is located?
    Kind regards
    Philippe Bosle

    Sorry for posting to this old thread, don't know what the posting rules are...we are running into a similar issue on two different UCS chassis setup.
    The FI and mgmt pool are in the same subnet.
    I can ssh into the Fab mgmt vip, FabA & FabB.  The KVM console to the blade works, but I can't access the blade CIMC via the browser.  How can I check my configuration and troubleshoot this issue?
    Thanks in advance,
    -- prasad

Maybe you are looking for