Summary: T64 4.0f, ES40, KZPCC-CE, and NHD3

John Galt <[email protected]>
Newsgroups gmane.os.tru64.managers
Message-ID <[email protected]>
Hello All,
Thanks to Ian Barker for his response. And to Christian and Russ at HP 
support who helped during the actual process.

The bottomline solution was to follow the instructions in the New Hardware 
Delivery 3 - Release Notes and Installation Instructions -- Section 3.4, 
skipping steps 1-8 which relate to  shutting the system down before a new 
full installation.

Basically the NHD3 CD is booted first with the following command:

boot -fl fax -fi GENERIC dqa0

Then follow the directions, swapping in the OS installation CD when prompted.
Pay particular attention to step 18 which specifies interrupting the reboot 
after the OS loads the subsets.  You must reboot from the NHD CD and not 
allow the system to boot to the hard disk.

Also, there is a misleading blurb in the notes about the NHD3 CD not being 
bootable on IDE CDROMs. I misinterpreted this statement. It relates only to 
the procedure for creating  a CD in section 2.1 of the release notes and 
not to an actual NHD3 CD.


John




Original Question:
-----------------------------------------------------------------------------
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.