Can't "see" SAN disk to restore / clone into

[IanV]

Howdy,

I have a nice working SAN boot BL860ci2 from which I did a make_net_recovery to the Ignite server.

I have a new blade (same as above) with no internal disks which I would like to be a clone of my first server.

Ignite is fine and I have discovered both hosts and have registered the MAC addresses etc.

I've done the magic with the cpio etc to copy the correct parts between directory structures.

NFS is setup properly etc.

I have an EMC Clariion CX4 array. One 70GB disk is presented from only one storage processor port to avoid multipath issues during deployment. I can see the disk as a device in the UEFI when I do a scan.

My problem is when I have sucessfully booted off the LAN and go through my ignite-UX menu and then attempt to deploy the image the SAN disk (which is in the hardware scan - under show summary) is not in the list of disks under the [Root Disk] or File System tab . The setup warns me that I don't have a disk large enough to take te recovery image - in fact as far as IUX is concerned I don't have a disk at all?

Previously when I presented all 4 paths IUX refused to accept the disk as a Root "candidate" as it stated that it couldn't install into a "virtualized SAN disk".

Blade is under Virtual Connect SAN as an NPV device.

So as I now have the simplest configuration of a single SAN disk I'm not sure what to try next?

I could build a system on internal disk, and then mirrordisk across to a SAN volume, set the boot order and drop off the SAS disk as I did previously, but that is kind of defeating the object.

All contributions gratefully received.

many thanks

Ian

[IanV]

Hello,

It turned out to be that the disks had been presented in "failover mode 4" on the Clariion which is correct for HPUX 11.31 multipath but not suitable for the pre-OS Ignite-UX mini-kernel.

Representing the disks as the default "Clariion Open failover mode 1" made the single LUN path visible to ignite and the image was able to be deployed  sucessfully.

Once deployed the HPUX image could be shutdown and the disks presented as FM4 to match the HPUX native multipathing.

Hope this helps someone else in the future.

Ian