AFF, NVMe, EF-Series, and SolidFire Discussions

shared cluster ports e0a/e0b

Hello everyone,
someone know how I can configure intercluster LIFs on shared data ports, on aff220 in metrocluster configuration? On aff220 I have only shared ports e0a and e0b for cluster and intercluster. On technical documentation this use case isn't very clear for me.

Re: shared cluster ports e0a/e0b


hi @jlf79 

unfortunately you cannot place Intercluster LIFs on ports e0a/e0b in this configuration if you already use them for Cluster network.
LIFs for replication between the two clusters need to be on a different port connected to the data network shared by the two clusters.


"Cluster peering can be done on dedicated ports or on data ports. Using dedicated ports provides higher throughput for the cluster peering traffic."

Re: shared cluster ports e0a/e0b


thanks for your answer.

On ontap9 documentation at I've found:


You can configure intercluster LIFs on ports shared with the data network. Doing so reduces the number of ports you need for intercluster networking.




on many documents as: (page 12) 


For the NetApp AFF A220 and FAS2750, software iWARP is used. These platforms have a fixed number
of network ports. To further enhance the use of network ports for front-end, host-side data access, the
two onboard 10GbE ports, e0a and e0b, that are typically reserved as cluster interfaces are combined.
This feature allows cluster traffic and MetroCluster IP traffic to share the same ports, and the remaining
four network ports can be used for host-side data access.


On this documents is highlighted which ports can be used for intercluster and cluster on aff220:


I've misunderstood these documents?


Thanks again!







Re: shared cluster ports e0a/e0b


For the AFF A200 in a MetroCluster IP configuration, the e0a/e0b ports are dedicated to "Shared cluster / MetroCluster IP interconnect".  Inter-cluster LIFs (LIFs used for SnapMirror traffic between clusters) must be on other ports on the AFF A200. 

Re: shared cluster ports e0a/e0b


thanks andris. 

I've just create the two ha clusters. Now I need to interconnect them. If I haven't misunderstood I need to assign 2 IPs to each node. 

Which ports can I use for this ?

On aff220 I've e0a/e0b, e0c/e0d and e0e/e0f and e0a/e0b used for ha-cluster at the moment.


Re: shared cluster ports e0a/e0b


I'm not really sure what you're asking about at this point.  Are you referring to the network connectivity between the two DR sites of your MetroCluster IP configuration or are you referring to peering with another cluster?

I would recommend you create a technical case for formal support.

Re: shared cluster ports e0a/e0b


For the Cluster Peering beetween the two HA-Pairs, you have to create InterCluster LIFs, This LIFs can be reside on e0c,e0d,e0e,e0f or on a LACP or on a VLAN whatever.  And you can also use the named Ports for Front Traffic (Data).

That is the meaning of Shared Data Port....

Re: shared cluster ports e0a/e0b


I'm using e0a/e0b for local cluster and Metrocluster. I had to create the DR group for the peering cluster first using e0e and e0f (my data ports). So I've created a metrocluster.


Now I've another doubt about the use of data ports for iscsi, nfs, cifs.

I would use always the same ports (e0e and e0f) but isn't clear for me how I can separate the traffic (iscsi_a, iscsi_b, nfs, cifs) because the physical interface was already used. I can create a svm but I can't use a vlan for it; also the GUi (9.7) allow me choose only the IP but I don't have find where set the vlan.


Should I use different ipspaces ?





Re: shared cluster ports e0a/e0b


On physical Ports you can create Link Aggreation Groups (LACP, etc) on this or without this you can create vlans. Also for each Traffice Group you have to build a Broadcast Domain.


For easy way switchback to the Classic Version..


Maybe you go to the learningcenter to view some Basic Videos about how Data Ontap Works.



Earn Rewards for Your Review!
GPI Review Banner
All Community Forums