OneView configuration with SE 32Gb FC module- in Synergy

[CadenLange]

Hi

I've also posted this on the Synergy forum was wasn't sure which was more appropriate :0)

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.

[Mark-S · Accepted solution]

First to be clear. 

Mezz 1  - Maps to ICM 3/6 in your case the 100Gb F32 Modules (Ethernet, FC, FCoE)  (4820c/6820c)

Mezz 2 - Maps to ICM 2/5 in your case the VC FC 32Gb (Fiber Channel Only) (5330c/5830c)

I assume all your ethernet traffic you plan to use 100Gb modules and all FC traffic via VC FC32 Module.

Once you create FC Networks (Fabric Attach) and assign them to the Uplink Sets with a set of ports.

Then create profile to map the downlink ports in the Server to the correct Network. There is a bit of intelligence build in where the Auto-mapping will be the easist to use and will add the connections to the correct mezz.

see below how ethernet maps to 3:1 while the FC networks map to the 2:1  (a-side) / 2:2 mezz (b-side)

From a non-redundant or redundant on the FC, it really comes down more to management and firmware operations.

If you create 2 LIGs, you will will have 2 FC Logical Interconnects. If you perform Firmware updates at the LI level, you would have to go to each LI to update the firmware on the ICM. (x2). If you want to make changes to A side and B-side it is 2 operations because you have to go to each LIG to make changes.

If you use redundant, you will have 1 LIGs and then 1 Logical Interconnect. Making changes to the FC is a single LIG so really a single operation. To update firmware, again at the LI level it is a single operation. 

The FC modules do not have a stacking option between them to truly make them a redundant path as you do with the Ethernet modules.

Some customers use non-redunant but I see others select redundant but again it only reapply applies to a mangagemt and Firmware operations of that module and how that is treated.

The Server Profile & FC connections would look the same either way. No configuration difference there.

hopes that sheds light.

[CadenLange]

Hi Mark

Thanks for the excellent explaination - that clarifies things superbly.

I'll create a single LIG in redundent mode to ease the upgrade procedures. I thought this option may need some kind of ring or mesh fabric to attach to but if it's only for management\firmware updates within OneView then that's great.

I'll use the auto-map for the server profile and look to ensure it's selected appopriate ports as per your screenshot.

many thanks again