CA Client Automation

  • 1.  Changing CA Client Automation 12.9 Protocol

    Posted Oct 02, 2015 10:58 AM

    Good morning to all.

    In our company we have identified that when launching packages using the DSM Explorer, some stations did not get them with the distribution.

    The identified solution is to change the protocol manually " camsave persist" command udp tcp = 4104 = 4105

    When this procedure is done , the distribution goes smoothly .

    What inconvenience could occur if we migrate the entire 12.9 CLA platform this protocol?

    Can I get you help or request a case to provide me more information?

    I will be attentive to your comments.

    Thank you.

    Jose Dominguez.



  • 2.  Re: Changing CA Client Automation 12.9 Protocol
    Best Answer

    Broadcom Employee
    Posted Oct 02, 2015 11:52 AM

    Changing a few machines to TCP has always been an acceptable solution to an issue similar to yours.

     

    BUT by default you usually don't want to change all machines to TCP, since that causes a traffic,

    this will actually cause CAM performance issues.

     

    I would only change the machines that have issues.



  • 3.  Re: Changing CA Client Automation 12.9 Protocol

    Broadcom Employee
    Posted Oct 05, 2015 06:37 AM

    Hi

     

    I agree with Gordon

     

    TCP has a higher network overhead than UDP and if you switch the entire estate to TCP this is likely to cause a CAM performance issue. Use TCP on problematic stations whilst you investigate the issue with UDP to these stations, maybe there is an MTU issue that you can resolve by changing the cam fragment size see http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec511460.aspx

     

    regards

    Rich



  • 4.  Re: Changing CA Client Automation 12.9 Protocol

    Posted Oct 05, 2015 07:57 AM

    Agreed