make_net_recovery client fails to boot from image

[David Burgess]

Hi,

I've run a make_net_recovery on a server. Now when I try and boot it to test that it works it fails to get an address via DHCP or instl_adm. I'm not running a DHCP server so I guess I need to get it working via instl_adm. In the past when I've built a server from the Ignite server everything works fine. It's just the recovery image that fails to get past obtaining it's network parameters.

Any ideas?

Regards,

Dave.

[Sundar_7]

Hi Dave,

Make sure you have instl_boots service uncommented in /etc/inetd.conf and check the /etc/opt/ignite/instl_boottab file.

Sunda

[David Burgess]

/etc/inetd.conf and /etc/opt/ignite/instl_boottab are fine.

I found this on the web

1.11 Q: Using bootptab entries to satisfy the DHCP request doesn't work, why?

There is a known problem with patches PHNE_17123, and PHNE_13648 to
the bootpd daemon. If you are strictly using entries in /etc/bootptab
such as described in question 5.5 in this document, you may have
problems once these patches are on your server.

The workaround is to either:
- Load the patch with the fix: PHNE_19241 (11.00) or PHNE_19095 (10.X).
- Remove these patches.
- Or, create a dummy entry in the /etc/dhcptab file which works
around the defect. The entry can look something like the entry
below. You will need to set the subnet-mask for your network.

DHCP_POOL_GROUP:\
pool-name=BLUE_SUBNET_POOL:\
subnet-mask=255.255.255.0 :\
lease-time=120:\
addr-pool-start-address= 192.11.22.254:\
addr-pool-last-address= 192.11.22.254:

I've installed PHNE_28828 which supercedes PHNE_19241 to no effect.

The DHCP pool doesn't seem to make any odds.

Regards,

Dave.