boot lan install for new server

[MikeL_4]

We had a server that we are replacing with a new server. The replacement server is in place using the same IP address as the old server.

I now need to load the new server with the old server make_net_recovery. Is there something I have to do on the Ignite server for it to recognize the change in servers ?

[Stephen Keane · Accepted solution]

If the Ignite server is filtering on MAC address, you'll have to update it with the MAC address of the new NIC. Unless you've kept the NIC out of the old server.

[Alex Lavrov.]

In /vat/opt/ignite (I think) on your ignite server, you'll see links. Each link is a name of the client of ignite and it links to the directory that it's name is a MAC address of the server. If you didn't kepp the original NIC, the link will be invalid and you'll fail to restore. You need to update this link with a news MAC adress and it should work.

Alex.

[Marvin Strong]

If the server resolves DNS you should be able to do the following from the ignite server if it is on the same subnet.

/opt/ignite/bin/bootsys -w -v {client_name}

[MikeL_4]

I modified the new MAC address in /var/opt/clients and it started the restore, then got to this error:

alloc_pdc_pages: Relocating PDC from 0xfffffff0f0c00000 to 0x1f700000.
gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: nfs3_link(): File system was registered at index 4.
NOTICE: autofs_link(): File system was registered at index 6.
NOTICE: cachefs_link(): File system was registered at index 7.
igelan0: INITIALIZING HP PCI 1000Base-T Core at hardware path 0/1/2/0
* Bringing up Network (lan0)
add net default: gateway 192.168.223.229
* Reading configuration information from server...

* tftp error log follows:
tftp> tftp> tftp> tftp> tftp> Transfer timed out.
tftp>
ERROR: Could not read /var/opt/ignite/INDEX from install tftp server.
NOTE: Retrying loadfile command...

[Bharat Katkar]

Hi,
As far as i remember you have to edit /etc/bootptab or /etc/opt/ignite/instl_boottab and add your new MAC address and it's associated IP address.

REgards,

[MikeL_4]

Thanks all, I realized the error of my ways... I was doing a boot lan.xxxx install to the correct subnet of the Ignite server but was forgetting to fill in the IP address on the Network Configuration screen...