Single user mode and SAN attached boot disk

[Travis Harp_1]

I have several systems coming in this next week that are all SAN booting, once they come in they need to have their IP's changed.

It's been suggested that I should boot them to single user mode, make the changes and then bring them up to full run level.

Normally, I would just boot the system to full run level with no network cables in, make my changes (via local console) and then reboot the systems with network cables in.

Do either one of these plans have more merit than the other?


Thanks

[Patrick Wallek]

I vote for going to single-user mode. If you do this, then you don't have the potential problems of things hanging during boot because of no network.

[Travis Harp_1]

What steps would I take to mount the SAN boot drives.
Will they show up in an ioscan or do I need to do something else to access them?

[D Block 2]

Travis,
serverl systems? so, there is a distinct scsi path (SAN) for each system to boot from? I'll assume you have the disk volumes to boot from and these are distnict boot areas. (guess, I'm new to this game of booting from SAN).

it would also seem to me, that these boot areas have to be Masked for only the host-name to r/w.

you might want to try both of your install options... and see which better control methods you can implement.

I would suggest, creating an Ignite for each disk-area boot -- once after you are confident with the unix ip/hostname changes.

best-of-luck,
Tom

btw, I'll assume you have no issues with your SAN switches supporting this remote boot.. firmware is up-to-date, etc.