ISO/IEC/IEEE 8802-1AX:2016

Information technology — Telecommunications and information exchange between systems — Local and metropolitan area networks — Specific requirements — Part 1AX: Link aggregation

Link Aggregation provides protocols, procedures, and managed objects that allow the following: - One or more parallel instances of full-duplex point-to-point links to be aggregated together to form a Link Aggregation Group (LAG), such that a MAC Client can treat the LAG as if it were a single link. - A resilient interconnect using multiple full-duplex point-to-point links among one to three nodes in a network and one to three nodes in another, separately administered, network, along with a means to ensure that frames belonging to any given service will use the same physical path in both directions between the two networks. ISO/IEC/IEEE 8802-1AX:2015 defines the MAC-independent Link Aggregation capability and general information relevant to specific MAC types that support Link Aggregation. The capabilities defined are compatible with previous versions of this standard.

Technologies de l'information — Télécommunications et échange d'information entre systèmes — Réseaux locaux et métropolitains — Exigences spécifiques — Partie 1AX: Agrégation de lien

General Information

• Status: Withdrawn
• Publication Date: 13-Jan-2016
• Withdrawal Date: 13-Jan-2016
• ICS: 35.110 - Networking
• Technical Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Drafting Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 13-Sep-2021
• Completion Date: 14-Feb-2026

Relations

• Revised: ISO/IEC/IEEE 8802-1AX:2021 - Telecommunications and exchange between information technology systems — Requirements for local and metropolitan area networks — Part 1AX: Link aggregation
• Effective Date: 18-Apr-2021

Standards Content (Sample)

INTERNATIONAL ISO/IEC/
STANDARD IEEE
8802-1AX
First edition
2016-01-15
Information technology —
Telecommunications and information
exchange between systems — Local and
metropolitan area networks — Specific
requirements
Part 1AX:
Link Aggregation
Technologies de l'information — Télécommunications et échange
d'information entre systèmes — Réseaux locaux et métropolitains —
Exigences spécifiques —
Partie 1AX: Agrégation de lien
Reference number
©
IEEE 2014
©  IEEE 2014
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from ISO, IEC or IEEE at the respective
address below.
Institute of Electrical and Electronics Engineers, Inc. �S� �o��right o��i�e
Ch. de Blandonnet 8 • CP 4013 Park Avenue, New York
NY 10016-5997, USA CH-1214 Vernier, Geneva, Switzerland
E-mail [e-mail] Tel. [phone]
Web www.ieee.org Fax [phone]
�o��right�iso.org
www.iso.org
Published in Switzerland
ii © IEEE 2014 – All rights reserved

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees established
by the respective organization to deal with particular fields of technical activity. ISO and IEC technical
committees collaborate in fields of mutual interest. Other international organizations, governmental and non-
governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO
and IEC have established a joint technical committee, ISO/IEC JTC 1.
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating
Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards
through a consensus development process, approved by the American National Standards Institute, which
brings together volunteers representing varied viewpoints and interests to achieve the final product. Volunteers
are not necessarily members of the Institute and serve without compensation. While the IEEE administers the
process and establishes rules to promote fairness in the consensus development process, the IEEE does not
independently evaluate, test, or verify the accuracy of any of the information contained in its standards.
The main task of ISO/IEC JTC 1 is to prepare International Standards. Draft International Standards adopted
by the joint technical committee are circulated to national bodies for voting. Publication as an International
Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is called to the possibility that implementation of this standard may require the use of subject matter
covered by patent rights. By publication of this standard, no position is taken with respect to the existence or
validity of any patent rights in connection therewith. ISO/IEEE is not responsible for identifying essential
patents or patent claims for which a license may be required, for conducting inquiries into the legal validity or
scope of patents or patent claims or determining whether any licensing terms or conditions provided in
connection with submission of a Letter of Assurance or a Patent Statement and Licensing Declaration Form, if
any, or in any licensing agreements are reasonable or non-discriminatory. Users of this standard are expressly
advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is
entirely their own responsibility. Further information may be obtained from ISO or the IEEE Standards
Association.
ISO/IEC/IEEE 8802-1AX was prepared by the LAN/MAN of the IEEE Computer Society (as
IEEE 8802-1AX-2014). It was adopted by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 6, Telecommunications and information exchange between systems, in parallel with its
approval by the ISO/IEC national bodies, under the “fast-track procedure” defined in the Partner Standards
Development Organization cooperation agreement between ISO and IEEE. IEEE is responsible for the
maintenance of this document with participation and input from ISO/IEC national bodies.
© IEEE 2014 – All rights reserved iii

