HPE GreenLake Administration
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- New brocode switches to an existing SAN EVA4000
HPE EVA Storage
1826499
Members
1615
Online
109692
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
Forums
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
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
08-20-2007 09:08 AM
08-20-2007 09:08 AM
Hi
A customer have bought two new brocades SAN switches 4/16 .
The EVA is a EVA4000 with controllers HSV200 not the HSV200-A.
So this controllers run up 2 GB.
Hi bought the 4/16 brocade switch because he was thinking that with the new san swithes he will get 4 GB in the HSV controllers ports too.
I said him that is not a good idea because he will not get more speed in the HSV controller ports , also I said that he can cascade the new san switches to the san switches that are working at this time.
Also I said that some OS are attached to the domain ID of the san switches and is possible that if we change the domain then the presented virtual disks will be see as new virtual disks for the OS.
Other Idea that the custumer has or had is:
Attach each port of the controller HSV200 to one port of each san switch (4 san switch)
I think that is not a good idea.
As always comments are welcomes
W.S
A customer have bought two new brocades SAN switches 4/16 .
The EVA is a EVA4000 with controllers HSV200 not the HSV200-A.
So this controllers run up 2 GB.
Hi bought the 4/16 brocade switch because he was thinking that with the new san swithes he will get 4 GB in the HSV controllers ports too.
I said him that is not a good idea because he will not get more speed in the HSV controller ports , also I said that he can cascade the new san switches to the san switches that are working at this time.
Also I said that some OS are attached to the domain ID of the san switches and is possible that if we change the domain then the presented virtual disks will be see as new virtual disks for the OS.
Other Idea that the custumer has or had is:
Attach each port of the controller HSV200 to one port of each san switch (4 san switch)
I think that is not a good idea.
As always comments are welcomes
W.S
rperez
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2007 03:50 PM
08-20-2007 03:50 PM
Solution
William,
It's not good idea to connect each port to 4 different SAN Switches, first you will fall into a non-supported environment and you may also face problems during host access (due to different HOPs for different EVA ports. Also, this will become major issue during any single path failure (host/fiber/san-switch failure).
You can draw a picture yourself with proposed configuration and then consider any of the switch failure and look at the host which is accessing the EVA via longest HOP, it will not only look odd but will give you performance issue as well as oversubscription on ISLs too.
Keep it as it is, and add the new switches in individual fabric then attach new hosts there. If you need better connectivity (high IOs & Bandwidth) between switches then add more ISLs or even go for Trunking licenses.
* Think long term growth.
It's not good idea to connect each port to 4 different SAN Switches, first you will fall into a non-supported environment and you may also face problems during host access (due to different HOPs for different EVA ports. Also, this will become major issue during any single path failure (host/fiber/san-switch failure).
You can draw a picture yourself with proposed configuration and then consider any of the switch failure and look at the host which is accessing the EVA via longest HOP, it will not only look odd but will give you performance issue as well as oversubscription on ISLs too.
Keep it as it is, and add the new switches in individual fabric then attach new hosts there. If you need better connectivity (high IOs & Bandwidth) between switches then add more ISLs or even go for Trunking licenses.
* Think long term growth.
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP