B420M3 w / 1240 + PE + 1280 + IOM ESXi 2208 + 5.5

Similar Questions

• How many vNIC on B200 M3 with VIC 1240 + extender?

  Hello

  Asking to confirm my resoning/interpretation of B200 M3 with VIC 1240 + extensible architecture.

  I'll apply vSphere 5.1 works UCS B200 M3 equipped with blades with VIC 1240 + expanders mezzanine.

  If I understand the documentation, all the physical links through the fabric between the host and the IOM are automatically approved by UCS, so if I don't create only one UCS vNIC by fabric, ESXi must 'see' vmnic with 40 Gbps capacity (with limitation of 10 Gbps for the single 'flow').

  Say this another way - there is no need to create 8 vNIC to use all 8 physical links?

  Nice day!

  With the VIC 1240 and Extender port and 2208 hypervisor ESX will be able to see an aggregation of links total of 40G network card.

• 10G between adpater and blades for VIC1240 + 1280

  As my other discussion suggested, I VIC 1240 and 1280 cards installed on the B200 M3 blade.

  UCS automatically creates 4x20G port-channel between the adapter and the blades. We have therefore 80 G total n/b to the INSTITUTION of the blade. Side has 40 G and 40 B side

  I have a delicate question: if I could change the 4 ports-channels to 8 individual links while I have granular control to 10G does level not 20G

  Can anyone help to answer the question?

  No, these are internal pc, automatically. Be aware that a single stream is limited to 10G, more if you have not configured a pc between the IOM and fi, you are limited by this public static pinning (IOM - FI) to 10G anyway. PC between IOM and fi requires the second generation material, for example. 62xx and 22xx.

• UCS ISCSI Boot Jumb MTU

  Light and matter seeks jumbp MTU working for ISCSI boot.

  UCS 6248S

  IOM 2208

  VIC YEARS 1240

  5.1 ESXi update 1

  VNX 5500

  I have a few rack mount hosts with 10G network cards, who works with jumbo MTU and I can vmkping the VNX SPs with ' vmkping d s 7000 10.1.1.1 "and it works.

  In UCS the operating system starts on the VNX via ISCSI

  The ISCSI network is a pair of Dell Force 10 S4810s

  UCS FI - A and FI - B have 2 10 uplinks in a s port LACP on the strength of Dell 10 channel

  Checked the jumbo MTU is enabled on the side of Dell

  The system class QoS now occupies the 9216

  There is a QoS ESX ISCSI strategy mapped to the class gold

  ESX ISCSI strategy is mapped to 2 vNIC models; one fabric and a fabric b

  If I set the MTU on the vNIC model 9000 errors the OS at startup a message on start-up banks missing

  If I set the MTU on the vNIC model 1500 the host boots fine

  I put groups of ISCSI ports and vSwitch to 9000 in ESX, but I cannot ping the VNX SPs with a package of more than 1500.

  Attached is a diagram

  Someone at - he of the clues as to what I'm missing? Thank you

  Make sure that you assign you best effort to 9216 so class on the system UCS class.

  The return traffic is probably not sent with a COS value so the UCS is the treatment to best effort which by default is 1500.

  Joey

