DHCP Problem

[Clodoaldo João Rodrigue]

Hello All,
In syslog.log there??s the follow entries:
Jan 7 18:12:45 arx04 bootpd[13396]: ACK not sent: reason = 316
Is it a problem ??
thanks for all

[A. Clay Stephenson]

Chances are that you don't even want your server to respond to bootp requests at all. If that is the case, edit /etc/inetd.conf and comment out the bootps line and then run inetd -c to reread the configuration file.

[Clodoaldo João Rodrigue]

I am following the entrances in syslog.log and also they appear as below:
Jan 7 20:27:59 arx04 bootpd[22060]: Received DHCPDISCOVER creating DHCPOFFER. R
equest data: ci = 0152415320A0218DD790D8C80101000000, req IP not sent, ciaddr 0.
0.0.0, giaddr 0.0.0.0, broadcast reply on, server id not sent.
Jan 7 20:28:27 arx04 bootpd[22060]: Received DHCPDISCOVER creating DHCPOFFER. R
equest data: ci = 0152415320A0218DD790D8C80101000000, req IP not sent, ciaddr 0.
0.0.0, giaddr 0.0.0.0, broadcast reply on, server id not sent.

I don??t know what happened.
an the dhcpdb file is empty.

[Ron Kinner]

There is a lot of network equipment (switches love to do this) out there which will try to use bootp or dhcp to get an IP address. If you go in via their maintenance port and manually assign an IP address then they will stop bugging you.

The question is tho do you want your hpux to act as a DHCP or bootp server? If yes then you will need a range of ip addresses for it to choose from. Odds are that it doesn't have anything in /etc/bootptab or /etc/dhcptab so it can't send out an offer. (If it had used them up then there would be something in /etc/dhcpdb.)

http://sequoia.ict.pwr.wroc.pl/~iro/hp/hp_install/APPXA.HTM

explains how to set it up if you really want it to work. Otherwise take Clay's advice and kill it off.

Ron

[U.SivaKumar_2]

Hi ,

Is your DHCP server is in another network (behind router or gateway ) ?

IF yes then you will have to configure your router to be a DHCP-RELAY agent.

regards,
U.SivaKumar

[Clodoaldo João Rodrigue]

Hello All,

Well, my HP-UX is a DHCP Server and it have two Ip ranges, One in netowrk 10.177.101.0 and another 10.177.102.0 and both with submask 255.255.255.0, but only one IP range this being offered (10.177.102.0).
Is there some solution or some patch to apply ?