Re: discovery of nodes with secondary IPs stay as multiple nodes
Dave Johnson <[email protected]> Tue, 13 Nov 2018 15:30:35 +0000
| Newsgroups | gmane.network.opennms.general |
|---|---|
| Message-ID | <85BF58CCA3C1F74A8320EE6AB969141D217A2F3A@mbx027-w1-ca-4.exch027.domain.local> |
Norbert-- That is an interesting solution, solving the listed givens. Thanks for the suggestion. I failed to mention that we want autodiscovery to auto find new hosts that are deployed on these vlans; a big feature of opennms that we like. Thus we will have to find another way... We do have a work around, but it seems like we are doing something wrong.... ? -----Original Message----- From: Norbert Steinhoff <[email protected]> Sent: Tuesday, November 13, 2018 6:53 AM To: General OpenNMS Discussion <[email protected]> Subject: Re: [opennms-discuss] discovery of nodes with secondary IPs stay as multiple nodes Hi Dave, create a management vlan with a separate ip range. Give each Switch a unique ip in this new network as its management ip. Discover only this management vlan. So every switch will only be found once and its interfaces in the other vlans will be assigned by snmp. HTH Norbert Am 12.11.18 um 21:03 schrieb Dave Johnson > This post is regarding autodiscovery of secondary IPs on both Arista and Cisco switches and opennms not auto-combining those nodes. Forgive me if I have missed the answer, I scoured the list and it seems there are similar previous posts (VRRP/HSRP and standard macs used; setting net-snmp pon agentaddresses), but non that address this particular issue. > > We recently went through a network migration and collapsed multiple switches into a fewer number. On a several of the SVIs (VLANs), we added some secondary IPs on the new switches that took over the roles of previous switches. One example, some hosts default routed towards a ".6" IP on a vlan; which went to a different switch (with different configs), but after the migration those separate switches were no longer required. > > In addition to these secondary IPs that are on the new switches from the migration, I've configured secondary IPs for the ".1" main default gw on the vlan and set ".2" and ".3" for two of the main switches. This ".1" secondary IP will likely eventually be placed in VRRP. > > Let me just focus on the ".1" interface scenario as a secondary IP for now. The opennms autodiscovery sees the ".1" and ".2" last octet IPs on the network. It creates these as a suspect nodes (ie: node "1001" and "1002") that opennms will need to snmp scan. After doing a snmp scan on those two nodes: > > * Node 1001 has ".1" as primary opennms interface; ".1" in the interface table, but NO "SNMP ifIndex" for the secondary IP. > * Node 1002 has ".2" as primary opennms interface; ".1" in NOT the interface table at all. > > It appears secondary IPs do not show up in snmp's "ipAddrTable", meanwhile all the node information (LLDP chassis information/serials/etc) are all identical. Even though a node suspect with an opennms primary interface being set on the nodes "secondary interface," it is the same node, shouldn't this be combined? > > For a switch with a dozen vlans, this adds up to an extra 12 instances of that switch. As a workaround, we omit scanning of .1-.3 IPs on many of the vlans, so autodiscovery doesn't keep adding the nodes with the secondary IPs. > > We are running 22.0.2 opennms; centos7.2; java 1.8.0_144. We tried this on a separate fresh minimal install of 23.0.0 opennms, and had similar results. > > Is there something we are missing or another way that opennms will handle secondary addresses on a network more gracefully? > > > * Dave > _______________________________________________ > Please read the OpenNMS Mailing List FAQ: > http://www.opennms.org/index.php/Mailing_List_FAQ > > opennms-discuss mailing list > > To *unsubscribe* or change your subscription options, see the bottom of this page: > https://lists.sourceforge.net/lists/listinfo/opennms-discuss _______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-discuss mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-discuss _______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-discuss mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-discuss