HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

Virtual Connect - Fibre Channel (VCFC) connectivity

 
chuckk281
Trusted Contributor

Virtual Connect - Fibre Channel (VCFC) connectivity

Avi had a Fibre Channel connectivity question:

 

*********************************

 

Hi all,

 

 

Is it supported to connect 2 ports from each VCFC  to two  different Cisco Mds switched ?

 

Port 1 from VCFC 1 connected to Mds1, port 2 from VCFC1 connected to Mds2.

Port 1 from VCFC2 connected to  Mds1, port 2 from VCFC2 connected to Mds2.

 

If this  supported ,  what’s the benefit  ?

 

Thanks

 

*******************************

 

We had a lot of responses:

 

**************************

 

From Alexander: 

As I know it is not supported. Even in VCM you can make fabric only on each VC FC module, so if it will be connected to two different switches status will be degraded.

 

From Vincent: 

If a VC *fabric* has uplinks going to different switches, it will show up as degraded. But you can define 2 fabrics on each module, each with one uplink to its own MDS, and it will be fine. As to the benefits of doing this, I can’t really think of any.

 

From Cullen: 

Note that a single HBA port can only connect to one fabric.  Creating two fabrics in the VC FC module would mean that some of the servers could connect to one and some to the other; none would connect to both.  This would be one way to manually balance the load on the two switches and ensure that the load stays balanced in case of a VC FC failure.  On the other hand, it provides no particular benefit over connecting both ports on each VC FC to the same switch.

 

********************

 

Other comments or input?