topic Re: DHCP Error on Boot Up in Operating System - HP-UX

DHCP Error on Boot Up

Richard Schiavi — Mon, 06 May 2002 17:29:21 GMT

Whenever I reboot my HP UNix 11.00 Server I recieve a message on the Console as follows

/sbin/auto_parms: DHCP access is disabled (see /etc/auto_parms.log)

dhcpdb2conf(ERR): main, setdhcpent() failed to access client database
interface name "-u" rejected usage:
dhcpclient -b interface [-f tracefile] [-g class-id] [-G]
[-l debug_level] [-n] [-p] [-t log_type]
[-x send_attempts] [-z time_to_wait] [-s server_ipaddress]
dhcpclient -d interface [-s server_ipaddress]
dhcpclient -m interface [-f tracefile] [-l debug_level] [-p]
[-t log_type] [-z time_to_wait] [-s server_ipaddress]
dhcpclient -r interface [-f tracefile] [-l debug_level] [-p]
[-t log_type] [-s server_ipaddress]
dhcpclient -v

I have an Unconfigured NIC Card on this system If I enable to NIC and assign it an IP Address this message does not come up. I am not using this NIC so I do not want to enable it. Anyone have any ideas.

Thanks

Re: DHCP Error on Boot Up

Helen French — Mon, 06 May 2002 18:23:25 GMT

Hi Richard:

Check the file /etc/rc.config.d/netconf:

DHCP_ENABLE[0]=0

Enter '0' for DHCP parameters. Also if you don't use them, you can rename the file:

# mv /sbin/auto_parms /sbin/auto_parms.old

HTH,
Shiju

Re: DHCP Error on Boot Up

Ron Kinner — Mon, 06 May 2002 18:40:29 GMT

auto_parms more or less does a lanscan -i to get a list of available LANs, then checks /etc/rc.conf.d/netconf for a reference to that LAN. My guess is that lanscan finds the NIC then when it checks in netconf it finds a reference to the card INTERFACE_NAME[1]=lan2

but doesn't find
DHCP_ENABLE[1]=0

I expect if you either add the DHCP_ENABLE line or delete all reference to the card from netconf that the error will go away.

Ron

Re: DHCP Error on Boot Up

U.SivaKumar_2 — Tue, 07 May 2002 03:21:04 GMT

hi,
better disable that NIC through SAM.

regards,
U.SivaKumar

Re: DHCP Error on Boot Up

Richard Schiavi — Tue, 07 May 2002 10:33:29 GMT

The Netconf File does have the DHCP_ENABLE[0]=0 and there are no references to the LAN0 Interface. My work around for this is to assign that NIC an IP address then DISABLE it through SAM. I do not recieve the message after this is done.