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.
Labels:

Comments

Post a Comment

Popular posts from this blog

How to import Putty Saved Connections to mRemoteNG

Just started using mRemoteNG and its being very cool to connect to different remote connection with different protocols e.g Window Remote Desktop, VNC to Linux, SSH, HTTP connection etc. from a single application. As new user I configured some remote desktop connection which was quite easy to figure out. But when I wanted to add SSH connections, it came in my mind to import all of the saved connections in the putty. But I couldn't figure it out how can it be done, though it was quite easy and here are the steps. Open your mRemoteNG Create a folder if you want segregation of multiple networks Create a new connection Enter the IP address of remote server under connection in Config pane Under the config pane, select protocol " SSH version 2 ".  Once you select protocol to SSH version 2 you are given option to import putty sessions, as shown in the snap below. In the above snap, I have imported CSR-AWS session from my saved sessions in Putty.
1 comment
Read more

Understanding PKI The Complete Process Explained

The Complete Public Key Infrastructure (PKI) Process: From Key Generation to Certificate Verification Public Key Infrastructure (PKI) is the backbone of secure communication on the internet. It ensures that sensitive data exchanged between clients and servers remains private and authentic. This blog post will guide you through the entire PKI process, from generating keys to verifying certificates and ensuring they haven't been revoked. 1. Key Pair Generation The first step in PKI is generating a public-private key pair using an asymmetric cryptographic algorithm, such as RSA or ECDSA: The private key is securely stored on the server and never shared. The public key is included in the certificate and shared with the Certificate Authority (CA) during the certificate request process. This key pair enables encryption and decryption, which are essential for secure communication. 2. Creating a Certificate Signing Request (CSR) The server creates a Certificate Signing Request (CSR) to...
Post a Comment
Read more

BGP Soft Reconfiguration vs. Route Refresh: Key Differences and Best Practices

In BGP (Border Gateway Protocol), managing route updates and reapplying new policies can sometimes be challenging, especially if you want to avoid resetting the BGP session. Two methods allow you to update routing policies without tearing down the session: BGP Soft Reconfiguration and BGP Route Refresh . While both methods serve the same purpose, they work differently and have distinct impacts on your router's resources. This post explains the key differences between Soft Reconfiguration and Route Refresh , when to use each, and why Route Refresh is preferred in most modern networks. 1. What is BGP Soft Reconfiguration? BGP Soft Reconfiguration is an older method of applying new policies (like route maps, filters, or prefix lists) without resetting the BGP session. It works by storing a local copy of all the routes received from a BGP neighbor before applying inbound policies. This local route copy allows the router to reprocess the routes when a policy change occurs. How So...
Post a Comment
Read more