topic Re: HP-UX Boot Problem !! in Operating System - HP-UX

HP-UX Boot Problem !!

Ramarao Bhavani shankar — Thu, 02 Mar 2000 17:23:08 GMT

Hi,

I am A Solaris System Administrator and a novice with HPUX.

I have a HP system which I should bring it on the network. I defined
domainname and also the IP address. When I try to boot the system it boots up
to the point where /sbin/auto_parm : searching network for DHCP server and just
hangs....

Can anyone help me out on this on how to go about solving this isssue and
bringing it on my NIS network.

Thank you

Regds.,
Bhavani

Re: HP-UX Boot Problem !!

Berlene Herren_1 — Fri, 03 Mar 2000 07:08:26 GMT

Break out and go to your /etc/rc.config.d/netconf file and set DHCP_ENABLE=0.

Regards,
Berlene

Re: HP-UX Boot Problem !!

Don Ferderber_1 — Fri, 13 Oct 2000 17:11:51 GMT

I have a HP6000 series 712 system which is on our NIS network. I defined domainname and also the IP address. When I try to boot the system it boots up to the point where /sbin/auto_parm :
searching network for DHCP server and just
hangs....

If I CTRL+SHIFT+| it will continue to boot and all is well. The /etc/rc.config.d/netconf is set to have DHCP_enable=0.

Need help so I don't have run down to the machine next time it's remotely rebooted.

Thanks

Re: HP-UX Boot Problem !!

Alan Riggs — Fri, 13 Oct 2000 17:37:21 GMT

You don't say how you defined the networking informaiton initially, but apparently there was some conflict since the server attempted to get an IP from DHCP rather than accepting the one you configured. I recommend re-establishing all of your networking information.

You can do this through /etc/rc.config.d/netconf
or by using the command set_parms.

Re: HP-UX Boot Problem !!

Dave Chamberlin — Fri, 13 Oct 2000 21:50:46 GMT

I recently had this exact problem after a "routine" reboot of the system - 6 hours and 4 HP support people later we got it to boot. We had tried a number of things like re-inputting the hostname and renaming the /sbin/auto_parms file to take it out of the init2 loop completely. We then did a complete power off reboot and it worked. The exact problem was never exactly determined, but the version of hpbasetconf in /etc/rc.config.d had a bad parameter so I replaced it with a corrected file. Apparently, a patch we installed in May for the 100baset LAN had given us a newer version of that file, but it didn't get put in rc.config.d . On HP's suggestion, I moved back the auto_parms file but set the mode to 444 instead of 544. This due to notes they had about a problem with it being 544. I rebooted without problems.