Ignite-UX release notes HP-UX 11iv1, HP-UX 11iv2 and HP-UX 11iv3 (5900-2307, April 2012)

Table 12 Supported Network Interfaces (continued)
NotesAmount of supportDriverType
fullfddiHPPB FDDI
2may workfddi3HSC/GSC FDDI
fullfddi4PCI FDDI
2,3may worktokenEISA token
2may worktoken2HPPB token
2may workpcitrPCI token
fullgelanGigabit
fulligelanGigabit
NOTE:
1. These interfaces are known to work correctly with DHCP.
2. The drivers for these interfaces are included in the INSTALL kernel, but have not been
tested due to lack of appropriate hardware in the test lab. They are "not known not to
work" at this point in time.
3. The EISA token-ring driver has been reported to work with Ignite-UX; however the correct
driver is not added to /stand/system automatically. See later in this section for a
workaround using mod_kernel.
• Ignite-UX attempts to use DHCP to get networking information at the beginning of the installation.
It times out in 30 seconds if no DHCP server responds. If you do not want Ignite-UX to attempt
to use DHCP, you can either:
◦ Turn off the use of DHCP in the "Advanced Options" menu accessible from the menu titled
"Welcome to Ignite-UX" which is displayed on the target console, just after the boot
process.
◦ If you are using an Ignite-UX server, you can specify the configuration file keyword:
disable_dhcp=true in either:
– The INSTALLFS file via the instl_adm command in which case DHCP will be
disabled for the entirety of the installation.
– In a configuration file such as /var/opt/ignite/config.local. In this case,
the initial Ignite-UX boot will attempt to use DHCP to get an address for use during
the installation, but the final system will have DHCP disabled via the DHCP_ENABLE
variable in /etc/rc.config.d/netconf.
• For environments where permanent IP address assignments are made ahead of time, they may
be done in /etc/bootptab and thus satisfy the DHCP request a client will make in order
to obtain networking information. See the appendix on configuring DHCP services in the
Ignite-UX Administration Guide at: http://www.hp.com/go/ignite-ux.
This may have an undesirable side effect in that the client will continue to contact that BOOTP
server each time it boots and will update any networking information that the server provides.
The reason this is undesirable is that DNS information cannot be provided in bootptab, and
thus the client will remove the DNS information from /etc/resolv.conf each time it boots.
This problem can be fixed by adding "disable_dhcp=true" to /var/opt/ignite/
config.local such that the client will use DHCP/BOOTP to get its initial networking
information, but will end up not using DHCP for on-going IP address management.
28 Known Problems and Workarounds