CTR 8500-8300 3.0 LA Config July2015 260-668256-005

CTR 8300/8500 CONFIGURATION
LA
Version 3.0
260-668256-005
Copyright & Terms of Use
July 2015
This documentation incorporates features and functions provided with CTR 8540 and CTR 8300 for software
release 3.0
Copyright © 2015 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, elec-
tronic, magnetic, optical, chemical, manual or otherwise, without the prior written permission of Aviat Net-
works Inc. To request permission, contact techpubs@aviatnet.com.
Warranty
Aviat Networks makes no representation or warranties with respect to the contents hereof and specifically dis-
claims any implied warranties or merchantability or fitness for any particular purpose. Further, Aviat Net-
works 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 install-
ation and service, and of measures to avoid any danger to themselves, to any other personnel, and to the equip-
ment.
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 this guide.
Local safety regulations must be used if mandatory. Safety instructions in this guide should be used in addi-
tion to the local safety regulations. In the case of conflict between safety instructions stated in this guide and
those indicated in local regulations, mandatory local norms will prevail. Should local regulations not be man-
datory, then the safety norms in this guide will prevail.
4. Service Personnel Skill: Service personnel must have received adequate technical training on tele-
communications and in particular on the equipment this guide refers to.
Trademarks
All trademarks are the property of their respective owners.
End User License Agreement and Open Source
By using this product you agree to the terms of the CTR 8540 End User License Agreement; to view this, log
into a CTR 8540 or CTR 8300 using the CLI command window and enter the CLI command “show EULA”.
The CTR 8540 and CTR 8300 use free and open source software components, which can be viewed by using
the CLI command “show system acknowledgments”. This command also details the licenses associated with
each component and describes the methods available to acquire the open source software.
260-668256-005 JULY 2015 I

LA CONFIGURATION CTR 8300 AND 8500
Aviat Networks Technical & Sales

Support
Technical Service and Support
For customer service and technical support, contact one of the regional Technical Help Desks listed below, or
for 24/7 (all day, every day of the year) there is the Global Technical Help Desk (GTHD). A call will be answered
by GTHD support staff who will resolve the issue, if possible, or quickly pass the call to the appropriate TAC
engineer for resolution. Contact information is available below or on the Aviat Networks web site.
Global Technical Help Desk
The GTHD number is: +1-210-526-6345, or toll free 1-800-227-8332 within USA
For 24/7 access you will need your Support Assurance PIN. Without a PIN you will still receive support, but the
support process will require an additional screening step. After-hours calls to Paris are routed to the GTHD,
with the existing number left in place during business hours.
Americas Technical Help Desk EMEA Technical Help Desk Asia Pacific Technical Help Desk
Aviat Networks Aviat Networks Aviat Networks
5200 Great America Parkway 4 Bell Drive Bldg 10, Units A&B
Santa Clara CA 95054 Hamilton International Technology Philexcel Industrial Park
U.S.A. Park M. Roxas Hi-way
Blantyre, Glasgow, Scotland Clark Freeport Zone
G72 0FB Philippines 2023
United Kingdom
Toll Free (Canada/USA): 800 227 Phone: Phone: +63 45 599 5192
8332 Hamilton: +44 (0) 1698 717 230 Fax: +63 45 599 5196
Phone: 210 561 7400 Paris: +33 (0) 1 77 31 00 33
Fax: 210 561 7399 Fax: +44 (0) 1698 717 204
Cus- Cus- CustomerCare.Asia@aviatnet.com
tomerCare.Americas@aviatnet.com tomerCare.EMEA@aviatnet.com
Sales and Sales Support

