- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Difference between Vsan and Zoning
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
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
тАО07-13-2009 11:31 PM
тАО07-13-2009 11:31 PM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-13-2009 11:45 PM
тАО07-13-2009 11:45 PM
Solutiona VSAN is a virtual fabric with it's own set of fabric services etc. You can implement a VSAN for security or redundancy purposes.
Zoning is a grouping of devices which helps you to restrict access to storage devices or servers. Only devices which belongs to the same zone can "see" each other. Zoning can be done by grouping ports, WWPN or WWNN together.
You can combine VSAN and zoning without problems.
Best regards,
Patrick
Patrick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-13-2009 11:49 PM
тАО07-13-2009 11:49 PM
Re: Difference between Vsan and Zoning
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-14-2009 12:35 AM
тАО07-14-2009 12:35 AM
Re: Difference between Vsan and Zoning
take your fabric and lay a virtual layout over it. You partition you fabric into two or more fabrics. Each virtual fabric has it's own set of fabric serves, for example fabric nameservice, RSCN etc. If you have serval customers in you SAN and you want to prevent a host of customer A to read informations from the nameserver about the storage of customer B, a VSAN can be a solution. This is because customer A has it's own "SAN" with his own fabric services. The other virtual fabric don't know anything about the other fabric. So you need a router (inter vsan-routing) to communicate between two fabrics. Another benefit of VSANs is availability. If you have a switch and you build two VSANs, you can connect each server with one path to each virtual fabric. A dual-fabric with one switch. ;) You should do this only with director-class switches because of the hardware availability. ;)
VSAN was developed by Cisco. So this term is only valid for cisco. Brocade call it LSAN. Brocade has also a Meta-SAN. A Meta-SAN are two or more fabrics connected by a Brocade FC-Router.
Hope this helps.
Best regards,
Patrick
Patrick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-14-2009 01:15 AM
тАО07-14-2009 01:15 AM
Re: Difference between Vsan and Zoning
When you create a VSAN an NEW & SEPERATE set of configuration is created within the new VSAN. The new configuration is a replica of services which consists of fabric services like name server, zone server, domain controller, login server, alias server.