Release Notes
•
Physical disk properties such as Manufacture day, Manufacture week, and Manufacture
year are available for SAS drives only.
•
Creating many sliced span virtual disks using the spun-down drives through the
command line or GUI result may be delayed.
Workaround: After creating one sliced span virtual disk, wait for some time to create the
next sliced span virtual disk.
•
In ESX4 Classic,’ deprecated SCSI ioctl' message is displayed on the console.
Description: In VMware ESX 4.0 Classic system, the following warning message(s) is
displayed on the console: “Program dsm_sa_datamgrd is using the deprecated SCSI ioctl,
Please convert it to SG_IO.” This is a kernel warning message displayed when storage
operations are in progress. This is only a deprecation warning and not an indication of a
failing operation.
Workaround: Reduce the kernel logging level. 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.
•
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 while rebooting
the system.
•
In the VMware ESX 4.x and ESX 5.x 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 the
system.
•
Patrol Read is not supported on SSD media. The Patrol Read feature fails for any controller
that has SSD media on a virtual disk.
•
Hot plug of enclosures takes time to enumerate the enclosure and its components. During
this time, there will be 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, another name is assigned to these virtual disks and
the "IR Virtual Disk" name is not displayed on the "Preview" page.
•
Storage Management does not permit connecting the first enclosure in single path and
attaching the subsequent enclosures in multipath. All enclosures must be connected in
multipath to enable the multipath view.
•
An error message may not appear when "Import Foreign Configuration" task is not
successful.
Description: The "Import Foreign Configuration" task can only import virtual disks that
have consistent data. A virtual disk with inconsistent data cannot be imported. When
importing multiple virtual disks in a single operation, however, the "Import Foreign
Configuration" task may report successful completion even when inconsistent virtual disks
are present and have not been imported successfully.