Cannot import Hypervisor Cluster profile in non-VC deployment

[FTravinsky]

Hello, world!
I'm willing to deploy an orchestrated SPP firmware+drivers update on a ESXi 6.7 Gen10 fully populated Synergy frame.

For an unknown reason it is mandatory that a Server profile template should have MGMT network in it's connections:

Unfortunately, the frame has non-VC interconnects:
- Synergy 40Gb F8 Switch Module
- Brocade 16Gb/12 FC Switch Module for Synergy
Thus, networking can't be managed by OneView.

Please tell the reason why this fact should forbid me from creating/importing a vCenter cluster.
In the end I just need OneView to toggle maintenance mode on and off like 12 times.

[AmRa]

Hi 

Please let us know the OneView version.

[FTravinsky]

---

Hi,

Latest 5.3. Although the error was there at 5.0 too.

I believe this limitation could be connected to grow cluster feature or virtual switch configurations (which I prefer staying managed by vCenter).

The hypervisor network configuration defines the virtual switches and port groups. The virtual switch configuration is
automatically built based on the connections in the associated server profile template and the hypervisor settings of the
hypervisor cluster profile

---

In any case such error/restriction better be lifted to Actions, which really require networking.

[tech3d]

Hi FTravinsky,

One of the requirements to use hypervisor cluster profile on OneView, is to define the networks on Virtual Connect.
Refer to page 30 of https://psnow.ext.hpe.com/doc/a00097801en_us
Synergy 40Gb F8 Switch Module doesn't appear to be supported as its not managed by OneView.

[FTravinsky]

As I can't through away existing interconnects for this feature, I humbly request OneView team to remove the VC-networking requirement for cluster management and move it elsewhere, for the Actions actually require adapter reconfiguration, like virtual switches or grow/shrink.

[FTravinsky]

Updated to OV 5.4. 
Still the same - can't import Hypervisor Cluster, as server profile template has no connections configured.

[Deepak_AG712]

Hi FTravinsky, 

please refer to the link - https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00101857en_us - Page 46

[FTravinsky]

Yeap,

The hypervisor network configuration defines the virtual switches and port groups. The virtual switch configuration is automatically built based on the connections in the associated server profile template and the hypervisor settings of thehypervisor cluster profile.

---

I'm just telling I absolutely don't need networking managed by OneView, but I do require orchestrated firmware upgrades.
Hope, OneView Team will consider my feature request.

[tech3d]

Hi  FTravinsky,

For managed driver & firmware updates of ESXi hosts, you need to use Integrated Smart Update Tools (iSUT)

Please check the following document :

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=emr_na-a00092495en_us

If you do not already have iSUT installed on your servers, it can be downloaded from this link :

https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_8e29abc6eccf447e8d0e879fbb

https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_55389489af724ac299a9148c7a

[FTravinsky]

I really do use iSUT.

I’m pointing out I currently have to manually enable maintenance mode in vCenter 12 times one by one to apply new SPP (with iSUT doing the job right the moment when maintenance enabled).

It takes a whole day as I can’t manage the Cluster from OneView due to named limitation (having Synergy non-VC interconnects purchased).