Using Ignite-UX with Integrity VM

Figure 1 - Entries in /etc/bootptab to accommodate Integrity VM clients
IADEF:\
ht=ethernet:\
hn:\
bf=/opt/ignite/boot/nbp.efi:\
bs=48:\
bp=75.99.87.15:\
sm=255.255.248.0:\
gw=75.99.87.254:\
ds=75.99.52.11:\
vm=rfc1048:
myvm01:tc=IADEF:ip=75.99.87.205:ha=86abc85d751a:
myvm02:tc=IADEF:ip=75.99.87.38:ha=86abc85d7509:
Setting up a DHCP environment
If Ignite-UX clients do not have static IP addresses assigned to them, as in a DHCP environment, then client-specific entries in
/etc/bootptab are not practical. To accommodate such anonymous clients, HP-UX 11i v2 provides an option for DHCP
configuration that enables the device_pool_group feature to be used. To use this feature, set up an entry in the
/etc/dhcptab configuration file similar to that in
Figure 2. The attributes of the entry in
Figure 2 are described as follows:
• dhcp_device_group - This starts a DHCP device pool group that provides a pool of IP addresses to a set of clients that
all have the same class-id in their boot messages.
• class-id - All IPF clients send boot messages that contain a class id with a 32-character string:
PXEClient:Arch:00002:UNDI:xxxyyy. Where "xxxyyy" are major and minor numbers for the Universal Network
Device Interface revision. This line tells bootpd to respond only to clients that match a string that starts with
PXEClient:Arch:00002, that is, IPF clients
• re - This is a binary option that tells bootpd to perform a regular expression match of the class-id rather than a default
literal match. This is a new 11.23 option.
• ncid - This is a binary option that tells bootpd to not send back a class-id on the message responses. This option is
necessary because bootpd does not support the full PXE protocol. This is a new 11.23 option.
• lease-time - This option indicates the time in seconds for leases given for IP addresses.
• addr-pool-start-address – Identifies the start of a range of IP addresses offered to clients.
• addr-pool-last-address – Identifies the end of a range of IP addresses offered to clients.
• subnet-mask – The subnet mask used by clients.
• bf – The EFI network boot program to use.
After this entry is made in the /etc/dhcptab file on the Ignite-UX server, restart the bootpd daemon. It is typically started
by inetd and you can verify this by examining the /etc/inetd.conf configuration file. If so, kill any instance of
bootpd and inetd -c will restart bootpd for you.