-
Re: Incorrect topolgy information
wbrown Sep 29, 2011 9:22 AM (in response to tonybarrett)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.
-
Re: Incorrect topolgy information
tonybarrett Sep 30, 2011 3:33 AM (in response to wbrown)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.
-
Re: Incorrect topolgy information
freemen Oct 3, 2011 12:42 PM (in response to wbrown)How does one disable the topology discovery during network discovery?
-
Re: Incorrect topolgy information
Nandish Oct 6, 2011 7:07 AM (in response to freemen)I don't think we have any option on the GUI to turn off topology discovery.But you can try this Discovery Profile Timeout,if not I would recommend to contact support for a work around.Feel free to post the ticket# and the solution.
-
-