UCS ISCSI Boot Jumb MTU

Similar Questions

• UCS iSCSI SAN Configuration

  All,

  I can't find good documentation on the connection of a UCS SAN iSCSI storage system.  We run an Equallogic SAN iSCSI and I need to connect our UCS system.  I find a lot of documentation on Fibre Channel, but of course who does not help me.  Does anyone know if any documentation configuration iSCSI they can point me to?  I intend to just use it for storage and will NOT try to boot from SAN.

  Thank you

  Ken

  Ken,

  There is no "formal" for iSCSI access guide, but it's pretty simple.  It's just like the implementation of ethernet access to something else. The only consideration you may want to make your MTU size is.  Most of the people set up MTU/frames extended on their iSCSI VLANS.

  This requires the following to accomplish.

  1. create a class system UCS QoS with a MTU of 9000 & apply to the vNIC (s) Service profile-> vNIC iSCSI->

  2. enable extended frames (9000 MTU) on all switches between (UCS) initiator and iSCSI Target (Equalloqic).

  3. turn on the frames on OS adapter (Vmkernel port for ESX, the Windows network adapter advanced properties)

  As you can see the only task-specific UCS is the QoS policy that allows an MTU of 9000 bytes size - assuming you use frames in your environment - very recommneded especially with 10 G.

  Robert

• Is iSCSI boot supported with VMware 5.5?

  Hello

  I see that VMware 5.5 is supported with the latest UCS code.  Do you know if it supports the iSCSI boot?

  Thank you.

  Hi Carl,

  Yes, it is, you can also check by looking at the compatibility below matrix (see example).  I would like to know if you have any questions or accept this post if I answered your questions

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

  

• iSCSI Boot target IP Question

  Hi all

  Setting up iSCSI starts for the first time and had a question.

  Installation: Blades UCS about a pair of N5K (vPC) with a double NetApp controller connected.  There are 4 UCS vNIC - two for only iSCSI (as the VLAN native) and two for everything else.

  The blades odd dΘmarrez since LUN on NetApp controller and the blades even dΘmarrez since LUN on NetApp B controller.

  So my question.  When I make for an odd Blade (for example) iSCSI targets, do I have both A and B "NIC" s point on A controller's IP?  Or NIC - A point on A controller and IP point of NIC - B to B controller IP?  I was not sure that, in this example, the controller would hold unit number logic that this odd blade is starting from.

  Thank you!

  Hi Ian

  You can add up to two iSCSI vNIC startup strategy. A vNIC acts as the source of primary iSCSI boot, and the other acts as the source of secondary iSCSI boot.

  "point of NIC - A controller - A IP and NIC B points to the IP Address of the controller of B ' YES.

  You would create another strategy of starting for blades, with the primary order / trade school.

• ISCSI Boot B200 M2 need, but get 'not enough available vNIC.

  Hello

  I'm trying to implement initialization iSCSI ESXi on a B200 M2 w / M71KR-Q card above.

  I add vNIC A and B (each linked to a fabric respectively), but trying to implement a vNIC iSCSI - I get the error «not enough vNIC» available

  Looking around, it seems that M71KR-Q only can support 2 vNIC (which I also confirmed by trying to add a third, same error message as above).

  I just thought that since the overlay of iSCSI vNIC real - it works.

  However, even when adding just 1 vNIC and trying to superimpose a vNIC top iSCSI - I get the "there not enough resources overall, not enough vNIC available" error message.

  Does anyone know if it is even possible to initializing iSCSI on B200-M2 w / M71KR-Q on?

  Thanks in advance!

  Petar

  Please refer to this document in the section documents iSCSI boot https://supportforums.cisco.com/docs/DOC-18756 it is very detailed, I tell myself.

  initializing iSCSI is only supported on CiscoVIC and Broadcom mezz cards. It is not supported on the M71KR-Q Qlogic Gen - 1 mezz.

  Dave

