Cisco UCS chassis hardware monitoring - c220?

Similar Questions

• Migration from HP C7000 to Cisco UCS

  Hello

  What is the best way to migrate servers currently on the HP chassis equpment to a whole new Cisco UCS chassis? It is for example a HP tool to migrate to a lun to start? Then we can start the same servers on Cisco UCS?

  Or do we have to reinstall every server and restore the backups in a window maintenance?

  physical server = i.e. ESXi? You must install this in your UCS blades? same goes for Windows or Linux? I don't see another solution?

• Cisco UCS B200 M4Compatible with 2100 FEX in UCS 5108 chassis & FI 6100?

  Hello

  The blade server Cisco UCS B200 M4 is compatible with FEX 2100 within a Cisco UCS 5108 chassis & Cisco UCS 6100 fabric of interconnection?

  The interop tool said clearly for the B200-M4:

  http://www.Cisco.com/Web/TechDoc/UCS/interoperability/matrix/matrix.html

  Note 14: The 2104XP fabric Extender is not compatible when the 1240 and 1280 or 1240 and VIC Port Expander are combined on the same blade. Applies to the M3 and M3 B200 as well as B420 B22 with 1240 and the 2 adapter connector populated

  or for the VIC 1340

  Note 38: 6100 series fabric interconnects and 2100 series fabric Extender is not supported

• How can Cisco ucs c220 m4 I start with 12g cisco sas controller? 2012 UEFI Server installation issues

  first time with cisco ucs c220 m4, check my photos

  You have a VD 11TB.

  Only way to start on this is by using UEFI.

  You need to activate UEFI in the boot order.

  Anything over 2 TB and more 4 K sector size readers require the UEFI boot option.

  BIOS will not process the VDs when manages UEFI.

  Kirk...

  Summary for those who seek a similar question:

  • Client a large VD created, 11TB
  • 2 TB and more, 4K sector drives, require boot UEFI + GPT, cannot use the legacy/MBR
  • To set startup to local HD option, that referenced the PCI-E Slot, the raid controller was in (HBA slot in this case)
  • UEFI mode, can't score a VD as "bootable disk / startup.
  • You will see not the VD/raid controller appear in the 'real' boot order during the OS install.
  • Once the installation of the OS compatible UEFI is made, it will create a UEFI boot to the operating system "Windows Boot Manager" entry in our case.
  • After the next reboot, if you check your boot order, you should see this UEFI OS boot manager entry.

• Cisco UCS C220 M3 SFF and R2 Datacenter Windows Server 2012

  Hi Experts,

  I intend to install Windows Server 2012 R2 Datacenter as an operating system for Cisco UCS C220 M3 Small Form Factor. This deployment is - supported?

  Thank you.

  Sy

  Yes, according to http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html

  Manufacturer = Cisco

  Driver = 2.2.0.17/2.2.0.13(NIC)
  Adapter Firmware = 2.1(1a)
  Startup code / BIOS = 2.1(1a)

  C220-M3(SFF/LFF) server requires version 1.4.7a [use HUU 1.4.7a.1].

• FreeBSD on Cisco UCS C220 or C240

  My question is that if it is possible to install version 10 of OS FreeBSD on a Cisco UCS C200 or C240 server, they are compatible or not?

  Hello

  It might be possible, but does not supported, so I will confine myself to saying:

  He is not here: http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html or here http://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/interoperability/matrix/r_hcl_C_rel1-56.pdf

  I may have forgotten, then you want to check the .pdf link again

  -Note THE answers useful.

  Kenny

• vFoglight with Cisco UCS

  Hello all,.
  We are looking for Cisco UCS for our ESX env. and I was wondering if someone was running vFoglight UCS and had problems.
  Or if someone of Quest/Vizioncore knows of any problem or future integration planned with UCS.

  Thank you
  Craig Dieck

  Craig, I know of many clients running the Cisco USC with VMware and they are very happy. There is no known issue with vFoglight perspective. VFoglight hardware monitoring currently able to extract any platform SNMP information. If you are looking for a vFoglgith to pull information from the physical ESX servers directly (not SNMP) you will need to ask for a discussion of the roadmap with your representative local of the quest.

  Inform the product manager for the platform you are using and what you want to be monitored and displayed...

