I have been working on cleaning up npm, with regards to monitoring our switch environment. We are currently 100% an Extreme Networks outfit.
I have been attempting to figure out if we could make use of the topology mappings provided by npm, specifically now that lldp is supported. In order to test this, I have enabled lldp between one of our cores and an edge.
Both devices are running Extreme XOS 12.3 or higher. Between these two devices is a static trunk of two ports.
CORE 5:16 <-----> Edge 2:48
CORE 6:18 <-----> Edge 1:48
However When I look at the topology of the Edge Switch I see the following has been discovered.
From this I can see that this is clearly not being retrieved from lldp, and most be using fdb to figure this out.
I took the liberty of going through this kb article:http://knowledgebase.solarwinds.com/kb/questions/3508/What+object+IDs+%28OIDs%29+does+the+Orion+Platform+poll+for+network+topology+information%3F+What+types+of+network+topology+information+does+the+Orion+Platform+poll%3F
and did an snmpwalk of the LLDP-MIB on the edge and core switch. Just wondering if anyone knows if this is supposed to be supported, or if it is a known issue
I am probably going to follow up with a ticket, as I am also having a couple of issues in regards to udt as well, however I wanted to post here first.
Orion Core 2012.1.0, SAM 5.0.1, NPM 10.3, UDT 2.0.0, IVIM 1.3.0
