Read me

By default, VMware ESX kernel logging level is set to ‘6’ to print
all the kernel messages with severity higher than ‘information.’
Reduce it to ‘4’, so that messages with severity, ‘error,’ and above
get printed to the console.
To do this, execute the following command as a ‘root’ user:
/proc/sys/kernel/printk.
* A Security Key Identifier can contain numerals, lowercase alphabets,
uppercase alphabets, non-alphanumeric characters (except space),
or a combination of any of these.
Note: If you have used the special characters ” \” (forward slash)
or “ ‘ ” (single quote) in the Security Key Identifier, they are
displayed as “_” (underscore) on the Change Security Key page and
Import Secured Foreign Configurations page.
This is applicable only to the Security Key Identifier and
not to the Passphrase.
* Storage Management does not support creating or importing of
sliced spanned virtual disks on the controllers that do not
supported PERC 7.1 firmware. You cannot create RAID 10, RAID 50,
or RAID 60 in sliced manner.
If you create sliced spanned virtual disks using another application
and attempt to import the same using Storage Management,
the behavior cannot be predicted.
* If Storage Management displays a path failure message for a Logical
Connector after a reboot, use the "Clear Redundant Path View"
provided in the "Change Controller Properties" controller task and
restart the system.
NOTE: Use this command only if you have intentionally removed the
multipath connection during reboot of the system.
* In the VMware ESX 3.5 and ESX 4.0 environment, when you create a
virtual disk using Storage Management, you may see an error message
"The task failed to complete : The create virtual disk task was
successful but the operating system may not be aware of the new
virtual disk." However, the virtual disk is available for all
operations on rebooting of the system.
* On VMware ESX4 Classic and embedded operating systems, after creating
a new virtual disk, the device name does not appear. In this case,
the operating system is not aware of the newly created virtual disk.
To avoid this issue, refresh the browser or reboot the server
after creating the virtual disk.
* Patrol Read is not supported on SSD media. The Patrol Read feature
will fail for any controller that has SSD media on a virtual disk.
* Hotplug of enclosures takes time to enumerate the enclosure and
its components. During this time, there is a delay in the
response time of tasks, such as displaying the physical disks on
the physical disk page and in the virtual disk selection page.
* All virtual disks from the SAS/iR controller display the name
"IR Virtual Disk" on the "Preview" page. On successful import,