Administer > Managing Overlapping IP Addresses in NAT Environments > Deploy NNMi in a Network Address Translation (NAT) Environment

Deploy NNMi in a Network Address Translation (NAT) Environment

Follow these steps to deploy NNMi in a NAT environment:

  1. Identify and make a list of each NAT domain in your network management environment.
  2. Determine which type of supported NAT is used within each NAT domain.
  3. Deploy each NNMi management server as required in relation to each NAT domain (inside or outside the NAT domain's internal IP address space). See special considerations:

    Static NAT Considerations

    Dynamic NAT and PAT Considerations

  4. Use the NNMiConfiguration > Discovery > Tenants workspace to define a unique Tenant name for each NAT domain.

    Note If using Global Network Management in your deployment, this name must be unique across all NNMi management servers (Regional Managers and the Global Manager).

  5. Decide which Nodes within each NAT domain that NNMi needs to monitor.
  6. Only for static NAT domains: Create any Overlapping Address Mappings to identify each Node's assigned NAT external/internal IP address pair. For the benefits of creating Overlapping Address Mappings, see Overlapping IP Address Mapping.

    Provide the following information:

    • Tenant name
    • External IP address
    • Internal IP address

    Use either the NNMi Configuration > Discovery > Overlapping Address Mappings workspace or the nnmloadipmappings.ovpl command line tool.

    See the NNMi online Help for details.

  7. Depending on where the NNMi management server is deployed in your network environment, a firewall might block NNMi from communicating with Nodes in a NAT domain whenNNMi uses the Node’s Internal Address. Therefore, for Configuration > Communication Configuration settings, use the appropriate Preferred Management Address setting (NAT’s External or Internal IP address).
  8. Verify Monitoring Configuration settings for NAT in your network environment:

  9. Configure a Discovery Seed for each Node.

    Note Assign any infrastructure device that interconnects multiple NAT domains (such as the NAT gateway router) to the Default Tenant.

    Use either the NNMiConfiguration > Discovery > Seeds workspace or the loadseeds.ovpl command line tool:

    • If the NNMi management server is inside the internal IP address space, configure Discovery Seeds using the Internal IP address:
      • Hostname/IP (use the Internal IP address)
      • Tenant name
    • If the NNMi management server is outside the internal IP address space, configure Discovery Seeds using the External IP address:
      • Hostname/IP (use the External IP address)
      • Tenant name

    See the NNMi online Help for details.

  10. Verify that NNMi Discovery found the Nodes you expected. If not, double-check your configurations (above).
  11. Verify that the NNMi settings meet your team's needs:

    • Fine tune the Security Group assignment of each Node to control which team members / customers can see each Node in the NNMi console. Use NNMi's Configuration > Security > Security Groups workspace.
    • Review the Monitoring Configuration settings that apply to these Nodes and fine-tune as necessary. Use the NNMi Configuration > Monitoring > Monitoring Configuration workspace.
  12. Verify that the connections between Nodes appear on NNMi maps as expected. If not:

    • Verify that both Nodes involved in the connection have proper Tenant assignments (Default Tenant or other tenant).
    • Verify that your Configuration > Discovery Configuration’s Subnet Connection Rules tab settings are correct.
    • To force NNMi to add connections that are not automatically found, use the nnmconnedit.ovpl command line tool. See theNNMi online Help > NNMi Documentation Library > Reference Pages for details.

  13. Review the SNMP trap forwarding rules configured in each Node’s SNMP Agent to include the appropriateNNMi management server’s IP address.
  14. For static NAT domains only: Configure the SNMP Agent on each static NAT Node to ensure that the interface associated with the NNMi Overlapping Address Mappings Internal Address sources all traps that are sent to theNNMi management server.
  15. If your network environment includes SNMPv1, make the appropriate required changes to the NNMi configuration. See Traps and Static NAT.