Contact one of the Aviat Networks headquarters, or find your regional sales office on the Aviat Networks web
site.
Corporate Headquarters, California, USA International Headquarters , Singapore
Aviat Networks, Inc. Aviat Networks(S) Pte. Ltd.
5200 Great America Parkway 17, Changi Business Park Central 1
Santa Clara CA 95054 Honeywell Building, #04-01
U.S.A. Singapore 486073
Phone: + 408 567 7000 Phone: +65 6496 0900
Fax: + 408 567 7001 Fax: + 65 6496 0999
Sales Inquiries: +1-321-674-4252
II AVIAT NETWORKS
Product Compliance Notes

CTR 8540, CTR 8312, and CTR 8311 have been tested for and meet EMC Directive 2004/108/EC. The equipment
was tested using screened cable; if any other type of cable is used, it may violate compliance.
CTR 8540, CTR 8312, and CTR 8311 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.
At CT R s of tw ar e r el eas e 3 . 0 , op er ati on of IRU 6 0 0 i s n ot s u p p or ted .
At CT R s of tw ar e r el eas e 3 . 0 , op er ati on of ODU 6 0 0 or ODU 3 0 0 h p on ANSI f r eq u en c y b an d s
i s n ot s u p p or ted .
At CT R s of tw ar e r el eas e 3 . 0 , op er ati on of ODU 6 0 0 on th e l i c en s e- f r ee 5 . 8 GHz b an d i s n ot
s u p p or ted .
International Use of 5.8GHz

ODU 600 or IRU 600 with CTR 8540, CTR 8312, or CTR 8311 on the 5.8 GHz license-free band do 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.
WEEE Directive
In accordance with the WEEE Directive (2002/96/EC), CTR 8540, CTR 8312, and CTR 8311 are 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 inform-
ation 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, and CTR 8311 meet the requirements of ROHS directive 2011/65/EU.
260-668256-005 JULY 2015 III

Declaration of Conformity, R&TTE Directive, 1999/5/EC

The reference to CTR in this declaration denotes intended use of the CTR 8540, CTR 8312, or CTR 8311, with
one or more of the following Aviat Networks ODUs: ODU 600, ODU 600sp, ODU 300hp.
IV AVIAT NETWORKS
The CTR 8540, CTR 8312, or CTR 8311 with an ODU 600, ODU 600sp, or ODU 300hp radio is classified under the
R&TTE Directive 99/5/EC as a class 2.8 radio (microwave fixed link) product.
Point-to-point radio relay equipment is intended to be used for:
- Interconnecting private and public networks.
- Interconnecting mobile base stations back to the PSTN point of presence (POP).
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 in the table below.
- The information contained in this table has been gathered from the relevant government authorities and
relates only to European countries participating in the R&TTE directive.
It s h ou l d b e n oted th at a l i c en s e to op er ate th i s eq u i p men t i s l i kel y to b e n ec es s ar y, an d
th e ap p r op r i ate r eg u l ator y ad mi n i s tr ati on s h ou l d b e c on tac ted .
260-668256-005 JULY 2015 V

VI AVIAT NETWORKS
Table of Contents
Copyright & Terms of Use i
Aviat Networks Technical & Sales Support ii
Product Compliance Notes iii
International Use of 5.8GHz iii
WEEE Directive iii
RoHS Directive iii
Declaration of Conformity, R&TTE Directive, 1999/5/EC iv
Table of Contents vii
CHAPTER 1. INTRODUCTION 1
Purpose and Scope 1
Acronyms 1
References 1
Document Conventions 2
General Configurations 2
Protocol Description 3
CHAPTER 2. CONFIGURING LINK AGGREGATION 5

Configuration Requirements 6
Default Configurations 6
Port and Aggregation States 6
Enabling Link Aggregation 7
Enabling Independent Mode 9
Configuring Port-channel Interfaces 10
Configuring LACP Port-Priority 14
Configuring LACP System Priority 23
Configuring Port-channel Load Balance 32
Configuring LACP System Identifier 33
Configuring LACP Port Identifier 35
MTU Configurations 39
Configuring LACP Wait Time 44
Configuring LACP Time-out 45
Displaying LACP Status 47
260-668256-005 JULY 2015 VII

