13.5 Considerations on static NAT

If each instance is configured as a unique tenant, one NNMi management server can monitor any number of static NAT instances. For details about tenants, see 14. NNMi Security and Multi-Tenancy and Configure Tenants in NNMi Help.

The following figure shows an example of a static NAT configuration.

Figure 13‒1: Example of a static NAT configuration

The node belonging to the default tenant can establish a Layer-2 connection with any of the nodes in any of the tenants. A node in a non-default tenant can establish a Layer 2 connection only with the devices in the same tenant or the default tenant.

Subnets are specific to tenants (a subnet does not span multiple tenants). The benefit of subnets is that the same subnet can be used by different tenants.

A router redundancy group (RRG) cannot span multiple tenants.

Allocate all infrastructure devices that interconnect to multiple NAT domains (such as NAT gateways) in the default tenant. This ensures that the Layer 2 connections that work groups (and clients) must check are displayed in NNMi.

The devices in the default security group are displayed in all views. To control access to a device, assign that device to a security group that is not the default security group.

Organization of this section

• 13.5.1 Hardware and software requirements for static NAT

• 13.5.2 Communication using static NAT

• 13.5.3 Discovery and static NAT

• 13.5.4 Monitoring configuration for static NAT

• 13.5.5 Traps and static NAT

• 13.5.6 Subnets and static NAT

• 13.5.7 Global network management and static NAT

To Page Top