- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: Zoning Best Practice for Multiple Arrays - Meg...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2009 09:10 AM
тАО10-19-2009 09:10 AM
URANUS_DISK:
EVA1_PORTS, EVA2_PORTS, EVA3_PORTS, XP1_FRONT, XP2_FRONT, XP3_FRONT, XP4_FRONT, URANUS_HBA_1, URANUS_HBA_3, URANUS_HBA_5, URANUS_HBA_7
The Array Ports are aliases of course to the appropriate Front ENd WWIDs.
Would it not be Best Practice to have a Zone for each array? The Storage Arrays do not have a reason to communicate with each other (or even if they did, it should be a separate zone). Probably something like:
URANUS_EVA1_DISK:
EVA1_PORTS, URANUS_HBA_1, URANUS_HBA_3, URANUS_HBA_5, URANUS_HBA_7
URANUS_EVA2_DISK:
EVA2_PORTS, URANUS_HBA_1, URANUS_HBA_3, URANUS_HBA_5, URANUS_HBA_7
URANUS_XP1_DISK_ZONE:
XP1_FRONT, URANUS_HBA_1, URANUS_HBA_3, URANUS_HBA_5, URANUS_HBA_7
... so forth..
TIA.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2009 09:18 AM
тАО10-19-2009 09:18 AM
SolutionYou can find best practices in the SAN Design Reference Guide here:
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00403562/c00403562.pdf
Cheers,
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2009 10:44 AM
тАО10-19-2009 10:44 AM
Re: Zoning Best Practice for Multiple Arrays - MegaZone or Individual Zones?
1. Single Intiator zoning - Keep only one HBA Port in one zone, be it any array
2. On each Fabric "zone" in all the EVA Ports(on each fabric) in one zone
following rule 1 and 2 you'll have something like this for EVA
URANUS_EVA1_DISK_HBA_1:
EVA1_PORT_8, EVA1_PORT_C, EVA1_PORT_A, EVA1_PORT_E, URANUS_HBA_1,
3. For XP... I will keep only one XP Port in one zone. If my Max. LUNs per XP port expires, I will use another XP CHIP Port and zone it in with the single HBA Port. Or may be you want additional performance then its a different case
this is how it shld look like for XP
URANUS_XP1_DISK_ZONE:
XP1_FRONT_1A, URANUS_HBA_1
I hope this helps...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2009 10:47 AM
тАО10-19-2009 10:47 AM
Re: Zoning Best Practice for Multiple Arrays - MegaZone or Individual Zones?
- HOST1_1,EVA1_C1P1,EVA1_C2P1
- HOST2_1,EVA1_C1P1,EVA1_C2P1
- HOST1_1,EVA2_C1P1,EVA2_C2P1
- HOST2_1,EVA2_C1P1,EVA2_C2P1
This isolates initiators from each other and it prevents 'leaks' if you are using Continuous Access. For CA, I create separate array/array replication zones, because somebody might want/need to disable that function for some reason.
There is a customer advisory for the wonderful EVA-4400 which requires an even finer granularity at least for the management server:
- HOST1_1,EVA1_C1P1
- HOST1_1,EVA1_C2P1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-20-2009 05:35 AM
тАО10-20-2009 05:35 AM
Re: Zoning Best Practice for Multiple Arrays - MegaZone or Individual Zones?
do you have the link for customer advisory on EVA4400 finer granularity with zoning rules ?
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-20-2009 10:56 AM
тАО10-20-2009 10:56 AM
Re: Zoning Best Practice for Multiple Arrays - MegaZone or Individual Zones?
I think single initiator to single target is the preferreed zoning method for most vendors, I know it is reccomended for HDS and EMC at least.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-21-2009 01:03 AM
тАО10-21-2009 01:03 AM
Re: Zoning Best Practice for Multiple Arrays - MegaZone or Individual Zones?
i agree with you, but the following rules of zoning must be applied in a CA configuration :
The zones for a Command View EVA management server must include both the source and destination arrays to enable the creation of DR groups and proper management of the arrays. The management server must also have at least one host port from each controller of the arrays zoned with the Command View EVA management server
HBA. Additional array pairs are zoned in a similar manner for each site. If an additional array is added to either site and it will participate in a DR relationship, then two additional zones should be created for each of the Command View EVA management server HBA ports and the additional array├в s host ports.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-21-2009 04:59 AM
тАО10-21-2009 04:59 AM
Re: Zoning Best Practice for Multiple Arrays - MegaZone or Individual Zones?
Inter-EVA communications should only have EVAs zoned within - for CA primarily.
Dito with XP's and EVA - for continous XP or External Storage XP.
Single Iniator Single Target as mandated.
Single Initiator, Multiple Targets as ercommended/suggested.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-21-2009 06:04 AM
тАО10-21-2009 06:04 AM