Effective December 3, NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources.
For accounts that did not pre-register (prior to Dec 3), access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity.
To learn more, read the FAQ and watch the video.
Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.

ONTAP Discussions

setup Ontap with two Separate vlans for ISCSI

miller

Hello,

 

As far as I know NetApp\Vmware best practice with iscsi protocol is setup Ontap with two Separate vlans for ISCSI

Iscsi A

Iscsi B

 

Do you have a document that states that?

 

Thank you.

1 ACCEPTED SOLUTION

AllenJohnson

It's Best Practice to have seperate Fabrics for Block storage. 
just like with FC traffic, it's not recommended to run iSCSI traffic on a single switch. 
One way to accomplish this, is to physically seperate Fabric A and Fabric B ( FC or iSCSI) on seperate switches. 
Another Best Practice is to use VLANs to seperate iSCSI traffic from other types of data traffic ( NFS / CIFs)

 

 

View solution in original post

5 REPLIES 5

SpindleNinja

https://library.netapp.com/ecm/ecm_download_file/ECMLP2495115

 

It is recommended that all SVMs in ISCSI configurations have a minimum of two LIF's per node in separate Ethernet networks for redundancy and MPIO across multiple paths.

 

doesn't necessarily have to be vlans,  just two separate networks (switches) 

miller

thank you for your reply.

there is no documentaion for using 2 vlans at all?

AllenJohnson

It's Best Practice to have seperate Fabrics for Block storage. 
just like with FC traffic, it's not recommended to run iSCSI traffic on a single switch. 
One way to accomplish this, is to physically seperate Fabric A and Fabric B ( FC or iSCSI) on seperate switches. 
Another Best Practice is to use VLANs to seperate iSCSI traffic from other types of data traffic ( NFS / CIFs)

 

 

View solution in original post

TMAC_CTG

Under VMware, one technique is to do this (using VLANs 133/134 for iSCSI):

1. Create a standard vSwtich (vSwitch 2) with both iSCSI vmnics (lets call them vmnic4 and vmnic5)

2. Create a port-group called iSCSI-A-133 in vSwitch 2 and insert a vmk

3. Create a port-group called iSCSI-B-134 in vSwitch 2 and insert a vmk

4. Configure the iSCSI-A-133 vmk teaming-failover to over-ride and make sure that vmnic4 is active and vmnic5 is unused.

5. Configure the iSCSI-B-133 vmk teaming-failover to over-ride and make sure that vmnic5 is active and vmnic4 is unused.

6. Go to the iSCSI software configuration and enable port-binding for those two vmks.

This allows for two interfaces inside a vswitch which allows vmware to think it has failover and you override that anyway with port-binding.

 

 

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public