Sunday, May 10, 2026

Cisco Nexus Port-Channel Configuration Guide | EtherChannel and Trunking on NX-OS

Cisco Nexus Port-Channel Configuration Guide | EtherChannel on NX-OS

Cisco Nexus Port-Channel Configuration Guide

This is Part 2 of the Cisco Nexus NX-OS configuration series. In Part 1, we configured VLANs and trunk ports between NX-01, NX-02, and NX-03.

Part 1: Step-by-Step Cisco Nexus Switch Configuration

Part 3 - Cisco Nexus LACP Port-Channel Configuration


Table of Contents


1. Introduction to Port-Channels

A Port-Channel combines multiple physical interfaces into a single logical interface.

Cisco also calls this:

  • EtherChannel
  • Link Aggregation
  • Port Aggregation

Why Port-Channels are Important

  • Increases bandwidth
  • Provides redundancy
  • Improves availability
  • Simplifies management
  • Prevents spanning-tree blocking

Without Port-Channel

Spanning Tree Protocol blocks redundant links.

Link 1 = Forwarding
Link 2 = Blocking

With Port-Channel

All links actively forward traffic.

Link 1 = Active
Link 2 = Active
Combined as Port-Channel 23

2. Task 1 - Default Trunk Interfaces

Before configuring the Port-Channel, we must reset the interfaces to their default state.

This ensures:

  • No conflicting configurations
  • No previous channel-group settings
  • Clean configuration baseline

NX-01


configure terminal

default interface ethernet1/1-4

end

NX-02


configure terminal

default interface ethernet1/1-4

end

NX-03


configure terminal

default interface ethernet1/1-4

end

CLI Output Example

Click to Expand CLI Output
NX-02(config)# default interface ethernet1/1-4
WARNING: This command will reset interface configuration.
Continue? [yes/no]: yes

3. Task 2 - Configure Port-Channel 23

Now we will configure interfaces E1/3 and E1/4 between NX-02 and NX-03 as a Port-Channel.

Important Requirement

The task specifically states:

  • No negotiation protocol
  • Static EtherChannel
  • Mode ON

What Does Mode ON Mean?

Mode ON creates a static EtherChannel.

No LACP or PAgP negotiation occurs.

Static EtherChannel Characteristics

Feature Static Mode ON
Negotiation No
Protocol None
Compatibility Check Minimal
Risk Level Higher

NX-02 Configuration


configure terminal

interface ethernet1/3-4
 channel-group 23 mode on
 no shutdown

end
copy running-config startup-config

NX-03 Configuration


configure terminal

interface ethernet1/3-4
 channel-group 23 mode on
 no shutdown

end
copy running-config startup-config

CLI Output Example

Click to Expand CLI Output
NX-02(config)# interface ethernet1/3-4
NX-02(config-if-range)# channel-group 23 mode on
NX-02(config-if-range)# no shutdown
NX-02(config-if-range)# end

4. Task 3 - Configure Port-Channel as Trunk

Once the physical interfaces join the Port-Channel, configuration should be applied on the logical Port-Channel interface itself.

This is very important.

Why Configure the Port-Channel Interface?

  • Centralized management
  • Consistency across member links
  • Simplified administration
  • Automatic inheritance by members

NX-02 Configuration


configure terminal

interface port-channel23
 switchport
 switchport mode trunk
 no shutdown

end

NX-03 Configuration


configure terminal

interface port-channel23
 switchport
 switchport mode trunk
 no shutdown

end

Verification Output

Click to Expand Port-Channel Verification
NX-02# show running-config interface port-channel23

interface port-channel23
 switchport
 switchport mode trunk
 no shutdown

5. Task 4 - Configure Load Balancing

Port-Channels use hashing algorithms to determine how traffic is distributed across links.

In this lab, we will use:

src-dst ip

What Does Source-Destination IP Mean?

Traffic distribution is calculated using:

  • Source IP Address
  • Destination IP Address

This creates better traffic distribution across links.


NX-02 Configuration


configure terminal

port-channel load-balance src-dst ip

end

NX-03 Configuration


configure terminal

port-channel load-balance src-dst ip

end

Verification Command


show port-channel load-balance

CLI Output Example

Click to Expand CLI Output
NX-02# show port-channel load-balance

System config:
Non-IP: source-dest-mac
IPv4: source-dest-ip
IPv6: source-dest-ip

6. Task 5 - Verify Port-Channel Status

Verification is one of the most important skills in networking.

Never assume configuration works without verification.

Verification Command


show port-channel summary

NX-02 Example Output

Click to Expand NX-02 Verification
NX-02# show port-channel summary

Flags:  D - Down
        P - Up in port-channel

Group Port-Channel Type Protocol Member Ports
-----+------------+----+--------+--------------------
23    Po23(SU)     Eth NONE     Eth1/3(P) Eth1/4(P)

NX-03 Example Output

Click to Expand NX-03 Verification
NX-03# show port-channel summary

Flags:  D - Down
        P - Up in port-channel

Group Port-Channel Type Protocol Member Ports
-----+------------+----+--------+--------------------
23    Po23(SU)     Eth NONE     Eth1/3(P) Eth1/4(P)

7. EtherChannel Concepts

Types of EtherChannel

Type Protocol Vendor Support
Mode ON None Universal
PAgP Cisco Proprietary Cisco Only
LACP IEEE 802.3ad Multi-Vendor

Modern Recommendation

Modern networks typically prefer:

  • LACP
  • Dynamic negotiation
  • Better error handling
  • Improved interoperability

8. Load Balancing Mathematics

Bandwidth Aggregation Formula

If:

\[ n = Number\ of\ Links \]

\[ B = Bandwidth\ per\ Link \]

Then:

\[ Total\ Bandwidth = n \times B \]

Example:

\[ n = 2 \]

\[ B = 10Gbps \]

\[ Total = 2 \times 10 \]

\[ Total = 20Gbps \]

Hashing Logic

Traffic distribution uses hashing:

\[ Hash = f(SourceIP + DestinationIP) \]

Example:

\[ Hash(10.1.1.1 + 10.2.2.2) \]

The resulting hash determines which link carries the traffic flow.

Flow Distribution

Suppose:

\[ Total\ Flows = 100 \]

And:

\[ Links = 2 \]

Average flows per link:

\[ \frac{100}{2}=50 \]

Each link ideally handles 50 flows.


9. Nexus vs Traditional IOS EtherChannel

Feature Cisco IOS Cisco NX-OS
Interface Syntax Fa0/1 Eth1/1
Port-Channel Interface Port-channel1 port-channel1
Data Center Features Limited Advanced
vPC Support No Yes
Automation APIs Limited Extensive

Traditional IOS Example


interface range g0/1 - 2
 channel-group 1 mode active

NX-OS Example


interface ethernet1/3-4
 channel-group 23 mode on

10. Modern NX-OS Practices

Although static mode ON still works, modern data center best practices prefer:

  • LACP
  • vPC
  • EVPN multihoming
  • Automation-driven deployment

Modern LACP Configuration


configure terminal

feature lacp

interface ethernet1/3-4
 channel-group 23 mode active
 no shutdown

interface port-channel23
 description UPLINK_TO_NX03
 switchport
 switchport mode trunk
 switchport trunk allowed vlan 10,20
 spanning-tree port type network
 no shutdown

Why Modern LACP is Better

  • Automatic negotiation
  • Error detection
  • Consistency checks
  • Better scalability
  • Industry standard

11. Troubleshooting

Problem: Port-Channel Down

Possible causes:

  • Speed mismatch
  • Duplex mismatch
  • VLAN mismatch
  • Trunk mismatch
  • Incorrect channel-group mode

Verification Commands


show port-channel summary

show interface status

show running-config interface port-channel23

show lacp neighbor

show spanning-tree

Problem: Member Ports Suspended

Usually caused by configuration inconsistency.

Check Interface Consistency


show port-channel compatibility-parameters

Complete Final Configuration


configure terminal

default interface ethernet1/1-4

interface ethernet1/3-4
 channel-group 23 mode on
 no shutdown

interface port-channel23
 switchport
 switchport mode trunk
 no shutdown

port-channel load-balance src-dst ip

end

copy running-config startup-config

Key Takeaways

✔ Port-Channels combine multiple physical links into one logical interface.

✔ Static mode ON does not use negotiation protocols.

✔ LACP is the preferred modern industry standard.

✔ Load balancing distributes traffic using hashing algorithms.

✔ Source-Destination IP hashing improves traffic distribution.

✔ Always verify EtherChannel status after configuration.


Conclusion

In this Cisco Nexus Port-Channel guide, we configured EtherChannel between NX-02 and NX-03 using static mode ON.

We configured:

  • Default interfaces
  • Port-Channel 23
  • Trunking on the Port-Channel
  • Load balancing based on source and destination IP
  • Verification commands

Although static EtherChannels are still supported, modern data center architectures typically prefer LACP and automation-driven deployment models for improved scalability and reliability.

No comments:

Post a Comment

Featured Post

How HMT Watches Lost the Time: A Deep Dive into Disruptive Innovation Blindness in Indian Manufacturing

The Rise and Fall of HMT Watches: A Story of Brand Dominance and Disruptive Innovation Blindness The Rise and Fal...

Popular Posts