• UCS chassis Fans

  All my fans in my UCS chassis are reported as unusable?

  Fans shout in the data center. Very strong. Room temperature is fine.

  A lot of mistakes like that?

  <>

  ACK = 'yes '.

  cause = "equipment unusable.

  changeSet =""

  Code = "F0373".

  created = "" 2014-03 - 06 T 21: 46:44 ""

  Descr = "' 1 Fan in the ventilation Module 1-1 under the terms of the operability of chassis 1: unusable" "

  DN="sys/chassis-1/fan-module-1-1/fan-1/fault-F0373".

  highestSeverity = "major."

  ID = "520430".

  lastTransition = "" 2014-03 - 06 T 21: 46:44 ""

  LC =""

  happen = '1 '.

  origSeverity = "major."

  prevSeverity = "major."

  rule = "equipment-fan-unusable.

  severity = "major."

  status = 'created '.

  Tags = "network, server.

  Type = "equipment" >

  Steven,

  See this:

  There is especially an communication error (not a hardware failure, at least at first glance) with IOM attached to FI - B. Look at the difference between the two from the IOM, IOM to FI - A is affected but not that much (I did a little more understandable):

  DC-UCS-FI -has# connect IOM 1

  FEX-1 # see the platform flexible cmc showi2c

  chassis of segment 1

  norxack 5514< means="" a="" problem="" if="" you="" have="" this="">

  unfinished 1

  lostarbitration 1

  correction 2

  Blade segment 2

  fan of segment 3

  segment 4 psu

  pca9541postio2 12

  Gilroy.Error.pca9541_control_state 77

  Gilroy.Error.do_reserve_pca9541_control 77

  bus_lost_counter: 991

  error_pca9541_per_device:

  c.Mme 77< this="" is="" a="" problem="" with="" the="" chassis="" management="" selector="" which="" is="" located="" on="" both="" ioms="" for="">

  c.GPIO0 1

  # I2C device statistics

  c.SEEPROM = {Success = 262839}

  f.FM0.fru = {SUCCESS = 1} < all="" fans="" are=""> speaks with the IOM that is supposed to manage their behavior

  f.FM1.fru = {SUCCESS = 1}

  f.FM2.fru = {SUCCESS = 1}

  f.FM3.fru = {SUCCESS = 1}

  f.FM4.fru = {SUCCESS = 1}

  f.FM5.fru = {SUCCESS = 1}

  f.FM6.fru = {SUCCESS = 1}

  f.FM7.fru = {SUCCESS = 1}

  --------------------------------------------------------------------------------------------------

  DC-UCS-FI -B# connect IOM 1

  FEX-1 # see the platform flexible cmc showi2c

  chassis of segment 1

  2795 norxack

  wait_gt_deadline 207743

  Blade segment 2

  fan of segment 3

  norxack 108550< is="" evident="" the="" problem="" when="" talking="" to="" the="" other="">

  timeout 27815

  14 unfinished

  Fixup 55614

  pca9541clrerrprs 7

  pca9541seterr 2

  pca9541postio3 2

  wait_gt_deadline 9319746

  hub_sw_mbb 27785

  hub_sw_mbb_to 27785

  segment 4 psu

  pca9541postio2 12

  wait_gt_deadline 6664338

  Gilroy.Error.pca9541_control_state 99

  Gilroy.Error.do_reserve_pca9541_control 99

  bus_lost_counter: 535

  error_pca9541_per_device:

  c.Mme 99< c.ms="">

  f.FM0.fc 3< and="" the="" fans="" showing="" up="">

  f.FM1.ms 1

  f.FM2.ms 1

  f.FM3.fc 2

  f.FM3.ms 1

  f.FM4.ms 1

  f.FM5.ms 1

  f.FM6.ms 1

  f.FM7.ms 1

  # I2C device statistics

  c.SEEPROM = {Success = 263768}

  f.FM0. FC = {Success = 4410402, EIO = 2,EBUSY= 3477}< this="" means="" an="" efforts="" to="" communicate="" but="" finds="" the="" channel="">

  f.FM1. FC = {Success = 4407270, = 2,EBUSY= 3478 ENXIO}

  f.FM2. FC = {Success = 4406286,EBUSY= 3478}

  f.FM3. FC = {Success = 4406492, = 2,EBUSY= 3476 ENXIO}

  f.FM4. FC = {Success = 4406621,EBUSY= 3476}

  f.FM5. FC = {Success = 4407430, EIO = 1, = 1,EBUSY= 3476 ENXIO}

  f.FM6. FC = {Success = 4407772,EBUSY= 3476}

  f.FM7. FC = {Success = 4407739, = 1,EBUSY= 3480 ENXIO}

  I would recommend to reinsert the IOM attached to the FI - B during an interview (unscrew for about 5 minutes, drain all the power), even as fans (take the fans for about 3 minutes, same reason as the IOM) and make sure that above, depending on the firmware you rotate or you run the following versions: 2.0.5b or later 2.1.1f or later version or any version 2.2.   IF you are already running one of these versions, then all just do the reinstall.

  I hope this helps.

  Note THE answers useful.

  -Kenny

• VNX 5300 file shared storage - connect to Cisco UCS 6200 interconnection fabric

  Hello

  I'm designing a calculation and Shared Storage solution to help

  • EMC VNX 5300 shared storage
    • Block
    • File - sharing two Data Mover with i/o 10GE ports
  • Cisco UCS Blade Server Platform
    • Interconnection of Cisco UCS 6248 fabric
    • Chassis Cisco UCS 5108

  I have a question about where the connection Data movers with i/o 10GE ports. I connected to the 6248 UCS Cisco fabric interconnections or connect them to the switch IP network?

  kind is ok.

• Cisco UCS components and software bug

  I was reading on the Cisco products affected by the vulnerability of software to the following Cisco Security Council

  http://Tools.Cisco.com/Security/Center/content/CiscoSecurityAdvisory/CIS...

  I couldn't find if below products/components are affected by this problem... can someone confirm if these products/components are vulnerable to the software?

  Cisco UCS Manager

  Integrated management of Cisco (CIMC) controller

  Cisco UCS blade chassis

  TIA

  I agree that sentence is a bit off, note that the view talking affected _products_ (or not), not specific _components_ of a product.

  UCS seems to be off the hook. Not affected are:

  • Cisco UCS series B (blade) servers
  • Cisco UCS C-Series (Stand alone Rack) servers
  • Cisco UCS Central
  • Cisco UCS fabric of interconnections
  • Systems Cisco UCS Invicta series Solid State

  MMIC and UCSM would be part of the FI or B-or-C-series, etc.

• Cisco UCS model to match Dell R900

  I am trying to replace existing Dell R900 (1 TB of disk space, RAM 24GO and 2 Quad core CPU) with Cisco UCS but don't know which model I should go with.  any response will be appreciated!

  It seems that the Dell R900 is a server in a rack, so if you are looking for something similar, you can try the C460-M4:

  Features at a glance

  • Four chassis rack unit (4RU)
  • 2 or 4 processor Intel® Xeon® E7-4800 v2 or product E7-8800 family processors v2
  • Up to 6 terabytes (to)^* memory (DDR3) 3 double-flow in 96 locations of memory online double (DIMM)
  • Up to 12 small Form Factor (SFF) hot-pluggable SAS/SATA/SSD drives readers
  • 10 slots PCI Express (PCIe) Gen 3 supporting the Interface Cards virtual Cisco UCS and the third-party adapters and GPU
  • Two ports Gigabit Ethernet LAN on motherboard (LOM)
  • Two 10 Gigabit Ethernet ports
  • A dedicated to out-of-band (OOB) management port

  ^* With 96 x 64 GB DIMMS when available.

  http://www.Cisco.com/c/en/us/products/servers-unified-computing/UCS-C460...

  I hope this helps.

  Let me know if you have any questions, if no, please check the question as answered.

  -Kenny

