Collecting data from an agentless data source
Chapter 4 Configuring, managing, and customizing Perceive 141
In this scenario, agentless computers are discovered as follows:
■ The discovery returns five systems, the four agentless systems and the proxy host.
■ History data for the proxy host is retrieved using that proxy host name.
■ History data for the other four systems is be retrieved using the computer names
and the proxy host name.
Because only one address was specified for the data source, the discovery returned
the four systems specified in the proxy configuration file on the proxy host as
agentless systems (not as non-proxy systems, even though an agent might have been
be running on those systems).
User scenario: range of IP addresses
If, instead, you had entered a range of IP addresses to discover agentless systems, an
agent is discovered within the given IP address range, and it is added to the set of
discovered systems, replacing a proxy listing if necessary. For example:
IP address range: 172.31.11.4 to 172.31.11.6
172.31.11.4 - an agent and proxy host which knows about systems 172.31.11.5,
172.31.11.6, and 172.31.11.18
172.31.11.5 - an agentless system
172.31.11.6 - an agent, but not a proxy host
172.31.11.18 - an agent, but not a proxy host
In the previous example with the specified IP addresses, Perceive discovers the agent
on address 172.31.11.4 and adds it to the set. Next, Perceive adds addresses
172.31.11.5, 172.31.11.6, and 172.31.11.18 to the set as agentless computers. Because
172.31.11.5 does not have an agent, it is left alone. Because 172.31.11.6 is running an
agent (and it is more efficient to communicate directly with agents, if possible), the
proxy listing for 172.31.11.6 is replaced with the agent listing. Even though
172.31.11.18 is running an agent, Perceive uses its proxy listing, because its IP address
is outside the search range.
For more information on agent-less data collection through a proxy host, refer to the
PATROL for Performance Manager for Windows and UNIX Collecting Data guide.
NOTE
You can also access agentless data from proxy hosts through a firewall by editing the
config.xml file. For more information, see the following section, “Firewall-enabled
remote agent data source access” on page 142.
