ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

BL20P boot from SAN with RDP

skippyllh
Occasional Advisor

BL20P boot from SAN with RDP

I am trying to get my blade servers to boot from the SAN (MSA1000). I can see the storage from the blades that have internal hard drives, but can't get the image to deploy to the blades with no internal storage. I have BL20P G@, MSA100o with dual 1500cs controllers, redundant 2/16V switches, and GBE2 interconnects to the SAN with RJ45 patch panel to LAN.
15 REPLIES
Steven Clementi
Honored Contributor

Re: BL20P boot from SAN with RDP

Lisa:

Have you installed the Boot from SAN scripts for RDP? There is a help file included with the package on how to modify your scripts to do "Boot from SAN" on your blades with no internal drives. Have you see this yet?


If so, there are a few different things that could be a problem, but would need to know more about the environment... Which errors are you experiencing, if any?


Steven
Steven Clementi
HP Master ASE, Storage and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5)
RHCE
NPP3 (Nutanix Platform Professional)
skippyllh
Occasional Advisor

Re: BL20P boot from SAN with RDP

No errors, just doesn't see the available space to install to.

I think I need to configure ssp, but i don't know how to find the wwid's of the blade servers.
Derek_31
Valued Contributor

Re: BL20P boot from SAN with RDP

Login to the SAN switch and you can look up the port number that a particular blade is connected to, and then show the WWID for that port.

If you have a Brocade switch, just connect to the web tools interface and you can easily pull up the name server and it shows ports and WWIDs of connectd devices.
Steven Clementi
Honored Contributor

Re: BL20P boot from SAN with RDP

If you use the remote console through the iLo, boot the server and go into the QLogic Bios utility. You can get the WWID from the utility as well as set the appropiate parameters needed to boot from SAN.

Alternatively, you can/should be able to get the WWID from a sticker on the card itself. (Requires removing the cover).

Alternatively, you can get the wwid's from your SAn Switch as Derek Suggests.


Steven
Steven Clementi
HP Master ASE, Storage and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5)
RHCE
NPP3 (Nutanix Platform Professional)
skippyllh
Occasional Advisor

Re: BL20P boot from SAN with RDP

the only ones showing up in the san switch are the ones that already have an image deployed to them (the ones with internal hard drives) the other ports show up as No_Sync.

After I get the wwid's, where do I enter them to make the blades see only the storage they each are supposed to see?
Steven Clementi
Honored Contributor

Re: BL20P boot from SAN with RDP

In the ACU, when you click on your MSA controller, to the right in the menu you should see Selective Storage Presentation.

Click SSP and select yes. That will put you into a window that allows you toselect which servers can see which LUN's.



Steven
Steven Clementi
HP Master ASE, Storage and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5)
RHCE
NPP3 (Nutanix Platform Professional)
skippyllh
Occasional Advisor

Re: BL20P boot from SAN with RDP

the only servers that show up to select, are the ones that are already configured, no the ones that need to boot from the san
Steven Clementi
Honored Contributor

Re: BL20P boot from SAN with RDP

Also, the one showing up as NO_SYNC will stay that way until you boot up and go into the qla bios utility and tell them to load the boot bios for the hba.

The blades you can see are booting from their local drives?


Steven
Steven Clementi
HP Master ASE, Storage and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5)
RHCE
NPP3 (Nutanix Platform Professional)
skippyllh
Occasional Advisor

Re: BL20P boot from SAN with RDP

Yes, the blades that I can see in the ACU are the ones booting from local drives.
Steven Clementi
Honored Contributor

Re: BL20P boot from SAN with RDP

Another way to get them to show up would be to locally set up an OS and load the fibre drives. The hba's do not link up to the switch until a driver is loaded or the boot bios is loaded.


I have some screenshots if they might help. The are on my home PC at the moment and do not have easy access to them.


Steven
Steven Clementi
HP Master ASE, Storage and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5)
RHCE
NPP3 (Nutanix Platform Professional)
skippyllh
Occasional Advisor

Re: BL20P boot from SAN with RDP

I found the wwid's in the qlogic bios setup. Thanks!

But, I still have to find a way to get the blades to see the storage without an OS so that they can get an image from the RDP server.
Steven Clementi
Honored Contributor

Re: BL20P boot from SAN with RDP

when you boot the blade and go into the bios with the boot option enabled, the hba should log into the fabric and the MSA should see it. Have the server sit at the QLA bios utility screen while checking the ACU on another machine.


Steven
Steven Clementi
HP Master ASE, Storage and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5)
RHCE
NPP3 (Nutanix Platform Professional)
skippyllh
Occasional Advisor

Re: BL20P boot from SAN with RDP

got acu to see the server! now i tried to deploy an image and got a 255 error on the rdp server.
Steven Clementi
Honored Contributor

Re: BL20P boot from SAN with RDP

Have you installed the Boot from SAN scripts for RDP? There is a help file included with the package on how to modify your scripts to do "Boot from SAN" on your blades with no internal drives. Have you see this yet?


At which point does it stop? Are you watching the install form the remote console?

Theorder of things... should be..

1. The script starts and the first thing it should do is reboot the server and dump an image down to the SAN disk. This image is a dos image that allows the Windows Installation to start in the next few steps.

2. The server should reboot and when it comes back, the normal process of dumping the Windows install files should happen.

3. The text mode Windows Install should then start and things would look like normal from there. (like you were installing locally)

4. After completing, install SP or the MPIO driver and your all done.


The "Boot from SAN scripts for RDP" file is important because it integrates some scripts and the necessary fibre drivers into your RDP server so that a blade can boot up, start a win install and already have the fibre drivers to complete the GUI setup mode.


How far is the install getting? Watch it on the remote console. Attach some screen shots if you can.


Steven
Steven Clementi
HP Master ASE, Storage and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5)
RHCE
NPP3 (Nutanix Platform Professional)
skippyllh
Occasional Advisor

Re: BL20P boot from SAN with RDP

Doesn't really get anywhere. It gets through conrep and then gets a 255 error.