Use this window to view information about agents, and to
remove agents.
- Agent statuses
- OK - There are no problems with the agent.
- Initializing - The agent has already connected to the server
but it has not performed the capacity scan yet. Note that the time
after the initial connection, during which the agent is to perform
the scan, has not yet passed. Wait for the agent to perform the scan.
The time the agent has to perform the scan is set by means of the agentInitializationTime parameter
in the setagentconf command. By default, it is 60
seconds, the minimum is 0, and the maximum is 24 hours.
- Not connecting - The agent has not contacted the server
for a long period of time. You can view the last agent activity to
check the time of the last successful connection with that agent.
Note: You
can set the time after which the agent becomes inactive using the maxAgentInactivity parameter
of the setserverconf command. The default value is
1440 minutes (1 day).
- Incomplete - The agent cannot determine its virtualization
hierarchy. You can perform the following actions depending on the
agent's operating system:
- VMware ESX(i)- Configure the proper virtual machine (VM) manager
in the user interface or use the Common Inventory Technology enabler.
- HP Integrity VM - If you did not install the agent on a host operating
system, install it and wait until it uploads the capacity scan results.
If there is an agent installed, wait for the agent to collect information
about the virtualization hierarchy or run the tlmagent -hw command
to force the upload of the capacity scan results.
- Solaris Container/Zones or Logical Domain (LDOM) - Make sure that
the agent is installed in the global zone on control domain as well
as in other global zones.
- Missing software scan - The software scan results have
not been uploaded to the server within the grace period. This status
will last until the software scan results are received.
- Missing capacity scan - The agent still has not performed
the capacity scan even though the time after the initial connection
to the server, during which the agent is to perform the scan, has
passed. Check if the agent communicates with the server, or run the
scan manually, using the tlmagent -hw command.
- Unknown - There is one or more duplicate agents. These
agents share the same host name, operating system, operating system
version, and physical host. This may happen when, for example, the
agent is reinstalled on the same system with a different agent ID.
- Failed - There are some problems with the agent.
- Version
- Refers to the agent version. If a warning icon appears, it means
that a given agent is not capable of gathering the necessary data
to support subcapacity licensing because its version is either 2.3
or 7.1 on the x86 instruction set architecture. To solve this problem,
upgrade to version 7.5, or use full capacity licensing.
- Scan group types
- Standard - a set of machines with installed agents. You
can schedule scans on them and gather scan results automatically by
means of the server.
- Stand-alone - a set of machines without installed agents.
You have to manually generate the scan scripts and use them to perform
scans on these machines. You also have to upload the scan results
manually to the server.
Note: By default, two scan groups marked as default are
created: one pertaining to the standard type and one to the stand-alone
scan group type. They are used by new agents when they connect to
the server for the first time if the scan group set in their configuration
file is not present in the system.
- This column is not visible if you have only standard scan groups
in your infrastructure. If you perform the stand-alone scan and import
its results to the server, the column will indicate to which group
type a given agent belongs.
- Network Address
- The network address is unknown when the host name of a
given machine is empty and when the agent is not able to retrieve
the IPv4 address during the first connection with the server. The
situation will be fixed after the first capacity scan.
- Last Expected Software Scan
- Shows the time of the last scheduled software scan for the scan
group to which a given agent belongs. The rest of agents from the
scan group have the same value in this column.
Tip: If
there are problems with the software scan, you can compare the value
in this column with the one in the Last Successful Software
Scan column to see for how long the scans have not been
uploaded to the server. The next step is to check whether the server
receives the scan results. To do that, run the scan manually using
the tlmagent -s command.
- Last Successful Software Scan
- Shows the time of the last successfully performed software scan.
You can sort the data in this column to check if there are any dates
older than the scheduled and expected time.
- Last Agent Activity
- Indicates the last time that the agent has contacted the server.
To view the description of actions that
you can perform with the table, see Table actions list.
- Download as PDF
- Downloads the whole table as a single document in the PDF format
for saving. The format retains the filtering and sorting performed
on the table. Note that the PDF format has a limited capacity so it
may not be possible to create if for too large tables.
- Download as CSV
- Downloads the whole table as a single document in the CSV format
for saving and editing. The format retains the filtering and sorting
performed on the table. It has no limitations as far as the number
of rows is concerned. You should use a spreadsheet application to
open it.