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

Network Discovery Failed

jefflby

Almost everyday Orion/NPM is reporting "Network Discovery Failed".

While I appreciate this alert, it's rather useless. There is not apparent link to a log or a reason that I can find.

Where can I get more information on what the failure was? Where is the log file for this?

Any direction you can provide would be great.

Thanks!

Find more posts tagged with

Accepted answers

dc4networks

Ok.

Not sure about that one.

I assume all the discovery settings are still a OTB Defaults?

I am sure there is something within the THWACK Community where It will tell where you can find the SolarWinds Orion Logs.

I think it is C:\ProgramData\Solarwinds\Logs

Although I am not sure if you will find what you need there.

There may be a report that you can run that will get you the details that you want?

All comments

dc4networks

How BIG is your Sonar Discovery?

If it is to big it may be timing out and hence failing.

Try and segment it in to Subnet Portions and Stagger the Time that that each Subnet Discovery.

jefflby

less than 150 hosts/devices

jefflby

And it doesn't always fail. I'm more looking to find out how I can find the logs to see what the real error is.

dc4networks

Ok.

That should be ok but...

I broke my discoveries down to maximum of 20, starting in 15 Minute intervals.

But this was targeting know IP Addresses as set Host Discoveries.

This being due to there being different Security Zones with Firewalls and awaiting a Communication Matrix for the SolarWinds Orion Monitoring Platform to be fully implemented throughout allowing the SolarWinds Orion Polling to get through the Firewalls and not be dropped.

Credentials?

We know that just using ICMP should work ok. (As long as the Firewalls let the Traffic Through).

Is the SNMPv2 Community String Correct?

Are the SNMPv3 Authentication and Encryption Correct?

Do the Hosts to be monitored know about the SolarWinds Orion Poller?

On a previous Project I used the Subnet Sonar Discovery with ICMP.

With the Network Device Discovered I then used NCM to push the SolarWinds Orion SNMP-Server and SNMP Details to the Network Device Configuration.

Then Hey Ho...

On the next Discovery be that immediate or scheduled over night SolarWinds Discovered the Network Devices as a Cisco Switch, Router or ASA Firewall.

Does any of this help?

dc4networks

Ok.

Not sure about that one.

I assume all the discovery settings are still a OTB Defaults?

I am sure there is something within the THWACK Community where It will tell where you can find the SolarWinds Orion Logs.

I think it is C:\ProgramData\Solarwinds\Logs

Although I am not sure if you will find what you need there.

There may be a report that you can run that will get you the details that you want?

lcsw2013

I believe all discovery related logs should be in this directory (Or similar) : C:\ProgramData\Solarwinds\Discovery Engine. The discovery engine logs should give you an idea of what failed. I would say try OrionDiscoveryJob.log, It should give you what you are looking for.

lcsw2013

checking the logs I mentioned above covers many of the items you listed and tells you what failed.Then you can check the failing point and fix it accordingly. Segregated networks, networks behind multiple firewalls etc, have the potential of my problems just due to the fact of the complexity.

In our network we have several small segregated networks. These networks are know to be problem childs in our monitoring. Working with the network team we identified a solution that worked for us by establishing direct routes on port 161 for snmp traffic.

But when it comes to discoveries I don't know of any logs that can give better information.

I hope this helps.