Virtual Connect multiple network configuration not working

craigP — Sun, 03 Oct 2021 06:29:43 GMT

I have a strange issue related to using Shared Uplink sets (SUS) and multiple network configurationas follows:
My example
Blade centre 1 has 2 SUS defined SUS1 and SUS2, both with vnet 1 in the uplink sets
Blade1 has a selected network configuration for its server profile -vnet 1a configured on pnic3
Blade1 also has a selected network configuration for its server profile -vnet 1b configured on pnic4.
I have blade16 also configured to use vnet1a and 1b only not as a selected networks but as a vnets in a multiple networks configuration for its server profile. If I try and change blade1’s configuration to match blade16 i.e. from selected network to multiple networks then all the vms hosted on blade 1 stop responding to pings. I have raised this with HP who have escalated to L2. Current virtual connect firmware is upto date.
Blade centre - BladeSystem c7000 Enclosure G3
Blades - ProLiant BL460c Gen8
Virtual connect
Model - HP VC FlexFabric-20/40 F8 Module
firmware - 4.85 2020-07-17T20:55:43Z
Anyone come across this?

Re: Virtual Connect multiple network configuration not working

Ihaqueit — Fri, 01 Oct 2021 13:15:57 GMT

Can you explain your blade server network connectivity?

e.g. Blades connected to vcflex via Core switch!

Is it first time configuration or existing?

After configure of VCflex any blinks ?

topic Re: Virtual Connect multiple network configuration not working in BladeSystem - General

Virtual Connect multiple network configuration not working

Re: Virtual Connect multiple network configuration not working