Switch# show vlan brief\n<\/code><\/pre>\nInspect the output. VLAN 50 should no longer appear in the table. Alternatively, check the specific VLAN ID:<\/p>\n
Switch# show vlan id 50\n% VLAN 50 not found in current VLAN database\n<\/code><\/pre>\n<\/span>Step 5: Save the Running Configuration<\/span><\/h3>\nIf the switch is running in VTP Transparent mode or storing configuration locally, commit your running changes to NVRAM:<\/p>\n
Switch# copy running-config startup-config\nDestination filename [startup-config]? [Enter]\nBuilding configuration...\n[OK]\n<\/code><\/pre>\n
\n<\/span>Batch Removal: Deleting Multiple VLANs or VLAN Ranges<\/span><\/h2>\nWhen decommissioning an entire site, department, or testing network, removing VLANs individually is inefficient. Cisco IOS supports deleting multiple distinct VLANs and contiguous ranges in a single command string.<\/p>\n
! ==============================================================================\n! CISCO IOS TEMPLATE: BATCH VLAN DELETION\n! ==============================================================================\n\n! Enter configuration mode\nconfigure terminal\n\n! Option A: Delete non-contiguous VLANs (comma-separated)\nno vlan 10, 20, 30, 40\n\n! Option B: Delete a contiguous range of VLANs (hyphen-separated)\nno vlan 100-110\n\n! Option C: Delete mixed ranges and individual VLANs simultaneously\nno vlan 15, 25, 100-105, 200-210\n\n! Exit and commit\nend\nwrite memory\n<\/code><\/pre>\nNote: Ensure there are no spaces between hyphens or commas in older IOS versions (e.g., use 10-15<\/code>, not 10 - 15<\/code>), as syntax parsers on legacy Catalyst switches may reject spaced intervals.<\/em><\/p>\n
\n<\/span>Global Deletion vs. Trunk Pruning: Understanding the Impact<\/span><\/h2>\nA common point of confusion is the distinction between deleting a VLAN globally (no vlan <id><\/code>) and removing a VLAN from a trunk interface (switchport trunk allowed vlan remove <id><\/code>). While both stop traffic for that VLAN across specific paths, their operational scope is completely different.<\/p>\n\n\n\n| Evaluation Criteria<\/th>\n | Global VLAN Deletion (no vlan <id><\/code>)<\/th>\nTrunk VLAN Removal (switchport trunk allowed vlan remove <id><\/code>)<\/th>\n<\/tr>\n<\/thead>\n\n\nConfiguration Mode<\/strong><\/td>\nGlobal Configuration: (config)#<\/code><\/td>\nInterface Configuration: (config-if)#<\/code><\/td>\n<\/tr>\n\nVLAN Database Status<\/strong><\/td>\nCompletely purged from vlan.dat<\/code> and the local switch database.<\/td>\n| Remains active in the local VLAN database.<\/td>\n<\/tr>\n | \nTrunk Link Impact<\/strong><\/td>\nCeases carrying traffic across all<\/strong> switch trunks because the VLAN no longer exists locally.<\/td>\nStops forwarding traffic only<\/strong> across the specific trunk link configured.<\/td>\n<\/tr>\n\nAccess Port Impact<\/strong><\/td>\n| All access interfaces assigned to this VLAN become inactive and stop passing traffic.<\/td>\n | No impact on local access ports assigned to this VLAN.<\/td>\n<\/tr>\n | \nVTP Propagation<\/strong><\/td>\n| Propagates deletion to all switches in the VTP domain (if running VTP Server mode).<\/td>\n | Local interface setting only; does not alter VLAN topology on other switches.<\/td>\n<\/tr>\n | \nPrimary Use Case<\/strong><\/td>\n| Permanent decommissioning of a broadcast domain switch-wide.<\/td>\n | Traffic engineering, bandwidth preservation, and security boundary isolation between switches.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\n<\/span>FAQ: Handling Inactive Access Ports After VLAN Deletion<\/span><\/h2>\n<\/span>What happens to access ports when their assigned VLAN is deleted?<\/span><\/h3>\nWhen you delete a VLAN globally, any access port statically assigned to that VLAN is not automatically returned to default VLAN 1. Instead, the port becomes inactive<\/strong> or “orphaned.” <\/p>\nThe physical link may stay physically up\/up<\/code>, but the port cannot forward or receive any Ethernet frames. If you issue the show interfaces status<\/code> command, the VLAN<\/code> column for that interface will display as inactive<\/code>:<\/p>\nPort Name Status Vlan Duplex Speed Type\nGi1\/0\/12 Server-Port connected inactive a-full a-1000 10\/100\/1000BaseTX\n<\/code><\/pre>\n<\/span>How should you remediate or prevent inactive ports?<\/span><\/h3>\nTo prevent unintended downtime, audit and reassign all associated access ports before issuing the no vlan<\/code> command:<\/p>\n\n- Audit ports currently using the VLAN:<\/strong>
\n text
\n Switch# show vlan id 50<\/code>
\n Note every port listed under the Ports<\/code> column.<\/li>\n- Reassign ports to an active VLAN or disable them:<\/strong>
\n text
\n Switch(config)# interface range GigabitEthernet 1\/0\/12 - 14
\n Switch(config-if-range)# switchport access vlan 10
\n ! Or place them administratively down:
\n ! Switch(config-if-range)# shutdown<\/code><\/li>\n- Remediating orphaned ports post-deletion:<\/strong>
\n If the VLAN was already deleted, locate all orphaned ports and map them to a valid VLAN:
\n text
\n Switch# show interfaces status | include inactive
\n Switch(config)# interface GigabitEthernet 1\/0\/12
\n Switch(config-if)# switchport access vlan 10<\/code><\/li>\n<\/ol>\n
\n<\/span>FAQ: Reserved VLANs and the “VLAN 1 Cannot Be Deleted” Error<\/span><\/h2>\n<\/span>Why does Cisco IOS reject deleting VLAN 1?<\/span><\/h3>\nIf you attempt to delete VLAN 1 using no vlan 1<\/code>, the switch rejects the command and returns the following error:<\/p>\nSwitch(config)# no vlan 1\n% Default VLAN 1 may not be deleted.\n<\/code><\/pre>\nIn Cisco switching architecture, VLAN 1 is the factory default Ethernet VLAN. It serves as the baseline internal control plane channel for critical Layer 2 protocols, including Cisco Discovery Protocol (CDP), Port Aggregation Protocol (PAgP), Dynamic Trunking Protocol (DTP), and Spanning Tree Protocol (STP). Because the hardware backplane relies on VLAN 1 to process these supervisory frames, Cisco IOS strictly prohibits its deletion or modification.<\/p>\n <\/span>Can legacy VLANs 1002 through 1005 be deleted?<\/span><\/h3>\nNo. VLAN IDs 1002 through 1005 are reserved for legacy transit networks:
\n– 1002<\/code>: fddi-default
\n– 1003<\/code>: token-ring-default
\n– 1004<\/code>: fddinet-default
\n– 1005<\/code>: trnet-default<\/p>\nAttempting to delete any of these IDs generates an error:<\/p>\n Switch(config)# no vlan 1002\n% VLANs 1002-1005 are reserved and cannot be deleted.\n<\/code><\/pre>\nThese IDs cannot be renamed, modified, or purged from the database, even if your network utilizes only standard Ethernet.<\/p>\n
\n<\/span>Resetting the VLAN Database: How to Delete vlan.dat from Flash<\/span><\/h2>\nOn Cisco Catalyst switches, VLAN definitions are not stored inside startup-config<\/code> when operating in VTP Server or Client mode; they are maintained in a binary file called vlan.dat<\/code> located in the switch’s local flash memory. If you are preparing a switch for decommissioning or a factory reset, simply erasing the startup configuration with write erase<\/code> will not<\/strong> wipe user-created VLANs. You must delete the vlan.dat<\/code> file directly.<\/p>\n<\/span>Step 1: Verify the Presence of vlan.dat<\/span><\/h3>\nIn Privileged EXEC mode, inspect the root directory of flash storage:<\/p>\n Switch# dir flash:\n<\/code><\/pre>\nLocate vlan.dat<\/code> in the directory list.<\/p>\n<\/span>Step 2: Delete the vlan.dat File<\/span><\/h3>\nExecute the delete<\/code> command targeting flash memory:<\/p>\nSwitch# delete flash:vlan.dat\nDelete filename [vlan.dat]? [Press Enter]\nDelete flash:\/vlan.dat? [confirm] [Press Enter]\n<\/code><\/pre>\nNote: On modular Catalyst switches with dual supervisors, repeat this process for the secondary supervisor (e.g., delete slaveflash:vlan.dat<\/code> or delete bootflash:vlan.dat<\/code>).<\/em><\/p>\n<\/span>Step 3: Clear the Startup Configuration (Optional)<\/span><\/h3>\nIf you are performing a full device reset, erase NVRAM to eliminate any interface-level VLAN associations:<\/p>\n Switch# erase startup-config\nErasing the nvram filesystem will remove all configuration files! Continue? [confirm] [Press Enter]\n<\/code><\/pre>\n<\/span>Step 4: Reload the Switch<\/span><\/h3>\nReboot the device to force Cisco IOS to initialize a clean, default VLAN database:<\/p>\n Switch# reload\nProceed with reload? [confirm] [Press Enter]\n<\/code><\/pre>\nUpon boot, the switch will recreate an empty vlan.dat<\/code> file containing only default VLANs 1 and 1002\u20131005.<\/p>\n
\n<\/span>Official Command Reference & Documentation<\/span><\/h2>\nThe commands covered above adhere to standard Cisco Catalyst command reference guidelines across major software trains, including Cisco IOS, IOS-XE, and Catalyst Switch Software Releases.<\/p>\n ================================================================================\nCISCO CATALYST COMMAND SPECIFICATION: VLAN DELETION\n================================================================================\n\nCommand Syntax:\n no vlan { vlan-id | vlan-range }\n\nCommand Modes:\n Global configuration mode: Switch(config)#\n\nParameters:\n vlan-id : Integer from 2 to 4094 representing an existing VLAN.\n vlan-range : Contiguous (e.g., 10-20) or noncontiguous (e.g., 10,20,30) \n list of VLAN IDs.\n\nHardware \/ Software Compatibility:\n - Cisco Catalyst 2960, 3560, 3750, 3850 Series\n - Cisco Catalyst 9200, 9300, 9400, 9500, 9600 Series\n - Cisco Industrial Ethernet (IE) Series\n - Operating Systems: Cisco IOS Software Release 12.2+, Cisco IOS-XE 16.x\/17.x\n\nExecution Privilege:\n Privilege Level 15 (enable) required.\n================================================================================\n<\/code><\/pre>\nFor advanced deployments involving Virtual Switching System (VSS), StackWise, or VLAN Trunking Protocol Version 3 (VTPv3), consult the official Cisco Catalyst Switching Software Configuration Guide<\/em> corresponding to your specific IOS-XE release on the official Cisco Support & Documentation portal.<\/p>\n
\n<\/span>Conclusion<\/span><\/h2>\nDeleting a VLAN on a Cisco switch takes only a single CLI command, but proper execution requires understanding the underlying network dependencies. Always audit your access ports using show vlan id <id><\/code> before issuing no vlan <id><\/code> to prevent ports from falling into an inactive state. If your goal is simply to prevent traffic from traversing an inter-switch uplink, prune the VLAN from the trunk using switchport trunk allowed vlan remove<\/code> rather than deleting it globally. Finally, remember that for complete switch repurposing, deleting vlan.dat<\/code> from flash memory is essential to eliminate custom broadcast domains entirely.<\/p>\nPlease follow and like us:<\/span><\/div>
| | | | | | | | | | | | | |