help in setting up Ignite server

[NDO]

Hi All!

I know this might sound as a repetition, but I want to be clear in what I am doing!

I have 5 blades running hp-ux 11.31, right now I am downloading the Ignite Software. I would like to make one of the blades as an Ignite server, and use this Ignite server to take ignite backups of the other 4 servers/blades.

Please can you confirm if my approach is correct:
1. download ignite software
2. installing in one of the blades
3.configure this as system as an ignite server
Now what remains to be done?

4. what to do in the clients?
5. How to take ignite backups of the clients?

Any help is appreciated.

F.R.

[Shibin_2]

Install ignite on your clients and configure your clients pointing to your ignite server.

you may read man pages of make_net_recovery. This is for your ignite network backup.

make_tape_recovery is for ignite tape backup. Read man pages for more details.

[Manix]

Hi,

Some simple steps
========================

1) Install the product
#swinstall -s
2) Verfiy the installation and note down the versions
#swlist -l product|grep -i ignite

3) Modify PATH and MANPATH variables
PATH=$PATH:/opt/ignite/bin
export PATH
MANPATH=$MANPATH:/opt/ignite/share/man
export MANPATH

4) Create software depots
#mk_depots -r B.11.31 -s
#mk_depots -r B.11.31 -s /dev/dsk/c0t0d0

The software depot is normally created in the following directory,
but can be placed in a common deployment location on another server:

/var/opt/ignite/depots/Rel_B.11.31

5) Create Ignite-UX configuration file

#mk_config -c -s
eg.
#/opt/ignite/bin/make_config â  c /var/opt/ignite/data/Rel_B.11.31/core_cfg
-s 192.168.112.231:/depot/HPUX-11.31

6) Create Index

#manage_index -a -f /var/opt/ignite/data/Rel_B.11.31/core_cfg -r B.11.31

7) Verify and examine the configuration file for following parameters.
(/var/opt/ignite/data/Rel_B.11.31/core_cfg)

source_format= SD

sd_server=

sd_depot_dir=
====================================
sw_source "core" {
description = "HP-UX Core Software"
source_format = SD
sd_server = "192.168.112.231"
sd_depot_dir = "/depot/HPUX-11.31"
source_type = "NET"
load_order = 0
===================================

8) Verify and examine the Index file(/var/opt/ignite/INDEX) for following parameters.

Check for the entry, cfg "HP-UX 11.31 Default"
==================================================
cfg "HP-UX B.11.31 Default" {
description "This selection supplies the default system configuration
that HP supplies for the B.11.31 release."
"/opt/ignite/data/Rel_B.11.31/config"
"/opt/ignite/data/Rel_B.11.31/hw_patches_cfg"
"/var/opt/ignite/data/Rel_B.11.31/core_cfg"
"/var/opt/ignite/config.local"
========================================================


9) Check the entry in /etc/dfs/dfstab and ensure that
NFS is running
.
share -F nfs -o anon=2 -d "Ignite Clients" /var/opt/ignite/clients
share -F nfs -o anon=2,ro -d "HPUX 11.23 Depot" /depot/HPUX-11.23
share -F nfs -o anon=2,ro -d "HPUX 11.31 Depot" /depot/HPUX-11.31

#ps -ef|grep nfsd


10) Check the entries in /etc/inetd.conf for tftpd,bootpd

tftp dgram udp wait root /usr/lbin/tftpd tftpd\
/opt/ignite\
/var/opt/ignite

bootps dgram udp wait root /usr/lbin/bootpd bootpd



11) Collect Client MAC address.

Shell>lanaddress

Shell> lanaddress

LAN Address Information

LAN Address Path
----------------- ----------------------------------------
*Mac(001B787AF2EA) Acpi(HWP0002,PNP0A03,100)/Pci(1|0)/Mac(001B787AF2EA)
Mac(001B787AF2EB) Acpi(HWP0002,PNP0A03,100)/Pci(1|1)/Mac(001B787AF2EB)
Mac(001B787AF2E6) Acpi(HWP0002,PNP0A03,200)/Pci(2|0)/Mac(001B787AF2E6)
Mac(001B787AF2E7) Acpi(HWP0002,PNP0A03,200)/Pci(2|1)/Mac(001B787AF2E7)

12) Edit /etc/bootptab and enter client inforamtions

#vi /etc/bootptab
ignite-defaults:\
ht=ethernet:\
hn:\
bf=/opt/ignite/boot/nbp.efi:\
bs=48
:\
tc=ignite-defaults:\
ha=001B787AF2EA:\
ip=192.168.112.177:\
sm=255.255.0.0:\
gw=192.168.114.252:\
ds=190.1.48.11

13) Restart inetd
#inetd -c


