HP Insight Control for Linux 6.1 Release Notes
2.4.2 Warning message: This system is already enabled
This message occurs when you try to apply a license to a system that is already enabled for the
product.
Corrective action: Deselect the system.
2.5 Discovery
This section contains notes about discovery.
2.5.1 Servers with NetXen gPXE NIC require DHCP modifications
A server with a NetXen gPXE 4.0.230 NIC will not accept an IP address from a Linux-based
dhcpd server, which causes problems with the discovery process.
Corrective action: Add the following lines to the /etc/dhcpd.conf file on the dhcpd server:
# gpxe options
option space gpxe;
option gpxe.no-pxedhcp code 176 = unsigned integer 8;
option gpxe-encap-opts code 175 = encapsulate gpxe;
option gpxe.priority code 1 = signed integer 8;
option gpxe.priority 1;
See the following website for more information:
http://etherboot.org
2.5.2 Bare metal discovery complains there is no DOS partition on the disk
During a bare-metal discovery on a new system with new disks, when the RAM disk loaded
onto the system, it reported that there was no valid DOS partition on the disk and subsequently
failed to complete the discovery process.
Corrective action: Remove the disk or disks temporarily and rerun the bare-metal discovery,
then replace the disks.
2.5.3 PXE bare-metal discovery might fail if system clocks differ significantly
If the system clock on the server you are discovering is significantly different from the system
clock on the CMS, the Bare metal Discovery Post Processing task might fail
intermittently during the Configure System to Boot from Local Disk operation with
a There are no MAC addresses registered for this system error message as
shown here:
Configuring system to boot from local disk.
There are no MAC addresses registered for this system.
Error while narrowing the mgmt processor node for specified server ({0}).
failed to get associated node for GUID 00000019bb28b16c000000030000000a
During a bare-metal discovery, Insight Control for Linux adjusts the system time on the server
being discovered to match the system time on the CMS. This might cause the NIC on the server
being discovered to go down momentarily if the time adjustment triggers a DHCP lease renewal.
If SIM is attempting to perform an Initial Data Collection task during this small window,
SIM might not be able to communicate with the server and, as a result, the task will not succeed.
Corrective action: You can either retry the bare-metal discovery operation or update the date
and time in the BIOS of the server being discovered to match the date and time of the CMS before
trying the operation.
2.6 Automatic firmware update note
This section contains a note with automatic firmware updates.
12 Notes and corrective actions