Control-M/Server Configuration Agent is displayed as "unavailable" on Control-M Configuration Manager (CCM) GUI

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Control-M/Enterprise Manager


    COMPONENT:

    Control-M/Enterprise Manager


    APPLIES TO:

    All versions of Control-M/Enterprise Manager



    PROBLEM:

     

      - One or more Control-M Servers defined in the Control-M/Enterprise Manager Control-M Configuration Manager (CCM) GUI display as "unavailable" even though the Configuration Agent or "CA" process is active on the datacenter.   
    - The error messages in the Control-M Server proclog directory for the CA* files repeat these messages: 
      
      0922 16:09:53.05 CA: cm_bca_accept - cm_bca_accept_first_time failed for fd 17  
    0922 16:09:53.05 CA: CTM6646 -> CM_open_session_FULL_DUPLEX: Unauthorized Client. cm_bca_accept failed.  
    0922 16:09:53.05 CA: CTM6647 -> CM_open_session_FULL_DUPLEX: Unable to terminate SSL session -1  
    0922 16:09:53.05 CA: CTM6710 -> AAComm::receiveMsg : Communication is down 
      
        
      
      Cycling the CA process does not remedy the communication problem. 
       
        

     


    CAUSE:

    Control-M/Enterprise Manager System Parameter "CmsCommMode" is not set correctly


    SOLUTION:

     

    - The solution is to set the Control-M/Enterprise Manager  System Parameter "CmsCommMode" from a default value of "tcp" to "auto" so it refreshes automatically. 
    -  In the  Control-M Configuration Manager (CCM) GUI, select Tools-> System Parameters, Control-M EM System Parameters and update the parameter. 
    - Cycle the Control-M EM Configuration Agent and Control-M Configuration Server processes for the change to take effect.

      
      In order to debug the problem, the following diagnostics can be set: 
      
     
    1. In the CONTROL-M/Server account, raise the CA debug level by running the command "dbglvl CA 4 0" 
      
      2. In the CONTROL-M/EM account, raise the CMS debug level as follows: 
      
      a. Edit the file <EM_HOME>/ini/CMS_DiagLvls.ini  
    b. Change the parameter "MinimumDbgLvl" from "MinimumDbgLvl 2 4" to "MinimumDbgLvl 7 7"  
    c. Restart the CMS by using the "root_menu" or by running the command "stop_CMS" and "start_CMS" 
      
      3. In the CONTROL-M/EM account, raise the CMSGATE debug level by running the following commands: 
      
            ecs ctl -U <EM DB user> -P <EM db password> -C CMS-GTW -name CMSGATE -cmdstr "TRACE_LINK_CTM on"  
          ecs ctl -U <EM DB user> -P <EM db password> -C CMS-GTW -name CMSGATE -cmdstr "TRACE_CTM on" 
      
      4. In the CONTROL-M/EM Client machine (where you run the CCM), raise the debug level of the CCM as follows: 
      
      a. Edit the file <EM_HOME>/ini/ccm_DiagLvls.ini  
    b. Change the parameter "MinimumDbgLvl" from "MinimumDbgLvl 2 4" to "MinimumDbgLvl 7 7"  
    c. Edit the file <EM_HOME>/ini/ccm_DiagLvls.nlog  
    d. Move the line 
      
      "<logger name="*.*" appendTo="file_dbg"     minLevel="Debug" final="true"/>" 
      
      above the line 
      
      "<logger name="*.*" appendTo="file_dbg"     minLevel="Error" final="true"/>" 
      
      e. Restart the CCM 
      
     
    The logs we would like to receive after enabling the debug levels and recreating the problem are: 
      
      1. From the CONTROL-M/Server account, the files <CTM_HOME>/CTM_server/proclog/CA*  
    2. From the CONTROL-M/EM account, the files <EM_HOME>/log/CMS*   (this will include the CMS_diag*, cmsg_log*, CMS_xml_dump*)  
    3. From the CONTROL-M/EM Client machine, the files <EM_HOME>/log/ccm* 
      
      Please reduce the debug levels of all components after reproducing the problem: 
      
      1. In the CONTROL-M/Server account, run the command "dbglvl CA 0 0"  
    2. In the CONTROL-M/EM account, edit the file "<EM_HOME>/ini/CMS_DiagLvls.ini" and set back the "MinimumDbgLvl" parameter to "MinimumDbgLvl 2 4"  
    3. Restart the CMS by using the "root_menu" or by running the command "stop_CMS" and "start_CMS"  
    4. In the CONTROL-M/EM account, run the following commands to stop CMSGATE debug: 
      
            ecs ctl -U <EM DB user> -P <EM db password> -C CMS-GTW -name CMSGATE -cmdstr "TRACE_LINK_CTM off"  
          ecs ctl -U <EM DB user> -P <EM db password> -C CMS-GTW -name CMSGATE -cmdstr "TRACE_CTM off" 
      
      5. In the CONTROL-M/EM Client machine (where you run the CCM), edit the file "<EM_HOME>/ini/ccm_DiagLvls.ini" and set back the "MinimumDbgLvl" parameter to "MinimumDbgLvl 2 4"  
    6. In the CONTROL-M/EM Client machine, edit the file <EM_HOME>/ini/ccm_DiagLvls.nlog and move the line 
      
      "<logger name="*.*" appendTo="file_dbg"     minLevel="Debug" final="true"/>" 
      
      after the line 
      
      "<logger name="*.*" appendTo="file_dbg"     minLevel="Error" final="true"/>" 
      
        
      
        

     


    Article Number:

    000094175


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles