Guys,
I am a promise partner and reseller as well as a VMware partner and I have sold and installed the Promise vTrak E610fD arrays for years. I have successfully used the "channel sku" version of the x10 series (vendor slang for the non-apple version) on several dozen VMware installs over the years and haven not had any issues. The Apple sku version of the x10 was compatible with vSphere 4.1 and earlier but has compatibility issues with vSphere 5 and later. The Apple sku version of the x10 lacks ALUA support which has implications for VMware multipathing as well as an incompatibility with ATS (the VAAI detection mechanism). I have found ways around these issues for customers who are not willing to upgrade which you guys may find useful.
Lets start with the units with Apple firmware:
First off, there is a way out of the Apple firmware if you're willing to make a small investment. Its a 100% fact that the hardware on all the promise x10 series units are identical. For example, there is zero difference between the controllers running inside an apple version E610fD and a channel E610fD (the non-Apple version). The chassis are also identical in every way BUT Promise included code in their firmware to prevent the controllers from booting if you place an a controller running apple firmware into a channel chassis and vice versa. You can however purchase an empty channel version chassis form any Promise vendor (me) or someplace like eBay and re-use all your controllers, drives, power supplies, etc in that unit. At first, the controllers wont boot in the non-Apple chassis due to the firmware mismatch (apple firmware on the controllers but a channel serial number on the chassis).
To get the unit up and running again you simply have to console in using the built in serial port (an RJ11 jack on the back) and flash each controller, one at a time with the correct, non-Apple firmware version. It takes about 20 minutes to "convert" the chassis and get everything going again. I have done about 15 of these "upgrades" with 100% success (see instructions below).
To convert your controllers to channel firmware and use them in a channel chassis:
PRIOR TO DOING THIS, MIGRATE ALL DATA TO SOME OTHER LOCATION. THESE INSTRUCTIONS ASSUME A TOTALLY BLANK CHASSIS, HARD DRIVES, ETC. YOU WILL NEED TO REBUILD EVERYTHING ON THE CHASSIS INCLUDING DATA AND THE CONFIG!
ALSO, JUST TO CONFIRM, THESE STEPS REQUIRE YOU TO PURCHASE A NON-APPLE CHASSIS SO THAT YOU CAN RE-USE YOUR CONTROLLERS. IF YOU PERFORM THESE STEPS TO FLASH CHANNEL FIRMWARE TO YOUR CONTROLLERS AND THEN PLUG THEM INTO APPLE CHASSIS THEY WONT BOOT (recoverable if needed).
Promise Command Line Tips:
-To disable the buzzer issue: buzz -a disable
-To show network settings issue: net -a list -m
-To shutdown the system issue: shutdown -a shutdown
Phase 1 (preparation):
-Starting with both controllers in the old "Apple chassis", verify that the controllers are running Vtrak E-Class Service Release 2.5 version 10.06.2270.00 which was published 9/24/2009. (Upgrade if needed)
-Verify that you clearly understand that the conversion process is to be completed one controller at a time with the second controller sitting nearby, NOT in the chassis.
-Move both power supplies and battery modules over to the new non-apple chassis (unless you got power supplies with the new chassis)
-Verify that the battery modules are installed in the new chassis (they sit inside of the blower modules)
-Remove any hard drives from the new chassis (all drive bays empty)
-Verify both power supplies are connected to power on new chassis
-Insert ONE controller with Apple firmware into the new channel chassis (verify that the other slot on the chassis is 100% empty)
-Connect console cable to the controller to be flashed ( 115200 - N/8/1 ) and use your favorite terminal emulator
-Connect an ethernet cable between the PC and the controllers ethernet management port
-Power on the chassis (if its not already running) log into the controller and reset the controller to factory defaults
-Shut down the chassis and turn the power supplies off
Phase 2 (flash to channel firmware):
-Verify that you understand that the alarm on the controller will sound during this process. Do not panic when the alarm starts sounding, its totally harmles and can be disabled using this command on the terminal emulator: buzz -a disable
-Apply power to the new chassis while watching the terminal emulator screen and pressing "ctrl-c" several times during the boot process to abort the standard boot script.
-When the "PBL_RAM>" prompt appears you are ready to begin the flashing process
-The IP address of the controller should appear during the boot process, verify your network card is on the same subnet. (To show network settings issue: net -a list -m on the terminal emulator)
-Download channel firmware version ex10_fw_multi_3_33_0000_00.img (DO NOT USE THE LATEST VERSION, START WITH THIS OLD VERSION)
-Use this command to flash the controller:
ptiflash -t -h 192.168.90.1 -f ex10_fw_multi_3_33_0000_00.img
Note: You may have an easier time typing the first piece and pasting the image name as it seems to want to enter strange characters in the center if you paste the entire command.
-When you're returned to the prompt reboot via this command: reset
-Allow the system to fully boot, login via the CLI and verify that the controller works
-Shutdown the controller via this command: shutdown -a shutdown
-Boot the chassis up one last time, perform a factory defaults reset via the web GUI
-Shut down the chassis and turn both power supplies off.
-Remove the controller you just flashed with channel code
-Insert the other controller (again, there should never be two controllers in the chassis while performing these steps)
-Flash the second controller using the same process detailed above
-When when done with the second controller, install both newly flashed controllers into the new chassis and boot.
-Verify that both controllers work
-Perform a factory defaults reset
-Apply any additional firmware updates via GUI with both controllers booted on the new chassis
-If using expansion chassis, re-apply the very latest firmware (a second time) with the entire stack connected to ensure that all the JBOD I/O modules get updated.
-Perform one final factory defaults reset.
You may now install your hard drives and configure the subsystem as if it were a new install.
