ignite recovery problem

[Jennifer Lam]

Hi team,
On the server, I have ignite archive completed successfully for system name 'raven'; on a GUI window, I click the icon name 'raven' that I just created an archived and from an action menu, I do 'new install', after fill all the information in the /opt/ignite/bin/itool, then click 'go!', the recovery process is halted, at the mean time a new icon is created with the name 'raven.0x{LLA}'on the GUI window.
On the client system 'raven', it kept waiting for installation instruction from server
Finally, I have stop a new install process then re-create an other archive under the new icon 'raven.0x{LLA}', then after ignite archive completed successfully for system name 'raven.0xLLA}'and I do recovery to the icon 'raven.0xLLA}completed successfully.
My question is:
- it is not right that the server created an new icon 'raven.0xLLA}when I do recovery for the icon 'raven', isn't it? would you help me with this problem please. Thank you.
Jen

[Michael Tully]

What ignite version are you using?

Have you installed the latest 'pax' patches on the ignite server ?

[Bernhard Mueller]

Hi,

on your ignite server under /var/opt/ignite/clients you have a soft link like:
hostname -> MAC-address
for each client.

If you change the hostname or replace the LAN card (with that MAC address) Ignite tries to solve this potential problem by assigning a "suitable" name.

By default the MAC is that of the core I/O LAN or that of the active LAN interface, however if you have additional interfaces such as FDDI, or more than one active LAN card, e.g. if raven is part of an MC/SG cluster where the Core I/O LAN is typically used for a separate heartbeat connection, this may be the root cause of this issue.

use lanscan to find out the MAC addr's and check the links on your ignite server.

you may manually correct the links and the content of /var/opt/ignite/client//client_name
to fix the Ignite server GUI

Regards,
Bernhard

[Kelli Ward]

Hi Jen,
I had a similar issue in the past. My Ignite test-box had crashed and recovered successfully. However, when I later went to generate a new client, it did so, then failed to successfully create the archive. The previously created clients appeared to be fine.
I decided to delete and recreate the client.
On re-creation, it told me the client already existed and created a new client with hostname.MAC (the client only had one LAN card) and the second subsequent archive also failed. At this time, I decided Ignite might have corrupted in the crash, so I used swremove to remove the old Ignite and reinstalled Ignite again.
I did manually remove the clients with issues, but left the clients that were okay.
After doing this all was well.
Since you can create and recover achives with this hostname.MAC client, your issue isn't the same as mine was and Bernhard should be correct. The new hostname won't affect the actual Ignite operation. If it bothers you you can manually change it as suggested and that would be fine.
It is very possible that a client with that name existed and was removed, but "remnants" exist, which would lead Ignite to differ between the two by adding the MAC to the second one.
Ultimately, if you do want to clean things up with a reinstall, you can do so, but do not install Ignite over the top of Ignite, you're asking for trouble. Remove the old Ignite and install fresh. In your case, it doesn't sound necessary.

HTH,
Kel

[Steven E. Protter]

I had similar issues generated by an upgrade to Ignite after building an ignite-ux server.

The solution in my case was to go to the console of the target client, reboot the machine.

I booted, and then interupted and used this command line:

bo lan.ip_of_ignite_server install

Like wonderful unexplained magic this fixed the icon problem on the server and the install proceeded. I was able to from the server push the same installation again after that.

If Ignite is totally broken, its probably a good idea to get to 4.1.61 on the server, go through the configuration pain and do a client pull installation to at least get Ignite on the client.

Networking is always important, the boot above must be on the built in lan0.

SEP