CTR 8500-8300 3.7.0 LA Configuration - December2018

CTR 8500-8300
LA Configuration
Version 3.7.0
260-668457-001
Build 42.5860
LA CONFIGURATION
Copyright & Terms of Use

December 2018
This documentation incorporates features and functions provided with CTR 8500-8300 LA
Configuration, version 3.7.0.
Copyright © 2018 by Aviat Networks, Inc.

All rights reserved.
No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval
system, or translated into any language or computer language, in any form or by any means,
electronic, magnetic, optical, chemical, manual, or otherwise, without the prior written
permission of Aviat Networks Inc.
To request permission, contact techpubs@aviatnet.com.
Warranty
Aviat Networks makes no representation or warranties with respect to the contents hereof
and specifically disclaims any implied warranties or merchantability or fitness for any
particular purpose.
Further, Aviat Networks reserves the right to revise this publication and to make changes
from time to time in the content hereof without obligation of Aviat Networks to notify any
person of such revision or changes.
Safety Recommendations
The following safety recommendations must be considered to avoid injuries to persons
and/or damage to the equipment:
1. Installation and Service Personnel: Installation and service must be carried out by
authorized personnel who have the technical training and experience necessary to be
aware of any hazardous operations during installation and service, and of measures to
avoid any danger to themselves, to any other personnel, and to the equipment.
2. Access to the Equipment: Access to the equipment in use must be restricted to service
personnel only.
3. Safety Norms: Recommended safety norms are detailed in the Health and Safety
sections of the Eclipse User Manual.
4. Service Personnel Skill: Service personnel must have received adequate technical
training on telecommunications and in particular on the equipment and capabilities this
addendum refers to.
Trademarks
All trademarks are the property of their respective owners.
260-668457-001 DECEMBER 2018 III

LA CONFIGURATION
IV AVIAT NETWORKS
LA CONFIGURATION
Aviat NetworksTechnical Support

Service and Technical Support:
For customer service and technical support, contact one of the regional Technical Help
Desks listed below.
Americas Technical Help Desk EMEA Technical Help Desk Asia Pacific Technical Help Desk
Aviat Networks, Inc. Aviat Networks Aviat Networks
San Antonio, TX Blantyre, Glasgow, Scotland Clark Freeport Zone
U.S.A. G72 0FB Philippines 2023
United Kingdom
Phone:+1 210 526 6345 Phone: +1 210 526 6345 Phone: +1 210 526 6345
Toll Free (USA): Fax: Fax: +63 45 599 5196
+1 800 227 8332 +44 16 9871 7204 (English)
Fax:+1 210 526 6315 +33 1 5552 8012 (French)
Email: TAC.AM@aviatnet.com Email: TAC.EMEA@aviatnet.com Email: TAC.APAC@aviatnet.com
Global Support Hotline: +1 210 526 6345

Call this phone number for support from anywhere in the world. Aviat Networks' Global
Support Hotline is available 24 hours a day, 7 days a week, providing uninterrupted support
for all our customers.
When you call our Global Support Hotline:
l You will be greeted by an automated response that will ask you for your PIN#.
Request a PIN# here: http://aviatnetworks.com/contact-us/technical-
assistance/pin-request-form/.
l As soon as you enter your PIN#, you will be transferred to our Global Technical
Helpdesk that will assist you with your technical issue.
l If you do not have a PIN# your call will be answered by our Support Assurance
Desk. Your call will be supported and prioritized accordingly.
Or you can contact your local Aviat Networks office. Contact information is available on our
website at: http://www.aviatnetworks.com/services/customer-support/technical-
assistance/
260-668457-001 DECEMBER 2018 V

LA CONFIGURATION
Sales and Sales Support:

For sales information, contact one of the Aviat Networksheadquarters, or find your regional
sales office at: HTTP://WWW.AVIATNETWORKS.COM/.
Corporate Headquarters International Headquarters

California, USA Singapore
Aviat Networks, Inc. Aviat Networks (S) Pte. Ltd.
860 N. McCarthy Blvd., Suite 200 51 Changi Business Park Central 2
Milpitas, CA 95035 #04-10 The Signature
U.S.A. Singapore 486066
Phone: + 1 408 941 7100 Phone: + 65 6496 0900

Fax: + 1 408 941 7110 Fax: + 65 6496 0999>
Toll Free for Sales Inquiries: Sales Inquiries:
+ 1 888 478 9669 +1-321-674-4252
VI AVIAT NETWORKS
LA CONFIGURATION
Product Compliance Notes

CTR 8540, CTR 8312, CTR 8311, and CTR 8380 have been tested for and meet all applicable
EMC standards. The equipment was tested using screened cable; if any other type of cable is
used, it may violate EMC compliance.
CTR 8540, CTR 8312, CTR 8311, and CTR 8380 are Class A products. In a domestic
environment these products may cause radio interference in which case the user may be
required to take adequate measures. This equipment is intended to be used exclusively in
telecommunications centers.
Regulatory Information for 5.8 GHz Band

ODU 600
The following regulatory information applies to license-free operation on the 5.8 GHz band of
ODU 600.
FCC Notices
l ODU 600, 5.8GHz, must be professionally installed and maintained.
l This equipment has been tested and found to comply with the limits for a Class A
digital device, pursuant to Part 15 of the FCC rules. These limits are designed to
provide reasonable protection against harmful interference when the equipment
is operated in a commercial environment. This equipment generates, uses and
can radiate radio frequency energy and, if not installed and used in accordance
with the instruction manual, may cause harmful interference to radio
communications. Operation of this equipment in a residential environment is
likely to cause harmful interference in which case the user will be required to
correct the interference at their own expense.
l ODU 600, 5.8GHz, is compliant with the relevant parts of FCC CFR47, Part
15.407.
l To ensure compliance with the FCC RF exposure requirements, a minimum
distance of 18 meters must be maintained between the antenna and any persons
whilst the unit is operational. This calculation is based on the maximum
conducted power and maximum antenna gain.
l ODU 600, 5.8GHz, has been certified for use with a parabolic antenna with a
maximum gain of 45.9dBi or a flat panel antenna with a maximum gain of 28dBi.
l The filters and software provided with this product allow for transmission only in
the frequency range 5725 – 5850 MHz to ensure compliance with Part 15.407.
l According to the conducted power limit in FCC CFR 47, Part 15.407, the power for
this device has been limited to 1W (30dBm) at the antenna port.
260-668457-001 DECEMBER 2018 VII

LA CONFIGURATION
l FCC CFR47, Part 15.407 excludes the use of point-to-multipoint systems,

omnidirectional applications and multiple co-located intentional radiators. This
system is only for fixed, point-to-point operation.
International Use of 5.8 GHz

ODU 600 with CTR 8540, CTR 8312, CTR 8311, or CTR 8380, 5.8 GHz, does not employ DFS,
and as such the equipment cannot be deployed within Europe or any country where DFS is a
regulatory requirement for protection of radars.
Networking Devices in Electric Power Substations

