A network engineer configures an interface on a Cisco Catalyst switch operating in VTP Client mode by executing the command switchport access vlan 50 under interface configuration mode. Upon verifying the port status using the show interfaces gigabitethernet 1/0/1 switchport command, the output indicates Access Mode VLAN: 50 (Inactive). What is the root cause of this inactive status, and how should it be resolved?
- VLAN 50 does not exist in the VLAN database propagated by the VTP Server; VLAN 50 must be created on the VTP Server switch.Cevap
- BThe local switch failed to automatically create VLAN 50 because global configuration mode requires the explicit command vlan 50 on the VTP Client switch.
- CThe interface is experiencing a native VLAN mismatch because the switchport mode access command was omitted during interface configuration.
- DThe interface was automatically placed in a blocking state because PortFast was enabled on an active interswitch trunk connection.
Cevap
VLAN 50 does not exist in the VLAN database propagated by the VTP Server; VLAN 50 must be created on the VTP Server switch.
When a port is assigned to an access VLAN on a Cisco Catalyst switch, the VLAN must exist in the VLAN database for the port to forward traffic. On switches in VTP Server or VTP Transparent mode, executing 'switchport access vlan X' automatically creates VLAN X in the database if it does not already exist. However, switches operating in VTP Client mode cannot modify the local VLAN database directly or auto-create VLANs. If the assigned VLAN does not exist in the VTP database advertised by the VTP Server, the switchport output displays the access mode VLAN as '(Inactive)'. To resolve this issue, VLAN 50 must be created on the VTP Server so that it is propagated to the VTP Client switch.
Adım Adım Çözüm
Anahtar Kavram
VLAN Database Inactive Status and VTP Client Behavior