New Synergy deployment with SE 32Gb FC modules.

[CadenLange]

Hi

I've a Synergy 12000 chassis fitted with 2 x SE 32Gb FC modules in bays 2 & 5. There are also 2 x SE 100Gb F32 modules in bays 3 & 6.

I have a couple of general questions on how I need to configure the LIGs for this environment.

Is it typical to create 3 x LIGs as below:

1 x LIG for the SE 100Gb F32 ,containing both the interconnects in Bay 3 & 6 configured in 'redundant' mode. This will be connected to pair of Cisco siwtches with a vpc.

1 x LIG for the SE 32Gb FC module in Bay 2 configured as 'Non reundant Side A'. This will be connected to an HPE B series switch in Fabric A

1 x LIG for the SE 32Gb FC module in Bay 5 configured as 'Non reundant Side B'. This will be connected to an HPE B series switch in Fabric B

I would then create an Enclosure Group with all three LIGs configured

Secondly - when creating a server profile template do I need to create  an FC 'connection' for the FC downlink ports to the HBA? Or is this only necessary to create connection for the Ethernet traffic on the SE 100Gb F32 module and he FC connections are configured only at an OS  (ESXi 7.x) level?

I've looked but can't really find any useful information on how to best configure these modules

Thanks in advance

Caden

[support_s]

System recommended content:

1. HPE Virtual Connect SE 32Gb FC Modules for HPE Synergy Release Notes

2. HPE Virtual Connect SE 32Gb FC Module for HPE Synergy Release Notes

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[tech3d]

Hi Caden, 

Greetings from HPE.

Here are the redundancy options available when creating LIG (logical interconnect group) - interconnect configuration template :

> High Availability (only available for multiple frame ILT using VC SE40G or VC SE100G interconnects.
Two interconnects on opposite sides of two enclosures that are both available to all enclosures connected with interconnect link modules. This configuration allows for the loss of any single interconnect or enclosure without affecting connectivity of the remaining enclosures.

> Redundant
The same interconnect type on both sides of a single enclosure. This configuration allows for the loss of the interconnect on one side without affecting connectivity of the enclosure. The loss of the interconnects on both sides causes the enclosure to lose connectivity.

> Non redundant side A
One interconnect in a single side A bay (1, 2, or 3) in an enclosure that can be connected to other enclosures that have an interconnect link module in the same bay. Loss of any interconnect results in loss of connectivity.

> Non redundant side B
One interconnect in a single side B bay (4, 5, or 6) in an enclosure that can be connected to other enclosures that have an interconnect link module in the same bay. Loss of any interconnect results in loss of connectivity.

If you are using a pair of interconnects its recommended to use either the 'High Availability' or the 'Redundant' option depending on the model of the interconnect being used.

So, here's the summary of steps :
1. define the networks (ethernet & FC)
 - its needed to defind the FC as well because OneView uses software defined networking, and we need entities to tag the connections point to point.
 
2. Create 2x LIGs. 1x for VC SE 100 & 1x for VC SE 32Gb FC.

3. Create a EG (enclosure group) - enclosure configuration template, and combile all the LIGs here.

4. Use the EG to configure the LE (logical enclosure).
   - this will create the LIs (logical interconnects) - the actual hardware configuration on the interconnects.
   
5. define server profiles, to assign the networks to the servers' ports.
 - the server profile also provides automation using a server profile template and we can define RAID on the local storage controller, set BIOS & iLO settings as well.