UCS 2.2(1b) - addition of M4 B200 blades

Similar Questions

• Can I disable the B200 blade Fibre Channel vHBA

  Hello

  I'm setting up my service to my B200 blades profiles and I was wondering if there was a way to disable the Fibre Channel HBA. I will not use CF as all my iSCSI storage.

  Thank you

  LTA

  When you create a service profile, you are asked if you want the storage (= CF) or not; you say no!

  If you missed this step and you have created vhba, just remove them later.

  It is not possible to disable vhna.

• UCS Plugin - How will I know if a blade is associated with related?

  I use the Plugin UCS to associate a Service profile with a blade. When I do, the function call returns immediately. But I want to wait that the blade be associated before proceeding. How to figure out when the blade is made combining? The UcsmBlade.status parameter is not good, it returns without return Null.

  A detailed example of a use case is described on the blog of vCO:

  http://blogs.VMware.com/Orchestrator/2011/04/sample-scenario-for-the-Cisco-UCS-Manager-plug-in.html

  Step 3, 4 and 5 of this use case are:

  3 assign the Service profile to a blade

  4. wait for the association must be true (the blade is going to be started)

  5 do something else after that depending on the result (for example, send a notification to someone)

  This should provide you with the information required to complete your use case.

  Thank you

  Igor.

• Cisco UCS B200 blade with installed vCenter

  Don't put the vCenter on one chassis 5108 blades and can control the ESXi hosts on the other blades? If this is the case, on the design, it's possible? Install the vCenter on a single blade with ESXi or ESXi?

  I ask this question because I have experience only having the vCenter as a separate machine whicn connects only to the network to control the ESXi hosts on 5108 chassis

  Thank you!

  as mentioned above, it is possible

  also the best design of practice in a certain measure, it is preferable to have VCenter in a virtual machine to take the advantage of using Vmotion HA for example features to reduce the risk of losing your vCenter because of HW faular for example

  You may have a blade for VCenter use in hunting and other blad for Vcenter backup for example hunting another!

  Good luck

  If useful rates

• Memory of UCS permutation

  I currently have 2 x blades series B200 M2 with 12 x 4GB 1066 MHz DIMM memory added to it. I just ordered a blade series B230 M2 and more memory for the B200 blades. I ordered memory 16GB sticks for the B200, which will fill the DIMM slots, and some of the 8 GB at 1333 MHz sticks for the 230's. I can add the left over 4 GB 1066 MHz sticks to the B230 without any problem?

  I am also aware that adding memory to speed the blade probably would decrease the speed of the 8 GB at 1333 MHz to 1066. But I don't want the size memory.

  Hello

  For B230, we must install bars in pairs and they must be the same within a pair. So unless that, if these modules are not classified as a pair, it is not recommended to be installed on B230.

  The following documentation provides more detailed information on the guidelines memory of population.

  Memory installation guide

  http://www.Cisco.com/en/us/docs/unified_computing/UCS/HW/chassis/install/B230.html#wp1003860

  Data sheet B230

  See the section:-notes memory, the authorized configurations, and rules and guidelines

  http://www.Cisco.com/en/us/prod/collateral/ps10265/ps10280/spec_sheet_c17-665957.PDF

  If you have already ordered their pair, yes we have memory modules (kit memory of 8 GB / 4 GB) as suggested in the document.

  Also if the B230 installed with Intel's EX family processors, they operate only at 1066 MHz, even though the memory module are able to operate at 1333 MHz.

  HTH

  Padma