• Cisco UCS update for vmware

  Hi all

  I am facing a problem to upgrade my vmware environment. Is it possible to upgrade my current environment to vmware vSphere 5.0 to 5.5 or v6 vSphere? Here's my current Cisco UCS report. Cisco said that no Vmware said yes.  Someone at - he tried or who have this problem?

  Current version = UCSM B series

  The UCS = 2.1 release (2)

  Server model = B230-M2

  Adapter = CAN-M91kR UCS Virtual Interface Card

  If you need confirm the hardware and software compatibility, here is your best friend:

  http://www.Cisco.com/Web/TechDoc/UCS/interoperability/matrix/matrix.html

  With version UCSM you use and the material, you have the latest version supported is ESXi 5.1 U1, but if you upgrade to 2.1.3 you will see Esxi 5.1 U2 - 3, 5.5, 5.5 ESXi U1 - 2 and 6 Esxi ESXi.

  I bet you meant to type M81KR, so keep this in mind for a proper functioning:

  1.5.0.45 = card driver (FNIC), 2.1.2.38 (ENIC)
  Adapter Firmware = 2.1 (3)

  Let me know if you have more doubts, if not, please check the question as "answered" so future users to see that you found the information you are looking for.

  -Kenny

• Cisco UCS C240M4 ESXi installation

  We are trying to install ESXi on Cisco UCS C240M4 server and during loading of the VMware purple screen with the following error

  NOT_IMPLEMENTED bora/vmkernel/hardware/apic.c:1897.

  I have seen this problem when the image is not a custom image from Cisco... try the custom image and let us know...

  Is it me or you have problems with installation of an OS (ESXi 4.1) who no longer supported by the vendor (VMware): http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd...

  -Kenny

• Configuring the Cisco UCS 5108 ports

  Hi all

  I'm new in the world of the Cisco UCS server and am setting up Cisco UCS 5108 blade server. The server has two Cisco UCS 6324 interconnections fabric I did the initial Setup on and I try to configure the ports for the blades. Looking through the various articles and tutorials after setting global policies, I see the whole world establishment of uplink and server ports. What I read the uplink ports are plugged directly into the switches (I work with two cisco nexus switches), and server ports are used to connect to the chassis.

  I wonder once the configured ports server what exactly are supposed to connect to? I assumed they would also connect to the switch nexus with the uplink ports. However, every time I set up the server ports and plug them in, the switch doesn't seem to have flooded and we lose all connectivity. If I unplug, the connection is restored almost immediately.

  The current configuration, that I work with is two ports uplink on each fabric interconnect (4 2 total in each switch of nexus), two server ports on each (4 2 total, in every nexus switch). The only other element connected to the nexus switches is a SAINT who will be configured as a boot and storage of the UCS 5108.

  Looks like you have a Mini UCS (6324), with 4-port 10 GB (each FI/IOM) with port QSFP 40 GB that can provide network connectivity linking rising, or if configured as a server port, could be used to connect to a server in a rack compatible Cisco UCS, or connect to a 5108 additional with IOM 2204XP chassis.  The blades installed in your initial 5108 chassis 6324 FI/IOM of housing have internal connectivity to the FIs / IOM without the need to configure ports 'server'...

  Please take a look at some of the visuals in the datasheet below.

  http://www.Cisco.com/c/en/us/products/collateral/servers-unified-computing/UCS-6300-series-fabric-interconnects/datasheet-C78-732207.html

  Unified ports can also be configured as a FC ports for connectivity of FC switch upstream or directly related to CF Storage processors.

  After having watched the datasheet, let me know if you have any other questions, and I'll try to address them.

  You'll not need actually configure ports such as ports 'server' unless you connect servers in a rack.

  Please configure any ethernet SFP type connected to your switches nexus upstream as 'network' uplinks.  I guess that you don't plan on a disjoint config layer 2 (where each FI has several sets of uplinks will different devices upstream, or the same device with different VLANS allowed on each link).    If you are, we can have a separate thread about how you need to configure that.

  Thank you

  Kirk...

• Cisco UCS C240M4 Esxi installation version 5.0 cisco custom image do not start

  Hi all

  We are trying to install ESXi 5.0 on Cisco UCS C240M4 server and during loading of the VMware purple screen with the following error

  Bora/vmkernel/hardware/apic.c:1913 and bora/vmkernel/hardware/apic.c:1915 NOT_IMPLEMENTED NOT_IMPLEMENTED.

  Greetings.

  ESXi 5.1 U2 is the first supported by Cisco for the C240M4. See matrix interop

  I suspect that older versions 5.0 and earlier versions will have problems with the latest chipsets, as well as the lack of 12 GB storage controller drivers.

  You will want to check the interop matrix for which OS versions are supported as well as different levels of driver for the network cards, storage, etc.

  Thank you

  Kirk...