Crossflashing an IBM M1115 RAID controller to LSI firmware

2 Replies

1. Download the flash package, and unzip it to folder SAS
http://forums.laptopvideo2go.com/topic/29059-lsi-92xx-firmware-files/

2. Download latest firmware from LSI website.

http://www.lsi.com/products/host-bus-adapters/pages/lsi-sas-9211-8i.aspx#tab/tab4

At this time, I’m using 9211-8i_Package_P18_IR_IT_Firmware_BIOS_for_MSDOS_Windows.

3. Unzip the firmware package, and copy below files to folder SAS created in step 1
2118ir.bin from FirmwareHBA_9211_8i_IR
2118it.bin from FirmwareHBA_9211_8i_IT
mptsas2.rom from sasbios_rel
sas2flsh.exe from sas2flash_dos_rel

4. Create a DOS bootable USB drives, you can download a tool from below link:
http://rufus.akeo.ie/

5. Turn machine off, and grab the SAS address of the card, it’s on the back on a green sticker (ie 500605B0xxxxxxxx)

6. Use the USB drive to boot the computer, and flash the firmware

Convert LSI9240(IBM M1015) to a LSI9211-IT mode
Type in the following exactly:
megarec -writesbr 0 sbrempty.bin
megarec -cleanflash 0
<reboot, back to USB stick >
sas2flsh -o -f 2118it.bin -b mptsas2.rom (sas2flsh -o -f 2118it.bin if OptionROM is not needed)
sas2flsh -o -sasadd 500605bxxxxxxxxx (x= numbers for SAS address)
<reboot>
Done!

Convert IBM M1115 to a LSI9211-IR mode
Type in the following exactly:
megarec -writesbr 0 sbrempty.bin
megarec -cleanflash 0
<reboot, back to USB stick>
sas2flsh -o -f 2118ir.bin -b mptsas2.rom
sas2flsh -o -sasadd 500605b0xxxxxxxx (x= numbers for SAS address)
<reboot>
Done!

Convert LSI9211-IT or IR to LSI9211 IR or IT
Type in the following exactly:
Megarec -cleanflash 0
<reboot, back to USB stick>
sas2flsh -o -f 2118ir.bin -b mptsas2.rom (2118it.bin = IT mode Firmware, change according to which way to flash)
sas2flsh -o -sasadd 500605bxxxxxxxxx (x= numbers for SAS address)
<reboot>
Done!

Convert LSI9211-IT/IR back to IBM M1115
Type in the following exactly:
Megarec -cleanflash 0
Megarec -writesbr 0 sbrm1015.bin
<reboot, back to USB stick>
Megarec -m0flash 0 0061_lsi.rom (for latest LSI firmware, also included 2x IBM roms too, just change name)
<reboot>
Done!

7. You may get an error message “ERROR: Failed to initialize PAL. Exiting program.” when you try to flash the card, it means that you’re unable to do this from DOS. You have to get a UEFI shell (https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/EdkShellBinPkg/FullShell/X64/Shell_Full.efi worked for me on my 64 bit CPU) and put it on your usb stick. Then you have to boot into UEFI shell, and use below command

sas2flash.efi -o -f 2118it.bin -b mptsas2.rom
sas2flash.efi -o -sasadd 500605bxxxxxxxxx

IIS: SSL Certificate Disappearing after import

Leave a reply

After import the certificate into IIS, when I navigated away from the Server Certificates window, the certificate would disappear.
I could see the certificate in the server’s Personal Certificate Store using MMC (Microsoft Management Console) but it wouldn’t show up in IIS.

After investigate, I found below solution for this issue:

Save the three portions of the certificate into three separate files (Note: The Intermediate Certificate is optional, if you were not supplied with one, just skip the steps involving it):

privatekey.txt – Copy and paste the contents of the private key including the begin and end lines.
certificate.txt – Copy and paste the contents of the Regular Certificate including the begin and end lines.
intermediate.txt – Copy and paste the contents of the Intermediate Certificate including the begin and end lines.

Upload all these files to a linux server, and run

openssl pkcs12 -export -out certificate.pfx -inkey privatekey.txt -in certificate.txt -certfile intermediate.txt

then import the certificate.pfx into IIS

Netscaler VPX license

Leave a reply

When I tried to install certificate to netscaler vpx, I got below error message:

Certificate with key size greater than RSA512 or DSA512 bits not supported

After investigate, I found that this problem is caused by Netscaler License. You need to install at least 3 licenses to Netscaler to support it’s functions

1) Netscaler Platform licence: this enables netscaler features, but more importantly, unlocks the higher grades of encryption. License issued against Host-ID (= mac addr)
2) Netscaler Gateway platform licences / ICA licenses: this licence gives you up "unlimited" basic mode (ie ICA-only) connections. License issued against Hostname
3) Universal licenses: paid for licenses (you get free ones with XD platinum / NS platinum) which allow use of smart-access mode (=vpn, clientless, or ICA with epa). License issued against Hostname.

Enable Clipboard Copy and Paste in VMware console

Leave a reply

Log in to a vCenter Server system using the vSphere Client and power off the virtual machine.
Select the virtual machine and click the Summary tab.
Click Edit Settings.
Navigate to Options > Advanced > General and click Configuration Parameters.
Click Add Row.
Type these values in the Name and Value columns:

    Name	Value
    isolation.tools.copy.disable	FALSE
    isolation.tools.paste.disable	FALSE

Note: These options override any settings made in the VMware Tools control panel of the guest operating system.

Click OK to close the Configuration Parameters dialog, and click OK again to close the Virtual Machine Properties dialog.
Power on the virtual machine.

Note: If you vMotion a virtual machine to a host where the isolation.tools.*=”FALSE” is already set, the copy and paste options are automatically activated for that virtual machine.

To enable this option for all the virtual machines in the ESX/ESXi host:

Log in to the ESX/ESXi host as a root user.
Take a backup of the /etc/vmware/config file.
Open the /etc/vmware/config file using a text editor.
Add these entries to the file:

    vmx.fullpath = "/bin/vmx"
    isolation.tools.copy.disable="FALSE"
    isolation.tools.paste.disable="FALSE"

Save and close the file.

The Copy and Paste options are only enabled when the virtual machines restart or resume the next time or shutdown and power-on the virtual machine for changes to take effect. This must be done on the virtual machine side, not the guest OS side.