Enable agent for NAT gateway devices in private address space

When the NAT gateway is not in the public address space, you can enable the NATGateway agent to correct the potential problem of incorrect connectivity.

About this task

The discovery assumes that the management interface of the NAT gateway is in public address space. If this is not the case, Network Manager cannot identify the address space of interfaces on the NAT gateway device, which might result in incorrect connectivity. For example, when a VPN is used to access the management interface, the NAT gateway management interface is not in the public address space.

The NATGateway agent enables Network Manager to determine whether a given interface on a NAT gateway device is on the public or private side of the NAT gateway, and thereby correctly resolve device connectivity.

To overcome this problem, activate the NATGateway agent and provide Network Manager with a mapping file, NATGateways.txt. In this file, provide a list of all NAT gateway devices together with the interfaces on each device and a field to indicate whether the interface is on the public or private side of the NAT gateway.

This agent works in conjunction with the NATGatewayRetProcessing.stch stitcher and with the NATGateways.txt file in NCHOME/precision/etc

Table 1 provides the format of the NATGateways.txt file by showing an example of the content of this file. Fields in this text file must be separated by tabs.

Table 1. Format of NATGateways.txt file
Base name	Inside or outside	Interface IP address
1.1.1.4	outside	172.16.4.10
1.1.1.4	inside	10.52.2.10
sca_T1ukP_16	outside	192.168.36.93
sca_T1ukP_16	outside	192.168.36.98