FAS8020 storage initiator connection rules in a MetroCluster solution

KB at your finger tips

This is one stop global knowledge base where you can learn about all the products, solutions and support features.

Products-NetApp

FAS8020 storage initiator connection rules in a MetroCluster solution

Applies to

MetroCluster
ONTAP 9
FAS8020 only

Issue

In a MetroCluster in clustered Data ONTAP, each controller must have two HBA initiator connections to each of the two fabrics to connect storage. Along with that, each controller requires four HBA initiator ports.

When using FAS8020 controllers, there might be a need to only use two, instead of four, HBA initiator ports to connect storage to use the single free slot for host connectivity or tape backup. This applies to the FAS8020 only and no other platform. This type configuration can also be called as a 'single initiator per fabric' configuration.

Note : If a MetroCluster is configured using FAS8020 controllers and the hardware configuration is changed, these rules must be evaluated in order to add / remote paths so the configuration remains supported.

FC-SAS Bridge Health Monitoring collection is older than 24 hours

Applies to

ATTO FibreBridge
MetroCluster
ONTAP 9
Out of band management

Description

FC-SAS Bridge Health Monitoring collection is older than 24 hours. The data collection for the FC-SAS Bridge is not current, and this will impact the ability to troubleshoot issues and indicate configuration issues.

Read article

Are FAS3240/V3240 and FAS3270/V3270 supported in MetroCluster running DATA Ontap 8.3 or later?

Applies to

FAS3240/V3240
FAS3270/V3270
ONTAP 8.3
ONTAP 9

Answer

FAS3240/V3240 and FAS3270/V3270 are not supported in MetroCluster running Data ONTAP 8.3 or later.

See the Interoperability Matrix for a list of supported configurations.

Additional Information

Read article

How to configure the Data ONTAP subnet feature in a MetroCluster

Applies to

MetroCluster
ONTAP 9
subnet feature

Description

This article describes the procedure to configure the Data ONTAP subnet feature in a MetroCluster.

Read article

How to identify a mismatch of shortwave and longrange SFPs in a FC-VI card?

Applies to

MetroCluster FC
FCVI
long wave and short wave intermix

Description

SFPs need to be the same for both ports on the FCVI card. The below procedure explains how to identify a mismatch.
In order to decide on the correct type of SFP you need to verify the infrastructure (cables / patch pannels) used in the datacenter.

Read article

Dynamic capacity expansion over asynchronous remote volume mirroring results in failed drives and failed volumes

Applies to

E-Series Controller Firmware 8.xx
SANtricity

E5500 running prior to 08.25.14.00 firmware.
• E5600 running prior to 08.25.14.00, or prior to 08.30.40.00 firmware, or 08.40.00.00 firmware.
• E5700 running 08.40.00.00 firmware.

Issue

When performing one of the following reconfigure operations on a volume group containing ARVM mirrors with PI enabled and a controller that supports multicore, the reconfigure operation can result in PI Reftag errors that lead to failed drives, failed volumes and failed reconfigure operations. Due to the volume failure during reconfiguration, the only way to recover is to delete the volume group. The data cannot be recovered by recreating the configuration.

Affected Reconfigure Operations:

Dynamic Capacity Expansion (DCE)
Dynamic Volume Expansion (DVE)
Dynamic Segment Sizing (DSS)
Dynamic RAID Migration (DRM)
Defrag

Check Active IQ if this impacts your systems

The following conditions must exist:

The system is running one of the platforms and affected releases listed in the Environment section (Multiple Core platform's only)
Volume Groups contain ARVM mirrors with PI enabled
A DCE, DVE, DSS, DRM, or Defrag reconfigure operation occurs on a Volume Group with PI enabled and ARVM mirrors
Traditional Volumes (DDP is not affected)

Read article

Welcome to Knowledge Base!

KB at your finger tips

Products-NetApp