Troubleshoot a VLAN with no connectivity using Cisco Catalyst access-port, trunk, STP, MAC-table, ARP, and gateway checks.
Test the nearest boundary first
Creating a VLAN does not place every required port and gateway into a working path. Begin at the affected client and move toward its gateway. Separate same-VLAN communication from communication to another subnet. The first failing boundary determines which part of the configuration needs attention.
Example topology and platform
The example uses VLAN 20, client 10.20.0.25/24, gateway 10.20.0.1, and Cisco Catalyst IOS XE 17.12 command style. Replace the interface names with those on your switch. Aruba AOS-CX has its own command syntax and VLAN model, so use the relevant platform reference when applying this method there.
Check the client-facing port
show interfaces status
show interfaces GigabitEthernet1/0/10 switchport
show vlan brief
show mac address-table vlan 20
Interpret the access-side evidence
Confirm the physical link, operational mode, and access VLAN. Generate traffic from the client and look for its MAC address on the expected port in VLAN 20. A missing MAC entry points toward the endpoint, cabling, access configuration, or a control that has prevented forwarding. An unexpected port can reveal a topology or cabling assumption.
Follow the VLAN across the uplink
show interfaces trunk
show interfaces GigabitEthernet1/0/48 switchport
show spanning-tree vlan 20
Read the operational state
Check both ends of every trunk in the path. Distinguish configured VLAN allowance from active and forwarding membership. Confirm the expected spanning-tree forwarding path and native VLAN agreement. If the uplink is a port channel, inspect its logical interface and member state. A configured trunk on one device does not establish the state of the peer.
Verify the gateway
show ip interface brief
show interfaces Vlan20
show ip arp 10.20.0.25
show ip route 10.30.0.0
Separate gateway reachability from routing
On the Layer 3 device, confirm the SVI address and operational state. Check the client mask and gateway, then test local gateway reachability. If the gateway works and a remote subnet fails, inspect routing, ACLs, and the remote return path. If ARP fails between a client and its on-link gateway, inspect Layer 2 reachability and addressing before changing remote routes.
Common patterns
| Observation | Next check |
|---|---|
| Only one client fails | Endpoint addressing, authentication state, and its access port |
| One VLAN fails across an uplink | Allowed, active, and STP forwarding VLANs |
| Local VLAN works but gateway fails | SVI, mask, ARP, and duplicate addressing |
| Gateway works but remote networks fail | Routing, ACLs, firewall policy, and return path |
Verify the repair
Repeat client-to-client, client-to-gateway, and client-to-application tests. Confirm the expected MAC and ARP entries, then check another VLAN on the same uplink. Preserve the original configuration and record exactly which link or setting broke the path.