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
Store

Best Practice for Unrouted Vlan Resource Monitoring

Hello,

I work in a large environment. So scaling is a issue we need to consider while migrating to Solarwinds. When monitoring resources, what would be the best practice for monitoring unrouted vlans? We have well over 300+ switches - 4-10+ vlans in each switch. Should i worry about just monitoring loopback's, interfaces, and HW info?

Find more posts tagged with

Accepted answers

superfly

I wouldn't bother monitoring unrouted VLAN's. In fact, I wouldn't even monitor VLAN's. I would monitor only uplink interfaces and interfaces to important devices like servers.

All comments

stuartd

I don't know that it is best practice, but traditionally we never monitored VLANs of any sort. Once virtualisation came along we took a more pragmatic approach and only monitored important VLANs as clearly there is no physical here - your definition of important may be very different to ours.

Also, this small thread may help you make up your mind: https://thwack.solarwinds.com/product-forums/network-performance-monitor-npm/f/forum/76035/significance-of-unrouted-vs-routed-when-referring-to-vlans-in-orion

superfly

I wouldn't bother monitoring unrouted VLAN's. In fact, I wouldn't even monitor VLAN's. I would monitor only uplink interfaces and interfaces to important devices like servers.

Endy101

Thanks for the reply. This was very helpful.

Endy101

Agreed. Thanks for replying.