Igniite N class with K class tape ?

[Larry Basford]

I am trying to ignite a N class from a K class tape. Is this possible ?

I was able to ignite a D class with the tape up to the first chance to abort. The C class will not.
I even made a DLT off the K and it also fails the same.
I get this error
HARD Booted.

ISL Revision A.00.43 Apr 12, 2000

ISL booting hpux (;0):INSTALL

Boot
: tape(0/0/1/0.5.0.0.0.0.0;0):WINSTALL
tape(0/0/1/0.5.0.0.0.0.0;0):WINSTALL: cannot open, or not executable
Exec failed: No such file or directory

[S.K. Chan]

The general cloning support statement from the make_recovery man page states:

The primary purpose of make_recovery is to create a system recovery tape, which is used to later restore that same system back to its previous state. make_recovery is not a generic cloning tool. It can be used to clone only systems with similar characteristics, such as kernel, drivers and i/o devices. When cloning is the objective,make_recovery isn't always the ideal tool, since the OS archives are specific to the machine the tape was created on. The cloning capabilities of make_recovery have only been tested only for systems within the same class. To create generic archives to be used across a wider range of systems, make_sys_image and make_medialif should be used.

[harry d brown jr]

Are you trying to boot off a DLT? Most DLT's won't work.

Check this out:

http://www.software.hp.com/products/IUX/docs/release_note_B.3.4.html

and go to section 4.4 (near the bottom) - search for "DLT Tape Boot Issues"


live free or die
harry

[Sanjay_6 · Accepted solution]

Hi Larry,

Looks like your ignite tape was prepared on a 32 bit system and the system you are trying to boot need a 64 bit make_recovery tape. The normal boot kernel on the K-Class make_recovery tape is INSTALL whereas the N Class needs a Kernel WINSTALL to boot the system.

Here is a link which might help,

http://us-support3.external.hp.com/cki/bin/doc.pl/sid=06f77f581bcf146ba0/screen=ckiDisplayDocument?docId=200000055176500

Hope this helps.

Regds

[harry d brown jr]

I should add that because the two servers (the K and the N-class) are SO different, you are better off "migrating" to the N-class from the K-class.

live free or die
harry

[Darrell Allen]

Hi Larry,

While you may be able to do this, you really shouldn't. There's different types of hardware on different classes and you may miss some drivers if igniting from an image made from a different class system. It's best to have an Ignite image for each server.

As Sanjay points out, 32 bit systems put INSTALL in the boot image while 64 bit systems put WINSTALL. And even if your K supports 32 or 64 bits, the ignite image from a K has INSTALL on it - even if actually running 64 bits.

Darrell

[Michael Tully]

Booting off a DLT may not work have a look at the following link which has a table off bootable DLT's.

http://www.software.hp.com/products/IUX/docs/release_note_A.3.5.html

also from this posting:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x158906295e00d6118ff40090279cd0f9,00.html

Given the very different classes of machines, I would be installing fresh!

-Michael

[Bill Hassell]

The first requirement is that the K-class MUST be running 64 bit 11.0 or 11i. If not, the ignite tape will never work. No 32bit version of HP-UX can ever be loaded on N (or A or L or V) class machines.

The second requirement is that EVERY driver needed by the N-class must be first installed on the K-class. So the warning in the man page is valid...the machines need to be the same class. make_tape_recovery was never designed or tested to be an all-HP9000 igniter. In fact, there 3 different loaders to match the different classes of machines, WINSTALL is just one.

[Sanjay_6]

Hi,

the link i have posted above says,

quote //

There are a few guidelines to follow when wanting to clone a system using Ignite's make_recovery, make_tape_recovery, make_net_recovery and make_sys_image.

First of all, if using a tape from make_recovery or make_tape_recovery, the source and target system have to be the same type of architecture.

This is because there are currently 3 different Ignite-UX INSTALL kernels that
are used. The model of the system does not, necessarily, have to be the same, but the architecture does or the tape won't boot. The kernels are:

WINSTALL - used for all systems that are 64bit ONLY (N,L,A...etc).
VINSTALL - used for V class systems.
INSTALL - used for systems that can run BOTH 32 and 64bit (K,D,R...etc).

So, for example, if a tape is created on a K series machine and tried to boot on an N class it would fail with a complaint of:

WINSTALL cannot open or not executable , exec failed no such file or directory.

//endquote

Hope this helps.

regds

[Larry Basford]

First I'd like to thank everyone who replied.

The correct answer was an N can not be ignited from a K. The fact that the N is looking for WINSTALL and can't find it is because the K makes INSTALL not WINSTALL.

I then decided to do a new install from an ignite server. It failed the first try due to not having exports setup correctly but then I find the N will not boot from the net. I did a full install with patches from the CD. (don't know what I'd do with one of my L classes since they have no CDROM.) ((I do have ignite tapes.))

[Sanjay_6]

Hi Larry,

Just a suggestion,

you can create an ingnite make_recovery tape on N-class and use it to install OS on L-Class if both the systems have tape drives. If not, you can create a ignite make_net_recovery image from the N-Class and use it to install OS on the L-Class.

Here is a link which might be useful,

http://us-support3.external.hp.com/cki/bin/doc.pl/sid=6d22d53d062de4f3c3/screen=ckiDisplayDocument?docId=200000058668960

Here is the complete ignite UX sysadm link,

http://www.software.hp.com/products/IUX/docs/sysadm.html

Hope this helps.

Regds