In the example scenario above, a Management Server and a Log Server manage system
components both at a company’s headquarters and at three branch offices.
• The SMC servers and the Central Firewall are at the “Headquarters” Location.
• The Remote Firewalls are all at the “Branch Office” Location.
In this scenario, contact addresses are typically needed as follows:
• The Firewall at the headquarters or an external router may provide the SMC servers external
IP addresses on the Internet. The external addresses of the SMC servers must be defined as
contact addresses for the “Branch Office” location, so that the components at the branch
offices can contact the servers across the Internet.
• The Branch Office Firewall or an external router may provide external addresses for the
system components at the branch office. The external IP addresses of the engines must be
defined as contact addresses for the “Headquarters” Location so that the Management
Server can contact the components.
• Alternatively, the external address of each component can be defined as a Default contact
address without adding a specific entry for “Headquarters” or “Branch Office”. The Default
contact address is used when a component does not have a specific contact address
definition for the contacting component’s Location. Note that the components must still be
divided into separate Locations for the contact address to be used.
If there are Management Clients used at any of the branch offices, each administrator must also
select “Branch Office” as their Location in the Management Client to be able to view logs from
the remote Log Server that is behind a NAT device