iSCSI Boot on IBM Bladecenter

Similar Questions

• Problems IBM BladeCenter S ESXI 5.0

  Hello

  I need help because it's been more than me that I me down with my IBM Bladecenter S and VmWare esxi 5.0.

  Configuration of our Lady:

  BladeCenter S 8886

  5 blades HS22 7870 with SAS (CIOv) connectivity cards

  2 modules NUMBER

  Of we have the option configured "Lun to search the block devices" SAS connectivity card on "Lun 0 only" because we have the boot on san for hypervisors.

  Pour policies manage the paths to the disks since the ESXi are configured on 'Fixed '.

  Operating system: ESXi 5.0 (boot on san)

  Two clusters are made between the 5 blades with a shared storage pour access to VMS and allow the migration to hot.

  The problem:

  The hosts lose access to LUNS on which virtual machines are located.

  Reduce the number of this type Hauptstr we noticed when insulating each LUN on a single host, the problem was much less, the activate option but we happens the HA to pay and to make migration hot.

  The problem seems to happen when the number of i/O disk becomes high.

  Attempted procedures:

  Update of firmware Modules NUMBER, we went on a updated version officially ESXi 5.0 (1.2.3.006)

  Update the firmware of the blades with Tmob, updating also card SAS connectivity.

  The certifier we did support and compatibility of our material by material support of IBM, at the request of the IBM Software support.

  Sending many bundle vmsupport, with newspapers and configuration, software to analyze support.

  Notre Dame configuration support for IBM Labs we have indicated what they.

  The problem was also occurred en ESXi 4 Update 1 version, but only 2 times and with less of VMs, so less i/o.

  We are waiting for a correct solution on the part of IBM since September 2011, we still have to intervene too often day and night on our servers because of these crashes that even if they are less scouring with the insulation of the luns, still prevent us from sleep.

  Thanks for your help, she is welcome!

  Hi Jeremy,.

  We have the same problem IBM Bladecenter S with VMware ESXi 5.0.

  Case is IBM and VMware.

• 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

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

• 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

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

• IBM Bladecenter on ESXi Network Setup

  Hi people,

  can you direct me to a best practices document that describes the configuration of the networking aspects of ESXi on a Bladecenter chassis IBM HS20 servers.

  You can tell the true value of a man by how he treats people who can't do anything for him...

  No problem.

  -KjB

  Be sure to leave points in scoring messages useful/correct.

• Connect IBM BladeCenter to the existing network

  Hello world

  I have a BladeCenter chassis with 2 blades installed with nortel esx 3.5 and 2 ethernet switches layer 2/3 and I'm testing how best to link this to my network environment.

  I'm not a networking person, I just want to know how of uplink my blade going to my regular switches. My question is: what's the point of having 4nics by blade for balance so then I uplink my blade switches with a single 1 GB eth cable? What is the right way to do this?

  Another thing, I noticed the configuration of VLAN is the following: consider that I used two external switches to test, I used a sw to test the lan and I attached a cable to each blade switch this switch and everything seems fine. then I used the other external switch to simulate my DMZ, I joined a new cable from each of the blade goes to this switch and a port goes into the FORWARDING State while the other is in a State of DEADLOCK. now, I would like to understand why this is happening.

  Thank you for your help, these questions may seem very basic to you people, but as I said that I'm not a networking person, so be patient

  A common way to do this would be to spend 2 x 2GbE trunks by blade, one of each truck at a different base switch. Maximizes availability and increases the throughput. There are many other things to consider so I suggest that read you on the VMware doco.

  Dave

