Operating System - HP-UX
1832490 Members
3091 Online
110043 Solutions
New Discussion

deploy HP-UX OS on remote server

 
Delrish
Trusted Contributor

deploy HP-UX OS on remote server

Hi,

Is there a solution for deploying HP-UX operating system from a local pc to a remote HP9000 or HP Integrity servers?


Alireza
5 REPLIES 5
Ranjith_5
Honored Contributor

Re: deploy HP-UX OS on remote server

Hi,

You should have an ingnite-ux server configured. From a PC you canot push the installation image.

The procedure for setting up the installtion environment is a bit lengthy so that cant be mentioned in 3-4 lines. You have go through the ignite-UX administration guide for a detiled information.

http://docs.hp.com/en/B2355-90875/index.html

go through the above doc on Ignite-UX administration. There is a lot of info.

Regards,
Syam
Ranjith_5
Honored Contributor

Re: deploy HP-UX OS on remote server

Go through the attached doc..This will also help you..


Regards,
Syam
Mark Fisher_4
Frequent Advisor

Re: deploy HP-UX OS on remote server

I have actually done this, but it's extremely slow. You will have to NFS mount the sw DVD on you PC. I used Hummingbird NFS Mistro to NF mount the DVD on my ignite server. You can also build a sw depot from this NFS mounted disk to your ignite server.
Steven E. Protter
Exalted Contributor

Re: deploy HP-UX OS on remote server

swcopy the Core OS to the NFS mount point to improve speed.

use lanadmin to check that speed and duplex are appropriate for the networking environment.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Bill Hassell
Honored Contributor

Re: deploy HP-UX OS on remote server

NFS is not the best choice as it is a general purpose network filesystem. Software Distributor has a built-in port designed to provide installation services over the network without the exra overhead from using NFS. When you swcopy filesets, patches and bundles to a depot, it is automatically made available across the network.

Now deploying and managing a remote server does require a lot more planning. First, you must have remote access to the console for all the system(s). Newer systems have a built in LAN console, but older servers have a simple serial interface. Don't use the remote support modem as the interface is not secure (unless you have a private line to the site). Similarly, the LAN console or HP's web console is not secure enough for Internet access. Again, if you have a private network to the remote site, this doesn't apply.

Next, you need to plan a backup and restore procedure. There are many steps to this: the first is to take care of the boot disk and OS. Design your system so just the OS is on VG00 which simplifies using Ignite/UX. Is this a true Lights-Out operation (no local operator available)? If so, all your backups and restores will be via the network. (and be sure to analyze what happens if the network goes down). Using Ignite/UX over the network will require a local boot-helper (which can serve all the machines). You'll need to setup an Ignite/UX network server with enough disk space to hold all the images (current and some number of previous versions).

Then there's the matter of remote backups and restoring application data. There are a lot of choices, so you'll need to plan (and test) the solution. Remember to include the very slow speed of the network when it comes to backups and restores. Unless your company can afford a Gigabit remote network, backups will be a major obstacle for uptime.

A lot of decisions need to be made based on whether the server is truly isolated or there wiil be people around to change tapes, replace parts, change cables, etc.


Bill Hassell, sysadmin