vmware ESXi 5 on Fujitsu Primergy RX100 S6

[RomulusMare]

I have a Fujitsu Primergy RX 100 S6 which worked just nice with ESXi 4. Everything, including sensor monitoring and RAID access, I have installed ESXi 4 from Fujitsu OEM packages.

Then upgraded to 5, downloaded directly from vmware and lost RAID access.

Then noticed that Fujitsu got a OEM packages for ESXi 5 and installed their offline bundle over my ESXi 5.

Now I lost all sensor data. CIM Server is stopped and while I can start it, there is no sensor data.

Any ideas?

[Heimatplan]

Hi RomulusMare,

Whenever you plan to upgrade, you should check the VMware Compatibility Guide. http://www.vmware.com/go/hcl 

Only use them with the EXACT BIOS you find on the HCL. Its Rev. 1.10.2863.A1. Only one version is compatible with ESX(i) and this version is sold outside Europe only.

I would recommend staying on the working 4-Version but keeping them in an non mission-critical environment only.

Ingo

[RomulusMare]

I doubt this has something to do with it.

HCL Lists the same just one BIOS version for ALL vmware releases, including the one which was working, and I moreover I have installed vmware ESXi 4 and 5 from Fujitsu DVDs for my RX100 S6.

[RomulusMare]

In the same HCL page it says:

"For further details about BIOS, server product configurations and best practices, please contact the server vendor."

So, basically I contacted the vendor and ESXi 5 is compatible.

[RomulusMare]

While installing the offline custom bundle from Fujitsu, a lot of VIBs get skipped, too many if you ask me. Could this be the problem? Why it skips so many packages?

~ # esxcli software vib install --depot=/vmfs/volumes/ThirdStore/fujitsu/FTS_FujitsuCustomOfflineBundleESXi50_2021515841_1069741.ZIP
Installation Result
   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
   Reboot Required: true
   VIBs Installed: Fujitsu_bootbank_svscimprovider_5.50-00
   VIBs Removed: Fujitsu_bootbank_svscimprovider_5.50-03
   VIBs Skipped: Emulex-Corporation_bootbank_emulex-cim-provider_3.4.15.5-01, Emulex_bootbank_ima-be2iscsi_4.0.317.1-1OEM.500.0.0.406165, Emulex_bootbank_net-be2net_4.0.355.1-1OEM.500.0.0.406165, Emulex_bootbank_scsi-be2iscsi_4.0.317.1-1OEM.500.0.0.406165, Emulex_bootbank_scsi-lpfc820_8.2.2.121.45-1OEM.500.0.0.472560, Fujitsu_bootbank_FTS-Configuration-VIB_5.0.0-202.1, Intel_bootbank_net-igb_3.2.10-1OEM.500.0.0.472560, Intel_bootbank_net-ixgbe_3.7.13-1OEM.500.0.0.472560, LSI_bootbank_LSIProvider_500.04.V0.24-261033, VMware_bootbank_ata-pata-amd_0.3.10-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-atiixp_0.4.6-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-cmd64x_0.2.5-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-hpt3x2n_0.3.4-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-pdc2027x_1.0-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-serverworks_0.4.3-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-sil680_0.4.8-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-via_0.3.3-2vmw.500.0.0.469512, VMware_bootbank_block-cciss_3.6.14-10vmw.500.0.0.469512, VMware_bootbank_ehci-ehci-hcd_1.0-3vmw.500.0.0.469512, VMware_bootbank_esx-base_5.0.0-0.7.515841, VMware_bootbank_esx-tboot_5.0.0-0.0.469512, VMware_bootbank_ima-qla4xxx_2.01.07-1vmw.500.0.0.469512, VMware_bootbank_ipmi-ipmi-devintf_39.1-4vmw.500.0.0.469512, VMware_bootbank_ipmi-ipmi-msghandler_39.1-4vmw.500.0.0.469512, VMware_bootbank_ipmi-ipmi-si-drv_39.1-4vmw.500.0.0.469512, VMware_bootbank_misc-cnic-register_1.1-1vmw.500.0.0.469512, VMware_bootbank_misc-drivers_5.0.0-0.7.515841, VMware_bootbank_net-bnx2_2.0.15g.v50.11-5vmw.500.0.0.469512, VMware_bootbank_net-bnx2x_1.61.15.v50.1-1vmw.500.0.0.469512, VMware_bootbank_net-cnic_1.10.2j.v50.7-2vmw.500.0.0.469512, VMware_bootbank_net-e1000_8.0.3.1-2vmw.500.0.7.515841, VMware_bootbank_net-e1000e_1.1.2-3vmw.500.0.7.515841, VMware_bootbank_net-enic_1.4.2.15a-1vmw.500.0.0.469512, VMware_bootbank_net-forcedeth_0.61-2vmw.500.0.0.469512, VMware_bootbank_net-nx-nic_4.0.557-3vmw.500.0.0.469512, VMware_bootbank_net-r8168_8.013.00-3vmw.500.0.0.469512, VMware_bootbank_net-r8169_6.011.00-2vmw.500.0.0.469512, VMware_bootbank_net-s2io_2.1.4.13427-3vmw.500.0.0.469512, VMware_bootbank_net-sky2_1.20-2vmw.500.0.0.469512, VMware_bootbank_net-tg3_3.110h.v50.4-4vmw.500.0.0.469512, VMware_bootbank_ohci-usb-ohci_1.0-3vmw.500.0.0.469512, VMware_bootbank_sata-ahci_3.0-6vmw.500.0.0.469512, VMware_bootbank_sata-ata-piix_2.12-4vmw.500.0.0.469512, VMware_bootbank_sata-sata-nv_3.5-3vmw.500.0.0.469512, VMware_bootbank_sata-sata-promise_2.12-3vmw.500.0.0.469512, VMware_bootbank_sata-sata-sil_2.3-3vmw.500.0.0.469512, VMware_bootbank_sata-sata-svw_2.3-3vmw.500.0.0.469512, VMware_bootbank_scsi-aacraid_1.1.5.1-9vmw.500.0.0.469512, VMware_bootbank_scsi-adp94xx_1.0.8.12-6vmw.500.0.0.469512, VMware_bootbank_scsi-aic79xx_3.1-5vmw.500.0.0.469512, VMware_bootbank_scsi-bnx2i_1.9.1d.v50.1-3vmw.500.0.0.469512, VMware_bootbank_scsi-fnic_1.5.0.3-1vmw.500.0.0.469512, VMware_bootbank_scsi-hpsa_5.0.0-17vmw.500.0.0.469512, VMware_bootbank_scsi-ips_7.12.05-4vmw.500.0.0.469512, VMware_bootbank_scsi-megaraid-mbox_2.20.5.1-6vmw.500.0.0.469512, VMware_bootbank_scsi-megaraid-sas_5.34-1vmw.500.0.0.406165, VMware_bootbank_scsi-megaraid2_2.00.4-9vmw.500.0.0.469512, VMware_bootbank_scsi-mpt2sas_06.00.00.00-5vmw.500.0.0.469512, VMware_bootbank_scsi-mptsas_4.23.01.00-5vmw.500.0.0.469512, VMware_bootbank_scsi-mptspi_4.23.01.00-5vmw.500.0.0.469512, VMware_bootbank_scsi-qla2xxx_901.k1.1-14vmw.500.0.0.469512, VMware_bootbank_scsi-qla4xxx_5.01.03.2-3vmw.500.0.0.469512, VMware_bootbank_uhci-usb-uhci_1.0-3vmw.500.0.0.469512, VMware_locker_tools-light_5.0.0-0.7.515841