• Planning for VLANs on IBM BladeCenter S fo ESX

  I'm planning an implementation of VLAN logic using a BladeCenter S chassis. Since in a blade environment have you don't have several NICs (4 for each blade in my case) I thought what would be the best thing to do in my case. Here are the requirements:

  (1) I don't want to lose any NIC for standby use

  (2) I need to run virtual machines that require access to one or more of these networks: LAN, DMZ, network management (for SC), backup network, vmotion

  (3) performance of vmotion

  (4) network paths must be fully redundant and load balanced

  The configuration that I thought was to make a single vSwitch with 5 groups of ports: LAN, DMZ, vMotion, backup and management port and assign each group to a VLAN different.

  The problem with this configuration is that most of the connections will not have a real separation LAN, vMotion, backup and management because everything will work on the same NIC 4 so for vMotion traffic will not be separated and the backup traffic will share the same cards as well, so having an impact on the overall performance of the network If I run backups in hours of work; vview performance point is the same things that share the port LAN backup, vmotion, lan group and management.

  I'm not much concearned on the DMZ network performance, because we publish just our own internal portal that does not generate a lot of traffic.

  If some of the things I brought are incorrect or based on designs wrong please correct me. hope you will help me clear my mind on this configuration.

  Thank you in advance.

  Since then, she looks like my suggestion! I am more than happy with it, no more comment if you like it & deal closed. hahahaha just kidding...

  System engineer

  Zen Systems Sdn Bhd

  Malaysia

  www.no-x.org

• HP SAS HBAS with IBM Storage and SAS SAN vs iSCSI SAN

  Hello, I am working on a project, and I have to add a SAN solution to my client infaestructure. My client already has a HP Server and we wanted to add another server, but an IBM one. I thought I'd add storage IBM (DS3200) that has two SAS interfaces. The problem is that the Distributor IBM says who does not know if the HP Server will be able to communicate with the SAS IBM storage. So, one possibility was to put on the server HP HP SAS HBA Controller. The second option is to put a SAS HBA Controller IBM. I think that the SAS is a standard, it doesn't matter what brand I use of HBA. Should not it works anyway?

  There is another option which adds instead of SAS one iSCSI storage. The problem is that I do not know the performance than the iSCSI storage. I want to put inside it's VM with Exchange Server (50 mailboxes), an ERP (for 50 users) with it's SQL Server, a computer file virtual, a virtual machine server with Active Directory.

  So, the questions are:

  1 - does anyone have experience with iSCSI storage to see if its performance if goog enough (I intend to use a dedicated to the iSCSI network gigabit switch)?

  2 does anyone know if I use different brands of servers (in this example an IBM and HP) with a SAS storage IBM? Who be it already done? The HP SAS HBA are compatible with the IBM iSCSI storage? IBM SAS HBA are compatible with HP servers?

  3. in the case of being able to do what I say to question 2, that do you suggest? Put a HP SAS HBA within the HP Server or upgrade an IBM SAS HBA inside HP Server?

  Of course the option I want to use is the addition of SAS IBM storage instead of using an iSCSI one, but I'm not sure of their compatibility between HP and IBM storage servers.

  Thanks in advance.

  In this case, the reason why I wouldn't use SAS is that your application requires this level of performance and the cost as not justified. You can configure iSCSI and direct savings in most important features such as snapshot, replication and dedup. If you were available to this solution with the DS3200 spend you 10K and that none of these features. Performance is very good, but you will find that the system is not yet warmed up with this load. The SAS Protocol can support high IO, but is not what provisions IO, is the number of disks and the RAID mode that defines your ability to e/s. I put 40 K terraced small IOPS / s on a single caching of 1 GB iSCSI target, so he can make the e/s. flow is not as high , but do you really need it. In the future you can profitable move to 10Gbe if you find insufficient bandwidth, which would be faster than the SAS 3 GB limit that is uneconomic to upgrade 3 + times.

  Kind regards

  Mike

  http://blog.laspina.ca/

  vExpert 2009