CHAPTER 3. INTERACTION BETWEEN LA AND VLAN 51
CHAPTER 4. DYNAMIC AGGREGATOR CONFIGURATION 55

Configurations 56
VIII AVIAT NETWORKS

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 pro-
tocol as a pre-requisite.
LA i s currentl y not supported for the CTR 8300 product. Thi s document
onl y appl i es to the CTR 8540 document.
Acronyms
Table 1-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 CLI Reference Guide
260-668256-005 JULY 2015 1

CHAPTER 1. INTRODUCTION
Document Conventions
Table 1-2. Conventions Used in this Document
Convention Usage
Code text CLI (Command Line Interface) Com-
mands
Code Italics User Inputs to Command
Blue code CLI Command output
Red code Output of the configured value
General Configurations
The following table provides the access and exit methods to various general configuration
modes.
Table 1-3. General Configurations
Command Mode Access Method Prompt Exit method
User EXEC This is the initial mode to start aos> The logout method is
a session. used.
Privileged EXEC Use the enable command to aos# Use the command dis-
enter the Privileged EXEC able to return from the
mode. Privileged EXEC mode to
User EXEC mode, the dis-
able command is used.
Global Con- Enter Privileged EXEC mode aos(config)# Use the command exit
figuration and use the command con- to log out of the Global
figure terminal to enter Configuration Mode, and
the Global Configuration the command end to log
Mode. out of the Privileged
EXEC mode.
Interface Con- In Global Configuration Mode, aos(config-if)# Use the command exit
figuration use the command command to log out of the Global
interface <interface- Configuration Mode, and
type><interface-id>to the command end to log
enter the Interface Con- out of the Privileged
figuration Mode. EXEC mode.
2 AVIAT NETWORKS
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 stand-
ard 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 mod-
ules (such as Spanning Tree).
Link Aggregation features include:
1. Load sharing
2. Increased availability
3. Increased bandwidth
4. Linear incremental bandwidth
5. 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 com-
posing 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 aggreg-
ated 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.
260-668256-005 JULY 2015 3

Figure 2-1. Link Aggregation - Example
4 AVIAT NETWORKS
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-1. Link Aggregation - Topology 1. By default Aviat Networks CTR 8540 sup-
ports a minimum of 1 port to a maximum of 8 ports per aggregation.
F or data on confi guri ng ports, radi o, L1LA, protecti on, and POE ports, see
other CTR fami l y documentati on, i ncl udi ng the G ettin g S tarted G u ide and
the C L I Referen ce.
260-668256-005 JULY 2015 5

CHAPTER 2. CONFIGURING LINK AGGREGATION
Configuration Requirements
LA configuration requirements are as follows:
1. Port-channel must be enabled in the system for Link aggregation configuration to
take effect.
2. 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 2-1. Default Configurations
Feature Default Setting
Port-channel Disabled
Channel-groups None
LACP System Pri- 0x8000 or 32768
ority
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 2-2. 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
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
6 AVIAT NETWORKS
State Settings
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.
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. 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

Li nk Aggregati on i s di sabl ed by defaul t.
Procedure
1. Execute the following commands in both the switches to enable Link Aggregation.
- Enter the Global Configuration mode.
aos# configure terminal
- Enable port channel.
aos(config)# set port-channel enable
260-668256-005 JULY 2015 7

- Exit from the Global configuration mode.

aos(config)# end
2. View the etherchannel information using the following command.
aos# show etherchannel summary
A sample result is:
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
The fol l owi ng command i s used to shut down the enti re LA
modul e
aos(config)# shutdown port-channel
8 AVIAT NETWORKS
Enabling Independent Mode