• install ESXi on UCS to boot from SAN

  Hello

  I have ucs and I need to boot from SAN

  I need to confirm something

  When I was installing WindowsServer the UCS to boot from SAN. I have attached the iso drivers for the HBA driver so that the blade can detect the boot LUN.

  Now, I'm going to install ESXi. Do you know if I need to use the iso as drivers for the HBA as with windows or ESXi detects this and will present me the boot LUN to start the installation?

  We will use the ESXi, VMware no custom of Cisco

  Thank you

  Hello

  A major difference:

  MSFT Windows has no drivers of enic fnic UCS preinstalled with the distribution of iso.

  ESXi has, but most likely not one who demands that the UCS support matrix.

  See http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html

  Therefore you install ESXi ISO of the distribution, and then you update the drivers of the enic/fnic

  See http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/vic_driver...

• iSCSI Boot on IBM Bladecenter

  Hi all

  Were switching environment leaves IBM with 32 GB of RAM and

  built in maps iSCSI. With that, we do iSCSI boot for the

  Drive to ESX. someone at - it experience with this? When I put it initially

  up, I did the installation with just an active card, it went very well, and

  on the prior knowledge of the fiber, I activated then the 2nd card and cela

  has run fine for a few days... Eventually the file system went read only.,.

  and I contacted Netapp. They sent documentation which seemed ot

  say disable the 2nd card, unless you will begin her. In

  addition, I had to completely out of the IP of the 2nd card

  to ensure that the errors do not return.

  Is this normal?

  Have you installed the Netapp iSCSI utility on each ESX Server ESX host? I also believe that I saw a Netapp engineer mention in his blog to turn off the second card at the start of SAN.

  David Strebel

  www.Holy-VM.com

  If you find this information useful, please give points to "correct" or "useful".

• IBM HS22 iscsi boot

  We bladecenter HS22 and tries to boot from iSCSI. Could someone do?

  At first, I don't know if I have it set up correctly, and in the second place, when I start installing esx 4 it cannot detect all partitions.

  The HS22 has a Broadcom NetXtreme 2, someone has set up one of these guys before, and he got to work.

  Second, the ESX 4 install the need of additional drivers during installation to detect partitions mapped to the NIC iscsi?

  Thank you very much.

  http://www.VMware.com/PDF/vSphere4/r40_u1/vsp_40_u1_iscsi_san_cfg.PDF

  Chapter four, begin an iSCSI SAN with ESX systems, which begins on page 51, says "guests only ESX with hardware iSCSI initiators can boot from SAN.

  Check the HCL to the product Versions Release = ESX4 and Type = iSCSI, return 20 results, which are all QLogic 405 x and x 406 re-slotted different forms.

  Probably not clear as you or your boss wants, however.

• Boot from SAN (iSCSI) No. hypervisor found 5.5

  Here is my config:

  VNX5400

  UCS blade

  10 GB LUNS dedicated to blade.

  VSphere 5.5 (image from Cisco)

  ESXi 5.5 installation is done correctly to the iscsi LUN, but on reboot, start the VMware hypervisor type recovery server.

  Says:

  BANK5: not a VMware boot Bank

  BANK6: not a VMware boot Bank

  No found hypervisor.

  I tried:

  UEFI vs legacy boot (before installing it as well as after the installation is complete)

  checked the mtu 9000 vnx nec and ucs iSCSI NICs

  Any help would be appreciated.

  Thank you

  Jim

  Yes - I found a shift of MTU.   Everything works fine now.

• Problem; ESX 5u1, initializing iSCSI on NetApp

  The problem that we see is;  VMware 5u1, even on 5 takes about 90% through the installation/copy of VMware on an 8 GB logical unit number (lun id 0)... .fails with the message "wait 2 start benches, found 0.

  HW configuration as follows;

  FIS 6248

  Blades B-200

  VIC M81KR Palo

  Configured "Device Ports" connection to NetApp 3240-10 GB e1a/e1b

  Firmware 2.0.2M

  Service profile

  assigned iSCSI (cdrom, iSCSI nic overlay) No. MAC startup strategy

  iSCSI boot vNIC, fabric a - no. failover, vLAN 550

  iSCSI_A vNIC, no failover, vLAN 550

  iSCSI_B vNIC, no failover, vLAN 551

  1 Mgmt vNIC fabric failover

  1 VMotion vNIC fabric failover

  VM - A vNIC, fabric failover

  VM - B vNIC, fabric failover

  NetApp 3240 DOT 8.0.2P6 7-mode

  10GB Ports connected to the FI 6248 "device Ports.

  E1A (vlan 550)

  E1B (vlan 551)

  It is a known problem with ESX 5.  At the end of installation to the iSCSI boot LUN, the Setup program tries to re - initialize the adapter iSCSI with a DHCP address.  This fails and kicks on the error you see.  Installation fine filled aura - restart just like you did.

  The VMFS LUNS not created on the start for ESX 5 LUN also is expected behavior.

  Kind regards

  Robert

• How to create a USB key with HUU for UCS

  Hello

  I have 4 UCS C220M3 requiring updates and I downloaded HUU2.0.3d - 1 for that in the ISO file

  I really want to use a USB key to start the UCS of the box before I shipthem - so there is no network can - just out of the box, boot on USB via F6 and go!

  I am Macedonia this before on code 1.5, but now with 2.0 I had all kinds of funny mistake, and I think its related to the way in which I create the USB

  So what is the best way to create a USB bootable from this Cisco's ISO image?

  I tried 3 kinds of 'decision-makers', but none can boot up and load the HUU.

  Later, I tried going to start and begin to HUU, but then just fails when loading the firmware and tools

  Please notify

  I did some research and found the defect following CSCup62091 who you might be hit.

  2.0(1a) HUU/4.0(1a) UCS USB boot error 906

  https://Tools.Cisco.com/bugsearch/bug/CSCup62091

  Let me know what you think

• initializing iSCSI SAN in VMWare Workstation 9

  Hi all!

  I created an iSCSI Target (Debian Wheezy) and an iSCSI Initiator (CentOS 6). Installation of netinstall (of CentOS) on eth0 to LUN0 on eth1 worked very well. Adjusted BIOS on VMWare to boot from first e1000. At startup, the operating system tries immediately PXE boot, iSCSI not...

  Any big brain here know what I'm doing wrong? I got about 16 hours sunk trying to develop this project, so any help would be appreciated! Thanks in advance for your time!

  Here is the answer to my problem: VMWare Workstation 9 does not support iSCSI boot.  It requires 'PXE chainloading', where a gPXE (or iPXE), PXE loads image gives VMWare PXE allows to start an iSCSI target.  Here are some valuable pages, I found on the subject, even if none show my specific "PXE boot CentOS of Debian iSCSI in VMWare Workstation 9"... guess I am the only one to write this tutorial!

  PXE boot Ubuntu on an iSCSI drive

  http://www.Heath-bar.com/blog/?p=184

  Setting up PXE chainloading

  pxechaining - Etherboot/gPXE Wiki

  Using iSCSI on Debian Squeeze (initiator and target)

  http://www.HowtoForge.com/using-iSCSI-on-Debian-squeeze-initiator-and-target

