Administer > Managing Overlapping IP Addresses in NAT Environments > Dynamic NAT and PAT Considerations

Dynamic NAT and PAT Considerations

Each dynamic NAT or PAT domain requires its own NNMi management server. The NNMi management server must participate in a Global Network Management environment as a Regional Manager.

The NNMi administrator creates a Tenant definition to identify each NAT domain. Tenants must be unique within the entire NNMi Global Network Management configuration.

See the following two examples of a dynamic NAT configuration.

Note If a Regional Manager is located behind a NAT firewall, its external (public) address must be static.

Example Dynamic NAT Configurations

See the following figure for an example of a Global Network Management configuration within a NAT environment.

Example Global Network Management Configuration within a NAT Environment

Devices that belong to the default tenant can have Layer 2 connections to any device in any tenant. Devices within any tenant other than default tenant can have Layer 2 connections only to devices within the same tenant or the default tenant.

Tip Assign any infrastructure device that interconnects multiple NAT domains (such as the NAT gateway) to the default tenant. This ensures that NNMi displays the Layer 2 connections your workgroup (and customers) need to see.

Devices within the default Security Group are visible from all views. To control access to a device, assign that device to a Security Group other than default Security Group.