I ndependent mode i s di sabl ed by defaul t.
Procedure
1. 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
00:01:02:03:04:05
aos# show etherchannel detail
The output in Switch A and Switch B is,
Port-channel Independent mode is enabled
00:01:02:03:04:05
The command used to di sabl e i ndependent feature i n the
swi tch i s:
aos(config)# set port-channel independentmode dis-
able
I ndependent mode feature can be veri fi ed by enabl i ng thi s
feature on both Actor and Partner si des. I f i t i s enabl ed on
ei ther of the si des, thi s wi l l end up i n i nconsi stent beha-
vi or. Avoi d thi s.
260-668256-005 JULY 2015 9

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 com-
mands:
aos(config)# interface port-channel 1
aos(config-if)# no shut
aos(config-if)# map switch default
aos(config-if)# end
The LACP feature can be veri fi ed by enabl i ng LACP (can be ei ther Act-
i ve/Passi ve) on both Actor and Partner si des. I f LACP i s enabl ed on Actor
si de and manual on partner si de or vi ce versa, i t wi l l end up i n i ncon-
si stent behavi or, hence thi s mi s-confi gurati on shoul d be avoi ded.
Procedure
1. Execute the following commands in both the switches.
- Enter the Global configuration mode.
- Create port channel.
aos(config-if)# no shutdown
aos(config-if)# map switch default
- 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
- 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 inter-
faces.
aos(config-if)# channel-group 1 mode active
- Mode can be
l active: LACP negotiation is started un-conditionally.
l passive: LACP negotiation is started only when an LACP packet is
received from the peer.
l on: Force the interface to be a part of the port channel without
communicating through the LACP protocol. This is equivalent to manual
aggregation.
- Exit from the Interface configuration mode.
aos(config-if)# end
10 AVIAT NETWORKS
aos# show etherchannel 1 detail

- The output in Switch A is
00:01:02:03:04:01

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
260-668256-005 JULY 2015 11

-------------------
Number of Ports = 1
HotStandBy port = null
Port state = Port-channel Ag-Inuse
Protocol = LACP
MAC selection = Dynamic
The output in Switch B is,
00:02:02:03:04:01
---------------------
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,

Port
State
--------------------------------------------------
----
Gi0/3 Bundle 128 1 1 0x3
0xa0
12 AVIAT NETWORKS
Port-channel : Po1
-------------------
Number of Ports = 1
Protocol = LACP
260-668256-005 JULY 2015 13

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.
Procedure
aos(config) # set port-channel enable
aos(config-if)# exit
aos(config-if)# end
- The output in Switch A is,
00:01:02:03:04:01

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

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

Distributing,
Port : Gi0/3
-------------
Port State = Hot standby
Channel Group : 1
Mode : Active
260-668256-005 JULY 2015 15


LACP Timeout : Long
Aggregation State : Aggregation,
Port
State
--------------------------------------------------
----
Gi0/1 Bundle 128 1 1 0x1
0xbc
Gi0/2 Bundle 128 1 1 0x2
0xbc
Gi0/3 Standby 128 1 1 0x3
0xa0
Port-channel : Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP
00:02:02:03:04:01

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

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

Distributing,
Port : Gi0/3
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Port
State
260-668256-005 JULY 2015 17

--------------------------------------------------
----
Gi0/1 Bundle 128 1 1 0x1
0xbc
Gi0/2 Bundle 128 1 1 0x2
0xbc
0xa0
Port-channel: Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP
Observati on before confi guri ng the LACP port pri ori ty:Port
Gi gabi tEthernet 0/3 i s the Standby port i n Swi tches A and
B. (as max ports i n the port channel i s 2 ports)
3. Execute the following commands in Switch A.
- Enter the Interface Configuration mode.
- 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
- To return to the default port-priority configuration for the interface use the com-
mand
aos(config-if)# no lacp port-priority.
- Exit from the Interface Configuration mode.
aos(config-if)# end
4. View the Etherchannel information using the following command.
00:01:02:03:04:01
18 AVIAT NETWORKS
---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Distributing,
Port : Gi0/2
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Port : Gi0/3
-------------
Channel Group : 1
Mode : Active
260-668256-005 JULY 2015 19


