cc/td/doc/product/natkit
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Using Device Discovery

Using Device Discovery

Device discovery helps you discover Cisco devices in your network to ensure that they are Y2K compliant. After the devices are discovered, a file that lists the discovered devices is automatically exported to the inventory application.

Once a device has been discovered and added to the inventory database, it will not be redetected in subsequent discoveries, and it will remain in the inventory database.

Because device discovery uses SNMP and CDP, which are standard but unreliable protocols, you will need to run device discovery several times to discover all Cisco devices in your network.


Note  If a device has connectivity problems, (for example, being off line, located behind a nonpermanent link, or not configured to respond to SNMP or CDP requests), the device will not be included in the device discovery file.

To set up and run the discovery process in your network and to transfer the information to the inventory application, complete the following steps:

To tailor your device discovery, you can:

After you have finished setting all the device discovery options, you can:

Device Discovery Method

The three methods of device discovery are discussed in the following sections:

Cisco Discovery Protocol

This method discovers only CDP-enabled Cisco devices in your network. It takes the least amount of time to complete, and is useful in networks that are made up entirely of Cisco devices. Products acquired by Cisco do not support CDP. CDP is supported in Cisco IOS release 10.0 and later, and is not supported by WAN switches.

Ping Sweep Starting IP Address

This method discovers all SNMP-enabled Cisco devices in your network. It takes the longest of the three methods to complete, but is the most comprehensive. In this method, device discovery finds all the devices connected to the device whose IP address is given. The process is repeated recursively until all devices are reached.

Ping Sweep IP Address Range

This method discovers a specific range of SNMP-enabled Cisco devices in your network. It takes more time to complete than the CDP method, but less time than the Ping Sweep Starting IP Address method. It is useful if you know the unique IP subnets in the network. In this method, device discovery finds all the devices within a range of user-supplied IP addresses. It also provides the ability to find unique IP address ranges from a single device, and performs device discovery using the address ranges. See Table 5-1 for a comparison of each method.


Note  Devices are discovered using standard SNMP and CDP methods. Cisco devices that are unable to respond using these protocols will not be checked. Connectivity problems (such as devices being off line, or located behind a nonpermanent link, or not configured to respond to SNMP or CDP requests), will cause a device to not be included in the report.

Table 5-1: Comparison of Discovery Methods
Method Bandwith Used Time to Complete Comprehen- siveness Access Caveats

CDP

Least

Shortest

Least

CDP/
SNMP

CDP is in IOS 10.0 and later.

WAN switches do not support CDP.

Other company products acquired by Cisco do not support CDP.

Use only in a complete/almost complete Cisco network.

Ping Sweep Starting IP Address

Moderate

Between
CDP and Ping Sweep IP Address Range

Depends on user input

Ping/
SNMP

Useful if the user knows the unique IP subnets in the network.

Ping Sweep
IP Address Range

Most

Longest

Most

Ping/
SNMP

Should be used for most complete results. May take a long time to complete.

Defining the Community Strings

Use this option to set the SNMP read-only community strings.

Discovery uses community strings to determine whether a device supports SNMP. For each community string you enter, discovery waits for the SNMP timeout to determine if the device supports that community. For example, if you have specified three community string names, and the SNMP timeout is set for 5000 milliseconds (ms), it will take 15,000 ms for discovery to ascertain if the device supports SNMP.

Starting or Stopping Device Discovery

Use this option to start or stop the device discovery immediately or to schedule it to start at a predefined time. If more than one user starts, stops, or schedules device discovery at the same time, the system will accept only one request for device discovery, and will send an error message to the other.


Note You will not be able to schedule a job using at (a UNIX scheduler command) if the bin username does not have permission to do so.

Completing Optional Device Discovery Tasks

Depending on your login level, you can complete the following optional tasks to prepare for device discovery:

Viewing Current Settings

To view your current settings for device discovery, select Tasks > Device Discovery > View Current Settings.

Viewing Discovery Status

To view the status of device discovery, select Tasks > Device Discovery > Discovery Status.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Wed Dec 15 14:36:45 PST 1999
Copyright 1989-1999©Cisco Systems Inc.