NAT Behind Nodes

GigaVUE-FM can manage nodes and clusters that use Network Address Translation (NAT) for IP address conversion. GigaVUE-FM identifies the nodes behind NAT based on the Node Behind NAT option which you must select at the time of adding the nodes. Refer to Add Nodes Manually.

Prerequisites

In order for GigaVUE-FM to manage the devices and clusters that are behind NAT:

■

GigaVUE-FM must be running software version 5.7 or higher.

■

Devices must be running software version 5.3 or higher.

■

Devices must be assigned NAT IP and Fully Qualified Domain Names.

■

Domain name server and default search domain must be configured in GigaVUE-FM.

Add NAT Behind Nodes

When managing clusters behind NAT, GigaVUE-FM does not know the NAT IP of the members in the cluster. You cannot also configure the NAT IP of the members. GigaVUE-FM only identifies the private IP of the nodes through the API. Therefore, for device specific operation, GigaVUE-FM uses host names to connect to the nodes. You must therefore configure the domain name server and default search domain in GigaVUE-FM. Refer to the “NAT Configuration” section in the GigaVUE Administration Guide. If you do not configure the domain name server and search domains, then it may lead to failure in node specific operations.

Note:  When adding nodes, ensure the following:

■

Select the Node behind NAT option for a node that is behind NAT.

■

Do not select the Node behind NAT option for a normal node.

If you fail to perform the above operations, then you may experience inconsistency in managing the nodes.

Refer to the “NAT Configuration” section in the GigaVUE Administration Guide for details.

Limitations

Though GigaVUE-FM can manage nodes behind NAT from software version 5.3, SNMP traps, Syslog messages and event notifications will not be pushed from the node to GigaVUE-FM. This is because GigaVUE-FM registers its eth0 address as target address on the nodes to receive the notifications but the nodes behind NAT will not be able to reach GigaVUE-FM by its eth0 IP. These limitations are not applicable for node version 5.7 and above.

Note:  Refer to the “NAT Configuration” section in the GigaVUE Administration Guide for details.