• FEX-Uplink Failover, loadbalancing

  I would like to understand more of the technology within a vblock
  I have a few questions gradually

  So I'm out. pls be patient and thank you in advance...

  VBlock 720 with the following generic configuration

  Switch 2 x Cisco 5000 Series
  2 x FI 6248
  6 x chassis 5108
  FEX 2204
  VIC 1240 (no Mezzanine Card)
  8 x M3 blade, 2 CPU

  uplinks of 4 x 10 G of each FEX to FI (port channel)
  uplink of 8 x 10 G of each FI for Ciso 5000 series swith (vpc)

  Assumptions:

  All chassis are completely fill

  Each blade has consistient thoroughput of bandwidth, but 6 GB

  1. When the blades connect to FEX A and B FEX, are active active connections?
  2. For exampleIs blades 1 and 5 has made the fallen on the same ports on the same FEX FEX?
  3. What is the method that load balances blade ping?
  4. Assume 1 Uplink fails between FEX and FI, is the uplink 1 on FEX B overexploited.
  5. How the virtual machine decides which ANC port to send traffic?

  She now...

  See online

  When the blades connect to FEX A and B FEX, are active active connections?

  I assume you mean of FEX = IOM in the chassis;

  Yes the two fabrics are active; all VIC are double hosted the fabric a and b

  For exampleIs blades 1 and 5 has made the fallen on the same ports on the same FEX FEX?

  You have the choice between static pinning (made by UCS Manager) blade slot to an Uplink of IOM, or set a port between IOM and fabric channel interconnection; port channel is the preferred mode.

  Static pinning depends on model of IOM, 2204 / 2208 and the number of uplinks, for example

  2204-4 uplinks

  slot 1 and 5--> uplink 1 chassis

  2 and 6-> uplink 2 chassis slot

  ......

  2208-8 uplinks

  Chassis slot 1-> uplink 1

  Chassis slot 2-> uplink 2

  ......

  Pinning static if a rising fails, the fabric slots correspondent has or b, are declining. There is no repinning for remaining uplinks; grouping and multipathing will take the appropriate action.

  If you have a port-channel, and you lose a link, no problem, as long as there is at least a link to the top; your bandwidth will decrease, but th vnic/vhba are still in place

  What is the method that load balances blade ping?

  Don't understand; To be more specific

  Assume 1 Uplink fails between FEX and FI, is the uplink 1 on FEX B overexploited.

  Yes, in principle. but you will have to design oversubscription from end to end in any case!

  How the virtual machine decides which ANC port to send traffic?

  It depends on the hypervisor; Take, for example, VMware ESXi and vswitch: load balancing can be configured by switch and / or port-group; important caveat: do not hash IP as interconnection of fabric does not support the Protocol LACP; by default, the original virtual¨port code.

• VIC1240 and 2208xp

  Hi team,

  Configure the UCS quickly to provide 80G blades B200 M3 link to FI.

  I have two adpaters: 1 VIC 1240 (VIC1240 is in the mLOM slot), 1 module VIC 1280 and IOM is 2208xp.

  After tchecked the doc, I found the solution in attached. But couldn't find the doc who shows how to configure in UCS?

  It is very appreciated if someone can suggest the steps in detail of the configuration.

  THX

  Hi David,

  With 1240 and 1280 on the blade adapters you will automatically have 80 G total n/b at the END of the blade. Side has 40 G and 40 B side

  There is a channel of automatic port created between the adapter and the blade, and you don't have to configure anything else.

  All you have to do is to create the vnic and vhba as usual in the profile of serivce.

  . / Afonso

• 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

• Vs of 1280 VIC VIC 1240 + Port Expander

  Hello

  What is the advantage of using VIC 1240 + Port Expander versus having a 1280 VIC? I don't see any.

  Someone has some entries?

  (a) # you can definitely add the mLOM later, but understand that the 'slot' mLOM is for the mLOM only.  The Mezz slot is for the 3rd GEN 1280 adapter or other.

  (b) Yes.  Now you have ther power!  Keep in mind the 160Gbp is burst capacity max.  You would be hard to find an application or at the end of the devices to maintain this flow

  Kind regards

  Robert

• ESXi vmnic connected to 20000 MB when waiting for 40000 MB

  Hi all
  I have 4 x B200M3 5u2 ESXi running blades in a single chassis UCS. They run a number of vSwitches, and all the connected vmnic show 40000 full duplex Mb (as expected).
  Yesterday, I added 2 B200M3 more (to slot 7 and 8), and I get only 20000 Mb on all the vmnic. The hosts are the same set up as the old via vCenter (although not not using the host profiles), and Service UCS profiles on new knives are clones of an existing blade.

  See attached screenshots...

  Does anyone have an idea of what this might be? Any help would be great.

  See you soon

  Yet one thing, you might hit the default below if you have the same hardware on all blades, including the two new b200 M3.

  You can also see the difference in the bandwidth if the new cards are one of the missing cards, it could be the port Expander or the 1280 or 1240 vic, is an expected behavior.

