Steps to install HP-UX from a ignite tape

[Rolando Cabrera]

I have a RX7640 servers with two identical NPAR.
I installed HP-UX 11iv3 in one of these and created a Ignite Tape.
In the second NPAR I installed the same operative system from the Ignite Tape, for this I selected "HP-UX Install" from the Ignite Menu.

The installation is OK, but when I try to run a installation depot the system indicates that "I don´t have permissions" but i am login as root user.

Which tasks need I do after the HP-UX Installation from the Ignite Tape?

Thanks for your help.

[Matti_Kurkela]

If your Ignite tape included the entire vg00, there should be no OS-related tasks left: after the Ignite tape installation is complete, the OS should be an exact copy of the OS of the server the Ignite tape was created in.

> [...] but when I try to run a installation depot [...]

Please describe _exactly_ what you're trying to do and how it's failing. With this description, I have no idea what you're actually trying to do.

If you're doing it on the command line, please copy & paste the exact command and any error messages you're getting. If you're using the swinstall GUI, take screenshots and/or attach the appropriate logs (accessible with the "swjob" command).

>[...] the system indicates that "I don´t have permissions" but i am login as root user

If you're dealing with local depots when this happens, it usually means one of two things:

1.) The system has problems resolving its own hostname. Make sure the hostname (in all forms) is listed in /etc/hosts with the correct IP address. The system's own hostname should always be recorded in /etc/hosts, even if you primarily use other name resolution services (DNS, NIS, LDAP?).

or

2.) The system's hostname has been changed without rebooting the system, and the swagentd process hasn't been restarted after the hostname change.

Fix:
sh /sbin/init.d/swagentd stop
sh /sbin/init.d/swagentd start

(When changing the hostname, you *really* should reboot the system, to make sure all the login sessions and system daemons are using the new name.)

MK