Booting Blades from a SAN
OK, so this is not the original first post I was going to make, however I just spent 3 hours for the second time in 6 months troubleshooting the exact same problem so I'm posting it here mainly for my benefit.
Our setup is an IBM BladeCenter with a combination of HS21 and HS21XM blades connected to an IBM DS3400 Fiber Channel SAN. We purchase our blades without drives and boot from the SAN. This works great once in production but has proved tricky to get into production (if you are like us and only do this every once in a while). I will list the steps below, however the tricky part that bit me again today is this: Once you have created your luns on the SAN and assigned them to your Blade our DS3400 (quietly) assigns a controller owner and preferred path. That controller owner setting must sync up with which HBA controller you have defined as the boot device. On our DS3400 screen that setting is under Modify/Change Logical Drive Ownership/Preferred Path. Without that setting the blade can see the drive, Windows setup can see the drive however it cannot write to it and strange 'unable to access disk' message occur.
I still have another blade to configure so I'll try and capture some screen prints and make a better how to post.
Our setup is an IBM BladeCenter with a combination of HS21 and HS21XM blades connected to an IBM DS3400 Fiber Channel SAN. We purchase our blades without drives and boot from the SAN. This works great once in production but has proved tricky to get into production (if you are like us and only do this every once in a while). I will list the steps below, however the tricky part that bit me again today is this: Once you have created your luns on the SAN and assigned them to your Blade our DS3400 (quietly) assigns a controller owner and preferred path. That controller owner setting must sync up with which HBA controller you have defined as the boot device. On our DS3400 screen that setting is under Modify/Change Logical Drive Ownership/Preferred Path. Without that setting the blade can see the drive, Windows setup can see the drive however it cannot write to it and strange 'unable to access disk' message occur.
I still have another blade to configure so I'll try and capture some screen prints and make a better how to post.
Comments