Release Notes

Work around: Restart sfcbd service.
● JIT-108887: On Storage Management, observes intermittently malformed alert log showing “XML Data generated for the
selection made is not well formed” on systems running ESXi operating system.
Work around: Restart sfcbd service.
● JIT-119082 : On multipath mode, if clear redundant path option is performed immediately after removing the enclosure
cable, few minutes of delay is observed on Server Administrator GUI to refresh.
Recommendation : It is recommended to wait for the Redundant path broken alerts before performing the clear redundant
path. If in case Server Administrator page delay is observed, wait for few minutes to return to the normal state page or
restart the service.
● JIT-120251: The foreign physical disks connected to the system, on reaching the maximum number of supported virtual disk
by the controller is displayed on the Import Preview page as Orphan Drive.
● JIT-117872: On performing the unblink operation on physical disk connected to 12Gbps SAS HBA, observing both health and
activity LEDs light turn off.
● JIT-121226: Storage Management is enumerating connector health status as HHHL AIC status in SWRaid NVMe
configuration. Correct health status of HHHL card is seen on HHHL enumeration page.
● JIT-121358: The Cryptographic erase capable for SATA SED drives is displayed as no in the physical disk attribute. However
the physical disk task will have the ‘Cryptographic erase’ operation and there is no functionality impact.
● JIT-125130: On deleting the encrypted virtual disk created with SED disks on EKM enabled controller, the ‘Encrypted’
physical disk property attribute of SED disks is shown as ‘Yes’ instead of ‘No’.
● JIT-125128: When an encrypted virtual disk, created on server with EKM enabled controller, is hot plugged in a server with
non-EKM or LKM enabled controller, the foreign configuration wizard shows blank page instead of listing all the foreign
configurations.
● JIT-128978 : When there is failed virtual disk in the same controller the Import foreign configuration on controller’s task,
does not list the available degraded virtual disks to import, recover or clear. The list can be observed after failed virtual disk
deletion.
● JIT-136314: The NVMe device protocol for Intel NVMe P4800x devices is displayed as NVMe 1.1 instead of NVMe 1.0 on
supported Linux distros .
● JIT-147761: Blink and unblink operation under virtual disk tasks in SWRAID is blocked, if any of the participating physical disk
is HHHL add in card. Blink and unblink operation is also blocked for Non Raid HHHL add in card virtual disk.
● On BOSS and SWR controller the failed alert for the physical disk part number will be displayed as NULL.
● Storage Management does not allow creation of 240 virtual disks, if spanned virtual disks are present in system.
● On UI if the submit button is clicked more than once an internal error may occur, but the task will be performed successfully.
● JIT-146959, JIT-151162: On HBA345 controller the Slot Occupancy Report may show an incorrect amount of drive slots
depending on server model and chassis.
● On PERC and HBA Controller PDR16,PDR51,PDR7 and PDR22 events are generated once in 24 hours.
● On PERC and HBA Controller use a single event PDR16 for the events PDR16 and PDR19.
● JIT-151771: On Software RAID controllers, while creation of multiple partial spanned RAID-10 virtual disks, the physical disks
SATA or NVMe belonging to a span in one virtual disk. This might be distributed across the spans for another virtual disk
formed on the same disk group.
● JIT-151463 : On RHEL 7.7 and SLES 15 SP1 the slots occupancy report does not display the empty slot available for HBA330
controller.
● JIT-153490 : On PowerEdge R7515 system with 8 SAS or SATA and 16 NVMe backplane configuration, the slot occupancy
report for hardware PERC controller displays as 12 slots instead of 8 slots that are connected to hardware PERC controller.
● JIT-143512: The EMM alert generation is delayed if there are failed drives present in the enclosure.
● Export log operation may fail for failed state drive.
● Part Number, Serial No, Product ID, Vendor ID, Firmware Revision, Sub-vendor ID, Model Number values may not enumerate
for failed state drive.
● JIT-162168 (CR): Sometimes when the Toshiba NVMe drive on the SWRAID controller is connected (and is part of a Virtual
Disk), or a failed NVMe drive is present in the system. There can be multiple PDR211 alerts that are logged in the alert log
page. The logs can lead to delayed of response on the GUI.
● JIT-161708 : If the data transfer is not performing on M.2 drives while performing hot-plug out operation, then after hot
plug-in back the same, the virtual disk rebuild alert will not be generated. The virtual disk status will change from degraded to
online.
● The Device name field of NVMe drives is displayed as char device name on PCIe subsystems running on Linux operating.
● JIT-154358: On S130 and later, any change in read and write policy values while creation of virtual disks does not reflect on
virtual disk. Use Change policy virtual disk task for changing these policies.
● JIT-155954: While hot-plug-in mulitple drives of MX5016s physically, wait for each insert alert to avoid the wrong
enumeration.
18