- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Virtual Connect multiple network configuration not...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2021 02:57 AM - last edited on 10-02-2021 11:29 PM by support_s
10-01-2021 02:57 AM - last edited on 10-02-2021 11:29 PM by support_s
Virtual Connect multiple network configuration not working
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2021 06:15 AM
10-01-2021 06:15 AM
Re: Virtual Connect multiple network configuration not working
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 ?