• FI/IOM: better design of wiring

  In our UCS system with 2 chassis, we have 2 links between the IOM 2208 and FI 6248:

  For an IOM, what is the best design wiring:

  -connect theIOM to Eth1/1-2

  -connect the IOM to Eth1/1; Eth1/8

  ... On average, it is preferable to use the same Unified Port Controller (UPC) ASIC [called Carmel, I think only] or use 2 different UPC?

  and why?

  THX.

  Nicolas.

  The 6200 and 2208 the best design option is actually to ensure all the server bindings (FI <->IOM) are related to the SAME UPC (carmel ASIC).  This will give you the number alive at the system max.  By spreading your connections through different UPCs may increase redundancy, but it will decrease your bright max County at the same time.

  If you want to see UPC mapping, you can connect to the CLI, connect to the NXOS context and run the following command:

  FI-A-6248-A (nxos) # display all-hardware ports internal carmel

  News Port of Carmel:

  name | Journal | Auto | Mac | flag | SMA | Opr | m:s:l | IPT | Fab | xcar | xpt | if_index | diag | ucVer

  -------+---+---+---+----+---+---+-----+---+---+----+---+--------+----+-----

  xgb1/1 | 0 | 0 | 0 | B7 | tell | DN | 0:0:f | 0 | 92. 0 | 0 | 1A 000000 | pass | 0.00

  xgb1/2 | 1. 0 | 1 | B7 | tell | DN | 1:1:f | 1. 88. 0 | 0 | 1A 001000 | pass | 0.00

  xgb1/3 | 2. 0 | 2 | B7 | tell | DN | 2:2:f | 2. 93. 0 | 0 | 1A 002000 | pass | 0.00

  xgb1/4 | 3. 0 | 3 | B7 | tell | DN | 3:3:f | 3. 89. 0 | 0 | 1A 003000 | pass | 0.00

  xgb1/5 | 4. 0 | 4 | B7 | tell | DN | 4:4:f | 4. 90. 0 | 0 | 1A 004000 | pass | 0.00

  xgb1/6 | 5. 0 | 5 | B7 | tell | DN | 5:5:f | 5. 94. 0 | 0 | 1A 005000 | pass | 0.00

  xgb1/7 | 6. 0 | 6 | B7 | tell | DN | 6:6:f | 6. 95. 0 | 0 | 1A 006000 | pass | 0.00

  xgb1/8 | 7. 0 | 7 | B7 | tell | DN | 7:7:f | 7. 91. 0 | 0 | 1A 007000 | pass | 0.00

  xgb1/9 | 8. 1. 0 | B7 | tell | DN | 0:0:f | 0 | 80. 0 | 0 | 1A 008000 | pass | 0.00

  xgb1/10 | 9. 1. 1 | B7 | tell | DN | 1:1:f | 1. 87. 0 | 0 | 1A 009000 | pass | 0.00

  xgb1/11 | 10. 1. 2 p | B7 | en | up | 2:2:f | 2. 81. 0 | 0 | 1a00a000 | pass | 0.00

  xgb1/12 | 11. 1. 3 P | B7 | en | up | 3:3:f | 3. 86. 0 | 0 | 1a00b000 | pass | 0.00

  xgb1/13 | 12. 1. 4 P | B7 | en | up | 4:4:f | 4. 82. 0 | 0 | 1a00c000 | pass | 0.00

  xgb1/14 | 13. 1. 5 p | B7 | en | up | 5:5:f | 5. 85. 0 | 0 | 1a00d000 | pass | 0.00

  xgb1/15 | 14. 1. 6 P | B7 | en | up | 6:6:f | 6. 83. 0 | 0 | 1a00e000 | pass | 0.00

  xgb1/16 | 15. 1. 7 p | B7 | en | up | 7:7:f | 7. 84. 0 | 0 | 1a00f000 | pass | 0.00

  xgb1/17 | 16. 2. 0 p | B7 | en | up | 0:0:f | 0 | 75. 0 | 0 | 1A 010000 | pass | 0.00

  xgb1/18 | 17. 2. 1 | B7 | tell | DN | 1:1:f | 1. 76. 0 | 0 | 1A 011000 | pass | 0.00

  xgb1/19 | 18. 2. 2 | B7 | tell | DN | 2:2:f | 2. 74. 0 | 0 | 1A 012000 | pass | 0.00

  xgb1/20 | 19. 2. 3 | B7 | tell | DN | 3:3:f | 3. 77. 0 | 0 | 1A 013000 | pass | 0.00

  xgb1/21 | 20. 2. 4 | B7 | tell | DN | 4:4:f | 4. 78. 0 | 0 | 1A 014000 | pass | 0.00

  xgb1/22 | 21. 2. 5 | B7 | tell | DN | 5:5:f | 5. 73. 0 | 0 | 1A 015000 | pass | 0.00

  xgb1/23 | 22. 2. 6 | B7 | tell | DN | 6:6:f | 6. 72. 0 | 0 | 1A 016000 | pass | 0.00

  xgb1/24 | 23. 2. 7 | B7 | tell | DN | 7:7:f | 7. 79. 0 | 0 | 1A 017000 | pass | 0.00

  xgb1/25 | 24. 3. 0 | B7 | tell | DN | 0:0:f | 0 | 71. 0 | 0 | 1A 018000 | pass | 0.00

  xgb1/26 | 25. 3. 1 | B7 | tell | DN | 1:1:f | 1. 64. 0 | 0 | 1A 019000 | pass | 0.00

  xgb1/27 | 26. 3. 2 | B7 | tell | DN | 2:2:f | 2. 65. 0 | 0 | 1a01a000 | pass | 0.00

  xgb1/28 | 27. 3. 3 | B7 | tell | DN | 3:3:f | 3. 70. 0 | 0 | 1a01b000 | pass | 0.00

  29/MFC1 | 28. 3. 4 | B7 | tell | DN | 4:4:0 | 4. 66. 0 | 0 | 0101 c 000 | pass | 0.00

  MFC1/30 | 29. 3. 5 | B7 | tell | DN | 5:5:1. 5. 69. 0 | 0 | 0101 d 000 | pass | 0.00

  MFC1/31 | 30. 3. 6 | B7 | tell | DN | 6:6:2 | 6. 67. 0 | 0 | 0101e000 | pass | 0.00

  MFC1/32 | 31. 3. 7 | B7 | tell | DN | 7:7:3. 7. 68. 0 | 0 | 0101f000 | pass | 0.00

  sup0 | 32. 4. 4 | B7 | en | DN | 4:4:0 | 4. 62. 0 | 0 | 15020000 | pass | 0.00

  sup1 | 33. 4. 5 | B7 | en | DN | 5:5:1. 5. 59. 0 | 0 | 15010000 | pass | 0.00

  The column with what you fear is a labeled "car" (carmel).  As you can probably see the first column corresponds to the Interface.

  FYI - I have yet to see a controller failing port ASIC.  Its MTBF is well beyond many other components including SPFS, cables, etc.  I don't sweat worrying about redundancy of ASIC level in this regard.

  Kind regards

  Robert

