camping fails with network error 2

book

Article ID: 111181

calendar_today

Updated On:

Products

CA Automation Suite for Data Centers - Configuration Automation CA Client Automation - Asset Management CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Remote Control CA Client Automation - Asset Intelligence CA Client Automation - Desktop Migration Manager CA Client Automation - Patch Manager

Issue/Introduction

client not contacting DM, camping giving network error 2

Cause

unstable UDP traffic or a blockage of UDP port 4104

Environment

Any Supported ITCM / ITCA CA Client Automation environment

Resolution

Assuming you cannot simply unblock UDP port 4104 to resolve the issue, converting the agent to use TCP to communicate with the Scalability Server (SS) or Domain Manager (DM) should allow things to work properly*

1. CAF STOP ALL
2. CAMCLOSE & CAM START -c -l
3. Camsave persist (will generate cam.cfg in %cai_msq%)
4. CAM change disabled
5. CAM stop
6. CSAMPMUX STOP
7. Open cam.cfg with notepad
8. In *PATHS section add a line like ‘<SS/DM Name> Protocol = tcp port = 4105’
9. Save the file (make sure it stays cam.cfg and does not save as cam.cfg.txt)
10. CAM Change auto & CAM start -c -l
11. Test a camping and see if it works
12. If it does then start CAF and confirm CAF PING now works**

*Note: This is perfectly acceptable to do in small numbers, but if more than a few hundred agents need to be converted this way, the network issue needs to be addressed as TCP is a 'heavy' protocol and will cause a performance impact if too many systems try to use it all at once.

**If it does not, please open a support ticket to investigate further.