LACP Timeout : Long

Distributing,
Port
State
--------------------------------------------------
----
Gi0/1 Bundle 128 1 1 0x1
0xbc
0xbc
Gi0/3 Bundle 20 1 1 0x3
0xa0
Port-channel : Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP
00:02:02:03:04:01

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

Channel Group : 1
Mode : Active
LACP Timeout : Long

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

Port
260-668256-005 JULY 2015 21


State
--------------------------------------------------
----
Gi0/1 Bundle 128 1 1 0x1
0xbc
0xbc
Gi0/3 Bundle 128 1 1 0x3
0xa0
Port-channel : Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP
Observati on after confi guri ng the LACP port pri ori ty:
Port 2 i s the Standby port i n Swi tches A and B.
22 AVIAT NETWORKS
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.
Procedure
aos(config) # set port-channel enable
iss(coning-if)# exit
aos(config-if)# end
00:01:02:03:04:01

---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
260-668256-005 JULY 2015 23


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

Port
24 AVIAT NETWORKS

State
--------------------------------------------------
----
Gi0/1 Bundle 128 1 1 0x1
0xbc
Gi0/2 Bundle 128 1 1 0x2 0xbc
0xa0
Port-channel : Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP
- The output in Switch B is,
00:02:02:03:04:01

---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
Channel Group : 1
Mode : Active
260-668256-005 JULY 2015 25


LACP Timeout : Long
Distributing,
Port : Gi0/2
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Distributing,
Port : Gi0/3
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Aggregation State : Aggregation
Port
State
--------------------------------------------------
---
Gi0/1 Bundle 128 1 1 0x1
0xbc
Gi0/2 Bundle 128 1 1 0x2
0xbc
26 AVIAT NETWORKS

0xa0
Port-channel : Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP
Observati on before confi guri ng the LACP system pri ori ty:
Port Gi gabi tethernet 0/3 i n swi tch A and B are standby
ports.
3. Execute the following commands in Switch B.
- 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
- Execute the following command to configure the LACP Port Priority, for Port 3 in
Switch A.
aos(config-if)# lacp port-priority 20
- Exit from the configuration mode.
aos(config-if)# end
00:01:02:03:04:01

---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
260-668256-005 JULY 2015 27

Port : Gi0/1
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Distributing,
Port : Gi0/2
-------------
Port State = Up in BundleChannel Group : 1
Mode : Active
LACP Timeout : Long
Distributing,
Port : Gi0/3
-------------
Port State = Hot stanby
Channel Group : 1
Mode : Active
LACP Timeout : Long
Distributing,
28 AVIAT NETWORKS
LACP Port Admin Oper Port Port

State
--------------------------------------------------
----
Gi0/1 Bundle 128 1 1 0x1
0xbc
Gi0/2 Bundle 128 1 1 0x2
0xbc
0xa0
Port-channel : Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP
00:02:02:03:04:01
---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
Channel Group : 1
Mode : Active
260-668256-005 JULY 2015 29

LACP Timeout : Long

Distributing,
Port : Gi0/2
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Distributing,
Port : Gi0/3
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
State
--------------------------------------------------
---
Gi0/1 Bundle 128 1 1 0x1
0xbc
Gi0/2 Bundle 128 1 1 0x2
0xbc
0xa0
30 AVIAT NETWORKS
Port-channel : Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP
After confi guri ng the LACP system pri ori ty:
Port Gi gabi tethernet 0/3 i n Swi tch A and B wi l l conti nue to
be standby ports. The port pri ori ty confi gured for the Port
3 i n Swi tch A i s not effecti ve, as the System pri ori ty of
Swi tch A i s l ess when compared to B.
260-668256-005 JULY 2015 31

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.
Procedure
1. Execute the following commands in the Switch A.
- Configure the load-balance policy.
aos(config)# port-channel load-balance dest-mac
1
- The load-balance policy can be configured as:
src-mac: Load distribution is based on the source MAC address in the frame. Pack-
ets from different hosts use different ports in the channel, but packets from the same
host use the same port.
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 dif-
ferent destinations are sent on different ports in the channel.
src-dest-mac: Load distribution is based on the source and destination MAC
addresses.
vlan-id: Load distribution is based on VLAN Identifier.
aos(config)# end
2. 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
I f the port-channel i ndex i s not i ncl uded i n thi s command,
then the l oad-bal anci ng appl i es for al l port-channel s con-
fi gured i n the system
32 AVIAT NETWORKS
Configuring LACP System Identifier

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


