Does Control-M support BigIP Load Balancer?

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:

    BMC Control-M/Enterprise Manager



    QUESTION:

    Question:
    - Does Control-M support loading-balancing router like BigIP ?

     




     


    ANSWER:

     

    Legacy ID:KA419369

      

    Solution:

      

    -  CAR00041978 Name: Network Load-Balancer Functionality and Benefits -
      " Control-M now supports network load-balancing routers (for example, BigIP), where the job is submitted to a virtual hostname and then routed to one of the nodes participating in the load balancing group.The following - The above CAR was added to Control-M Server 800 Fix Pack 1
      http://documents.bmc.com/supportu/documents/02/89/440289/440289.pdf
    - To enable the feature the Control-M/EM system parameter EnableLoadBalancerRouter must be set to true, and the CMS (Configuration Manager Server) must be recycled.
       Prerequisites:
       Install the latest Fix Pack available for Control-M EM V8
       Install the latest Fix Pack available for Control-M Server V8
       Inbstall the latest Fix Pack available for Control-M Agent V8
    - For more information, see the Control-M Workload Automation Administrator Guide.

      

    Additional Information:
    Load balancer limitations
    1.1.1 Selective SSL mode is possible only as long as all agents behind the load balancer are configured with the same mode (all SSL or all TCP).
    1.1.2 The load balancer agents should not work in persistent mode because it defeats the purpose of having a load balancer.
    1.1.3 Node limits won't be supported for the load balancer and for the agents connected to the load balancer.
    1.1.4 Multi agent won't be supported for the load balancer agents ( Multi agent is the ability to submit\order a job to all agents in a node group).
    1.1.5 Remote hosts won't be supported for the load balancer agents.
    1.1.6 Control Modules accounts availability won't be supported for the load balancer agents. 
    1.1.7 All agents connected through a given LB must have the same Control-M communication protocol version (higher or equal to 10 - V8FP1 protocol version).
    1.1.8 All agents connected through a given LB must have the same CMs on each agent. The reason is that we do not know to which agent job will be submitted.
    1.1.9 All agents connected through a given LB must have the same owner.
    1.1.10 Agent logical name should be the same name on server side. In other word, run ctmagcfg at agents to configure the agent logical name to same name(even though their physical hostnames are different).
    1.1.11 Customer should define all of the load balancer agents through the Control-M Configuration Manager.
    1.1.12 CPU@ won't be supported for the load balancer agents (CPU@  is default Control-M Server load balancing mechanism)
    1.1.13 The system autoedit %%nodeid won't be supported for the load balancer agents.
    1.1.14 Load balancer cannot be part of a node group.
    1.1.15 Load balancer and agent cannot have the same name.
    1.1.16 Control-M/Agents machines, Control-M/Server, and load balancer machine should be pingable (can ping from server to LB machine and from agent to LB machine).

     

      
    Related Products:  
       
    1. Control-M/Server for UNIX and Microsoft Windows
    2.  
    3. Control-M/Agent for UNIX and Microsoft Windows
    4.  
    5. Control-M/Enterprise Manager

     


    Article Number:

    000029899


    Article Type:

    FAQ/Procedural



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