Cisco+lab+162 -

Note: Your specific lab manual may use different IP ranges (e.g., 172.16.10.0), but the logic remains identical. We will approach this in three phases: Access Layer, Trunk Layer, and Inter-VLAN Routing. Phase 1: Access Layer Configuration (Switches SW1 and SW2) The first goal is to place PCs into the correct VLANs. VLANs must be created in the switch’s database before assignment.

First, enable IP routing:

Configure the trunk ports toward the access switches: cisco+lab+162

interface gigabitEthernet 0/0.10 encapsulation dot1Q 10 ip address 192.168.10.1 255.255.255.0 interface gigabitEthernet 0/0.20 encapsulation dot1Q 20 ip address 192.168.20.1 255.255.255.0 Note: Your specific lab manual may use different

ping 192.168.20.3 Success (!!!) or (!.). If it fails, proceed to the troubleshooting section. Common Troubleshooting in Cisco Lab 162 Even seasoned engineers get stuck here. Here are the top 5 failure points in Lab 162: VLANs must be created in the switch’s database

interface gigabitEthernet 0/1 switchport trunk encapsulation dot1q switchport mode trunk switchport trunk allowed vlan 10,20 no shutdown Run show interfaces trunk . You should see the ports listed with Native VLAN "1" and allowed VLANs "10,20". If this output is blank, the trunk did not form—check for mismatched encapsulation or cabling. Phase 3: Inter-VLAN Routing (The "162" Challenge) Now, PC1 (VLAN 10) and PC3 (VLAN 20) cannot ping each other because they are on different subnets. To enable routing, we need a Layer 3 gateway. Lab 162 usually uses a Multilayer Switch (MLS).