.png)
#
Lab 2 - Trunks
Construction of IDF-B on the second floor is finished. Configure the new switch and ensure layer 2 is properly spanned between floors.
Tip: Individual topology files are available in the diagrams folder on my Github
#
Configuration Tasks
#
VLAN Configuration
Create and configure the following VLANs on both switches:
- VLAN 10 - Sales Department
- VLAN 20 - Engineering Department
- VLAN 99 - Network Management
#
Host & Access Port Configuration
#
Switchport Configuration
- Configure the inter-switch link (Eth0/3 on both switches) as an 802.1Q trunk to carry only VLANs 10,20, and 99.
- Configure VLAN 99 SVI for sea-a1-asw1 - 10.1.99.10/24
- Configure VLAN 99 SVI for sea-b1-asw1 - 10.1.99.20/24
#
Success Criteria
- Bob and Linda can ping each other (both in VLAN 10)
- Alice cannot ping Bob or Linda (Different VLANs)
- sea-a1-asw1 can ping sea-b1-asw1 VLAN 99 SVI
- Steve can both VLAN SVIs
- VLAN database consistent across both switches
- SSH to sea-a1-asw1 from Steve
- SSH to sea-b1-asw1 from sea-a1-asw1
- Configure port descriptions for all interfaces
#
Verification Commands
eos
# Show VLAN configuration
show vlan brief
# Show trunk interfaces and allowed VLANs
show interfaces trunk
# Show interface status and mode
show interfaces status
# Show MAC address table
show mac address-table [dynamic]
#
Questions to Explore
- Why do we need trunks? What problem do they solve?
- Why do we specify the VLANs on a trunk instead of allowing all?
- Run
show spanning-tree vlan 10before and after you remove it from the trunk on one side, what changes? - If Linda can't ping Bob, what are the possible causes?
"Host Access"
If SSH isn't working: docker exec -it <container-name> bash
Configure static IP: sudo ip addr add 10.1.10.10/24 dev eth1