- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- LACP PDUs Tx/Rx: meaning of PDU Tx/Rx dissimilar v...
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
07-16-2018 02:00 AM - edited 07-16-2018 05:54 AM
07-16-2018 02:00 AM - edited 07-16-2018 05:54 AM
LACP PDUs Tx/Rx: meaning of PDU Tx/Rx dissimilar values
Is anyone able to explain why LACP PDUs Tx/Rx values reported on different LACP trunks (Switch-to-Server versus Switch-to-Switch) can be so dissimilar (especially considering the received LACP PDU from remote peer...in this case a Server)?
Is below difference reasonable or not (the LACP is working normally AFAIK)?
Switch-to-Server LACP Trunk case (fast):
VSF# show lacp counters ethernet 1/B15,2/B15 LACP Port Counters. LACP LACP Marker Marker Marker Marker Port Trunk PDUs Tx PDUs Rx Req. Tx Req. Rx Resp. Tx Resp. Rx Error ----- ------ --------- --------- -------- -------- -------- -------- -------- 1/B15 Trk110 3554552 118098 0 0 0 0 0 2/B15 Trk110 3554439 118099 0 0 0 0 0
Note: the LACP Trunk on remote Server is done on IBM Power8 VIOS.
Switch-to-Switch LACP Trunk case (fast):
VSF# show lacp counters ethernet 1/C1,2/C1 LACP Port Counters. LACP LACP Marker Marker Marker Marker Port Trunk PDUs Tx PDUs Rx Req. Tx Req. Rx Resp. Tx Resp. Rx Error ----- ------ --------- --------- -------- -------- -------- -------- -------- 1/C1 Trk1 174902 174899 0 0 0 0 0 2/C1 Trk1 174898 174897 0 0 0 0 0
Shouldn't be that - in an ideal situation - LACP PDUs Tx and Rx counters should increment in unison (like the case of Switch-to-Switch LACP)?
I'm not an HPE Employee

Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP