topic Re: setup ignite-ux in Operating System - HP-UX

setup ignite-ux

Jeffrey F. Goldsmith — Thu, 22 Mar 2007 14:08:18 GMT

Good morning all.

I have an rp3440-4 w/HP-UX 11.23. I was checking to see if I could use ignite-ux this morning when I noticed that it has not been setup yet. How do I go about setting up ignite-ux with x-windows?

root: / ==> swlist |grep -i ignite
B5725AA C.6.2.241 HP-UX Installation Utilities (Ignite-UX)

I know that a lot of people only use command line but I prefer using GUI when possible.

Thanks for the help.

Re: setup ignite-ux

Steven E. Protter — Thu, 22 Mar 2007 14:18:22 GMT

Shalom,

Nothing.

All you need to do is install it.

Connect via X Windows.

open a terminal session

whence ignite

Use that to run Ignite.

There are menus to guide you through the process of setting up an Ignite client or server.

For more:
Install
http://docs.hp.com/en/B2355-90153/apcs02.html
Golden System
http://docs.hp.com/en/B2355-90153/apcs08.html
Server stuff
http://docs.hp.com/en/5991-6440/ch02s05.html
For pa-risc clients
http://docs.hp.com/en/5991-6440/ch03s01.html

SEP

Re: setup ignite-ux

Jeffrey F. Goldsmith — Thu, 22 Mar 2007 18:23:28 GMT

Thanks for the information. The first time I tried to setup ignite-ux followed these steps and was stummped when I got to the "Server Setup: Software Depot Setup" page. Should this software be on my server or do I need to reinstall it from the DVD's again? For either case where can I find the required software?

Thanks.

Re: setup ignite-ux

Jeffrey F. Goldsmith — Fri, 23 Mar 2007 13:24:58 GMT

This morning I went through all the steps to setup ignite-ux on my server. After the program has been installed the Ignite-UX screen is up but there are no Installation clients. Did I do something wrong? On my other server (HP-UX 11.0) the server shows up as an Icon so I can create an Ignite tape. What do I need to do on this server (HP-UX 11.23) to get it to show up?

Re: setup ignite-ux

Patrick Wallek — Fri, 23 Mar 2007 14:17:29 GMT

Try going up to the ACTIONS menu and select "Add new client for recovery...".

I must say though, going through all of this to run a make_tape_recovery is a lot of trouble. You would be far better off learning, and using the command line for this (and lots of other things). After all you may not always have a GUI screen available.

The command to create a tape is fairly simple:

# /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00

That's it. I also add a '-t "$(uname -n) system recovery tape created on $(date)" ' to my command so it looks like:

# /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -t "$(uname -n) system recovery tape created on $(date)" -x inc_entire=vg00

If you need to know what the options do, have a look at the make_tape_recovery man page.

Also, using the command line makes it a whole lot easier to script things and automate them via cron.

Re: setup ignite-ux

Jeffrey F. Goldsmith — Fri, 23 Mar 2007 16:15:23 GMT

When I go into Actions and select Add new client for Recovery. I put in the server name which I am working on and it gives me a Confirmation page. Says "Command access using remsh(1m) to gravina was denied. Would you like to make a second attempt supplying the root password? (Note: The password will be transmitted over the network as clear test)

I answer YES and get an error remshd:login incorrect.

If I cant get this working I will have to create an ignite tape via the command line. I just dont know why it is so hard to set this up to work with a GUI.

Re: setup ignite-ux

Rasheed Tamton — Sat, 24 Mar 2007 07:06:19 GMT

You have to make trust the ignite server with the client by creating a file called .rhosts on the client side. The r commands are now normally disabled because of the security issues.

Tthe server name and the user name need to be added on the .rhosts file as below:

servername username

Then, enable remsh (the r* commands) on the client system.

The files related to are
/etc/inetd.conf
/etc/services
/var/adm/inetd.sec (hosts allow/deny) optional

After you uncomment (by removing the #) you have to restart the inetd command.

inetd or inetd -c (reconfigure option).

Regards,
Rasheed Tamton.