This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Monitoring multiple nodes on a remote site

Hi everyone

We have NPM server on datacenter & most of nodes placed on branch office.

Existing Practice 1

For our existing practice, we have a double NAT. (1st on branch office firewall, 2nd on datacenter firewall because orion web not allow different node with same IP)

Example:

NPM IP: 192.168.0.1/16

Branch Public IP: 2.2.2.2

Monitored Nodes Address: 192.168.0.2:161, 192.168.0.3:161 (Virtual IP on datacenter)

Datacenter 1st NAT: 192.168.0.2:161 -> 2.2.2.2:1161

                                 192.168.0.3:161 -> 2.2.2.2:1162

Branch 2nd NAT: 2.2.2.2:1161 -> 10.10.0.1:161

                              2.2.2.2:1162 -> 10.10.0.2:161

Practice 2

To simplfy our routing job I using python to add nodes & found API allow adding nodes by same IP with different SNMP port, so I think the 2nd NAT no longer required & less configuration is required.

Example:

NPM IP: 192.168.0.1

Branch Public IP: 2.2.2.2

Monitored Nodes Address: 2.2.2.2:1161, 2.2.2.2:1162 (No virtual IP is needed)

Branch NAT: 2.2.2.2:1161 -> 10.10.0.1:161

                     2.2.2.2:1162 -> 10.10.0.2:161

I am still testing 1-3 days to observe the result. Does anyone have tried the practice 2 and any potential cons for it?