Re: FS5022 and external Storwize v7000
« Reply #1 on: August 05, 2014, 01:16:57 PM »
Thank you for your question. Below I will explain best practices for SAN zoning. Also the v7000 is an active/active SAN storage system so at ALL TIMES I/O will be going through both fabrics A and B. So if these are VMware hosts you want to set the LUN Access Policy to Round Robin.SAN Overview
SAN stands for Storage Area Network and it defines the relationship between storage systems and hosts for mapping of additional storage capacity to servers with limited internal capacity. A Fabric is a collection of ports from a single or group of switches to form a virtual storage area network or virtual fabric. Each Fabric has static FC ports assigned to it or redundant switches. The purpose of multiple SAN fabrics is for redundancy. So, if you have two (2) fabrics (Fabric A and Fabric B) and you lose Fabric A then assuming zoning is done per the best practices below then Fabric B should pick up the traffic and no hosts should go offline. Zoning
Zoning is a fabric-based service in SANs that groups hosts and storage devices that need to communicate. In zoning, only members in the same zone can communicate to each other.
In a typical environment, SAN zones should follow the Single Initiator Zoning (SIZ) practice. With this setup, zones contain a single initiator (host HBAs) and one to many targets (storage ports). Also, separate HBAs and zones should be used for disk and tape traffic. All aliases should be created with WWPN, unless where required.
All aliases and zones should be descriptive enough to determine the host and storage devices. Some zones use aliases as well as WWPNs. It is a best practice to create aliases for WWPNs and use only aliases to zone, the reason for this is easier manageability. Alias based zoning is also important because it allows you to not be tied to a specific port so, for example, if the port were to fail you could simply connect to another port and no additional zoning changes need to be made. All aliases, zones, and zonesets should also be named similarly, just with a different fabric designation.
Examples of aliases and zones in different fabrics:
? Alias - SERVERNAME_P1 for Fabric A.
? Alias - SERVERNAME_P2 for Fabric B.
? Zone - SERVERNAME_STORAGE_A for Fabric A.
? Zone - SERVERNAME_STORAGE_B for Fabric B.
Let me know if this helps!!