• ESXi VNIC speed fell after upgrade 2.2.2c

  Hello

  I hope someone can help me, I just finished the UCS upgrade to 2.2.2c and noticed that my ESXi hosts (with adapters 1240 B200M3) past the speed of 40000 to 10000.  I came across this bug https://tools.cisco.com/bugsearch/bug/CSCun21077 but my firmware and drivers are newer (2.2.2c and 2.1.2.50).  Anyone else run into this?

  Thank you

  If you hit the bug mentioned, so I guess that you have applied to the vNIC QoS policies? Change rate (KB/s) rate to 40000000 Presented to VMware speed will change immediately. Which unfortunately seems to rate some of the 2.2 release means 10GbE.

• VLAN between two hosts ESXi

  Hello

  I have two virtual machines based on VMware and some configuration of VLAN

  VM1 - VLAN 130 on ESXi01

  VM2 - VLAN 135 on ESXi02

  For example, a machine of vlan ESX1 130 cannot ping a VM one another in the vlan ESX2 130. But if I move the ESX1 second VM, it works.

  VM1 im going through vSwitch 130 VLAN via the ESXi01, what's happening than ESXi via vmnic11 port Vethernet910 on FABRIC

  FABRIC-001-B # connect nxos
  Operating system (NX - OS) Cisco Nexus software
  TAC support: http://www.cisco.com/tac
  Copyright (c) 2002-2014, Cisco Systems, Inc. All rights reserved.
  The copyright in certain works contained in this software are
  owned by others and used and distributed under
  license. Some components of this software are licensed
  the GNU Public License (GPL) version 2.0 or GNU
  Lesser General Public License (LGPL) Version 2.1. A copy of each
  This license is available at
  http://www.opensource.org/licenses/GPL-2.0.php and
  http://www.opensource.org/licenses/LGPL-2.1.php
  Fabric-001-B (nxos) # sh ver

  Operating system (NX - OS) Cisco Nexus software
  TAC support: http://www.cisco.com/tac
  Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_series_h...
  Copyright (c) 2002-2014, Cisco Systems, Inc. All rights reserved.
  The copyright in certain works contained in this document are the property of
  other third parties and are used and distributed under license.
  Portions of this software are covered by the GNU Public
  License. A copy of the license is available at
  http://www.gnu.org/licenses/gpl.html.

  Software
  BIOS: version 3.6.0
  Charger: version N/A
  Kickstart: version 5.2 (3) N2(2.21c)
  system: version 5.2 (3) N2(2.21c)
  power-seq: Module 1: version v2.0
  Module 2: version v1.0
  Module 3: version v2.0
  uC: version v1.2.0.1
  SFP UC: Module 1: v1.1.0.0
  Compile of the BIOS time: 09/05/2012
  kickstart image file is: bootflash:///installables/switch/ucs-6100-k9-kickstart.5.2.3.N2.2.21c.bin
  Kickstart compile time: 05/02/2014 11:00 [05/02/2014 19:47:41]
  filesystem image is: bootflash:///installables/switch/ucs-6100-k9-system.5.2.3.N2.2.21c.bin
  compile time: 05/02/2014 11:00 [05/02/2014 21:42:39]

  Material
  Cisco UCS 6248 series fabric of interconnection ("O2 32X10GE/Modular universal platform supervisor")
  Intel Xeon CPU with 16553964 k of memory.
  Processor Board ID

  Device name: FABRIC-001-B
  bootflash: 31266648 kB

  The availability of the core is 147 day (s), 15 hour (s), 15 minute (s), 46 second (s)

  Last reset
  Reason: unknown
  The system version: 5.2 (3) N2(2.21c)
  Service:

  plugin
  Core Plugin Ethernet, Fc Plugin, Plugin, Plugin of virtualization
  Fabric-001-B (nxos) #.

  on NXOS, I see

  See the fabric-001-B (nxos) # run interface vethernet 910

  interface Vethernet910
  Description 1/3 Server, VNIC VNIC9
  switchport mode trunk
  switchport trunk allowed vlan 1 108-109 115-119 150 - 151
  pinning Server sticking border-interface port-channel13
  pinning of pinning-down server drop down link
  queues of default entry - type service-policy policy
  bind the interface port-channel1282 910 road
  no downtime

  and information portchannel

  Fabric-001-B (nxos) # sh port-channel summary
  Flags: D - low P - Up in the port-channel (members)
  I - individual H - standby (LACP only)
  s suspended r - Module-removal
  S - Dial R - routed
  U - up (port-channel)
  M not in use. Min-links not met
  --------------------------------------------------------------------------------
  Group-Type Port Protocol Ports members
  Channel
  --------------------------------------------------------------------------------
  11 Po11 (SU) Eth LACP Eth1/15 (P) Eth1/16 (P) Eth1/31 (P) Eth1/32 (P)
  13 Po13 (SU) Eth LACP Eth1/14 (P) Eth1/30 (P)
  1280 Po1280 (SU) Eth NO Eth1/1/13 (P) 1/Eth1/14 (P) 1/Eth1/15 (P) 1/Eth1/16 (P)
  1281 Po1281 (SU) Eth NO Eth1/1/1 (P) Eth1/1/3 (P)
  1282 Po1282 (SU) Eth NO Eth1/1/9 (P) Eth1/1/11 (P)
  1283 Po1283 (SU) Eth NO Eth1/1/5 (P) Eth1/1/7 (P)
  1284 Po1284 (SU) Eth NO Eth2/1/1 (P) Eth2/1/3 (P)
  1285 Po1285 (SU) Eth NO Eth3/1/1 (P) Eth3/1/3 (P)
  1286 Po1286 (SU) Eth NO Eth3/1/5 (P) Eth3/1/7 (P)
  1287 Po1287 (SU) Eth NO Eth3: 1/9 (P) Eth3/1/11 (P)
  1288 Po1288 (SU) Eth NO Eth3/1/13 (P) Eth3/1/14 (P) Eth3/1/15 (P) Eth3/1/16 (P)
  1289 Po1289 (SU) Eth NO Eth4/1/1 (P) Eth4/1/3 (P)
  1300 Po1300 (SU) Eth NO Eth1/1/17 (P) Eth1/1/19 (P)

  I have lack of VLAN, how can I edit and update the information of vlan?

  Of UCS Manager? I don't have 1000v.

  Hello

  To add VLANs, you must go to the LAN tab, create them and after that, add them to the vNIC of blades you want to pass traffic for that/those support VLAN.

  You have configured a VLAN in UCSM native?

  The two, ESXi01 ESXi02 & use the same fabric for interconnection to pass traffic?  If a host goes through A traffic and the other through B, traffic will need to visit the switch upstream as cause of tissue switches do not switch traffic between them.

  Try the commands below and paste it here:

  * show circuit of service X Server profile / Y< chassis/server="" in="">

  * Connect nxos one | b< first="" try="" "a"="" then="" "b"="" and="" the="" output="" of="" the="" below="" command="" for="">

  * sh pinning border-interfaces

  * See the platform flexible NHS inter vlandb of info id #.< "#"meaning="" the="" vlan="">

  -Kenny

