bootptab entries

[Alan Meyer_4]

g'd morning... I'm not too familiar with bootp, can someone please tell me what these entries in my bootptab file are for...

test:\
bf=C2300B:\
hd=/usr/lib/X11/700X/bin:\
hn:\
ht=ether:\
vm=rfc1048:\
ha=080009000000:\
ip=192.30.103.01
ignite-defaults:\
ht=ethernet:\
hn:\
bf=/opt/ignite/boot/nbp.efi:\
bs=48
System-IPF:\
tc=ignite-defaults:\
ha=00d009000000:\
ip=190.40.101.22:\
sm=255.255.248.0:\
gw=190.1.48.1:\
ds=190.1.48.11

thanks...

-a

[Gavin Clarke]

I'm curious to know why you are using bootp?

I'm sure you've got a good reason.

Looks like you've got three entries there.

test

hn with an IP Address of 192.30.103.01
and
hn again with an IP Address of 190.40.101.22

ha is hardware address,
sm subnet mask
gw gateway
ds - Hmmmm.

Erm, that would be the easy ones anyway.

[Alan Meyer_4]

well, why bootp is being used is the basis of why I am asking these questions... These are systems I have been given and I am questioning the bootp usage.

[Gavin Clarke]

Well this is what ours looks like and we're not running bootpd, I hope it helps:

# Example /etc/bootptab: database for bootp server (/usr/lbin/bootpd).
#@(#)B.11.11_LR $Revision: 1.4.214.1 $ $Date: 96/10/08 12:46:42 $
#
# Format:
# nodename:tag=value:tag=value: ... :tag=value
#
# first field -- nodename (hostname) of terminal followed by colon
# (should be full domain name)
#
# Blank lines and lines beginning with '#' are ignored.
# Make sure you include a colon and a backslash to continue a line.
# Don't put any spaces in the tag=value string.
# The ht tag MUST precede the ha tag.
#
# The options listed below are commonly used for HP X Window terminals,
# HPUX NFS Diskless, BOOTP Fixed Address Devices. They are specified as
# tag=value and delimited by colons. For a list of all possible options,
# see the bootpd.1m man page.
#
# ba -- broadcast bootp reply for testing with bootpquery
# bf -- bootfile (for tftp download)
# bp -- bootp server IP addresses to relay the bootp requests
# bs -- bootfile size in 512-octet blocks
# ci -- client ID (for dhcp clients only)
# cs -- cookie server IP address
# dn -- domain name
# ds -- domain name server IP address
# ef -- extensions file, containing more options for the client
# gw -- gateway IP address (must have sm tag defined also)
# ha -- hardware address (link level address) (hex)
# hd -- home directory for bootfile (chrooted to tftp home directory)
# hn -- send nodename (boolean flag, no "=value" needed)
# hm -- hardware mask (hex) (must be preceded the ht tag)
# hp -- maximum hops value (cannot exceed 16)
# ht -- hardware type (ether) (must precede the ha and hm tag)
# im -- impress server IP address
# ip -- (client) IP address
# lg -- (MIT-LCS UDP) log server IP address
# lp -- LPR (line printer) server IP address
# md -- file to dump core image to in the event of a crash
# na -- NETBIOS name server IP address
# nb -- NETBIOS datagram distribution server IP address
# nc -- NETBIOS over TCP/IP node type (B-node, P-node, M-node, or H-node)
# nd -- NETBIOS over TCP/IP scope
# ns -- name server (IEN 116) IP address
# nt -- network time protocol server IP address
# rl -- resource location server
# rp -- path name to client's root disk
# sm -- network subnet mask
# ss -- swap server IP address
# tc -- template for common defaults (should be the first option listed)
# th -- threshold value in seconds
# to -- time offset in seconds from Coordinated Universal Time (UTC)
# tr -- renewal (T1) time value (a percentage of the lease time)
# ts -- time server IP address
# tv -- rebinding (T2) time value (a percentage of the lease time)
# vm -- vendor magic cookie selector (should be rfc1048)
# xd -- X window system display manager IP address
# xf -- X window system font server IP address
# yd -- NIS domain name
# ys -- NIS server IP address
# Tn -- generic option tag n
# T144 remote config file name (file name must be enclosed in "")
# Vn -- vendor specific information for vendor option tag of n
#
#----------------------------------------------------------------------------
# First example: simple network with no domains, no gateway, no subnets
#
# The first entry is the template for options common to all the
# X terminals.
#
#global.defaults:\
# bf=C2300B:\
# hd=/usr/lib/X11/700X/bin:\
# hn:\
# ht=ether:\
# vm=rfc1048:\
# T144="C2300B.cfg"
#
# Now the actual entries for the individual X terminals are listed.
#
#xterm1:\
# tc=global.defaults:\
# ha=08000903212F:\
# ip=190.40.101.22
#
#xterm2:\
# tc=global.defaults:\
# ha=0800090324AC:\
# ip=190.40.101.35
#
#----------------------------------------------------------------------------
# Second example: network with domains, subnets, and gateways
#
# The first entry is the template for options common to all the
# X terminals.
#
#----------------------------------------------------------------------------
#global.defaults:\
# bf=C2300B:\
# ds=15.2.112.119:\
# gw=15.8.19.100:\
# hd=/usr/lib/X11/700X/bin:\
# hn:\
# ht=ether:\
# sm=255.255.248.0:\
# vm=rfc1048:\
# T144="site.cfg"
#
# Now the actual entries for the individual X terminals are listed.
#
#xterm1.div.hp.com:\
# tc=global.defaults:\
# ha=08000903212F:\
# ip=15.8.19.22
#
# Note that template options can be individually overridden. Here we specify
# a gateway and a remote config file different than the template.
#
#xterm2.div.hp.com:\
# tc=global.defaults:\
# gw=15.8.19.3:\
# ha=0800090324AC:\
# ip=15.8.19.35:\
# T144="xterm2.cfg"
#
#----------------------------------------------------------------------------
#
# Third example: NFS diskless client entry:
#
# client1:\
# hn:\
# vm=rfc1048:\
# ht=ether:\
# ha=08000919BB78:\
# ip=15.1.55.234:\
# bf=/export/tftpboot/client1/stand/uxbootlf
#
#----------------------------------------------------------------------------
#
# Fourth example: bootp relay entries:
#
# Common relay entry.
#
# relay-default:\
# ht=ethernet:\
# bp=15.4.3.136 15.13.6.192:\
# th=2:\
# hp=1
#
# Relay entry for node2
#
# node2:\
# tc=relay-default:\
# ha=08000902CA00
#
# Group relay entry
#
# group-machines:\
# tc=relay-default:\
# ha=080009000000:\
# hm=080009000000
#
# Turn the relay off (block the relay) for the following machines.
#
# blocked-machines:\
# ht=ethernet:\
# ha=07000A000000:\
# hm=07000A000000
#
# Relay definition for all other machines.
#
# all:\
# tc=relay-default:\
# ha=000000000000:\
# hm=000000000000
#----------------------------------------------------------------------------

