Table Of Contents

Network Address Translation Support

Introducing NAT Support

Managing devices outside the NAT

Network Address Translation Support

---

This chapter introduces Network Address Transalation (NAT) support in Resource Manager Essentials and provides details of the tasks you need to perform to enable support.

Introducing NAT Support

Essentials can manage devices outside the NAT boundary using their IP addresses. As the NAT would translate between the public and private address for the Essentials servers, these devices will remain SNMP reachable. In Essentials, config fetch and image transfer commands can be performed using TFTP. Essentials uses SNMP to perform these operations. When Essentials issues an SNMP set command to a device, the device will initiate a TFTP transfer with the parameters provided through SNMP. In the SNMP command set if Essentials sets its private address, the TFTP transfer would fail as a device outside the NAT cannot reach private address of the RME servers.

The Figure 4-1 depicts a typical NAT scenario. In the figure, the Essentials server is within the NAT boundary. Essentials can manage the devices within the NAT boundary using their private addresses. When Essentials tries to manage devices outside the NAT boundary you need to enable support for NAT as described in the following section.

Figure 4-1 NAT Support

Managing devices outside the NAT

To manage devices outside the NAT boundary:

---

Step 1 Open a command prompt window.

Step 2 Navigate to $NMSROOT/www/classpath/com/cisco/nm/config/archive/

Step 3 Open the config.properties file in a text editor

Step 4 Modify the config.properties file:

USE_NAT= Yes

USER_FIELD=X

where X is 1 or 2 or 3 or 4.

The value X corresponds to the User Fields under Resource Manager Essentials > Administration > Inventory > Add Devices

---

Note While adding the device outside the NAT boundary, in addition to the Device Name field, provide the public address of the Essentials server in User Field X.

While adding the device within the NAT boundary, just provide the Device Name as before. You need not enter any value in the User Field.

---

---