NPM Network Topology - Showing incorrect information

In the NPM resource showing the network topology, i´m seeing a lot of completely wrong info. For a while, i figured tyhat a table was not beeing updated, as the topologywas mostly showing (incorrect) information from the same location.

Now, i found that even new nodes imported via network discovery, shows the same behaviour. Even nodes that are added manually.

At the moment i´m seeing a node located in a datacenter in Hong Kong, directly connected to a switch in Stockholm.

Often (but not always) one or more interface showss as unknown.

What am i missing.. ?

Shoul i trunkate a table somewhere (which) and let the sonar find new topology information ?

How is the topology info updated ? Only by discovery, or will the resource utilize the bridge mib poll ?

brgds

Jesper

Find more posts tagged with

network

topology

npm

Accepted answers

All comments

joelgarnick

any answers to this question? I'm having the same problem...I have several servers that say they're plugged into a voice router....not even close!

dfairles

NPM Topology is not finished. It gives partial and incorrect information. I had an open ticket, and I got this information directly from Mav Turner the product manager. He said they would rather push something out rather than wait until it was finished.

Bad decision to me. How do we know what is supposed to work and what does not work by design?

superfly

That's crazy!! Nothing should be released until it's working as per its design.

mavturner

This is a mis-characterization of my statement. I said we shipped Topology with Layer 2 support only, no Layer 3 support, this was by design. I certainly respect your opinion that you would rather have waited to have both Layer 2 and Layer 3 topology at the same time, but many customers receive significant benefit in having Layer 2 data today and that is why the decision was made to ship with Layer 2 topology now and add Layer 3 support later. Layer 2 topology support wasn't rushed just to ship. If there are bugs or issues, we certainly want to know about those so we can resolve them. As to the two above questions in the thread, I'm not sure what is going on in these specific situations, but I strongly suggest you open tickets so we can resolve the issues.

To answer the other question about what should work, I just posted a blog with more detail about what we expect topology to do today and how it works.