- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- LCAP Truncking Virtual Connect
BladeSystem - General
1753518
Members
5105
Online
108795
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
01-29-2010 08:03 AM
01-29-2010 08:03 AM
LCAP Truncking Virtual Connect
I was arguing with my network team saying that LCAP and/or trunking is not done on the LAN core switch, but they are saying that they enabled it.
From virtual connect manager, how we can find out whether a connected port is in LCAP and trunking?
Thanks.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2010 09:42 AM
01-29-2010 09:42 AM
Re: LCAP Truncking Virtual Connect
Shashi,
Although UplinkSets can be created on the VC side using several physical uplink cables, the lan switch ports also need to be configured as an LACP Trunk, or LACP group. This tells the port that it can send the network traffic for the blades down any of the ports in the trunk, and it will get there.
If this is not done, it is likely that your uplink will still work, however an important piece of information is being withheld from the switch, and as a result the usage of the uplinks will be very inefficent. Ports will start generating errors, and could eventually end up being "errored-out".
The bottom line is that the uplinkset/trunk must be configured on both the VC side, and on the Switch side.
Dave.
Although UplinkSets can be created on the VC side using several physical uplink cables, the lan switch ports also need to be configured as an LACP Trunk, or LACP group. This tells the port that it can send the network traffic for the blades down any of the ports in the trunk, and it will get there.
If this is not done, it is likely that your uplink will still work, however an important piece of information is being withheld from the switch, and as a result the usage of the uplinks will be very inefficent. Ports will start generating errors, and could eventually end up being "errored-out".
The bottom line is that the uplinkset/trunk must be configured on both the VC side, and on the Switch side.
Dave.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP