How to Disable Firewall Proxies in CAM

Products

CA Client Automation - IT Client Manager CA Client Automation

Issue/Introduction

Camping fails, CA Client Automation performance is poor, reboot or recycle services temporarily relieves symptoms.

Problem is due to name resolution issues or a firewall IP address being passed to CAM instead of the host's IP Address.

This results in CAM getting stuck in a loop.

For example, in %cai_msq%\logs, the log file dg00* log shows the following:

queue 192.0.2.10:4104 reversed identity with proxy 192.0.2.12:4104
queue 192.0.2.12:4104 reversed identity with proxy 192.0.2.12:4104

and this repeats over and over.

This problem is most often seen on Domain Managers and Scalability Servers.

Environment

Client Automation - All Versions

Resolution

Configure CAM to disable proxies using the procedure below:

1. CAF STOP

2. camclose & cam start -c -l

3. Browse to the %cai_msq% directory and see if there is a CAM.CFG file.

If so, skip to step 5. Otherwise:

4. From a cmd prompt issue 'camsave config' and a file called 'CAM.save' should get created in the CAM directory.

Rename that file to cam.cfg

Note: That the command may fail because of the state CAM is in, but the file should still get created.

If it does not or is blank, download and use the sample attached in cam.zip.

5. Open the cam.cfg, and in the *config section add the following parameter:

disable_proxies = yes

6. Clear out ALL entries that get created under the *PATHS and *ROUTING sections

7. Save the file and issue the commands (the new cam.cfg won't be used until CAM is recycled):

camclose & cam start -c -l

8. CAF START

Then see if overall CAM and CAF performance improves.

Additional Information

There are some additional situations where using the setting disable_proxies=yes in the cam.cfg can help:

1. Agent collection issues - there has been issues that after changing the setting to disable_proxies=yes

agent can help eliminate network traffic trying to communicate to non intended addresses.

2. DSM Explorer performance issues - if this issue is occurring it can slow down the loading of DSM Explorer

and retrieving objects from mdb

3. System Performance Issues - can cause issues related to excessive CPU and or Memory issues

NOTE:

You should not set disable_proxies in the cam.cfg if you have any entries in the routing section of the cam.cfg

An example of when not to set disable_proxies

*routing

forward 127.0.0.1=<IP Address to be used> <IP Address to be used>

If you do set that it will ignore the section in the *Routing section and can cause issues with cam communication.

Attachments

1564164874962__cam.zip get_app