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

what criteria does orion use to connect interfaces in network atlas

I started creating some network maps for my branch offices using network atlas and when i click conect now it finds links but it seems to be finding some virtual interfaces that are showing being connected to places the router is not physically connected to. I'm not sure if this is a networking problem or if solarwinds is wrong. I have a router that shows being connected to my core switches and floor switches at the same time, which of course would be bad. the interface solarwinds is saying is conected is a virtual interface. What criteria does solarwinds use to determine what an interface is connected to and what would be a good way to determine if solarwinds is right or wrong?

Find more posts tagged with

network

map_atlas_beginner

atlas

Accepted answers

All comments

zizi

Orion NPM 10.2 is able to utilize information from bridge forwarding and filtering tables (Bridge-MIB and Q-Bridge-MIB) and ARP tables (ipNetToMedia table in IP-MIB). Incorrect connections are often built using ARP table data. Orion utilizes ARP table only if no other connections were discovered using bridge forwarding and filtering tables for specific node. If this is the case, you can try disabling ARP polling by unchecking L3 topology poller in List Resources on affected nodes. You should be able to notice a change after next Orion Database Maintenance run.

If you want to see immediate change, you need to:

uncheck L3 pollers in List Resources on affected Nodes
run Database Maintenance manually (C:\Program Files (x86)\SolarWinds\Orion\Database-Maint.exe
Open Node Management page, select nodes from the first step and use More Actions -> Rediscover Now
Wait few minutes to let Orion refresh all data and Use More Actions -> Update Topology

Please let me know how it goes. If you decide to open a support ticket, please post back with the case number here, so I can take a look.

Thanks,

Marek Zizlavsky

SolarWinds Developer

krfitzgerald

that makes sense, thank you very much. Would I be loosing any useful monitoring or information by unchecking L3 pollers? Is this fairly common? How can I make sure this is solarwinds reading the connection wrong or someting wrong with my switches in the virtual interface setup?

zizi

Unchecking L3 pollers forces Orion to stop polling ARP table data, which means it won't collect and utilize them for creating connections. The only affected feature is topology, so it should be safe to disable L3 polling. Connections based on ARP tables are not reliable, so it is most likely issue with Orion reading the data than real problem with device configuration. You can check all manually defined static records in both forwarding and ARP tables, just to make sure.

krfitzgerald

I tried your steps but the incorrect links keep coming back?

zizi

Would it be possible for you to open a support ticket? I need full Orion Diagnostics for further troubleshooting. Please post back with a ticket number here, so I can take a look. Thanks!