Cisco Port-Channel Generator

Generate consistent IOS or NX-OS LACP port-channel configuration with member-interface safeguards.

Config generator Cisco Runs in your browser

Result

Port-channel
10
Members
2
Negotiation
LACP active
Cisco IOS configuration
interface range TenGigabitEthernet1/0/47 , TenGigabitEthernet1/0/48
 description NETVORX-LAG-MEMBER
 channel-group 10 mode active
 no shutdown
interface Port-channel10
 description NETVORX-PORT-CHANNEL
 switchport
 switchport mode trunk
 switchport trunk native vlan 999
 switchport trunk allowed vlan 10,20,100-110
 no shutdown
Verification commands
show etherchannel summary
show interfaces Port-channel10
show lacp neighbor
Member speed, duplex, MTU, switchport mode and VLAN settings must match on both ends.

About Cisco Port-Channel Generator

Build a consistent EtherChannel configuration for IOS/IOS XE or NX-OS, including member interfaces, LACP mode and Layer 2 or Layer 3 settings. The generated member and logical-interface commands stay together for easier peer review.

Bundling requirements

Every physical member must use compatible speed, duplex, MTU and switching parameters. LACP active mode is normally safer than a static bundle because it detects an incompatible or disconnected peer before forwarding traffic.

Change procedure

Validate the remote configuration and cabling before enabling members. Add links in a controlled maintenance window, confirm that LACP reports them bundled, then test forwarding and spanning tree. A member that is suspended or individual usually indicates a mismatch. For Layer 2 trunks, compare native and allowed VLAN lists on both ends. For routed bundles, verify addressing, routing adjacencies and MTU before moving production traffic.

Common use cases

  • Create a redundant switch uplink.
  • Bundle server or firewall interfaces with LACP.
  • Generate a routed port-channel between core devices.

Edge cases and gotchas

  • Apply during a maintenance window to avoid loops or traffic loss.
  • Verify the remote side uses compatible mode and identical VLAN/MTU settings.
  • Do not paste the template blindly into interfaces carrying production traffic. Review existing commands, spanning-tree role, port security, QoS and peer configuration, then keep console or out-of-band access available for rollback.

Frequently asked questions

Should I use active, passive or on?
Use active for most LACP deployments. Passive requires an active peer, while on creates a static bundle with no negotiation protection. Active on both ends is valid and usually provides the clearest operational behaviour.
Why is a member suspended?
Common causes include mismatched LACP mode, VLAN policy, interface type, speed, MTU or an incompatible remote bundle. Compare both ends before forcing a member online.