About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Troubleshooting
Problem
System hangs with error, 'loading ESXI S.V00', during the first start after VMware ESXi 5.1 is installed over legacy internet Small Computer System Interface (iSCSI).
Resolving The Problem
Source
RETAIN tip: H21725
Symptom
System hangs with error, 'loading ESXI S.V00', during the first start after VMware ESXi 5.1 is installed over legacy internet Small Computer System Interface (iSCSI).
Affected configurations
The system may be any of the following IBM servers:
- Flex System x220 Compute Node, type 7906, any model
- Flex System x240 Compute Node, type 8737, any model
- Flex System x240 Compute Node, type 8738, any model
- Flex System x440 Compute Node, type 7917, any model
This tip is not software specific.
This tip is not option specific.
The following system BIOS or UEFI level(s) are affected:
- Build ID: CNE121DUS, CNE122DUS, CNE125HUS, and CNE126HUS
Solution
The symptom was fixed with ibm_fw_uefi_cne136s-1.30_anyos_32-64 available on IBM Support's Fix Central web page at the following URL:
Workaround
Use the Unified Extensible Firmware Interface (UEFI) iSCSI to install EXSi.
Additional information
The iSCSI transfer for a number of files takes a lot of time.
Some Universal Network Device Interface (UNDI) implementations tried to skimp and not handle interrupts. The V7000 Storage Node has a very short KeepAlive ping. If they leave interrupts disabled, it can drop the link.
In the case of legacy start, it is the Network Interface Controller (NIC) Adapter ROM that implements UNDI. For UEFI start, it is UEFI core that implements UNDI.
Using a WireShark trace to analyze, the issue will happen when network bandwidth is poor for iSCSI and large amounts of data in one packet are requested by VMware boot loader. One possible workaround is to put the I/O in same chassis. Multiple legacy OS will be affected.
Document Location
Worldwide
Applicable countries and regions
- Worldwide
[{"Type":"HW","Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"QU01GRH","label":"PureFlex System and Flex System->x240 Compute Node->8737"},"Platform":[{"code":"PF032","label":"VM"}],"Line of Business":{"code":"","label":""}},{"Type":"HW","Business Unit":{"code":"BU050","label":"BU NOT IDENTIFIED"},"Product":{"code":"QU01GRJ","label":"PureFlex System and Flex System->x220 Compute Node->7906"},"Platform":[{"code":"PF032","label":"VM"}],"Line of Business":{"code":"","label":""}},{"Type":"HW","Business Unit":{"code":"BU050","label":"BU NOT IDENTIFIED"},"Product":{"code":"QU01GRM","label":"PureFlex System and Flex System->x440 Compute Node->7917"},"Platform":[{"code":"PF032","label":"VM"}],"Line of Business":{"code":"","label":""}},{"Type":"HW","Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"QUOEDBG","label":"PureFlex System and Flex System->x240 Compute Node->8738"},"Platform":[{"code":"PF032","label":"VM"}],"Line of Business":{"code":"","label":""}}]
Was this topic helpful?
Document Information
More support for:
PureFlex System and Flex System->x240 Compute Node->8737
Operating system(s):
VM
Document number:
863080
Modified date:
30 January 2019
UID
ibm1MIGR-5093610
Manage My Notification Subscriptions
