Hello Managers,
I've seen some questions and answers in the list archives concerning this,
but nothing definitive.
I have a client who, due to applications limitations, must run T64 version
4.0f on an ES40.
The hardware consists of the ES40, a KCPCC-CE internal raid controller, and
two KGPSA HBAs ( for connectivity to a dedicated SAN consisting of two
HSG80 controllers).
The client wants to use a mirrorset on the KZPCC as the boot device.
However, that controller is not nativity supported by 4.0f, so I need NHD3
to get that support.
Is there are way to load the OS directly on a unit on the KZPCC and load
the NHD3 at the same time? If so, can someone detail the procedure for me.
If not, ( and I suspect not) I assume I can load the OS on a standalone
internal SCSI disk and then load the NHD3. I can then use a vdump/vrestore
procedure to move the root/usr/var domains to a unit on the KZPCC.
Correct? ( I have moved the filesystems and made the new disk bootable
before, so I don't need detailed instructions, just a confirmation that it
can be done in this case.)
If I use the standalone method, do I load the OS, then patch kit 8, then
the NHD in that order? And should the KZPCC be physically installed in the
ES40 while I am loading the OS and patches?
Any other gotchas, or recommendations would be welcome.
Thanks.
John
Received on Mon May 16 2005 - 22:07:32 NZST