0 Replies Latest reply on Nov 19, 2014 11:00 AM by Joe Haley

    AIX NSH Script and BLPackage Jobs Failing with agent error: TLS setup failed for agent: Protocol mismatch. Check that client and server "secure" files match. Exiting and terminating connection

    Joe Haley

      Hi,

       

      I am having problems returning stdout with nexec commands such as "nexec $target uname" through an NSH script job.  The command returns no results for 243 AIX servers out of 1300 servers.  An empty BLPackage deploy job is also failing on the same servers.  I have compared the secure file with a successful server and a problem server and they match.  I am able to verify and NSH to the servers as well.

       

      BSA Version: 8.5.01.231

       

      Server info for problem and successful server:

      OS: AIX

      Patch Level: 6100-09

      RSCD: 8.5.0.469

       

       

       

      1. Command in script

      nexec $target uname

       

      2. Job Results

       

      3. RSCD Logs

      11/06/14 09:25:03.897 WARN     rscd -  ::ffff:10.136.134.103 2162906 -1/-1 (Not_available): (Not_available): TLS setup failed for agent: Protocol mismatch. Check tha
      t client and server "secure" files match. Exiting and terminating connection.
      11/06/14 09:25:03.920 INFO     rscd -  dchisxwsapp032 2162908 -1/-1 (Not_available): (Not_available): FIPS already enabled11/06/14 09:25:03.942 INFO     rscd -  ::ffff:10.136.134.103 2162908 0/0 (BLAdmins:i330245@ADHCSCINT.NET): agentinfo: agentinfo dchisxwsapp03211/06/14 09:25:03.997 INFO     rscd -  dchisxwsapp032 2162910 -1/-1 (Not_available): (Not_available): FIPS already enabled11/06/14 09:25:04.014 INFO     rscd -  ::ffff:10.136.134.103 2162910 0/0 (BLAdmins:i330245@ADHCSCINT.NET): agentinfo: agentinfo dchisxwsapp03211/06/14 09:25:04.059 INFO     rscd -  dchisxwsapp032 2162912 -1/-1 (Not_available): (Not_available): FIPS already enabled11/06/14 09:25:04.083 INFO     rscd -  ::ffff:10.136.134.103 2162912 0/0 (BLAdmins:i330245@ADHCSCINT.NET): nexec: nexec dchisxwsapp032 uname11/06/14 09:25:04.100 INFO1    rscd -  ::ffff:10.136.134.103 2162912 0/0 (BLAdmins:i330245@ADHCSCINT.NET): nexec: > 01010 Execute remote command: uname11/06/14 09:25:05.166 INFO     rscd -  dchisxwsapp032 14483492 -1/-1 (Not_available): (Not_available): FIPS already enabled11/06/14 09:25:05.180 INFO     rscd -  ::ffff:10.136.134.103 14483492 0/0 (BLAdmins:i330245@ADHCSCINT.NET): nexec: nexec dchisxwsapp032 uname
      11/06/14 09:25:05.192 INFO1    rscd -  ::ffff:10.136.134.103 14483492 0/0 (BLAdmins:i330245@ADHCSCINT.NET): nexec: > 01010 Execute remote command: uname

       

      Has anyone seen this behavior before?  Thanks in advance.

       

       

      ******************************************************************************************************************************************************

      This was resolved by deleting the /etc/rsc/certificate.pem file and running the command "/opt/bmc/bladelogic/NSH/sbin/agentctl restart" to restart the agent and re-create the file. The nscript job and deploy job were then able to complete successfuly.

      *******************************************************************************************************************************************************

       

      Message was edited by: Joe Haley