Skip to main content

EtherChannel

 

EtherChannel Overview:

  • EtherChannel groups multiple trunk, access, tunnel, or routed ports into one logical port.
  • Configuration settings are placed in the port-channel interface.
  • Layer 2 vs. Layer 3: Member interfaces need to be in the correct layer before being associated with a port-channel.

Useful Commands:

  • show lacp neighbor
  • show etherchannel summary
  • show lacp sys-id
  • clear lacp counters to reset LACP counters.

PAgP (Port Aggregation Protocol):

  • PAgP silent mode: Operates even with non-PAgP devices.
  • Non-silent mode: Faster connection with PAgP-compliant switches.

MLAG (Multi-Chassis Link Aggregation Protocol):

  • Synchronization happens between switches over the control plane.
  • On VSS (Virtual Switching System), control plane is synchronized over Virtual Switch Link (VSL), typically 2x10G LAG.

vPC (Virtual PortChannel):

  • Available on Nexus Series switches.
  • Control plane synchronized over the vPC Peer Link (2x10G LAG).
  • Two independent control planes and two independent management planes.

EtherChannel On Mode:

  • Used to manually configure an EtherChannel without negotiation.
  • Ports in on mode must have compatible characteristics (speed, duplex).

LACP (Link Aggregation Control Protocol):

  • LACP fast: LACP packets sent every 1 second, removing links faster if a failure is detected.
  • LACP slow: Default with packets sent every 30 seconds.
  • LACP rate fast command enables fast mode.

Load Balancing in EtherChannel:

  • You configure load-balancing using the port-channel load-balance command.
  • Options include balancing by source/destination IP, MAC, or both.

Minimum & Maximum Number of Member Interfaces:

  • Minimum links: The EtherChannel can be configured to become active only when a certain number of member links are up (port-channel min-links).
  • Maximum links: Ensures a set number of active interfaces based on powers of two, useful for load balancing (lacp max-bundle).

LACP Priorities:

  • System priority: Determines which switch is the master in selecting active links.
  • Interface priority: Used by the master switch to choose active member links.

EtherChannel Misconfiguration Guard:

  • Detects EtherChannel misconfigurations (like mismatched channel parameters or missing EtherChannel on the other device).
  • Places misconfigured interfaces into error-disabled state.
  • Enabled with the command spanning-tree etherchannel guard misconfig.

Switch Polarization:

  • Occurs when a switch selects the same link repeatedly in a multi-link EtherChannel. Load balancing effectiveness depends on the hashing algorithm and having a power-of-two number of links (e.g., 2, 4, 8).

Load-Balancing Methods:

  • Common methods include source and destination IP/MAC addresses.
  • The command show etherchannel port shows load distribution in hex format.

Comments

Popular posts from this blog

Basic MPLS BGP and L3VPN Lab Setup

In this lab, we’ve set up a basic MPLS, BGP, and L3VPN environment, which is a great foundation for understanding how service providers build scalable networks. The lab uses the EVE-NG simulator along with Router IOS C7200-ADVENTERPRISEK9-M, Version 15.2(4)M8 to emulate a realistic MPLS environment. Below is a summary of the key components and roles of each router in the lab. MPLS Core Routers : The MPLS core consists of the routers responsible for label switching and forwarding customer traffic through the network: PE1 (Provider Edge 1) : Connects customer networks to the MPLS core and handles both MPLS and BGP routing. It also hosts VRF (Virtual Routing and Forwarding) instances for customers. PE2 (Provider Edge 2) : Functions similarly to PE1, connecting another customer network to the MPLS core. P1 (Core Router 1) and P2 (Core Router 2) : These routers serve as MPLS core routers and handle label switching but do not store or process customer routes directly. They simply f

OSPF Adjacency Stuck in EXSTART on Cisco IOS XR – Issue and Solution

In a recent lab setup using Cisco IOS XR on EVE-NG, I faced a common but frustrating issue with OSPF adjacencies getting stuck in the EXSTART state. After spending considerable time troubleshooting interface MTUs and configurations, I discovered that the root cause was related to the virtual network interface type being used. This post outlines the issue, troubleshooting steps, and the eventual solution that got everything working. Issue: While configuring OSPF between two routers running Cisco IOS XR in my lab, OSPF adjacencies were getting stuck in the EXSTART state. I verified that interface configurations, MTU settings, and OSPF parameters were correct, but the problem persisted. I tried adjusting the MTU size, using the mtu-ignore command, and even checked for ACLs, but nothing seemed to resolve the issue. Troubleshooting Steps: MTU Settings: I started by verifying that both sides of the OSPF adjacency had matching MTUs. I used the default MTU and even tried different values wit

How to Properly Clone an EVE-NG Lab with Configurations

Cloning labs in EVE-NG is a great way to duplicate setups and expand or experiment on a new copy without affecting the original lab. However, if not done correctly, the cloned lab may only copy the topology without configurations. In this guide, I’ll show you how to properly clone a lab in EVE-NG with all configurations using the EVE-NG GUI . Follow these steps to ensure that both the topology and router configurations are retained when cloning your lab. Steps to Clone an EVE-NG Lab with Configurations Save Running Configuration on All Devices In your original lab, make sure all devices have their configurations saved to NVRAM. Go into the CLI of each router and run the command: copy running-config startup-config Export All Configurations (CFGs) On the left sidebar in the EVE-NG Web UI , click on the "More Actions" option. Then select "Export all CFGs" . This step exports the configurations of all devices in the lab. Shutdown All Devices After exporting the confi