- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- EVA4400 Cabling
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
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
тАО12-03-2010 03:19 PM
тАО12-03-2010 03:19 PM
The current configuration is (cross-cable):
Controller 1
FP1 - Switch 1
FP2 - Switch 2
Controller 2
FP1 - Switch 2
FP2 - Switch 1
The SAN design reference guide indicates that it should be (straight-cable):
Controller 1
FP1 - Switch 1
FP2 - Switch 2
Controller 2
FP1 - Switch 1
FP2 - Switch 2
Everything appears to be working correctly... there are no errors on the EVA or switches, the systems see 4 paths to each LUN and fail-overs work.
Can someone please explain to me what can happen in the current configuration?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2010 04:32 PM
тАО12-03-2010 04:32 PM
Re: EVA4400 Cabling
Assuming there is little SAN activity, would you recommend that I do the following 'on-the-fly'?
1. Assign all luns owned by controller 2 to controller 1
2. Swap Controller 2 FP's on the switches
3. Correct the zoning on the switches
Would you guys recommend this approach? Do I even need to worry about re-assigning the controller (step 1) since the EVA should technically do this for me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-03-2010 10:59 PM
тАО12-03-2010 10:59 PM
Re: EVA4400 Cabling
Make sure that your hosts are installed with Multipathing solution like MPIO for Windows etc. If then you can do it online.
And try to do it in less IO period.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2010 12:25 AM
тАО12-04-2010 12:25 AM
Re: EVA4400 Cabling
And if you want to change it on the fly then make sure all hosts should have connectivity to all FP ports of both controllers. And as above said do it only in less peak hours only.
BK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2010 09:26 AM
тАО12-04-2010 09:26 AM
Re: EVA4400 Cabling
All my hosts have the EVA FF MPIO drivers installed and although not all are connected to both switches for full redundancy, it shouldn't mater because C1 is on both switches. I'll give it a shot during the next maintenance period.
Does anyone know why some devices are cross-cable and others straight-cable? I'd like to know more about why the SAN guide recommends this cabling practice for the EVA and I can't seem to find further information.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-05-2010 07:42 AM
тАО12-05-2010 07:42 AM
Solutioncross cabling was the old method for Active/Passive controllers of first generation EVA's (EVA3K&5K)
After all EVA's became Act/Act. staignt cabling started to be used. All the odd ports of the controllers to one switch and all the even ones to the other switch.
you dont need to do anything on the host side or the EVA side if you have an empty slot just unplug the port1 of the controller2 and plug it on the switch one. by that way only one port of the controller2 will be unavailable for a short period of time and this is transparent to the hosts.
when ctr2/port1 is up then you can move ctr2/port2 to the second switch.
If you want, you can move ctr2/port1 to the port where ctr2/port2 was plugged before the operation.
that is all, and I myself done this a few times on different EVA's without any issue.