Stop ignite discovering SAN

[Michael O'brien_1]

Hi,

I have quite a few machines I have to ignite and they all have large amounts of SAN connected to them. When the ignite process starts it queries all hardware including the connected SAN, this can take 1-2 hours per machine. Does anybody know away to prevent the ignite build process from querying the attached SAN disks, with out actually unpluging the fibre cables.

Thanks
Michael

[Olivier Masse]

I would ask that question the other way around: why do your servers have a bunch of LUNs mapped to themselves? If these luns don't belong to your hosts, you would be better off configuring some zoning in your SAN. This will also prevent any data corruption if, in the future, you ever reference the bad lun from one of your servers.

[Steven E. Protter]

Shalom,

I agree. If they detect disk they don't use, then its a SAN zoning issue, not an Ignite issue.

SEP

[Michael O'brien_1]

Hi

Thanks for your replies to my question, all the san connected to the servers have been correctly zoned and the san connected to each server are to used by the server. Each server can only see the disk assigned to them but they all have quite a lot to disks assigned and they all have 4 paths to each disk for load balancing. My issue is before ignite will being it queries all the attached hardware, which I know is the correct practice it just takes a very longtime to query all the san down the four paths. I just wondered if their was an option to stop ignite querying the san attached disks.

Thanks
Michael

[Al Miller_1 · Accepted solution]

Hello Michael,

The latest version of Ignite-UX (C.7.2, June 2007) has a new feature that was driven by requests from customers like you. Hopefully this will be useful to you. From the release notes:

- In response to the request to improve I/O inventory performance,
Ignite-UX has introduced the ability to block particular paths and
protocols during inventory. This can be done by using the
"inventory_block_path", and "inventory_block_protocols" variables
either in the first 8KB in *INSTALLFS or from the hpux boot loader
command line. See instl_adm(4).

[skt_skt]

is this blocking treue for C.7.1.93. I do have a similar problem . Ignite start looking for disks with ISL information and gets hung if it start searching on LUN where the current stattus is NO_HW.

[Michael O'brien_1]

Thanks Al,

That was the answer I was looking for. I'll download the latest copy and give it a go.

Cheers
Michael

[Michael O'brien_1]

The new feature of Ignite allows you to limit the hardware which ignite discovers. See Al Miller's response.

[Michael O'brien_1]

Santhosh,

I had a similar problem with c7.1 where the ignite was hanging when if the server had SAN attached. We were forced to use an earlier release of ignite due to this issue. When we raised a call with HP they said this issue would be fixed in C7.2

I hope this helps.

Cheers
Michael