• Cisco UCS Direct Attached ISCSI Storage access upstream to storage array

  I'm doing my first installation of UCS with a chassis 5108) and (4) B200 M3 blade and (2) 6248 fabric interconnects. The plan is to connect our EMC VNX directly on the fabric of interconnections as the chassis will be the only system for access to the SAN, after migration from our current system. The fabric interconnects will be transmitted to (2) 4500-X switches configured in a vs.

  In my research of best practices and general deployment guidelines I noticed the need to create (2) separate iscsi VLANS for fabric and a fabric in B. I'm guessing that this requirement is the lack of STP as YEW is configured in EHM, but I was not able to find an exact answer. Any idea would be appreciated.

  My main question and my concern is that if I create a second VLAN ISCSI on our X 4500 and then create both of these VIRTUAL on FI networks A & B I'll be able to connect the SAN to the UCS as well as our former VMware cluster (we are migrating our system HP Compute and storage UCS 5.5 environment) in order to facilitate the vMotions of storage?

  I noticed the need for iscsi separated (2) VLAN a fabric and a fabric B

  Are you referring to

  https://www.EMC.com/collateral/hardware/technical-documentation/h8229-VN...

  p 36

  If I understand your question: can a host attached to 4500 (connected to the UCS FI), access LUNS on the VNX, which is directly connected to the UCS fabric interconnect through lanes (EHM FI) material? YES! I would accept this for a migration, but not forever, because it means that traffic on the fabric of interconnection.

• Mini of the UCS + 4 switches, no VLAN

  Hi all

  I have a mini UCS with 6324 modules e/s with B200 m3 x 5 blades, each ESXi 6.0 running.

  I want to uplink the UCS mini with four cables to four switches separated for traffic, and I wish that each host ESXi b200 see four separate vmincs, one on each network. The switches have no VLAN, but running DHCP. I want to get DHCP from each card.

  How can I go on the correspondences between the vNIC?  Groups of LAN Pin?

  Hi Alex,

  That is right. You can also implement Layer 2 disjoint explained in the guide below for more secure access.

  http://www.Cisco.com/c/en/us/solutions/collateral/data-center-virtualiza...

  I hope this helps.

  Qiese Sa'di

• Win2k3R2 with SP2 cannot recognize local HDD in B200 :(

  Hello

  I tried to install en_win_srv_2003_r2_datacenter_x64_with_sp2, but he could recognize no hard drive built-in B200 blade. Is this a feature or I do something wrong? Or to rephrase my question, is there a special driver for it and where it can be downloaded from?

  Best regards

  Taenarum

  Taenarum,

  You need ISO cisco.com driver and then load the LSI controller.

  Follow the instructions in this guide, and you should have no problem:

  http://www.Cisco.com/en/us/docs/unified_computing/UCS/SW/b/OS/Windows/install/2003-VMedia-install.html

  Kind regards

  Robert

• The question about the interconnections of fabric UCS 6300 Series

  Hello

  I have a question about UCS 6300 Series fabric interconnects. Is this fabric UCS interconnections 6300 series integrated into the extension of tissue function?  The reason why I asked this question was, when there is 6300 series fabric has been plugged UCS 5100 chassis, there is no more space to plug in extension of UCS 2200 series fabric. My understanding on the topology of the UCS, tissue extender is the connection between the blade and the fabric of the interconnections.

  Thank you

  Bob

  Hi Bob

  Yes, that's correct!

  The chassis so called FI - IOM (see attachment p52); THE IOM = FEX.

  I/O of the blade adapter to connect inside basket chassis, which connects to the built-in IOM.

  IOM is then connected to the built-in FI.

• question from newb on 6100 fabrics

  Hey,.

  What is the difference between the 6100's and nexus switches?

  I look at vids on UCS and it seems that the networking and the fabric are on the 6100 6100 modules are s of the nexus switch? They are completely serperate devices this site to the South the Nxs switches?

  Can someone give a brief explanation?

  Brent, the interconnections of fabric UCS (FI) are the point of grouping all the chassis connection blade & rack UCS servers.  In addition, the FI to run the software of management of the UCS.  FIS are a separate device.  They have just the same physical appearance as the nexus 5K, but they are distinct & unique devices.

  UCS can uplink in your Distribution, or even of the basic network switches.  It could very well be a pair of Nexus, Nexus 7 K, Cat6K 5Ks or any which non-Cisco switch.

  Here's how common a UCS deployment would look like & sit in a network running continuous.

  

  Here is an another digram showing the UCS uplink for both SAN and LAN Ethernet fabrics.

  

  HTH,

  Robert

• Fabric 6248 with MDS

  Hi all

  We are at the stage of inter-connecting simple IBM V3700 SAN box with double FI 6248 (redundant) via unique Cisco MDS 9000 SAN Switch with single UCS 5108 chasis.

  We have four blades B200 M3 in UCS 5108. The blades have no local hard disks. Our requirement is to install hyperV/Windows on IBM storage.

  I did the physical connections between IBM and MDS & MDS FI 6248 and FI 6248 dual Core 6509 VSS enabled.

  I don't have issues with part FI 6248 and LAN, I have doubts about FI 6248 with SAN kindly advise.

  6248 FI are default mode (Host End). I need to change FI on switch mode?
  I change ports Uplink FC, unified FI ports connected to the MDS are configured as storage CF?
  How vNIC, vSAN (vSAN how do I need), vHBA & Service profile works to each other? can any advise please?
  What steps do we need to set up in FI & MDS so that we can use SAN storage for hyperV/Windows installation?

  It's my first deployment of the UCS 5108, to apologize to ask fundamental questions.

  Kind regards

  1. what would be the impact of multiple VSANS vs default vSAN, I plan to use default vSan in the two FI-6248 & I can't find any problem with this, please advise.

  Please do not use default vsan (vsan nr or 1); best practices: create different VSAN fabric A and B; e.g. vsan 10A, vsan 20 b

  2 - pool WWPN, should I create two different WWPN pool 1 for FI-6248-A & others for FI-6248-B? I have only a UCS 5108 chasis, we cannot set an unique WWPN for the two FI-6248 Pool? What is the best practice? I can't find any problem with single WWPN pool. Please advise.

  Best practices: use pools of different pwwn to fabric A and B; useful for troubleshooting; in General: all pools must also encode a field id UCS (your starting with 1). just in case in the future, you have another! See attachment.

  3 - incase, if I will configure 1 WWPN pool would I face any problem in mapping the area in MDS? According to my understanding there will be no problem because the area is just the initiator (Server Blade) mapping & target (IBM Storage). Keep in mind, I only Cisco MDS SAN Switch NOT redundant. Please advise.

  Even with an SDM, you create a virtual double fabric with 10 and 20 VSANs. zoning is done by VSANs, zones and activation as well!

  what adapter policy 4 - Creating Service profile should I choose in the menu Dynamics vNIC? I want to install Windows on Hyper V environment, but I'm not hyper V option. It has linux, VMWare, VMWare passthrough, window, default & some HyperV more but not?

  You do not create dynamic vNIC! This only applies to the VM - FEX, resp. SR - IOV. Hyper-V means political adapter = window

  Good luck

  Walter.

• Blades with mixture of ViC/NAC

  Hi all

  Is there a problem if a UCS 5108 chassis B200 blades with a mix of card NAC & ViC? say a few blades have M73KR & others ViC1240.

  would this work?

  Thank you

  Kass

  Yes it is supported, you can check this by using the following compatibility matrix http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html let me know if that answers your question

• UCSM Server

  My UCSM server is to have a critical error with the reason WILL_BOOT_FAULT:Sensor failure said.

  Anyone has an idea about this error? Any help would be grateful.

  Hi Mark,

  By UCSM server maybe you talking to a B200 - blade M3? Also what version of UCS - M you are currently running and the Version of the BIOS. This information will help us to refine your question.

  However, based on the error code that looks like you are running in a question about the discovery on the blade. I pasted a link with the pasted clip out on the issue, you CAN be hit. However, without more information we will not be able to help you fully.

  http://www.Cisco.com/c/en/us/TD/docs/unified_computing/UCS/HW/CPU/IVB/install/IVB-B.html#wp45312

  Upgrade scenario 2: UCSM and BIOS to Version 2.1(3a) or later CPU earlier than Intel E5-2600 v2

  This scenario assumes that the following conditions:

  Cisco UCS Manager software is version 2.1(3a) or later.
  The server already uses the BIOS/MMIC version 2.1(3a) or later.
  The server uses version Intel E5-2600 v2 series CPU processors.

  In this case, the server already has the prerequisite software and firmware. Use the following procedure to upgrade the processors:

  Step 1 disassociate server in Cisco's UCS Manager.

  Step 2 turn off the server.

  Step 3 replace the processors with Intel-E5-2600 v2 series processors.

  Use the procedures in the Installation of the server blade and Note of Service for your server.

  Step 4 reinsert the server to the chassis.

  Step 5 Wait for Cisco UCS Manager to automatically discover the server.

  Note at this point, the LED of the health of the server displays a critical flaw and Cisco UCS Manager reports a generic error message: WILL_BOOT_FAULT: sensor failure said. This is because an activation of the controller of the Board of Directors is required, as described in the next step.

  Step 6 perform activation of card controller using the CLI Cisco UCS Manager interface. Use the following sequence of commands:

  Note the server restarts automatically after running the commit buffer command.

  Notice that the picture show in the sequence below command lists the versions of controller available for the server Board. Always activate the latest version of controller board image when you use the
  activate the firmware.

  # server scope
  # scope boardcontroller
  Show picture #.
  # activate the firmware .0 force
  buffer validation #.

  See also example Board controller Activation Command Sequence.

  Step 7 do not continue with the next step until the end of the activation of the Board controller. Check if the activation is finished using the show version command.

  As shown in the example below, wait until the activation status returned Ready. This process takes a few minutes before you activate registered completes successfully and returns Ready.
  # See the version
  BoardController:
  Race-worms: 8.0
  Package-about:
  Activate status: ready

  Step 8 remove the WILL_BOOT_FAULT by using the Cisco UCS Manager GUI to reset the MMIC server:

  1. In the Navigation pane, click the Hardware tab.

  2. On the Hardware tab, expand facilities > chassis > chassis number > servers, and then select your server.

  3. In the work pane, click the general tab.

  4. In the Actions box, click on recover the server.

  5. In the recovery server dialog box, click Reset MMIC (controller server), and then click OK.

  Wait the MMIC to restart and for Cisco UCS Manager to make a shallow discovery of the server. It takes two to three minutes. At the end of this process, the WILL_BOOT_FAULT is cleared.

• Number of Clusters

  We are mounted to finally put VC2.5 in vSphere and I have a question about clusters in vSpere 4 update1. At this moment we have tough 6 hosts (nodes) running s 70vm each. As we look at adding additional nodes xseries or blades, should we be creating additional clusters or just keep everything in 1 cluster. Are there disadvantages of pro with who (stipulated the rate cap for vSphere cluster 8, 9 or more nodes etc.). I mean I guess my question is why create a 2nd cluster just because I add more hosts? A colleague suggests an additional cluster will alleviate cpu contention, but by adding more nodes to an existing cluster should do the same thing in my mind. Thank you for advice or links to best practices.

  vmdawg

  The most important thing that could lead you to a new grouping would be CPU compatibility - you have CVS available, but if it is not currently enabled will require your virtual machines stop and restart them once active CVS.

  IMHO, I prefer smaller larger clusters that's easier to manage them and their virtual machines

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• NO DRIVERS FOR UCS BLADE B200 M4 (missing ethernet controller) with W2012R2.

  We have installed windows 2012 R2 x 64 picture in a B200 M4 (2.2.7b) blade. We have installed all the drivers of Cisco web page, but that one THAT CISCO VIC ETHERNET INTERFACE (20gbps) pilot was found. The other Ethernet controller was not found in the .iso image file (UCS-bxxx-pilots - windows.2.2.7.iso).

  Can someone help us with these drivers?

  The id of the part is UCSB-MLOM - 40G - 03

  capture.jpg

  

  Thank you

  All ethernet interfaces, which represent the vNIC you created in your service profile, will use a single driver.  Make sure that you have installed the chipset drivers intel \ucs-bxxx-drivers-windows.2.2.7.iso\ChipSet\Intel\B200M4\W2K12R2\ and then confirm you need to install the driver of vic.  When the driver chipset and vic are installed, your ethernet interfaces must map all just as network several adapters of VIC.

  Additionally, make sure that you have not created vNIC dynamic (which may appear as follows in the Device Manager) in your service profile, unless you create for your VM - Fex NIC hyperV environment.  For VM-Fex/dynamic vNIC, there is a specific process to create these, so the Windows hyperV host does not see in Device Manager and is only visible in hyperV guestVMs.

  Thank you

  Kirk...