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

Sonar Discovery using SNMP on non-standard port

I have upwards of 100 nodes for which I need to discover the volumes. These nodes are using an SNMP agent listening on port 11611, instead of the standard 161.

Is there any way to change the Network Sonar Discovery so that it performs a discovery on this port

Find more posts tagged with

Accepted answers

All comments

tlwoodstx

It would probably be easiet to bring those in under the discovery without using an SNMP string and relying on just ICMP(ping). Add the unknown devices then do a bulk edit under Manage Nodes applying the SNMP string and desired port. Then run a Rediscovery on those nodes.

bshopp

Are all devices being monitored in Orion using that port or just specific ones?

darryld

These 100 nodes are all HP-UK servers with a secondary SNMP agent (because the HP one is rubbish). This Orion is also monitoring about 400 windows servers and 200 assorted networking devices on the usual port 161.

cshirkoff

Your tip was spot on for my situation also. Are there any plans to add CSV imports of nodes like we can do with IPAM entries?