Configuring VLANs, Trunk Ports, and EtherChannel on Cisco Switches
This guide demonstrates how to create VLANs, assign them to interface ranges, configure trunk ports, and set up EtherChannel for redundant parallel connections on Cisco switches using CLI commands.
This article shows step‑by‑step CLI commands to create VLAN 2 and VLAN 3 on two Cisco switches, name the VLANs, and assign them to specific fast‑ethernet interface ranges using switchport access vlan.
Example commands for Switch0 include:
Switch0(config)#vlan 2 Switch0(config-vlan)#name wangluobu Switch0(config-vlan)#interface range fastethernet0/1-2 Switch0(config-if-range)#switchport access vlan 2 Switch0(config)#vlan 3 Switch0(config-vlan)#name xiaoshou Switch0(config-vlan)#interface range fastethernet0/3-4 Switch0(config-if-range)#switchport access vlan 3Similar commands are repeated for Switch1, followed by show vlan to verify the VLAN configuration.
To configure a trunk port on Switch1, the guide uses:
Switch1(config)#interface fastEthernet 0/5 Switch1(config-if)#switchport mode trunkThe resulting trunk status can be displayed with: Switch#show interface fastEthernet 0/5 switchport For redundancy, multiple ports are bundled into an EtherChannel. The commands on Switch0 are:
Switch0(config)#interface range fastethernet 0/6-7 Switch0(config-if-range)#switchport mode trunk Switch0(config-if-range)#channel-group 1 mode onAfter configuration, the EtherChannel summary can be checked with: show etherchannel summary Additional steps include shutting down interfaces and testing connectivity with a ping to 192.168.1.4 to confirm the setup.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Practical DevOps Architecture
Hands‑on DevOps operations using Docker, K8s, Jenkins, and Ansible—empowering ops professionals to grow together through sharing, discussion, knowledge consolidation, and continuous improvement.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
