![brocade san switch netapp array l-port to f-port brocade san switch netapp array l-port to f-port](https://niktips.files.wordpress.com/2015/03/vnx_lport1.jpg)
![brocade san switch netapp array l-port to f-port brocade san switch netapp array l-port to f-port](https://docplayer.net/docs-images/42/19926911/images/page_12.jpg)
- #Brocade san switch netapp array l port to f port how to#
- #Brocade san switch netapp array l port to f port windows#
Then go to MPIO Control Panel and add support for iSCSI devices.
#Brocade san switch netapp array l port to f port windows#
On the Windows Server start by installing Multipath I/O feature. On IP Settings tab you will find iSCSI Control Port IP address settings. From there select your fault domain and click Edit Fault Domain. To create and assign Fault Domains go to Storage Management > System > Setup > Configure Local Ports > Edit Fault Domains. IP settings for iSCSI ports can be configured at Storage Management > System > Setup > Configure iSCSI IO Cards. This translates into one Fault Domain and one Control Port on the Compellent. In my case I had two stacked switches, so I chose to use one iSCSI subnet. In other words, instead of using IPs configured on the Compellent iSCSI ports, you’ll need to use Control Port IP for iSCSI target discovery. When server targets iSCSI port IP address, it automatically discovers all ports in the fault domain. Control Port has its own IP address and one Control Port is configured per Fault Domain. Which means that you will have one fault domain in the one subnet scenario and two fault domains in the two subnets scenario.įor iSCSI target ports discovery from the hosts, you need to configure a Control Port on the Compellent. Worth mentioning that Compellent uses a concept of Fault Domains to group front-end ports that are connected to the same Ethernet network.
![brocade san switch netapp array l-port to f-port brocade san switch netapp array l-port to f-port](https://slidetodoc.com/presentation_image/4b6db5be92d62d3a0c3d0170ad8df6a8/image-6.jpg)
I could not find a specific recommendation from Dell on whether it should be one or two subnets, so I assume that both scenarios are supported. And it all typically boils down to two most common scenarios: two stacked switches and one subnet or two standalone switches and two subnets. And two questions you need to ask yourself are, what your switch topology is going to look like and how you are going to configure your subnets.
![brocade san switch netapp array l-port to f-port brocade san switch netapp array l-port to f-port](https://i.ytimg.com/vi/mkjWPYQspZ0/maxresdefault.jpg)
I used Windows Server 2012 R2, but the process is similar for other Windows Server versions.Īll iSCSI design considerations revolve around networking configuration. In this post I want to talk specifically about the Windows scenario, such as when you want to use it for Hyper-V. And there seem to be some confusion on what the best practices for iSCSI are. I hope I can shed some light on it by sharing my experience.
#Brocade san switch netapp array l port to f port how to#
I haven’t seen too many blog posts on how to configure Compellent for iSCSI. To confirm that the issue is fixed send an AutoSupport message either from OnCommand System Manager or right from the console and make sure that status shows “sent-successfull”. Then make sure to enable Externally Secured authentication type on the Authentication tab. To set this up on a Exchange server go to Exchange Management Console > Server Configuration > Hub Transport, select a Receive Connector (or create it if you don’t have one for whitelisting already), go to properties and add NetApp IPs on the network tab. There are two things you need to make sure are configured: NetApp controllers management IPs are whitelisted on the mail server and authentication is disabled. The most common cause of the issue is blocked relay. If AutoSupport is configured to use SMTP as in this case, then the first place to check is obviously the mail server. When you list the AutoSupport history on the target system you see something similar to this: You need to fetch some information for the customer from the My AutoSupport web-site and can’t because the last AutoSupport message is from half a year ago.