Troubleshooting network device scan failures
When you observe failures while scanning network devices, use the troubleshooting steps described in this section to either resolve the problem or create a BMC Support case.
- An SNMP scan fails.
In the DiscoveryAccess node, any of the following error messages are displayed:
ERROR: SNMP++: SNMP request timeout
Perform the following steps to troubleshoot the SNMP scan failures:
Step 1: Verify the prerequisites
- Check that the scanned device is supported.
sysoid(sometimes, this is in the result of
getDeviceInfo) and check that it is in the list of supported SNMP devices. If it is not yet supported, contact BMC Customer Support. If possible, also provide a device capture to Support.
- Check that the scanned device can be pinged (ping
device_ip_address) from the appliance/instance or the BMC Discovery Outpost scanning it. If this does not work, engage your IT to check why the IP does not respond.
Check that the SNMP port of the scanned device, typically port 161, is opened from the appliance/instance or the BMC Discovery Outpost scanning it. If not, contact your IT team to open the port.
You can use the following commands to check for open port:
nmap -p 161 device_ip_address
The typical result when the port is open:
[tideway@discovery ~]$ nmap -p 161 device_ip_address
PORT STATE SERVICE
161/tcp open unknown
telnet device_ip_address 161
The typical result when the port is closed:
[tideway@discovery ~]$ telnet device_ip_address 161
telnet: connect to address device_ip_address: Connection refused
Check your SNMP credential with a test credential from the BMC Discovery UI. If this fails, try again with
snmpwalk. If this too fails, send the
snmpwalkcommands and results to your IT team and ask why it fails. See the following examples for SNMP version-dependent information:
/usr/tideway/snmp++/bin/snmpWalk device_ip_address -v1 -Cpublic
/usr/tideway/snmp++/bin/snmpWalk device_ip_address -v2c -Cpublic
/usr/tideway/snmp++/bin/snmpWalk device_ip_address '126.96.36.199.188.8.131.52.3.1' -v3 -snMyLogin -sl2 -authMD5 -uaMyPassword
/usr/tideway/snmp++/bin/snmpWalk device_ip_address '184.108.40.206.220.127.116.11.3.1' -v3 -snMyLogin -sl3 -authSHA -ua'My$Password' -privDES -up'MyPrivateKey'
If all the prerequisites are working correctly but the scan still fails, proceed to Step 2.
Step 2: Test and review the BMC Discovery configuration
In case of a time out, perform the following steps:
- Move the dedicated credential for this IP address to the top of the credential list.
getBulkin the SNMP credential.
- Set the credential timeout value to 300.
- Restart the tideway services.
If the problem persists, send the discovery debug logs and the result of the earlier steps to BMC Customer Support.
Log in or register to comment.