• VM Ware ESXi 6 - Raid controllers?

  Hi all here.

  I'm pretty new to VM Ware ESXi I need to use this software house to build my own computer to test, so now I build my computer, the last thing I need is a raid controller it supports ESXi 6.0 can sombardy recommend one for me.

  Requireing:

  min. RAID5

  6 x SATA 600 conneters

  so cheap as posibule
  

  
  

  I hope I can help here!
  

  Hello

  Please refer to controller RAID LSI - HBA equivalence mapping | ServeTheHome and ServeThe.Biz Forums and search for a provider (DELL, IBM, etc.) marked controller LSI.

  2108/2208 chipset based ones should work fine with VMWare 6. Be sure to get one with a saved stack cache (BBU) or a flash saved to get decent performance.

  Double check with VMWare HCL to ensure compatibility to the version 6: VMware Compatibility Guide: search system

  cykVM

• 4MOT/4 / 4000000:HDD - 1240

  I ran AHT and copy the following code came 4MOT/4 / 4000000:HDD - 1240, I tried to know what it is but can't seem to get info, can anyone shed some light on this here.

  Thanks Mark

  More precisely than the code refers to the hard drive fan motor. 99% of the time that your hard drive has failed.

• Toshiba Satellite A100-683 - display resolution of 1280 x 800

  Hallo,

  I just had an upgrade from Windows Xp to Windows 7.

  I downloaded and installed all the drivers for this model of Toshiba web site, including the ATI mobility radeon X 1600 driver and the Mobile Intel (r) 945 GM Express Chipset controller 0.

  Later, while trying to set the resolution of the screen, I realized that I could only choose between 1024 x 768 or 800 x 600, but I don't know that before the operation I could put also the resolution of 1280 x 800 (maximum display resolution). In fact, the display resolution was much better than now.

  Can you help me please? How can I return to the maximum display resolution?

  Thank you very much in advance and greetings.

  Antonio

  Once more here to add some details: I tried to install the ATI mob. rad + Nvidia drivers, which can be downloaded from this site for Satellite A100-683 + windows 7 display.
  The second (Nvidia) seems to be the right one, as stated in the description (improves the features of the screen and allows different settings, etc.), but it doesn't seem to work.

  Any help? Thanx