NPM 10.4 Multiple IP question.

Question

npmNode Discovery and Management

- Devices with multiple IP addresses are no longer added in Network Discovery as duplicate nodes.

If we have existing devices with multiple IPs already in Orion is there a way to force the deduplication? Where can you see the multiple IPs assigned to a node? How do you select the IP that NPM should poll?

An example is a linux server with multiple IPs. When preforming a discovery with the IP range NPM discovers the 20 nodes and correctly assigns them back to 2. However the duplicate nodes are still in the database. Do these need to be deleted manually?

eth0      Link encap:Ethernet HWaddr 00:50:56:B0:02:A4
          inet addr:172.23.222.20 Bcast:172.23.222.63 Mask:255.255.255.192
          inet6 addr: fe80::250:56ff:feb0:2a4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:440047006 errors:0 dropped:0 overruns:0 frame:0
          TX packets:465127629 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:185316494349 (172.5 GiB) TX bytes:186967848830 (174.1 GiB)

eth0:0    Link encap:Ethernet HWaddr 00:50:56:B0:02:A4
          inet addr:172.23.222.21 Bcast:172.23.222.63 Mask:255.255.255.192
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0:1    Link encap:Ethernet HWaddr 00:50:56:B0:02:A4
          inet addr:172.23.222.22 Bcast:172.23.222.63 Mask:255.255.255.192
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0:2    Link encap:Ethernet HWaddr 00:50:56:B0:02:A4
          inet addr:172.23.222.23 Bcast:172.23.222.63 Mask:255.255.255.192
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0:3    Link encap:Ethernet HWaddr 00:50:56:B0:02:A4
          inet addr:172.23.222.24 Bcast:172.23.222.63 Mask:255.255.255.192
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0:4    Link encap:Ethernet HWaddr 00:50:56:B0:02:A4
          inet addr:172.23.222.25 Bcast:172.23.222.63 Mask:255.255.255.192
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0:5    Link encap:Ethernet HWaddr 00:50:56:B0:02:A4
          inet addr:172.23.222.26 Bcast:172.23.222.63 Mask:255.255.255.192
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0:6    Link encap:Ethernet HWaddr 00:50:56:B0:02:A4
          inet addr:172.23.222.27 Bcast:172.23.222.63 Mask:255.255.255.192
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0:7    Link encap:Ethernet HWaddr 00:50:56:B0:02:A4
          inet addr:172.23.222.28 Bcast:172.23.222.63 Mask:255.255.255.192
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0:8    Link encap:Ethernet HWaddr 00:50:56:B0:02:A4
          inet addr:172.23.222.29 Bcast:172.23.222.63 Mask:255.255.255.192
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

zizi · Accepted Answer

Orion NPM 10.4 added a new resource Node Detail Reports -> All IP Addresses on ${Caption}, which displays all known IP addresses assigned to a node. It might be assigned to a Node Details View. Resource is able to highlight the IP, which is used for polling. You need to use Edit Node page to change the IP used for polling.

10.4 is now able to avoid inserting new duplicate nodes in Network Sonar Discovery's import results wizard. However existing duplicates in Orion Database have to be removed manually.

NPM 10.4 Multiple IP question.

npmNode Discovery and Management

Top Replies