extending / by using ignite archive

[Taylor Lewick_2]

Hi all. I need to extend / on one of my servers. I have read through the posts and understand the safe/supported way of doing this is by creating an ignite tape and installing using the tape.

I have sucessfully created an ignite archive by running make_net_recovery.

My question is, can you do the same thing if you don't have a tape drive available, by booting to the ignite server over the network?

Not quite sure because the man pages make it sound like when you try this ignite realizes its a recovery and not an install, so don't know if I'll be given the chance to resize /

Any help is appreciated.
Taylor

[Jaime Bolanos Rojas.]

Taylor,

Yes, you will be able to do it, the idea is just to select the client that you want to install on the server, boot the client and then you will have a list of action or options in which you can modify the root file system and sereval other options.

Regards,

Jaime.

[DCE]

Yes you can. You need to boot the server over the network.

Interrupt the boot process and enter the command
bo lan. install

This will work best if both servers are on the same subnet. You also need to use the core i/o lan port on the server being ignited for the ignite to work properly.

Once the initial ignite screen comes up, you want to do the interactive restore - this will allow you to change the size of /, and any other mount point

[IT_2007]

remember that you won't be able to boot client over the network if Ignite server is on different subnet.

[Taylor Lewick_2]

DEC, thanks, that helps.

One more question, how do I ensure that I am using the core IO/Lan port?

Thanks,
Taylor

[Taylor Lewick_2]

Yep, both servers are in same subnet.

So when I run the boot command from the boot prompt, when it finds the ignite server, will it automatically find the client archive, or will I need to select it?

Thanks all, this is helpful.

[IT_2007]

yes. it will find the client archive unless you modifed it in Ignite server at /var/opt/ignite/clients directory.

[IT_2007]

To check core lan path:

# ioscan -fnClan
Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
lan 0 0/0/0/1/0 igelan CLAIMED INTERFACE HP A7109-60001 PCI 1000Base-T Core
lan 3 0/0/10/1/0/6/0 igelan CLAIMED INTERFACE HP A9784-60001 PCI/PCI-X 1000Base-T FC/GigE Combo Adapter
lan 7 1/0/10/1/0/6/0 igelan CLAIMED INTERFACE HP A9784-60001 PCI/PCI-X 1000Base-T FC/GigE Combo Adapter


In the above example, lan0 is the core lan. Hook lan cable to core lan device after initiating boot from Ignite.

[DCE · Accepted solution]

Taylor,

The network version i=of ignite works off of the mac address of the lan card of the ignited server.

IF you used the core i/o lan port on the server to make the ignite image (the ignite srver ueses the mac address as a directory name), then the ignite restore will automatically find the right image.

if you used a different card, then you wil have to do one of two things: either create a new ignite mage using the correct card, or create a new directory under /var/opt/ignite/clients on the ignite server with the correct mac address as the name, then move the files from original ignite backup, and relink the system name to tne new directory.

[Taylor Lewick_2]

Okay, thanks again for the info, I saw in /var/opt/ignite/clients the hostname for my server. I didn't even key off the MAC addresses. Now I realize that the hostnames are just links to the MAC addresses.

Should be my final question.
I saw in earlier versions of ignite you could run a command called check_recovery to compare any differences between now and the last time you ran a make_net_recovery or make_tape_recovery.

That command doesn't appear to exist anymore. Is there an equivalent?

[IT_2007]

No. Still you can check /var/adm/make_net_recovery.log for details whether it is successful or not.

[IT_2007]

Also as DCE said in the above post that:

Interrupt the boot process and enter the command
bo lan. install

================
Exact syntax is :

bo lan.,/opt/ignite/bin/WINSTALL

otherwise it will fail.