~ #

[kjb007]

Those packages are not all custom Fujitsu, and are installed via the default package during install.

You can see the installed packages using 'esxcli software vib list'

-KjB

[kjb007]

May be a silly question, but did you reboot after the custom vib install?

-KjB

[Heimatplan]

Its a difference between "Its on the HCL" and "Its compatible". HCL means the Fujitsu ran a 3 days test and approved by signing a contract that this hw has passed every test. They are liable for bad stuff happening on their hardware. "Its compatible" just means: Yes, we could install it, for anything else: Good luck.

Is the RAID-Controller on board or a seperate card? Maybe you can especially look for the used card if its not onboard.

Ingo

[RomulusMare]

It's onboard.

Funny thing is that I HAD sensors data with original ESXi 5, just RAID data was missing. With OEM ESXi 5 from fujitu I installed over, I do not have anything.

[RomulusMare]

Now, looks like I have solved partly my problem. I have succeded in starting all services.

Two things...

1. CIM Server was stopped. Regardless if I was starting it from client, nothing happened. Noticed in vmkernel log...

sfcb

cimXmlFdHardLimit: 1022 - invalid control statement

cimXmlFdSoftLimit: 512 - invalid control statement

then cimslp -- using /etc/sfcb/sfcb.cfg

so I removed the two lines from config file and restarted CIM Server.

Still nothing. Reboot. Still nothing.

Then I have noticed that another service is stopped.

2. I/O Redirector. I've started it and finally got my sensor data back, INCLUDING storage.

But they look funny, I think they looked differently. Is the image in attachement, looking normal?

Drive 64_5 is a drive in my RAID which is still foreign and it's normal for the moment.

What battery is that? How should I deal with the alert?

[kjb007]

Looks normal enough.  That battery is the cache battery on your RAID card.

-KjB

[RomulusMare]

The server was off for a 6 months in a box. Could this be the cause for the battery failure? Also, what is the battery for? What can I loose without it?

[kjb007]

The battery in a RAID card is for cache.  Typically, it should be able to recharge unless it's gone bad completely, so the warning may only be temporary.  Without it, your performance to disk can degrade.

-KjB

[Mr_Smith2]

Hi,

I've just found this post through a google search and not sure if it is still being monitored / is active but for the record ...

The RX100 S6 is certified for use with VMware ESXi 5.  The query about BIOS versions is that this is the version which is sent with the machine for initial certification.  It may not be 1.0 as there will be various developement builds of the BIOS before a server is released.  Every single new BIOS after this is not re-tested by VMware but they are still supported by the manufacturer, who would deal with VMware directly if there were any issues introduced with new BIOS's and resolve them.

Fujitsu use LSI RAID cards and if you have the any of the RAID 5/6 cards or the newer RAID 0/1 card (D2607) then the default LSI CIMs support access through ServerView RAID.  This being said you should still use the Custom Fujitsu image on Fujitsu Servers or add the Fujitsu CIMs to the standard ESXi image.

The onboard SATA RAID IS NOT SUPPORTED for use with VMware ESXi. (And probably never will be on any Fujitsu server as things atand at present)

There was a bug in recent releases of ServerView RAID and it did not work correctly with ESXi for a while.  You need to make sure you are using at least version 5.5.7

To set up the connection between ServerView RAID and the ESXi host follow the instructions in the attached document.