1 Reply Latest reply on Mar 8, 2013 1:37 PM by jbiggley

    SNMP Discovered Interfaces and Volumes for Multiple Nodes


      This is probably an easy answer, but the logic is escaping me on a Friday afternoon.


      I want to be able to define a list of IP addresses that can be scanned for SNMP and produce a list of nodes with all of the discovered interfaces and volumes listed by node before I add them to the NPM database.  I know that I can use discovery, but I don't get the detail of the interfaces and volumes.  I've tried the Engineer's Toolkit - Network Sonar, but it only allows for seed routers, not a list of IP addresses.


      What I'd like to do is walk a list of IP addresses and then turn the list over to the client so that they can specify which elements need to be monitored and any custom attribute volumes that need to be added.


      Thoughts?  Ideas?  (Insane or otherwise!)




      EDIT:  Apparently NPM 10.5 (in beta now) supports the ability to filter out interfaces during the discovery process.  Closer to what I am after, but not quite there.


      The specified item was not found.

        • Re: SNMP Discovered Interfaces and Volumes for Multiple Nodes

          I've been thinking about this one a little more and I've got a few comments to add.


          1)  The issue with adding them to the database is the size of the environment.  If I am adding hundreds of nodes at once I risk impacting the performance of the Orion server with elements that I am not going to monitor.  When you are hosting environments with thousands of nodes, every bit of performance impact matters!


          2)  If I could flag the nodes into unmanage mode on entry, this would allow me to run a custom report against all unmanaged nodes so that I could pull the resource details and get them approved by the client.


          3)  All of this would be solved if there was a) an tool outside of NPM to provide the resource details of a list of IP addresses and b) a way to import a list of nodes and resources from that said tool back into NPM.


          It seems that Orion has been developed for the 'subnet sweep and monitor' crowd but is missing the ability to be granular about what resources you want to monitor without some significant manual intervention via the GUI.


          Just thinking as I bang my head against this problem this afternoon.