Making SSH Connections to C7000 Blade ILO2s

From TDiWiki

Using the Console type SSH with Public Key Encryption for C7000 Blade iLO2’s

This example is based on a ConsoleWorks server running on the Linux platform.

Specific differences for ConsoleWorks running on OpenVMS may be found here:

http://wiki.tditx.com/index.php/Making_SSH_Connections_to_ILOs

Prerequisites:

SSH on the Blades must be enabled.

SSH keys may be generated on the ConsoleWorks server using the >Admin >Server Configuration >SSH Keys feature..

Once the key is created, you will copy it and paste it into a text file and change the account name at the end of the key to match the account that the C7000 OA uses to login to the Blades.

For this example that account name is Administrator. The capital A does matter. This is not necessarily the account used by users to log into the OA itself.

ConsoleWorks screen where keys are generated

Copy the contents to Clipboard. Windows may prompt you for permission. Please allow it.

Paste the contents to Notepad or some other Text editor and change the name to the Account that the OA uses to log into your blades.

For this example that account is Administrator

Key has been changed to reflect the correct login account.

The next step is to log into the Blade System you’ll be working on, and click into the Blade you need to import this certificate into.

Note: If the host system you are using is different than your Desktop, for example you have to RDP to another Windows machine to get connected to the Blade Chassis, you’ll need to make a copy of the key file on that system so that you can “Browse” to the file.

Select the Blade of interest from the HP Bladesystem Onboard Administrator by clicking on its IP address.

This is the IP address you’ll be using in ConsoleWorks.

Click your way to Administration, Security

“Browse” to the location and key file you created in the previous steps. For this example I created BladeKeys.txt.

Click Authorize Key

Example of successful import

Repeat this import process for each Blade that will be managed and monitored in ConsoleWorks.

The next step is to create the Consoles in ConsoleWorks!

We will assume that you know how to “Add Consoles” and skip to the relevant information for this exercise. Creating a SSH with Public Key Encryption Console type.

For this example, I’ve named the Console Blade_5 to match the blade example above.

The IP address matches the above Blade

ConsoleWorks suggests port 22, but you need to actually fill the port in.

ConsoleWorks suggests a Username of root. Change this to match the login name we used in the Cert. This example uses Administrator

No password required. Leave fields blank.

For the Key field select the name of the Key you generated at the beginning of this exercise.

Add the console to any Groups, Scans, Profile Permissions, Expect-Lite scripts as needed per usual.

Click Save.

Go to the View Consoles Window and test connectivity.