For IEEE 1613 compliant products, category 7 Ethernet cables must be used in order to
ensure compliance.
WEEE Directive
In accordance with the WEEE Directive (2012/19/EU), CTR 8540, CTR 8312, CTR 8311, and
CTR 8380 is marked with the following symbol:
This symbol indicates that this equipment should be collected separately for the purposes of
recovery and/or recycling.
For information about collection and recycling of Aviat Networks equipment please contact
your local Aviat Networks sales office. If you purchased your product via a distributor please
contact the distributor for information regarding collection and recovery/recycling.
More information on the WEEE Directive is available at our website:
http://www.aviatnetworks.com/products/compliance/weee/.
(WEEE is the acronym for Waste Electrical and Electronic Equipment)
RoHS Directive
CTR 8540, CTR 8312, CTR 8311, and CTR 8380 meets the requirements of ROHS directive
2011/65/EU.
VIII AVIAT NETWORKS

LA CONFIGURATION
Declaration of Conformity, Radio Equipment Directive

(RED), 2014/53/EU
С настоящото Aviat Networks декларира, че този тип

радиосъоръжение ODU 600/ODU 600sp with CTR 8311, CTR 8312, CTR
Bulgaria 8380, CTR 8540 е в съответствие с Директива 2014/53/ЕС.
Цялостният текст на ЕС декларацията за съответствие може да се
намери на следния интернет адрес: www.aviatnetworks.com
Tímto Aviat Networks prohlašuje, že typ rádiového zařízení ODU

600/ODU 600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540 je v
Czech Republic souladu se směrnicí 2014/53/EU. Úplné znění EU prohlášení o shodě je
k dispozici na této internetové adrese: www.aviatnetworks.com
Hermed erklærer Aviat Networks, at radioudstyrstypen ODU 600/ODU

600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540 er i
Denmark overensstemmelse med direktiv 2014/53/EU. EU-
overensstemmelseserklæringens fulde tekst kan findes på følgende
internetadresse: www.aviatnetworks.com
Hiermit erklärt Aviat Networks, dass der Funkanlagentyp ODU 600/ODU

600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540 der Richtlinie
Germany Austria Switzerland Belgium 2014/53/EU entspricht. Der vollständige Text der EU-
Konformitätserklärung ist unter der folgenden Internetadresse
verfügbar: www.aviatnetworks.com
Luxembourg Netherlands Liechtenstein
Käesolevaga deklareerib Aviat Networks, et käesolev raadioseadme
tüüp ODU 600/ODU 600sp with CTR 8311, CTR 8312, CTR 8380, CTR
Estonia 8540 vastab direktiivi 2014/53/EL nõuetele. ELi vastavusdeklaratsiooni
täielik tekst on kättesaadav järgmisel internetiaadressil:
www.aviatnetworks.com
Hereby, Aviat Networks declares that the radio equipment type ODU
600/ODU 600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540 is in
United Kingdom Ireland Malta compliance with Directive 2014/53/EU. The full text of the EU
declaration of conformity is available at the following internet address:
Por la presente, Aviat Networks declara que el tipo de equipo
radioeléctrico ODU 600/ODU 600sp with CTR 8311, CTR 8312, CTR
Spain 8380, CTR 8540 es conforme con la Directiva 2014/53/UE. El texto
completo de la declaración UE de conformidad está disponible en la
dirección Internet siguiente: www.aviatnetworks.com
Με την παρούσα ο/η Aviat Networks, δηλώνει ότι ο ραδιοεξοπλισμός

ODU 600/ODU 600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540
πληροί την οδηγία 2014/53/ΕΕ. Το πλήρες κείμενο της δήλωσης
Greece Cyprus
συμμόρφωσης ΕΕ διατίθεται στην ακόλουθη ιστοσελίδα στο διαδίκτυο:
Le soussigné, Aviat Networks, déclare que l'équipement
radioélectrique du type ODU 600/ODU 600sp with CTR 8311, CTR 8312,
France Luxembourg Switzerland Belgium CTR 8380, CTR 8540 est conforme à la directive 2014/53/UE. Le texte
complet de la déclaration UE de conformité est disponible à l'adresse
internet suivante: www.aviatnetworks.com
260-668457-001 DECEMBER 2018 IX

LA CONFIGURATION
Il fabbricante, Aviat Networks, dichiara che il tipo di apparecchiatura

radio ODU 600/ODU 600sp with CTR 8311, CTR 8312, CTR 8380, CTR
Italy Switzerland 8540 è conforme alla direttiva 2014/53/UE. Il testo completo della
dichiarazione di conformità UE è disponibile al seguente indirizzo
Internet: www.aviatnetworks.com
Ar šo Aviat Networks deklarē, ka radioiekārta ODU 600/ODU 600sp

with CTR 8311, CTR 8312, CTR 8380, CTR 8540 atbilst Direktīvai
Latvia 2014/53/ES. Pilns ES atbilstības deklarācijas teksts ir pieejams šādā
interneta vietnē: www.aviatnetworks.com
Aš, Aviat Networks, patvirtinu, kad radijo įrenginių tipas ODU 600/ODU
600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540 atitinka
Lithuania Direktyvą 2014/53/ES. Visas ES atitikties deklaracijos tekstas
prieinamas šiuo interneto adresu: www.aviatnetworks.com
Hierbij verklaar ik, Aviat Networks, dat het type radioapparatuur ODU
600/ODU 600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540
Netherlands Belgium conform is met Richtlijn 2014/53/EU. De volledige tekst van de EU-
conformiteitsverklaring kan worden geraadpleegd op het volgende
internetadres: www.aviatnetworks.com
Aviat Networks ovime izjavljuje da je radijska oprema tipa ODU

600/ODU 600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540 u
Croatia skladu s Direktivom 2014/53/EU. Cjeloviti tekst EU izjave o sukladnosti
dostupan je na sljedećoj internetskoj adresi:
B'dan, Aviat Networks, niddikjara li dan it-tip ta' tagħmir tar-radju
Malta huwa konformi mad-Direttiva 2014/53/UE. It-test kollu tad-
dikjarazzjoni ta' konformità tal-UE huwa disponibbli f'dan l-indirizz tal-
Internet li ġej: www.aviatnetworks.com
Aviat Networks igazolja, hogy a ODU 600/ODU 600sp with CTR 8311,
CTR 8312, CTR 8380, CTR 8540 típusú rádióberendezés megfelel a
Hungary 2014/53/EU irányelvnek. Az EU-megfelelőségi nyilatkozat teljes
szövege elérhető a következő internetes címen:
Aviat Networks niniejszym oświadcza, że typ urządzenia radiowego
Poland jest zgodny z dyrektywą 2014/53/UE. Pełny tekst deklaracji zgodności
UE jest dostępny pod następującym adresem internetowym:
O(a) abaixo assinado(a) Aviat Networks declara que o presente tipo de
equipamento de rádio ODU 600/ODU 600sp with CTR 8311, CTR 8312,
Portugal CTR 8380, CTR 8540 está em conformidade com a Diretiva 2014/53/UE.
O texto integral da declaração de conformidade está disponível no
seguinte endereço de Internet: www.aviatnetworks.com
Aviat Networks potrjuje, da je tip radijske opreme ODU 600/ODU 600sp

