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

Monitoring a device on a non-routed vlan.

I am trying to figure out a way to monitor a critical device that happens to reside on a non-routed vlan. Non of my SolarWinds systems are members of that vlan. I am toying with the idea of creating a second interface on the poller that would monitor it. Does anyone else have an idea of how to accomplish this?

Jon

Find more posts tagged with

Accepted answers

All comments

dhanson

I take it the particular device doesn't have a DRAC or ILO port? No management interface that can be connected in a different VLAN? Otherwise, you're stuck putting a NIC from your poller into the VLAN.

Another option is to make the VLAN routable, but put a policy denying any traffic aside from management traffic. Not an optimal approach, but it'd work.

Good luck!

irishjd

Yea, it isn't a device that we control either as it belongs to our service provider. I hate the thought of routing the vlan as that will cause all sorts of security concerns from IA, so I am just going to go with the second NIC, and see how that works out.

d09h

If your SW second NIC is in the same subnet, you could leave default gateway off of SW NIC and the critical device's NIC. Set a persistent route. Apologies if I'm stating the obvious.

ecklerwr1

And obviously don't allow routing across the host.

irishjd

Almost forgot about the persistent route, so thanks for reminding me!

irishjd

This is probably a silly question, but how would you prevent routing across the host?

RichardLetts

monitor the switch interface that's plugged into it?

irishjd

Hi Richard, not exactly... We have access to a second, not-for-work network. It is the typical, log in with a username and password portal thing. It is managed by a third party, so I just want to ping the DG to verify that it is up. That is why it is so important not to route traffic between that network and the production network. I hope this makes sense...