Registering a Domain Manager to the Enterprise Server fails with an error [CMM209411] in a NAT environment.

Products

• CA Client Automation - IT Client Manager
• CA Client Automation

Issue/Introduction

The following error may be observed while trying to register a Domain Manager to the Enterprise Server in a NAT environment:

SME_SPI_NETERROR The remote machne was not contactable. The peer messaging service may not be running or network errors were encountered.
[CMM2O9411]

 

Environment

Client Automation - All versions

Resolution

In order to register a Domain Manager to the Enterprise Manager do the following:

1. Edit the Routing section under cam.cfg on each server as below:
   
   *Routing
   
   forward 127.0.0.1=x.x.x.x(virtualip) x.x.x.x(same virtual ip)
   forward 127.0.0.1=y.y.y.y(realIp)
   forward x.x.x.x=y.y.y.y (forward virtual to real)
   
   Note: If cam.cfg does not exist run "camsave persist" to generate one in the %cai_msq% folder.
   
   
2. Open a CMD prompt run CAMCLOSE on the Enterprise Server and the Domain Manager. CAM will shut down and restart automatically.
   
   
3. Try CAMPING the DM from the ES and vice-versa.
   
   Syntax: CAMPING <IP Address>
   
   Note: The IP address refers to the public IP address and not the NATTED IP address.
   
   
4. If it still does not reply, do the following:
   
   FROM Enterprise Manager:
   
   
   1. Perform CAMSTAT and ensure that the name or IP address is listed
      
      
   2. camq -c -d -n <Hostname of the Domain Manager> (or IP, whichever is listed under HOSTS when running CAMSTAT on that box)
      
      
   3. Repeat this until the message 'no such cam queue' is returned.
   
   
   Note: Pipe out the above command to a text file for better readability.
   
   

FROM Domain Manager:

* Perform the same three steps as above but using the Enterprise info as outlined above.

• Try CAMPING in both directions to ensure that there is communication between the Enterprise Manager and the Domain Manager.

**IMPORTANT: Sometimes 'camsave persist' may fail due to timeout which in most cases happens on a Domain Manager that is busy. This would generate a partial CAM.CFG and break CAM upon its restart.

The solution is to open the partial CAM.CFG after disabling CAM from the system services, running CAMCLOSE and then modifying CAM.CFG to add the following under the partially completed PATHS section:

*ROUTING
*AUDIT
off

This will return CAM to normal functionality. Now you can set the CAM service back to manual and start CAM using 'CAM START -c'