with CTR 8311, CTR 8312, CTR 8380, CTR 8540 skladen z Direktivo
Slovenia 2014/53/EU. Celotno besedilo izjave EU o skladnosti je na voljo na
naslednjem spletnem naslovu: www.aviatnetworks.com
X AVIAT NETWORKS
LA CONFIGURATION
Aviat Networks týmto vyhlasuje, že rádiové zariadenie typu ODU

600/ODU 600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540 je v
Slovakia súlade so smernicou 2014/53/EÚ. Úplné EÚ vyhlásenie o zhode je k
dispozícii na tejto internetovej adrese: www.aviatnetworks.com
Aviat Networks vakuuttaa, että radiolaitetyyppi ODU 600/ODU 600sp

with CTR 8311, CTR 8312, CTR 8380, CTR 8540 on direktiivin
Finland 2014/53/EU mukainen. EU-vaatimustenmukaisuusvakuutuksen
täysimittainen teksti on saatavilla seuraavassa internetosoitteessa:
Härmed försäkrar Aviat Networks att denna typ av radioutrustning ODU
600/ODU 600sp with CTR 8311, CTR 8312, CTR 8380, CTR 8540
Sweden överensstämmer med direktiv 2014/53/EU. Den fullständiga texten till
EU-försäkran om överensstämmelse finns på följande webbadress:
Hér með lýsir Aviat Networks yfir því aðODU 600/ODU 600sp with CTR
8311, CTR 8312, CTR 8380, CTR 8540 er í samræmi við grunnkröfur og
aðrar kröfur, sem gerðar eru í tilskipun 2014/53/EU.
Iceland
Aviat Networks erklærer herved at utstyret ODU 600/ODU 600sp with
CTR 8311, CTR 8312, CTR 8380, CTR 8540 er i samsvar med de
grunnleggende krav og øvrige relevante krav i direktiv 2014/53/EU.
Norway
Prin prezenta, Aviat Networks declară că tipul de echipamente radio
România este în conformitate cu Directiva 2014/53/UE. Textul integral al
declarației UE de conformitate este disponibil la următoarea adresă
internet: www.aviatnetworks.com
Full declarations of conformity are available at:

http://aviatnetworks.com/doc/ODU600CTR8311CTR8312.pdf
http://aviatnetworks.com/doc/ODU600CTR8380.pdf
http://aviatnetworks.com/doc/ODU600CTR8540.pdf
http://aviatnetworks.com/doc/ODU600spCTR8311CTR8312.pdf
http://aviatnetworks.com/doc/ODU600spCTR8380.pdf
http://aviatnetworks.com/doc/ODU600spCTR8540.pdf
Country Availability Matrix

Aviat’s radios are classified under the Radio Equipment Directive (2014/53/EU) as Class 2
products. For details of where the equipment is intended to be used, see the country matrix
below. Aviat Networks intends to market this equipment where a cross (X) is shown.
Band (GHz) L6 U6 07 08 10 11 13 15 18 23 26 28 32 38 42
Austria X X X X X X X X X X X X X X X
Belgium X X X X X X X X X X X X X
Bulgaria X X X X X X X X X X X X X
Croatia X X X X X X X X X X X X X
260-668457-001 DECEMBER 2018 XI

LA CONFIGURATION
Cyprus X X X X X X X X X X X X X X
Czech Republic X X X X X X X X X X X
Denmark X X X X X X X X X X X X
Estonia X X X X X X X X X X X X X X X
Finland X X X X X X X X X X X X X X
France X X X X X X X X X X X X X X
Germany X X X X X X X X X X X X X X X
Greece X X X X X X X X
Hungary X X X X X X X X X X X
Iceland X X X X X X X X X X X X X
Ireland X X X X X X X X X X X
Italy X X X X X X X X X X X X X
Latvia X X X X X X X X X X X
Lithuania X X X X X X X X X X X X X X
Luxembourg X X X X X X X X X X X X X
Malta X X X X X X X X X X X X X
Netherlands X X X X X X X X X X X
Norway X X X X X X X X X X X X X
Poland X X X X X X X X X X X X X X
Portugal X X X X X X X X X X X X
Romania X X X X X X X X X X X X X X X
Slovak Republic X X X X X X X X X X X X X
Slovenia X X X X X X X X X X X X X X
Spain X X X X X X X X X X X X
Sweden X X X X X X X X X X X
Switzerland X X X X X X X X X X X X X X
United Kingdom X X X X X X X X X X X X X
IT SHOULD BE NOTED THAT A LICENSE TO OPERATE THIS EQUIPMENT WILL BE

REQUIRED AND THE RELEVANT REGULATOR MUST BE CONTACTED PRIOR TO
INSTALLATION AND COMMISSIONING.
XII AVIAT NETWORKS

LA CONFIGURATION
Conventions and Terminology

This document uses the following conventions and terminology.
Graphic Cues
The following items have graphic cues to identify important supporting information.
N O TE: A no te item identifies additional information about a procedure or
func tion.
CAUTION: A caution item identifies important information pertaining to actions that may
cause damage to equipment, loss of data, or corruption of files.
WARNING: A warning item identifies a serious physical danger or major possible problem.
Font Changes
Bold font is used for the names of on-screen elements such as; fields, buttons, and drop-
down selection lists, keywords, commands and for keys on the keyboard.
Courier font in blue text is used to indicate commands that the user needs to type in.
WTM4100# show radio-carrier status Carrier1/1
Any responses or report output from a command is shown as brown text and indented.
radio-carrier status Carrier1/1
oper-status up
Italic font is used to emphasize words and phrases, to introduce new terms, and for the titles
of printed publications.
Common Terminology
Click or Select: Point the mouse pointer at the item you want to select, then quickly press and
release the left mouse button.
Right-Click: Point the mouse pointer at the item you want to select, then quickly press and
release the right mouse button.
260-668457-001 DECEMBER 2018 XIII

LA CONFIGURATION
Contents
Copyright & Terms of Use iii

Aviat NetworksTechnical Support v
Product Compliance Notes vii
Regulatory Information for 5.8 GHz Band vii
Networking Devices in Electric Power Substations viii
WEEE Directive viii
RoHS Directive viii
Declaration of Conformity, Radio Equipment Directive (RED), 2014/53/EU ix
Conventions and Terminology xiii
Contents xiv
CHAPTER 1. INTRODUCTION 15
Purpose and Scope 15
Acronyms 15
References 15
General Configurations 15
Protocol Description 17
CHAPTER 2. CONFIGURING LINK AGGREGATION 19

Configuration Requirements 20
Default Configurations 20
Port and Aggregation States 20
Enabling Link Aggregation 21
Enabling Independent Mode 23
Configuring Port-channel Interfaces 24
Configuring LACP Port-Priority 27
Configuring LACP System Priority 33
Configuring Port-channel Load Balance 39
Configuring LACP System Identifier 40
Configuring LACP Port Identifier 42
MTU Configurations 45
Configuring LACP Wait Time 49
Configuring LACP Time-out 50
Displaying LACP Status 51
CHAPTER 3. INTERACTION BETWEEN LA AND VLAN 53

Examples 53
CHAPTER 4. DYNAMIC AGGREGATOR CONFIGURATION 57

Configurations 58
XIV AVIAT NETWORKS

LA INTRODUCTION CHAPTER 1
Chapter 1. Introduction
Purpose and Scope

The Aviat Networks LA product allows one or more links to be aggregated together to form
a Link Aggregation (LA) Group as if it were a single link. This supports the establishment of
logical links which consist of ‘n’ number of parallel, full-duplex, point-to-point links
operating at the same data rate.
This document explains the configurations for Aviat Networks LA running as a part of Aviat
Networks CTR 8500 and 8300. The reader is expected to have a basic knowledge of the LA
protocol as a pre-requisite.
N O TE: LA is c urrently not s upported for the C TR 8300 produc t. This
doc ument only applies to the C TR 8540 doc ument.
Acronyms
Table 1. Acronyms used in this document
Acronym Expansion
CLI Command Line Interface
ISS Intelligent Switch Solutions
LA Link Aggregation
LACP Link Aggregation Control Protocol
MAC Media Access Control
MI Multiple Instance
MIB Management Information Base
PDU Protocol Data Unit
SNMP Simple Network Management Protocol
MTU Maximum Transmission Unit
References
l CTR 8500-8300 CLI Commands Guides
General Configurations
The following table provides the access and exit methods to various general configuration
modes.
AVIAT NETWORKS DECEMBER 2018 15

CHAPTER 1 LA INTRODUCTION
Table 2. General Configurations

Command Mode Access Method Prompt Exit method
User EXEC This is the initial mode to start a aos> The logout method is used.
session.
Privileged EXEC Use the enable command to aos# Use the command disable to
enter the Privileged EXEC mode. return from the Privileged
EXEC mode to User EXEC
mode, the disable command
is used.
Global Enter Privileged EXEC mode and aos(config)# Use the command exit to log
Configuration use the command configure out of the Global
terminal to enter the Global Configuration Mode, and the
Configuration Mode. command end to log out of
the Privileged EXEC mode.
Interface In Global Configuration Mode, aos(config-if)# Use the command exit to log
Configuration use the command command out of the Global
interface <interface- Configuration Mode, and the
type><interface-id>to enter the command end to log out of
Interface Configuration Mode. the Privileged EXEC mode.
16 DECEMBER 2018 AVIAT NETWORKS

LA INTRODUCTION CHAPTER 1
Protocol Description
Link Aggregation allows aggregation of point-to-point links operating at the same data rate.
Link Aggregation is supported only on point-to-point links with MAC clients operating in full
duplex mode.
A MAC client communicates with a set of ports through an Aggregator, which presents a
standard IEEE 802.3 service interface to the MAC client. The Aggregator binds to one or
more ports within a system.
LACP (Link Aggregation Control Protocol) is used for automatic communication of
aggregation capabilities and automatic configuration of Link Aggregation between systems.
The list of ports that are aggregated to a particular aggregator is transparent to the higher
modules (such as Spanning Tree).
Link Aggregation features include:
l Load sharing
l Increased availability
l Increased bandwidth
l Linear incremental bandwidth
l Low risk of duplication or mis-ordering
Upon Link Aggregation, individual point-to-point ports/interfaces are aggregated into a

group that is regarded as a single port/interface by the higher layers such as Spanning-tree.
The total capacity of such an aggregated group is the sum of the capacities of the individual
links composing the aggregate, thus providing higher bandwidth to the MAC client (such as
Spanning Tree). As shown in the figure below, multiple links on the server side of the switch
are aggregated together to form a single link.
LA is responsible for taking frames from the aggregator and submitting them for
transmission on the appropriate port. The physical port for transmission is chosen based on
the selection policy in the chipset. LA is responsible for collecting the frames received on
various ports of the aggregator.
The user can configure a specific distribution policy for the traffic flow based on the
deployment scenario. This allows the switches to get the advantage of increased bandwidth
for the traffic between the hosts and the server. Also, if one of the links in the aggregation
group is down for maintenance purposes, it will not affect the traffic between the hosts and
the server.

CHAPTER 1 LA INTRODUCTION
Figure 1. Link Aggregation - Example

CONFIGURING LINK AGGREGATION CHAPTER 2
Chapter 2. Configuring Link Aggregation

The following sections describe the configuration of Aviat Networks LA running as a part of
Aviat Networks AOS.
Figure 2. Link Aggregation - Topology 1. By default Aviat Networks CTR 8540 supports a minimum
of 1 port to a maximum of 8 ports per aggregation.
N O TE: For data on c onfiguring ports , radio, L1LA, protection, and POE ports,
see other C TR family doc umentation, inc luding the Gettin g S tarted Gu ide and
the CL I Referen ce.

CHAPTER 2 CONFIGURING LINK AGGREGATION
Configuration Requirements
LA configuration requirements are as follows:
l Port-channel must be enabled in the system for Link aggregation configuration to
take effect.
l If 802.1x is enabled on a port, then Link Aggregation can be enabled on that port
only when the port is in the authorized state. Link Aggregation cannot be enabled
on unauthorized ports.
Default Configurations
Table 3. Default Configurations
Feature Default Setting

Port-channel Disabled
Channel-groups None
LACP System Priority 0x8000 or 32768
Load balancing Source and Destination MAC
address based.
LACP Port Priority 128 on all interfaces.
LACP Wait time 2
MAC-selection Dynamic: Port-channel MAC
address is address of an active port
Port and Aggregation States

These values describe the LACP port state according to IEEE 802.1AX-2008 LACP Standard:
Table 4. Aggregation States
State Settings
LACP Activity Encoded in bit 0. Activity control value with regard to this link. Active
LACP is encoded as a 1; Passive LACP is encoded as a 0.
LACP timeout Encoded in bit 1. Timeout control value for this link. Short Timeout is
encoded as a 1; Long Timeout is encoded as a 0.
The long timeout value means that LACP PDU will be sent every 30
seconds and LACP timeout value (no packet is received from peer) is 90
seconds

State Settings
Aggregation Encoded in bit 2.
l TRUE (encoded as a 1) - Link is a potential candidate for
aggregation.
l FALSE (encoded as a 0) - Link is Individual; i.e., can be operated
only as an individual link.
Synchronization Encoded in bit 3.

l FALSE (encoded as a 0) - Link is OUT_OF_SYNC, i.e, in the
incorrect Aggregation.
l TRUE (encoded as a 1) - Link is IN_SYNC; i.e., it has been allocated
to the correct Link Aggregation Group, the group has been
associated with a compatible Aggregator, and the identity of the
Link Aggregation Group is consistent with the System ID and
operational Key information transmitted.
Collecting Encoded in bit 4.
l TRUE (encoded as a 1) - Collection of incoming frames on this link
is currently enabled and is not expected to be disabled in the
absence of administrative changes or changes in received protocol
information.
l Its value is otherwise FALSE (encoded as a 0).
Distributing Encoded in bit 5.
l FALSE (encoded as a 0) - Distribution of outgoing frames on this
link is currently disabled and is not expected to be enabled in the
absence of administrative changes or changes in received protocol
information.
l Its value is otherwise TRUE (encoded as a 1).
Defaulted Encoded in bit 6.
l TRUE (encoded as a 1), this flag indicates that the Actor’s Receive
machine is using Defaulted operational Partner information,
administratively configured for the Partner.
l FALSE (encoded as a 0) - The operational Partner information in
use has been received in a LACPDU.
Expired Encoded in bit 7.
l TRUE (encoded as a 1) - Actor’s Receive machine is in the
EXPIRED state.
l FALSE (encoded as a 0) - Actor’s Receive machine is not in the
EXPIRED state.
Enabling Link Aggregation

