HP OneView for VMware vCenter - Manual (Page 130)

Cannot configure datastore block size
You cannot configure the block size for the VMFS-5 file system when creating a datastore in an
vSphere 5.x/ESXi 5.x environment.
Cause: When creating datastores using the VMFS-5 file system, VMware does not support values
other than 1 MB for the block size.
Cannot configure HP MSA array when using user-created account
When configuring HP MSA arrays, an Unable to Authenticate error occurs.
Cause: The WBI does not include an option to enable SMI-S when a new user is created. It has
an option to enable FTP, CLI, and WBI only. This is a WBI limitation.
Action: Use the CLI with the manage option to create the user.
For example: create user newUser level manage interfaces cli, ftp, smis,
wbi password password
Troubleshooting for VASA
For information about system alerts, go to http://www.hp.com/support/hpgt/3par and select
your server platform.
NOTE: If you are using HP 3PAR OS Software version 3.1.1 or lower, refer to HP 3PAR OS
3.1.1 Messages and Operators Guide for information about system alerts.
VASA Provider Registration Related Issue
If an error occurs during the VASA Provider registration process on the vCenter server, it might be
caused by one of the following issues:
•
The port used by Recovery Manager for the VMware installed host is being blocked by firewall
or antivirus software. By default, the VASA Web service uses port 9997 for communications.
The current port number can be obtained through the Admin Tool interface.
•
A proper SMS certificate has not been properly installed on the Recovery Manager for VMware
host prior to the VASA provider registration. See
“Registering an SMS Certificate for the 3PAR
VASA Provider” (page 24) for complete details.
Inspecting VASA Provider and vCenter Server Communication
VASA provider and vCenter server communications can be inspected by setting the log level to
"High" from the Configuration option from the VASA tab available from the Admin Tools. When
the log level is set to "High", the received soap requests and replied responses will be written to
the log file. Following are descriptions of the alarm and event messages that might be generated
and suggested actions for each.
Alarm Type Message
MESSAGE
(ID:300de) -{Info}
SUGGESTED ACTION
Refer to Alert Code 0x300de in HP 3PAR OS Message and Operator's Guide.
MESSAGE
(ID:300fa) -{Info}
130 Troubleshooting