Agent discovery - NAT IP Environment

[MADANRAJ SIVAGNANAM]

Hi All,

We have CA ITCM DM with physical IP and ITCM with Physical / NAT IP and there are no communication between these two. 

We have agents which has both physical / NAT IP and these agents are pointing to ITCM SS.. We could see multiple agents are discovered with Physical IP in DSM explorer and when we are trying to push software jobs to these agents via SS.. software are not getting deployed to the agents and we could see communication over discovered physical IP is not happening - this is our observation.. 

How ITCM SS can discover the agents (in NAT environment) only thru NAT IP instead of physical IP(local IP). How can we achieve this ?..

Gone thru CA docs about NAT configuration in cam.cfg of SS, but it doesn't work as expected.. May be i am doing wrong configuration.. Can anyone suggest / help me on this.

[James Surgent]

We have targets with NAT IP addresses as well.  Normal software delivery jobs will not function on them as designed since the Scalability Server tries to contact the real IP and not the NAT IP.  Our workaround for this is to use the CAF Scheduler in the Configuration Policy.  This can be found at DSM\Common Components\CAF\Scheduler\Run the USD Agent.  We configured our agents to run hourly.  Using this method, the Software Delivery Agent will check in every hour with the Scalability Server to see if a software job is present.  Once the agent establishes communications with the Scalability Server, the software jobs will run.

[MADANRAJ SIVAGNANAM]

Hi James,

Agent to contact SS for every hour - does it make any impact on network bandwidth / amagent scanning issue ?..

Also if UPM patch scheduled for an target say at 10:15 PM and agent communicates to SS at 10:00 PM followed by 11:00 PM, so on.. Does the software delivery will be skipped for an target actually scheduled at 10:15 PM and start executing software deployed at 11:00 PM or software delivery will be triggered for an agent at 10:15 PM itself.