N O TE: Link Aggregation is dis abled by default.
Execute the following commands in both the switches to enable Link Aggregation.
1. Enter the Global Configuration mode.

aos# configure terminal

2. Enable port channel.
aos(config)# set port-channel enable
3. Exit from the Global configuration mode.
aos(config)# end
4. View the etherchannel information using the following command.
A sample result is:
aos# show etherchannel summary
Port-channel Module Admin Status is enabled
Port-channel Module Oper Status is enabled
Port-channel Independent mode is disabled
Port-channel System Identifier is 00:01:02:03:04:05
LACP System Priority: 32768
N O TE: The follow ing c ommand is us ed to s hut dow n the entire LA module
aos(config)# shutdown port-channel

Enabling Independent Mode

N O TE: Independent mode is dis abled by default.
Execute the following commands in both the switches to enable Independent mode.
aos(config)# set port-channel independentmode enable
aos(config)# end
aos# show etherchannel summary
The output in Switch A and Switch B is,
Port-channel Independent mode is enabled
aos# show etherchannel detail
The output in Switch A and Switch B is,
Port-channel Independent mode is enabled
N O TE: The c ommand us ed to dis able independent feature in the sw itch is :
aos(config)# set port-channel independentmode disable
CAUTION: Independent mode feature can be verified by enabling this feature on both Actor
and Partner sides. If it is enabled on either of the sides, this will end up in inconsistent
behavior. Avoid this.

Configuring Port-channel Interfaces

Port 3 of both the switches are configured to be a part of the link aggregation.
If the port-channel interface is not present, then it must be created using the following
commands:
aos(config)# interface port-channel 1
aos(config-if)# no shut
aos(config-if)# map switch default
aos(config-if)# end
N O TE: The LAC P feature c an be v erified by enabling LA (c an be either
Ac tive/Pas s iv e) on both Ac tor and Partner s ides. If LAC P is enabled on
Ac tor side and manual on partner s ide or v ic e v ersa, it w ill end up in
inc ons is tent behav ior, henc e this mis -c onfiguration should be avoided.
Execute the following commands in both the switches.
1. Enter the Global configuration mode.
3. Create port channel.
aos(config-if)# no shutdown
aos(config-if)# map switch default
4. Enter the Interface configuration mode.
Up to eight interfaces of the same type and speed can be configured for the same group.
aos(config)# interface gigabitethernet 0/3
5. Configure the physical port in a port channel and specify the mode by which the port
becomes part of the port-channel.
The channel-group-number ranges from 1 to 64. Each port-channel can have up to eight
compatibly configured Ethernet interfaces.
aos(config-if)# channel-group 1 mode active
Mode can be
n active: LACP negotiation is started un-conditionally.
n passive: LACP negotiation is started only when an LACP packet is received from
the peer.
n on: Force the interface to be a part of the port channel without communicating
through the LACP protocol. This is equivalent to manual aggregation.

6. Exit from the Interface configuration mode.

aos(config-if)# end
aos# show etherchannel 1 detail
The output in Switch A is

Channel Group Listing
---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/3
-------------
Port State = Up in Bundle

Channel Group : 1
Mode : Active
Pseudo port-channel = Po1
LACP port-priority = 128
LACP Wait-time = 2 secs
LACP Port Identifier = 3
LACP Activity : Active
LACP Timeout : Long
Aggregation State: Aggregation, Sync, Collecting, Distributing,
LACP Port Admin Oper Port Port

Port State Priority Key Key Number State
------------------------------------------------------
Gi0/3 Bundle 128 1 1 0x3 0xa0
Port-channel : Po1
-------------------
Number of Ports = 1
HotStandBy port = null
Port state = Port-channel Ag-Inuse
Protocol = LACP
MAC selection = Dynamic
The output in Switch B is,
---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/3
-------------


Channel Group : 1
Mode : Active
LACP Timeout : Long
Aggregation State : Aggregation, Sync, Collecting, Distributing,

------------------------------------------------------
Gi0/3 Bundle 128 1 1 0x3 0xa0
Port-channel : Po1
-------------------
Number of Ports = 1
Protocol = LACP

Configuring LACP Port-Priority

Ports 1, 2 and 3 are part of link aggregation. All ports in both the switches are configured to
belong to port-channel 1.
1. Execute the following commands in both the switches.
aos(config) # set port-channel enable
aos(config-if)# exit
aos(config-if)# end
The output in Switch A is,

---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group

------------------
Port: Gi0/1
-------------
Channel Group : 1

Mode : Active
LACP Timeout : Long
Port : Gi0/2
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Port : Gi0/3
-------------
Port State = Hot standby
Channel Group : 1
Mode : Active
LACP Timeout : Long
Aggregation State : Aggregation,
------------------------------------------------------
Gi0/1 Bundle 128 1 1 0x1 0xbc
Gi0/3 Standby 128 1 1 0x3 0xa0
Port-channel : Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP

---------------------
Group: 1
----------
Protocol :LACP

Ports in the Group

------------------
Port : Gi0/1
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long

Port : Gi0/2
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long

Port : Gi0/3
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
------------------------------------------------------
Port-channel: Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP
N O TE: Obs erv ation before c onfiguring the LAC P port priority:Port
GigabitEthernet 0/3 is the Standby port in Sw itc hes A and B. (as max ports
in the port c hannel is 2 ports )
Execute the following commands in Switch A.


2. Enter the Interface Configuration mode.
3. Execute the following command to configure the LACP Port Priority.
The range of values is from 0-65535. The lower the value, the more likely that the
interface will be used for LACP transmission.
aos(config-if)# lacp port-priority 20

4. To return to the default port-priority configuration for the interface use the command
aos(config-if)# no lacp port-priority.
5. Exit from the Interface Configuration mode.
aos(config-if)# end
6. View the Etherchannel information using the following command.

---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Port : Gi0/2
-------------
Channel Group : 1
Mode : Active

LACP Timeout : Long

Port : Gi0/3
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long

------------------------------------------------------
Gi0/2 Standby 128 1 1 0x2 0xbc
Gi0/3 Bundle 20 1 1 0x3 0xa0
Port-channel : Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP

---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Aggregation State: Aggregation, Sync, Collecting, Distributing,

Port : Gi0/2
-------------
Channel Group : 1
Mode : Active


LACP Timeout : Long
Port : Gi0/3
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long

------------------------------------------------------
Gi0/2 Standby 128 1 1 0x2 0xbc
Gi0/3 Bundle 128 1 1 0x3 0xa0
Port-channel : Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP
N O TE: Obs erv ation after c onfiguring the LAC P port priority:
Port 2 is the Standby port in Sw itc hes A and B.

Configuring LACP System Priority

