Professional Documents
Culture Documents
NetApp
f. ForMultipathing andHP-UX
HP-UX, use the EMC PowerPath co-existence
default storage settings.
EFI boot
SAN bootsupport
using standard EFI or UEFI boot is supported only for hosts running HP-UX 11iv2, HP-UX 11iv3, and later. Check the specific configuration in IMT t
For all other host operating systems, SAN boot is supported only using the UEFI Legacy Option (BootBIOS).
Ethernet Switch Support
For FCoE configurations, only the models specifically listed in IMT are supported.
Ethernet
- Hostsupports
NetApp NIC, TCP/IP Offload
all 1GbE and (TOE)
10GbEAdapter, Host Bus
TCP/IP offload Adapter
(TOE) (HBA),
adapters and Converged
for software iSCSI andNetwork Adapter
NAS blade server(CNA) Model Support
configurations. Specific NIC or adapter
Third-party
Brocade Certifications with NetApp Storage Systems
Brocade Partner Network
Third-party Virtualization
NetApp supports Appliance
IBM's support of FASSupport - IBM Storage
storage systems Virtualization
with SVC. Controller
In the event (SVC) support situations, NetApp will diagnose basic storage hardw
of configuration
support, which provides an escalation process to IBM support and/or IBM SVC engineering. IBM maintains supported configurations for IBM N series and FA
Virtualization
Server running the Hyper-V as a role. Note that Microsoft Windows Server 2008/2012 Hyper-V does not run on Standard Edition.
To support 12 Node Cluster Data ONTAP SAN cluster on ONTAP 9.1 , Windows hosts running Server Versions 2012 and
2012 R2 with MSDSM needs to be patched with the following hotfix.
8533 Please refer to burt 1040557 for more information on the issue.
Hotfix KB2869606 is required for systems running Windows 2012 and Windows 2012R2, and must be obtained directly from
7493 Microsoft Product Support Services at (See next Cell)
For WUHU 7.1 installation below mentioned patches are required and must be obtained directly from Microsoft Product
Support Services at (See next Cell). -
Win 2016 - KB3197954
Win 2012 R2 - KB2955164*, KB2990170, KB3036614
Win 2008 R2 SP1 - KB2528357,KB2851144, KB2908783, KB2990170
Win 2008 SP2 - KB2684681, KB2990170, KB968675
NOTE* - Only KB2908783 is required but since it do not have a standalone installer for Win 2012, KB2955164 will suffice the
requirement [Refer the link https://support.microsoft.com/en-us/help/2908783/data-corruption-occurs-on-iscsi-luns-in-
8887 windows]
Hotfix 2869606 is required for systems running Windows Server 2012 and must be obtained directly from Microsoft Product
Support Services at (See next Cell) . Hotfixes 2990170, 2908783, 2822241, and 2845371 are recommended and can be
7802 obtained from Microsoft Product Support Services as well.
Hotfix 2869606 is required for systems running Windows Server 2012 R2 and must be obtained directly from Microsoft
Product Support Services at (See next Cell) . Hotfixes 2990170, 2845371, 2919355, and 2919442 are recommended and can
7803 be obtained from Microsoft Product Support Services as well.
The PowerShell Toolkit "Invoke-NcSsh" and "Invoke-NaSsh" commands fail. The issue
only occurs in ONTAP 9.3.
WORKAROUND
Hotfix Q2520235, Q2522766, Q2528357, Q2531907, and Q2532153 is required for systems running Windows 2008 R2 SP1,
5566 and must be obtained directly from Microsoft Product Support Services at (See next Cell)
Hotfixes 2522766, 2528357, 2908783 and 2869606 are required for systems running Windows Server 2008 R2 SP1 and must
be obtained directly from Microsoft Product Support Services at (See next Cell) . Hotfix 2990170 is recommended and can be
7823 obtained from Microsoft Product Support Services as well.
For release notes and important information on deployment of Brocade HBAs and CNAs with NetApp Storage, please refer to:
5056 (See next Cell)
Info
For reference to the 16G ICM and 40g Virtual Component please refer to the below documents
https://www.hpe.com/h20195/v2/GetPDF.aspx/c04815256.pdf
https://www.hpe.com/h20195/v2/GetPDF.aspx/c04815258.pdf
For reference please refer to HPE Synergy Configuration and Compatibility Guide:
231 Requires installation of the Microsoft iSCSI initiator service only. Microsoft iSCSI software initiator is not required.
The NetApp Windows Host Utilities are available at no charge and can be downloaded from the NetApp on the Web (NOW)
site (See next Cell). The NetApp Windows Host Utilities consist of software and documentation that help a user optimize host
configurations for support of NetApp Fibre Channel and iSCSI storage systems in a Windows host environment. The NetApp
237 Host Utilities do not include HBAs or HBA drivers/firmware (as of FCP Windows Attach Kit 3.0)
Emulex HBA and CNA drivers and firmware qualified by NetApp are available from the NetApp page of the Emulex Web site -
246 www.emulex.com/ts/index.html.
Qlogic HBA and CNA drivers and firmware qualified by NetApp are available from the NetApp page of the QLogic Web site -
251 (See next Cell)
NetApp supports all rack server hardware models corresponding to the server or processor architecture listed in the
interoperability matrix, but does not specify server models by brand.
This configuration was edited mid-2016 to remove specific (or less general) server hardware information from the 'Host
Platform' field and replace it with more general components. NetApp support overall has not been reduced in any way by this
change.
IMT is not an exhaustive hardware support matrix for all aspects of the host-side configuration. The customer should verify
8381 the supportability of their configuration with all appropriate hardware vendor HCL/interoperability matrices.
382 MPIO via Veritas DMP DSM requires Veritas Storage Foundation 5.0
383 MPIO via Veritas DMP DSM is supported only in Active-Active (round-robin) mode
7039 SLES 11 SP2 is supported as a Guest OS only with Kernel version: 3.0.38-0.5.1-default.
Dynamic Disks are supported with the requirement that all LUNs composing the dynamic disks are located on the same
storage controller. Note, dynamic disks are not supported with SnapDrive. Dynamic disks are not supported for use with
256 Windows Native Clustering.
With Microsoft Windows operating systems, the memory paging system requires fast access to the pagefile.sys file. Delays in
access requests to or from the paging file may cause the operating system to halt and require a reboot. If pagefile latency
issues are suspected, Microsoft recommends placing the pagefile on the host's local hard disk to guarantee reliable access.
This recommendation and other considerations related to booting Windows hosts through Fibre Channel are overviewed in
the following Microsoft article:
(See next Cell) For Microsoft recommendations regarding SAN Boot in MSCS configurations, see the following Microsoft
258 article: http://support.microsoft.com/default.aspx?scid=kb;en-us;886569
For additional SnapDrive or for SnapManager compatibility information, see the SnapDrive compatibility matrix at (See next
261 Cell).
NetApp supports the following third-party HBA models so long as the HBA is used with NetApp-qualifed driver and firmware
levels and within configurations outlined in the NetApp Support Matrix: HP FCA2214DC (QLogic QLA2342); HP FC2142SR
263 (Emulex LPe1150), HP FC2242SR (Emulex LPe11002), HP FC2242 (Emulex LP11002), HP FC2143 (Emulex LP1150).
3914 ALUA is required for the native MSDSM and is supported on Windows Server 2008 and later with Ontap 7.3.0 and later.
Hotfix Q2796995 is recommended for systems running Windows 2012 with NetApp Data ONTAP 8.2 and higher, and must be
6927 obtained directly from Microsoft Product Support Services at (See next Cell)
If you are using Windows Native Multipathing (Microsoft MS DSM) and have hosts that simultaneously connect to multiple
NetApp SAN targets running various versions of Data ONTAP must use WHU 6.0.1 if any one of those targets is using
6928 Clustered Data ONTAP 8.1.x or earlier, or 7-mode Data ONTAP 8.1.2 or earlier.
NetApp supports all HP/IBM/Dell Blades corresponding to the server or processor architecture listed in the interoperability
matrix, but does not specify Blades by its model.
This configuration was edited in Nov-2016 to remove specific (or less general) server blades information from the 'Host
Platform' field and replace it with more general components. NetApp support overall has not been reduced in any way by this
change.
IMT is not an exhaustive hardware support matrix for all aspects of the host-side configuration. The customer should verify the
8595 supportability of their configuration with all appropriate hardware vendor HCL/interoperability matrices.
Virtual Fibre Channel (vFC) is not supported for Windows Server 2012 and vFC is not supported
on 7 Mode with any Version on Windows OS.
vFC was not working as expected in 7 mode due to various issues seen in testing and hence 7 Mode configuration with vFC
6550 in any versions of Windows OS was not supported. Please refer to burts 696976 and 767620 for more information.
During installation of Windows Unified Host Utilities (WUHU) on Windows Server 2016 OS , The WUHU may prompt for a
hotfix which is related to previous versions of Windows Server OS and is not related to Server 2016.
Please ignore this hotfix request and the WUHU 7.0 installation should progress and complete successfully.
8535 This hotfix requirement for 2016 will be removed in the next release of WUHU.
NetApp supports all Guest Operating Systems (GOS) that are listed as supported in the Microsoft Hyper-V GOS support
8729 matrix.
Support for NetApp iSCSI LUNs presented directly to a Guest Operating System (GOS) should be validated against the IMT
treating the GOS as a standard host OS running on a physical server. In this case, the GOS owns and manages both the
filesystem and the TCP/IP connection to the NetApp controllers. The overall behavior of the NetApp storage resources is not
affected by the Hyper-V hypervirsor here, so the GOS may be treated as a standard host OS running on a physical server.
The Hyper-V hypervisor only provides a virtual IP network interface, and NetApp generally supports IP infrastructures without
a need for specific switch or NIC support and its management of the NetApp storage resources is independent of the Hyper-V
hypervisor. So you need not validate the specific Hyper-V configuration against the NetApp IMT in this case, but the GOS
must still be listed as supported in the Microsoft Hyper-V GOS support matrix.
For example, a Win2K12 GOS using the Microsoft iSCSI initiator on a Hyper-V hypervisor to directly connect to a NetApp
iSCSI LUN must be validated against the NetApp IMT as a Win2K12 standard OS running on a physical server, and should
also be listed as supported in the Microsoft Hyper-V GOS support matrix and must adhere to all Hyper-V requirements. This is
to ensure that the Win2K12 GOS is running in a stable configuration and does not have any restrictions that may affect
8730 NetApp storage connectivity. But there's no need to validate the specific Hyper-V configuration against the NetApp IMT.
Support for NetApp storage presented directly to a Guest Operating System (GOS) using an Hyper-V pass-through LUN must
be validated against the NetApp IMT in two steps here, because two operating systems are involved with the storage
connectivity in this case - the GOS and the Hyper-V hypervisor. First, the GOS must be validated as an standard host OS
running on a physical server. This ensures the GOS can correctly use the Hyper-V pass-through NetApp LUN as if it was
running on a physical server. Second, the Hyper-V hypervisor must be validated against the NetApp IMT, as it is responsible
for maintaining the FC/iSCSI protocol connectivity to the NetApp LUN. In addition, the GOS must also be listed as supported
in the Microsoft Hyper-V GOS support matrix, and must adhere to all Hyper-V requirements.
For example, a Win2K12 GOS using a Hyper-V pass-through NetApp FC device should be validated against the NetApp IMT
as a standard Win2K12 OS running on a physical server. As the Hyper-V hypervisor is responsible for the FC connection to
the NetApp controllers, the exact Hyper-V configuration used here must also be validated against the NetApp IMT using that
version of Hyper-V as a host OS. The Win2K12 GOS would also need to be listed as supported on the Microsoft Hyper-V
8731 GOS support matrix, and adhere to all Hyper-V requirements.
Oracle ASM:
Oracle ASM is a lightweight combined volume manager and filesystem. NetApp supports the use of ASM with SAN
connectivity where (a) the configuration is generally supported by Oracle and conforms to all Oracle configuration
requirements and (b) the complete configuration can be found within the NetApp Interoperability Matrix in every respect with
the exception of the volume manager and filesystem. For example, when deploying ASM on AIX, the configuration must
include a supported version of the AIX operating system, HBA, HBA driver, and multipathing software. The columns for
filesystem and volume manager can be disregarded.
Caution - when using the Oracle Unbreakable Enterprise Kernel with asmlib, care must be taken when performing an upgrade
ONTAP of an ASM diskgroup created using ONTAP 8.0.3 and earlier or ONTAP 8.1 and earlier. Changes in the SCSI target
software introduced in ONTAP 8.0.4 and 8.1.1 interfere with asmlib communication. See Oracle document ID 1500460.1 for
details.
Oracle RAC:
NetApp supports the use of SAN resources under control of Oracle RAC. Support will be offered where (a) the configuration
conforms to all Oracle requirements and (b) the complete configuration can be found within the NetApp Interoperability matrix.
Support is limited to issues arising from SAN connectivity itself. Customers seeking assistance with configuration and
management of Oracle RAC should contact Oracle or NetApp Professional Services. When a support issue cannot be clearly
linked to a problem with connectivity to NetApp hardware and software, the NetApp support center may require the customer
8605 to open a case with the Oracle or the OS vendor in order to provide additional analysis.
NetApp supports the O/S vendor-specific versions of the host filesystems listed in the interoperability matrix, but no longer
specifies them by vendor. Instead host filesystems are now listed generically. This configuration was edited in Dec-2016 to
remove specific (or less general) host filesystem information from the "Host Filesystems" field and replace it with more general
components. NetApp support overall has not been reduced in any way by this change. IMT is not an exhaustive hardware
support matrix for all aspects of the host-side configuration. The customer should verify the supportability of their configuration
8606 with all appropriate hardware vendor HCL/interoperability matrices.
rver Versions 2012 and
https://support.microsoft.com/en-us/kb/3036614
http://h20566.www2.hpe.com/hpsc/doc/public/display\?
sp4ts.oid=1008615198&docId=emr_na-
c05061206&docLocale=en_US
is not required.
NetApp on the Web (NOW)
at help a user optimize host
t environment. The NetApp http://now.netapp.com/NOW/download/software/sanho
st_win/Windows/
erability-in-windows-se
https://support.microsoft.com/en-
nz/help/4048968/windows-eot-font-engine-information-
disclosure-vulnerability
ed in the interoperability
leases.
ccessfully.
th configuration and
port issue cannot be clearly
r may require the customer
ility matrix, but no longer
was edited in Dec-2016 to
d replace it with more general
an exhaustive hardware
rtability of their configuration