HP Lights-Out 100 Remote Management - Manual (Page 51)

where:
• <URI> is the //tftpserver IP/path/filename to be downloaded.
• tftpserver is the URL or IP address of the TFTP server containing the certificate.
• Path is the path of the file relative to the TFTP server root.
• filename is the file name of the certificate file (server_cacert.pem in this example).
After you issue the load command to upload and install the certificate, reset the BMC by entering
the following command:
rest map 1
LO100 checks the validity of the key/certificate pair after you reset the BMC.
You can also find these commands in /map1/firmware directory.
To install a private key, log in to LO100 as administrator through the CLP interface and issue
the load command to upload and install the certificate. For example:
load -source <URI> -oemhpfiletype key
where:
• <URI> is the //tftpserver IP/path/filename to be downloaded.
• tftpserver is the URL or IP address of the TFTP server containing the private key file.
• Path is the path of the file relative to the TFTP server root.
• filename is the file name of the private key file (server_privkey.pem in this example).
After you issue the load command to upload and install the certificate, reset the BMC by entering
the following command:
reset map 1
LO100 checks the validity of the key/certificate pair after you reset the BMC.
You can also find these commands in /map1/firmware directory.
To successfully establish SSH/SSL connections after loading a key or certificate through the CLI
or the GUI, and after you click Apply, you must reset the BMC by choosing either of the following:
• Issuing the following command from the CLI (/./-> cd map1 a"reset map 1")
• Physically pulling AUX power
HP Systems Insight Manager support
HP Systems Insight Manager discovers LO100 to identify and launch LO100 and its license
manager to retrieve or deploy LO100. See your HP Systems Insight Manager user guide for more
information on using HP Systems Insight Manager with LO100.
Resolving character and line feed issues
HP recommends using similar operating systems to communicate between the CMS and your
applications or workstations. For example, if you are running a Linux CMS, run Linux on your
workstations, and use a Linux telnet client. Likewise, if you are running a Windows CMS, run
Windows on your workstations, and use a Windows Telnet client.
If you run multiple operating systems in your environment, an application limitation issue might
occur. For example, running Linux on your servers and using a Windows Telnet client or PuTTY
might cause an end of line character issue. If you experience issues, do one the following:
• For a Windows Telnet client to Linux console redirection configuration, make sure Windows
Telnet sends a CR for the line feed. To set CR, use the following command for Windows
Telnet:
unset crlf
HP Systems Insight Manager support 51