LACP Timeout : Long
Distributing,
Port : Gi0/2
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Distributing,
State
--------------------------------------------------
----
Gi0/1 Bundle 128 1 1 0x1
0xbc
Gi0/2 Bundle 128 1 1 0x2
0xbc
Port-channel : Po1
-------------------
Number of Ports = 2
Protocol = LACP
34 AVIAT NETWORKS
Configuring LACP Port Identifier

Ports 1, 2 and 3 are part of Link Aggregation.
Procedure
1. Observe the Port State behavior with default port identifier.
00:01:02:03:04:01

---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Distributing, Defaulted
Port : Gi0/2
-------------
Channel Group : 1
260-668256-005 JULY 2015 35

Mode : Active
LACP Timeout : Long
Port : Gi0/3
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Aggregation State : Aggregation, Defaulted
State
--------------------------------------------------
----
Gi0/1 Bundle 128 1 1 0x1 0xbe
Gi0/2 Bundle 128 1 1 0x2 0xbe
Gi0/3 Standby 128 1 1 0x3 0xa2
Port-channel : Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP
Observati on before confi guri ng the LACP port i denti fi er:
Port Gi gabi tethernet 0/3 i n swi tch A and B are Standby
ports.
36 AVIAT NETWORKS
2. Now, configure the port identifier of Port 3 in Switch A as 1.

aos(config-if)# lacp port-identifier 1
3. View the configuration use the following command.
00:01:02:03:04:01

---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
Distributing,
Port : Gi0/2
-------------
Channel Group : 1
Mode : Active
260-668256-005 JULY 2015 37


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

Distributing,

State
--------------------------------------------------
----
Gi0/2 Standby 128 1 1 0x2 0xa0
Port-channel : Po1
-------------------
Number of Ports = 3
HotStandBy port = 1
Protocol = LACP
Observati on after confi guri ng the LACP port i denti fi er:
Port Gi gabi tethernet 0/3 i n Swi tch A becomes up i n
bundl e.
38 AVIAT NETWORKS
MTU Configurations
Ports 1, 2 and 3 are part of link aggregation.
When the MTU of a port i n a bundl e di ffers from the Port Channel ’ s MTU,
then the port wi l l not be up i n the bundl e.
Procedure
1. 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
2. Execute the following commands to configure the MTUs.
- Enter into the Global Configuration mode.
- Create the Interface.
260-668256-005 JULY 2015 39

aos(config-if)# shutdown
- Configure the MTU.
aos(config-if)# mtu 1000
- Exit from the Interface Configuration mode.
aos(config-if)# end
3. View the configured information using the following command.
00:01:02:03:04:01
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
40 AVIAT NETWORKS

LACP Timeout : Long
State
--------------------------------------------------
---
Gi0/1 Down 128 1 1 0x1
0xa2
Gi0/2 Bundle 128 1 1 0x2
0xbe
Port-channel : Po1
-------------------
Number of Ports = 2
Protocol = LACP
Observati on after confi guri ng the MTU of Port 1 to 1000:
As the MTU of port 1 di ffers from MTU of Port Channel
i nterface, the Port Gi gabi tethernet 0/1 i n swi tch A wi l l
become down i n bundl e.
There i s a system mtu <x> command whi ch sets MTU on
al l i nterfaces (i ncl udi ng port channel ) at the same ti me. I t
does not change the MTU on any new i nterfaces: however,
the command can be run a second ti me.
- 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.
260-668256-005 JULY 2015 41

