Why does discovery not cover 100% of network?
Troubleshooting Check Lists In general a discovery is NEVER 100% complete on the first run, issues that can effect the discovery are listed below:-: Missing Devices, Ports, or Links – Check List There are several reasons why a discovery may not cover the complete enterprise network. The following check list covers some areas that should be investigated:- • Switches may be not responding to SNMP: User needs to check SNMP access, SNMP community and VLAN – The autoAsset host Workstation must be on the management VLAN. Devices should be checked to ensure they are not configured with filters or Access Lists restricting which administration addresses are allowed. • Devices may be not responding to SNMP -SNMP Agents may not be available or may not have been activated • Forwarding tables may not be accurate (e.g., Switches broadcasting instead of keeping clean forwarding tables, creating virtual broadcast domains). • Devices may not respond to Ping Scan – the discovery operation is blocked by
Troubleshooting Check Lists In general a discovery is NEVER 100% complete on the first run, issues that can effect the discovery are listed below:-: Missing Devices, Ports, or Links – Check List There are several reasons why a discovery may not cover the complete enterprise network. The following check list covers some areas that should be investigated:- • Switches may be not responding to SNMP: User needs to check SNMP access, SNMP community and VLAN – The autoMap host Workstation must be on the management VLAN. Devices should be checked to ensure they are not configured with filters or Access Lists restricting which administration addresses are allowed. • Devices may be not responding to SNMP -SNMP Agents may not be available or may not have been activated • Forwarding tables may not be accurate (e.g., Switches broadcasting instead of keeping clean forwarding tables, creating virtual broadcast domains). • Devices may not respond to Ping Scan – the discovery operation is blocked by a
Troubleshooting Check Lists In general a discovery is NEVER 100% complete on the first run, issues that can effect the discovery are listed below:-: Missing Devices, Ports, or Links – Check List There are several reasons why a discovery may not cover the complete enterprise network. The following check list covers some areas that should be investigated:- • Switches may be not responding to SNMP: User needs to check SNMP access, SNMP community and VLAN – The autoAsset/autoMap host Workstation must be on the management VLAN. Devices should be checked to ensure they are not configured with filters or Access Lists restricting which administration addresses are allowed. • Devices may be not responding to SNMP -SNMP Agents may not be available or may not have been activated • Forwarding tables may not be accurate (e.g., Switches broadcasting instead of keeping clean forwarding tables, creating virtual broadcast domains). • Devices may not respond to Ping Scan – the discovery operation is blo
