OneView 3.0 and VC-FC modules without ANY VC-Enet or VC-Flex installed

[eci]

I have a C7000 with the following:

1,2 = 10Gbps pass-thrus

3,4 = 4Gbps FC pass-thrus

5,6 = 8Gbps VC-FCs

I was able to configure the VC-FC modules with OneView - assigned Server profiles etc. The modules show configured and operational and are connected to a Cisco Nexus 5548UP using NPIV. I successfully mapped the Blade HBA ports to a MSA 2042 SAN also connected to the switch. I can map the storage - the works.

My question is, why is this working? According to HP it is impossible, that you must have a VC-Enet installed to get the VC-FC to work. It is working however. Thoughts?

[eci]

Attaching screenshots.

[peyrache]

just to be curious

are something working on bay 5 and 6 or configuration works only on pasthru ?

JY

[eci]

I have 3 Gen9 blades with Mezz2 HBAs. I was able to zone them on my Nexus switches. 

According to the VC-FC docs from 2013 it should not work - but it does.

Is this just a case of HP needing to update their docs? I am well aware that not all VCM features are supported, but the ones that are not I don't need:

Virtual Connect features not supported in HPE OneView 3.00

The following Virtual Connect features are not supported in HPE OneView 3.00:

• Multi-enclosure stacked domains

• iSCSI connections configured with DHCP addresses

• c3000 enclosures

• Network access groups

• IGMP multicast filters

• Double dense servers

• RADIUS and TACACS+ user authentication

• sFlow®

That's fine. 

[eci]

Per HPE OneView engineer:

"HPE OneView would support this, not Virtual Connect Manager. HPE OneView is the manager here, not VCM (which would have been turned off if you had VC Ethernet modules in the Enclosure).

The architecture of HPE OneView is different than Virtual Connect Manager.  If you were not using HPE OneView, then you will need VC Ethernet modules and that is where VCM lives.  Since you are using HPE OneView, it does not require VC Ethernet modules just to manage VC Fibre Channel modules.  Please do not rely on Virtual Connect Manager documentation here, as it is not applicable.  You need to review HPE OneView supporting documentation."

Awesome.