- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- EVA 8100 cabling question
Disk Enclosures
1748177
Members
4230
Online
108758
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
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
тАО10-18-2010 06:31 PM
тАО10-18-2010 06:31 PM
EVA 8100 cabling question
Scenario two MDS switches, ISL'd and multiple vsans each can see. Servers with single hba's. Storage is eva8100. If an MDS switch goes down, how can the single pathed systems stay up with out reconfiguring zoning and vsans? Can eva controller pairs be split between MDS switches and vsans as follows, ports 1 & 2 to one mds switch, each on different vsans then same for ports 3 & 4. Is this possible and if not, why?
MDS1-------ISL---------MDS2
vsanA --1 8100A 3--vsanB
vsanA --2 8100A 4--vsanB
This doesn't work with out causing an outage, requiring reconfiguration:
MDS1-------ISL---------MDS2
vsanA --1 8100A 2--vsanB
vsanA --3 8100A 4--vsanB
MDS1-------ISL---------MDS2
vsanA --1 8100A 3--vsanB
vsanA --2 8100A 4--vsanB
This doesn't work with out causing an outage, requiring reconfiguration:
MDS1-------ISL---------MDS2
vsanA --1 8100A 2--vsanB
vsanA --3 8100A 4--vsanB
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2010 11:52 AM
тАО10-19-2010 11:52 AM
Re: EVA 8100 cabling question
I wrote this wrong, I meant can I do this:
MDS1-------ISL---------MDS2
vsanA --1 8100A 3--vsanA
vsanB --2 8100A 4--vsanB
I want to split the pairs between MDS switches but keep vsans and zoneing the same.
MDS1-------ISL---------MDS2
vsanA --1 8100A 3--vsanA
vsanB --2 8100A 4--vsanB
I want to split the pairs between MDS switches but keep vsans and zoneing the same.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2010 01:25 PM
тАО10-19-2010 01:25 PM
Re: EVA 8100 cabling question
You cannot guarantee to stay up a single HBA server what ever you do. If the switch that HBA connected goes down then you are down. Single HBA itself is a Single Point of Failure(SPoF) on the other hand.
EVA cabling should be done in the following rule:
Odd numbered ports of both controllers to one switch and Even numbered ports of both controllers to the other switch. Usually we dont connect the switches to each other. It only duplicates the number of paths but brings no redundancy or performance.
You need second HBA's to your hosts to have actually no SPoF.
EVA cabling should be done in the following rule:
Odd numbered ports of both controllers to one switch and Even numbered ports of both controllers to the other switch. Usually we dont connect the switches to each other. It only duplicates the number of paths but brings no redundancy or performance.
You need second HBA's to your hosts to have actually no SPoF.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2010 03:45 PM
тАО10-19-2010 03:45 PM
Re: EVA 8100 cabling question
I have the switches ISL'd so I can bring one down for an upgrade with out downtime. I have had failures also, and the configuration most certainly keep us up. The vsans, fabric is seen from both, they are redundant. I can litterally turn one off and run with one exception. Right now the odd ports are connected to one MDS switch on the same vsan. The server HBA is zoned for them. When that MDS when down, then that server couldn't see storage. If I loose port 1 on a controller, then 3 is still up. I got them impression they were a failover pair so if they (1,3) are connected to the same switch that defeats the purpose.
That's what prompted my question. If they are a pair, evens and odds can they be physically connected to two different switches? Just like if the server had dual hba's. Each pair would be in the same vsan, zone etc.
That's what prompted my question. If they are a pair, evens and odds can they be physically connected to two different switches? Just like if the server had dual hba's. Each pair would be in the same vsan, zone etc.
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