- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- Re: Zone Creation Sanity Check
MSA Storage
1753767
Members
5521
Online
108799
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО05-18-2010 10:14 AM
тАО05-18-2010 10:14 AM
I need to get zones implemented and believe I finally understand everything that needs to be done. I'd like to be sure I'm right before moving ahead.
Our environment is comprised of two Storageworks 4/8 SAN switches, an HSV300/EVA4400 with redundant FC modules, and five servers.
As I understand it, on each switch I should create an alias for each of the five servers based on the WWN (or more specifically, the WWPN). Aliases should also be created for each of the two HSV300 connections.
Once the aliases are created I need to create a zone for each server. Each zone will have 3 members - the two HSV300 port aliases and a server alias.
Assuming I have it right, there's one more piece I need to clear up. There are currently mis-configured zones in place from a prior visit by a support rep. Would I be better off to create a new Zone Config with my work, Enable it and reboot the switches or just update the existing Zone Config and remove the mess after a reboot?
Our environment is comprised of two Storageworks 4/8 SAN switches, an HSV300/EVA4400 with redundant FC modules, and five servers.
As I understand it, on each switch I should create an alias for each of the five servers based on the WWN (or more specifically, the WWPN). Aliases should also be created for each of the two HSV300 connections.
Once the aliases are created I need to create a zone for each server. Each zone will have 3 members - the two HSV300 port aliases and a server alias.
Assuming I have it right, there's one more piece I need to clear up. There are currently mis-configured zones in place from a prior visit by a support rep. Would I be better off to create a new Zone Config with my work, Enable it and reboot the switches or just update the existing Zone Config and remove the mess after a reboot?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-18-2010 10:30 AM
тАО05-18-2010 10:30 AM
Re: Zone Creation Sanity Check
It is normally not necessary to reboot an FC switch after a simple thing like a zoning change - sounds like you are using Brocade-based switches, so it is a simple
> cfgEnable "configname"
For the EVA-x400 series it is necessary to implement "single-initiator/single-target zones". That means: create separate zones for the adapter and each EVA host port.
> cfgEnable "configname"
For the EVA-x400 series it is necessary to implement "single-initiator/single-target zones". That means: create separate zones for the adapter and each EVA host port.
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-18-2010 10:43 AM
тАО05-18-2010 10:43 AM
Re: Zone Creation Sanity Check
Thank you for the quick reply.
Yes, the switches are Brocade-based.
To be clear, each zone would then have just two members and each server would be a member of two zones; e.g Zone1's members would be ServerA & EVA_Mod1_Port1 and Zone2's members would be ServerA & EVA_Mod2_Port1. Correct?
Yes, the switches are Brocade-based.
To be clear, each zone would then have just two members and each server would be a member of two zones; e.g Zone1's members would be ServerA & EVA_Mod1_Port1 and Zone2's members would be ServerA & EVA_Mod2_Port1. Correct?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-18-2010 10:46 AM
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP