The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes how the IEEE 802.3ad Link Bundling feature leverages the EtherChannel infrastructure within Cisco IOS XE software to manage the bundling of Ethernet links. The supported Ethernet link types for link bundling are Gigabit Ethernet and Ten Gigabit Ethernet.
Knowledge of how EtherChannels and Link Aggregation Control Protocol (LACP) function in a network
Verification that both ends of the LACP link have the same baseline software version
All links must operate at the same link speed and in full-duplex mode (LACP does not support half-duplex mode).
EVCs must be with configured untagged encapsulation along with L2PT peer, to activate the LACP neighbor configuration.
All links must be configured as either EtherChannel links or LACP links.
Only physical interfaces can form aggregations. Aggregations of VLAN interfaces are not possible nor is an aggregation of aggregations.
If a router is connected to a switch, the bundle terminates on the switch.
An EtherChannel will not form if one of the LAN ports is a Switched Port Analyzer (SPAN) destination port.
All ports in an EtherChannel must use the same EtherChannel protocol.
Maximum of four bundled ports per Ethernet port channel are supported.
The maximum number of bundled ports per Ethernet port channel that can be supported varies by platform. Some platforms support 4, 8, and 14 while other platforms support a maximum of 16.
Maximum of 64 Ethernet port channels in a chassis are supported.
For RSP3, a maximum of 48 Ether channel and a maximum of 8 member-link per Ether channel are supported prior to the Cisco IOS XE Gibraltar 16.11.x release. Starting from the Cisco IOS XE Gibraltar 16.11.x release, 16 member-link per port channel is supported. The restrictions for 8 member-link port channel are also applicable for 16 member-link port channel.
Quality of service (QoS) is supported on individual bundled ports and not on Ethernet port channels.
Generic Routing Encapsulation (GRE) is not supported.
Media type should be uniform across 1G and 10G links.
For load balancing across 16 member links per port channel, a wide range of addresses (such as Source MAC, Destination MAC, Source IP, Destination IP, and VC) should be used to have the traffic flowing across all the16 member links.
Quality of service (QoS) is supported on individual bundled ports and not on Ethernet port channels.
Generic Routing Encapsulation (GRE) is not supported.
Media type should be uniform across 1G and 10G links.
For load balancing across 16 member links per port channel, a wide range of addresses (such as Source MAC, Destination MAC, Source IP, Destination IP, and VC) should be used to have the traffic flowing across all the16 member links.
LACP neighbor comes up on dot1q tagged EFP. This is a known behavior.
Same media type SX-SFP/T-SFP or RJ45/SPF supports load balance.
IP-based load balancing works only if there are more than two traffic flows through the Cisco ASR 920 routers.
Effective with Cisco IOS XE Everest 16.6.1, the Port-channel (PoCH) scale is reduced to 24 from 48 for Cisco ASR 900 RSP3 module.
 Note |
