Note:
Network Address Translation is not supported between the 5620 SAM
Auxiliary Call Trace Collector and the Managed Network.
The following two figures illustrates a deployment of 5620 SAM where NAT is used
between the 5620 SAM Server and the 5620 SAM Clients (GUIs, OSS or Client
Delegates). In
Figure 8-4, “5620 SAM Server deployment using NAT with IP Address
, SAM Clients on the private side and public side of the
NAT-Enabled Firewall must connect to the public IP address of the SAM Server. A
routing loopback from the SAM Server private IP address to the SAM Server public IP
address must be configured in this scenario as all SAM Clients must communicate to the
SAM Server through the SAM Server public IP address.
The 5620 SAM Auxiliary will need to be able to connect to the public IP address of the
5620 SAM server.
Figure 8-3 5620 SAM Server deployments with NAT between the Server and the
managed network
NAT-Enabled
Firewall
22664
Private
Network
Public
Network
5620 SAM Server
5620 SAM Auxiliary
5620 SAM Database
Managed
Network
Deploying the 5620 SAM with multiple network
interfaces/IP addresses
Using Network Address Translation
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
8-10
5620 SAM
3HE-09809-AAAG-TQZZA 13.0 R7
Issue 1
December 2015
