Leonard, The code used within ADDM for network discovery is based on the devices MIB tables. Not all MIBs for all devices are configured. This explains why ADDM knows it is a Cisco device (based on the MIB discovery) but not the details. Every month things get better and better with each new TKU release, but there are still devices that are unaccounted for.
I believe you can still open a ticket with BMC with the devices that are not "supported" and they can assist. I do not believe the capability exists to utilize SSH to discover network devices. Many of the building blocks are in place, but the patterns would have to be designed and implemented locally ... unless you can convince the product managers that this functionality is warranted. :-) .: Mike T :. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Leonard Johnson Sent: Wednesday, November 14, 2012 2:44 PM To: [email protected] Subject: ADDM discovery of SNMPv3 Switches We are trying to discover Cisco switches that have SNMP3 turned on and its showing the switches as an unsupported device and doesnt create the device node in Discovery. But when we click on the corresponding IP address, it knows that the device is a Cisco device (just unsupported) so its finding and recognizing it correctly as a Cisco device. Has anyone come across this and have a solution? Also, has anyone used SSH as a discovery method for switches/routers? We currently use SSH to discover Unix/Linux devices but curious how to set up for network devices since we dont see in the configuration. Thanks for any ideas. Lj _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
