Monitoring discovery agent status
As the discovery progresses, different discovery agents are called to retrieve device and connectivity data from discovered devices. This data will later be used to build the network topology. You can use the Discovery Status GUI to track overall and detailed status of the discovery agents.
About this task
Discovery agents run in the following order. Let's
assume that the Ping finder has just verified the existence of the
device 10.40.230.1, in our Class B subnet.
- After the Ping finder has verified the existence of IP address 10.40.230.1, the Details agent is called to retrieve basic information from this device.
- Once the Details agent has retrieved information from the IP address 10.40.230.1, the AssocAddress agent is called to retrieve all the IP addresses associated with 10.40.230.1. If the associated IP addresses have not yet been discovered and are in scope, then the IP address is passed to the Ping finder so that the device existence can be verified.
- Meanwhile other agents are called to interrogate the IP address 10.40.230.1. For example, this IP address is a router, so the IpRoutingTable agent is called to retrieve information from the routing table of router 10.40.230.1 and to feed back connected devices to the Ping finder. More precisely, 10.40.230.1 is a Cisco router within a BGP network, so the CiscoBGPTelnet agent is called to retrieve BGP-related data from the device.
Note: The Details agent
and the AssocAddress agent are the only discovery agents that interrogate
every device in scope. The IP address counts for these agents are
therefore always higher than those of the other agents.
As
you monitor discovery agent progress, some of the key questions to
ask are the following?
- Are all agents running okay? Have any agents crashed? If so, which IP address might have caused the agent to crash.
- Which agents are taking a long time to complete and which IP address appears to be causing this delay?
- Which agents are holding up a discovery phase and preventing the phase from completing? For example, which agents are holding up the Interrogating Devices phase?
- How many IP addresses does a particular agent, for example, the Details agent, still have to work on? How far is the agent through its work?
- Which IP addresses were found late in the discovery?
Procedure
Results
- Are all agents running okay? Have any agents crashed? If so, which IP address might have caused the agent to crash.
- Which agents are taking a long time to complete and which IP address appears to be causing this delay?
- Which agents are holding up a discovery phase and preventing the phase from completing? For example, which agents are holding up the Interrogating Devices phase?
- How many IP addresses does a particular agent, for example, the Details agent, still have to work on? How far is the agent through its work?
- Which IP addresses were found late in the discovery?