Agentless jobs support for Solaris 11 on SPARC/x86/x86_64 requires a workaround before a job can be submitted to this platform using Agentless.

Control-M/Agent 7.0/6.4.01/6.3.01 is not supported on Solaris 11 unless Control-M/Agent 7.0.00 Fix Pack 3 has been applied.

There are two issues that cause Solaris 11 compatibility issues with the Control-M/Agent:

1. Control-M/Agent Home Directory: The Control-M/Agent cannot run on Solaris 11 out of the box since Solaris 11 uses a symbolic link for /home to /export/home, where all home directories must reside.  Solaris 11 shells also handle symbolic links differently than in previous Solaris versions.  This causes the Control-M/Agent to fail on Solaris 11.

2. Remote Host/Agentless Ciphers: Solaris 11 changed the default list of supported cyphers for SSH communication.  As a result, Control-M/Agent cannot connect.  Jobs submitted to a Solaris 11 Remote Host (Agentless) will fail.  Enabling the the cyphers used in previous Solaris versions will resolve the problem.  The problem will occur no matter the version of the Control-M/Agent controlling the Remote Host. 

The following is a list of possible scenarios in which the problem may be observed:

1. When defining a new remote host on Solaris 11 from CCM and trying to ping it, the following error appears:
Check Remote Host state Failed.
Failed to ping Remote Host <host name>

CONTROL-M/Server is not authorized for this CONTROL-M/Agent.

2. When defining a new remote host on Solaris 11 it will be defined but it will stay unavailable because ping will fail.  Jobs are not able to be submitted as a result.

3. If the remote host was defined and available (as Solaris 10) and then upgraded the remote host to Solaris 11 and submitted a job, the job would be submitted and show the following errors in the <ctmagent_home>/proclog/AS debug log:

AS:Error details: ctn->err 'ERROR: Couldn't agree a client-to-server cipher (available: aes128-ctr,aes192-ctr,aes256-ctr,arcfour128,arcfour256,arcfour)', ctn->err_code=0
AS:notifyUnavToServer: Connection to RH failed. CTM Server must be notified

4. When submitting a job to a remote host that is not yet defined, it will go into 'Wait Node' status and the remote host will be in 'Discovering' status until the workaround is applied

CAR00045114 was created to track this problem. It is fixed in v7 FP3

Legacy ID:KA361183

Problem 1: Control-M/Agent Home Directory
Corrective Action Request (CAR) CAR00045114 was opened for this issue.  It is scheduled to be released in April 2012.  Until then, the Control-M/Agent can not be installed on Solaris 2011.  As a workaround, use the Solaris 11 system as a Remote Host/Agentless

Problem 2: Remote Host/Agentless Ciphers
Contact the local Unix System Administrator for assistance in performing the steps below as necessary.
1. Login into the Solaris 11 remote host as root
2. Open the file /etc/ssh/sshd_config for editing
3. Add the line: Ciphers aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc,blowfish-cbc
4. Recycle the ssh daemon using the command: /lib/svc/method/sshd restart
5. This will enable the ssh ciphers that are supported by the Control-M/Agent, and used in previous Solaris versions, allowing the Control-M/Agent to connect.

1. Control-M/Agent for UNIX and Microsoft Windows