Ports 1, 2 and 3 are part of link aggregation. All ports in both the switches are configured to
belong to port-channel 1.
1. Execute the following commands in both the switches.
aos(config) # set port-channel enable
iss(coning-if)# exit
aos(config-if)# end

---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
Channel Group : 1
Mode : Active


LACP Timeout : Long
Port : Gi0/2
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Port : Gi0/3
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long

------------------------------------------------------
Port-channel : Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP

---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------

Channel Group : 1
Mode : Active
LACP Timeout : Long
Port : Gi0/2
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Port : Gi0/3
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Aggregation State : Aggregation
-----------------------------------------------------
Port-channel : Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP
N O TE: Obs erv ation before c onfiguring the LAC P sys tem priority:
Port Gigabitethernet 0/3 in s w itc h A and B are standby ports .
Execute the following commands in Switch B.
2. Set the LACP System priority.

The priority value ranges from 0 to 65535. The lower the value, the higher the system
priority. The switch with the lower system priority value determines the links between
the LACP partner switches that are in active and standby states for each LACP port-
channel.
aos(config)# lacp system-priority 20

3. Execute the following command to configure the LACP Port Priority, for Port 3 in
Switch A.
aos(config-if)# lacp port-priority 20
4. Exit from the configuration mode.
aos(config-if)# end

---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Port : Gi0/2
-------------
Port State = Up in BundleChannel Group : 1
Mode : Active
LACP Timeout : Long
Port : Gi0/3

-------------
Port State = Hot stanby
Channel Group : 1
Mode : Active
LACP Timeout : Long
------------------------------------------------------
Port-channel : Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP
---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Port : Gi0/2
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long

Port : Gi0/3
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
-----------------------------------------------------
Port-channel : Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP
N O TE: After c onfiguring the LAC P s y s tem priority :
Port Gigabitethernet 0/3 in Sw itc h A and B w ill continue to be standby ports.
The port priority c onfigured for the Port 3 in Sw itc h A is not effec tive, as the
Sy stem priority of Sw itc h A is les s w hen c ompared to B.

Configuring Port-channel Load Balance

Traffic in a port-channel is distributed across the individual bundled links in a deterministic
fashion. However, the load is not necessarily balanced equally across all the links. Instead,
frames are forwarded on a specific link using any of the following criteria - source MAC,
destination MAC, and source + destination MAC. The default setting is source + destination
MAC. For virtual ports this release only supports source + destination MAC.
Execute the following commands in the Switch A.
2. Configure the load-balance policy.
aos(config)# port-channel load-balance dest-mac 1
The load-balance policy can be configured as:
n src-mac: Load distribution is based on the source MAC address in the

frame. Packets from different hosts use different ports in the channel, but
packets from the same host use the same port.
n dest-mac: Load distribution is based on the destination MAC address in the
frame. Packets to the same destination are sent on the same port, but
packets to different destinations are sent on different ports in the channel.
n src-dest-mac: Load distribution is based on the source and destination MAC
addresses.
n vlan-id: Load distribution is based on VLAN Identifier.

aos(config)# end
4. View the Etherchannel load-balance information using the following command.
aos# show etherchannel load-balance
The output in the Switch is,
---------------------
Group : 1
----------
Destination MAC Address
Group : 2
----------
Source & Destination MAC Address
N O TE: If the port-c hannel index is not inc luded in this command, then the
load-balanc ing applies for all port-c hannels c onfigured in the sys tem

Configuring LACP System Identifier

Ports 1, 2 and 3 are part of Link Aggregation.
Execute the following commands in both the switches to configure the global LACP System
ID.
3. Create port channel.
aos(config)# end
5. Configure the LACP System Identifier.
aos(config)# lacp system-identifier 00:55:44:33:22:11
aos(config)# end
7. View the Etherchannel information using the following command.
---------------------
Group: 1
----------
Protocol: LACP
Ports in the Group
------------------
Port: Gi0/1
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Port : Gi0/2
-------------


Channel Group : 1
Mode : Active
LACP Timeout : Long
------------------------------------------------------
Port-channel : Po1
-------------------
Number of Ports = 2
Protocol = LACP

Configuring LACP Port Identifier

Ports 1, 2 and 3 are part of Link Aggregation.
Observe the Port State behavior with default port identifier.

---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Defaulted
Port : Gi0/2
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Defaulted
Port : Gi0/3
-------------
Channel Group : 1
Mode : Active

LACP Timeout : Long

Aggregation State : Aggregation, Defaulted
------------------------------------------------------
Gi0/1 Bundle 128 1 1 0x1 0xbe
Port-channel : Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP
N O TE: Obs erv ation before c onfiguring the LAC P port identifier:
Port Gigabitethernet 0/3 in s w itc h A and B are Standby ports .
1. Now, configure the port identifier of Port 3 in Switch A as 1.
aos(config-if)# lacp port-identifier 1
2. View the configuration use the following command.

---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Port : Gi0/2
-------------
Channel Group : 1
Mode : Active


LACP Timeout : Long
Port : Gi0/3
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long

------------------------------------------------------
Port-channel : Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP
N O TE: Obs erv ation after c onfiguring the LAC P port identifier:
Port Gigabitethernet 0/3 in Sw itc h A bec omes up in bundle.

MTU Configurations
Ports 1, 2 and 3 are part of link aggregation.
N O TE: W hen the MTU of a port in a bundle differs from the Port C hannel’s
MTU , then the port w ill not be up in the bundle.
Observe the Port State behavior with default MTU Settings for all the Ports.
aos# show interface mtu
Gi0/1 MTU size is 1500
po1 MTU size is 1500
vlan1 MTU size is 1500
Execute the following commands to configure the MTUs.
1. Enter into the Global Configuration mode.
2. Create the Interface.
aos(config-if)# shutdown
3. Configure the MTU.
aos(config-if)# mtu 1000
4. Exit from the Interface Configuration mode.
aos(config-if)# end
5. View the configured information using the following command.


Maximum ports per Port Channel is 24 with maximum 8 active ports

---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
Port State = Down, Not in Bundle
Channel Group : 1
Mode : Active
LACP Timeout : Long
Aggregation State : Aggregation, Defaulted
Port : Gi0/2
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Defaulted
-----------------------------------------------------
Gi0/1 Down 128 1 1 0x1 0xa2
Port-channel : Po1
-------------------
Number of Ports = 2
Protocol = LACP
N O TE: Obs erv ation after c onfiguring the MTU of Port 1 to 1000:
As the MTU of port 1 differs from MTU of Port C hannel interface, the
Port Gigabitethernet 0/1 in s w itc h A w ill become dow n in bundle.
N O TE: There is a system mtu <x> c ommand w hic h sets MTU on all
interfac es (inc luding port c hannel) at the s ame time. It does not
change the MTU on any new interfac es : how ever, the command can
be run a s ec ond time.

However, if we change the MTU of the port channel then it will be applied on all the ports in
the bundle. All the port-channel member ports will become up in bundle in Switch A.
aos(config-if)# end
---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Defaulted
Port : Gi0/2
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Defaulted


-----------------------------------------------------
Port-channel : Po1
-------------------
Number of Ports = 2
Protocol = LACP

Configuring LACP Wait Time

