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

Running Network Sonar after V10 upgrade

Prior to upgrade we manually added all network devices, would like to take advantage of new features in V10 of NPM. I would like to utilize the ConnectNow feature in Network Atlas.

Would I setup a Sonar scan of existing devices managed IP addresses and import this information into NPM. What will this do to existing managed devices in the database, would it create duplicates or append found inromation to existing devices.

Find more posts tagged with

Accepted answers

All comments

extrands

That's going to depend on how many devices you have, and how much time you have to correct the duplicates you are going to have. Sonar apparently lacks the ability to determine if a device already exists in the DB. You will discover a device, possibly by a different IP address, and then have to manually tell Sonar to ignore interfaces or nodes you don't want discovered. Very time consuming process in a large network, and several of us have asked that the discovery be enhanced to take topology into account before the import, and to also do a better job of duplicate detection, but those requests are not in this release.

I have also found that the ConnectNow feature works only on flat networks. Networks with VLANs fail, seriously reducing its utility for us.

Steve Extrand

Sr Network Analyst

Tyco Electronics

(1) Orion v10 SLX polling engine & Additional Web Server 25500 elements

(2) Orion v10 SLX polling engine

(3) NTA v3.6 689 interfaces

(3) IPSLA SLAX v3.1.0

FormerMember

I had run a sonar scan but had not imported devices yet pending responces to post.

Just happened to be checking on Node details for device and saw that connection data was now showing up in NPM network topology.

So I ran a test using connectnow in Network Atlas and it worked. So it would seem all you need to do is run the scan, no import required.

DirtySouth

I'm trying to utilize the new "Find Connected Port for End Host" feature, but am not having very good luck. It originally told me I had to run the Network Sonar scan before I could get any results. I ran the scan for a couple of our subnets, but I'm still not able to find devices when I search by IP or DNS name. Does it make a difference the the host and associated switch are managed on two seperate subnets? Has anyone else had much luck with this?

FormerMember

Follow-up

Ran full discovery last night for all manually added devices in NPM. Both ConnectNow and NPM and CORE topology only recognize L2 trunk ports. L3 links to core network and Vlans are not seen.

Not sure what good this is, being that I migrated from L2 networks about 10 years ago.