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

Incorrect topolgy information

I'm currently running NPM 10.1.3 on a network consisting of HP Procurve switches. I've noticed that, when looking at the NPM Network Topolgy information for a node, the 'Connects to' section, I'm getting erratic information, which can either be;

The 'NPM Network Topology' section doesn't show at all, even though there should be valid information

If it does display, the port shows as 'Unknown', but the switch shows correct

Occasionally, I get the odd device showing the correct port and switch, but this is not many.

I did trial UDT1.0 as well, which even though it was meant to fully support HP switches, didn't work properly, and also showed erratic or incorrect information on our network. There are no network issues to report, all switches are configured with LLDP enabled. I really think LLDP support in NPM should be a must, just for reporting basic topology information. I understand UDT can do the more advanced stuff.

Find more posts tagged with

Accepted answers

All comments

wbrown

I have similar issues with my Cisco Catalyst switches where multiple layer 3 interfaces are present.

Once thing that helped (when it did show connections) was to ensure the connecting interfaces/trunks are monitored on both sides of a link and then rediscover the connected switches in the same discovery. This showed more topology info but was still too often incomplete or incorrect.

Since then I've completely disabled the topology discovery on all my discoveries because the info was just too inconsitent and made the discoveries take WAY too long to process.

NPM 10.2 is supposed to be better able to handle layer 3 switches as well as separate the topology discovery from the network discovery. I haven't tried or even looked at the betas.

tonybarrett

Thanks for the info. Sounds like it's not just me then. I would say though, that I was expecting topology information to be discovered at layer 2 as well, as this is where LLDP/CDP operate. I know UDT 1.0 was primarily using ARP information to gather this, and not the proper layer 2 discovery protocols, and it looks like NPM 10.1 is doing this as well. Let's hope 10.2 fixes this, and allows proper port mapping at L2 and L3.

freemen

How does one disable the topology discovery during network discovery?

Nandish

I don't think we have any option on the GUI to turn off topology discovery.But you can try this link,if not I would recommend to contact support for a work around.Feel free to post the ticket# and the solution.