Known Issues Third-Party Hardware and Software
Total Page:16
File Type:pdf, Size:1020Kb
Known Issues Third-party hardware and software September 2021 This document contains all Third-party Hardware and Software that, when used together with SANsymphony, may cause unexpected behavior or impact accessibility, performance, and function. Known issues that apply to DataCore's own products are in their own release notes which are all available from the DataCore Support website. Also see Minimum Hardware Requirements https://www.datacore.com/products/software-defined-storage/tech/prerequisites/ Qualified Hardware Components http://datacore.custhelp.com/app/answers/detail/a_id/1529 The authority on real-time data Continued from previous page Table of Contents Changes made to this document 4 Broadcom 15 BCM57xxx 15 Intel S4510 and S4610 SATA SSD (only 1.8 TB and 3.84 TB are affected) 4 Emulex 15 Applies to all 4 Oce11102-NX/Oce10102-NX 15 Disclaimer 5 Hewlett Packard 15 Server hardware 6 All Converged Network Adaptors (CNAs) 15 CN1000Q 15 Microsoft Windows (general) 7 NC55* SFP 10 Gigabit Adaptors 16 Windows 2016 update regression 7 NC375x/NC382i/NC52x Gigabit Adaptors 16 Windows 2016/2012/2012 R2/2008 7 ProLiant BL460c (Gen10) server blades 16 Windows 2012/2012 R2 only 8 Windows 2008 R2 only 8 IBM 16 49y4250/49y7950 10GiB Adaptor 16 Cisco 9 49y4250/49y7950 10GiB Adaptor 16 Unified Computing Systems (UCS) 9 Intel 17 Fujitsu 9 x710 Chipset 17 Primergy ServerView Control Service 9 Primergy Server Agent 9 Nvidia Mellanox 18 ConnectX SmartNICs - general 18 Hewlett-Packard 9 ConnextX-5 18 Servers with Windows 2012/2012 R2 9 ConnextX-3 18 Servers with Windows 2008 10 All PCI Express 2.0 ConnectX Adaptors 18 Servers with Xeon 7500 or E7 Processors 10 ProLiant G9 Servers 10 Storage hardware 19 Automatic Server Recovery (ASR) 10 C-Class BladeSystems 10 Previously used Disk Pool disks 19 Integrated Lights Out (ILO) 10 Insight Management 11 NVMe Storage 19 HPE Storage Devices 11 All NVMe storage 19 Virtual Connect 11 Adaptec 20 IBM 12 maxView Storage Manager 20 IPMI Watchdog Timer (IBM) 12 BladeCenter and System x 12 Allied TeleSyn 20 Gigabit Media Converter - MC1000 series 20 Lenovo 12 ThinkSystem 12 Areca 20 Fibre channel adaptors 13 ARC-188x 20 Emulex 13 Dell EMC 20 Third-party Process Logout (TPRLO) 13 MD 36xx/38xx FC 20 All 16GB (including OEM) 13 Clariion AX150/AX4 20 All 8GB (including OEM) 13 Compellant SC series 20 RealSSD (Micron) 20 PowerEdge 21 QLogic 14 SAS Arrays using Seagate disks 21 All models (including OEM) 14 All 16GB (including OEM) 14 Fusion-io 21 Using SANsymphony’s Deduplication 21 Hewlett-Packard 14 VSL Ram calculations 21 HP StoreFabric 84Q 14 Network adaptors (inc. iSCSI) 15 Hewlett Packard 22 EVA 4000/8xxx 22 Continued from previous page Table of Contents HPE MSA 1040/2040 22 All Switch Vendors 27 P440AR 22 Registered State Change Notifications 27 SAS Storage systems 22 Brocade 27 Hitachi 22 Fabric OS 7.x 27 Virtual Storage Platform (VSP) F and G Fabric OS 6.x 27 series 22 Cisco Systems Inc. 28 IBM 23 Nexus and MDS Series 28 DS3400/3500 23 DS4100 23 QLogic 28 ServeRAID M5100e 23 IO StreamGuard 28 ServeRAID M and MR10 Series 23 System x 23 Third-party software 29 Intel 23 Anti-Virus Software 29 NVMe 23 Applies to all 29 Lenovo 24 Broadcom 29 Intel S4510 and S4610 SATA SSDs 24 Advanced Server Program (BASP) 29 Micron M.2 and SSD drives 24 Symantec 29 LSI 24 Network Threat Protection (NTP) 29 Nytro WarpDrive 24 McAfee 30 Micron Technology Inc. 24 VirusScan 30 RealSSD 24 Oracle 31 NetApp 25 Automatic Storage Management (ASM) 31 All E Series arrays 25 Automatic Load Balancing (ALB) 25 Veeam 31 Backup Management Suite 31 Netgear 25 Changed Block Tracking 31 ReadyNAS 3100 25 Previous changes 32 PureStorage 25 All models (including OEM) 32 All FlashArray storage 25 Skyera 25 skyHawk 25 Toshiba OCZ 26 Z-Drive 26 Transtec 26 Provigo 26 Violin Memory 26 All PCIe Flash Memory Cards 26 X-IO 26 ISE 1 Storage Arrays 26 ISE 2 Storage Arrays 26 G3 and G4 Storage Arrays 26 Switches – FC, FCoE and IP 27 Changes made to this document The most recent version of this document is available from here: https://datacore.custhelp.com/app/answers/detail/a_id/838 All changes since February 2021 Added Network adaptors (inc. iSCSI) – Nvidia Mellanox ConnectX SmartNICs Affects the DataCore Server DataCore have had reports by customers using ConnectX-5 SmartNICs configured for speeds of 100G behaving erratically – the symptoms being IO stalls and continuous disconnects /reconnects between the Target and Initiator - when used for iSCSI connections to or from a DataCore Server. It is also not clear if other models of the ConnectX SmartNIC family (4, 6 and 7) will also show this same problem when using speeds of 50GB or more. DataCore are recommending reducing the speed of the NIC to 25GB as this has been shown to resolve the problems stated above. We are currently investigating this problem. Storage Hardware – Lenovo Intel S4510 and S4610 SATA SSD (only 1.8 TB and 3.84 TB are affected) Affects the DataCore Server After 1700 hours of cumulative power-on idle time users can see critical errors under certain use conditions. The drive may report BAD_CONTEXT_2033, BAD_CONTEXT_1042 or excessive LBA mismatch (SMART attribute B8h) after. Once the error code is triggered, the drive will fail to respond on the bus. Search Lenovo’s own support website for Document ID: HT507987 (last updated Sept 2019) Updated Third Party Software – Anti-Virus software Applies to all When installed on a DataCore Server Exclude the following on a DataCore Server: • The DataCore Executive process – Dcsx.exe For previous changes made to this document please see page 32 Page | 4 Known Issues - Third-party hardware and software Disclaimer DataCore Software cannot be held responsible for any incorrect information regarding third- party products or assumptions made that DataCore Software has direct communication with any of the third-party vendors regarding any of the issues listed here. DataCore Software always recommend that users contact the third-party vendor directly to see if there are any updates or fixes since they were documented here. DataCore always recommend that the latest software drivers, firmware and/or BIOS are used on any SAN component (unless of course they are listed here as not working as expected). A few of the issues documented here were discovered during DataCore’s own testing but most have been reported by end users and then subsequently confirmed by the third-party Vendor. Known issues that apply to DataCore's own products are in their own release notes which are all available from the DataCore Support website. Page | 5 Known Issues - Third-party hardware and software Server hardware Some of the information in this section may overlap with known issues reported in the section Storage hardware on page 19. Also see Minimum Hardware Requirements https://www.datacore.com/products/software-defined-storage/tech/prerequisites/ Best Practice Guidelines for SANsymphony https://datacore.custhelp.com/app/answers/detail/a_id/1348 Page | 6 Known Issues - Third-party hardware and software Server hardware Microsoft Windows (general) Windows 2016 update regression Affects the DataCore and Host Servers Unexpected BSOD when using MPIO Disk Devices after applying updates between Nov and Dec 2020. A crash in Microsoft’s mpio.sys driver may occur when two or more paths to an MPIO disk device are removed, unexpectedly at the same time. This may affect: • Hosts that being served Virtual Disks that are being managed either by Microsoft’s own MPIO or DataCore’s Windows Integration Kit both of which use the Widows mpio.sys driver. • DataCore Servers that are using iSCSI Mirrored Virtual Disks – where SANsymphony utilizes the mpio.sys driver. Fibre Channel mirrored Virtual Disks are unaffected. This issue was fixed in an update issued in January 12th, 2021. Also see January 12, 2021—KB4598243 (OS Build 14393.4169) https://support.microsoft.com/en-us/help/4598243 Windows 2016/2012/2012 R2/2008 Affects clustered, hyper-converged DataCore Servers Do not use the DataCore Loopback port to serve mirrored Virtual Disks to Hyper-V Virtual Machines This known issue only applies when SANsymphony is installed in the root partitions of clustered, Hyper-V Windows servers where virtual disks are ‘looped-back’ to the Windows Operating system for use by Hyper-V Virtual Machines. Also see: https://docs.datacore.com/SSV-WebHelp/hyperconverged_virtual_san_software.htm A limitation exists in the DataCore SCSI Port driver - used by the DataCore Loopback Ports - whereby if the DataCore Server providing the ‘Active’ cluster path is stopped, the remaining DataCore Server providing the ‘Standby’ path for the Hyper-V VMs is unable to take the SCSI Reservation (previously held by the stopped DataCore Server). This will result in a SCSI Reservation Conflict and prevent any Hyper-V VM from being able to access the DataCore Disks presented by the remaining DataCore Server. In this case please use iSCSI connections as ‘Loopbacks’ for SANsymphony DataCore Disks presented to Hyper-V Virtual Machines. Affects the DataCore Server BitLocker Drive Encryption This server feature must not be installed on a DataCore Server as it will prevent SANsymphony’s Disk Pool feature from working. Page | 7 Known Issues - Third-party hardware and software Server hardware Windows 2012/2012 R2 only Affects the DataCore Server SAS boot drives Restart problems after Microsoft update rollup 2919355. See: https://support.microsoft.com/en-gb/help/2966870 (Last update 2015) A regression in a Windows March 2017 update This caused a TCP Port 'exhaustion' when one or more Microsoft iSCSI initiators cannot connect to a Target (e.g.