- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: Blade Fiber Channel Mezz card connection with ...
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
тАО06-07-2013 12:23 PM
тАО06-07-2013 12:23 PM
Blade Fiber Channel Mezz card connection with Virtual Connect
When you only have 1 dual port FC Mezzanine card in a blade, how many SAN fabrics can you connect to? Just 2, or does Virtual Connect work its magic and allow more? We are installing a new 3PAR system that will be adding storage to what is provided to our C7000 blade enclosure by an EVA, but all our blades only have the one FC mezz card and both ports are already used for the existing EVA to give path redundancy. We can create a new SAN fabric for the 3PAR and use it to update the server profiles in Virtual Connect, but when applied, the new paths show as "not mapped". We need the blades to have access to both the EVA and the 3PAR. We are migrating all our virtual desktops to the 3PAR from the EVA. Short of buying a second FC mezz card for each blade, any ideas how to make this work? Thanks for any help.
- Tags:
- 3PAR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-12-2013 11:05 AM
тАО06-12-2013 11:05 AM
Re: Blade Fiber Channel Mezz card connection with Virtual Connect
Hi!
Only way I know of to connect to two Storage Arrays through a single HBA is by SAN zoning. If you already have a pair of SAN fabric Switches for path A & B, just create new zones for new storage. New storage would have to be set up to recognize HBA's WWN. I don't know about 3Par, but HP EVA and EMC best practice is to zone 1 target and 1 host (initator), but nothing that I know of says that same host could not target a second storage array by using a new different zone. It would be up to the host (s) to see storage LUN's correctly. Present a new LUN, then scan on each host for new storage, continuing until all new LUN's are presented. This way you are guaranteed each host sees the same LUN in same order. You will have to check on using native OS mulitpathing for all LUN's.
Louis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-16-2013 11:48 PM
тАО06-16-2013 11:48 PM
Re: Blade Fiber Channel Mezz card connection with Virtual Connect
You only have 2 ports. VC doesn't do any magic there to create more.
But those 2 ports can connect to almost as many arrays as you want as long as all those arrays (and the VC FC modules) are connected to the same SAN Fabric.