• The network connectivity of RedHat 6.4 Installer

  Please excuse my lack of knowledge in this area as this is all new to us (UCS, SAN and Linux).

  We have a UCS chassis with blade series B200 and start ISCSI disks on a HP 43000 storage nodes.

  With the help of the CISCO rep, we set up the profiles Server UCSM and parms ISCSI boot, etc. and installed Redhat 6.4 - Basic Configuration.  I'm now trying to configure the network access server and this is, I'm stuck and I wonder if a step is missed in our configuration.

  On the side of UCSM, it conversely fabric is assigned IPs xxx.xxx.34.71 and 34,72 with a VIP address to 34,70.  Both A & B fabrics are connected to our network switches and are also directly connected to our isolated SAN switches.

  We have created a pool of MAC and a POOL of IP (xxx.xxx.34.73 80) and created two VLAN VLAN20 and 21.

  In service profiles, I see:

  -two vNIC ISCSI, one for each switch fabric

  VLAN21 (Native) being for fabric sw A & B routes (xx.xx.0.21 & xx.xx.0.41) to ISCSI storage to start nodes. No adapter policy is set.

  -4 vNIC FabA and B - Dev, FabA and B-ISCSI. There is no configuration policy dynamics vNIC connection or LAN connectivity

  The FabX-Dev are assigned to the VLAN20 and ISCSI-FabX are assigned to VLAN21

  I see the blades in the tab LAN USCM, receive an IP address from the IP pool (for example. xx.xx.34.73)

  Seen this configuration, I now install the OS and once completed, I see eth0, ane ibft is already configured

  However when I run system-config-network, I see eth0, 2 and 3 are labelled Cicso VIC Ethernet NIC and eth1 is just Ethernet.

  Eth2 and 3 are configured for dhcp while eth0 is not.

  At this point, I can reboot and launch a KVM of USCM session. I can ping the IP assigned to the blade, but permission denied trying to ssh in as root.

  I tried to configure eth1 at xxx.xxx.43.60, but get a device is not present when you do an ipup eth1. I also tried to configure eth3 with the same IP address, but it does not work too.

  What Miss me?

  Norm

  Hello

  If you have decided to dedicate a NIC for iSCSI traffic (say KEEN 767), you should be allowing to the VLAN necessary under the Service profile > vNIC > VLAN article.

  Similarly, you must allow VLAN necessary in other vNIC.

  The OS point of view, you configure the IP address and associate it to the respective network interfaces.

  Padma

• Frames and DF bit

  Enabling Jumbo frames the UCS does not seem to set the DF bit? fix?

  This is adjustable by UCSM and/or CLI?

  Once I did the test on the jumbo supervises the performance of the network and cannot see any significant difference.

  During this time, I used an oracle RAC installed in the UCS and NetApp file with configuration of DROPOUTS server.

  In the UCS, you must configure MTU in two different places (QoS configuration and vNIC configuration).

  In your test with active df - bit indicator using the maximum size of the package of 8972.

• HO to start from a SD card with B200 M3 with 2.1 - 3A

  Hi all

  can someone help me?

  I need to start my B200 M3 of my Flex SD Card 16 GB of Cisco

  I made the following adjustments

  -Servers\Policies\root\local Disc political Config--> Flex Flash State = Enable + Mode = No. Local storage or any Configuration (two doesent work)

  -Servers\Policies\root\Boot Policy\ 1) CD Rom (doesent work)

  (- Servers\Policies\root\Boot Policy\) 1 CD Rom 2) floppy (doesent work)

  I can boot the ESX ISO but I don't se any of installation disk. The SD card is in the lower slot

  Can U help me?

  PS: the system a 2.13 hole has

  Hello Stefan,

  First of all, you have activated support SD card in local disk configuration strategy?

  If so, is the part of the policy of the service profile?

  Once you associate the service profile, enter the BIOS and make changes to the boot order of the devices.

  -on top of the doc.

  When FlexFlash is enabled in a policy of local disk and a server is capable of supporting SD cards, the controller of FlexFlash will be activated during the deployment of service profile.

  To manually start since the partition of the HV, Local disk should be present in the startup strategy used in the Service profile and be launched from the start of the BIOS (F6) menu.

  Limitation

  If FlexFlash is enabled and the startup strategy contains the Local disk, boot SAN or iSCSI Boot, then the boot order can be determined. You should disable FlexFlash before using one of these startup options and enable once startup is complete.

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

  Padma