HP-UX Booting problem + NTP,DNS configuration

[Vinay_20]

My current Set-up : I have a HP-UX CPU , with No Dispaly monitor attached to it. Instead I am using My Windows 2000 machine as interface to work on it . I have connected RS-232 console cable from win-2000 machine's serial port to HP-UX's serial port. And using "Hyper-Terminal" to get the dispaly. ( No GUI,only command prompt)

Problem : 1. HP-UX OS has "Stuck" while booting, this happens when it comes to -
"Start NFS client subsystem ....."

From here onwards it stops booting , and hangs...( Attaching the sanpshot of the same , Please see attachment" ) What is to be done to overcome this problem, and boot successfully ?

Question 2 : I want to configure NTP and DNS clients after succesful boot-up ( Please note that I don't have GUI dispaly only command prompt dispaly)
So Please provide sequence of commands to configure NTP and DNS clients, also to check whether these NTP and DNS deamons are up and running or Not..

[Scot Bean]

This means
- machine is not on the network
- NFS is not configured
- LAN config is incorrect

At the console, try hitting Ctrl-\ a couple times to break out of the hung NFS start.

This should let you boot the machine and then properly configure LAN access.

[RAC_1]

At the messages

"Start NFS client subsystem ....."

Can you do

Press CTRL + SHIFT + | (pipe)
or Press SHIFT-DEL
And check if goes further.

If not, power off machine and power it on. While booting, it would prompt you to press any key within 10 seconds. Press any key and say yes to interact with ISL prompt.

Once on ISL prompt do

ISL> hpux -is

This will take you to single user mode.
do mountall and edit /et/rc.config.d/nfsconf and isable NFS. Reboot the system and it should boot and give you a console login prompt.

Anil

[Steven E. Protter]

That hang is often caused by an error in networking in the /etc/rc.config.d/netconf file.

A misplaced dot is all it takes.

In the single user mode above, try this:

mount /usr

set_parms

It will rebuild networking and get it right.

Never keep a backup copy of netconf in the /etc/rc.config.d/ directory. It will get loaded again and your machine will become a gigantic paperweight.

SEP

[KapilRaj]

90 % it is a corrupted /etc/hosts file hopefully you can get a login prompt if u can Press 'CTRL+"\" ' key combination. and then correct the /etc/hosts file.

If this does not work, you may restart the system and when it says "Press a key to stop booting" .. Press a key

bo
injteract with IPL "Y"
hpux -is
and u get a prompt

correct /etc/hosts file here.

To configure DNS u just need to edit the following files check man pages for more details..

/etc/nwswitch.conf
/etc/resolv.conf

for NTP,

/etc/ntp.conf (?) not very sure

Regds,

Kaps

[Bill Hassell]

The hang for NFS is a very common problem. As mentioned, reboot the machine and interrupt the boot process to go into single user mode. Then mount the filesystems needed for vi to work:

mount /usr
mount /tmp
mount /var

Now edit the file /etc/rc.config.d/nfsconf and change all the NFS options from =1 to =0. Then reboot normally by typing: reboot -q

That will get rid of the hang. You can then setup your networking including DNS (resolv.conf and nsswitch.conf).

For NTP, after you get booted normally, use ntpq to find a working NTP server. If your server is called ntp1:

ntpq -p ntp1

This should return a report on the remote NTP server's time services. Once that works OK, edit /etc/ntp.conf and add these lines:

server ntp1
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10 # backup clock (internal)
driftfile /etc/ntp.drift # path for drift file

The ntp.conf file has a lot of comments. You can delete everything and just put in the above lines. A copy of the original ntp.conf file is found in /usr/newconfig/etc/ntp.conf.

Now edit /etc/rc.config.d/netdaemons and modify these two lines:

export NTPDATE_SERVER=ntp1
export XNTPD=1

Now start NTP with: /sbin/init.d/xntpd start

You can check on the progress of NTP with ntpq -p (with no server name, it checks the local system). You can also monitor accuracy in syslog.