HP Insight Control for Linux 6.0 Release Notes

Corrective action: HP suggests that you do not create the swap partition in an LVM volume,
and that you do not use the Partition Wizard for creating or renaming the swap partition.
2.12 Console management note
2.12.1 The CMF console command not working due to expired SSL certificate
The /etc/init.d/cmfd script creates the SSL certificates that are used when the console or
cmfmgr command want to communicate with cmfd.
The certificate files are: /opt/hptc/cmf/certs/cert.pem and /opt/hptc/cmf/.key/
privkey.pem.
Because no expiration date was given when the certificate was created, it defaults to 30 days. As
a result, this error occurs whenever you attempt to connect to cmfd:
ConnectToCMF: SSL_connect failed to node ares.usa.hp.com :
SSL_ERROR_SSL: A failure in the SSL library occurred, usually a protocol error.
Corrective action: Follow this procedure:
1. Modify the /etc/init.d/cmfd file to add -days 3650.
output=`echo -e "\n\n\n\n\n\n" |
openssl req -new -days 3650 -x509 -key $SSL_PRIVATE_KEY_FILE \
-out $SSL_CERTIFICATE_FILE 2>&1`
2. If the certificate files already exist, remove them:
# rm /opt/hptc/cmf/certs/cert.pem
# rm /opt/hptc/cmf/.key/privkey.pem
3. Restart the CMF service.
When service cmfd restart is run, it regenerates the files with the new expiration.
If hubs are being used, you need to run Options→IC-Linux→Configure Management
Services to push out the SSL certificate.
2.13 HP Insight control virtual machine management notes
Release notes specific to virtual machine management are described in the HP Insight Control
Release Notes, located at the following web address:
www.hp.com/go/insightcontrol/docs
2.13.1 ESX 3.x does not configure the network properly when NIC2 is used as boot
NIC
After installation, the ESX 3.x host cannot be accessed through the network when NIC2 is the
boot NIC; NIC1 was disabled in the onboard administrator (OA).
Corrective action: Use either of these methods to gain network connectivity:
Method A
This method updates the network configuration after installation.
1. Connect to the console of the installed system.
2. Press Alt-F1 to invoke a login session.
3. Log in as the root user.
4. Determine the MAC address of the boot NIC either from the DHCP configuration or using
the Network Configuration Editor.
Make a note of the MAC address.
5. Identify the Ethernet device for the Boot NIC as follows:
2.12 Console management note 23