- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: SAN rules re: Storage & HBA ports & Quads
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
тАО04-22-2010 05:49 AM
тАО04-22-2010 05:49 AM
SAN rules re: Storage & HBA ports & Quads
Given the following environment, what would be the best-practice way of cabling up a fabric?
HP c-Class Blade with 2 x 20-port VC-FC modules
2 x Storageworks 8/40 SAN switches (24 ports enabled)
2 x MSA2000fc (dual controllers - possibly expanding to 4 x MSA later)
4 x DL380s (dual port FC - possibly expanding to 8 x DLs later)
Specifically I'm looking to ensure I'm following sensible guidelines as to which devices get connected to which quads on the switches.
I've seen some references saying to avoid configuring hosts & targets on the same quad, and others (although specifically referring to EVA connections to be fair) saying to avoid EVA connections to the same quad.
So, should I try to spread out the load (across the 6 available quads) or perhaps designate storage quads & host quads?
Target O/S's are windows & VMware boxes, no other O/S planned.
Any suggestions appreciated.
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-23-2010 10:30 AM
тАО04-23-2010 10:30 AM
Re: SAN rules re: Storage & HBA ports & Quads
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2010 06:23 AM
тАО04-26-2010 06:23 AM
Re: SAN rules re: Storage & HBA ports & Quads
As it happens I'm planning on connecting all for of each VC-FC module (20-port model) so that it's "set & forget" configured rather than someone having to come back later to change things but I've always been led to believe that each VC-FC uplink is independant of the others (and, in fact, serves distinct server bays in the enclosure).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2010 06:29 AM
тАО04-26-2010 06:29 AM
Re: SAN rules re: Storage & HBA ports & Quads
to the VC-FC uplink ports are handled dynamically, and the load is balanced across all available ports in the group.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2010 06:41 AM
тАО04-26-2010 06:41 AM
Re: SAN rules re: Storage & HBA ports & Quads
Although it's been a while since I installed my last cClass, I do recall info at the time (with the original 4Gb VC-FC) relating to physical port-mappings. A quick google lead me to a site I remember finding very useful info at http://vinf.net/2008/04/09/how-does-an-hp-fibre-channel-virtual-connect-module-work/ (specifically the section titled "Which VC-FC Port does my blade's HBA map to?".
Has this config changed in the newer modules? ISTR seeing HP documentation somewhere supporting the above info but, again, that was some time ago now.
If it no longer works this way then that is indeed a step in the right direction!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2010 06:56 AM
тАО04-26-2010 06:56 AM
Re: SAN rules re: Storage & HBA ports & Quads
this is from the latest version of the VC for Dummies book.
Fibre Channel (FC)login distribution and
failover features The Virtual Connect Fibre Channel connection provides login distribution and failover on FC uplinks to the SAN. A failure in your server connectivity with the SAN is a major problem. So HP has designed Virtual Connect Fibre Channel with built-in functionality that can automatically login to another active Fibre Channel port if a Fibre Channel connection fails. In other words, Virtual Connect provides Fibre Channel (FC)
login distribution and failover features, which means that the SAN administrator can automatically distribute server HBA
fabric logins across all Virtual Connect Fiber Channel (VC-FC) uplink ports on the same VC-FC module. Should a port fail or
lose the link, the VC-FC module bautomatically relogs the WWN into the fabric on another active VC-FC uplink port from the nsame VC-FC module.