test:\
bf=C2300B:\
hd=/usr/lib/X11/700X/bin:\
hn:\
ht=ether:\
vm=rfc1048:\
ha=080009000000:\
ip=192.30.103.01







ignite-defaults:\
ht=ethernet:\
hn:\
bf=/opt/ignite/boot/nbp.efi:\
bs=48
System-IPF:\
tc=ignite-defaults:\
ha=00d009000000:\
ip=190.40.101.22:\
sm=255.255.248.0:\
gw=190.1.48.1:\
ds=190.1.48.11

[Alan Meyer_4]

Actually, that's exactly what mine looks like too.

What concerns me is that I am getting syslog messages that say bootp is booting.

[Fabio Ettore]

Hi Alan,

essentially bootp is a protocol to boot machine diskless. Here a good explaination about how bootp works:

http://docs.hp.com/en/B2355-90685/ch05s02.html

It is configured by /etc/inetd.conf by the following line:

bootps dgram udp wait root /usr/lbin/bootpd bootpd

Of course lines currently in /etc/bootptab comes for default and they are not significant. I think in your instance that line is without comment but if you don't want it just comment out.

inetd -c

to re-read /etc/inetd.conf file.

HTH.

Best regards,
Fabio

[Moderator edit: Removed the broken link. Please refer to https://support.hpe.com/]

[Bill Hassell]

The C2300B entry would be used to supply an Xwindow terminal with an IP address. See if 192.30.103.1 is even part of your current network, and that it really exists.

The Ignite entry is one way to supply an address to a machine which is being reinstalled over the network (not by tape). Since the gateway address is 192.1.48.1, I would assume that this used to be on a different network.

bootpd is a daemon that supplies network configuration information to clients on the same subnet, typically network printers, network appliances, or for Ignite/UX network installations. Note that since bootp uses unaddressed or broadcast packets, nothing outside this subnet would normally see this service.

The easiest way to test this is to turn off bootp service in inetd.conf and see if anything breaks. This assumes that you have a clear picture of what is attached to the current subnet.

[Alan Meyer_4]

The IP addresses specified in the bootptab file are non-existant addresses and not even close to our addressing scheme so I am gettin gthe picture that this is a default bootptab file supplied by HP.

No what concerns me though, is that periodically, I receive syslog messages that bootp is being rebooted. So from Fabio's post, can I assume that everyting that inetd is recycled, that bootp is rebooted?

[Michael Roberts_3]

Itanium based systems use bootp to request network boot/install services. The EFI boot protocol is PXE and sends the udp broadcast packets out on the bootp port. On PA-RISC systems you have a choice of using instl_bootd or bootp:

BCH> boot lan.10.10.10.10 install # instl_bootd

OR

BCH> boot lan.10.10.10.10 #bootp

The line:
bf=/opt/ignite/boot/nbp.efi:\
indicates that this is for booting an Itanium system.