topic Upgrade Ignite/UX on ignite server in Operating System - HP-UX

Upgrade Ignite/UX on ignite server

Balaji_5 — Wed, 29 Sep 2004 20:56:51 GMT

I have an ignite server, running 11i, and having Ignite/UX B.4.1.55. This server was used to store ignite images (make_net_recovery) of about 100 clients and also as a software depot. All the clients have ignite B.4.1.55 installed. I plan to upgrade the ignite version on the ignite server to B.5.1.33. I would like to know if there is any documented procedure to do this without disturbing the configuration files. Also is it possible to take a make_net_recovery of the clients without upgrading the ignite on the clients.

Re: Upgrade Ignite/UX on ignite server

Sยภเl Kย๓คг — Wed, 29 Sep 2004 22:27:15 GMT

Have a look at this
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=667878
regrads
SK

Re: Upgrade Ignite/UX on ignite server

Michael Roberts_3 — Thu, 30 Sep 2004 18:50:34 GMT

First off I would not recommend going to B.5.1.33 version of Ignite, B.5.4 is much better. See the information at http://software.hp.com/products/IUX for more information on that.

The file /var/opt/ignite/INDEX will be re-written when you update the version of Ignite-UX. The only content that will be changed will be any '# comment' lines that have been added by you. The Ignite behavior of the INDEX file will remain unchanged. All of the other configuration files will remain unchanged.

You cannot have a valid run of make_net_recovery on a client if it does not match the version of Ignite-UX that the server is running, that is an Ignite-UX requirement.

Re: Upgrade Ignite/UX on ignite server

Cheryl Griffin — Fri, 01 Oct 2004 06:38:44 GMT

It is always recommended to swremove the old version of Ignite and swinstall the new version. By doing so you avoid any problems of having mismatched program versions installed.

swremove only remove the program files for Ignite. It leaves all data files intact so that when you install the new version, you will see your old clients and data.

Look at the swagent.log for details of what it removes. You will find only program files listed.