HP StorageWorks P9000 Replication Manager Software 7.1.1 User Guide (TB584-96030, September 2011)

4. Confirm that user authentication was successful. Make sure the P9000 RAID Manager
authentication files were created using the same account names (with which authentication was
performed) as the user names contained in the file names that execute the commands.
Example authentication file of local system account:
C:\HORCM\usr\var\host01_SYSTEM_53038
Example authentication file of user account for executing Application Agent service:
C:\HORCM\usr\var\host01_Administrator_53038
5. To perform discovery of the new applications, click Refresh Hosts in the Applications view.
If a virtual command device fails to call the Device Manager Agent
The following message might appear in a configuration that uses a virtual command device to manage
copy pairs:
Failed to call the Device Manager agent (Agent error code: RPM-03216)
[RPM-01629]
This message appears if there is an authorization problem:
• The user is not authenticated in the storage system when an SVP is used as a virtual command
device.
• The user is not authenticated in the storage system when the Virtual Command Device server is
used as a virtual command device and the user authentication setting of the command device is
enabled.
In either case, first make certain you are using a supported version of P9000 RAID Manager. In
addition:
• When an SVP is used as a virtual command device, authenticate the user in the storage system.
• When a virtual command device server is used, disable the user authentication setting of the
command device or authenticate the user in the storage system.
For details about how to authenticate a user in the storage system, see “Performing user authentication
for replica operations” on page 245.
P9000 RAID Manager response time and virtual command devices
When managing copy pairs in a configuration that uses copy groups defined in storage or a virtual
command device, the response time for P9000 RAID Manager commands is much slower than for a
physical command device. This time lag can cause the Device Manager to terminate with an error.
For best results, set the following properties file values as described here.
Device Manager agent properties:
• Set the value of the server.agent.rm.moduleTimeOut property of the server.properties
file to 1800 or higher.
• Set the value of the agent.rm.TimeOut property of the agent.properties file to 1800
or higher.
After changing these properties, restart the Device Manager agent service.
Replication Manager properties:
• Set the value of the hdvmagtif.MaxPollingCount property of the agentif.properties
file to 100.
Managing pair life cycle246