# NOTE: This table is only for booting PA-RISC clients.  For booting IPF clients
#       you have to edit /etc/bootptab.  Please see the example in
#       /etc/bootptab for instruction how to add entries.
#
# /etc/opt/ignite/instl_boottab:  Used by /opt/ignite/lbin/instl_bootd(1M)
#
# This file contains a list of IP addresses to be reserved for booting
# clients during an the HP-UX install process.  These addresses are
# used only during the boot period and not at any other time, thus
# they are temporary.
#
# A list of (one or more) IP addresses should be entered below, one
# per line, beginning in the first column.  The IP addresses will be
# cycled through for each consecutive client that boots.  If many
# clients are booting at the same time, it may be necessary for you to
# enter several addresses to keep the server from denying any client
# access.
#
# When instl_bootd allocates an IP address to a client, it will
# change the line to include the clients network hardware address and
# the date/time that it booted (fields 2 and 3).  This data is for use
# by instl_bootd when determining which address to use next time.
#
# File Syntax:
#
#    - Comments can be included as appropriate.  They are denoted
#      by the '#' character and end-of-line.  They can appear at the
#      end of an IP address line, or on a line by themselves.  Blank
#      lines are also allowed.
#
#   Non-comment lines can contain 1 or 4 fields.  Fields are separated
#   by the ":" (colon) character.  Each fields is described as follows:
#
#       Field 1: Must start in the first column, and contain an IP
#                address in "dot" notation.  This field is not optional.
#
#       Field 2: Can be empty, or can specify the LAN hardware address
#                of the system that last used the entry, or (depending
#                on field 4), the only system that is allowed to use it.
#                This field is updated automatically by instl_bootd.
#
#       Field 3: Can be empty, or can specify the date/time of the last
#                time that the IP address was used.  This field is also
#                updated by instl_bootd.  It should be left empty when
#                adding new entries.
#
#       Field 4: Can be empty, or the keyword "reserve" can be
#                specified to prevent an IP from being allocated to
#                any client not matching the hardware address value in
#                field 2.  If field 2 is empty ("::"), then when the
#                entry is issued to a client, that entry/IP-Address
#                will become reserved for that system and will not be
#                allocated to any other systems.
#
# Example: (lines are intentionally commented out)
# 15.1.54.125                             # IP address usable by any client
# 15.1.54.126:080009123456:19960116132331 # Entry usable by all (used already)
# 15.1.54.127:::reserve                   # Reserve this entry once used.
# 15.1.54.138:080009123457::reserve       # Reserve an IP-Addr for specific host
#
10.233.7.241:0x0013217C54EB:20060125174012:
10.233.7.240:::
10.233.7.75:::
10.233.16.60:::
10.233.16.61:::
10.233.16.62:::
10.233.16.63:::
10.233.16.64:::
10.233.16.65:::
10.233.16.66:::
10.233.16.67:::
10.233.16.68:::
10.233.16.69:::
10.233.16.70:::
10.233.16.71:::
10.233.16.72:::
10.233.16.73:::
10.233.16.74:::
10.233.16.75:::
10.233.16.76:::
10.233.16.77:::
10.233.16.78:::
10.233.16.79:::
10.233.16.80:::
10.233.16.81:::
10.233.16.82:::
10.233.16.83:::
10.233.16.84:::
10.233.16.85:::
10.233.16.86:::
10.233.16.87:::
10.233.16.88:::
10.233.16.89:::
10.233.16.89:::
10.233.16.90:::
10.233.16.91:::
10.233.16.92:::
10.233.16.93:::
10.233.16.94:::
10.233.16.95:::