The PoCH scale for Cisco ASR 907 routers is 48. |
Effective with Cisco IOS XE Fuji 16.9.1, the micro-BFD enabled with port channel having minimum link set to the total member links, is not supported.
Gigabit EtherChannel (GEC) is high-performance Ethernet technology that provides Gigabit per second (Gb/s) transmission rates. A Gigabit EtherChannel bundles individual Ethernet links (Gigabit Ethernet or Ten Gigabit Ethernet) into a single logical link that provides the aggregate bandwidth of up to physical links. All LAN ports in each EtherChannel must be the same speed and all must be configured as either Layer 2 or Layer 3 LAN ports. Inbound broadcast and multicast packets on one link in an EtherChannel are blocked from returning on any other link in the EtherChannel.
When a link within an EtherChannel fails, traffic previously carried over the failed link switches to the remaining links within that EtherChannel. Also when a failure occurs, a trap is sent that identifies the device, the EtherChannel, and the failed link.
Each EtherChannel has a numbered port-channel interface that must be manually created before interfaces can be added to the channel group. The configuration of a port-channel interface affects all LAN ports assigned to that port-channel interface.
To change the parameters of all ports in an EtherChannel, change the configuration of the port-channel interface; for example, if you want to configure Spanning Tree Protocol or configure a Layer 2 EtherChannel as a trunk. Any configuration or attribute changes you make to the port-channel interface are propagated to all interfaces within the same channel group as the port-channel; that is, configuration changes are propagated to the physical interfaces that are not part of the port-channel but are part of the channel group.
The configuration of a LAN port affects only that LAN port.
The IEEE 802.3ad Link Bundling feature provides a method for aggregating multiple Ethernet links into a single logical channel based on the IEEE 802.3ad standard. This feature helps improve the cost effectiveness of a device by increasing cumulative bandwidth without necessarily requiring hardware upgrades. In addition, IEEE 802.3ad Link Bundling provides a capability to dynamically provision, manage, and monitor various aggregated links and enables interoperability between various Cisco devices and devices of third-party vendors.
LACP supports the automatic creation of EtherChannels by exchanging LACP packets between LAN ports. LACP packets are exchanged only between ports in passive and active modes. The protocol “learns” the capabilities of LAN port groups dynamically and informs the other LAN ports. After LACP identifies correctly matched Ethernet links, it facilitates grouping the links into an EtherChannel. Then the EtherChannel is added to the spanning tree as a single bridge port.
Both the passive and active modes allow LACP to negotiate between LAN ports to determine if they can form an EtherChannel, based on criteria such as port speed and trunking state. (Layer 2 EtherChannels also use VLAN numbers.) LAN ports can form an EtherChannel when they are in compatible LACP modes, as in the following examples:
A LAN port in active mode can form an EtherChannel with another LAN port that is in active mode.
A LAN port in active mode can form an EtherChannel with another LAN port in passive mode.
A LAN port in passive mode cannot form an EtherChannel with another LAN port that is also in passive mode because neither port will initiate negotiation.
LACP uses the following parameters:
LACP system priority—You must configure an LACP system priority on each device running LACP. The system priority can be configured automatically or through the command-line interface (CLI). LACP uses the system priority with the device MAC address to form the system ID and also during negotiation with other systems.
LACP port priority—You must configure an LACP port priority on each port configured to use LACP. The port priority can be configured automatically or through the CLI. LACP uses the port priority to decide which ports should be put in standby mode when there is a hardware limitation that prevents all compatible ports from aggregating. LACP also uses the port priority with the port number to form the port identifier.
LACP administrative key—LACP automatically configures an administrative key value on each port configured to use LACP. The administrative key defines the ability of a port to aggregate with other ports. A port’s ability to aggregate with other ports is determined by the following:
Port physical characteristics such as data rate, duplex capability, and point-to-point or shared medium
Configuration restrictions that you establish
On ports configured to use LACP, it tries to configure the maximum number of compatible ports in an EtherChannel, up to the maximum allowed by the hardware. To use the hot standby feature in the event a channel port fails, both ends of the LACP bundle must support the lacp max-bundle command.
As a control protocol, LACP uses the Slow Protocol Multicast address of 01-80-C2-00-00-02 to transmit LACP protocol data units (PDUs). Aside from LACP, the Slow Protocol linktype is to be utilized by operations, administration, and maintenance (OAM) packets, too. Subsequently, a subtype field is defined per the IEEE 802.3ad standard [1] (Annex 43B, section 4) differentiating LACP PDUs from OAM PDUs.
Note |
LACP and Port Aggregation Control Protocol (PAgP) are not compatible. Ports configured for PAgP cannot form port channels on ports configured for LACP, and ports configured for LACP cannot form port channels on ports configured for PAgP. |
Increased network capacity without changing physical connections or upgrading hardware
Cost savings from the use of existing hardware and software for additional functions
A standard solution that enables interoperability of network devices
Port redundancy without user intervention when an operational port fails
The following LACP enhancements are supported:
Four member links per LACP bundle.
Stateful switchover (SSO), in service software upgrade (ISSU), Cisco nonstop forwarding (NSF), and nonstop routing (NSR) on Gigabit EtherChannel bundles.
Link failover time of 250 milliseconds or less and a maximum link failover time of 2 seconds; port channels remain in the LINK_UP state to eliminate reconvergence by the Spanning-Tree Protocol.
Shutting down a port channel when the number of active links falls below the minimum threshold. In the port channel interface, a configurable option is provided to bring down the port channel interface when the number of active links falls below the minimum threshold. For the port-channel state to be symmetric on both sides of the channel, the peer must also be running LACP and have the same lacp min-bundle command setting.
The IEEE Link Aggregation Group (LAG) MIB.
The LACP (802.3ad) for Gigabit Interfaces feature bundles individual Ethernet links (Gigabit Ethernet or Ten Gigabit Ethernet) into a single logical link that provides the aggregate bandwidth of up to four physical links.
All LAN ports on a port channel must be the same speed and must all be configured as either Layer 2 or Layer 3 LAN ports. If a segment within a port channel fails, traffic previously carried over the failed link switches to the remaining segments within the port channel. Inbound broadcast and multicast packets on one segment in a port channel are blocked from returning on any other segment of the port channel.
Note |
The network device may impose its own limits on the number of bundled ports per port channel. |
The table below lists the features that are supported on Gigabit EtherChannel (GEC) bundles.
|
Cisco IOS XE Release |
Feature |
Bundle Interface |
|---|---|---|
|
2.5 |
Access control lists (ACLs) per bundle |
Supported |
|
All Ethernet routing protocols |
Supported |
|
|
Intelligent Service Gateway (ISG) IP sessions |
Not Supported |
|
|
Interface statistics |
Supported |
|
|
IP switching |
Supported |
|
|
IPv4: unicast and multicast |
Supported |
|
|
IPv6: unicast without load balancing across member links |
Supported |
|
|
IPv6: multicast |
||
|
Layer 2 Tunneling Protocol Version 3 (L2TPv3), IPinIP, Any Transport Over Multiprotocol Label Switching (MPLS) (AToM) tunnels |
Supported |
|
|
Layer 2 Tunneling Protocol Version 2 (L2TPv2) |
Not Supported |
|
|
MPLS (6PE) |
Supported |
|
|
Multicast VPN |
Not Supported |
|
|
VLANs |
Supported |
|
|
2.6 |
Virtual Private Network (VPN) Routing and Forwarding (VRF) |
Supported |
|
3.4 |
IPv6: unicast and multicast |
Supported |
|
3.6 |
Bidirectional Forwarding Detection (BFD) over GEC |
Supported |
|
3.7 |
Layer 2 Tunneling Protocol Version 2 (L2TPv2) |
Supported |
|
PPPoX (PPPoEoE, PPPoEoQinQ, PPPoVLAN) |
Supported |
|
|
3.7.6 |
Policy-based routing (PBR) over GEC |
Supported |
|
3.11 |
GEC over L2TPv3 |
Supported |
|
3.12 |
MPLS TE (Traffic Engineering) over GEC |
Supported |
Port channel interfaces that are configured improperly with LACP are disabled automatically to avoid network loops and other problems. To avoid configuration problems, observe these guidelines and restrictions:
Every port added to a port channel must be configured identically. No individual differences in configuration are allowed.
Bundled ports can be configured on different line cards in a chassis.
Maximum transmission units (MTUs) must be configured on only port channel interfaces; MTUs are propagated to the bundled ports.
QoS and committed access rate (CAR) are applied at the port level. Access control lists (ACLs) are applied on port channels.
MAC configuration is allowed only on port channels.
MPLS IP should be enabled on bundled ports using the mpls ip command.
Unicast Reverse Path Forwarding (uRPF) should be applied on the port channel interface using the ip verify unicast reverse-path command in interface configuration mode.
Cisco Discovery Protocol enable is not supported on the port channel interface.
All LAN ports in a port channel should be enabled. If you shut down a LAN port in a port channel, the shutdown is treated as a link failure and the traffic is transferred to one of the remaining ports in the port channel.
Create a port channel interface using the interface port-channel command in global configuration mode.
When an Ethernet interface has an IP address assigned, disable that IP address before adding the interface to the port channel. To disable an existing IP address, use the no ip address command in interface configuration mode.
The hold queue in command is valid only on port channel interfaces. The hold queue out command is valid only on bundled ports.
The LACP 1:1 redundancy feature provides an EtherChannel configuration with one active link and fast switchover to a hot standby link.
To use LACP 1:1 redundancy, you configure an LACP EtherChannel with two ports (one active and one standby). If the active link goes down, the EtherChannel stays up and the system performs fast switchover to the hot standby link. When the failed link becomes operational again, the EtherChannel performs another fast switchover to revert to the original active link.
For the LACP 1:1 redundancy feature to work correctly (especially the fast switchover capability) the feature needs to be enabled at both ends of the link.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
|
Step 3 |
interface port-channel channel-number Example: |
Identifies the interface port channel and enters interface configuration mode. |
|
Step 4 |
ip address ip-address mask Example: |
Assigns an IP address and subnet mask to the port channel interface. |
|
Step 5 |
exit Example: |
Returns to global configuration mode. |
|
Step 6 |
interface type slot/subslot/ port Example: |
Specifies the port to bundle. |
|
Step 7 |
no ip address Example: |
Disables the IP address on the port channel interface. |
|
Step 8 |
channel-group channel-group-number mode {active | passive } Example: |
Configures the interface in a channel group and sets it as active. In active mode, the port will initiate negotiations with other ports by sending LACP packets. |
|
Step 9 |
end Example: |
Returns to privileged EXEC mode. |
You must manually create a port channel logical interface. Perform this task to configure a port channel.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
|
Step 3 |
interface port-channel channel-number Example: |
Identifies the interface port channel and enters interface configuration mode. |
|
Step 4 |
lacp max-bundle max-bundles Example: |
Configures three active links on the port channel. The remaining links are in standby mode. Traffic is load-balanced among the active links. |
|
Step 5 |
ip address ip-address mask Example: |
Assigns an IP address and subnet mask to the EtherChannel. |
|
Step 6 |
end Example: |
Returns to privileged EXEC mode. |
|
Step 7 |
show running-config interface port-channel group-number Example: |
Displays the port channel configuration. |
This example shows how to verify the configuration:
Device# show running-config interface port-channel 10
Building configuration...
Current configuration: : 110 bytes
!
interface Port-channel10
ip address 172.31.52.10 255.255.255.0
no negotiation auto
lacp max-bundle 3
end
The EtherChannel Min-Links feature is supported on LACP EtherChannels. This feature allows you to configure the minimum number of member ports that must be in the link-up state and bundled in the EtherChannel for the port channel interface to transition to the link-up state. You can use the EtherChannel Min-Links feature to prevent low-bandwidth LACP EtherChannels from becoming active. This feature also causes LACP EtherChannels to become inactive if they have too few active member ports to supply your required minimum bandwidth.
To configure the EtherChannel Min-Links feature, perform this task in interface configuration mode:
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
|
Step 3 |
interface port-channel group-number Example: |
Selects an LACP port channel interface. |
|
Step 4 |
lacp min-bundle number Example: |
Configures the minimum number of bundle ports in the EtherChannel for the port channel interface to transition to the link-up state. Default is one. |
|
Step 5 |
end Example: |
Exits configuration mode. |
|
Step 6 |
show running-config interface port-channel group-number Example: |
Displays the port channel configuration. |
|
Step 7 |
show interfaces port-channelgroup-number Example: |
Note |
Although the EtherChannel Min-Links feature works correctly when configured only on one end of an EtherChannel, for best results, configure the same number of minimum links on both ends of the EtherChannel. |
Device> enable
Device# configure terminal
Device(config)# interface port-channel 1
Device(config-if)# lacp min-bundle 2
Device(config-if)# end
Perform this task to create a port channel with two bundled ports. You can configure a maximum of four bundled ports per port channel.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
|
Step 3 |
interface port-channel number Example: |
Specifies the port channel interface and enters interface configuration mode.
|
|
Step 4 |
ip address ip-address mask Example: |
Assigns an IP address and subnet mask to the port channel interface. |
|
Step 5 |
exit Example: |
Returns to global configuration mode. |
|
Step 6 |
interface type slot/subslot/ port Example: |
Specifies the port to bundle. |
|
Step 7 |
no ip address Example: |
Disables the IP address on the port channel interface. |
|
Step 8 |
channel-group channel-group-number mode {active | passive } Example: |
Assigns the interface to a port channel group and sets the LACP mode.
|
|
Step 9 |
exit Example: |
Returns to global configuration mode. |
|
Step 10 |
interface type slot/subslot/ port Example: |
Specifies the next port to bundle and places the CLI in interface configuration mode. |
|
Step 11 |
no ip address Example: |
Disables the IP address on the port channel interface. |
|
Step 12 |
channel-group channel-group-number mode {active | passive } Example: |
Assigns the interface to the previously configured port channel group.
|
|
Step 13 |
end Example: |
Returns to privileged EXEC mode. |
Device> enable
Device# configure terminal
Device(config)# interface port-channel 1
Device(config-if)# ip address 10.1.1.1 255.255.255.0
Device(config-if)#
Device(config-if)# no ip address
Device(config-if)# channel-group 1 mode active
Device(config-if)# exit
Device(config)#
Device(config-if)# no ip address
Device(config-if)# channel-group 1 mode active
Device(config-if)# end
For the LACP 1:1 redundancy feature, the LACP EtherChannel must contain exactly two links, of which only one is active. The link with the lower port priority number (and therefore a higher priority) will be the active link, and the other link will be in a hot standby state. The LACP max-bundle must be set to 1.
To configure the LACP 1:1 redundancy feature, perform this task in interface configuration mode:
| Command or Action | Purpose | |||
|---|---|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
||
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
||
|
Step 3 |
interface port-channel group-number Example: |
Selects an LACP port channel interface. |
||
|
Step 4 |
lacp fast-switchover Example: |
Enables the fast switchover feature for this EtherChannel. |
||
|
Step 5 |
lacp max-bundle max-bundles Example: |
Sets the maximum number of active member ports to 1.
|
||
|
Step 6 |
end Example: |
Exits configuration mode. |
||
|
Step 7 |
show running-config interface port-channel group-number Example: |
Displays the port channel configuration. |
||
|
Step 8 |
show etherchannel summary Example: |
Note |
For the LACP 1:1 redundancy feature, both ends of the EtherChannel must be enabled. |
This example shows how to configure an LACP EtherChannel with 1:1 redundancy. Because Fast Ethernet port 5/6 is configured with a higher port priority number (and therefore a lower priority) than the default of 32768, it will be the standby port.
Device> enable
Device# configure terminal
Device(config)# lacp system-priority 33000
Device(config)# interface range fastethernet 5/6 -7
Device(config-if)# channel-group 1 mode active
Device(config)# interface fastethernet 5/6
Device(config-if)# lacp port-priority 33000
Device(config)# interface port-channel 1
Device(config-if)# lacp fast-switchover
Device(config-if)# lacp max-bundle 1
Device(config-if)# end
Perform this task to set the LACP system priority and port priority. The system ID is the combination of the LACP system priority and the MAC address of a device. The port identifier is the combination of the port priority and port number.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
|
Step 3 |
lacp system-priority priority Example: |
Sets the system priority. |
|
Step 4 |
interface slot/subslot/ port Example: |
Specifies the bundled port on which to set the LACP port priority and enters interface configuration mode. |
|
Step 5 |
lacp port-priority priority Example: |
Specifies the priority for the physical interface.
|
|
Step 6 |
end Example: |
Returns to privileged EXEC mode. |
|
Step 7 |
show lacp sys-id Example: |
Displays the system ID (a combination of the system priority and the MAC address of the device). |
Device> enable
Device# configure terminal
Device(config)# lacp system-priority 200
Device(config)# interface gigabitethernet 0/1/1
Device(config-if)# lacp port-priority 500
Device(config-if)# end
This example shows how to verify the LACP configuration:
Device# show lacp sys-id
200.abdc.abcd.abcd| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
|
Step 3 |
interface type slot/subslot/port Example: |
Configures a Gigabit Ethernet interface. |
|
Step 4 |
channel-group channel-group-number mode {active | passive } Example: |
Adds an interface to a channel group and enters interface configuration mode.
|
|
Step 5 |
no channel-group channel-group-number Example: |
Removes the Gigabit Ethernet interface from channel group. |
|
Step 6 |
end Example: |
Returns to privileged EXEC mode. |
Perform this task to remove a Gigabit Ethernet port channel group from a physical port.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
|
Step 3 |
no interface port-channel number Example: |
Removes the specified port channel group from a physical port. |
|
Step 4 |
end Example: |
Returns to privileged EXEC mode. |
Device> enable
Device# configure terminal
Device(config)# no interface port-channel 1
Device(config)# end| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
|
Step 2 |
show lacp {number | counters | internal | neighbor | sys-id } Example: |
Displays internal device information. |
To verify and isolate a fault, start at the highest level maintenance domain and do the following:
Check the device error status.
When a error exists, perform a loopback test to confirm the error.
Run a traceroute to the destination to isolate the fault.
If the fault is identified, correct the fault.
If the fault is not identified, go to the next lower maintenance domain and repeat steps 1 through 4 at that maintenance domain level.
Repeat the first four steps, as needed, to identify and correct the fault.
To display Gigabit Ethernet port channel information, use the show interfaces port-channel command in user EXEC mode or privileged EXEC mode. The following example shows information about port channels configured on ports 0/2 and 0/3. The default MTU is set to 1500 bytes.
Device# show interfaces port-channel 1
Port-channel1 is up, line protocol is up
Hardware is GEChannel, address is 0013.19b3.7748 (bia 0000.0000.0000)
MTU 1500 bytes, BW 2000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 04:00:00
No. of active members in this channel: 2
Member 0 : GigabitEthernet , Full-duplex, 1000Mb/s Member 1 : GigabitEthernet , Full-duplex, 1000Mb/s
Last input 00:00:05, output never, output hang never
Last clearing of "show interface" counters 00:04:40
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Interface Port-channel1 queueing strategy: PXF First-In-First-Out
Output queue 0/8192, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
3 packets output, 180 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped outThe table below describes the significant fields shown in the display.
|
Field |
Description |
|---|---|
|
Port-channel1 is up, line protocol is up |
Indicates the bundle interface is currently active and can transmit and receive or it has been taken down by an administrator. |
|
Hardware is |
Hardware type (Gigabit EtherChannel). |
|
address is |
Address being used by the interface. |
|
MTU |
Maximum transmission unit of the interface. |
|
BW |
Bandwidth of the interface, in kilobits per second. |
|
DLY |
Delay of the interface, in microseconds. |
|
reliability |
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes. |
|
tx load rxload |
Transmit and receive load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes. The calculation uses the value from the bandwidth interface configuration command. |
|
Encapsulation |
Encapsulation type assigned to the interface. |
|
loopback |
Indicates if loopbacks are set. |
|
keepalive |
Indicates if keepalives are set. |
|
ARP type |
Address Resolution Protocol (ARP) type on the interface. |
|
ARP Timeout |
Number of hours, minutes, and seconds an ARP cache entry stays in the cache. |
|
No. of active members in this channel |
Number of bundled ports (members) currently active and part of the port channel group. |
|
Member <no. > Gigabit Ethernet: <no. /no. /no. > |
Number of the bundled port and associated Gigabit Ethernet port channel interface. |
|
Last input |
Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the Device. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched. |
|
output |
Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. This counter is updated only when packets are process-switched, not when packets are fast-switched. |
|
output hang |
Number of hours, minutes, and seconds since the interface was last reset because of a transmission that took too long. When the number of hours in any of the “last” fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed. |
|
last clearing |
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared. *** indicates that the elapsed time is too long to be displayed. 0:00:00 indicates that the counters were cleared more than 231 ms and less than 232 ms ago. |
|
Input queue |
Number of packets in the input queue and the maximum size of the queue. |
|
Queueing strategy |
First-in, first-out queueing strategy (other queueing strategies you might see are priority-list, custom-list, and weighted fair). |
|
Output queue |
Number of packets in the output queue and the maximum size of the queue. |
|
5 minute input rate 5 minute output rate |
Average number of bits and packets received or transmitted per second in the last 5 minutes. |
|
packets input |
Total number of error-free packets received by the system. |
|
bytes (input) |
Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system. |
|
no buffer |
Number of received packets discarded because there was no buffer space in the main system. Broadcast storms on Ethernet lines and bursts of noise on serial lines are often responsible for no input buffer events. |
|
broadcasts |
Total number of broadcast or multicast packets received by the interface. |
|
runts |
Number of packets that are discarded because they are smaller than the minimum packet size for the medium. |
|
giants |
Number of packets that are discarded because they exceed the maximum packet size for the medium. |
|
input errors |
Total number of no buffer, runts, giants, cyclic redundancy checks (CRCs), frame, overrun, ignored, and terminated counts. Other input-related errors can also increment the count, so that this sum might not balance with the other counts. |
|
CRC |
CRC generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits or other transmission problems on the data link. |
|
frame |
Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems. |
|
overrun |
Number of times the serial receiver hardware was unable to pass received data to a hardware buffer because the input rate exceeded the receiver’s capacity for handling the data. |
|
ignored |
Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be incremented. |
|
watchdog |
Number of times the watchdog receive timer expired. |
|
multicast |
Number of multicast packets received. |
|
packets output |
Total number of messages transmitted by the system. |
|
bytes (output) |
Total number of bytes, including data and MAC encapsulation, transmitted by the system. |
|
underruns |
Number of times that the far-end transmitter has been running faster than the near-end Device’s receiver can handle. |
|
output errors |
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this might not balance with the sum of the enumerated output errors, as some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories. |
|
collisions |
Number of messages retransmitted because of an Ethernet collision. A packet that collides is counted only once in output packets. |
|
interface resets |
Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within a certain interval. If the system notices that the carrier detect line of an interface is up but the line protocol is down, the system periodically resets the interface in an effort to restart that interface. Interface resets can also occur when an unrecoverable interface processor error occurred, or when an interface is looped back or shut down. |
|
babbles |
The transmit jabber timer expired. |
|
late collision |
Number of late collisions. Late collision happens when a collision occurs after transmitting the preamble. The most common cause of late collisions is that your Ethernet cable segments are too long for the speed at which you are transmitting. |
|
deferred |
Indicates that the chip had to defer while ready to transmit a frame because the carrier was asserted. |
|
lost carrier |
Number of times the carrier was lost during transmission. |
|
no carrier |
Number of times the carrier was not present during the transmission. |
|
PAUSE output |
Not supported. |
|
output buffer failures |
Number of times that a packet was not output from the output hold queue because of a shortage of shared memory. |
|
output buffers swapped out |
Number of packets stored in main memory when the output queue is full; swapping buffers to main memory prevents packets from being dropped when output is congested. The number is high when traffic is bursty. |
The following example shows how to configure Gigabit Ethernet ports 0/2 and 0/4into port channel 1 with LACP parameters.
Device> enable
Device# configure terminal
Device(config)# lacp system-priority 65535
Device(config)# interface port-channel 1
Device(config-if)# lacp max-bundle 1
Device(config-if)# ip address 10.1.1.1 255.255.255.0
Device(config-if)# exit
Device(config)# interface gigabitethernet 0/2
Device(config-if)# no ip address
Device(config-if)# lacp port-priority 100
Device(config-if)# channel-group 1 mode passive
Device(config-if)# exit
Device(config)# interface gigabitethernet 0/4
Device(config-if)# no ip address
Device(config-if)# lacp port-priority 200
Device(config-if)# channel-group 1 mode passive
Device(config-if)# end This example shows how to configure channel group number 5 and include it in the channel group.
Device1# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Device1(config)# interface port 5
Device1(config-if)#
*Aug 20 17:06:14.417: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to down
*Aug 20 17:06:25.413: %LINK-3-UPDOWN: Interface Port-channel5, changed state to down
Device1(config-if)#
Device1(config-if)#
Device1(config-if)# channel-group 5 mode active
Device1(config-if)#
*Aug 20 17:07:43.713: %LINK-3-UPDOWN: Interface GigabitEthernet, changed state to down
*Aug 20 17:07:44.713: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet, changed state to down
*Aug 20 17:07:45.093: %C10K_ALARM-6-INFO: ASSERT CRITICAL GigE Physical Port Link Down
*Aug 20 17:07:45.093: %C10K_ALARM-6-INFO: CLEAR CRITICAL GigE Physical Port Link Down
*Aug 20 17:07:47.093: %LINK-3-UPDOWN: Interface GigabitEthernet, changed state to up
*Aug 20 17:07:48.093: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet, changed state to up
*Aug 20 17:07:48.957: GigabitEthernet added as member-1 to port-channel5
*Aug 20 17:07:51.957: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to up
Device1(config-if)# end
Device1#
*Aug 20 17:08:00.933: %SYS-5-CONFIG_I: Configured from console by console
Device1# show etherchannel summary
Flags: D - down P/bndl - bundled in port-channel
I - stand-alone s/susp - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator
M - not in use, minimum links not met
u - unsuitable for bundling
w - waiting to be aggregated
d - default port
Number of channel-groups in use: 1
Number of aggregators: 1
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
1 Po1(RU) LACP Te0/3/0(bndl) Te0/3/1(hot-sby)
RU - L3 port-channel UP State
SU - L2 port-channel UP state
P/bndl - Bundled
S/susp - Suspended
Device1# show running-config int po1
Building configuration...
Current configuration : 87 bytes
!
interface Port-channel1
no ip address
lacp fast-switchover
lacp max-bundle 1
end
Device1# show lacp internal
Flags: S - Device is requesting Slow LACPDUs
F - Device is requesting Fast LACPDUs
A - Device is in Active mode P - Device is in Passive mode
Channel group 5
LACP port Admin Oper Port Port
Port Flags State Priority Key Key Number State
SA bndl 32768 0x5 0x5 0x43 0x3D
Device1# show interface port 5
Port-channel5 is up, line protocol is up
Hardware is GEChannel, address is 0014.a93d.4aa8 (bia 0000.0000.0000)
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 04:00:00
No. of active members in this channel: 1
Member 0 : GigabitEthernet , Full-duplex, 1000Mb/s
Last input 00:00:05, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Interface Port-channel5 queueing strategy: PXF First-In-First-Out
Output queue 0/8192, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
9 packets output, 924 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped outThe following example shows how to add an interface to a bundle:
Device1# show lacp internal
Flags: S - Device is requesting Slow LACPDUs
F - Device is requesting Fast LACPDUs
A - Device is in Active mode P - Device is in Passive mode
Channel group 5
LACP port Admin Oper Port Port
Port Flags State Priority Key Key Number State
SA bndl 32768 0x5 0x5 0x43 0x3D
Device1# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Device1(config)#
Device1(config-if)# channel-group 5 mode active
Device1(config-if)#
*Aug 20 17:10:19.057: %LINK-3-UPDOWN: Interface GigabitEthernet, changed state to down
*Aug 20 17:10:19.469: %C10K_ALARM-6-INFO: ASSERT CRITICAL GigE Physical Port Link Down
*Aug 20 17:10:19.473: %C10K_ALARM-6-INFO: CLEAR CRITICAL GigE Physical Port Link Down
*Aug 20 17:10:21.473: %LINK-3-UPDOWN: Interface GigabitEthernet, changed state to up
*Aug 20 17:10:21.473: GigabitEthernet taken out of port-channel5
*Aug 20 17:10:23.413: GigabitEthernet added as member-1 to port-channel5
*Aug 20 17:10:23.473: %LINK-3-UPDOWN: Interface Port-channel5, changed state to up
Device1(config-if)# end
Device1#
*Aug 20 17:10:27.653: %SYS-5-CONFIG_I: Configured from console by console
*Aug 20 17:11:40.717: GigabitEthernet added as member-2 to port-channel5
Device1# show lacp internal
Flags: S - Device is requesting Slow LACPDUs
F - Device is requesting Fast LACPDUs
A - Device is in Active mode P - Device is in Passive mode
Channel group 5
LACP port Admin Oper Port Port
Port Flags State Priority Key Key Number State
SA bndl 32768 0x5 0x5 0x43 0x3D
SA bndl 32768 0x5 0x5 0x42 0x3D
Device1#
Device1# show interface port 5
Port-channel5 is up, line protocol is up
Hardware is GEChannel, address is 0014.a93d.4aa8 (bia 0000.0000.0000)
MTU 1500 bytes, BW 2000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 04:00:00
No. of active members in this channel: 2
Member 0 : GigabitEthernet , Full-duplex, 1000Mb/s <---- added to port channel bundle
Member 1 : GigabitEthernet , Full-duplex, 1000Mb/s
Last input 00:00:00, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/150/0/0 (size/max/drops/flushes); Total output drops: 0
Interface Port-channel5 queueing strategy: PXF First-In-First-Out
Output queue 0/8192, 0 drops; input queue 0/150, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
104 packets output, 8544 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
The following example shows how to remove an interface from a bundle:
Device1# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Device1(config)#
Device1(config-if)# no channel-group 5 mode active
Device1(config-if)#
*Aug 20 17:15:49.433: GigabitEthernet taken out of port-channel5
*Aug 20 17:15:49.557: %C10K_ALARM-6-INFO: ASSERT CRITICAL GigE Physical Port Link Down
*Aug 20 17:15:50.161: %C10K_ALARM-6-INFO: CLEAR CRITICAL GigE Physical Port Link Down
*Aug 20 17:15:51.433: %LINK-3-UPDOWN: Interface GigabitEthernet, changed state to down
*Aug 20 17:15:52.433: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet, changed state to down
Device1(config-if)# end
Device1#
*Aug 20 17:15:58.209: %SYS-5-CONFIG_I: Configured from console by console
Device1#
*Aug 20 17:15:59.257: %C10K_ALARM-6-INFO: ASSERT CRITICAL GigE Physical Port Link Down
*Aug 20 17:15:59.257: %C10K_ALARM-6-INFO: CLEAR CRITICAL GigE Physical Port Link Down
Device1#
*Aug 20 17:16:01.257: %LINK-3-UPDOWN: Interface GigabitEthernet, changed state to up
*Aug 20 17:16:02.257: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet, changed state to up
Device1# show lacp internal
Flags: S - Device is requesting Slow LACPDUs
F - Device is requesting Fast LACPDUs
A - Device is in Active mode P - Device is in Passive mode
Channel group 5
LACP port Admin Oper Port Port
Port Flags State Priority Key Key Number State
SA bndl 32768 0x5 0x5 0x42 0x3D
The following example shows LACP activity that you can monitor by using the show lacp command.
Device1# show lacp internal
Flags: S - Device is requesting Slow LACPDUs
F - Device is requesting Fast LACPDUs
A - Device is in Active mode P - Device is in Passive mode
Channel group 5
LACP port Admin Oper Port Port
Port Flags State Priority Key Key Number State
SA bndl 32768 0x5 0x5 0x42 0x3D
Device1# show lacp 5 counters
LACPDUs Marker Marker Response LACPDUs
Port Sent Recv Sent Recv Sent Recv Pkts Err
---------------------------------------------------------------------
Channel group: 5
21 18 0 0 0 0 0
Device1# show lacp 5 internal
Flags: S - Device is requesting Slow LACPDUs
F - Device is requesting Fast LACPDUs
A - Device is in Active mode P - Device is in Passive mode
Channel group 5
LACP port Admin Oper Port Port
Port Flags State Priority Key Key Number State
SA bndl 32768 0x5 0x5 0x42 0x3D
Device1# show lacp 5 neighbor
Flags: S - Device is requesting Slow LACPDUs
F - Device is requesting Fast LACPDUs
A - Device is in Active mode P - Device is in Passive mode
Channel group 5 neighbors
Partner's information:
Partner Partner LACP Partner Partner Partner Partner Partner
Port Flags State Port Priority Admin Key Oper Key Port Number Port State
SP 32768 0011.2026.7300 11s 0x1 0x14 0x3C
Device1# show lacp counters
LACPDUs Marker Marker Response LACPDUs
Port Sent Recv Sent Recv Sent Recv Pkts Err
---------------------------------------------------------------------
Channel group: 5
23 20 0 0 0 0 0
Device1# show lacp sys-id
32768,0014.a93d.4a00The following example shows how to display the configuration of port-channel interface 1.
Device# show interface port-channel 1
Port-channel1 is up, line protocol is up
Hardware is GEChannel, address is 0013.19b3.7748 (bia 0000.0000.0000)
MTU 1500 bytes, BW 2000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 04:00:00
No. of active members in this channel: 2
Member 0 : GigabitEthernet , Full-duplex, 1000Mb/s Member 1 : GigabitEthernet , Full-duplex, 1000Mb/s
Last input 00:00:05, output never, output hang never
Last clearing of "show interface" counters 00:04:40
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Interface Port-channel1 queueing strategy: PXF First-In-First-Out
Output queue 0/8192, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
3 packets output, 180 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
Feedback