Operating System - HP-UX
1847276 Members
3344 Online
110263 Solutions
New Discussion

Re: Ignite version mis-match

 
SOLVED
Go to solution
Daryl Smith_3
Occasional Contributor

Ignite version mis-match


What can I do to fix this error:

ERROR: The version of Ignite-UX on the server you are using (B.4.4.30) is different then the version of Ignite-UX that the client booted (B.4.0.203). The versions must match in order to ensure correct behavior. You may need to update the device you booted from with the components found on the server.

There was the default OS on this [rp2400] machine, however when I tried to Ignite it from my Ignite server (which is on a rx2600) I get the above error.

Thanks,
Daryl
6 REPLIES 6
Elena Leontieva
Esteemed Contributor
Solution

Re: Ignite version mis-match

Daryl,

Are your Ignite server and client running the same versions of OS? Looks like you have the lates Ignite on your server. If this is the case, install the client OS version filesets on your Ignite server and try to push the client again.
Your Ignite server can support 10.20, 11.00, 11.11 and 11.22
clients even if it is running 11.00 OS.

Run swlist -l fileset |grep -i ignite to see if you have all the filesets.

My Ignite server (11.00) looks like:
swlist -l fileset |grep -i ignite
# Ignite-UX B.4.4.29 HP-UX System Installation Services
Ignite-UX.BOOT-KERNEL-IA B.4.4.29 Installation Boot Kernel for IA64 clients
Ignite-UX.BOOT-KERNEL-PA B.4.4.29 Installation Boot Kernel for S700/S800 clients
Ignite-UX.BOOT-SERVICES B.4.4.29 Network Boot Services for System Installations
Ignite-UX.CFG-FILE-11-22 B.4.4.29 File Archives Used By Clients During HP-UX Install
Ignite-UX.FILE-SRV-10-20 B.4.4.29 File Archives Used By Clients During HP-UX Install
Ignite-UX.FILE-SRV-11-00 B.4.4.29 File Archives Used By Clients During HP-UX Install
Ignite-UX.FILE-SRV-11-11 B.4.4.29 File Archives Used By Clients During HP-UX Install
Ignite-UX.FILESRV-1122IA B.4.4.29 File Archives Used By Clients During HP-UX Install
Ignite-UX.IGNITE B.4.4.29 Graphical Ignite User Interface for Installations
Ignite-UX.IGNT-ENG-A-MAN B.4.4.29 Ignite-UX Manual Pages
Ignite-UX.MGMT-TOOLS B.4.4.29 Tools for Managing Data Files on an Ignition Server
Ignite-UX.OBAM-RUN B.4.4.29 User Interface Libraries Needed for Older Systems
Ignite-UX.RECOVERY B.4.4.29 System disaster recovery tools
Obsolete.INSTANTIGNITE B.11.00 INSTANTIGNITE

HTH
Elena.
Todd McDaniel_1
Honored Contributor

Re: Ignite version mis-match

Daryl,

I would say you must upgrade the Netbackup to the version of your Ignite server...

Also, I believe there is a small dependency of your Ignite server to be the SAME OS version. I cant find my notes but i think there is something that stated the OS have to be the same as well... maybe my memory is failing me...

For sure, you must upgrade the server in question to the same version as your Ignite server.
Unix, the other white meat.
Daryl Smith_3
Occasional Contributor

Re: Ignite version mis-match


Elena,

Thanks for the tip. I did infact have the wrong version on there:

# swlist -l fileset |grep -i ignite
# Ignite-UX B.4.0.203 HP-UX System Installation Services
Ignite-UX.BOOT-KERNEL-PA B.4.0.203 Installation Boot Kernel for S700/S800 clients
Ignite-UX.FILE-SRV-10-20 B.4.0.203 File Archives Used By Clients During HP-UX Install
Ignite-UX.FILE-SRV-11-00 B.4.0.203 File Archives Used By Clients During HP-UX Install
Ignite-UX.FILE-SRV-11-11 B.4.0.203 File Archives Used By Clients During HP-UX Install

Most likely they didn't get updated by my IA-only depot update. In any case I've updated them on the server. Any hints on how I can tell the client to get the updated files via the network?

Todd--as for the same OS, I'm not sure. From what I've seen, the 4.4.* version of Ignite is supposed to support IA and PA chipsets. Of course finding documentation that answers that question has been difficult...

Thanks,
Daryl
Elena Leontieva
Esteemed Contributor

Re: Ignite version mis-match

Daryl,

I would reinstall Ignite-UX on your server to include all the filesets, set it up as an ignite server and then push the client.

My client has the following:
coc741(root):/tmp> swlist |grep -i ignite
IUX-Recovery B.4.4.29 Ignite-UX network recovery tool subset
coc741(root):/tmp>

HTH,
Elena.
Todd McDaniel_1
Honored Contributor

Re: Ignite version mis-match

Hey Daryl,

Can you fill us in on what you ultimately did?

Would be nice to see it posted here as a solution.
Unix, the other white meat.
Daryl Smith_3
Occasional Contributor

Re: Ignite version mis-match

Todd,

Elaine pointed out why the version mismatch was occuring. The complete Ignite-UX bundle wasn't installed (just the Ignite-UX-11i version 1.6 portion of it (aka 11.22), which doesn't include updated versions for pa-risc machines [aka 11.00]).

After updating the Ignite packages, I was able to boot the client to a point where it didn't complain of a version mismatch. I did, unfortunately, run into other problems which I'll detail here just becuase you asked.

A) "boot lan.###.###.###.### install" doesn't work very well with a cisco 6509 [switch]. It requires a hub until you can get the IP specified on the client with Ignite. Once the Ignite process gets to the point of needing to mount the clients folder/file from the Ignite server you have to plug back into the cisco 6509 (for some reason my gatewayless hub failed to work beyond this point).

B) In order to properly ignite pa-risc machines you need a hp-ux 11.0 cd dated september 2003 (or later) AND support plus cd dated september 2003 (or later). Initially I created my depot with just the first CD and the machine would install properly but once it got done booting you run into several errors (a software error, and a processor error, generally they repeat a few times) that once you (a)cknowledge them, the server reboots. To fix this problem you need the support plus CD, and you need to add to your 11.00 depot the HWE1100 directory (additional patches). Once you've added that, when you Ignite the client and are specifying which software packages to install, be sure to select the HWE1100 package.

Then your Ignited rp2400 from an rx2600 will boot normally.

As a side note, I will say that 11.00 is a functions differently than 11.22. The major annoyance is ^C and @ not working. You "fix" this with a .profile setting:

stty kill '^K' (or ^U if you prefer)
stty intr '^C'

Also it appears the default umask is 000....yikes! But now I'm really off on a tangent...

Thank you everyone for your help!