Ignite - booting from Ignite server creates new client

[Kevin O'Donovan]

Y'all,

anyone can help me with this it would be much appreciated...

I have 2 HPUX 11.00 machines, A and B. A is acting as my Ignite server, B is a machine I'm trying to increase the / filesystem on from 143MB to 1024MB.

I've backed up B onto A using
make_net_recovery -s A -v -x inc_entire=vg00
which went through with no problems. Of course edited the system_cfg file so the / would be enlarged.

When I try to boot B from A:
a) boot lan. install; doesn't work
b) using bootsys from client or server reboots B but when it connects to A I get a message in Ignite saying something close to "An icon with the name B already exists, a new icon with the name B.<0x0....> will be created instead.". It creates this new icon, which of course doesn't have the backup behind it and it won't allow me to use the B icon, saying I should Boot it using Boot client from the Actions menu.

I've done the exact same thing with another machine, call it C, which backed up onto A fine, booted off A fine and did the recover fine. B & C are both L2000, HPUX 11.00, same versions of Ignite, etc.

Also, nslookup (straight and reverse) for A and B work fine on the server, A.

Anyone come across this behaviour, or have any suggestions of things to try to sort it out?

thanks in advance,
Kevin.

[Tom Geudens]

Hi,
A possible cause is that server B is not on the same subnet as server A (and server C is). In that case you need a boothelper (procedure is explained in the Ignite manual) to boot server B in the way you describe. Another alternative in this case is making a boottape (procedure is also in the Ignite manual) from the archive and booting server B from tape.

Hope this helps,
Tom Geudens

[Kevin O'Donovan]

Hi,

thanks for the input, but they're on the same subnet alright.

We've tracked it down a bit more, apparently Ignite stores the files in a directory with the MAC address of the LAN card in use. So when the client (B) boots from the Ignite server (A) it boots using the config with the directory name of its MAC address.

HOWEVER, when I do the make_net_recovery, it uses one MAC address, which is the same as lan0 in lanscan output, and when it boots from the Ignite server it provides a different MAC address for lan0 which didn't appear in the lanscan output at all.

Thus, it should be looking for /var/opt/ignite/clients/0x001234556 say, and instead is creating a new directory there, called 0x00453347 (both numbers out of the air as examples).

The client, A, is an L2000, core LAN I/O card being used, also has a 4 port LAN card installed which isn't in use (only LAN cable connected to box is in core LAN I/O card). This ring a bell with anyone?

Kevin.

[Sanjay_6]

Hi Kevin,

You can play with the mac address and even though the system B is identified with a differenet mac address now, you can use the cloing to install the os on system B. Try this link to guide you through the procedure,

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

Hope this helps.

Regds

[Hooi Siew Hoong_1]

Hi,

Let assume you are not using an very old version of Ignite software. My guess is that there are more than 1 lan connection on server B, that is why you see two MAC address for the same server B.

When you are booting up B using "bo. install", the TUI will prompt you which lan card to use. Select the lan card that you use to make_net_recovery. This will boot up to the correct B icon.

Another simpler way is to normal boot up B, add an entry for A in .rhost file. From the Ignite GUI in A, click Action->Boot Client. Input B hostname and click OK.

[Kevin O'Donovan]

Thanks for the replies, heres what happened...

the file /etc/rc.config.d/hpbase100conf for a reason unknown to myself was changing the MAC address of the lan0 card (which was being used). This change only took effect during HPUX 11.00 boot, so when I boot from the Ignite server it didn't pick up this change and had a different MAC address.

So, when I did the make_net_recovery, it had booted into HPUX and the MAC address had been changed at boot time, the backup being stored on the Ignite server in a directory with that MAC address in /var/opt/ignite/clients.

Booting off the Ignite server the MAC address hadn't been changed, and it tried to find a backup with the unchanged MAC address, which obviously didn't exist.

2 solutions, copy the backup into a directory with the unchanged MAC address, alternatively prevent the MAC address from being changed and do the backup again.