Storage Resource Manager Enterprise Edition Installation Guide

C–14 Storage Resource Manager Enterprise Edition
SRM Troubleshooting Guide
• The security key in the Agent registry is not configured correctly.
• The agent machine is down.
• There are name resolution issues.
• The SRM service on the Agent is not started.
• There are connectivity issues.
If you get a DWORD error, this usually means there was a security failure on the agent
when trying to authenticate the requesting user.
NOTE: This test contacts the agent as the SRM Server process would and the Agent
authenticates it against the SECURITY registry key. If you are logged into an account that does
not have access to this key, the test will fail. For a valid test you MUST be logged in via the SRM
Server service account.
UNIX Agent Test Scan
To allow easy stand-alone testing of the UNIX agent without communicating with an
SRM machine, a command line interface is provided:
./srmagent/srmagent –test scan_type
Where scan_type is one of the following values:
computer
file
newfail
segv
• Use of the “-test” option allows possible recreation of problems encountered
during an SRM-initiated scan.
• For the “file” scan, it is necessary to provide on STDIN (normally through
command line redirection) the set of necessary configuration information
necessary to drive the scan.
• The “newfail” scan type causes the agent to continue to try to allocate memory
using the C++ “new” operator, to test the correct handling of this event.
• The “segv” scan types causes the agent to trigger a segmentation violation
exception, to test the correct handling of this type of exception.
Output normally returned to SRM is written to STDOUT when the “-test” option is
employed. Additional informational messages written to STDERR may also appear;
when the agent is invoked from SRM these message are suppressed.