Hi!
I wanna ask how you setup zoning in a VMware environment with SANs in general and with an EMC Clariion. In the past i found it interesting that each consultant or manufacturer has his own idea for a proper zoning. So it would be cool to know which configuration are out there.
Lets take as an example one EMC Clarion 3-10, two SAN switches and two servers with dual HBAs.
Recommendations i heard so far are (for different SAN of course):
1. No zoning because you have two fabrics separated through the switches.
2. Zoning to separate the HBAs but not the SP. So a zone on switch one would be HBA1 of Server 1 and SP1a and SP2a into one zone and on switch two it would be HBA2 of Server 1 and SP1b and SP2b. (4 zones in sum)
3. Zoning from HBA directly to SP e.g on switch 1 HBA1 of Server 1 to SP1a, HBA 1 of S1 to SP2a, and so on. (8 zones in sum)
Maybe you have version 4 and 5 lets see.
Mike
EMC has a pdf called Open Systems Configuration Guide (OSCG) which lists various zoning scenarios.
Bottom line is single initiator/single target per zone.
There is no problem in most cases implementing single initiator/multi target per zone.
One layered application that requires single/single is SANcopy. If you implement SANcopy in your environment you will want to have single/single throughout the fabrics. (long story of why)
To be clear:
Initiator = HBA
Target = Storage Port
You do not want to have more than 1 initiator in a zone. Isolating initiators in zones protects them from being affected by RSCN, LIP, resets... from other initiators.
Steve
You should always use zones with 2 initiators (EMC highly recommended).
So each path between server and storage array get's it's own zone:
Server with 2 hba's in 2 fabrics needs 2 zones if your array is attached with one hba to each fabric.
Server with 2 hba's in 2 fabrics should have 4 zones if your array is attached with 2 hba's (one from each sp) per fabric.
The reason for zones with as less initiators as possible (= 2 ) is the time needed within each zone for resume communications after a failure or during initial startup. Each initiator has to talk to the others.
Regards Spex
EMC has a pdf called Open Systems Configuration Guide (OSCG) which lists various zoning scenarios.
Bottom line is single initiator/single target per zone.
There is no problem in most cases implementing single initiator/multi target per zone.
One layered application that requires single/single is SANcopy. If you implement SANcopy in your environment you will want to have single/single throughout the fabrics. (long story of why)
To be clear:
Initiator = HBA
Target = Storage Port
You do not want to have more than 1 initiator in a zone. Isolating initiators in zones protects them from being affected by RSCN, LIP, resets... from other initiators.
Steve
Thanks Steve /Spex, now I understand the EMC recommendation.
Mike
Message was edited by:
MikeAT