aos(config-if)# end
00:01:02:03:04:01
8 active ports
---------------------
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
42 AVIAT NETWORKS

LACP Timeout : Long
State
--------------------------------------------------
---
Gi0/1 Bundle 128 1 1 0x1
0xbe
Gi0/2 Bundle 128 1 1 0x2
0xbe
Port-channel : Po1
-------------------
Number of Ports = 2
Protocol = LACP
260-668256-005 JULY 2015 43

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.
Procedure
1. Execute the following commands to configure the LACP Wait time.
aos(config)#configure terminal
- Enter into the Interface configuration mode.
Configure the LACP Wait time.
aos(config-if)# lacp wait-time 1
2. View the Etherchannel information using the following command
00:01:02:03:04:01
8 active ports
---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
Channel Group : 1
Mode : Active
LACP Timeout : Long
44 AVIAT NETWORKS
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.
The l ong ti meout val ue means that LACP PDU wi l l be sent for every 30
seconds and LACP ti meout val ue (no packet i s recei ved from peer) i s 90
seconds.
The short ti meout val ue means that LACP PDU wi l l be sent for every 1
second and ti meout val ue i s 3 seconds.
Procedure
1. Execute the following commands to configure the LACP Wait time.
aos(config)#configure terminal
- Enter into the Interface configuration mode.
Configure the LACP Time-out.
aos(config-if)# lacp timeout short
2. View the Etherchannel information using the following command
00:01:02:03:04:01

8 active ports
---------------------
Group: 1
----------
Protocol :LACP
Ports in the Group
------------------
Port : Gi0/1
-------------
Channel Group : 1
Mode : Active
260-668256-005 JULY 2015 45


LACP Timeout : Short
46 AVIAT NETWORKS
Displaying LACP Status

Procedure
1. 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
Distributing,
Port : Gi0/2
-------------
Channel Group : 1
Mode : Active
260-668256-005 JULY 2015 47

LACP Timeout : Long

Distributing
Port-channel : Po1
-------------------
Number of Ports = 2
Protocol = LACP
2. 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
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
48 AVIAT NETWORKS
Port State Flags Decode

------------------------
Activity: Passive
LACP Timeout: Long
Distributing
260-668256-005 JULY 2015 49

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
1. 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
260-668256-005 JULY 2015 51

CHAPTER 3. INTERACTION BETWEEN LA AND VLAN
--------------------------------------------------
--
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
2. Consider that Port 1 and Port 2 are aggregated into a bundle.
3. View the configured information using the following command.
aos# show vlan
Vlan database
-------------
Vlan ID : 1
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
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
52 AVIAT NETWORKS
Member Ports : Gi0/3, Gi0/4, Gi0/5

Untagged Ports : Gi0/3, Gi0/4, Gi0/5
Name :
Status : Permanent
----------------------------------
Observati on after creati ng the port channel : Member
ports of the bundl e 1 and 2 wi l l be removed from al l the
VLANs. The port channel port wi l l become the member of
the defaul t VLAN (Vl an 1).
4. 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
5. 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/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
260-668256-005 JULY 2015 53

CHAPTER 3. INTERACTION BETWEEN LA AND VLAN
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
--------------------------------------------------
--
Observati on after del eti ng the port channel :
Port Channel port wi l l be removed from the VLAN. Member
ports of the bundl e 1 and 2 wi l l become the member of the
defaul t VLAN (Vl an 1 ), but not of other VLANs.
54 AVIAT NETWORKS
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. Other-
wise, 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 4-1. 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.
1. Actor System ID (Mac address + Priority)
2. Actor Admin Key
3. Partner System ID (Mac Address + Priority)
4. Partner Admin Key
260-668256-005 JULY 2015 55

