Switch(config)# no vlan 40\n<\/code><\/pre>\nTo delete multiple non-contiguous VLANs at once, separate the IDs with commas (without spaces):<\/p>\n
Switch(config)# no vlan 10,20,30\n<\/code><\/pre>\nTo delete a contiguous block of VLANs, specify the range using a hyphen:<\/p>\n
Switch(config)# no vlan 50-60\n<\/code><\/pre>\nYou can also combine discrete IDs and ranges in a single statement:<\/p>\n
Switch(config)# no vlan 15,25,70-75\n<\/code><\/pre>\n<\/span>Step 4: Verify the Global Removal<\/span><\/h3>\nExit configuration mode and verify that the target VLAN IDs no longer appear in the active database:<\/p>\n
Switch(config)# end\nSwitch# show vlan brief\n<\/code><\/pre>\nThe output should confirm that the deleted VLANs have been expunged from the switch’s active broadcast domains.<\/p>\n
<\/span>Step 5: Save the Running Configuration<\/span><\/h3>\nCommit your changes to non-volatile RAM (NVRAM) so they persist across reboots:<\/p>\n
Switch# copy running-config startup-config\n<\/code><\/pre>\n
\n<\/span>What Happens to Access Ports When Their VLAN Is Deleted?<\/span><\/h2>\nA common misconception among administrators is that deleting a VLAN returns its assigned access ports to the default VLAN (VLAN 1). In Cisco IOS and IOS-XE, this is not what occurs.<\/p>\n
<\/span>Frequently Asked Questions<\/span><\/h3>\nDo access ports automatically revert to VLAN 1 after VLAN deletion?<\/h4>\n
No. Cisco IOS does not automatically reassign an orphaned port to VLAN 1 or any other active VLAN. The interface retains its configured association (for example, switchport access vlan 10<\/code>) inside the running configuration, but the underlying broadcast domain no longer exists in the VLAN database.<\/p>\nWhat is the operational state of an access port assigned to a deleted VLAN?<\/h4>\n
The interface becomes inactive<\/strong> (orphaned). While the physical port may still indicate an active link carrier (layer 1 “up” and layer 2 “up”), the port cannot transmit or receive user traffic. Frames arriving at the port are dropped because the switch has no forwarding table or broadcast domain associated with that missing VLAN ID.<\/p>\nWhen you run show interfaces status<\/code>, the Vlan<\/code> column displays inactive<\/code>:<\/p>\nSwitch# show interfaces status\n\nPort Name Status Vlan Duplex Speed Type\nGi0\/3 Workstation-A connected inactive auto auto 10\/100\/1000BaseTX\n<\/code><\/pre>\nAdditionally, running show vlan brief<\/code> will completely omit that physical port from all active VLAN port listings.<\/p>\nHow do you restore traffic on an orphaned port?<\/h4>\n
You can resolve an orphaned port through one of three methods:
\n1. Reassign the port to a valid active VLAN:<\/strong>
\ntext
\nSwitch(config)# interface GigabitEthernet0\/3
\nSwitch(config-if)# switchport access vlan 20<\/code>
\n2. Reset the port to the default VLAN 1:<\/strong>
\ntext
\nSwitch(config)# interface GigabitEthernet0\/3
\nSwitch(config-if)# no switchport access vlan<\/code>
\n3. Re-create the missing VLAN globally:<\/strong>
\ntext
\nSwitch(config)# vlan 10
\nSwitch(config-vlan)# name Engineering<\/code>
\nAs soon as VLAN 10 is re-created in the database, all interfaces configured for VLAN 10 immediately return to an active forwarding state without needing manual interface reconfiguration.<\/p>\n
\n<\/span>Removing a VLAN from a Trunk Port Without Deleting It Globally<\/span><\/h2>\nOften, your goal is not to eliminate a VLAN across the entire switch, but rather to restrict its traffic from traversing a specific uplink or inter-switch trunk. Deleting the VLAN globally in this scenario would inadvertently break connectivity on local access ports. Instead, you modify the trunk port’s allowed VLAN list.<\/p>\n
Warning:<\/strong> Never use the command switchport trunk allowed vlan <id><\/code> when intending to prune a VLAN. Running that command replaces the entire<\/em> allowed list with only the specified ID, instantly dropping all other production VLANs on that trunk. Always use the explicit remove<\/code> keyword.<\/p><\/blockquote>\n<\/span>Step 1: Identify the Trunk Interface and Current Allowed List<\/span><\/h3>\nExamine the trunk’s active configuration:<\/p>\n
Switch# show interfaces trunk\n\nPort Mode Encapsulation Status Native vlan\nGi0\/1 on 802.1q trunking 1\n\nPort Vlans allowed on trunk\nGi0\/1 1-4094\n<\/code><\/pre>\n<\/span>Step 2: Enter Interface Configuration Mode<\/span><\/h3>\nNavigate to the target trunk interface or interface range:<\/p>\n
Switch# configure terminal\nSwitch(config)# interface GigabitEthernet0\/1\n<\/code><\/pre>\n<\/span>Step 3: Remove the VLAN from the Allowed List<\/span><\/h3>\nUse the switchport trunk allowed vlan remove<\/code> command followed by the target VLAN ID or list:<\/p>\nSwitch(config-if)# switchport trunk allowed vlan remove 20\n<\/code><\/pre>\nTo remove multiple VLANs or a range of VLANs from the trunk:<\/p>\n
Switch(config-if)# switchport trunk allowed vlan remove 30,40,100-105\n<\/code><\/pre>\n<\/span>Step 4: Verify Trunk Traffic Filtering<\/span><\/h3>\nConfirm that the trunk interface reflects the updated allowed list:<\/p>\n
Switch(config-if)# do show interfaces trunk\n\nPort Vlans allowed on trunk\nGi0\/1 1-19,21-29,31-39,41-99,106-4094\n<\/code><\/pre>\nVLAN 20 remains fully operational in the global database and continues to service local access ports, but its broadcast, multicast, and unicast frames will no longer pass across GigabitEthernet0\/1<\/code>.<\/p>\n
\n<\/span>Troubleshooting VLAN Deletion: VTP Restrictions and Reserved VLANs<\/span><\/h2>\nWhen attempting to run no vlan <id><\/code>, you may encounter error messages preventing the deletion. These errors typically stem from VLAN Trunking Protocol (VTP) client constraints or attempts to delete system-reserved VLANs.<\/p>\n<\/span>Frequently Asked Questions<\/span><\/h3>\nWhy does the switch return %VTP: VLAN configuration not permitted in VTP client mode<\/code>?<\/h4>\nThis error occurs because the switch is operating as a VTP Client. A VTP Client switch cannot create, alter, or delete VLANs locally; it can only synchronize its database from a VTP Server within the same management domain.<\/p>\n
To resolve this issue, use one of the following approaches:
\n– Delete the VLAN on the VTP Server:<\/strong> Access the switch configured as the VTP Server for that domain and execute no vlan <id><\/code> there. The change will automatically propagate to all client switches.
\n– Change the local switch to VTP Transparent mode:<\/strong> If this switch should manage VLANs independently without network-wide VTP synchronization, switch its operating mode:
\ntext
\nSwitch(config)# vtp mode transparent
\nSetting device to VTP Transparent mode for VLANS.
\nSwitch(config)# no vlan 20<\/code>
\n– Change the local switch to VTP Server mode:<\/strong> If the switch was misconfigured as a client and should function as an authoritative server:
\ntext
\nSwitch(config)# vtp mode server
\nSetting device to VTP Server mode for VLANS.
\nSwitch(config)# no vlan 20<\/code><\/p>\nWhy can’t VLAN 1 be deleted?<\/h4>\n
Attempting to run no vlan 1<\/code> produces the error:<\/p>\n% Default VLAN 1 cannot be deleted.\n<\/code><\/pre>\nVLAN 1 is the hardcoded default management and control VLAN on Cisco switches. Essential control-plane protocols\u2014including Cisco Discovery Protocol (CDP), Dynamic Trunking Protocol (DTP), Port Aggregation Protocol (PAgP), and VTP\u2014transmit control frames across VLAN 1 by default. The switch operating system strictly forbids deleting or renaming VLAN 1 to maintain core internal operations.<\/p>\n
What are VLANs 1002 through 1005, and why can’t they be removed?<\/h4>\n
VLANs 1002, 1003, 1004, and 1005 are factory-reserved defaults originally allocated for legacy network architectures:
\n– 1002:<\/strong> fddi-default<\/code>
\n– 1003:<\/strong> token-ring-default<\/code>
\n– 1004:<\/strong> fddinet-default<\/code>
\n– 1005:<\/strong> trnet-default<\/code><\/p>\nEven on modern enterprise Catalyst switches that lack legacy hardware interfaces, Cisco IOS reserves these four IDs within the standard VLAN range. Attempting to delete any ID between 1002 and 1005 yields:<\/p>\n
% Default VLAN 1002 cannot be deleted.\n<\/code><\/pre>\nLike VLAN 1, these IDs cannot be modified, deleted, or reassigned for standard Ethernet traffic.<\/p>\n
Why did a deleted VLAN reappear after reloading the switch?<\/h4>\n
If a deleted VLAN returns following a reboot, check the following common causes:
\n– VTP Synchronization:<\/strong> If the switch is joined to an active VTP domain and another switch is acting as a VTP Server with a higher configuration revision number, the server will repopulate the VLAN upon boot.
\n– Startup Configuration Discrepancies:<\/strong> Extended-range VLANs (IDs 1006\u20134094) in VTP Transparent or VTPv3 modes are saved directly within the text configuration file. If you deleted an extended VLAN from the running configuration but failed to save (copy running-config startup-config<\/code>), the switch will reload the VLAN from the startup configuration.<\/p>\n
\n<\/span>Purging the Entire VLAN Database by Deleting vlan.dat<\/span><\/h2>\nWhen preparing a switch for redeployment, decommissioning hardware, or performing a factory reset, deleting dozens of individual VLANs one by one is impractical. On Cisco Catalyst switches, standard-range VLANs (1\u20131005) are not stored in the ASCII startup-config<\/code> file; they are kept in a separate binary file named vlan.dat<\/code> located in flash memory.<\/p>\nTo completely reset the VLAN database back to factory defaults, you must delete this file and restart the switch.<\/p>\n
<\/span>Step 1: Verify the Location of vlan.dat<\/span><\/h3>\nFrom privileged EXEC mode, list the contents of the primary flash file system:<\/p>\n
Switch# dir flash:\n\nDirectory of flash:\/\n\n 101 -rwx 616 Mar 1 2026 00:04:12 +00:00 vlan.dat\n 102 -rwx 33554432 Jan 15 2026 12:20:00 +00:00 c2960x-universalk9-mz.152-7.E2.bin\n<\/code><\/pre>\nOn modular switches or platforms equipped with dual supervisors, the path may be designated as bootflash:vlan.dat<\/code> or flash:vlan.dat<\/code>.<\/p>\n<\/span>Step 2: Delete the vlan.dat File<\/span><\/h3>\nExecute the delete<\/code> command referencing the storage medium and filename:<\/p>\nSwitch# delete flash:vlan.dat\n<\/code><\/pre>\nThe switch CLI will prompt for confirmation twice:<\/p>\n
Delete filename [vlan.dat]? [Press Enter]\nDelete flash:\/vlan.dat? [confirm] [Press Enter]\n<\/code><\/pre>\nPress Enter<\/strong> at both prompts to confirm removal.<\/p>\n<\/span>Step 3: (Optional) Erase the Startup Configuration<\/span><\/h3>\nIf your objective is a complete factory reset of the switch, erase the configuration file so old interface VLAN assignments and host settings do not persist:<\/p>\n
Switch# erase startup-config\nErasing the nvram filesystem will remove all configuration files! Continue? [confirm] [Press Enter]\n[OK]\nErase of nvram: complete\n<\/code><\/pre>\n<\/span>Step 4: Reload the Switch<\/span><\/h3>\nReload the switch to force Cisco IOS to initialize an empty, default VLAN structure:<\/p>\n
Switch# reload\nProceed with reload? [confirm] [Press Enter]\n<\/code><\/pre>\nIf prompted to save the running configuration prior to the reload, type no<\/strong>. Entering “yes” will regenerate parts of the old configuration into NVRAM.<\/p>\n<\/span>Step 5: Verify the Factory Default State<\/span><\/h3>\nOnce the switch finishes booting, confirm that all user-defined VLANs have been cleared:<\/p>\n
Switch# show vlan brief\n\nVLAN Name Status Ports\n---- -------------------------------- --------- -------------------------------\n1 default active Gi0\/1, Gi0\/2, Gi0\/3, Gi0\/4 ...\n1002 fddi-default act\/unsup \n1003 token-ring-default act\/unsup \n1004 fddinet-default act\/unsup \n1005 trnet-default act\/unsup \n<\/code><\/pre>\nAll ports revert to default VLAN 1, and only system-reserved VLANs remain.<\/p>\n
\n<\/span>Cisco Catalyst Command Reference and Official Documentation<\/span><\/h2>\nFor formal documentation and command verification across Cisco Catalyst, Nexus, and Industrial Ethernet platforms, refer to the following structural command definitions and technical reference guides.<\/p>\n
<\/span>Command Reference Summary<\/span><\/h3>\n\n\n\n| Command Syntax<\/th>\n | Execution Mode<\/th>\n | Prerequisites & Constraints<\/th>\n | Functional Description<\/th>\n<\/tr>\n<\/thead>\n |
\n\nno vlan <vlan-id><\/code><\/td>\nGlobal Configuration (config<\/code>)<\/td>\n| VTP mode must be Server, Transparent, or Off. Cannot be applied to VLAN 1 or 1002\u20131005.<\/td>\n | Deletes a single standard or extended VLAN from the switch database.<\/td>\n<\/tr>\n | \nno vlan <start-id>-<end-id><\/code><\/td>\n | | |