LACP wait time is the wait interval for a link to become aggregated. Configuring the wait-
time value as 0 ensures that links get aggregated immediately.
The default value of the LACP Wait time is 2.
Execute the following commands to configure the LACP Wait time.
aos(config)#configure terminal
2. Enter into the Interface configuration mode.
Configure the LACP Wait time.
aos(config-if)# lacp wait-time 1
3. View the Etherchannel information using the following command
---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long

Configuring LACP Time-out

LACP time out is a periodic interval, on the expiry of which an LACP PDU is sent out
regularly. Default value of LACP time out is Long.
N O TE: The long timeout v alue means that LAC P PD U w ill be sent for every
30 seconds and LAC P timeout v alue (no pac k et is received from peer) is 90
seconds.
N O TE: The s hort timeout v alue means that LAC P PD U w ill be sent for every
1 second and timeout v alue is 3 s ec onds .
Execute the following commands to configure the LACP Wait time.
aos(config)#configure terminal
2. Enter into the Interface configuration mode.
3. Configure the LACP Time-out.
aos(config-if)# lacp timeout short
4. View the Etherchannel information using the following command

---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Short

Displaying LACP Status

View the port-channel information in a detailed and summarized form along with load
balance frame distribution scheme, port and port-channel information using the following
command.
Port-channel is enabled
Max Port Channels is 24 with maximum 8 active ports per port
channel
---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Port : Gi0/2
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Aggregation State : Aggregation, Sync, Collecting, Distributing
Port-channel : Po1
-------------------
Number of Ports = 2
Protocol = LACP
View the LACP information such as traffic counters and neighbor information.
aos# show lacp neighbor detail
Flags:
A - Device is in Active mode
P - Device is in Passive mode
Channel group 1 neighbors
Port Gi0/1

----------
Partner System ID : 00:01:02:03:04:21
Flags : P
LACP Partner Port Priority : 128
LACP Partner Oper Key : 2
LACP Partner Port State : 0x3c
Port State Flags Decode

------------------------
Activity : Passive
LACP Timeout : Long
Aggregation State : Aggregation, Sync, Collecting, Distributing
Port Gi0/2
----------
Partner System ID : 00:01:02:03:04:21
Flags : P
LACP Partner Port Priority : 128
LACP Partner Oper Key : 2
LACP Partner Port State : 0x3c
Port State Flags Decode

------------------------
Activity: Passive
LACP Timeout: Long
Aggregation State: Aggregation, Sync, Collecting, Distributing

INTERACTION BETWEEN LA AND VLAN CHAPTER 3
Chapter 3. Interaction Between LA and VLAN

Whenever a port-channel is created, it is added as an untagged member port of the default
VLAN 1. For other VLANs, it needs to be explicitly configured (or dynamically learnt through
GVRP) as a member port. It does not inherit the VLAN membership of its member ports.
When a port is aggregated into a bundle, that port will not be visible to higher Layer 2
applications like VLAN, STP, etc., only the port-channel port will be visible to them. Hence,
when the port is aggregated into a port channel port, it will be removed from the
membership of the specific VLAN. Similarly, when a port is disaggregated from a port-
channel, it is added as a member port of the default VLAN 1.
Examples
For example, consider 2 VLANs configured in a Switch.
aos# show vlan
Vlan database
-------------
Vlan ID : 1
Member Ports: Gi0/1, Gi0/2, Gi0/3, Gi0/4, Gi0/5, Gi0/6
Gi0/7, Gi0/8, Gi0/9, Gi0/10, Gi0/11, Gi0/12
Gi0/13, Gi0/14, Gi0/15, Gi0/16, Gi0/17, Gi0/18
Gi0/19, Gi0/20, Gi0/21, Gi0/22, Gi0/23, Gi0/24
Untagged Ports: Gi0/1, Gi0/2, Gi0/3, Gi0/4,Gi0/5,Gi0/6
Gi0/7, Gi0/8, Gi0/9, Gi0/10, Gi0/11, Gi0/12
Gi0/13, Gi0/14, Gi0/15, Gi0/16, Gi0/17, Gi0/18
Gi0/19, Gi0/20, Gi0/21, Gi0/22, Gi0/23, Gi0/24
Forbidden Ports : None
Name :
Status : Permanent
----------------------------------------------------
Vlan ID : 2
Member Ports: Gi0/1, Gi0/2, Gi0/3, Gi0/4, Gi0/5
Untagged Ports: Gi0/1, Gi0/2, Gi0/3, Gi0/4, Gi0/5
Name :
Status : Permanent
Consider that Port 1 and Port 2 are aggregated into a bundle.

CHAPTER 3 INTERACTION BETWEEN LA AND VLAN
View the configured information using the following command.
aos# show vlan
Vlan database
-------------
Vlan ID : 1
Gi0/9, Gi0/10, Gi0/11, Gi0/12, Gi0/13, Gi0/14
Gi0/15, Gi0/16, Gi0/17, Gi0/18, Gi0/19, Gi0/20
Gi0/21, Gi0/22, Gi0/23, Gi0/24, po1
Untagged Ports: Gi0/3, Gi0/4, Gi0/5, Gi0/6, Gi0/7, Gi0/8
Gi0/9, Gi0/10, Gi0/11, Gi0/12, Gi0/13, Gi0/14
Gi0/15, Gi0/16, Gi0/17, Gi0/18, Gi0/19, Gi0/20
Gi0/21, Gi0/22, Gi0/23, Gi0/24, po1
Name :
Status : Permanent
------------------------------------------
Vlan ID : 2
Member Ports : Gi0/3, Gi0/4, Gi0/5
Untagged Ports : Gi0/3, Gi0/4, Gi0/5
Name :
Status : Permanent
----------------------------------
N O TE: Obs erv ation after c reating the port c hannel: Member ports of the
bundle 1 and 2 w ill be remov ed from all the VLAN s . The port channel port
w ill bec ome the member of the default VLAN (Vlan 1).
Unmap from the default switch.
aos(config)# int port-channel 1
aos(config-if)# no map switch default
aos(config)# no interface port-channel 1
aos(config)# exit
Delete the port channel.
aos(config)# no interface port-channel 1
aos(config)exit
aos# show vlan
Vlan database
-------------
Vlan ID : 2
Member Ports : Gi0/3, Gi0/4, Gi0/5
Untagged Ports : Gi0/3, Gi0/4, Gi0/5
Name :
Status : Permanent
----------------------------------------------------
Vlan ID : 1
Gi0/7, Gi0/8, Gi0/9, Gi0/10, Gi0/11, Gi0/12
Gi0/13, Gi0/14, Gi0/15, Gi0/16, Gi0/17, Gi0/18
Gi0/19, Gi0/20, Gi0/21, Gi0/22, Gi0/23, Gi0/24

INTERACTION BETWEEN LA AND VLAN CHAPTER 3
Untagged Ports: Gi0/1, Gi0/2, Gi0/3, Gi0/4, Gi0/5, Gi0/6

