Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
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.
Solaris Fibre Channel client applications may go offline in MetroCluster configurations with Tie Breaker server, during
unplanned switchover events, and during Automatic Switchover events. The application disruption occurs because the
fcp_offline_delay timeout is set to default 20s.
For MetroCluster configurations, customers are advised to modify the fcp_offline_delay timeout to a value between 60 to 120
depending on the customer environment. Please refer to following KB article to modify FCP Offline Delay timeout value and
further info: (See next Cell)
8086 For Veritas filesystem with Solaris and MetroCluster support, customers are advised to file PVR.
For ONTAP 8.0 and above, HU 5.1 is recommended in order to obtain full functionality. For more information, please see the
3534 Solaris Host Utilities 5.1 Installation and Setup Guide.
Info
The minimum supported Solaris operating system level for the M3000, M4000, M5000, M80000, and M9000 differs based on
the processor type in the server. Please consult the table below for the specific version for your server.
Support for SPARC Server platforms applies to all standard rack servers. Specific platform is only required for blade system,
such as the Sun Blade 6000 or Fujitsu PRIMERGY BX line. Support for a given combination of platform, OS, and HBA
8582 components also requires support from the server vendor.
134 Veritas Cluster Server (VCS) 5.0 MP3, 5.0 MP1, 4.1 MP1, 4.1 MP2, 4.0 MP2, and 5.1 qualified with up to six nodes.
136 NetApp cfmode (controller failover): SSI (Single System Image); S (Standby); P (Partner); DF (Dual Fabric); M (Mixed)
QLogic QLA2460 4Gb 1-port PCI-X (Sun model SG-XPCI1FC-QF4); QLA2462 4Gb 2-port (Sun SG-XPCI2FC-QF4); QLE2460
4Gb 1-port PCI-Express = NetApp Part Number X1088A-R6 (Sun SG-XPCIE1FC-QF4); QLE2462 4Gb 2-port PCI-Express =
NetApp Part Number X1089A-R6 (Sun SG-XPCIE2FC-QF4); QLA2340 2Gb 1-port PCI-X (Sun SG-XPCI1FC-QL2); QLA2342
140 2Gb 2-port PCI-X (SG-XPCI2FC-QF2-Z)
5292 Express Module HBAs are supported with the Oracle Sun Fire X4800 server model.
5008 Sun Cluster 3.2u2 requires the following minimum patch level: 126107-35 for X86 and 126106-35 for SPARC.
Solaris virtualization options include Solaris Logical Domains (also called LDOMs or Oracle VM Server for SPARC), Solaris
Dynamic Domains, Solaris Zones and Solaris Containers. In some case multiple options can be used together such as a
Solaris Container within a particular Solaris Logical Domain.
NetApp generally supports the use of these virtualization technologies where the overall configuration is supported by Oracle
and any partition with direct access to LUNs can be found on the IMT in a supported configuration. Partitions which use only
8696 virtualized resources such as a vdsk, do not need specific qualification as they do not have direct access too NetApp LUNs.
The use of Solaris 10 10/09 (Update8) and Oracle Solaris 10 9/10 (Update 9) with T4 servers requires the installation of the
5753 Solaris 10 8/11 (Update10) Patch Bundle. This is true for both guest and control domains.
NetApp Fibre Channel Solaris Host Utilities (Attach Kits, part number SW-FAK-SOL) are available for users to download from
the NetApp on the Web (NOW) site. The Solaris Host Utilities consist of software and documentation to integrate and support
NetApp Fibre Channel storage systems in a Solaris host environment. The Host Utilities do not include HBAs or HBA
122 drivers/firmware.
Special considerations apply when LUNs are used as virtual disk devices within an LDOM. The reason is the source of the
LUN is masked by virtualization and the LDOM will not properly detect the block sizes.
Solution:The LDOM operating system must be patched for Oracle Bug 15824910 and a vdc.conf file must be created that sets
the block size of the virtual disk to 4096. See Oracle Doc 2157669.1 for further information.
To verify : After creating a zpool, run zdb -C against the zpool and ensure the value of ashift is 12. If it is not 12,ensure the
correct patch was installed and recheck the contents of vdc.conf. Do not proceed until ashift shows a value of 12.
Patches are available for bug 15824910 on various versions of Solaris. Contact Oracle if assistance is required in determining
8506 the best kernel patch.
124 UltraSPARC IV+ servers = Sun Fire V490, V890, E2900, E4900, E6900, V480, V1280, E12K, E20K, E25K
UltraSPARC servers = Sun Fire V240, V210, V440. Note: The Sun Fire V210 has a single HBA slot and is not capable of full
125 HA configurations.
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 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.
UltraSPARC III servers = Sun Fire 280R, V120, V880, V880z, 3800, 4800, 4810, 6800, 12000, 25000; Ultra 30, 60, 80;
126 Enterprise 220R, 420R, 250, 450, 3500, 4500, 5500, 6500; Ultra Enterprise 3x00, 4x00, 5x00, 6x00
The use of Solaris 10 10/09 (Update8) with T3 servers requires the installation of the Oracle Solaris 10 9/10 (Update 9) Patch
5278 Bundle. This is true for both guest and control domains.
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.
eaker server, during
n occurs because the
https://kb.netapp.com/app/answers/answer_view/a_id/
1001373
th up to six nodes.
al Fabric); M (Mixed)
G-XPCI2FC-QF4); QLE2460
2 4Gb 2-port PCI-Express =
G-XPCI1FC-QL2); QLA2342
for SPARC.
ce is required in determining
0K, E25K
th configuration and
port issue cannot be clearly
r may require the customer
ecture listed in the