12-10-2010 02:40 PM - edited 03-01-2019 09:45 AM
I've been booting my B200-M1 (and M2) blades from the SAN with no issues, but when I try it with the B440, it just hangs. I know it sees the LUN because when I boot from the install ISO I can select the lun as the install location. I'm also using the same boot policy as my B200 blades, so the targets are correct. The firmware on the system is 1.3.1n.
Anyone else having a problem SAN booting a B440?
12-20-2010 09:23 PM
Mark,
1. Have you included the corresponding option ROM (Host firmware package) with your profile?
2. What type of Array you using? For Clariion you have to ensure the Target SP from your Boot Policy is the "Owner" of the LUN if you plan on booting from it.
Regards,
Robert
12-21-2010 07:00 AM
Update and resolution:
Update: there was no problem with CentOS 5.5 or VMware 4.x - I just hadn't checked those when I posted this message.
Update: there is a problem with CentOS (or RHEL) < 5.5 - see fix below
Solution: during the install boot, use the following: 'boot: linux mpath'
The problem was that I wasn't using 'boot: linux mpath' during the install boot of CentOS. By not using mpath, something was messed up with the subsequent SAN boot.
Note: even with the Cisco drivers, this wasn't resolved until I used mpath
Note: despite the fact that Cisco doesn't have a driver for RHEL 5.3, it still works if you use mpath during install
Cheers!
12-21-2010 04:54 PM
Thanks for sharing your resolution Mark! I'm sure you wont be the last person to hit this.
Happy Holidays,
Robert
08-16-2022 01:15 AM
ok
08-16-2022 01:15 AM
okzxzxzxzxsx
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide