"start: Target /CH/BLx/SP/cli cannot be started" on Blades with ILOM 3.2.x and CMM with ILOM 3.1.x

Asset ID:	1-72-1968438.1
Update Date:	2017-05-26
Keywords:

Solution Type Problem Resolution Sure

Solution 1968438.1 : "start: Target /CH/BLx/SP/cli cannot be started" on Blades with ILOM 3.2.x and CMM with ILOM 3.1.x

Applies to:

SPARC T4-1B - Version All Versions and later
SPARC T3-1B - Version All Versions and later
SPARC T5-1B - Version All Versions and later
Information in this document applies to any platform.

Symptoms

When trying to connect from the CMM to the Blade's CLI, one of the following messages can appear:

-> start /CH/BL3/SP/cli
Are you sure you want to start /CH/BL3/SP/cli (y/n)? y
start: Can't use Single Sign On for /CH/BL3/SP/cli
start: Property /CH/BL3/SP/cli/user needs to be set in order to connect to the target SP
start: Failed to start /CH/BL3/SP/cli

Or simply:

-> start /CH/BL3/SP/cli
start: Target /CH/BL3/SP/cli cannot be started

Changes

This situation will appear when the ILOM on CMM is 3.1.x (or higher) and the Blade on which we want to start the CLI session has ILOM 3.2.x

The platforms that enabled luapi_proxy_feature (such as T4-1B) and when the ILOM is 3.1 on CMM, this is as designed.

These platforms that have ILOM revision 3.1.x or greater, will have this feature enabled by default.

Cause

The situation that the CLI cannot be started on a Blade from CMM is in fact not an issue. It is a matter of how CMM connects to a Blade in different ILOM revisions.

This is because we now have a mirror on CMM for a blade: "CMM /CH/BLx/" <-> "Blade /" and everything we can do from blade's CLI, now can be done from CMM, by adding prefix "/CH/BLx/".

To sum up the above, we can state the below:
- when CMM ILOM is 3.0.x the CLI from CMM to blade works with any ILOM revision on the blade (3.0.x and 3.2.x)
- when CMM ILOM is 3.1.x the CLI from CMM to blade works only when the blade's ILOM is 3.0.x
- when CMM ILOM is 3.1.x the CLI from CMM to blade does not work when the blade's ILOM is 3.2.x

Solution

With ILOM 3.1 on the CMM and 3.2 on the Blade, the "/CH/BLx/SP/cli" is not needed any more.

Accordingly, "start /CH/BLx/SP/cli" isn't supported in Blade's ILOM 3.2 because on blade "/SP/cli" doesn't have a "start" command.

Therefore, instead of connecting to the Blade to issue any kind of command:

-> start /CH/BL1/SP/cli
[BL1] -> show /HOST/status

We can now issue the command directly from CMM:

-> show /CH/BL1/HOST/status

To sum up, with ILOM 3.1 on CMM and 3.2 on Blade, now any action on the Blade can be done directly from the CMM simply by using the /CH/BLx/ prefix in target.

References

<BUG:16912865> - AFTER ILOM UPGRADE TO 3.2.1.1.B THE CLI FROM CMM DOES NOT WORK

Attachments

This solution has no attachment