• ESX 4.0 restart failed with IBM x 3650 M2

  Just installed 2 x ESX 4.0 Build 171294 on 2 x IBM x 3650 M2 yesterday and the two system worked very well so far. In any case currently having same problem happened on two devices. Whenever I reboot the system, it does not start in ESX with error message "boot hdisk0 failed. But when I boot using the DVD installation ESX 4.0 and selected boot from the first hard disk, there continue to start in ESX installed successfully without error.

  The vi client adapter and storage configuration, I see 4 x adapter scsi as below:

  • ICH10 - vmhba3

  • ICH10 - vmhba33

  • ISP2432 - HBA vmhba1 & vmhba2

  • LSI Logic Megarade - vmhba0

  vmhba0 is the place where the local disk (73 x 2 = RAID1) currently being attached & installed with ESX 4.0

  any idea?

  vcbMC - 1.0.6 Beta

  Lite vcbMC - 1.0.7

  http://www.no-x.org

  I had this problem too, when installing Win2k8 R2 on x 3650 M2. I guess it's the same for any OS.

  I found the following articles from IBM. I did have the chance again to check if it suits it.

  Local boot OS fails when the external storage is attached - IBM System x 3550 M2 / x 3650 M2

  http://www-947.IBM.com/systems/support/SupportSite.WSS/docDisplay?lndocid=MIGR-5081613&brandind=5000008

  This is for ACPI operating systems no UEFI.

  Operating system that supports UEFI does not start after message load defaults or deployment - IBM BladeCenter and System x

  http://www-947.IBM.com/systems/support/SupportSite.WSS/docDisplay?lndocid=MIGR-5079636&brandind=5000008

  UEFI and Windows 2008 operating systems.

• ISCSI HBA con problemas y el failover

  Is.

  Tengo el the siguiente problema: tengo UN IBM BladeCenter, in sus hojas tengo una an ESX 3.5 con una controladora iSCSI HBA DOUBLE. Por otro lado UN IBM DS3300 iSCSI storage con doble controladora.

  CONFIGURADO siguiente manera:

  A HBA port - 192.168.3.60 & gt; switch 1 & gt; SPA_NIC1 - 192.168.3.53 - SPB_NIC1 - 192.168.3.55

  B HBA port - 192.168.4.61 & gt; switch 2 & gt; SPA_NIC2 - 192.168.4.54 - SPB_NIC2 - 192.168.4.56

  Development the situation ahora y el problema.

  Having esta config tengo cuatro paths o caminos hacía las del LUN storage.

  Ahora el problema.

  If switch 1 (simulando una caida) apago El el failover happens sin problemas y los caminos increasing an el use switch 2. Hasta ahi esta in orden, don't sin embargo, cuando todo is restituye the led unit switch 1, el ESX no vuelve a ver estos caminos, por lo tanto if only una caida en el switch 2 the unit total seria perdida. Esto sucede tanto if the fixed esta o en MRU failover policy.

  The unica manera por the black recover esos switch paths led back 1 are doing UN Scaneo las LUNS. Sucede lo mismo so the caida is da en el switch2.

  MI jerking that're esos caminos is recuperen automatically cuando vuelven a estar activos, y currently only en indefinidamente "DEAD."

  The Plaça HBA are una QLOGIC 40xx.

  The question are so estoy cometiendo algun error config o tr por el contrario en is debe realize algun seteo para a nivel del ESX as chequee los paths.

  Gracias a todos.

  Buenas ElGogy,

  The "problem" is in the telephone box, todo lo demas esta Ok. Cabina give en dicha HCL y luego the quitaron y luego volvieron a poner. Finalmente esta con admitida ESX > = 3.5 y solo con Software initiator. (Played a look has the HCL ahora are easy con search: http://www.vmware.com/resources/compatibility/search.php?action=search&deviceCategory=san&productId=1&keyBasic=ds3300&maxDisplayRows=50&key=ds3300&release%5B%5D=-1&datePosted=-1)

  Fijate tambien in communities of las este thread of: http://communities.vmware.com/thread/121802?tstart=0&start=0

  Of todas formas as you creo La cabina esta running OK. El con las DS of ESX behavior are MRU, aun if usar el pones o no el fixed en ESX (the da igual has the cabina.). Este behavior is lo Indica has the 'lun to host mapping' pones en cabina cuando LNXCLUSTER el. (that are that hay than poner lo).

  Cabinas are Simplemente no tienen el failback automático. Supongo as lo hacen para avoid errors: If a cae switch, mejor you criteria y requiera manual attention stink if no dock than a switch could what's cae y is levanta todo el rato (fallos momentaneos en the conexion, fallos electricos in bucle, o firmware aleatorio, fallo x ej,) would be doing that el cambie rising path, no're lo mejor del mundo.

  A saludo y espero you sirva!

  http://kurrin.blogspot.com

• 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

• 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