What is the secure file on the system ?
Have you tried restartign the agent ?
In addition to what Rohit said, what do you see in the rscd.log? See the kb: https://kb.bmc.com/infocenter/index?page=content&id=KA348199&actp=search&viewlocale=en_US&searchid=1330511294843
When interacting with a BMC BladeLogic Server Automation Suite(BBSA) RSCD Agent, an "Error in TLS protocol: <servername>" error is encountered.
The RSCD log on the target agent contains the following:
05/03/11 13:56:11.109 WARN rscd - 184.108.40.206 25778 -1/-1 (???): ???: TLS setup failed for agent: Protocol mismatch. Check that client and server "secure" files match. Exiting and terminating connection.
05/03/11 17:43:01.716 WARN rscd - 220.127.116.11 24859 -1/-1 (???): ???: TLS setup failed for agent: Protocol mismatch. Check that client and server "secure" files match. Exiting and terminating connection.
As suggested by the error message, the secure file on both the nsh client or appserver and the target server should be examined to ensure the appropriate entries match.
In rare cases, this seems to be caused by a communication issue between the appserver/nsh client and the target server and the RSCD agent should be restarted and the operation reteste
What OS is the target?
How are you connecting from the console – live browse or nsh?
Does agentinfo work to the target ?
Having exactly the same error!
BL8.2 on Windows App Server - Target is W2k3 64bit - tested with 3 different versions of RSCD agent: 8.0, 8.1SP2 and 8.2. All give the same "SSL finish error.".
Have tried adding debug to RSCD loging, but got nothing useful, other than a "FIPS alread enabled" debug message.
Tried "Verify" via console, and various options from NSH - including agentinfo.
Appserver log only shows the NHS proxy SSO connection taking place successfully.
BL8.2 on Windows App Server
Target is W2k3 64bit
Tested with 3 different versions of RSCD agent: 8.0, 8.1SP2 and 8.2.
All give the same "SSL finish error." !!!
Try thisThis error can be caused by an empty <WINDIR>\rsc\certificate.pem or /usr/lib/rsc/certificate.pem left behind by a previous install
1. Stop RSCD Agent
2. Delete certificate.pem
3. Start Agent
4. Valid certificate is created automatically
There is no certificate.pem on this system
Did you try looking into the secure file on the agent as suggested above ?
What are its contents ?
The secure file matches all other servers that we're managing - default entries.
Seems like a candidate for Ticket.
There was a similar problem fixed with 8.1 SP1, for SSL finish error in fileserver agent