I have a C7000 with the following:
1,2 = 10Gbps pass-thrus
3,4 = 4Gbps FC pass-thrus
5,6 = 8Gbps VC-FCs
We don't want any VC-FC features - we just want pass-through to our Nexus 5548UPs. Using OneView in managed mode, I was able to configure the VC-FC's and my Nexus switches see the Blade PWWNs.
It *appears* this can work now without VC-Enets at all. Any input?
Is VC-Enet still required now that we have OneView?
I can't find the latest firmware for HP VC 16Gb 24-Port FC Module. I'm getting an error in our C-Class Blade enclosure that I need version 3.05 of this firmware. However the latest firmware that comes with OA 4.5 is 3.0. I can't find this anywhere to download. Does anyone have any suggestions?
The error is: Module in bay enc0:iobay3 firmware version 3.00 does not match the supported firmware version 3.05.
Thanks!
Interconnect Bay Status - Bay 3(HP VC 16Gb 24-Port FC Module) 
From VCSU...I thought I could get it from the SPP and the 450 bin file. I guess not...
HP VC 16Gb 24-Port FC 3.00 v7.2.1_38 module
Message says I need 3.05.
I appreciate the help. Unfortunately the latest version I can find is 4.5.
This is what I have and it doesn't include the newer firmware I need. It's not in the latest bundle that is available online.
I think I need to call support.
VC FC firmware version 3.05 is part of VC firmware 4.50.
Get the file vcfwall450.bin and start vcutil in interactive mode (option update).
Leave all parameters to default except FORCE=HEALTH, review the summary and confirm the update.
This will only update the "incompatible" module.
>> Is VC-Enet still required now that we have OneView?
Without the ethernet modules you cannot configure the VC FC modules.
Even Oneview configures the Enet modules, then the Enet modules pass the config to the FC modules.
Thanks for the reply. I am confused, then!
OneView allowed me to create the interconnect group, and map the ports completely to the SAN. The blade HBA ports appear on my Cisco Nexus interfaces, I zoned them, and the MSA2042 SAN sees both initators......I can map storage, the blade can mount it. Is this supposed to be impossible?
See attached -
Maybe you use
3,4 = 4Gbps FC pass-thrus
We wanted 8gbps. HP never made a passthru @ that speed. :(
How can it be explained that the server can use the SAN storage through the VC-FC? This is OneView 3.0 - maybe some new features? It found the VC-FC instantly and reported success on configuring it. OneView added the VCM link into the OBA.
Also - as far as being able to configure them -
I made a Server Profile that included the 2 ports and applied it. Immediately, the PWWN's showed up on the Nexus. So it does appear to be doing something...
Interesting ...
If you review the virtual connect quickspec, you will not find in the supported configurations section any config without an ethernet module.
So obviously it works, but it is unsupported.
Can you open the virtual connect manager?
Just for my curiosity ...
I would not use an unsupported configuration in a production environment.
The Virtual Connect Manager link presented in OBA is a link to OneView. It works.
OneView 3.0 cookbook:
" HPE OneView replaces Virtual Connect Manager and Virtual Connect Enterprise Manager when the enclosure is migrated into HPE OneView. Virtual Connect Manager is no longer available and cannot be logged into once the enclosure is managed by HPE OneView"
http://h20195.www2.hpe.com/V2/getpdf.aspx/4AA5-0351ENW.pdf?ver=Rev%206
Yes, once configured in OneView, you cannot manage with other tools.
I was not sure if you can still open VCM ...
Maybe you can ask here again
https://community.hpe.com/t5/HPE-OneView/bd-p/hp-oneview
but I still think this configuration is not supported.
If in doubt, ask HPE support.
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."
OK, OneView is replacing the VCM. No doubt.
The documentation
HPE OneView 3.0 Support Matrix
chapter 2.10 Interconnect modules
list the VC FC modules as fully supported and it does not say an ethernet module is needed.
It does also not say it is working without such modules... but obviously it does.
However, a real corner case, since you get all the advantages of blades and OneView only with the Enet modules.
Yes - an odd case.
It was a 5 year old chassis with just pass through. Customer wanted to use 8Gbps. Much, much cheaper doing it this way than buying an additional 2 modules.
Hello,
If I try to connect to Virtaul Connect Manager by using the Virtual Connect IP address I get "Your browser does not have the required functionality to run this application". I can use the DNS name for the Virtual Connect and it connects fine and I can login. Windows 2008 IE 11. Firefox works either way.
Anyone know how to address this? I went through all the sign-in help instructions and haven't found a workaround yet.
Mark
