An access switch without a VLAN IP cannot route or communicate within that VLAN; configuring a Switch Virtual Interface (SVI) with an IP address is required for Layer 3 connectivity.

Understanding the Issue

When a VLAN on a switch does not have an IP address assigned, devices in that VLAN cannot communicate beyond the local broadcast domain, and DHCP requests may fail if the switch is expected to route traffic to a DHCP server . This is common on Layer 2 switches where VLANs exist but no SVI is configured.

Configuring a VLAN IP

To assign an IP to a VLAN on a Cisco switch:

1. Enter global configuration mode:

Switch> enableSwitch# configure terminal

1. Create or select the VLAN interface:

Switch(config)# interface vlan 10

1. Assign an IP address and subnet mask:

Switch(config-if)# ip address 192.168.10.1 255.255.255.0

1. Enable the interface:

Switch(config-if)# no shutdown

1. Verify the configuration:

Switch# show ip interface brief

This ensures the VLAN interface is active and reachable .

Common Troubleshooting Steps

• Check VLAN existence: Ensure the VLAN is created on the switch and ports are assigned correctly using show vlan brief .
• Switchport mode: Access ports must be set to the correct VLAN:

Switch(config)# interface gig1/0/1Switch(config-if)# switchport mode accessSwitch(config-if)# switchport access vlan 10

• DHCP relay: If the DHCP server is on a different VLAN, configure ip helper-address on the VLAN interface to forward DHCP requests .
• Trunk ports: Ensure trunk ports allow the VLAN if connecting to other switches or routers:

Switch(config)# interface gig1/0/24Switch(config-if)# switchport mode trunkSwitch(config-if)# switchport trunk allowed vlan 10

• Connectivity testing: Ping the VLAN IP from a host in the same VLAN to confirm reachability and check the MAC address table with show mac address-table vlan 10 .

Additional Considerations

• On Layer 2 switches, the VLAN IP is only for management or routing via a router-on-a-stick setup; it does not provide Layer 3 routing by itself .
• Ensure no IP conflicts exist and that the subnet mask matches the network design.
• For multi-vendor environments (e.g., TP-Link or Omada), verify that VLAN tagging and PVID settings match the router or DHCP server configuration . By properly configuring the VLAN interface with an IP and ensuring correct port assignments, the access switch will support inter-VLAN communication and DHCP functionality.