- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Follow up On: How to architecturally configure the...
StoreEver Tape Storage
1752614
Members
4750
Online
108788
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
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
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
- 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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP