HP StorageWorks XP Provisioning Manager User Guide (December 2005)

Troubleshooting 143
Table 11-2 Troubleshooting Information: Provisioning Manager Functions
Problem Cause Recommended Action
The current setting does not allow the
use of 2 GB or larger files.
If Solaris™ or HP-UX VERITAS™ File
System is being used, a setting for using
files that are 2 GB or larger is required.
Refer to the file system documentation
and enable the use of large files by a
method such as executing the fsadm
command with the -F vxfs -o
largefiles option specified.
A file that is 2 GB or larger cannot be
created.
The file size exceeds the resources
allocated to the user.
Refer to a section in the OS
documentation, such as the ulimit
command reference, and check whether
file sizes are limited by the allocated user
resource limits.
To create a file that exceeds the allocated
limit, increase the allocated limit.
Provisioning Manager cannot be
started from other Command View XP
AE Suite software.
The URL for Provisioning Manager is
not properly registered in Common
Component.
Change the URL for Provisioning
Manager by using the hcmdschgurl
command of Common Component. For
details on the hcmdschgurl command,
see the manual HP StorageWorks
Command View XP Advanced Edition
Device Manager Server Installation and
Configuration Guide.
Table 11-3 Troubleshooting Information (Logging In)
Problem Cause Recommended Action
The following message is displayed on the
GUI window: “A connection with the
Provisioning Manager server could
not be established”
Processing to start the Provisioning
Manager server is being performed.
Wait a while, and then retry
the operation.
An attempt to start the Provisioning
Manager server failed because the
Device Manager version does not
match the prerequisite version for
Provisioning Manager.
Install the Provisioning
Manager that starts the
installed Device Manager
version.
For details about prerequisite
program products, see the HP
StorageWorks XP Provisioning
Manager Installation and
Configuration Guide.
The Provisioning Manager server is not
running.
Starting the Device Manager
server will start the
Provisioning Manager server.
Table 11-4 Troubleshooting Information: Host Information Collection
Problem Cause Recommended Action
Device Manager has not
been started on the target
host.
Start the Device Manager
agent on the target host.
Host information cannot be collected.
The Device Manager agent
setting is invalid.
Check the setting by
referring to the Device
Manager manual.