Look at the excellent link below on docs.hp.com..

http://docs.hp.com/en/B2355-90772/ch02s02.html?jumpid=reg_R1002_USEN

[NDO]

I am getting confused a little bit:
Shibin: you are saying to install ignite on clients and point those clients to the server?

Manix: You gave me a good step by step procedure to configure ignite server.

Does Shibin actions should be taken after the ignite server is configured? (Manix actions)

F.R.

[Manix]

Yes , you are correct the clients can be made
only after configuring the ignite server.

Both are correct , you need to go in steps.

Thanks
Manix

[NDO]

Hi

Where the client images will be kept? Assuming that I will only take ignite backups for only 4 servers, and only when there are configurations changes, how much space will be needed?
On point 4) create software depots. Is this the place where the images will be kept?

F.R.

[NDO]

Hi

I am having the following error, on point 4 when creating depots.
"#make_depots -r B.11.31 -s /dev/dsk/c0t0d0 -d /var/opt/ignite/depots/Rel_B.11.31
make_depots: warning - -r option ignored with -d absolute path name
ERROR: cannot mount /dev/dsk/c0t0d0 as CDFS, errno = 16"

the command mk_depots does not work.

F.R.

[Torsten.]

Maybe a better solution:

Install all needed software on one of the blades and create a golden image (even on itself).

Now configure the ignite server to make the image available to the clients (see ignite manual).

Now on the clients use "dbprofile" from EFI shell to boot the clients, select the golden image and install it in less than 30min.

[NDO]

Hi Torsten

>Maybe a better solution:

>Install all needed software on one of the >blades and create a golden image (even on >itself).

>Now configure the ignite server to make the >image available to the clients (see ignite >manual).

>Now on the clients use "dbprofile" from EFI >shell to boot the clients, select the >golden image and install it in less than >30min.

Scenario:

the other 4 blades are up running with their applications, but I do not want them to boot from the ignite server. I just want one of the blades to act as an Ignite Server, and take ignite backups of the others.
I have already downloaded from HP web site the Ignite software, and installed in one of the servers, now I am trying to configure it. But I am stuck in configuring the depots as it says on the manual. The manual assumes that I have installed the ignite server from the CD, but I did not.
Pls can you help

F.R.

[Torsten.]

You want to create backups only? So you don't need any depots on the ignite server.


Just do a "make_net_recovery" from the client and store the image on the server.

See the quick start guide at

http://www.hp.com/go/ignite-UX

[NDO]

Hi

>You want to create backups only? So you >don't need any depots on the ignite server.


>Just do a "make_net_recovery" from the >client and store the image on the server.

>See the quick start guide at

>http://www.hp.com/go/ignite-UX

Now I am confused.
Are you saying that what I really ought to do is :
1. install ignite software on all the other blades.
2. run "make_net_recovery" one each of the clients.
3. take this image created in point 2 and store it somewhere else.

Is that what you saying?

If so, does make_net_recovery produces a image (file) that can be placed somewhere in a storage?

F.R.

[Torsten.]

No, not somewhere else. You should place the image on the ignite server.

[NDO]

Hi

Ok, but for that, apart from installing the Ignite software, I need to CONFIGURE Ignite Server right?, So I need to create depots??

Pls clarify

F.R.

[Torsten.]

The steps written by Manix (creating depots etc) are neede if you want to do a fresh install from ignite server.

You just copy (swcopy) the installation DVDs to the server and configure them. Then you can do fresh installs.


But if you want to do backups only, you don't need the depots on the server.

[NDO]

Ok,

All I need now is to create some space in one of the servers, to cater for the ignite images of the other blades and use the make_net_recovery as this:

on the client:

#make_net_recovery -s
F.R.

[Torsten.]

If you use dbprofile later on to boot the clients in case of a restore, there is almost nothing to do on the server side.

Just create some space and export it via NFS.

Then run the make_net_recovery command for complete vg00.

[NDO]

Ok,

So after configuring NFS and exporting it,
the syntax to run the command will be, on the client:

"make_net_recovery -s -x inc_entire=vg00"

F.R.

[NDO]

Hi

When catering for space for the ignite images do we have to use "allocated" space of VG00 or the "used" space of VG00?

F.R.

[Dennis Handly · Accepted solution]

>When catering for space for the ignite images do we have to use "allocated" space of vg00 or the "used" space of vg00?

Only the used space. This may vary for sparse files and may balloon. (But you shouldn't have those on vg00.)

[Torsten.]

The ignite backup image is in fact a g'zipped tar file.
So the occupied space by files in vg00 does matter (don't care about swap).

[NDO]

Hi

On the server, I have created the following directory: /var/opt/ignite/recovery/archive/

then I did:

chown bin:bin /var/opt/ignite/recovery/archive/

Then on the same server I created a file in vi called exports on /etc/, and I have added the following line :
/var/opt/ignite/recovery/archives/ -anon=2,access=prep01

save & exit

Then run exportfs -av

On the client I have installed ignite and run, and gave me the following:

prep01[246]/opt/ignite/bin #./make_net_recovery -s 10.100.48.13 -x inc_entire=vg00
NOTE: /var/opt/ignite/recovery directory does not exist. Will create it.
* Creating NFS mount directories for configuration files.
nfs mount: 10.100.48.13:/var/opt/ignite/clients: Permission denied
ERROR: Could not NFS mount directory /var/opt/ignite/clients on 10.100.48.13. If the OS on the 10.100.48.13 is 11.31 or later, the dfstab
file on 10.100.48.13 should contain the entry "share -F nfs -o anon=2 /var/opt/ignite/clients". Ensure that /var/opt/ignite/clients
has been exported using the "shareall -F nfs" command. Otherwise, the exports file on 10.100.48.13 should contain the entry
"/var/opt/ignite/clients -anon=2". Ensure that /var/opt/ignite/clients has been exported using the "exportfs -av" command.
ERROR: Failed mounting directory /var/opt/ignite/recovery/client_mnt:/No such file or directory (errno = 2)
ERROR: Failed to create NFS mount directories for configuration files.

======= 01/26/11 11:22:14 SAST make_net_recovery completed unsuccessfully
prep01[247]/opt/ignite/bin #

Do I have to create a exports file as well on the client/prep01



Pls can you assist?


F.R.

[NDO]

Hi

I did the changes recomemded by the error message seen on the previous post, but now I getting the following error:

prep01[259]/opt/ignite/bin #./make_net_recovery -s 10.100.48.13:/var/opt/ignite/recovery/archives/prep01 -x inc_entire=vg00
ERROR: 10.100.48.13:/var/opt/ignite/recovery/archives/prep01 is an unknown host


Please can you help


F.R.

[NDO]

Hi All!


I think I have managed to create an ignite image after the changes suggested by the error message, and after running the command:

make_net_recovery -s 10.100.48.13 -x inc_entire=vg00
01/26/11 12:19:31 SAST Started ./make_net_recovery. (Wed Jan 26 12:19:31 SAST 2011)
@(#)Ignite-UX Revision C.7.11.444
@(#)ignite/net_recovery (opt) Revision: /branches/IUX_RA1009/ignite/src@81712 Last Modified: 2010-07-23 02:35:40 -0600 (Fri, 23 Jul
2010)

* Checking Versions of Recovery Tools
* Scanning system for IO devices...
* Boot device is: 0/2/1/0.0x2a3b48261bb4444.0x0
* Creating System Configuration.
* /opt/ignite/bin/save_config -f /var/opt/ignite/recovery/client_mnt/0x78E7D1723FBE/recovery/2011-01-26,12:19/system_cfg vg00
* Backing Up Volume Group /dev/vg00
* /usr/sbin/vgcfgbackup /dev/vg00
* Creating Map Files for Volume Group /dev/vg00
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg00.mapfile /dev/vg00

* Backing Up Volume Group /dev/vg01
* /usr/sbin/vgcfgbackup /dev/vg01
* Creating Map Files for Volume Group /dev/vg01
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg01.mapfile /dev/vg01

* Backing Up Volume Group /dev/vg02
* /usr/sbin/vgcfgbackup /dev/vg02
* Creating Map Files for Volume Group /dev/vg02
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg02.mapfile /dev/vg02

* Backing Up Volume Group /dev/vg03
* /usr/sbin/vgcfgbackup /dev/vg03
* Creating Map Files for Volume Group /dev/vg03
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg03.mapfile /dev/vg03

* Creating Control Configuration.
* Creating Archive File List
* Creating Archive Configuration

.........................

01/26/11 12:19:31 SAST Started ./make_net_recovery. (Wed Jan 26 12:19:31 SAST 2011)
@(#)Ignite-UX Revision C.7.11.444
@(#)ignite/net_recovery (opt) Revision: /branches/IUX_RA1009/ignite/src@81712 Last Modified: 2010-07-23 02:35:40 -0600 (Fri, 23 Jul
2010)

* Checking Versions of Recovery Tools
* Scanning system for IO devices...
* Boot device is: 0/2/1/0.0x2a3b48261bb4444.0x0
* Creating System Configuration.
* /opt/ignite/bin/save_config -f /var/opt/ignite/recovery/client_mnt/0x78E7D1723FBE/recovery/2011-01-26,12:19/system_cfg vg00
* Backing Up Volume Group /dev/vg00
* /usr/sbin/vgcfgbackup /dev/vg00
* Creating Map Files for Volume Group /dev/vg00
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg00.mapfile /dev/vg00

* Backing Up Volume Group /dev/vg01
* /usr/sbin/vgcfgbackup /dev/vg01
* Creating Map Files for Volume Group /dev/vg01
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg01.mapfile /dev/vg01

* Backing Up Volume Group /dev/vg02
* /usr/sbin/vgcfgbackup /dev/vg02
* Creating Map Files for Volume Group /dev/vg02
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg02.mapfile /dev/vg02

* Backing Up Volume Group /dev/vg03
* /usr/sbin/vgcfgbackup /dev/vg03
* Creating Map Files for Volume Group /dev/vg03
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg03.mapfile /dev/vg03

* Creating Control Configuration.
* Creating Archive File List
* Creating Archive Configuration

But, my console reseted, so I dont know if it runned successfully. I looked for any logs, like makerec.log1, and could not find anything, only the following:
prep03[534]/var/opt/ignite/recovery/archives/prep01 #ll
total 13030096
-rw------- 1 bin sys 6671399791 Jan 26 13:12 2011-01-26,12:19
prep03[535]

So I assume this is that tar archive. But I would like to test it if its fine. Do you know how can I test if that file is the image? Is there a way to test it? Or the only way is to try and restote it?

F.R.

[Torsten.]

How about "check_net_recovery" from the client?

The server should have log entries too.

[NDO]

Hi!

This is what I have got:

prep01[164]/opt/ignite/bin #check_net_recovery 10.100.48.13
ERROR: No response from Ignite-UX Server: "unknown"
prep01[165]/opt/ignite/bin #./check_net_recovery 10.100.48.13
ERROR: No response from Ignite-UX Server: "unknown"
prep01[166]/opt/ignite/bin #./check_net_recovery prep03
ERROR: No response from Ignite-UX Server: "unknown"
prep01[167]/opt/ignite/bin #

and from /var/adm/syslog/syslog.log
got this:

Jan 26 12:19:34 prep01 LVM[5382]: lvmadm -t
Jan 26 12:19:35 prep01 LVM[5405]: lvlnboot -v vg00
Jan 26 12:19:37 prep01 LVM[5584]: lvlnboot -v /dev/vg00
Jan 26 12:19:39 prep01 LVM[6049]: Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.conf
Jan 26 12:19:39 prep01 LVM[6049]: /usr/sbin/vgcfgbackup /dev/vg00
Jan 26 12:19:39 prep01 LVM[6050]: /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg00.mapfile /dev/vg00
Jan 26 12:19:40 prep01 LVM[6051]: Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.conf
Jan 26 12:19:40 prep01 LVM[6051]: /usr/sbin/vgcfgbackup /dev/vg01
Jan 26 12:19:40 prep01 LVM[6052]: /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg01.mapfile /dev/vg01
Jan 26 12:19:40 prep01 LVM[6054]: Volume Group configuration for /dev/vg02 has been saved in /etc/lvmconf/vg02.conf
Jan 26 12:19:40 prep01 LVM[6054]: /usr/sbin/vgcfgbackup /dev/vg02
Jan 26 12:19:40 prep01 LVM[6055]: /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg02.mapfile /dev/vg02
Jan 26 12:19:40 prep01 LVM[6056]: Volume Group configuration for /dev/vg03 has been saved in /etc/lvmconf/vg03.conf
Jan 26 12:19:40 prep01 LVM[6056]: /usr/sbin/vgcfgbackup /dev/vg03
Jan 26 12:19:41 prep01 LVM[6057]: /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg03.mapfile /dev/vg03
Jan 26 12:26:43 prep01 sshd[7970]: SSH: Server;Ltype: Kex;Remote: 10.100.4.14-49588;Enc: aes256-ctr;MAC: hmac-sha1;Comp: none
Jan 26 12:43:14 prep01 sshd[2219]: SSH: Server;Ltype: Kex;Remote: 10.100.4.14-50980;Enc: aes256-ctr;MAC: hmac-sha1;Comp: none
Jan 26 12:57:24 prep01 sshd[5537]: SSH: Server;Ltype: Kex;Remote: 10.100.4.18-2846;Enc: aes256-ctr;MAC: hmac-sha1;Comp: none
Jan 26 13:39:23 prep01 sshd[7970]: SSH: Server;Ltype: Kex;Remote: 10.100.4.14-49588;Enc: aes256-ctr;MAC: hmac-sha1;Comp: none
Jan 26 13:39:37 prep01 sshd[2219]: SSH: Server;LType: Throughput;Remote: 10.100.4.14-50980;IN: 19020;OUT: 12980;Duration: 6979.5;tPut_in: 2.7;t
Put_out: 1.9



F.R.