Operating System - HP-UX
1849031 Members
4190 Online
104041 Solutions
New Discussion

Re: Ignite client has new lanic id

 
SOLVED
Go to solution
Ruth Hutchings
Occasional Contributor

Ignite client has new lanic id

Good morning, ignite experts everywhere, have a question here for you.
A HP-UX.11.00 ignite client has been given a new HP-PB 100 lan card, and therefore a new MAC address.
What's a best practice for updating the ignite server with this information ?
I had thought that the simplest thing to do might be to remove this client from the Ignite server GUI and then run a fresh install, but I haven't been able to do this because when I select the icon in the GUI, the option to remove client is greyed out. On the server I can see a directory going by the old MAC address name under /var/opt/ignite/clients,
and can also see from previous forum postings that confusion has arisen in the past over this issue. Should I manually remove the old MAC address directory and it's contents ?

Regards

Ruth

Criticism is the hallmark of a mediocre mind
2 REPLIES 2
Jerome Baron
Respected Contributor
Solution

Re: Ignite client has new lanic id

Hi Ruth,

show this FAQ :
Question


I replaced the client system, and the LAN address is now different. How can I restore the new system from the old net-recovery archive?


Answer


Ignite-UX uses a separate directory for each client under /var/opt/ignite/clients. Each subdirectory is named based on the client's LAN address (i.e., LANIC, LLA, MAC address, etc.).

If you replace the client hardware - or even the LAN card that the old LAN address was based on, then it will no longer access the same directory on the server.


Details


The simplest solution is to obtain the new LAN address, which you can do from the boot-ROM console command LanAddress (actual command may vary from system to system). Once you have the new address, then manually rename the directory. You may just remove the hostname symlink (it will be recreated automatically). Note that the LAN address must be in all upper-case, and begin with 0x.

If you already booted the client from the server which caused it to create a new directory, you can just remove that directory before renaming the old directory. Be careful not to remove the original directory or else you will loose the recovery information.

For example:

cd /var/opt/ignite/clients
mv 0x00108300041F 0x00108300042A
rm oldhostname

Products affected
all hp workstation b series
all hp workstation c series
all hp workstation J series
all hp Visualize b class workstations
all hp Visualize c class workstations
all hp Visualize J class workstations
all hp 9000 series 700 workstations

HP 9000 Workstations - UNIX HP Visualize Workstations - UNIX HP Workstations - UNIX Features


Regards,
Jerome
Ruth Hutchings
Occasional Contributor

Re: Ignite client has new lanic id

Succinct and to the point confirmation with the FAQ. Full marks for that prompt reply !

As soon as I renamed the directory Ignite "detected" the new client. Sorted.
Many thanks for your help.
Criticism is the hallmark of a mediocre mind