[HPADM] SUMMARY - Ignite server on another OS

From: Eric Hunter (ehunter@marsys.com)
Date: Thu Aug 29 2002 - 20:47:23 EDT


Well, the consensus seems to be no, but there was a ray of hope in that
I was able to find messages through MARC and google groups that
suggested some people have had success using bootp to serve bootable
golden images to HP boxes, so I havent given up yet. At this point I'm
just writing to these people to find out what boot files they used and
what port ignite is on (one suggested that ignite is just bootp on a
different port).

So I'm still asking, has anybody out there tried this? -- even with
minimal success?

These boxes live in a predominately Win2k/NT environment and there is no
tape drive I can borrow to do a make_recovery tape, but thanks for the
suggestion Allen Marillier!

from google groups.

John Kelly wrote:

> RusH wrote:
> > begin qIroS napłodził(a):
> >
> >
> >>But what I really want to be able to do is
> >>to dd the entire disk image to a file and then save it to tape,
> >>thus taking a snapshot of the disk in case of failure.
> >>
> >
> > one does not have to know stuff like filesystem to simply dump a
> > content of a drive to a file, ghost'it, and if a driver will be
> > available (apparently it is in beta stage now) you will be available
to
> > mount this big file as a loop image
> >
> >
> >
> >
> > Pozdrawiam.
> >
>
> Look for Ignite on Google with the link below. This will make a
> bootable tape which will restore your disk config and the contents of
> /dev/vg00.
>
> http://www.google.com/search?hl=en&q=ignite+hp-ux
>
> Cheers
>
> JK

The Ignite solution has a lot of advantages over the dd of the disk.

With an Ignite make_tape_recovery tape you don't waste tape
backing up all the empty bits.

The Ignite tape can be used to restore onto different sized disks

It allows you to re-layout your disk.

If you have more than one HP you could use network based
Ignite, there is no reason to why the actual image shouldn't
be on a Linux box, you just need another HP-UX system as
the boot server... in fact it should be trivial to make a Linux
box into a boot server, it's just using bootp on a different
port and then tftp and NFS.

Cheers

Ken

from MARC:

 Tom Lieuallen <toml@engr.orst.edu>
Date: 2002-06-05 18:20:14

Looks like we can use bootp to give the network boot information
to a workstation that we want to install via ignite. I had been
using a minimum install of ignite on each subnet and instl_bootd.
I'd be much happier to just use dhcpd if I can.

I've had only minimal success so far. If I use HP's bootpd with the
following entry, it will tftp load the boot files from the HP bootpd
server.

myhostname:hn:vm=rfc1048:ht=ether:ha=00306e2bd86f:ip=128.193.54.123:\
        bf=/opt/ignite/boot/boot_lif

However, I'd like to be able to send the information from ISC dhcp 3.0
and be able to tftp load the files from a machine other than the dhcp
server. It _should_ work. The following is the relevant info from
dhcpd.conf.

    allow bootp;
    option domain-name "engr.orst.edu";
    option domain-name-servers 128.193.54.1, 128.193.38.105,
207.98.65.2;
    option ntp-servers 128.193.54.250;
    option time-offset 28800; # 8 hours from GMT (PST, adjust for PDT)

    subnet 128.193.54.0 netmask 255.255.254.0 {
      option routers 128.193.54.250;
      option subnet-mask 255.255.254.0;
      option broadcast-address 128.193.55.255;
      option domain-name-servers 128.193.54.1, 128.193.38.105,
207.98.65.2;
      option domain-name "engr.orst.edu";
    }

    host myhostname {
      hardware ethernet 00:30:6e:2b:d8:6f;
      fixed-address 128.193.54.123;
      next-server 128.193.40.123;
      filename "/opt/ignite/boot/boot_lif";
      always-reply-rfc1048 on;
    }

So, with this setup, the HP workstation gets the boot information but
hangs when WINSTALL loads. Just sits there...

    Main Menu: Enter command > boot lan
    Interact with IPL (Y, N, Q)?> n

    Booting...
    Network Station Address 00306e-2bd86f

    System IP Address 128.193.54.123
    Server IP Address 128.193.40.123

    Boot IO Dependent Code (IODC) revision 2

    HARD Booted.

    ISL Revision A.00.43 Apr 12, 2000

    ISL booting hpux (;0)/boot/INSTALL

    Boot
    : lan(10/0/12/0;0)/boot/WINSTALL
    9777152 + 1687552 + 2602664 start 0x2012e8

I even tried putting the /opt/ignite/boot files on the dhcp server
(happens to be a sun). Thus, removing the need for 'next-server',
but it still hangs.

Any ideas? Has anyone done this? It's sooo close. :-( :-(

Thank you

Tom Lieuallen
Oregon State University


--
             ---> Please post QUESTIONS and SUMMARIES only!! <---
        To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
       Name: hpux-admin@dutchworks.nl     Owner: owner-hpux-admin@dutchworks.nl
 
 Archives:  ftp.dutchworks.nl:/pub/digests/hpux-admin       (FTP, browse only)
            http://www.dutchworks.nl/htbin/hpsysadmin   (Web, browse & search)



This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:18 EDT