Introduction
Overlay Transport Virtualization (OTV) is used to extend Layer 2 VLANs across different data center sites. During migration, cleanup, or service decommissioning, you may need to remove VLANs from OTV. This must be done carefully to avoid impacting live traffic.
This guide explains how to remove all VLANs or selected VLANs from OTV using correct syntax and best practices.
Remove All VLANs from OTV
To remove all VLANs configured under OTV, use the following command:
N7K(config-if-overlay)# no otv extend-vlan
Example:
N7K(config-if-overlay)# no otv extend-vlan 2-100
This command removes all VLANs from being extended across the OTV overlay.
Remove Selected VLANs from OTV
Important point: Cisco Nexus OTV does not allow removing a VLAN directly from a range. You must redefine the VLAN list.
Scenario 1: Remove VLANs from a Range
Current configuration:
otv extend-vlan 2-34
Requirement: remove VLAN 3 and VLAN 4
Correct approach:
N7K(config-if-overlay)# otv extend-vlan 2,5-34
After this change, VLAN 3 and VLAN 4 will no longer be extended across OTV.
Or
otv extend-vlan remove 10
Verification Commands
After making changes, verify the configuration:
show otv vlan
show otv route
To check if a VLAN is actively used:
show mac address-table vlan
Impact of VLAN Removal
Before removing a VLAN, consider the following:
- Layer 2 extension for that VLAN will stop
- Traffic between data centers for that VLAN will be impacted
- Applications using that VLAN may go down
Best Practices
- Always verify VLAN usage before removal
- Coordinate with application and network teams
- Perform changes during maintenance window
- Keep rollback configuration ready
Rollback Command
If required, restore the original VLAN list:
otv extend-vlan
Conclusion
Removing VLANs from OTV requires proper planning and correct command usage. While removing all VLANs is simple, removing specific VLANs requires redefining the VLAN list. Following best practices ensures smooth execution without impacting production services.
If you want, I can create more SEO and AdSense optimized blogs on Cisco ACI, Nexus, BGP, or real troubleshooting scenarios.
Introduction
Overlay Transport Virtualization (OTV) is used to extend Layer 2 VLANs across different data center sites. During migration, cleanup, or service decommissioning, you may need to remove VLANs from OTV. This must be done carefully to avoid impacting live traffic.
This guide explains how to remove all VLANs or selected VLANs from OTV using correct syntax and best practices.
Remove All VLANs from OTV
To remove all VLANs configured under OTV, use the following command:
N7K(config-if-overlay)# no otv extend-vlan
Example:
N7K(config-if-overlay)# no otv extend-vlan 2-100
This command removes all VLANs from being extended across the OTV overlay.
Remove Selected VLANs from OTV
Important point: Cisco Nexus OTV does not allow removing a VLAN directly from a range. You must redefine the VLAN list.
Scenario 1: Remove VLANs from a Range
Current configuration:
otv extend-vlan 2-34
Requirement: remove VLAN 3 and VLAN 4
Correct approach:
N7K(config-if-overlay)# otv extend-vlan 2,5-34
After this change, VLAN 3 and VLAN 4 will no longer be extended across OTV.
Or
otv extend-vlan remove 10
Verification Commands
After making changes, verify the configuration:
show otv vlan
show otv route
To check if a VLAN is actively used:
show mac address-table vlan
Impact of VLAN Removal
Before removing a VLAN, consider the following:
- Layer 2 extension for that VLAN will stop
- Traffic between data centers for that VLAN will be impacted
- Applications using that VLAN may go down
Best Practices
- Always verify VLAN usage before removal
- Coordinate with application and network teams
- Perform changes during maintenance window
- Keep rollback configuration ready
Rollback Command
If required, restore the original VLAN list:
otv extend-vlan
Conclusion
Removing VLANs from OTV requires proper planning and correct command usage. While removing all VLANs is simple, removing specific VLANs requires redefining the VLAN list. Following best practices ensures smooth execution without impacting production services.
If you want, I can create more SEO and AdSense optimized blogs on Cisco ACI, Nexus, BGP, or real troubleshooting scenarios.
