NetIM: How to troubleshoot common device discovery issues?

• In order for NetIM to discover a device it must meet the following requirements
  • It must be SNMP accessible.
  • It must respond to SNMP ping as defined in NetIM. The ping response must include the following
    • sysname
    • ifNumber
    • sysUptime
  • If the device response to ping additional information about the node is collected to create a light-weight model. This model include system, interface, memory and CPU information

What's causing my discovery problem?

• SNMP Credentials not in the NetIM Global Discover settings
• The device does not respond to SNMP ping  but is otherwise SNMP accessible
  • Security Devices
  • Router/Switches with security packages installed
• Access Control List blocking SNMP access
• SNMP View Based Access Control settings
• Device was merged with another device based on IP matches
• NetIM processes are stalled or queued

How do I troubleshoot my discovery issue?

• Check the "Add Device Discovery Result History" report for failure reasons. Did discovery fail or was the device merged?

• Confirm SNMP access to the device using the MIB Browser, loading the RFC1213 MIB
  • app.bat mib_browser
• Does the device respond with sysname, ifnumber and sysuptime?

• Enabled debug on the Adapter Server process and rediscover the device. Configure>All Settings>Server Status
• Check adapter server log to determine if the SNMP ping was successful
• If logs are inconclusive perform a packet capture to verify that SNMP ping is being sent from NetIM and its response
• If SNMPv3 is enabled, please check if the device is using AES 256 encryption. NetIM is not compatible with some vendor specific variants of AES 256
• If the device is being merged, use the mib browser check the device IP address table
  • Search file install_dir\log\errorLogs\Device Discovery\Device and Platform Info Auto Discovery\debug\orderedIPs.txt for these addresses to see if they are present on different nodes
  • If there are matching addresses, adding them to file install_dir\input\AutoDiscovery\excludeFromDpiSelection.txt should allow the device to be discovered
  • If a match is found but the node in question does not have the match address in its address list when browsing the device, clear the content of orderedIP.txt and  try rediscovering the device
  • If these matching address are internal address on the device and common among a certain device mode, submit a feature request to have these exclusions included in a future release

Collected Data for Support

• Note the sysnames and access addresses of the devices not getting discovered.
• Enabled debug and rediscover the device
• Provide a logpacker
• Confirm that the device is accessible via SNMP from the NetIM system using the MIB browser
• Confirm that NetIM has the SNMP credentials in Global Discovery
• Confirm that the device is not configured for AES 256 encryption
• Confirm that the device is not getting merged