Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Follow up On: How to architecturally configure the...
StoreEver Tape Storage
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
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
- Email to a Friend
- Report Inappropriate Content
01-25-2010 02:54 PM
01-25-2010 02:54 PM
Follow up On: How to architecturally configure these components together
This is a follow-up question on the following thread:
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1400618
In this thread, Steven Clementi pointed out that to create "one to one" like zoning woud be best pratice, which is Scenario1 in this case. My question is, why is that? why Scenario1 is recommended, what these potential issues are if we use Scenario2 or 3.
Thanks for your help, specifically, Steven, please let me know if you see this thread.
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1400618
In this thread, Steven Clementi pointed out that to create "one to one" like zoning woud be best pratice, which is Scenario1 in this case. My question is, why is that? why Scenario1 is recommended, what these potential issues are if we use Scenario2 or 3.
Thanks for your help, specifically, Steven, please let me know if you see this thread.
none
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-25-2010 10:56 PM
01-25-2010 10:56 PM
Re: Follow up On: How to architecturally configure these components together
Hi,
If you Google for "single initiator zoning" you'll get lots of answers to your question...
Essentially scenario 1 is best practice because it prevents devices talking to each other when they shouldn't.
It also prevents RSCNs (Registered State Change Notifications) from disrupting things.
There's a good description here:
http://derek858.blogspot.com/2009/10/san-zoning-best-practices-be-prepared.html
Hope this helps,
Regards,
Rob
If you Google for "single initiator zoning" you'll get lots of answers to your question...
Essentially scenario 1 is best practice because it prevents devices talking to each other when they shouldn't.
It also prevents RSCNs (Registered State Change Notifications) from disrupting things.
There's a good description here:
http://derek858.blogspot.com/2009/10/san-zoning-best-practices-be-prepared.html
Hope this helps,
Regards,
Rob
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.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP