Storage Resource Manager Enterprise Edition Installation Guide

Storage Resource Manager Enterprise Edition C–27
SRM Troubleshooting Guide
“Computer Could not be Scanned,” “Scan Time Exhausted.”
The UNIX agent expects to be able to complete a computer scan in less than 10
minutes. For very large or old and slow systems, this may not be adequate, especially
on AIX. The maximum value can be overridden via agentconfig file configuration
directive COMPUTERSCAN_TIMER, with the value specified in seconds.
Note that the agent sets an alarm timer to limit its execution to just the estimated scan
time; it will then terminate and return a Scan Time Exhausted error to SRM.
“SRM UNIX Agent Failed: <servername> Reported SRM Server
is not Present in the Agentconfig File.”
There are a couple of possibilities:
• The entry for the SRM server somehow got deleted from the agentconfig file
• There was a problem with the nameserver used to resolve host names. The agent
attempts to look up the IP address of the SRM server connecting to it based on the
server name in the agentconfig file. A nameserver failure, which is often a
transient event, can cause this to occur.
“srmagent” Processes on Various UNIX Systems Which have
been in Execution for a Long Time
It is generally safe to kill these processes, given that other agent processes apparently
are starting and stopping OK. One known circumstance that can cause agents to hang
in execution is that the SRM server went down in a non-graceful way while agents
were trying to post scan results. The agent thinks it is still connected to the SRM
server, and is never told otherwise.
One way to see if this is occurring is to enter at the shell prompt on the UNIX system
over a period of time:
netstat –a | grep <SRM_Server>
If there are persistent lines showing an ESTABLISHED connection, this is likely the
situation.