Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Node and Interface discovery and management in Orion 10.1.2

Node discovery and managment has come a long way since the early days of Orion.
Being able to select and edit multiple elements at once through the web gui is a huge benefit.

However, I wonder if I am missing something here.
Please let me know.

Firstly;

I'm using the Node discovery to import new nodes and their associated interfaces into a new Orion install.
I have 260 switches to import, but only want to monitor the Fa0/1 & Fa0/2 ethernet interfaces (regardless if they are up or down).
I end up importing all interfaces and then deleting Fa0/3-48 manually after they are all imported. Am I doing this right?

Secondly;

Using the Manage Nodes page > Interfaces, I want to delete all unknown and down interfaces from a group of nodes.
I can't find the filter that allows me to select all down or unknown interfaces. Or is there a way to sort by interface status?
What am I missing?

I realize much of this can be done using custom SQL queries, but for the average user, I would think these features/options should be available in the gui?

Find more posts tagged with

Accepted answers

FormerMember

NG,

#1 - Yeah, you're doing it right but unfortunately, the ability to select specific interface ports on node discovery is not possible now. It sure would be nice to have this flexibility added.

#2 - Manage Nodes page > Interfaces > Group By > Status. Should get you what you're looking for.

All comments

FormerMember

NG,

#1 - Yeah, you're doing it right but unfortunately, the ability to select specific interface ports on node discovery is not possible now. It sure would be nice to have this flexibility added.

#2 - Manage Nodes page > Interfaces > Group By > Status. Should get you what you're looking for.

Network_Guru

Thanks Glen!

For #2, I got so hung up on the filter side, I totally missed the 'group by' box.
Doh!

<edit> After reviewing this, it's not working as well as it should. By grouping the interfaces by status, I've lost my node filter. Now instead of just seeing interfaces from my Cisco 1811 routers, I'm seeing all 8K interfaces for all nodes. I ran into this issue when using the search function as well. If I start out with a node filter of say Machine Type and then switch to the interfaces view, the Machine Type filter is lost when doing a search on the interfaces.

What is really required is a nested query like the Report Writer - select interfaces where node type = x and node region = y and interface = z

The node management tool still has a way to go before it is ready for prime time in a large Enterprise environment</edit>

Network_Guru

After doing some more discovery and additions, I found it is easy to get burned with the Sonar Discovery if you don't watch what you're are doing.

Example, I have 500 routers with loopback IPs in a different subnet than the LAN interface/subnet. After adding the routers, I created a discovery of the switches which are in the LAN subnet on all these routers. Of course the routers also show up in this discovery with their LAN interfaces. If you forget to unselect the routers when adding the devices into Orion, you end up with a bunch of duplicate entries for the routers - one using the loopback IP and one using the LAN IP. What a mess to go through and clean up...

I wonder if Solarwinds could add a feature that checks for the same System Name when importing nodes and reject them as duplicates?

FormerMember

add a feature that checks for the same System Name when importing nodes and reject them as duplicates

+1 here. This functionality is really needed. And also including a message something like "Node xxxxx (current ip address) already exists - Node with IP address <new ip address> ignored." in the import log history.