Release Notes

● JIT-10452 (BITS236815): Occasionally, the virtual disk creation process on PERC 9 hardware controllers may fail on GUI
and CLI. Workaround: Restart the server to resolve this issue.
● BITS055347: On systems running the ESXi 5.1 or later operating system, the “Device Name” for all virtual disks will be
displayed as a blank. This is an expected behavior on systems running the ESXi 5.1 or later operating system.
● JIT-8321 (BITS220411): Unable to create Partial Secure virtual disk using the GUI when all the available SEDs are selected.
This operation will work if any other physical disk, which is not a part of any virtual disk, is connected.
● JIT-11205 (BITS242664): When a physical disk, which is a part of multiple partial virtual disks, is reinserted into the
system, the status of the partial virtual disks will be displayed on Storage Management after a short delay.
● JIT-8442 (BITS221272): Few enclosure alerts such as Enclosure power on/off and Fan removal, does not appear if the
enclosure is connected to the server using a SAS 12 Gbps HBA card. Restart Data Manager Service to update component
status.
● JIT-10933 (BITS240247): Storage Management does not display the Device name on a system where there more than 300
virtual disks.
● JIT-16919 (BITS270856): On Precision 7910 running a client operating system (for example, Windows 8.1 x64), the PERC
9.3 driver version is displayed as outdated and a yellow bang is shown on such hardware configurations. This issue does not
cause any functionality limitation.
● JIT-43557 : In Split Mode, Slot occupancy report displays inaccurate empty slots when there are no drives connected to
the backplane. The report shows the message empty slots interchanged between controller. This issue occurs for the server
with no drives attached to the backplane in split mode only. Slot occupancy report works fine as expected for servers with a
minimum of one drive.
● JIT-52091: Cryptographic erase operation might take longer time to be visible in the dropdown list for the ISE Capable
SATA SSDs after this operation is done.
● On a PowerEdge server with maximum configuration of 2 populated enclosures connected to the PERC hardware controller,
the user can experience a delay in response.
● Unable to create Partial Secure virtual disk using the GUI when all the available SEDs are selected. This operation will work if
any other physical disk, which is not a part of any virtual disk, is connected.
● JIT-58147: In the BOSS-S1 controller properties, slot ID is displayed as "Embedded".
● If the background IO is in progress, "Prepare to Remove" operation for the NVME devices might fail.
● From 14G onwards, no Channel/Connector information will be displayed under “PCIe SSD Subsystem”. Enclosure/Backplane
will be directly connected to the “PCIe SSD Subsystem”. There is no change in the display of “NVMe Devices ( Arraydisk )
and Add-On Card ( HHHL Card )”. NVMe Devices ( Arraydisk ) will be displayed under “Enclosure / Backplane” whereas
Add-On Card ( HHHL Card ) will be displayed under “PCIe SSD Subsystem”.
● JIT-60971 : In OMSA, the empty slots in slot-occupancy report is not displayed after "prepare to remove" operation is
performed on the servers with one or more PCIe Backplane.
● JIT-63561 : On YX4X generation of PowerEdge servers, while doing the "Reconfiguration" operation, "Auto Configure
RAID0" option is listed in OMSA under H730P controller's "Available tasks". It happens during RAID level migration from
RAID1 to RAID0.
● JIT-71918: On YX4X generation of PowerEdge servers when connected with two SAS 12Gbps controllers in Slot4 & Slot5
and each controllers are connected with separate MD1400 enclosure, both Enclosure EMMs are listed under “Connector 0”
and no device is listed under “Connector 1 ”. Slot-4 SAS 12Gbps controller is connected with two redundant EMMs which
are listed in “Connector 0”. Slot-5 12Gbps controller is also connected with two redundant EMMs, but both are listed under
“Connector 0”.
● JIT-71919: On YX4X generation of PowerEdge servers when connected with two SAS 12Gbps controller in Slot4 & Slot5
and each controllers are connected with separate MD1400 enclosure, with two redundant cable i.e. EMM0 & EMM1, then
with redundant EMM both enclosures are listed for EMM0 & EMM1, but physical disks are not displayed for EMM1. Slot-4
SAS 12Gbps controller is connected with two redundant EMMs – Here both EMMs are listed under “Connector 0”, and for
EMM0 physical Disk is listed and for EMM1 no physical disks are listed. Slot-5 SAS 12Gbps controller is connected with single
EMM (ie.EMM1) – Here one EMM0 is listed under “Connector 0”, and for EMM1 physical Disk are listed.
● JIT-78857: Successful Prepare to remove and reinsertion operation on a drive for 3-4 times, will result in all the drives
getting removed and inserted back in ESXi 6.5 U1 operating system.
● JIT-79925: On YX3X generation of PowerEdge servers, OMSS reports for PCIe Link Speed is negotiated and maximum link
speed/width shows '0' for Slot 1 device.
● JIT-76259: EMMI alert description for Dedicated hot spare assigned physical disk should contain meaningful alert
description instead of the statement, This alert is provided for informational purposes.
● JIT-72304 : Able to assign lesser capacity physical disk as a DHS to the virtual disk created with physical disk having higher
capacity.
● JIT-80085: The alert descriptions, in the online help, for Set Available Spare Warning Threshold and Set Available Spare
Critical Threshold show "The Available Spare Warning Threshold for PCIe SSDs is set to %1" and "The Available Spare
15