Professional Documents
Culture Documents
Windows 2008 R2 Enterprise Edition SP1
Windows 2008 R2 Enterprise Edition SP1
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.
7137 This configuration is supported with 2.1(2c) and 2.1(2d) UCSM releases.
P81E is supported with upstream connectivity to Cisco Nexus Switches for FCoE with Adapter-FEX functionality and IMT
supported NX-OS firmware 5.1(3)N2(1b) or greater within the NX-OS 5.x line of firmware releases.
6625 For more information on Adapter-FEX, please please refer to: (See next Cell)
The Cisco UCS FCoE Initiator is supported to both NetApp Fibre Channel and FCoE Targets.
For critical switch support information with Cisco UCS B-Series (and C-Series managed configurations), please consult the
following IMT rows in the "SAN-Switch (Switch)" Storage Solution:
For UCS B-Series 3.0(1x) releases:
7778 20141021-200445697
The Cisco UCS FCoE Initiator is supported to both NetApp Fibre Channel and FCoE Targets.
For critical switch support information with Cisco UCS B-Series (and C-Series managed configurations), please consult the
following IMT rows in the "SAN-Switch (Switch)" Storage Solution:
For UCS B-Series 2.2(6x) releases: 20151211-021637975
For UCS B-Series 2.2(5x) releases: 20150903-072235888
For UCS B-Series 2.2(4x) releases: 20150903-214344214
For UCS B-Series 2.2(3x) releases: 20141021-091611066
For UCS B-Series 2.2(2x) releases: 20140620-173430621
For UCS B-Series 2.2(1x) releases: 20140218-111632988
For UCS B-Series 2.1(3x) releases: 20131025-064439148
For UCS B-Series 2.1(2x) releases: 20130807-203753077
For UCS B-Series 2.1(1x) releases:20130123-065704867
For UCS B-Series 2.0(1x) releases:20111009-173337978
For UCS B-Series 2.0(2x) releases:20120312-185126253
For UCS B-Series 2.0(3x) releases:20120712-122857952
For UCS B-Series 2.0(4x) releases:;20121002-061750399
For UCS B-Series 2.0(5x) releases:20130528-175017205
7785 For UCS B-Series 1.4(x) releases:20110130-05503889
8568 This configuration is supported with 2.2(8b), 2.2(8c), 2.2(8d) UCSM releases.
For more information on Adapter-FEX, please please refer to: (See next Cell)
This row contains a driver version which has successfully passed basic NetApp qualification testing. However IBM has
qualified a different, IBM-specific driver for IBM BladeCenter HBAs.
If you do not need to change driver versions, we recommend using your current driver version until the new driver is listed in
3454 the NetApp interoperability matrix
In UCS End-Host Mode on a UCS 6x00 Fabric Interconnect:
FC connections from a Cisco UCS Fabric Interconnect may be made to a MDS Switch running 6.2.1 or later within 6.2(x)
releases or to a Nexus 5xxx Switch running 5.1(3) [5.1(3)N2(1b) release or later within 5.1(3) releases] or 5.2(1) [5.2(1)N1(1)
or later within 5.2(1) releases] or 6.0(2) [6.0(2)N1(1) or later within 6.0(2) releases] or firmware releases.For Nexus 5672
firmware release 7.0(1)N1(1) is supported. For Nexus 6000 firmware release 6.0(2)N2(1) is supported.
FC connections from the Cisco UCS Fabric Interconnect Switch can be made to a Brocade switch running FOS 6.4.1b, 6.4.2b,
6.4.3b, 7.0.2, 7.0.1b, 7.1.0a, 7.0.1a, 7.1.1.
FCoE connections from the Cisco UCS Fabric Interconnect Switch must connect to a Nexus 5xxx Switch running 5.1(3)
[5.1(3)N2(1b) release or later within 5.(1(3) releases] or 5.2(1) [5.2(1)N1(1) or later within 5.2(1) releases] firmware or a
Nexus 7000 switch running 6.1(1) or greater. For Nexus 5672 firmware release 7.0(1)N1(1) is supported.
FCoE connections from the Cisco UCS Fabric Interconnect Switch to a Brocade switch are NOT supported.
FC ISL connections from the Cisco UCS Fabric Interconnect Switch to a Brocade switch are NOT supported.
Direct Attach FC and FCoE target connections from a NetApp controller to a Cisco UCS 6x00 Fabric Interconnect switch are
supported with 2.2(x). UCS Manager-Based Fibre Channel zoning is supported. UCS Fabric Interconnect Unified Storage
Ports with simultaneous NAS and FCoE access is supported.
For all configurations, please make sure that Cisco supports the configuration as part of their Hardware Compatibility List
8449 (see: (See next Cell) ). ONLY configurations on NetApp's IMT and Cisco HCL are supported by NetApp.
8961 This configuration is supported with 2.2(8i) ,2.2(8j) and 2.2(8l) UCSM releases.
For release notes and important information on deployment of Cisco UCS with NetApp Storage, please refer to: (See next
4995 Cell)
In UCS End-Host Mode on a UCS 6x00 Fabric Interconnect:
FC connections from a Cisco UCS Fabric Interconnect may be made to a MDS Switch running 4.2.1b or 6.2.1(see (See next
Cell) for supported firmware versions) or to a Nexus 5xxx Switch running 5.1(3) [5.1(3)N2(1b) release or later within 5.1(3)
releases] or 5.2(1) [5.2(1)N1(1) or later within 5.2(1) releases] or 6.0(2) [6.0(2)N1(1) or later within 6.0(2) releases] or
firmware releases.For Nexus 5672 firmware release 7.0(1)N1(1) is supported. For Nexus 6000 firmware release 6.0(2)N2(1)
is supported.
FC connections from the Cisco UCS Fabric Interconnect Switch can be made to a Brocade switch running FOS 6.4.1b, 6.4.2b,
6.4.3b, 7.0.2, 7.0.1b, 7.1.0a, 7.0.1a, 7.1.1.
FCoE connections from the Cisco UCS Fabric Interconnect Switch must connect to a Nexus 5xxx Switch running 5.1(3)
[5.1(3)N2(1b) release or later within 5.(1(3) releases] or 5.2(1) [5.2(1)N1(1) or later within 5.2(1) releases] firmware or a
Nexus 7000 switch running 6.1(1) or greater. For Nexus 5672 firmware release 7.0(1)N1(1) is supported.
FCoE connections from the Cisco UCS Fabric Interconnect Switch to a Brocade switch are NOT supported.
FC ISL connections from the Cisco UCS Fabric Interconnect Switch to a Brocade switch are NOT supported.
Direct Attach FC and FCoE target connections from a NetApp controller to a Cisco UCS 6x00 Fabric Interconnect switch are
supported with 2.2(x). UCS Manager-Based Fibre Channel zoning is supported. UCS Fabric Interconnect Unified Storage
Ports with simultaneous NAS and FCoE access is supported.
For all configurations, please make sure that Cisco supports the configuration as part of their Hardware Compatibility List
(see: http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_list.html ). ONLY configurations on NetApp's
8201 IMT and Cisco HCL are supported by NetApp.
The Brocade 415, 425, 815, 825, 1860 adapter ports configured as HBA and HP 590647-B21 (Brocade 804) HBA can only be
6285 used with Brocade FC capable switches running firmware per the appropriate row in the IMT.
8206 This configuration is supported with 2.2(3g) & 2.2(3h) UCSM releases.
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.
Requires:
KB3033929 : Starting in January 2016, Microsoft requires that Windows server 2008 R2 drivers must be signed by using
SHA-2. For Windows server 2008 R2 and Windows server 2008 R2 SP1, before updating to this driver version you must
install hotfix KB3033929 to allow Windows Server 2008 R2 to recognize SHA-2 signed drivers.
8464 (See next Cell)
P81E and 1225 adapters are supported with connectivity to Cisco Nexus 2232 Fabric Extenders and UCS B-Series Fabric
Interconnects.
In these configurations system release versions on both C-Series and B-Series must be compatible, please consult the
following Cisco documentation at:
* UCS B-Series and C-Series HCLs located at: (See next Cell)
* Server Installation and Service Guide for your specific C-Series Server located at:
http://www.cisco.com/en/US/products/ps10493/prod_installation_guides_list.html
If you need additional information about supported Cisco UCS C-Series managed configurations, please consult Cisco
6431 support.
In UCS End-Host Mode on a UCS 6x00 Fabric Interconnect:
FC connections from a Cisco UCS Fabric Interconnect may be made to a MDS Switch running 4.2.1b or 6.2.1(see (See next
Cell) for supported firmware versions) or to a Nexus 5xxx Switch running 5.1(3) [5.1(3)N2(1b) release or later within 5.1(3)
releases] or 5.2(1) [5.2(1)N1(1) or later within 5.2(1) releases] or 6.0(2) [6.0(2)N1(1) or later within 6.0(2) releases] or
firmware releases.For Nexus 5672 firmware release 7.0(1)N1(1) is supported. For Nexus 6000 firmware release 6.0(2)N2(1)
is supported.
FC connections from the Cisco UCS Fabric Interconnect Switch can be made to a Brocade switch running FOS 6.4.1b, 6.4.2b,
6.4.3b, 7.0.2, 7.0.1b, 7.1.0a, 7.0.1a, 7.1.1.
FCoE connections from the Cisco UCS Fabric Interconnect Switch must connect to a Nexus 5xxx Switch running 5.1(3)
[5.1(3)N2(1b) release or later within 5.(1(3) releases] or 5.2(1) [5.2(1)N1(1) or later within 5.2(1) releases] firmware or a
Nexus 7000 switch running 6.1(1) or greater. For Nexus 5672 firmware release 7.0(1)N1(1) is supported.
FCoE connections from the Cisco UCS Fabric Interconnect Switch to a Brocade switch are NOT supported.
FC ISL connections from the Cisco UCS Fabric Interconnect Switch to a Brocade switch are NOT supported.
Direct Attach FC and FCoE target connections from a NetApp controller to a Cisco UCS 6x00 Fabric Interconnect switch are
supported with 2.2(x). UCS Manager-Based Fibre Channel zoning is supported. UCS Fabric Interconnect Unified Storage
Ports with simultaneous NAS and FCoE access is supported.
For all configurations, please make sure that Cisco supports the configuration as part of their Hardware Compatibility List
(see: http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_list.html ). ONLY configurations on NetApp's
8352 IMT and Cisco HCL are supported by NetApp.
Hotfix Q2522766 is required for systems running Windows 2008 R2 SP1, and must be obtained directly from Microsoft
5666 Product Support Services at (See next Cell)
The Cisco UCS FCoE Initiator is supported to both NetApp Fibre Channel and FCoE Targets.
For critical switch support information with Cisco UCS B-Series (and C-Series managed configurations), please consult the
following IMT rows in the "SAN-Switch (Switch)" Storage Solution:
For UCS B-Series 2.2(7x) releases : 20160427-044138724
8354 For UCS B-Series 2.2(8x) releases : 20160804-045830540
The Cisco UCS FCoE Initiator is supported to both NetApp Fibre Channel and FCoE Targets.
For critical switch support information with Cisco UCS B-Series (and C-Series managed configurations), please consult the
following IMT rows in the "SAN-Switch (Switch)" Storage Solution:
For UCS B-Series 2.2(7x) releases : 20160427-044138147
8355 For UCS B-Series 2.2(8x) releases : 20160804-045831045
7204 This configuration is supported with 2.1(3a), 2.1(3b), 2.1(3c),2.1(3d), 2.1(3e), 2.1(3f) and 2.1(3g) UCSM releases.
In UCS End-Host Mode on a UCS 6x00 Fabric Interconnect:
FC connections from a Cisco UCS Fabric Interconnect may be made to a MDS Switch running 4.2.1b or 6.2.1(see (See next
Cell) for supported firmware versions) or to a Nexus 5xxx Switch running 5.1(3) [5.1(3)N2(1b) release or later within 5.1(3)
releases] or 5.2(1) [5.2(1)N1(1) or later within 5.2(1) releases] or 6.0(2) [6.0(2)N1(1) or later within 6.0(2) releases] or
firmware releases.For Nexus 5672 firmware release 7.0(1)N1(1) is supported. For Nexus 6000 firmware release 6.0(2)N2(1)
is supported.
FC connections from the Cisco UCS Fabric Interconnect Switch can be made to a Brocade switch running FOS 6.4.1b, 6.4.2b,
6.4.3b, 7.0.2, 7.0.1b, 7.1.0a, 7.0.1a, 7.1.1.
FCoE connections from the Cisco UCS Fabric Interconnect Switch must connect to a Nexus 5xxx Switch running 5.1(3)
[5.1(3)N2(1b) release or later within 5.(1(3) releases] or 5.2(1) [5.2(1)N1(1) or later within 5.2(1) releases] firmware or a
Nexus 7000 switch running 6.1(1) or greater. For Nexus 5672 firmware release 7.0(1)N1(1) is supported.
FCoE connections from the Cisco UCS Fabric Interconnect Switch to a Brocade switch are NOT supported.
FC ISL connections from the Cisco UCS Fabric Interconnect Switch to a Brocade switch are NOT supported.
Direct Attach FC and FCoE target connections from a NetApp controller to a Cisco UCS 6x00 Fabric Interconnect switch are
supported with 2.2(x). UCS Manager-Based Fibre Channel zoning is supported. UCS Fabric Interconnect Unified Storage
Ports with simultaneous NAS and FCoE access is supported.
For all configurations, please make sure that Cisco supports the configuration as part of their Hardware Compatibility List
(see: http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_list.html ). ONLY configurations on NetApp's
8102 IMT and Cisco HCL are supported by NetApp.
7472 This configuration is supported with 2.2(1b), 2.2(1c), 2.2(1d) and 2.2(1e) UCSM releases.
The Cisco UCS FCoE Initiator is supported to both NetApp Fibre Channel and FCoE Targets.
For critical switch support information with Cisco UCS B-Series (and C-Series managed configurations), please consult the
following IMT rows in the "SAN-Switch (Switch)" Storage Solution:
For UCS B-Series 2.2(1x) releases: 20140218-111632988
For UCS B-Series 2.1(3x) releases: 20131025-064439148
For UCS B-Series 2.1(2x) releases: 20130807-203753077
For UCS B-Series 2.1(1x) releases:20130123-065704867
For UCS B-Series 2.0(1x) releases:20111009-173337978
For UCS B-Series 2.0(2x) releases:20120312-185126253
For UCS B-Series 2.0(3x) releases:20120712-122857952
For UCS B-Series 2.0(4x) releases:;20121002-061750399
For UCS B-Series 2.0(5x) releases:20130528-175017205
7474 For UCS B-Series 1.4(x) releases:20110130-05503889
Cluster Data ONTAP would be supporting 12 Node cluster from 9.1. Windows hosts running Server Versions 2008R2 SP1 and
previous releases running with MSDSM may BSOD in MSDSM.sys module.
Workaround to use 12 Nodes NetApp Cluster on 9.1 is to either upgrade to Windows Server 2012 and later releases OR
migrate from Windows MSDSM to ONTAP DSM 4.1P1
8503 Please refer to burt 1017813 for more information on the issue.
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]
In UCS End-Host Mode on a UCS 6x00 Fabric Interconnect:
FC connections from a Cisco UCS Fabric Interconnect may be made to a MDS Switch running 4.2.1b or 6.2.1(see (See next
Cell) for supported firmware versions) or to a Nexus 5xxx Switch running 5.1(3) [5.1(3)N2(1b) release or later within 5.1(3)
releases] or 5.2(1) [5.2(1)N1(1) or later within 5.2(1) releases] or 6.0(2) [6.0(2)N1(1) or later within 6.0(2) releases] or
firmware releases.For Nexus 5672 firmware release 7.0(1)N1(1) is supported. For Nexus 6000 firmware release 6.0(2)N2(1)
is supported.
FC connections from the Cisco UCS Fabric Interconnect Switch can be made to a Brocade switch running FOS 6.4.1b, 6.4.2b,
6.4.3b, 7.0.2, 7.0.1b, 7.1.0a, 7.0.1a, 7.1.1.
FCoE connections from the Cisco UCS Fabric Interconnect Switch must connect to a Nexus 5xxx Switch running 5.1(3)
[5.1(3)N2(1b) release or later within 5.(1(3) releases] or 5.2(1) [5.2(1)N1(1) or later within 5.2(1) releases] firmware or a
Nexus 7000 switch running 6.1(1) or greater. For Nexus 5672 firmware release 7.0(1)N1(1) is supported.
FCoE connections from the Cisco UCS Fabric Interconnect Switch to a Brocade switch are NOT supported.
FC ISL connections from the Cisco UCS Fabric Interconnect Switch to a Brocade switch are NOT supported.
Direct Attach FC and FCoE target connections from a NetApp controller to a Cisco UCS 6x00 Fabric Interconnect switch are
supported with 2.2(x). UCS Manager-Based Fibre Channel zoning is supported. UCS Fabric Interconnect Unified Storage
Ports with simultaneous NAS and FCoE access is supported.
For all configurations, please make sure that Cisco supports the configuration as part of their Hardware Compatibility List
(see: http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_list.html ). ONLY configurations on NetApp's
8121 IMT and Cisco HCL are supported by NetApp.
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)
For release notes and important information on deployment of Brocade HBAs and CNAs with NetApp Storage, please refer to:
5056 (See next Cell)
Hotfix Q981379 (MSDSM), Q979711, Q2520235, Q2522766, Q2528357 and Q2532153 are required for systems running
5058 Windows 2008 R2, and must be obtained directly from Microsoft Product Support Services at (See next Cell).
Hotfix Q981379 (MSDSM) and Q2522766 are required for systems running Windows 2008 R2, and must be obtained directly
5700 from Microsoft Product Support Services at (See next Cell).
7876 This configuration is supported with 2.2(3a), 2.2(3b), 2.2(3c) and 2.2(3d) UCSM releases.
SAN booting is supported only with legacy BIOS systems. SAN booting is not supported with
5061 Extensible Firmware Interface (EFI) based systems.
7877 This configuration is supported with 2.2(3d) & 2.2(3e) UCSM releases.
5062 iSCSI offload is supported only with iSCSI software target using 10GbE NIC(s) in the storage controller.
7751 This configuration is supported with 2.2(3a), 2.2(3b) and 2.2(3c) UCSM releases.
The adapter firmware have been updated from 4.1(1) to 4.1(2) to align with Cisco HCL, here is the link:
The Cisco UCS FCoE Initiator is supported to both NetApp Fibre Channel and FCoE Targets.
For critical switch support information with Cisco UCS B-Series (and C-Series managed configurations), please consult the
following IMT rows in the "SAN-Switch (Switch)" Storage Solution:
For UCS B-Series 2.1(3x) releases: 20131025-064439148
For UCS B-Series 2.1(2x) releases: 20130807-203753077
For UCS B-Series 2.1(1x) releases:20130123-065704867
For UCS B-Series 2.0(1x) releases:20111009-173337978
For UCS B-Series 2.0(2x) releases:20120312-185126253
For UCS B-Series 2.0(3x) releases:20120712-122857952
For UCS B-Series 2.0(4x) releases:;20121002-061750399
For UCS B-Series 2.0(5x) releases:20130528-175017205
5845 For UCS B-Series 1.4(x) releases:20110130-05503889
FCoE direct connect is not supported in cDOT with UCS firmware 3.0(1c),3.0(1d) and 3.0(2c). FCP and iSCSI Direct Connect
7766 are supported in cDOT, In 7-mode, FCP, iSCSI and FCoE are all supported for Direct Connect.
In UCS End-Host Mode on a UCS 6x00 Fabric Interconnect:
FC connections from a Cisco UCS Fabric Interconnect may be made to a MDS Switch running 4.2.1b or 6.2.1(see (See next
Cell) for supported firmware versions) or to a Nexus 5xxx Switch running 5.1(3) [5.1(3)N2(1b) release or later within 5.1(3)
releases] or 5.2(1) [5.2(1)N1(1) or later within 5.2(1) releases] or 6.0(2) [6.0(2)N1(1) or later within 6.0(2) releases] or
firmware releases.For Nexus 5672 firmware release 7.0(1)N1(1) is supported. For Nexus 6000 firmware release 6.0(2)N2(1)
is supported.
FC connections from the Cisco UCS Fabric Interconnect Switch can be made to a Brocade switch running FOS 6.4.1b, 6.4.2b,
6.4.3b, 7.0.2, 7.0.1b, 7.1.0a, 7.0.1a, 7.1.1.
FCoE connections from the Cisco UCS Fabric Interconnect Switch must connect to a Nexus 5xxx Switch running 5.1(3)
[5.1(3)N2(1b) release or later within 5.(1(3) releases] or 5.2(1) [5.2(1)N1(1) or later within 5.2(1) releases] firmware or a
Nexus 7000 switch running 6.1(1) or greater. For Nexus 5672 firmware release 7.0(1)N1(1) is supported.
FCoE connections from the Cisco UCS Fabric Interconnect Switch to a Brocade switch are NOT supported.
FC ISL connections from the Cisco UCS Fabric Interconnect Switch to a Brocade switch are NOT supported.
Direct Attach FC and FCoE target connections from a NetApp controller to a Cisco UCS 6x00 Fabric Interconnect switch are
supported with 2.2(x). UCS Manager-Based Fibre Channel zoning is supported. UCS Fabric Interconnect Unified Storage
Ports with simultaneous NAS and FCoE access is supported.
For all configurations, please make sure that Cisco supports the configuration as part of their Hardware Compatibility List
(see: http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_list.html ). ONLY configurations on NetApp's
8154 IMT and Cisco HCL are supported by NetApp
8671 This configuration is supported with 2.2(6j) UCSM release
Info
Windows Server 2008 SE = Windows Server 2008 Standard Edition (32-bit, x86)
Windows Server 2008 EE = Windows Server 2008 Enterprise Edition (32-bit, x86)
Windows Server 2008 SE SP1/SP2 (x86) = Windows Server 2008 Standard Edition with SP1/SP2 (32-bit, x86)
Windows Server 2008 EE SP1/SP2 (x86) = Windows Server 2008 Enterprise Edition with SP1/SP2 (32-bit, x86)
Windows Server 2008 SE (x64) = Windows Server 2008 Standard x64 Edition (64-bit, x64)
Windows Server 2008 EE (x64) = Windows Server 2008 Enterprise x64 Edition (64-bit, x64)
Windows Server 2008 SE SP1/SP2 (x64) = Windows Server 2008 Standard x64 Edition with SP1/SP2 (64-bit, x64)
Windows Server 2008 EE SP1/SP2 (x64) = Windows Server 2008 Enterprise x64 Edition with SP1/SP2 (64-bit, x64)
Windows Server 2008 R2 SE (x86) = Windows Server 2008 R2 Standard Edition (32-bit, x86)
Windows Server 2008 R2 EE (x86) = Windows Server 2008 R2 Enterprise Edition (32-bit, x86)
Windows Server 2008 R2 SE SP2 (x86) = Windows Server 2008 R2 Standard Edition with SP2 (32-bit, x86)
Windows Server 2008 R2 EE SP2 (x86) = Windows Server 2008 R2 Enterprise Edition with SP2 (32-bit, x86)
Windows Server 2008 R2 SE (x64) = Windows Server 2008 R2 Standard x64 Edition (64-bit, x64)
Windows Server 2008 R2 EE (x64) = Windows Server 2008 R2 Enterprise x64 Edition (64-bit, x64)
Windows Server 2008 R2 SE SP2 (x64) = Windows Server 2008 R2 Standard x64 Edition with SP2 (64-bit, x64)
Windows Server 2008 R2 EE SP2 (x64) = Windows Server 2008 R2 Enterprise x64 Edition with SP2 (64-bit, x64)
Windows Server 2008 EE SP1/SP2 (IA64) = Windows Server 2008 Enterprise Edition with SP1/SP2 for Itanium-based
Systems (IA64)
5154 Server Core installation option of Windows Server® 2008 or Windows Server® 2008 R2 is supported.
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)
The LPe111-E is targeted at SMB SANs and can support up to 16 target port logins. The card has been qualified against the
1901 FAS200, FAS2000, and FAS3000 series. Any other configurations require a PVR to determine supportability.
For Windows 2008 versions: Data ONTAP DSM version 3.5 requires the following hotfixes:
Windows 2008 SP2 - Q968675, and Q2522766. Windows 2008 R2 - Q2522766, Q2528357, and Q2520235. Windows 2008
R2SP1 - Q2522766, Q2528357, Q2520235 and Q2531907.
These hotfixes must be obtained directly from Microsoft Product Support Services at (See next Cell). The Data ONTAP DSM
5679 installation tool checks for appropriate OS patches and prompts users to update or obtain patches, as required.
Intel PCI-Express implementation of software iSCSI boot supports specification of a primary and a secondary boot port in a
304 single system, in addition to Windows MPIO with Microsoft iSCSI DSM supported once the OS is running.
8176 This configuration is supported with 2.2(4b) & 2.2(4c) UCSM releases.
Emulex LP11000 4Gb PCI-X single port = NetApp Part Number X1086A-R6; LP11002 4Gb PCI-X dual port = NetApp Part
243 Number X1087A-R6. NetApp does not currently sell the LP1150 4Gb PCI-X single-port midrange HBA.
NetApp does not currently sell or spare the Emulex LPe1100x 4Gb PCI-Express HBA or LPe1150 4Gb PCI-Express single-
244 port midrange HBA.
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.
257 NetApp cfmode (controller failover) : SSI (Single System Image); S (Standby); P (Partner); DF (Dual Fabric); M (Mixed).
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
NetApp supports all Cisco supported Host Blade Platforms listed in the Cisco UCS Hardware and Software Interoperability
Matrix, but does not specify the individual Blade models.
This change is made to remove specific (or less general) Blade model 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
8450 supportability of their configuration with Cisco HCL/Interoperability Matrix. ( Refer: (See next Cell) )
To avoid damaging your HBA make sure you are running the supported HBA driver, firmware and BIOS before installing the
4418 Netapp Windows Host Utilities or the Data ONTAP DSM. See bug 383779 at Bugs Online.
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).
Hotfix Q959384 is required for Windows Server 2008 (RTM/SP1), and must be obtained directly from Microsoft Product
Support Services at (See next Cell). The Windows Host Utilities installation tool checks for appropriate OS patches and
3015 prompts users to update or obtain patches, as required.
8200 This configuration is supported with 2.2(6c), 2.2(6d), 2.2(6e) and 2.2(6f) UCSM releases
3914 ALUA is required for the native MSDSM and is supported on Windows Server 2008 and later with Ontap 7.3.0 and later.
Windows Servers running 10G FCoE card model Qlogic QLE8242 may face this issue with this Driver and firmware
combination.
The 'vserver fcp ping-initiator show' command fails to ping the Fibre Channel over Ethernet (FCoE) initiator card (QLE8242)
from multiple target adapters.
The 'ping status' output reports as 'not-reachable'. This issue occurs because of the slow response time of the echo request.
This does not have any other impact on other operations when using this card.
Qlogic has already been engaged for the issue and they have a fix planned as part of their upcoming releases for the 10G
8526 FCoE card.
8079 This configuration is supported with 2.2(5a), 2.2(5b), 2.2(5c) & 2.2(5d) UCSM releases.
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 Cisco supported server hardware platforms listed in the Cisco UCS Hardware and Software
Interoperability Matrix, but does not specify the individual server models.
This change is made 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 the
8466 supportability of their configuration with Cisco HCL/Interoperability Matrix. ( Refer: (See next Cell) )
For Windows 2008 versions: Data ONTAP DSM version 3.2R1 does not require any hotfixes. Data ONTAP DSM version 3.3
and 3.3.1 require hotfixes Q953390, and Q958912. Data ONTAP DSM 3.4 requires hotfixes Q979743, Q953390, Q958912.
These hotfixes must be obtained directly from Microsoft Product Support Services at (See next Cell). The Data ONTAP DSM
3026 installation tool checks for appropriate OS patches and prompts users to update or obtain patches, as required.
Microsoft iSNS Server 3.0 is supported. The Data ONTAP option iscsi.isns.rev must be set correctly for the version of iSNS
275 Server used. See KB article 5190 for details at - (See next Cell)
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.
276 Error Recovery Level (ERL) >0 requires software initiator version 2.0 or higher, and Data ONTAP 7.1 or higher.
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.
285 Multipathing options are not available during boot step, but multipathing is supported once the OS is running.
X functionality and IMT
s.
http://www.cisco.com/en/US/netsol/ns1118/index.html
ches/product-details/vdx-
http://www.cisco.com/en/US/netsol/ns1118/index.html
supported.
supported.
supported.
supported.
https://support.microsoft.com/en-in/kb/3033929
supported.
supported.
UCSM releases.
2.1b or 6.2.1(see (See next
ease or later within 5.1(3)
n 6.0(2) releases] or
mware release 6.0(2)N2(1)
supported.
supported.
supported.
supported.
roller.
ations), please consult the
e link:
http://www.cisco.com/c/dam/en/us/td/docs/unified_com
puting/ucs/interoperability/matrix/b_hcl_B_rel2-28.pdf
supported.
supported.
32-bit, x86)
32-bit, x86)
)
4)
P2 (64-bit, x64)
SP2 (64-bit, x64)
P2 for Itanium-based
ported.
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/
Software Interoperability
ed in the interoperability
th configuration and
port issue cannot be clearly
r may require the customer
S is running.