Known Issues: Third-Party Hardware and Software (Formerly Known as FAQ 1277)
Explore this Page
- Overview
- Change Summary
- Server hardware
- Known Issues
- Fibre Channel Adapters – Known Issues
- Network adaptors (inc. iSCSI)
- Storage Hardware
- Previous Changes
Overview
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 specifically to DataCore products are documented in their respective release notes, which are available on the DataCore Support website.
Refer to the following documentation for more information:
- Minimum Hardware Requirements
- Qualified Hardware Components FAQ documentation.
Change Summary
Changes since December 2021
| Added | Content Changes |
|---|---|
| Storage Hardware – Intel Optane - Persistent Memory (PMem) |
Added Affects the DataCore Server The PMem feature is not supported with SANsymphony. PMem has two different accessibility modes:
|
Disclaimer
DataCore Software cannot be held responsible for any incorrect information regarding thirdparty 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.
Server hardware
Some of the information in this section may overlap with known issues reported in the Storage Hardware section.
Refer to the following documentation for more details:
Known Issues
Unexpected BSOD when using MPIO disk devices after applying Windows 2016 updates
Issue: Unexpected BSOD when using MPIO disk devices after applying Windows 2016 updates (Nov–Dec 2020).
Affects: DataCore and Host Servers
Description: 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 using Microsoft MPIO or DataCore’s Windows Integration Kit.
- DataCore Servers using iSCSI Mirrored Virtual Disks (Fibre Channel VDs are unaffected).
Resolution: Fixed in January 12, 2021 update.
Reference: KB4598243
Loopback Port Causes SCSI Reservation Conflicts in Hyper-V Clusters
Issue: Loopback Port Causes SCSI Reservation Conflicts in Hyper-V Clusters.
Affects: Clustered, Hyper-converged DataCore Servers (Windows Server 2016/2012/2012 R2/2008)
Description: Do not use the DataCore Loopback port to serve mirrored Virtual Disks to Hyper-V virtual machines.
This issue applies when:
- SANsymphony is installed in the root partitions of clustered Hyper-V servers.
- Virtual Disks are looped back to the OS for Hyper-V VM access.
Due to a limitation in the DataCore SCSI Port driver used by Loopback Ports, the 'Standby' DataCore Server cannot take over SCSI Reservations when the 'Active' server is stopped, resulting in SCSI Reservation Conflicts and VM access failures.
Workaround: Use iSCSI connections as loopbacks for presenting SANsymphony Virtual Disks to Hyper-V VMs
Reference: Hyperconverged Virtual SANsymphony Software
BitLocker Prevents Disk Pool Operations
Issue: BitLocker Prevents Disk Pool Operations
Affects: DataCore Server
Description: This server feature must not be installed on a DataCore Server as it will prevent SANsymphony’s Disk Pool feature from working.
Restart Problems with SAS Boot Drives After Windows Update
Issue: Restart Problems with SAS Boot Drives After Update Rollup 2919355.
Affects: Windows 2012/2012 R2 only — Affects the DataCore Server.
Description: Restart problems occur after Microsoft update rollup 2919355.
Reference: KB2966870 (Last update 2015)
TCP Port Exhaustion Due to iSCSI Connection Failures
Issue: TCP Port Exhaustion Due to iSCSI Connection Failures
Affects: Windows 2012/2012 R2 only — Affects the DataCore Server
Description: A regression in a Windows March 2017 update caused a TCP Port 'exhaustion' when one or more Microsoft iSCSI initiators cannot connect to a target (e.g., because the DataCore Server is not available/shutdown or if there is a network problem preventing IP connections from being made).
Symptoms include:
- Logins to the DataCore Management Console will fail and an "Insufficient Winsock resources available …” error is displayed.
- The server is unavailable for any RDP and/or other network-based logins.
- SANsymphony Asynchronous Replication connections will fail.
Resolution: A fix was made available as of the July 2017 rollup.
Reference: Microsoft KB4025335
Remote Share Access Blocked After Jan 2019 Security Update
Issue: Remote Share Access Blocked After Jan 2019 Security Update.
Affects: Windows 2008 R2 only — Affects the DataCore Server
Description: A regression was introduced in Microsoft’s January 8, 2019 security update (KB4480970).
“Local users who are part of the local ‘Administrators’ group may not be able to remotely access shares.”
This affects DataCore ‘DcsAdmin’ user.
Symptoms include:
- Login to the DataCore Management Console will fail.
- DataCore Servers within the same Server Group will lose connection via SANsymphony’s ‘management LAN’ to other DataCore Servers in the group.
- SANsymphony Asynchronous Replication connections will fail to and from Replication Groups.
Resolution: A fix is available from Microsoft.
Reference: Microsoft KB4487345
Custom vNIC Settings Lost After Replacement
Issue: Custom vNIC Settings Lost After Replacement.
Affects: Windows 2008 R2 only
Description: When a new vNIC is created in place of an existing one, custom settings are lost.
Reference: Microsoft KB3125574 (Last updated 2018).
Memory Leak in Win32_Service WMI Class
Issue: Memory Leak in Win32_Service WMI Class
Affects: Windows 2008 R2 only
Description: The "Win32_Service" WMI class leaks memory in Windows Server 2008 R2.
Resolution: A Hotfix is available
Slow Performance on Windows 2008 R2 When Using Balanced Power Plan
Issue: Slow Performance on Windows 2008 R2 When Using Balanced Power Plan.
Affects: Windows 2008 R2 only
Description: Slow performance may occur when using the “Balanced” Power Plan on Windows Server 2008 R2.
Resolution: Possible workarounds documented by Microsoft.
Reference: Microsoft KB2207548 (Last updated 2017).
System Shuts Down After Modifying Battery Notification Level Policy
Issue: System Shuts Down After Modifying Battery Notification Level Policy.
Affects: Windows 2008 R2 only
Description: System shuts down after modifying the Critical Battery Notification Level Policy on Windows.
Windows 2008 R2 – Access Issues Due to KB4480970 Update
Issue: Remote Access Broken After Windows 2008 R2 Security Update (Windows 2008 R2 only).
Affects: DataCore Server
A regression was introduced in Microsoft’s January 8th, 2019 security update (KB4480970):
“Local users who are part of the local ‘Administrators’ group may not be able to remotely access shares.”
This affects DataCore’s ‘DcsAdmin’ user and symptoms include:
- Logins to login to the DataCore Management Console will fail.
- DataCore Servers within the same Server Group will lose connection via SANsymphony’s ‘management LAN’ to other DataCore Servers in the group.
- SANsymphony Asynchronous Replication connections will fail to and from Replication Groups.
Reference: Refer to Microsoft KB4487345 for details on the fix.
Advanced Format 4K Storage Incompatibility on Early SANsymphony Versions
Issue: Advanced Format 4k storage does not work with older SANsymphony versions.
Affects: Cisco Unified Computing Systems (UCS), DataCore Server.
Description: Advanced Format 4k storage does not work with SANsymphony versions 10.0 PSP 4 Update 1 or earlier.
Workaround: For earlier versions of SANsymphony with LUNs greater than 4TB, use multiple, smaller sized physical disks and format them using either 512 or 512e.
Fujitsu ServerView Control Service Delays DataCore Startup
Issue: Fujitsu ServerView Control Service Delays DataCore Startup
Affects: Fujitsu Primergy
Description: After any reboot of a DataCore Server, the ServerView Control Service will prevent SANsymphony’s DataCore Executive service from starting (manually or automatically) for about 20 minutes.
Workaround: Disable/remove this service if possible. If not, change the DataCore Executive service startup type to "Automatic (Delayed Start)" to delay until the ServerView service finishes.
Server Agent versions cause WMI issues
Issue: Server Agent versions cause WMI issues.
Affects: Fujitsu Primergy
Description: Earlier versions of the Server Agent caused problems with Microsoft WMI, resulting in connection issues with the SANsymphony Management Console.
Workaround: Use version 7.10.14 or later of the Fujitsu Server Agent.
BSOD on Hewlett-Packard Smart Array Controller with specific driver
Issue: BSOD on HP Smart Array Controller with specific driver.
Affects: Hewlett-Packard Servers with Windows 2012/2012 R2.
Description: Servers may Blue Screen if configured with an HP Smart Array Controller and the Windows Server 2012 HPCISSS2.SYS Driver Version 62.26.0.64.
Reference: Search Hewlett Packard’s Enterprise Support Center using keyword [c03793656] (Last updated 2014).
Excessive memory use by Hewlett-Packard Agentless Management Service
Issue: Excessive memory use by HP Agentless Management Service.
Affects: Hewlett-Packard ProLiant Gen8 Servers.
Description: HP ProLiant Agentless Management Service (AMS) may consume excessive amounts of system memory.
Reference: Search Hewlett Packard’s Enterprise Support Center using keyword [c04219029] (Last updated 2016).
NIC teaming memory leak
Issue: NIC teaming memory leak.
Affects: Hewlett-Packard Servers
Description: Some NIC teaming configurations may experience a memory leak up to 5MB/hour.
Reference: Search Hewlett Packard’s Enterprise Support Center using keyword [c04209163] (Last updated 2014).
Hewlett-Packard AMS Causes Excessive Memory Usage on Gen8 Servers
Issue: May Consume Excessive Amounts of System Memory on ProLiant Gen8 Servers.
Affects: Servers with Windows 2008; affects the DataCore Server.
Description: HP Agentless Management Service (AMS) Version 9.60 corrects this issue.
Reference: Search Hewlett Packard’s Enterprise Support Center with keyword c04219029 (Last updated 2015).
HP Gen8 Servers (Duplicate Reference): AMS High Memory Usage
Issue: HP ProLiant Agentless Management Service (AMS) May Consume Excessive Amounts of System Memory on ProLiant Gen8 Servers.
Affects: Servers with Windows 2008; affects the DataCore Server.
Reference: Search Hewlett Packard’s Enterprise Support Center with keyword c04219029 (Last updated 2016).
Xeon 7500/E7 Systems May Behave Unpredictably Without ROM Update
Issue: Xeon 7500/E7 Systems May Behave Unpredictably Without ROM Update.
Affects: Servers with Xeon 7500 or E7 Processors; Affects the DataCore Server.
Description: System ROM Upgrade required to Prevent Unpredictable System Behavior in ProLiant Servers.
Reference: Search Hewlett Packard’s Enterprise Support Center with keyword c03346558 (Last updated 2012).
POST Errors on Reboot in ProLiant Gen9 with Smart Array Controllers
Issue: POST Errors on Reboot in ProLiant Gen9 with Smart Array Controllers.
Affects: ProLiant G9 Servers; Affects the DataCore Server
Description: The Server May Stop Responding and Will Display Power-On Self-Test (POST) Error Messages on Reboot When Running Smart Array Controllers and/or Host Bus Adaptors.
Reference: Search Hewlett Packard’s Enterprise Support Center using keyword c04805565 (Last updated 2016).
HP Automatic Server Recovery (ASR) May Trigger Unexpected Reboots
Issue: HP Automatic Server Recovery (ASR) May Trigger Unexpected Reboots.
Affects: DataCore Server
Description: This feature must be disabled on a DataCore Server. Some SANsymphony drivers can trigger these function which will result in an unexpected reboot or shutdown.
C-Class BladeSystems May Lose SAN Connections
Issue: C-Class BladeSystems May Lose SAN Connections.
Affects: C-Class BladeSystems; Affects the DataCore Server.
Description: Server Blades May Sporadically Lose SAN Connections Through HP Virtual Connect FlexFabric Modules. HP Virtual Connect firmware Version 4.10 corrects this issue.
Reference: Search Hewlett Packard’s Enterprise Support Center with keyword c03811226 (Last updated 2012).
Time Zone Mismatch Between ILO and Server Clock May Cause Executive Fault
Issue: Time Zone Mismatch Between ILO and Server Clock May Cause Executive Fault.
Affects: Integrated Lights Out (ILO); Affects the DataCore Server
Description: Significant TZ (time zone) settings differences within the ILO software and the server’s own system clock/BIOS may result in the DataCore Executive service faulting. These faults will result in unexpected ‘Not Connected’ and/or ‘Logstore not available’ warning messages from other DataCore Servers in the group. Ensure that the TZ settings match.
Delay in Starting DataCore Executive Service Due to Insight Management
Issue: Delay in Starting DataCore Executive Service Due to Insight Management
Affects: DataCore Server
Description: After a reboot of a DataCore Server, these services may prevent SANsymphony’s own DataCore Executive service from starting for anywhere up to 20 minutes. It is possible to manually start the service during this period either, as it will eventually fail with a ‘timeout’ warning.
If this issue occurs, do one of the following:
- Disable or remove the Insight Management feature.
- Change the DataCore Executive service’s own startup type from Automatic to Automatic (Delayed Start). This forces DataCore Executive service to wait for all the Insight Management services to complete their startup before starting itself automatically.
Excessive Media Errors Reported by HPE NVMe SSD
Issue: Excessive Media Errors Reported by HPE NVMe SSD
Affects: DataCore Server
Description: Certain SSD drive models may report an excessive number of media errors. These errors may be the result of data written incorrectly when the NVMe drive is in idle power mode.
The media errors may not be reported in the logs for AHS, IML, or iLO. Instead the errors will be visible in the operating system (or application) logs. In some cases, one or more files may not open.
Reference: Search Hewlett Packard’s Enterprise Support Center with keyword a00113342en_us (Last updated Jun 2021).
HPE SAS SSDs Require Critical Firmware Upgrade
Issue: HPE SAS SSDs Require Critical Firmware Upgrade.
Affects: DataCore Server
Description: Critical Firmware Upgrade Required for Certain HPE SAS Solid State Drive Models to Prevent Drive Failure at 32,768 Hours of Operation – 12th December 2019.
Reference: Search Hewlett Packard’s Enterprise Support Center with keyword a00092491en_us (Last updated Dec 2019).
Intermittent Lockups in Smart Array Controllers
Issue: Intermittent Lockups in Smart Array Controllers.
Affects: DataCore Server
Description: Update to Smart Array firmware Version 5.04 to Correct Intermittent Controller Lockup Issues.
Reference: Search Hewlett Packard’s Enterprise Support Center with keyword a00007847en_us (Last updated 2017).
Lockup Code 0xAB in P212/P410/P410i/P411/P711m/P712m/P812 Controllers
Issue: Lockup Code 0xAB in P212/P410/P410i/P411/P711m/P712m/P812 Controllers.
Affects: DataCore Server
Description: One or More Spare Drives and firmware Version 6.40 (or Earlier) May Halt with "Lockup Code = 0xAB" Around 64, 128, or 256 Days.
Reference: Search Hewlett Packard’s Enterprise Support Center with keyword c04325462 (Last updated 2015).
Crash During Install/Upgrade Due to cpqfcac.sys Driver
Issue: Crash During Install/Upgrade Due to cpqfcac.sys Driver
Affects: DataCore Server
Description: HP’s cpqfcac.sys driver should be removed from the Windows Operating system before installing SANsymphony when using DataCore’s FC drivers on Back-end Port connections to HP storage arrays. Otherwise, the DataCore Server may crash during the install/upgrade of SANsymphony.
Virtual Connect
Affects: DataCore Server
Description: A pause flood detection on VC uplink ports results in poor performance and/or an FCoE outage. Generic parity errors are fixed for the HP VC FlexFabric-20/40 F8 Module.
HP Virtual Connect Version 4.45 corrects these issues. Search Hewlett Packard’s Enterprise Support Center with keyword c04731344 (Last updated 2015).
IPMI Watchdog Timer (IBM)
Affects: DataCore Server
Description: This feature must be disabled on a DataCore Server. Some SANsymphony drivers can trigger these function which will result in an unexpected reboot or shutdown.
BladeCenter and System x
Affects: DataCore and Host Server
Description: UEFI systems with HBA and > 2 TB LUN may have data consistency errors. (Last updated 2010).
Reference: MIGR-5084554.
ThinkSystem (Lenovo)
Affects: DataCore or Host Server
Description: Micron 5100 SSD series may report errors and cause background process to fail. Upgrade the Micron 5100 drive firmware to version MD51 or later. Search Lenovo’s own support website for Document ID: HT507307 (last updated May 2019).
Fibre Channel Adapters – Known Issues
The following section highlights known issues with certain Fibre Channel HBAs (Host Bus Adapters) when used with DataCore SANsymphony. These issues may affect host or DataCore Servers and are accompanied by recommendations or reference links where applicable.
Emulex
Third-party Process Logout (TPRLO)
Applies to: Host Server
This must be disabled on any host using Emulex Fibre Channel ports connected to a DataCore Server.
All 16GB (including OEM)
Affects: DataCore Server
These HBAs may behave erratically when using the DataCore Emulex Fibre Channel driver with SANsymphony 10.0 PSP 7 Update 1 or earlier.
If already using DataCore's 16GB/s Emulex Fibre Channel driver prior to October 2016 (and qualified by DataCore), upgrade to 10 PSP 7 Update 2.
All 8GB (including OEM)
Affects: DataCore Server
Use firmware 2.01a12 or later. Earlier firmware versions may cause the DataCore Server to hang or crash during the installation or upgrade of SANsymphony.
Also, refer to the Qualified Hardware Components FAQ document for more information.
QLogic
All models (including OEM)
Affects: DataCore Server
When using a vendor’s own Fibre Channel driver to connect to a storage array:
- QLogic driver version 9.1.17.21 with firmware earlier than 08.03.00 may cause some storage arrays to panic or crash.
- QLogic driver version 9.3.3.20 with firmware 8.01.41 may cause loss of access to storage attached to the DataCore Server or a crash of the server after 42 days. Upgrade to driver version 9.4.1.20 or later.
All 16GB (including OEM)
Affects: DataCore Server
When using directly connected QLogic 16GB Mirror ports between two DataCore Servers with SANsymphony 10.0 PSP 4 Update 1 or earlier, set the Data rate mode of all connected SANsymphony MR ports to 8GB.
Also, refer to the following documentation for more information:
- Modifying Fibre Channel Port Settings
- SANsymphony : Using direct-connected Fibre Channel Ports with a DataCore Server
Hewlett-Packard
HP StoreFabric 84Q
Affects: DataCore Server
Do not use the DataCore Fibre Channel driver on this 4-port HP-branded HBA.
Using the DataCore QLogic driver on the HP-branded QLogic HBA has been reported as unstable. Symptoms include unexplained CRC errors and/or high transmission and link error counts. Replace the DataCore driver with the vendor’s recommended driver.
Using the vendor driver limits the HBA to storage connectivity only—it will no longer appear in the SANsymphony Management Console.
Also, refer to Replacing the DataCore Fibre Channel Driver section from the Qualified Hardware Components FAQ.
Using the equivalent QLogic ‘own-branded’ version of this 4-port HBA does not show the same symptoms when using the same DataCore QLogic driver.
Network adaptors (inc. iSCSI)
Refer to the following documentation for more information:
- The DataCore Server: Qualified Hardware Components
- Best Practice Guidelines for SANsymphony – ISCSI and Fibre Channel Connections
Broadcom BCM57xxx
Issue: iSCSI MBA Initiator Interferes with DataCore.
Affects: DataCore Server
Description: Disable the ‘iSCSI MBA initiator’ feature as this interferes with DataCore’s iSCSI Target Driver. Even if the NIC is only used for management LAN connections between DataCore Servers it is still recommended to disable this feature.
Workaround: Contact the vendor for instructions.
Emulex Oce11102-NX / Oce10102-NX
Issue: TCP Chimney Offload Causes Shutdown Issues
Affects: DataCore Server
Workaround: Disable ‘TCP Chimney Offload’ on these adaptors; otherwise, the SANsymphony software may not be able to be stopped properly.
Reference: TCP Chimney Offload article.
Hewlett Packard – All Converged Network Adaptors (CNAs)
Issue: “Immediate Data” Not Supported
Affects: DataCore Server
Description: “Immediate Data” is not supported and must be set to “No”.
Hewlett Packard – CN1000Q
Issue: Requires Firmware Update
Affects: DataCore Server
Description: Use firmware version 4.8.22 or later.
Hewlett Packard – Intel Ethernet 10Gb 562SFP+ Adapter
Issue: NTFS File Corruption on iSCSI Volumes with Jumbo Frames
Affects: DataCore or Host Servers
Description: HPE Intel i40ea Driver for Windows Server 2016 Versions 1.8.83.0 or 1.8.94.0 may cause NTFS file corruption to iSCSI mounted volumes when jumbo frames are enabled.
Workaround: Search Hewlett Packard’s Enterprise Support Center using keywords a00074697en_us (Last updated June 2019).
Hewlett Packard – NC55* SFP 10 Gigabit Adaptors
Issue: TCP Chimney Offload Interference with SANsymphony
Affects: DataCore Server
Description: Disable ‘TCP Chimney Offload’ on these adaptors; otherwise, the SANsymphony software may not be able to be stopped properly.
Reference: Microsoft KB951037 (Last updated 2014).
Hewlett Packard – NC375x/NC382i/NC52x Gigabit Adaptors
Issue: iSCSI Instability with Older Driver/Firmware
Affects: DataCore or Host Server
Description: When used for iSCSI connections, use driver version 5.3.27.606 and firmware 4.0.0.19 (9 Sep 2014) or later.
Reference: Search Hewlett Packard’s Enterprise Support Center using keywords: c02964542 (Last updated 2012) and c03734205 (Last updated 2013).
Hewlett Packard – ProLiant BL460c (Gen10) Server Blades
Issue: Broadcom BCM57xxx Chipset NICs Cause Issues
Affects: DataCore Server
Description: These server blades use NICs with Broadcom BCM57xxx chipsets. See the Broadcom entry for more details.
Broadcom – Emulex/BCM57xxx-Based NICs
Issue: Delays or Instability Caused by Certain Chipsets.
Affects: DataCore Server
Description: Broadcom-based NICs (such as Emulex and BCM57xxx) may interfere with SANsymphony performance or startup.
Workaround: Update firmware and drivers or avoid NICs based on these chipsets when possible.
IBM – 49y4250 / 49y7950 10GiB Adaptors
Issue: TCP Chimney Offload Interference with Shutdown.
Affects: DataCore or Host Server
Description: Disable ‘TCP Chimney Offload’ on these adaptors; otherwise, the SANsymphony software may not be able to be stopped properly.
Reference: Microsoft KB951037
Intel x710 Ethernet Controller
Affects: the DataCore and Host Server
Issue: DataCore had previously made recommendations to avoid using this family of adaptors for any/all iSCSI connections due to erratic behavior under load.
Symptoms:
- Continual disconnect/reconnect events to/from Host and Mirror Port iSCSI Initiators
- Initial reports involved rebranded NICs (e.g., HP, Dell) and drivers from vendors (Feb 2017) rather than directly from Intel
Workaround: Reports from end users suggest that updating Intel NVM to version 6.01 (Dec 2017) resolves these issues.
Rebranded NICs may require vendor-specific NVM updates—contact your hardware vendor for availability.
Reference:
- Non-Volatile Memory (NVM) Update Utility for Intel® Ethernet Network Adapter 710 Series, refer to KB24769.
- If using HP hardware with ESXi, refer to VMware KB2126909.
Intel – x710 Ethernet Controller (VMware ESXi)
Issue: PSOD on ESXi Hosts with i40e Driver.
Affects: ESXi hosts including Hyperconverged SANsymphony installations.
Description: ESXi hosts using Intel Corporation Ethernet Controller X710 10GbE SFP+ NICs with the i40e driver may fail with PSOD.
Reference: VMware KB 2126909
For HP servers with ESXi: VMware KB 2126909
Nvidia Mellanox
Issue: ConnectX SmartNICs – General
Affects: DataCore Server
Description: DataCore have had reports by customers using ConnectX-5 SmartNICs configured for speeds of 100Gb/s 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/s or more.
DataCore are recommending reducing the speed of these NIC to 25Gb/s as this has been shown to resolve the problems stated above. DataCore are currently investigating this problem.
ConnextX-5
Affects: DataCore Server
Description: Use a minimum firmware version of 16.27.1016 and WinOF-2 driver version 2.40 (22511.0 or later). Users on earlier firmware and driver versions reported unexpected and repeated network disconnections.
ConnextX-3
Affects: DataCore and Host Server
Description: DataCore recommend a minimum of WinOF VPI version 5.50 or later.
All PCI Express 2.0 ConnectX Adaptors
Affects: DataCore and Host Server
Description: When used for iSCSI connections use firmware version 2.9.1000 or later with PCI Express 2.0 otherwise I/O may stall or stop working completely.
Storage Hardware
Some of the information in this section may overlap with known issues reported in the Server hardware section. Refer to SANsymphony : Storage Hardware Guideline for use with DataCore Servers for more information.
Disks Previously Used for Disk Pools
Issue: Disks previously used for Disk Pools.
Affects: DataCore Server
Description: Physical disk devices that had previously been used in another Disk Pool but had not been ‘cleanly’ deleted may be re-discovered as a ‘foreign’ Disk Pool that cannot be deleted or imported. This happens because the Disk Pool driver has detected the previous Disk Pool’s indexes on the discovered disk device(s); the index references other physical disks that no longer exist or cannot be seen by the DataCore Server.
Workaround: To prevent this from happening, always cleanly decommission physical disks from a Disk Pool or, if that is not practical, make sure that the disk device is completely re-formatted before presenting it back to the DataCore Server to remove any residual Disk Pool indexes from being detected. Refer to Removing Physical Disks from Pools for more information.
NVMe Storage Devices – SANsymphony versions 10.0 PSP 1 Update 1 or earlier
Issue: NVMe devices are not supported.
Affects: DataCore Server
Description: NVMe devices do not work with SANsymphony versions 10.0 PSP 1 Update 1 or earlier.
NVMe Storage Devices – SANsymphony versions 10.0 PSP 2 or later
Issue: Microsoft-provided drivers may underperform.
Affects: DataCore Server
Description: DataCore always recommend using the NVMe vendor’s own device driver for any devices used in a DataCore Server (example: SANsymphony Disk Pool disks) as we have found in both testing and reports from the field that performance, when using the vendors own driver, is often better than when using those that might be automatically provided by Microsoft (i.e., via Windows Updates).
Third-party Storage Devices
Adaptec RAID Controllers
Issue: RAID controllers not discovered; Task Triggers fail.
Affects: DataCore Server
Description: Use version v1.07.21229 or later of maxView Storage Manager. Earlier versions prevented Adaptec RAID controllers from being discovered and SANsymphony Task Triggers from sending Emails.
Allied TeleSyn MC1000 Media Converter
Issue: Smart Missing Link (SML) mode interferes with stability.
Affects: DataCore Server
Description: Do not use ‘Smart Missing Link’ (SML) Mode Status.
Areca ARC-188x
Issue: Server becomes unresponsive or fails to boot.
Affects: DataCore Server
Description: Use firmware versions 1.51 2012-12-24 or later. Earlier versions may cause the DataCore Server to become unresponsive or unable to boot after a restart.
Dell EMC MD 36xx/38xx FC
Issue: LUN access and failover do not work as expected.
Affects: DataCore Server
Description: Access to and failover of storage LUNs will not work as expected when connected to DataCore FC drivers. Use Dell EMC-approved FC drivers and MPIO software.
Dell EMC Clariion AX150/AX4
Issue: LUN access and failover do not work as expected
Affects: DataCore Server
Description: Access to and failover of storage LUNs will not work as expected when connected to DataCore FC drivers. Use Dell EMC-approved FC drivers and MPIO software.
Dell EMC Compellant SC Series
Issue: Increased latency when using built-in deduplication
Affects: DataCore Server
Description: DataCore have had reports of significant increased latency while using this storage array’s own, built-in, deduplication feature. While DataCore do not have any special recommendations when using a storage array’s own deduplication feature, we would recommend temporarily turning this feature off to see if there is any overall increased performance.
Micron RealSSD
Issue: Performance degradation
Affects: DataCore Server
Description: Use Support Pack version 145.07.xx with firmware version 218 or higher. Earlier versions have been reported as having performance issues.
PowerEdge
Affects: DataCore Server
Issue: Fan Offset settings are lost after any power failure.
Description: When using Dell PowerEdge servers with firmware versions from 2.15.10.10 to 2.21.21.21, the Fan Offset settings are not retained after a power failure.
Workaround: Update to a later firmware version.
SAS Arrays using Seagate disks (Model: ST8000NM0185)
Affects: DataCore Server
Issue: Unexpected Disk Pool offline state.
Description: Customers using firmware version 2.3.11.183 reported SANsymphony Disk Pools going offline unexpectedly due to constant I/O resets.
Workaround: Dell recommends updating the firmware to PT52, A00 (dated 25 April 2019) or later.
Reference: Dell Support Driver Page.
Fusion-io with Deduplication
Affects: DataCore Server
Issue: Indefinite hang during Deduplication Pool creation.
Description: When using Fusion-io disk devices with SANsymphony’s deduplication feature, older firmware versions (e.g., 2.3.11.183) caused indefinite hangs during pool creation.
Workaround: Use Fusion-io driver/firmware version 3.2.10.1509 or greater.
VSL RAM Calculations
Affects: DataCore Server
Issue: Incorrect RAM sizing.
Description: Inaccurate sizing may occur when calculating the VSL maximum RAM requirement.
Workaround: Set the "Average Written Block Size (bytes)" to 512 during RAM calculation.
Hewlett Packard EVA 4000/8xxx
Affects: DataCore Server
Issue: Unexpected disconnections.
Description: Using firmware version 6.22 on EVA storage controllers can cause connection drops to the DataCore Server.
Workaround: Avoid using firmware version 6.22.
Hewlett Packard MSA 1040/2040
Affects: DataCore Server
Issue: Unstable storage connections.
Description: Controller firmware versions earlier than GL220P008 cause unexpected disconnections to the DataCore Server.
Workaround: Use firmware version GL220P008 or later. Seach HPE Support Center using keyword c05158553.
Hewlett Packard - Smart Array P440AR
Affects: DataCore Server
Issue: Poor performance.
Description: Driver versions up to and including 63.12.0.64 have been linked to degraded performance when used with DataCore Servers.
Workaround: Upgrade to driver version 63.12.0.64 (A) or later.
Hewlett Packard - SAS Storage Systems
Affects: DataCore Server
Issue: Data Compare failure.
Description: Some SAS hard drive models may experience rare data comparison issues.
Workaround: Perform firmware upgrades as per HPE advisories c03747345 (2014) and c03924194 (2013).
Hitachi - Virtual Storage Platform (VSP) F and G Series
Affects: Host
Issue: Virtual Disks inaccessible after reboot.
Description: System Option Mode 725 = OFF (default setting) may prevent Host Virtual Machines from being able to access DataCore Virtual Disks after rebooting the DataCore Server. Each time a DataCore Server is stopped, HUS VMs will report that paths to the DataCore Server’s Virtual Disks are ‘Not Ready’. When this ‘Not Ready’ status is returned 3 times within 3 minutes to the VM, the path to the DataCore Server’s Virtual Disk is blocked – even if the DataCore Server is running and the Virtual Disk is accessible. This blocked status cannot be recovered automatically.
Workaround: DataCore recommend using System Option Mode 725 = ON for paths to DataCore Virtual Disk devices to avoid this problem. Contact Hitachi for more information on this System Option Mode setting. Also, refer to Hitachi’s own Knowledgebase.
IBM
DS3400/3500
Issue: DS3400/3500 requires LNXAVT setting for proper operation.
Affects: DataCore Server
Description: These arrays may need to have LNXAVT enabled to function as an ‘Active/Active’ storage array for DataCore Server Back End connections.
Workaround: Testing is strongly advised.
DS4100 LUN failover problems
Issue: DS4100 LUN failover problems with DataCore FC drivers.
Affects: DataCore Server
Description: Access to and failover of storage LUNs will not work as expected when connected to DataCore FC drivers.
Workaround: Use IBM-approved FC drivers and MPIO software.
ServeRAID M5100e
Issue: ServeRAID M5100e poor performance with FastPath enabled.
Affects: DataCore Server
Description: Poor performance under high load has been reported when the “Performance Accelerator for IBM System x with MegaRAID FastPath” setting is enabled.
Workaround: Disable the FastPath setting. Testing is strongly advised.
ServeRAID M and MR10 Series
Issue: ServeRAID M and MR10 Series unexpected resets or hangs
Affects: DataCore Server
Description: Driver version v6.702.07.00 for Windows Server 2012R2/2012/2008R2/2008 may cause unexpected controller resets or system hangs under moderate to heavy I/O.
Workaround: Use a different driver version.
Reference: IBM Support Document MIGR-5096069.
System x NMI error
Issue: System x NMI error on cable changes
Affects: DataCore Server
Description: An NMI may occur when network cables are removed or reconnected.
Workaround: Not specified.
Reference: IBM Support Document MIGR-5084146.
Intel
Optane - Persistent Memory (PMem)
Issue: PMem feature is not supported with SANsymphony. PMem has two different accessibility modes:
• Memory Mode — significantly higher access latency than standard DRAM so not suitable for use with SANsymphony.
• App Direct — Raw Device Access mode is not supported when used in a Disk Pool.
Affects: DataCore Server
Description: The PMem feature is not supported with SANsymphony.
NVMe — Disk device ID not unique
Issue: Earlier Intel drivers, including those bundled with Microsoft Windows, prevent NVMe disk devices from having a unique disk device identifier.
Affects: DataCore Server
Description: This causes problems in SANsymphony Server Groups with more than one DataCore Server, where each server has its own NVMe storage. Without a unique device identifier, all NVMe storage appears incorrectly as ‘shared physical disks’ across all DataCore Servers.
Workaround: Always use the latest Intel device driver available.
Microsoft Windows PCIe driver
Issue: Possible BSOD when issuing a temperature request.
Affects: DataCore Server
Workaround: Use driver version 4.4.0.1003 or later.
Reference: See release notes from Intel.
Lenovo
Intel S4510 and S4610 SATA SSDs
Affects: DataCore Server
Description: 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.
Reference: See Lenovo support website for Document ID: HT507987 (last updated September 2019).
Micron M.2 and SSD drives
Issue: Micron 5100 SSD series may report errors and cause background processes to fail.
Affects: DataCore Server
Workaround: Upgrade the Micron 5100 drive firmware to version MD51 or later.
Reference: See Lenovo support website for Document ID: HT507307 (last updated May 2019).
LSI
Nytro WarpDrive
Issue: These SSDs may ship with identical disk device identifiers.
Affects: DataCore Server
Description: Reformat the SSD using LSI’s own disk utility to re-generate a new unique disk device identifier. Contact LSI directly for instructions. Without a unique device identifier, all LSI SSD storage will appear incorrectly as ‘shared physical disks’ across all DataCore Server groups with more than one DataCore Server.
Micron Technology Inc.
RealSSD
Issue: Earlier Support Pack versions and firmware cause performance issues.
Affects: DataCore Server
Description: Use Support Pack version 145.07.xx with firmware version 218 or higher. Earlier versions are known to cause performance issues.
NetApp
All E Series arrays
Issue: Access to storage LUNs fails with DataCore FC drivers.
Affects: DataCore Server
Description: Use NetApp’s own DSM as well as NetApp-approved HBA and Switch firmware (refer to their own Interoperability Matrix Tool).
Automatic Load Balancing (ALB)
Issue: ALB feature may cause additional latency for backend I/O.
Affects: DataCore Server
Description: This feature, when enabled, may cause additional latency for backend I/O to and from a DataCore Server. Any user that experiences latency warnings or errors when connected to NetApp storage should disable this feature as a first-step to see if this resolves the problem.
From NetApp’s own documentation:
“Although overhead for volume ownership transfer has been minimized in development, the feature is not completely free, and there is some amount of added I/O latency for the duration of the transfer. As a result, ALB should be disabled in latency-sensitive environments that cannot tolerate even the slightest fluctuation in I/O response times.”
Reference: Refer to Enabling and Disabling ALB section from NetApp’s Technical Reference documentation TR-4737 for more information.
Netgear
ReadyNAS 3100
Issue: Poor performance under ‘high load’.
Affects: DataCore Server
Description: Poor performance under ‘high load’ has been reported to DataCore using these arrays. Testing is strongly advised.
PureStorage
All FlashArray storage
Issue: Access to storage LUNs fails with DataCore FC drivers before controller version 3.40.
Affects: DataCore Server
Description: Access to storage LUNs will not work when connected to DataCore FC drivers unless using controller versions 3.40 or later. For versions before 3.40 use PureStorage-approved drivers and MPIO software.
Skyera
skyHawk
Issue: Firmware versions before v1.0 cause loss of disk configuration.
Affects: DataCore Server
Description: Using firmware versions v1.0 or later to avoid unexpected loss of the array’s own disk configuration settings - which results loss of access from the DataCore Server.
Toshiba OCZ
Z-Drive
Issue: Older firmware causes serious Disk Pool access and data integrity problems.
Affects: DataCore Server
Description: Affects 4500, R4 R and Deneva 2 R Series drives. Use firmware 3.22e or higher. Storage arrays using older firmware versions have been reported with serious problems with Disk Pool access and data integrity when used in a DataCore Server.
Transtec
Provigo
Issue: Overload Management setting affects latency on firmware 3.5 or 3.7.
Affects: DataCore Server
Description: For firmware releases 3.5 or 3.7 go into the Storage Management Software > Advanced Options > Performance Options and set ‘Overload Management’ to ’Disabled’ for lowest latency.
Violin Memory
All PCIe Flash Memory Cards
Issue: These storage devices may ship with identical disk device identifiers.
Affects: DataCore Server
Description: Reformat them using Violin Memory’s recommended disk utility to re-generate a new unique disk device identifier. Contact Violin Memory directly for instructions. Without a unique device identifier, all storage devices will appear incorrectly as ‘shared physical disks’ across all DataCore Server groups with more than one DataCore Server.
X-IO
ISE 1 Storage Arrays
Issue: Older firmware versions cause crashes.
Affects: DataCore Server
Description: Use controller firmware versions 1.7.20 and higher. Earlier versions would cause the DataCore Server to crash.
ISE 2 Storage Arrays
Issue: Performance may degrade with older firmware.
Affects: DataCore Server
Description: DataCore recommend firmware 4.1.14 or higher which contains improvements to I/O queue handling that will help improve overall performance. Contact X-IO for more information.
G3 and G4 Storage Arrays
Issue: Older firmware lacks I/O queue handling improvements.
Affects: DataCore Server
Description:
- For G4 Storage Arrays: DataCore recommend firmware version 4.1.14 or higher which contains improvements to I/O queue handling that will help improve overall performance.
- For G3 Storage Arrays: Contact X-IO to see if there is a later firmware version with equivalent improvements as per the G4 storage arrays noted above.
Switches – FC, FCoE and IP
All Switch Vendors
Issue: RSCNs must be configured consistently across all connected ports.
Affects: DataCore Server
Description: Registered State Change Notifications (RSCNs) must be enabled on all DataCore Server and Host connected switch ports. The RSCNs Event Timeout setting must also be the same across all DataCore Server, Host, and Storage Array controller ports.
Brocade
Fabric OS 7.x
Issue: Port login and connectivity issues, and random 16Gb FC Port logouts.
Affects: DataCore Server
Description: Use FOS 7.4.1a or later.
This includes fixes where:
- DataCore and Host ports may not login after a DataCore Server or switch reboot, or after any other ‘significant’ disruption (Brocade defect DEFECT000429695 – also fixed in FOS 7.0.2d, 7.1.1, and 7.2.0a).
- Switches may observe loss of connectivity on ports and/or trunked Inter Switch Links (ISL) (Brocade defect DEFECT000324848).
- A small number of users had reported unexpected, random logouts for 16Gb FC Port connections while using FOS versions before 7.0.3a due to Switch Buffer Credit exhaustion. A workaround to this specific case was to set the DataCore FC Port’s ‘Data rate mode’ to 8Gb.
Fabric OS 6.x
Issue: SCR value registration problems and connectivity loss.
Affects: DataCore Server
Description: Use FOS 6.4.3e or later.
The following fixes apply in situations where:
- State Change Registration (SCR) value was not properly registered in the switch’s own name server table (Brocade defect DEFECT000284472).
- DataCore and Host ports may not login after a DataCore Server or switch reboot, or after any other ‘significant’ disruption (Brocade defect DEFECT000429695).
- Switches may observe loss of connectivity on ports and/or trunked Inter Switch Links (ISL) (Brocade defect DEFECT000324848).
Brocade (8GB FC Switches Only)
Applies to 8GB Brocade switches.
Issue: Mixing 4GB and 8GB Fibre Channel connections in the same fabric zone can cause communication issues if fillword settings are not correctly configured.
Affects: DataCore Server environments using a mix of 4GB and 8GB FC connections on Brocade switches.
Description: Incorrect fillword settings can lead to symptoms such as random port log-outs and errors (er_enc_out, er_bad_os). Use the portcfgshow command to verify current settings and portCfgFillWord to apply the correct configuration:
- Use mode 3 on all 8GB ports
- Use mode 0 on all 4GB ports
Changing the fillword setting will temporarily disable the port. While it’s not necessary to stop the SANsymphony software, changes should be made one port at a time to avoid dual-path failures. Always verify port re-establishment before proceeding.
Workaround: Set appropriate fillword modes as per port speed. Refer to Brocade documentation for command syntax and additional details.
Cisco Systems Inc. (Nexus and MDS Series)
Cisco Nexus and MDS Fibre Channel switch series.
Issue: DataCore Server ports must have unique Fibre Channel Area IDs and may experience intermittent frame drops on some firmware versions.
Affects: DataCore Servers connected to Cisco Nexus 7xxx or MDS 9xxx Series switches, especially on the following releases:
- 8.2(0)SK(0.90)
- 8.2(1)
- 8.2(2)
Description: Intermittent frame timeout drops may occur without typical signs of congestion (e.g., no transmit credit wait or credits-to-zero events). Unique FC Area IDs must be assigned to all connected DataCore ports. Refer to Cisco documentation for proper configuration.
Workaround: Ensure all DataCore ports have unique FC Area IDs. Monitor for intermittent drops and apply firmware updates or patches as needed.
Reference: Cisco Bug ID: CSCvj58687
QLogic
QLogic adapters used in SAN fabrics with DataCore Servers.
Issue: IO StreamGuard must be disabled to support RSCN (Registered State Change Notification) functionality.
Affects: All DataCore environments using QLogic adapters.
Description: If IO StreamGuard is enabled, RSCN functionality may be blocked, which could impact fabric discovery and zoning changes.
Workaround: Disable IO StreamGuard. Refer to the “All Switch Vendors” entry for additional background.
Third-Party Software
Anti-Virus Software
Applies to all third-party antivirus software installed on a DataCore Server.
Issue: Certain antivirus programs interfere with SANsymphony processes, especially during configuration updates and replication.
Affects: DataCore Servers running SANsymphony.
Description: Exclude the following on a DataCore Server to avoid interference:
- The DataCore Executive process – Dcsx.exe
- The SANsymphony installation folder – C:\Program Files\DataCore
- SANsymphony’s Asynchronous Replication buffer. This stops any delay in the sending of replication data to the remote DataCore Server.
Workaround: Configure antivirus exclusions for the above paths and processes.
Reference: See the “Third-Party Software” section in Best Practice Guidelines for SANsymphony.
Broadcom – Advanced Server Program (BASP)
Issue: TCP/IP interruptions can cause the virtual NIC’s MAC Address to change unexpectedly.
Affects: DataCore iSCSI Targets
Description: TCP/IP interruptions can cause the virtual NIC's MAC address to change, resulting in:
- Existing DataCore iSCSI Targets going offline
- New Target Ports appearing
Workaround: Avoid using BASP in configurations where NIC stability is critical for SANsymphony operations.
Symantec – Network Threat Protection (NTP)
Issue: Network Threat Protection affects SANsymphony performance.
Affects: SANsymphony server operations and responsiveness.
Description: Performance degradation has been observed when NTP is enabled.
Workaround: Disable NTP when running SANsymphony.
McAfee
VirusScan
Issue: McAfee’s software may interfere with the installation or upgrade of DataCore’s software products, leading to conflicts or unexpected results.
Affects:
- VirusScan
- When installed on a DataCore Server
Description: Current versions of McAfee’s software products interfere with the installation/upgrade of DataCore’s software products. Apply the following settings to avoid any conflicts or unexpected results when running, upgrading, or modifying either SANsymphony or DataCore’s Windows Integration Kit (WIK).
Workaround: Using ePolicy Orchestra (ePO) settings:
- Exclusions:
- C:\Program Files\DataCore
- Any other directory where the DataCore Installation/upgrade binaries are run from.
- Asynchronous Replication buffer (applies to SANsymphony only)
Using Unmanaged Client Settings:
-
Navigate to Common > Advanced options
- Exclusion:
- Dcsx.exe as a process (applies to SANsymphony only)
- Exclusion:
Threat Prevention
- Exclusions:
- The SANsymphony installation folder – C:\Program Files\DataCore
- Any other directory where the DataCore Installation/upgrade binaries are run from.
Threat Prevention > Advanced options > On-Access Scan > Process Settings
Add the following as Low Risk:
- setup.exe
- smartdeploymentwizard.exe
- DatacoreServer.exe
- DcsAddMem.exe
- DcsConsole.exe
- DcsDriverSetup.exe
- DcxGroupInstall.exe
- DcsImport.exe
- DcsTelemetry.exe
- DcsTrace.exe
- DCSX.exe
Process Type
- Exclusions:
- C:\Program Files\DataCore
- Any other directory where the DataCore Installation/upgrade binaries are run from.
Threat Prevention > Advanced options > On-Demand Scan > Full, Quick Scan and Right Click Scans
- Exclusions (include subfolders):
- C:\Program Files\DataCore
- Asynchronous Replication buffer (applies to SANsymphony only)
Refer to the Third-party software section in Best Practice Guidelines for SANsymphony.
Oracle
Automatic Storage Management (ASM)
Issue: Automatic Storage Management (ASM) default timeout setting may cause compatibility issues with DataCore-recommended host timeouts.
Affects: Host
Description: The ASM default ‘15’ second timeout needs to be increased so that it is greater than the DataCore-recommended disk timeout setting for the host’s Operating System.
Refer to the following documentation for more information:
Veeam
Backup Management Suite
Issue: Compatibility issues with DataCore’s VSS Hardware provider and potential boot failure due to Changed Block Tracking (CBT) driver.
Affects: DataCore Server when used with DataCore’s VSS Hardware provider
DataCore Server when Veeam CBT driver is installed
Description: Backup Management Suite
Requires Patch 4 (or later) with Veeam Backup & Replication 7.0
The following SANsymphony-related issues are fixed by this patch:
- The DataCore’s VSS Hardware Provider cannot be selected by the ‘Resource Owner’ of a Microsoft Cluster when using Cluster Shared Volumes (CSVs).
- The ‘Resource Owner’ cannot backup its own CSVs using DataCore’s VSS. Nodes that are not designated however are still able to use the DataCore VSS hardware provider as normal.
Changed Block Tracking
Affects: The DataCore Server
Description: Do not install Veeam’s Changed Block Tracking driver (CBT) on a DataCore Server as this will prevent the DataCore Server from being able to boot (until Veeam CBT is removed via the "Veeam Recovery Media").
Workaround: Use the "Veeam Recovery Media" to remove the CBT driver and restore boot functionality.
Refer to the following documentation for more information:
- Veeam KB1891 (Last updated 2014)
- Veeam Changed Block Tracking Driver
Previous Changes
| Section | Content Changes | Date |
|---|---|---|
| Storage Hardware – NVMe Storage (all vendors) / ConnectX SmartNICs |
Added
|
December 2021 |
| Storage Hardware – HPE Storage Devices (HPE NVMe SSD) / Intel S4510 and S4610 SATA SSD (only 1.8 TB and 3.84 TB are affected) |
Added Affects the DataCore Server Certain SSD drive models may report an excessive number of media errors. These errors may be the result of data written incorrectly when the NVMe drive is in idle power mode. The media errors may not be reported in the logs for AHS, IML, or iLO. Instead, the errors will be visible in the operating system (or application) logs. In some cases, one or more files may not open. Search Hewlett Packard’s Enterprise Support Center with keyword a00113342en_us (Last updated Jun 2021) |
December 2021 |
| 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. | September 2021 |
| Storage Hardware – Lenovo Intel S4510 and S4610 SATA SSD (only 1.8 TB and 3.84 TB are affected) |
Added 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) |
September 2021 |
| Third Party Software – Anti-Virus software |
Updated Affects the DataCore Server When installed on a DataCore Server Exclude the following on a DataCore Server: The DataCore Executive process – Dcsx.exe |
September 2021 |
| Fibre Channel Adaptors – QLogic (All models including OEM) |
Added
|
February 2021 |
| Microsoft Windows – General (Windows 2016 update regression) |
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:
|
January 2021 |
| Server Hardware – Lenovo - ThinkSystem Servers | Added Affects the DataCore or Host Server | January 2021 |
| Microsoft Windows – General (Windows 2016 update regression) |
Added Affects the DataCore and Host Servers Unexpected BSOD when using MPIO Disk Devices after applying KB4586830 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:
|
December 2020 |
| Storage Hardware – Intel NVMe - Microsoft Windows PCIe driver |
Added Affects the DataCore Server Possible BSOD when issuing a temperature request. Use driver version 4.4.0.1003 or later. Refer to release notes: Client-NVMe Microsoft Windows Drivers for Intel SSDs. |
September 2020 |
| Storage Hardware – X-IO - G3 and G4 Storage Arrays |
Updated Affects the DataCore Server
|
August 2020 |
| Server Hardware – Lenovo - ThinkSystem Servers |
Added Affects the DataCore or Host Server Micron 5100 SSD series may report errors and cause background process to fail. Upgrade the Micron 5100 drive firmware to version MD51 or later. Search Lenovo’s support website for Document ID: HT507307 (last updated May 2019) |
August 2020 |
| Network Adaptors - Hewlett Packard - HPE Intel Ethernet 10Gb 562SFP+ Adapter |
Added
|
August 2020 |
| Network Adaptors - Mellanox Technologies - ConnextX-5 |
Added Affects the DataCore Server
|
August 2020 |
| Storage Hardware – Lenovo - Micron M.2 and SSD drives |
Added Affects the DataCore Server Micron 5100 SSD series may report errors and cause background process to fail. Upgrade the Micron 5100 drive firmware to version MD51 or later. Search Lenovo’s support website for Document ID: HT507307 (last updated May 2019). |
August 2020 |
| Server Hardware - HPE Storage Devices |
Added
|
January 2020 |
| General | This document has been reviewed for SANsymphony 10.0 PSP 9. No additional settings or configurations are required. | October 2019 |
| Storage Hardware – NetApp - Automatic Load Balancing (ALB) |
Added Affects the DataCore Server This feature, when enabled, may cause additional latency for backend I/O to and from a DataCore Server. Any user that experiences latency warnings or errors when connected to NetApp storage should disable this feature as a ‘first step’ to see if this resolves the problem. From NetApp’s own documentation: “Although overhead for volume ownership transfer has been minimized in development, the feature is not completely free, and there is some amount of added I/O latency for the duration of the transfer. As a result, ALB should be disabled in latency-sensitive environments that cannot tolerate even the slightest fluctuation in I/O response times.” Refer to the Enabling and Disabling ALB section from NetApp’s Technical Reference documentation TR-4737 for more details: |
August 2019 |
| Storage Hardware - Dell EMC - Compellant SC series |
Added Affects the DataCore Server DataCore have had reports of significant increased latency while using this storage array’s own, built-in, deduplication feature. While DataCore do not have any special recommendations when using a storage array’s own deduplication feature, we would recommend temporarily turning this feature off to see if there is any overall increased performance. |
July 2019 |
| Storage Hardware - Fusion-IO - SANsymphony Console display |
Removed Affects the DataCore Server with SANsymphony-V 9.0 PSP4 Update 4 (and earlier) Fusion-io disk devices will not display ‘UNKNOWN’ for all Vendor-specific information in the ‘Info’ tab. This has no functional impact and can be ignored. As SANsymphony 9.0 PSP4 Update 4 is now end of life, this entry has been removed. |
July 2019 |
| Storage Hardware - Hitachi - Virtual Storage Platform (VSP) F and G series |
Added Affects the Host System Option Mode 725 = OFF (default setting) may prevent Host Virtual Machines from being able to access DataCore Virtual Disks after rebooting the DataCore Server. Each time a DataCore Server is stopped, HUS VMs will report that paths to the DataCore Server’s Virtual Disks are ‘Not Ready’. When this ‘Not Ready’ status is returned 3 times within 3 minutes to the VM, the path to the DataCore Server’s Virtual Disk is blocked – even if the DataCore Server is running and the Virtual Disk is accessible. This blocked status cannot be recovered automatically. Therefore, DataCore recommend using System Option Mode 725 = ON for paths to DataCore Virtual Disk devices to avoid this problem. Contact Hitachi for more information on this System Option Mode setting and also refer to Hitachi’s own Knowledge Base article. |
July 2019 |
| Storage Hardware - Dell EMC - Compellant SC series |
Added Affects the DataCore Server DataCore have had reports of significant increased latency while using this storage array’s own, built-in, deduplication feature. While DataCore do not have any special recommendations when using a storage array’s own deduplication feature, we would recommend temporarily turning this feature off to see if there is any overall increased performance. |
April 2019 |
| SAS Arrays using Seagate disks with model number ST8000NM0185 |
Added Affects the DataCore Server Dell recommend updating firmware to PT52, A00 (25 April 2019) or later. Customers using older firmware version 2.3.11.183 reported SANsymphony Disk Pools going offline unexpectedly because of constant I/O resets. Refer to Drivers Details. |
April 2019 |
| Third Party Software - Oracle Automatic Storage Management (ASM) |
Added Affects the Host The ASM default ‘15’ second timeout needs to be increased so that it is greater than the DataCore-recommended disk timeout setting for the host’s Operating System. Also see: ASM diskgroup dismount with "Waited 15 secs for write IO to PST" (Doc ID 1581684.1) Refer to the Host Server Configuration Guides section from SANsymphony |
April 2019 |
| Veeam - Changed Block Tracking |
Added Affects the DataCore Server Do not install Veeam’s Changed Block Tracking driver (CBT) on a DataCore Server as this will prevent the DataCore Server from being able to boot (until Veeam CBT is removed via the "Veeam Recovery Media"). Refer to Veeam Changed Block Tracking Driver for more information. |
April 2019 |
| Server Hardware - Microsoft Windows (general) - Switches – Fibre Channel, FCoE and IP |
Added Cisco Systems Inc. - Nexus 7xxx and MDS 9xxx Series using releases 8.2(0)SK(0.90) 8.2(1) 8.2(2) Intermittent frame timeout drops with no other signs of congestion in the form of transmit credit wait or credits to zero transition events. Drops may occur on any port type (Fibre Channel or Ethernet). Refer to Cisco Bug: CSCvj58687. |
March 2019 |
| QLogic - IO StreamGuard | Must be disabled so as to enable RSCN. | March 2019 |
| Switches – Fibre Channel, FCoE and IP - McData Sphereon |
Removed This company no longer exists (it was acquired by Brocade in 2006). |
March 2019 |
| Server Hardware - Microsoft Windows (general) |
Added 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. Refer to DataCore Hyperconverged Infrastructure for more information. 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, use iSCSI connections as ‘Loopbacks’ for SANsymphony DataCore Disks presented to Hyper-V Virtual Machines. |
|
| Windows 2008 R2 only |
Affects the DataCore Server A regression was introduced in Microsoft’s January 8th, 2019 security update (KB4480970). “Local users who are part of the local “Administrators” group may not be able to remotely access shares.” This affects DataCore’s ‘DcsAdmin’ user and symptoms include:
|
November 2018 |
| Network Adaptors (inc. iSCSI) - Hewlett Packard |
ProLiant BL460c (Gen10) server blades It has been reported that these server blades use NICs with Broadcom BCM57xxx chipsets – Refer to the Broadcom entry on the previous page for more details. |
November 2018 |
| Server Hardware - Microsoft Windows (general) - Windows 2016 |
Added BitLocker Drive Encryption This feature must be disabled on a DataCore Server as it prevents Disk Pools from functioning properly. |
November 2018 |
| Hewlett-Packard - Integrated Lights Out (ILO) |
Affects the DataCore Server Significant TZ (time zone) settings differences within the ILO software and the server’s own system clock/BIOS may result in the DataCore Executive service faulting. These faults will result in unexpected ‘Not Connected’ and/or ‘Logstore not available’ warning messages from other DataCore Servers in the group. Ensure that the TZ settings match. |
November 2018 |
| Storage Hardware - X-IO - ISE 2, G3 and G4 Storage Arrays |
Added DataCore recommend to use firmware 4.1.14 or higher which contains improvements to I/O queue handling that will help improve overall performance. |
November 2018 |
| Fibre Channel Adapters - Directly connected ports |
Removed This information has now been moved to: ‘Using direct-connected Fibre Channel Ports with a DataCore Server’. Refer to DataCore FAQ 1703. |
November 2018 |
| ISCSI and Network Adaptors - Hewlett-Packard |
Neither of these adaptors are supported by HP on Windows 2008 or later. Search Hewlett Packard’s Enterprise Support Center using keyword c01507703 (Last Updated 2008). |
November 2018 |
| Third Party Software - McAfee VirusScan | NA | October 2018 |
| Third Party Software - Any AV Software | NA | October 2018 |
| ISCSI and Network adaptors - Intel - All x710 Adaptors |
Updated Added a VMware KB as this ‘Known Issue’ will apply if configuring ESXi as a DataCore Server Hyperconverged Host. |
October 2018 |
| Server and storage controller hardware - NetApp, X-IO |
Removed NetApp All E Series arrays Cannot be used for SANsymphony Multi-Path Array (SMPA) configurations. X-IO ISE2 Use controller firmware versions 2.8.3 or later when used as storage for SANsymphony Shared Multipath Arrays (SMPA). The information regarding SMPA issues for both of these arrays is already documented in the ‘Shared Multi Port Array (SMPA) Tested Configurations. Refer to FAQ 1485. |
October 2018 |
| ISCSI and Network adaptors |
Added Mellanox Technologies – ConnectX-3 Adaptors Hewlett Packard – All Converged Network Adaptors Updated
|
February 2018 |
| Third Party Software – Microsoft |
Updated Affects the Host and the DataCore Server (Windows 2012 or 2012 R2 only): A regression was introduced in a Windows update from March 2017 that caused a TCP Port 'exhaustion' when one or more Microsoft iSCSI initiators cannot connect to a Target (e.g., because the DataCore Server is not available/shutdown or if there is a network problem preventing IP connections from being made). Symptoms include:
|
February 2018 |
| Storage arrays and controllers - Intel – NVMe storage | NA | December 2017 |
| Fibre Channel host bus adaptors - Emulex and QLogic |
Updated The information here was duplicated in both the 'Emulex' and 'HP' sections; therefore, the Emulex and QLogic sections have both been retitled to cover OEM Vendor equivalents as well. |
December 2017 |
| DataCore server hardware settings |
Removed Turbo Boost (Intel), Processor ‘States’ (aka C-states) and PowerNow Technology (AMD). The information for all of the above settings has been moved to the more appropriate 'Best Practice Guidelines for SANsymphony'. Refer to FAQ 1348. |
December 2017 |
| Fibre Channel host bus adaptors |
Removed Hewlett Packard - SN1000E and FC2142SR, Agilent, ATTO, Brocade and LSI. The information for all of the above HBAs has been moved to the more appropriate 'Qualified hardware components' document. Refer to FAQ 1529. |
December 2017 |
| Storage arrays and controllers - Smart Array in P2xx, P4xx, P7xx, P8xx and ProLiant Servers |
Added Update to Smart Array firmware Version 5.04 to Correct Intermittent Controller Lockup Issues. |
October 2017 |
| Switches (Fibre Channel and FCoE) - All Switch Manufacturers |
Added Registered State Change Notification (RSCN) settings |
June 2017 |
| Fibre Channel Host Bus Adaptors – Emulex Corporation |
Added 16GB HBA Models. |
June 2017 |
| Third-party Software – Microsoft Corporation |
Added The DataCore Server Operating System - Windows 2012 or 2012 R2 A regression was introduced in a Windows update issued in March 2017 that causes TCP Port 'exhaustion'. See the entry for more information |
June 2017 |
| Storage Arrays and Controllers – All Storage |
Updated 512b, 512(e)b and 4Kbyte sector support. |
June 2017 |
| Switches (Fibre Channel and FCoE) |
Removed Registered State Change Notification (RSCN) settings. These duplicate entries have all been removed and a single entry, under 'All Switch Manufacturers', has been added. |
June 2017 |
| Fibre Channel Host Bus Adaptors - Emulex Corporation |
Removed LP1150, Lpe1150 and Lpe111 - These HBAs could not take the DataCore Fibre Channel Driver and are documented as 'Discontinued' by Emulex. |
June 2017 |
| XenServer |
Removed "If using QLogic QLA405x/406x iSCSI HBAs, use QLogic’s firmware revision 3.01.49 or later …" This has been moved to the 'Known Issues' section in the Citrix XenServer Configuration Guide. |
April 2017 |
| Converged Network Adaptors |
Removed QLogic's Dual-Port, 10Gbps Ethernet-to-PCIe Converged Network Adaptor (CNA). For VMware ESX Hosts disable (a) select a LUN to Boot from, and (b) the adaptor BIOS. This has been moved to the 'Known Issues' section in the VMware ESXi Configuration Guide. |
April 2017 |
| Third-party Software – Microsoft Corporation |
Removed Offloaded Data Transfers (ODX). Only supported with SANsymphony-V 9.0 PSP4 and later. For earlier versions of SANsymphony-V, ODX must be disabled on the Host. Refer to Deploy Windows Offloaded Data Transfers. |
April 2017 |