Gi0/7, Gi0/8, Gi0/9, Gi0/10, Gi0/11, Gi0/12
Gi0/13, Gi0/14, Gi0/15, Gi0/16, Gi0/17, Gi0/18
Gi0/19, Gi0/20, Gi0/21, Gi0/22, Gi0/23, Gi0/24
Name :
Status : Permanent
----------------------------------------------------
N O TE: Obs erv ation after deleting the port c hannel:
Port C hannel port w ill be remov ed from the VLAN . Member ports of the
bundle 1 and 2 w ill bec ome the member of the default VLAN (Vlan 1 ), but
not of other VLAN s .

DYNAMIC AGGREGATOR CONFIGURATION CHAPTER 4
Chapter 4. Dynamic Aggregator Configuration

The Dynamic Aggregator feature enables ports to choose their aggregator dynamically
based on their partner information. When two ports are connected to a same partner and
their LAGG id (System id + Admin key) information is identical, they will form a single
aggregation. Otherwise, the ports will belong to different aggregators.
For a port to participate in this dynamic selection, it has to be configured as a “default” port
of an aggregator. Only one default port can be configured for an aggregator. When a default
port is configured for an aggregator, no other port can be configured to be a member of that
aggregator. The port will belong to the default aggregator when it is connected to a unique
partner or when no partner information is available.
Consider the following scenario where four aggregators are created and each has been
assigned a default port.
Figure 3. Initial Scenario
All the ports should be configured with the same Actor Admin key.
After the LACP PDUs are exchanged, selection logic is triggered to choose the aggregator
based on the Partner information. The following parameters are compared for a port to
belong to the same aggregator.
Actor System ID (Mac address + Priority)
Actor Admin Key
Partner System ID (Mac Address + Priority)
Partner Admin Key
Figure 4. Port Reallocation across Aggregator at end of Selection Logic

CHAPTER 4 DYNAMIC AGGREGATOR CONFIGURATION
When two or more ports are connected to the same partner (these ports have same LAG-
ID), then the lowest numbered aggregator associated with the set of ports will be chosen
and all the ports will be attached to that aggregator. The default port of the least aggregator
is referred to as the “primary” port. In the figure above, Ports 1, 2 and 3 are connected to
the same partner and Port 4 is connected to a different partner. Therefore, Ports 2 and 3
move out of their default aggregator and get attached to Agg-2.
Figure 5. Primary Port is Down
When the primary port in aggregator goes down, the associated aggregator will also go
down and the rest of the ports in the aggregator will move to next least numbered
aggregator.
When a port moves to a different aggregator the port will inherit all the aggregator
properties to which they are bound.
The port specific attributes, like Actor Admin state, Partner Admin state, Actor admin port,
will remain same even if the port moves to a new aggregator. VLAN/STP properties will be
inherited from the new aggregator to which the ports become bound.
Configurations
This section describes the configuration for creating an aggregator and binding a port to an
aggregator.
The following configuration creates po25 and binds s Port-1 to po25 with
aAggPortActorAdminKey = 25 and aAggActorAdminKey = 25
1. Execute the following commands
aos#
aos(config)# end
aos(config)# interface port-channel

DYNAMIC AGGREGATOR CONFIGURATION CHAPTER 4

aos(config-if)# end
2. View the information using the following command
Port-channel Independent mode is disabled
---------------------
Group: 25
----------
Protocol :LACP
Ports in the Group

------------------Port : Gi0/1-------------
Channel Group : 25
Mode : Active
Port-channel = Po25
LACP Timeout : Long

Defaulted
------------------------------------------------------
Gi0/1 Bundle 128 25 25 0x1 0xbe
Port-channel : Po25
-------------------
Number of Ports = 1
Protocol = LACP
Aggregator-MAC 00:01:02:03:04:19
Maximum number of Ports = 8

260-668457-001
WWW.AVIATNETWORKS.COM

CTR 8500-8300 3.7.0 LA Configuration - December2018

Uploaded by

Copyright:

Available Formats

CTR 8500-8300 3.7.0 LA Configuration - December2018

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CTR 8500-8300 3.7.0 LA Configuration - December2018

Uploaded by

Copyright:

Available Formats

CTR 8500-8300

Copyright & Terms of Use

Copyright © 2018 by Aviat Networks, Inc.

260-668457-001 DECEMBER 2018 III

Aviat NetworksTechnical Support

Global Support Hotline: +1 210 526 6345

260-668457-001 DECEMBER 2018 V

Sales and Sales Support:

Corporate Headquarters International Headquarters

Phone: + 1 408 941 7100 Phone: + 65 6496 0900

Product Compliance Notes

Regulatory Information for 5.8 GHz Band

260-668457-001 DECEMBER 2018 VII

l FCC CFR47, Part 15.407 excludes the use of point-to-multipoint systems,

International Use of 5.8 GHz

Networking Devices in Electric Power Substations

VIII AVIAT NETWORKS

Declaration of Conformity, Radio Equipment Directive

С настоящото Aviat Networks декларира, че този тип

Tímto Aviat Networks prohlašuje, že typ rádiového zařízení ODU

Hermed erklærer Aviat Networks, at radioudstyrstypen ODU 600/ODU

Hiermit erklärt Aviat Networks, dass der Funkanlagentyp ODU 600/ODU

Με την παρούσα ο/η Aviat Networks, δηλώνει ότι ο ραδιοεξοπλισμός

260-668457-001 DECEMBER 2018 IX

Il fabbricante, Aviat Networks, dichiara che il tipo di apparecchiatura

Ar šo Aviat Networks deklarē, ka radioiekārta ODU 600/ODU 600sp

Aviat Networks ovime izjavljuje da je radijska oprema tipa ODU

Aviat Networks potrjuje, da je tip radijske opreme ODU 600/ODU 600sp

Aviat Networks týmto vyhlasuje, že rádiové zariadenie typu ODU

Aviat Networks vakuuttaa, että radiolaitetyyppi ODU 600/ODU 600sp

Full declarations of conformity are available at:

Country Availability Matrix

260-668457-001 DECEMBER 2018 XI

IT SHOULD BE NOTED THAT A LICENSE TO OPERATE THIS EQUIPMENT WILL BE

XII AVIAT NETWORKS

Conventions and Terminology

260-668457-001 DECEMBER 2018 XIII

Copyright & Terms of Use iii

CHAPTER 2. CONFIGURING LINK AGGREGATION 19

CHAPTER 3. INTERACTION BETWEEN LA AND VLAN 53

CHAPTER 4. DYNAMIC AGGREGATOR CONFIGURATION 57

XIV AVIAT NETWORKS

Purpose and Scope

AVIAT NETWORKS DECEMBER 2018 15

Table 2. General Configurations

16 DECEMBER 2018 AVIAT NETWORKS

Upon Link Aggregation, individual point-to-point ports/interfaces are aggregated into a

AVIAT NETWORKS DECEMBER 2018 17

Figure 1. Link Aggregation - Example

18 DECEMBER 2018 AVIAT NETWORKS

Chapter 2. Configuring Link Aggregation

AVIAT NETWORKS DECEMBER 2018 19

Feature Default Setting

Port and Aggregation States

20 DECEMBER 2018 AVIAT NETWORKS

Synchronization Encoded in bit 3.

Enabling Link Aggregation

AVIAT NETWORKS DECEMBER 2018 21

aos# configure terminal