- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- VC with LACP
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
03-27-2020 05:12 AM - edited 03-27-2020 05:12 AM
03-27-2020 05:12 AM - edited 03-27-2020 05:12 AM
Hello.
I need test instance without VC configured. Can someone tell me VC work with LACP without basic setup and configured domain? If I plug in 2 SFP in two VC on empty config VC created LACP automaticaly?
Solved! Go to Solution.
- Tags:
- LACP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-30-2020 03:54 AM
03-30-2020 03:54 AM
SolutionDefault VC module configuration:
When VC modules are inserted into an enclosure that is not yet part of a Virtual Connect domain, the modules are configured to provide basic connectivity. After a Virtual Connect domain is defined for an enclosure, server blades within that enclosure are isolated from all external network and fabric connections until configured explicitly within VCM.
When not part of a Virtual Connect domain, each VC-Enet module is configured so that all server ports connected to that module are connected to a single network, which is then connected to a single uplink. To provide greater bandwidth, you can use LACP to aggregate additional ports on that module, as long as they are connected to the same external switch. For aggregation of links to an external switch, the external switch must support dynamic creation of link aggregation groups using the IEEE 802.3ad LACP. All stacking links are disabled. This default configuration enables connectivity testing between server NICs and devices outside the enclosure prior to Virtual Connect domain configuration.
When not part of a Virtual Connect domain, all of the VC-FC Module uplink ports are grouped into an uplink port group and dynamically distribute connectivity from all server blades across all available uplink ports.
For more information please refer HPE Virtual Connect for c-Class BladeSystem Setup and Installation Guide Version 4.80
https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00094034en_us
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]