Ora

How to remove vss configuration?

Published in Cisco VSS 5 mins read

Removing a Virtual Switching System (VSS) configuration typically involves a process of breaking the VSS domain, clearing the existing configuration, or manually removing VSS-specific commands. The method you choose depends on whether you aim for a complete system reset, a granular cleanup, or a re-configuration.

Here are the primary methods to remove VSS configuration:

Methods for VSS Configuration Removal

1. Systematic VSS Breakage and Full Configuration Erase

This method is ideal for a complete reset, ensuring no residual VSS configuration remains and allowing you to either re-configure VSS from scratch or return the devices to standalone operation. It combines the idea of reverting to standalone mode with a full configuration wipe.

Steps:

  1. Backup Current Configuration: Before making any significant changes, save your running configuration to a remote server or local flash. This is crucial for recovery if anything goes wrong.

    • copy running-config tftp://<TFTP_SERVER_IP>/<FILENAME>.cfg
    • copy running-config flash:backup-config.cfg
  2. Break the VSS Domain (Revert to Standalone): This step disbands the VSS pair, returning each device to an independent, standalone state.

    • On the active VSS member: Identify the VSS ID and domain.
      Switch# show switch virtual
    • Remove VSS configuration: This involves negating the VSS-specific commands. The exact sequence can vary, but generally includes:
      • no switch virtual domain <domain_id>
      • no vc-port <port_channel_number>
      • no stack-port <etherchannel_number>
    • Reload the peer (if still connected): If the peer is still online, reloading it will cause it to come up in standalone mode.
      Switch# redundancy reload peer unit
    • Verify Standalone Status: After the process, confirm that both devices are operating as standalone switches.
      Switch# show switch virtual

      (Output should indicate standalone mode or no VSS configured).

  3. Erase Configuration: Once both devices are standalone, clear their startup configurations. This ensures a clean slate.

    • On each switch, issue the command:
      Switch# write erase

      Confirm the erase when prompted.

  4. Reload the Switches: Reload both switches to load with a fresh, empty configuration.

    Switch# reload
  5. Apply Final Configuration: After the reload, the switches will boot with default configurations. You can then apply your desired standalone configuration or re-configure VSS if needed.

2. Manual Removal Using no Commands

This method offers granular control, allowing you to remove specific VSS-related commands without a full configuration wipe. It's more painstaking but can be useful for minor adjustments or if a complete reset is not feasible.

Steps:

  1. Identify VSS-Specific Commands: Review your running configuration for commands related to VSS. These typically include:

    • switch virtual domain <domain_id>
    • switch virtual link <ID>
    • vc-port <port_channel_number>
    • stack-port <etherchannel_number>
    • mode virtual (within interface configurations, if applicable)
    • switchport virtual (for interfaces acting as VSS links)
  2. Negate Commands: Enter global configuration mode and use the no form of each identified VSS command.

    • Switch(config)# no switch virtual domain 1
      Switch(config)# no vc-port 1
      Switch(config)# interface port-channel 1
      Switch(config-if)# no stack-port
      Switch(config-if)# exit
    • Repeat for all relevant VSS commands on both switches.
  3. Save Configuration: After negating all VSS-related commands, save your changes.

    Switch# write memory
  4. Reload (Optional but Recommended): A reload can help ensure all VSS states are cleared and the switches fully revert to standalone operation.

3. Complete Configuration Reset (erase nvram: or write erase)

This is the most straightforward and drastic method for removing any configuration, including VSS. It effectively wipes the entire startup configuration, returning the device to its factory-default state upon reboot. This is particularly useful if you want to start completely fresh.

Steps:

  1. Backup Configuration: As with any major change, always back up your current configuration.

  2. Issue Erase Command:

    • On each switch, you can use:
      Switch# erase nvram:

      OR

      Switch# write erase
    • Confirm the erase when prompted.
  3. Reboot the Switch: After erasing the configuration, reload the switch.

    Switch# reload

    The switch will boot up with a blank configuration, effectively removing all previous settings, including VSS.

Comparison of VSS Removal Methods

Method Pros Cons When to Use
Systematic VSS Breakage & Erase Cleanest full removal, ensures no lingering config Requires careful execution, more steps, downtime Complete VSS removal, moving to standalone, or re-configuring VSS from scratch
Manual no Commands Granular control, less impact on non-VSS config Tedious, prone to errors, potential for residual config Minor VSS adjustments, partial removal, or if full erase is not an option
Complete Configuration Reset (erase nvram / write erase) Quickest and simplest for a full wipe Wipes all configuration, requires full re-configuration Starting fresh, complete system reset, troubleshooting complex VSS issues

Important Considerations

  • Downtime: All methods, especially those involving write erase or reload, will cause network downtime. Plan accordingly.
  • Backup: Always backup your configuration before attempting any VSS removal procedure. This is your primary safety net.
  • Impact on Network: Understand the network's dependencies on the VSS. Removing VSS will turn the pair into two independent switches, which may require re-architecting your network connections.
  • IOS Version: Specific commands or their behavior might slightly vary between Cisco IOS versions. Always consult the official Cisco documentation for your specific hardware and IOS version if you encounter issues.

Removing VSS configuration requires careful planning and execution to avoid unintended network disruptions. Always proceed with caution and a clear understanding of the steps involved.