cbowden wrote: > > The connections are calculated and drawn without any problems however my > desired setup is as follows. > > Switch A - Running LLDP and SNMPv3 > Switch B - Running LLDP and SNMPv3 > > I've tested that LLDP is working correctly between the switches and can see > the neighbour information. >
Type "#vpollerstat" in the search field of the L2 window to see information that the L2 engine has collected for each device (the IP's are in hex). Look in the poll_table column for entries named lldpRemTable and lldpRemManAddrTable and check the number of rows returned for each. If the number of rows is 0, the table was polled but no data was returned. If you can't find the lldp entries, they weren't polled. The L2 engine presently ships with Cisco devices on the LLDP exclude list due to issues reported during beta testing (high CPU when polling lldp entries). There is currently no way to modify the exclude setting; I can add one in the next 5.4.x beta. I do not know why you see different results with CDP when running SNMPv3 -- this puzzles me. The cdpCacheTable is a normal table retrieval; there shouldn't be any difference between protocol versions. Again, the #vpollerstat command may shed some light on whether certain tables are being polled, and how many rows are seen. InterMapper does all the polling for the L2 engine. If there are SNMPv3 errors, you might see them logged in the InterMapper Debug log, not the L2 log. -------------------- m2f -------------------- Read this topic online here: http://forums.dartware.com/viewtopic.php?p=3397#3397 ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [email protected]