CHAPTER 4. DYNAMIC AGGREGATOR CONFIGURATION
Figure 4-2. Port Reallocation across Aggregator at end of Selection Logic

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 4-3. 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 aAg-
gPortActorAdminKey = 25 and aAggActorAdminKey = 25
Procedure
1. Execute the following commands
aos#
aos(config)# end
aos(config)# interface port-channel
aos(config-if)# end
56 AVIAT NETWORKS
2. View the information using the following command

Port-channel Independent mode is disabled
00:01:02:03:04:01
---------------------
Group: 25
----------
Protocol :LACP
Ports in the Group

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

State
--------------------------------------------------
----
Gi0/1 Bundle 128 25 25 0x1
0xbe
Port-channel : Po25
-------------------
Number of Ports = 1
260-668256-005 JULY 2015 57

CHAPTER 4. DYNAMIC AGGREGATOR CONFIGURATION

Protocol = LACP
Aggregator-MAC 00:01:02:03:04:19
Maximum number of Ports = 8
58 AVIAT NETWORKS
260-668256-005
WWW.AVIATNETWORKS.COM

CTR 8500-8300 3.0 LA Config July2015 260-668256-005

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

CTR 8500-8300 3.0 LA Config July2015 260-668256-005

Încărcat de

Drepturi de autor:

Formate disponibile

CTR 8300/8500 CONFIGURATION

260-668256-005 JULY 2015 I

Aviat Networks Technical & Sales

Sales and Sales Support

Product Compliance Notes

International Use of 5.8GHz

260-668256-005 JULY 2015 III

Declaration of Conformity, R&TTE Directive, 1999/5/EC

260-668256-005 JULY 2015 V

CHAPTER 2. CONFIGURING LINK AGGREGATION 5

260-668256-005 JULY 2015 VII

CHAPTER 3. INTERACTION BETWEEN LA AND VLAN 51

CHAPTER 4. DYNAMIC AGGREGATOR CONFIGURATION 55

VIII AVIAT NETWORKS

260-668256-005 JULY 2015 1

Red code Output of the configured value

260-668256-005 JULY 2015 3

Chapter 2. Configuring Link

260-668256-005 JULY 2015 5

Port and Aggregation States

Enabling Link Aggregation

260-668256-005 JULY 2015 7

- Exit from the Global configuration mode.

Enabling Independent Mode

260-668256-005 JULY 2015 9

Configuring Port-channel Interfaces

aos# show etherchannel 1 detail

LACP System Priority: 32768

Port State = Up in Bundle

Aggregation State: Aggregation, Sync, Collecting,

LACP Port Admin Oper Port

260-668256-005 JULY 2015 11

LACP Port Admin Oper Port

260-668256-005 JULY 2015 13

Configuring LACP Port-Priority

LACP System Priority: 32768

Channel Group Listing

Ports in the Group

Aggregation State : Aggregation, Sync, Collecting,

Aggregation State : Aggregation, Sync, Collecting,

260-668256-005 JULY 2015 15

LACP Activity : Active

LACP System Priority: 32768

Aggregation State : Aggregation, Sync, Collecting,

Aggregation State : Aggregation, Sync, Collecting,

260-668256-005 JULY 2015 17

LACP System Priority: 32768

Channel Group Listing

260-668256-005 JULY 2015 19

LACP Port Identifier = 3

Aggregation State : Aggregation, Sync, Collecting,

LACP System Priority: 32768

Port State = Up in Bundle

Aggregation State: Aggregation, Sync, Collecting,

LACP Port Admin Oper Port

260-668256-005 JULY 2015 21

Port State Priority Key Key Number

Configuring LACP System Priority

LACP System Priority: 32768

260-668256-005 JULY 2015 23

Port State = Up in Bundle

LACP Port Admin Oper Port

Port State Priority Key Key Number