vSphere on IBM HS 22 in BladeCenter H 8852

[mirko_josipovic]

Hi all

i have problems installing vSphere on HS22 7870B3G.

it boots ok and after loading network drivers (22%) it breaks connection to IMM of Blade which then lose connection to chassis AMM.

after that i have to restart Blade from AMM web UI and start over again.we tried to load vSphere from Media Tray(DVD) but problem is same.

so we have IBM H 88524YG loaded with:

1.two AMM (25R5778)

2.four Power Supply (31R3335)

3.six Cisco 3012 (43W4395) loaded in 1,2,3,4,7 and 9 Bay IO slot

4.two Fibre Brocade 20 port SAN Switch module (32R1812) loaded in 8, 10 Bay

5.two interconnect modul (39Y9314)

We have 14 blades in chassis but only 6 is for vSphere.

So HS22 7870B3G is loaded with:

1.2 Intel Xeon 5530,32GB ram

2.2×146GB SAS internal drives (for boot vsphere)

3.one QLogic Ethernet and 8Gb Fibre Channel Expansion (44X1940); two eth, two FC port

4.one Ethernet Expansion Card (CIOv) (44W4475); two eth

AMM has 10.0.29.0 range address

Cisco has 10.0.29.0 range address

Fibre Switch has 10.0.29.0 range address

Intenal management network of chassis are default and vlan id is 4095 ( tried vlanid 1000)

Cisco Modules

Firmware data:

Type : Main Application 1

Build ID : 12.2.40

File Name : CBS31X0-UNI

Release Date : 04/16/2008

Release Level : EX2

AMM firmware

Version:		2.50c
Release Date:		2009-08-31

Blades firmware

1 SN#YK12509982KP FW/BIOS P9E130A 08/24/2009 1.04 Different

1 SN#YK12509982KP Diagnostics DSYT19A 08/20/2009 2.33 Different

1 SN#YK12509982KP Blade Sys Mgmt Processor YUOO32F 1.05 Different

I tried to load RHEL 5 and Win2k8 and installation went fine.

So it looks like vmware is trying to make some changes (change to promiscuit mode or loads its driver) and then i loose connectivity to IMM of blade

which leads to loosing all connections between AMM and blade.

did anybody of you gays have something similar?

thanks

regards

[Frvik]

Have you solved your problem yet? I have the same problem when trying to install vSphere on HS22 blade, I have opened a cast to both IBM and VMware.

They are both working on it, so when I hear from them with a solution I post it here.

[francs]

Hi

I'm having the exact same issue on and IBM HS 22 in BladeCenter H.

Any help would be greatly appretiated.

Regards

[szekelyk]

Facing with the same issue, but ESXi 3.5 U4 embedded is working.

Krisztian

[CharlieU]

It has been a struggle to get the HS22 and vSphere to work nicely together. After a bitter fight I think I built a solid foundation.

It took 6 RMA'd CFFh cards. Make sure all data is accessible via the Hardware VPD on the AMM.

This is what it took to get me up and running:

The following can be done via the AMM if you are running an OS; I pxe'd to a live cd. Use 'Blade Tasks - Firmware Update'

• Blade IMM firmware update Version 1.05 - Build ID: YUOO32I

• Blade uEFI flash update Version 1.05 - Build ID: P9E131A

The following needs to be done via the UEFI shell to access the CFFh and the CIOv cards

• Download the UEFI Shell and the Mulitboot image for 8Gb CFFh, 4G & 8G CIOv Card

1. Unzip the contents of the Multiboot package onto the root directory of a Universal Serial Bus (USB) key along with the UEFI shell.

2. Insert the USB key into the chassis and make sure that the blade has the media tray button selected.

3. Boot the blade with the failing card and press F1 to enter Setup.

4. Select Boot Manager.

5. Select Boot from File.

6. Navigate to the USB key entry and select the shell and hit Enter. Yellow text will now appear on the screen.

7. Type "map -r" to see the drives and what mapping name they have.

8. If the drive is mapped (for example to fs0:), type "fs0:" at the Shell> prompt. The prompt should then change to fs0:

9. Type update.nsh; this will flash the 2.09af level of code to the card.

hope this helps!

-charlie

[dcbbeets]

Goodmorning see also the following tip from IBM

http://www-947.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5081233&brandind=5000...

- VMware: VMware 4.0u1, which will include the necessary

driver, is expected to be available in Fourth Quarter 2009.

Regards Davy

[francs]

My blades had the cKVM modules installed. By disabling them and using analog mode, I got around the disconnect problem.

Managed to install 2 blades this way using the remote ISO mount option.

[dcbbeets]

Goodday all,

Update 1 did not solve the problem.

Download and install new driver from http://downloads.vmware.com/d/details/esx_esxi_40_broadcom_bnx2_dt/ZHcqYmRqZHRidGR3

Regards Davy

[a2pr]

How can I create a esxi 4 u1 install iso with the new drivers?

[DmitriyIlyin]

ESX 4 Update 2 still does not have correct driver.

Need to use dcbbeets tip from this post http://communities.vmware.com/message/1427071#1427071

[stevenbright1]

I would ensure that you have your IMM and uEFI firmware version up to date. I don't remember the exact version, but I know I have ran into this exact problem with both ESX and other Linux operating systems during boot. Whenever the Broadcom drivers initialize, the IMM will lose its cKVM connection and sometimes its connection to the chassis AMM (and thus, the chassis media tray).

The IMM and uEFI firmware have been very buggy since their initial release for the HS22, so I would try to keep them up to date, but I realize how difficult itcan be when it can take a significant amount of time to update for each release (which seem to be released every 1-2 months). Best of luck!