IEEE Standard for
Local and metropolitan area networks—

Link Aggregation
IEEE Computer Society
Sponsored by the
LAN/MAN Standards Committee
IEEE
IEEE Std 802.1AX™-2014
3 Park Avenue
(Revision of
New York, NY 10016-5997
IEEE Std 802.1AX-2008)
USA
IEEE Std 802.1AX™-2014
(Revision of
IEEE Std 802.1AX-2008)
IEEE Standard for
Local and metropolitan area networks—
Link Aggregation
Sponsor
LAN/MAN Standards Committee
of the
IEEE Computer Society
Approved 10 December 2014
IEEE SA-Standards Board
ISO/IEC/IEEE 8802 1AX:2016(E)
Abstract: MAC-independent Link Aggregation capability and general information relevant to
specific MAC types are defined in this standard. Link Aggregation allows parallel full-duplex point-
to-point links to be used as if they were a single link and also supports the use of multiple links as
a resilient load sharing interconnect between multiple nodes in two separately administered
networks.
Keywords: Aggregated Link, Aggregator, Distributed Resilient Network Interconnect, DRNI, ®
IEEE 802 , IEEE 802.1AX™, interconnect, Link Aggregation, Link Aggregation Group, local area
network, management, Network-Network Interface, NNI
The Institute of Electrical and Electronics Engineers, Inc.
3 Park Avenue, New York, NY 10016-5997, USA
All rights reserved. Published 30 December 2014. Printed in the United States of America.
IEEE and 802 are registered trademarks in the U.S. Patent & Trademark Office, owned by The Institute of
Electrical and Electronics Engineers, Incorporated.
Print: ISBN 978-0-7381-9448-6 STD20052
PDF: ISBN 978-0-7381-9449-3 STDPD20052
IEEE prohibits discrimination, harassment, and bullying.
For more information, visit http://www.ieee.org/web/aboutus/whatis/policies/p9-26.html.
No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission
of the publisher.
ISO/IEC/IEEE 8802 1AX:2016(E)
Important Notices and Disclaimers Concerning IEEE Standards Documents
IEEE documents are made available for use subject to important notices and legal disclaimers. These notices
and disclaimers, or a reference to this page, appear in all standards and may be found under the heading
“Important Notice” or “Important Notices and Disclaimers Concerning IEEE Standards Documents.”
Notice and Disclaimer of Liability Concerning the Use of IEEE Standards
Documents
IEEE Standards documents (standards, recommended practices, and guides), both full-use and trial-use, are
developed within IEEE Societies and the Standards Coordinating Committees of the IEEE Standards
Association (“IEEE-SA”) Standards Board. IEEE (“the Institute”) develops its standards through a
consensus development process, approved by the American National Standards Institute (“ANSI”), which
brings together volunteers representing varied viewpoints and interests to achieve the final product.
Volunteers are not necessarily members of the Institute and participate without compensation from IEEE.
While IEEE administers the process and establishes rules to promote fairness in the consensus development
process, IEEE does not independently evaluate, test, or verify the accuracy of any of the information or the
soundness of any judgments contained in its standards.
IEEE does not warrant or represent the accuracy or content of the material contained in its standards, and
expressly disclaims all warranties (express, implied and statutory) not included in this or any other
document relating to the standard, including, but not limited to, the warranties of: merchantability; fitness
for a particular purpose; non-infringement; and quality, accuracy, effectiveness, currency, or completeness of
material. In addition, IEEE disclaims any and all conditions relating to: results; and workmanlike effort.
IEEE standards documents are supplied “AS IS” and “WITH ALL FAULTS.”
Use of an IEEE standard is wholly voluntary. The existence of an IEEE standard does not imply that there
are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to
the scope of the IEEE standard. Furthermore, the viewpoint expressed at the time a standard is approved and
issued is subject to change brought about through developments in the state of the art and comments
received from users of the standard.
In publishing and making its standards available, IEEE is not suggesting or rendering professional or other
services for, or on behalf of, any person or entity nor is IEEE undertaking to perform any duty owed by any
other person or entity to another. Any person utilizing any IEEE Standards document, should rely upon his
or her own independent judgment in the exercise of reasonable care in any given circumstances or, as
appropriate, seek the advice of a competent professional in determining the appropriateness of a given IEEE
standard.
IN NO EVENT SHALL IEEE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO:
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE PUBLICATION, USE OF, OR RELIANCE UPON
ANY STANDARD, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE AND
REGARDLESS OF WHETHER SUCH DAMAGE WAS FORESEEABLE.
iii
ISO/IEC/IEEE 8802 1AX:2016(E)
Translations
The IEEE consensus development process involves the review of documents in English only. In the event
that an IEEE standard is translated, only the English version published by IEEE should be considered the
approved IEEE standard.
Official statements
A statement, written or oral, that is not processed in accordance with the IEEE-SA Standards Board
Operations Manual shall not be considered or inferred to be the official position of IEEE or any of its
committees and shall not be considered to be, or be relied upon as, a formal position of IEEE. At lectures,
symposia, seminars, or educational courses, an individual presenting information on IEEE standards shall
make it clear that his or her views should be considered the personal views of that individual rather than the
formal position of IEEE.
Comments on standards
Comments for revision of IEEE Standards documents are welcome from any interested party, regardless of
membership affiliation with IEEE. However, IEEE does not provide consulting information or advice
pertaining to IEEE Standards documents. Suggestions for changes in documents should be in the form of a
proposed change of text, together with appropriate supporting comments. Since IEEE standards represent a
consensus of concerned interests, it is important that any responses to comments and questions also receive
the concurrence of a balance of interests. For this reason, IEEE and the members of its societies and
Standards Coordinating Committees are not able to provide an instant response to comments or questions
except in those cases where the matter has previously been addressed. For the same reason, IEEE does not
respond to interpretation requests. Any person who would like to participate in revisions to an IEEE
standard is welcome to join the relevant IEEE working group.
Comments on standards should be submitted to the following address:
Secretary, IEEE-SA Standards Board
445 Hoes Lane
Piscataway, NJ 08854 USA
Laws and regulations
Users of IEEE Standards documents should consult all applicable laws and regulations. Compliance with the
provisions of any IEEE Standards document does not imply compliance to any applicable regulatory
requirements. Implementers of the standard are responsible for observing or referring to the applicable
regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not
in compliance with applicable laws, and these documents may not be construed as doing so.
Copyrights
IEEE draft and approved standards are copyrighted by IEEE under U.S. and international copyright laws.
They are made available by IEEE and are adopted for a wide variety of both public and private uses. These
include both use, by reference, in laws and regulations, and use in private self-regulation, standardization,
and the promotion of engineering practices and methods. By making these documents available for use and
adoption by public authorities and private users, IEEE does not waive any rights in copyright to the
documents.
iv
ISO/IEC/IEEE 8802 1AX:2016(E)
Photocopies
Subject to payment of the appropriate fee, IEEE will grant users a limited, non-exclusive license to
photocopy portions of any individual standard for company or organizational internal use or individual, non-
commercial use only. To arrange for payment of licensing fees, please contact Copyright Clearance Center,
Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; [phone]. Permission to
photocopy portions of any individual standard for educational classroom use can also be obtained through
the Copyright Clearance Center.
Updating of IEEE Standards documents
Users of IEEE Standards documents should be aware that these documents may be superseded at any time
by the issuance of new editions or may be amended from time to time through the issuance of amendments,
corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the
document together with any amendments, corrigenda, or errata then in effect.
Every IEEE standard is subjected to review at least every ten years. When a document is more than ten years
old and has not undergone a revision process, it is reasonable to conclude that its contents, although still of
some value, do not wholly reflect the present state of the art. Users are cautioned to check to determine that
they have the latest edition of any IEEE standard.
In order to determine whether a given document is the current edition and whether it has been amended
through the issuance of amendments, corrigenda, or errata, visit the IEEE-SA Website at http://
ieeexplore.ieee.org/expel/standards.jsp or contact IEEE at the address listed previously. For more
information about the IEEE SA or IOWA’s standards development process, visit the IEEE-SA Website at
http://standards.ieee.org.
Errata
Errata, if any, for all IEEE standards can be accessed on the IEEE-SA Website at the following URL: http://
standards.ieee.org/findstds/errata/index.html. Users are encouraged to check this URL for errata
periodically.
Patents
Attention is called to the possibility that implementation of this standard may require use of subject matter
covered by patent rights. By publication of this standard, no position is taken by the IEEE with respect to the
existence or validity of any patent rights in connection therewith. If a patent holder or patent applicant has
filed a statement of assurance via an Accepted Letter of Assurance, then the statement is listed on the IEEE-
SA Website at http://standards.ieee.org/about/sasb/patcom/patents.html. Letters of Assurance may indicate
whether the Submitter is willing or unwilling to grant licenses under patent rights without compensation or
under reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfair
discrimination to applicants desiring to obtain such licenses.
Essential Patent Claims may exist for which a Letter of Assurance has not been received. The IEEE is not
responsible for identifying Essential Patent Claims for which a license may be required, for conducting
inquiries into the legal validity or scope of Patents Claims, or determining whether any licensing terms or
conditions provided in connection with submission of a Letter of Assurance, if any, or in any licensing
agreements are reasonable or non-discriminatory. Users of this standard are expressly advised that
determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their
own responsibility. Further information may be obtained from the IEEE Standards Association.
v
ISO/IEC/IEEE 8802 1AX:2016(E)
Participants
The following individuals were officers and members of the Higher Layer LAN Protocols Working Group at
the beginning of the Working Group ballot. Individuals may have not voted, voted for approval, disapproval,
or abstained on this standard.
Glenn Parsons, Working Group Chair
John Messenger, Working Group Vice Chair
Stephen Haddock, Chair, Interworking Task Group
Michael Seaman, Chair, Security Task Group
Michael Johas Teener, Chair, Time Sensitive Networking Task Group
Pat Thaler, Chair, Data Center Bridging Task Group
Maximilian Riegel, Chair, OmniRAN Task Group
Eric Gray, Recording Secretary
Ting Ao Hitosh Hayakawa Karen Randall
Jeremy Hitt
Christian Boiger Dan Romascanu
Paul Bottorff Rahil Hussain Jessy V. Rouyer
David Chen Anthony Jeffree Panagiotis Saltsidis
Feng Chen Peter Jones Behcet Sarikaya
Weiying Cheng Hal Keen Daniel Sexton
Diego Crupnicoff Marcel Kiessling Johannes Specht
Rodney Cummings Yongbum Kim Kevin B. Stanton
Patrick Diamond Philippe Klein Wilfried Steiner
Aboubacar Kader Diarra Jouni Korhonen Vahid Tabatabaee
Janos Farkas Jeremy Touve
Jeff Lynch
Norman Finn Ben Mack-Crane Karl Weber
Geoffrey Garner Christophe Mangin Yuehua Wei
Anoop Ghanwani James McIntosh Brian Weis
Mark Gravel Eric Multanen Jordon Woods
Craig Gunther Donald Pannell Juan-Carlos Zuniga
vi
ISO/IEC/IEEE 8802 1AX:2016(E)
The following members of the individual balloting committee voted on this standard. Balloters may have
voted for approval, disapproval, or abstention.
James Innis
Thomas Alexander Michael Newman
Richard Alfvin Osamu Ishida Nick S.A. Nikjoo
Butch Anton Akio Iso Paul Nikolich
Jacob Ben Ary Atsushi Ito Satoshi Obara
Nancy Bravin Raj Jain Maximilian Riegel
William Byrd Anthony Jeffree Dan Romascanu
Juan Carreon Michael Johas Teener Jessy V. Rouyer
Keith Chow Peter Jones Panagiotis Saltsidis
Charles Cook Shinkyo Kaku Peter Saunderson
Piotr Karocki Michael Seaman
Patrick Diamond
Yezid Donoso Stuart Kerry Kapil Sood
Sourav Dutta Yongbum Kim Thomas Starai
Donald Eastlake, 3rd Bruce Kraemer Rene Struik
Richard Edgar Geoff Ladwig Walter Struppler
Mark Laubach William Taylor
Andrew Fieldsend
Yukihiro Fujimoto John Lemon Dmitri Varsanofiev
Devon Gayle Ru Lin Prabodh Varshney
Anoop Ghanwani Elvis Maculuba George Vlantis
Randall Groves Roger Marks Hung-Yu Wei
Andreas Wolf
Chris Guy Jeffery Masters
Stephen Haddock Brett Mcclellan Chun Yu
Werner Hoelzl Jonathon Mclendon Charles Wong
Rita Horner Richard Mellitz Michael Wright
Victor Hou John Messenger Oren Yuen
Noriyuki Ikeuchi Charles Moorwood Daidi Zhong
Jose Morales
vii
ISO/IEC/IEEE 8802 1AX:2016(E)
When the IEEE-SA Standards Board approved this standard on 10 December 2014, it had the following
membership:
John Kulick, Chair
Jon Walter Rosdahl, Vice Chair
Richard H. Hulett, Past Chair
Konstantinos Karachalios, Secretary
Peter Balma Michael Janezic Ron Peterson
Farooq Bari Jeffrey Katz Adrian Stephens
Joseph L. Koepfinger* Peter Sutherland
Ted Burse
David J. Law Yatin Trivedi
Clint Chaplain
Hung Ling Phil Winston
Stephen Dukes
Don Wright
Jean-Phillippe Faure Oleg Logvinov
Yu Yuan
T. W. Olsen
Gary Hoffman
Glenn Parsons
*Member Emeritus
Also included are the following nonvoting IEEE-SA Standards Board liaisons:
Richard DeBlasio, DOE Representative
Michael Janezic, NIST Representative
Michelle Turner
IEEE-SA Content Publishing
Kathryn Bennett
IEEE-SA Technical Community Programs
viii
ISO/IEC/IEEE 8802 1AX:2016(E)
Introduction
This introduction is not part of IEEE Std 801.AX™-2014, IEEE Standard for Local and metropolitan area
networks—Link Aggregation.
This standard contains state-of-the-art material. The area covered by this standard is undergoing evolution.
Revisions are anticipated within the next few years to clarify existing material, to correct possible errors, and ®
to incorporate new related material. Information on the current revision state of this and other IEEE 802
standards can be obtained from:
Secretary, IEEE-SA Standards Board
445 Hoes Lane
P.O. Box 1331
Piscataway, NJ 08855-1331
USA
ix
ISO/IEC/IEEE 8802 1AX:2016(E)
x
ISO/IEC/IEEE 8802 1AX:2016(E)
Contents
1. Overview. 1
1.1 Scope. 1
1.2 Purpose. 1
1.3 State diagram conventions . 2
2. Normative references. 3
3. Definitions . 4
4. Acronyms and abbreviations . 7
5. Conformance. 8
5.1 Requirements terminology. 8
5.2 Protocol Implementation Conformance Statement. 8
5.3 Link Aggregation requirements . 8
5.3.1 Link Aggregation options . 9
5.4 Distributed Resilient Network Interconnect requirements . 9
5.4.1 Distribution Resilient Network Interconnect options . 9
6. Link Aggregation. 11
6.1 Overview. 11
6.1.1 Goals and objectives . 11
6.1.2 Positioning of Link Aggregation within the IEEE 802 architecture. 12
6.1.3 LLDP Parser/Multiplexer . 13
6.1.3.1 LLDP Parser state diagram . 14
6.1.3.1.1 LLDP Parser Function . 14
6.1.3.1.2 Constants . 14
6.1.3.1.3 Variables. 14
6.1.3.1.4 State diagram . 14
6.2 Link Aggregation operation.15
6.2.1 Principles of Link Aggregation. 15
6.2.2 Service interfaces. 16
6.2.3 Frame Collector . 17
6.2.3.1 Frame Collector state diagram. 17
6.2.3.1.1 Constants . 17
6.2.3.1.2 Variables. 17
6.2.3.1.3 Messages. 17
6.2.3.1.4 State diagram . 17
6.2.4 Frame Distributor. 18
6.2.4.1 Frame Distributor state diagram . 19
6.2.4.1.1 Variables. 19
6.2.4.1.2 Messages. 19
6.2.4.1.3 State diagram . 19
6.2.5 Marker Generator/Receiver (optional). 19
6.2.6 Marker Responder. 20
6.2.7 Protocol Parser/Multiplexer. 20
6.2.7.1 Protocol Parser state diagram . 20
6.2.7.1.1 Functions . 20
xi
ISO/IEC/IEEE 8802 1AX:2016(E)
6.2.7.1.2 Variables. 21
6.2.7.1.3 Messages. 21
6.2.7.1.4 State diagram . 21
6.2.8 Aggregator Parser/Multiplexer . 22
6.2.8.1 Aggregator Parser state diagram. 22
6.2.8.1.1 Constants . 22
6.2.8.1.2 Variables. 22
6.2.8.1.3 Messages. 23
6.2.8.1.4 State Diagram . 23
6.2.9 Aggregator . 24
6.2.10 Control Parser/Multiplexer . 24
6.2.10.1 Control Parser state diagram. 24
6.2.10.1.1 Control Parser Function. 24
6.2.10.1.2 Constants . 24
6.2.10.1.3 Variables. 25
6.2.11 Addressing . 25
6.2.11.1 Source address (SA). 25
6.2.11.2 Destination address . 25
6.3 Link Aggregation Control. 26
6.3.1 Characteristics of Link Aggregation Control. 27
6.3.2 System identification . 28
6.3.3 Aggregator identification. 28
6.3.4 Port identification . 28
6.3.5 Capability identification . 29
6.3.6 Link Aggregation Group identification . 30
6.3.6.1 Construction of the Link Aggregation Group Identifier. 30
6.3.6.2 Representation of the Link Aggregation Group Identifier. 31
6.3.7 Selecting a Link Aggregation Group . 31
6.3.8 Agreeing on a Link Aggregation Group . 32
6.3.9 Attaching a link to an Aggregator. 32
6.3.10 Signaling readiness to transfer user data. 32
6.3.11 Enabling the Frame Collector and Frame Distributor . 33
6.3.12 MAC_Operational status . 33
6.3.13 Monitoring the membership of a Link Aggregation Group. 33
6.3.14 Detaching a link from an Aggregator . 34
6.3.15 Configuration and administrative control of Link Aggregation . 34
6.3.16 Link Aggregation Control state information . 34
6.4 Link Aggregation Control Protocol . 35
6.4.1 LACP design elements. 35
6.4.2 LACPDU structure and encoding . 35
6.4.2.1 Transmission and representation of octets. 35
6.4.2.2 Encapsulation of LACPDUs in frames. 36
6.4.2.3 LACPDU structure . 36
6.4.2.4 Version 2 TLVs . 40
6.4.2.4.1 Port Algorithm TLV . 40
6.4.2.4.2 Port Conversation ID Digest TLV. 41
6.4.2.4.3 Port Conversation Mask TLVs . 41
6.4.2.4.4 Port Conversation Service Mapping TLV . 44
6.4.3 LACP state machine overview . 44
6.4.4 Constants. 46
6.4.5 Variables associated with the System. 46
6.4.6 Variables associated with each Aggregator . 47
6.4.7 Variables associated with each Aggregation Port. 48
6.4.8 Variables used for managing the operation of the state machines. 50
xii
ISO/IEC/IEEE 8802 1AX:2016(E)
6.4.9 Functions. 52
6.4.10 Timers .54
6.4.11 Messages. 54
6.4.12 Receive machine . 54
6.4.13 Periodic Transmission machine . 56
6.4.14 Selection Logic . 57
6.4.14.1 Selection Logic—Requirements . 58
6.4.14.2 Selection Logic—Recommended default operation . 59
6.4.15 Mux machine . 60
6.4.16 Transmit machine . 64
6.4.17 Churn Detection machines. 64
6.4.18 Long LACPDU machine . 65
6.5 Marker protocol . 67
6.5.1 Introduction. 67
6.5.2 Sequence of operations . 67
6.5.3 Marker and Marker Response PDU structure and encoding . 68
6.5.3.1 Transmission and representation of octets. 68
6.5.3.2 Encapsulation of Marker and Marker Response PDU in frames. 68
6.5.3.3 Marker and Marker Response PDU structure. 68
6.5.4 Protocol definition . 70
6.5.4.1 Operation of the marker protocol. 70
6.5.4.2 Marker Responder state diagram . 70
6.5.4.2.1 Variables. 70
6.5.4.2.2 Messages. 71
6.6 Conversation-sensitive frame collection and distribution . 71
6.6.1 Conversation-sensitive collection and distribution state diagrams. 72
6.6.1.1 Conversion-sensitive collection state diagram . 72
6.6.1.1.1 Variables. 72
6.6.1.1.2 Variables associated with each Aggregation Port . 73
6.6.1.1.3 Functions . 73
6.6.1.1.4 Messages. 73
6.6.1.1.5 State diagram . 73
6.6.2 Conversation-sensitive LACP state diagrams. 74
6.6.2.1 Per-Aggregator Variables . 74
6.6.2.2 Variables associated with each Aggregation Port. 76
6.6.2.3 Variables used for managing the operation of the state diagrams . 78
6.6.2.4 Functions. 78
6.6.2.5 Timers . 81
6.6.2.6 Messages. 81
6.6.2.7 State diagrams. 81
6.7 Configuration capabilities and restrictions . 87
6.7.1 Use of system and port priorities . 87
6.7.2 Dynamic allocation of operational Keys . 87
6.7.3 Link Aggregation on shared-medium links . 88
6.7.4 Selection Logic variants. 88
6.7.4.1 Reduced reconfiguration. 88
6.7.4.2 Limited Aggregator availability. 89
7. Management. 90
7.1 Overview. 90
7.1.1 Systems management overview. 90
7.1.2 Management model. 91
7.2 Managed objects . 91
xiii
ISO/IEC/IEEE 8802 1AX:2016(E)
7.2.1 Introduction. 91
7.2.2 Overview of managed objects. 92
7.2.2.1 Text description of managed objects . 92
7.2.3 Containment. 93
7.2.4 Naming. 93
7.2.5 Capabilities . 94
7.3 Management for Link Aggregation . 98
7.3.1 Aggregator managed object class . 98
7.3.1.1 Aggregator attributes . 99
7.3.1.1.1 aAggID . 99
7.3.1.1.2 aAggDescription. 99
7.3.1.1.3 aAggName . 100
7.3.1.1.4 aAggActorSystemID . 100
7.3.1.1.5 aAggActorSystemPriority . 100
7.3.1.1.6 aAggAggregateOrIndividual . 100
7.3.1.1.7 aAggActorAdminKey. 100
7.3.1.1.8 aAggActorOperKey. 101
7.3.1.1.9 aAggMACAddress . 101
7.3.1.1.10 aAggPartnerSystemID . 101
7.3.1.1.11 aAggPartnerSystemPriority . 101
7.3.1.1.12 aAggPartnerOperKey . 102
7.3.1.1.13 aAggAdminState . 102
7.3.1.1.14 aAggOperState. 102
7.3.1.1.15 aAggTimeOfLastOperChange. 102
7.3.1.1.16 aAggDataRate. 103
7.3.1.1.17 aAggOctetsTxOK . 103
7.3.1.1.18 aAggOctetsRxOK. 103
7.3.1.1.19 aAggFramesTxOK. 103
7.3.1.1.20 aAggFramesRxOK . 104
7.3.1.1.21 aAggMulticastFramesTxOK . 104
7.3.1.1.22 aAggMulticastFramesRxOK . 104
7.3.1.1.23 aAggBroadcastFramesTxOK. 104
7.3.1.1.24 aAggBroadcastFramesRxOK . 105
7.3.1.1.25 aAggFramesDiscardedOnTx . 105
7.3.1.1.26 aAggFramesDiscardedOnRx . 105
7.3.1.1.27 aAggFramesWithTxErrors . 105
7.3.1.1.28 aAggFramesWithRxErrors . 106
7.3.1.1.29 aAggUnknownProtocolFrames . 106
7.3.1.1.30 aAggPortList. 106
7.3.1.1.31 aAggLinkUpDownNotificationEnable. 106
7.3.1.1.32 aAggCollectorMaxDelay. 106
7.3.1.1.33 aAggPortAlgorithm . 107
7.3.1.1.34 aAggPartnerAdminPortAlgorithm. 107
7.3.1.1.35 aAggConversationAdminLink[]. 107
7.3.1.1.36 aAggPartnerAdminPortConversationListDigest . 107
7.3.1.1.37 aAggAdminDiscardWrongConversation. 108
7.3.1.1.38 aAggAdminServiceConversationMap[] . 108
7.3.1.1.39 aAggPartnerAdminConvServiceMappingDigest . 108
7.3.1.2 Aggregator Notifications . 108
7.3.1.2.1 nAggLinkUpNotification. 108
7.3.1.2.2 nAggLinkDownNotification. 109
7.3.2 Aggregation Port managed object class. 109
7.3.2.1 Aggregation Port Attributes. 109
7.3.2.1.1 aAggPortID. 109
xiv
ISO/IEC/IEEE 8802 1AX:2016(E)
7.3.2.1.2 aAggPortActorSystemPriority. 109
7.3.2.1.3 aAggPortActorSystemID. 109
7.3.2.1.4 aAggPortActorAdminKey . 110
7.3.2.1.5 aAggPortActorOperKey . 110
7.3.2.1.6 aAggPortPartnerAdminSystemPriority . 110
7.3.2.1.7 aAggPortPartnerOperSystemPriority . 110
7.3.2.1.8 aAggPortPartnerAdminSystemID . 110
7.3.2.1.9 aAggPortPartnerOperSys
...