Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
This video (3:26) will show you how to add elements that were discovered in a Scheduled Discovery to the database so these elements can be monitored. A scheduled discovery only finds network elements, but does not automatically start monitoring. You must select what you want the system to monitor. If the scheduled job locates nodes that you do not want to monitor, select those nodes and click Add to Ignore List. Ignoring hides elements from the results list the next time the discovery job runs.
This video is available in the following languages: German, Simplified Chinese, Spanish and Portuguese.
Orion Platform products version 2015
Server & Application Monitor v6.2.3
Network Performance Monitor v11.5
Network Traffic Analyzer
|Storage Resource Monitor|| |
Network Configuration Manager
Web Performance Monitor
IP Address Manager
User Device Tracker
VoIP & Network Quality Manager
In previous sections we built Network Sonar Discovery jobs and we looked at running those jobs manually. But now let’s take a look at our scheduled discovery results and what happens when a discovery job runs automatically. How do we see the results of those discovery jobs? First of all, it’s important to remember that automated or scheduled discovery jobs do not start monitoring anything they find automatically. Instead, you’ll see a summary of the job on the notification bar at the top of the web console. But you have to go into the discovery results and choose which elements you want to monitor. You can click on View Results on the notification bar. Or you can also go to Network Sonar Discovery in the Settings menu and choose the Scheduled Discovery Results tab. Either way takes you to the same screen.
On the Scheduled Discovery Results tab, you notice that you see any nodes that the discovery job found changes for; whether it’s a brand new node or there were new elements discovered on the node, like a new interface or a new application. But here you’ll notice that nothing is selected by default. Again with manual discovery jobs the default assumption is that everything you find you’re going to want to monitor. But with scheduled discovery jobs you have to tell it explicitly what to monitor. Scheduled discovery jobs don’t make any changes monitoring on their own. The reason for this is that you don’t want to come in one morning and discover you’re out of licenses or your polling engine is swamped because of a scheduled discovery job.
But notice that you have tremendous granularity in what you can choose to add here. You can choose to just accept all the changes to a particular node, or you can expand the node and choose just specific elements. And you’ll notice that here you see all the elements on the node with the newly discovered elements being highlighted. So shows you everything Orion has discovered and is capable of monitoring for a particular node.
For instance you can see that this discovery job found 24 new interfaces on my switch. I could import all the changes by selecting the check box for the switch, or I could select just specific interfaces to import. You can also choose to ignore certain elements. For example, maybe a new server pops up on the network that you don’t want to monitor. If don’t do anything, every time the automated discovery runs that server will show up as a new node. Well it’s not a new node at that point. You already know it’s out there, and seeing it all the time may cloud your ability to keep track of changes to the network. So you can select the server and click Add to Ignore list. Now you know it’s out there but you won’t see it as a new node with each discovery. And if you decide later that you do want to monitor the server, you can always click on discovery ignore list and take it off of ignore.
Once you’ve selected the nodes you want to import, or the specific elements on the node, click on Import nodes.
This will take you back into the Network Sonar Results wizard that we already looked at when we ran a discovery job manually, but with just the nodes you selected from the discovery job included in the array. This will allow you to refine your import and then add the new elements to the database to begin monitoring. Just keep in mind that scheduled discovery jobs will run in the background but won’t automatically make changes to your monitoring. Nothing will be monitored until you view the results and tell Orion what to monitor.