Configure vEdge Routers during Maintenance Window

Available Languages

Download Options

  • PDF     (40.1 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (81.8 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (67.0 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:November 5, 2019
Document ID:214659

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

    Introduction

    This document describes the best practices on how to configure Viptela vEdges at the time of Customer Maintenance Window, in order to prevent any unwanted outages due to the configuration changes that are made, which might result in unintended consequences.  

    Prerequisites

    Requirements

    There are no specific requirements for this document.

    Components Used

    This document is not restricted to specific software and hardware versions.

    The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.

    Configure

    When the customer deployment windows, it is always recommended to configure with “exclusive” option, so that you can verify the

    configuration, prior to the commit.

    This allows for any un-intended configuration, not to go into production that might cause any issues. These could manifest in the

    form of losing connectivity to the device or when a wrong policy is applied. This allows rollback of the configuration to a (prior)

    working state.

    It is always recommended to come up with a configuration prior to the maintenance window and test in the laboratory before you apply on the production router.

    These are the configuration options that are allowed on vEdges.

    vEdge# config ?
    Possible completions:
      exclusive  no-confirm  shared  terminal  |  <cr>

    Configure with the exclusive command.

    vEdge# config exclusive 
    Entering configuration mode exclusive
    Warning: uncommitted changes will be discarded on exit
    vEdge(config)#

    This is the message that appears when the commit command is not executed.

    vEdge(config)# vpn 1 
    vEdge(config-vpn-1)# ip route 23.23.23.23/32 null0
    vEdge(config-vpn-1)# commit confirmed 1
    Warning: The configuration will be reverted if you exit the CLI without
    performing the commit operation within 1 minutes.

    vEdge(config-vpn-1)# exit
    vEdge(config)# exit
    vEdge# config exclusive 
    Aborted: confirmed commit in progress

    vEdge#     
    Message from system at 2019-07-08 01:07:13...
    confirmed commit operation not confirmed by admin from cli
    configuration rolled back
    vEdge# 
    vEdge# config exclusive 
    Entering configuration mode exclusive
    Warning: uncommitted changes will be discarded on exit
    vEdge(config)# vpn 1
    vEdge(config-vpn-1)# ip route 23.23.23.23/32 null0
    vEdge(config-vpn-1)# commit confirmed 1
    Warning: The configuration will be reverted if you exit the CLI without
    performing the commit operation within 1 minutes.
    vEdge(config-vpn-1)# 
    Message from system at 2019-07-08 21:07:37...
    confirmed commit operation not confirmed by admin from cli
    configuration rolled back
    vEdge(config-vpn-1)#

    Once you are sure all is in place, you can execute the command commit.

    vEdge(config-vpn-1)# commit
    Commit complete. Configuration is now permanent.
    vEdge(config-vpn-1)#

    For the commit confirmed option, it is recommended to have about 5 to 10 minutes in order to validate the configuration that was put in place. Here, 1 minute is used as an example.

    Verify

    Use this section in order to confirm that your configuration works properly.

    Execute show running-config or appropriate config-sub-block command.

    Here is an example of validation:

    vEdge# show running-config  vpn 1 ip 
    vpn 1
     ip route 23.23.23.23/32 null0
    !
    vEdge#

    Troubleshoot

    There is currently no specific troubleshooting information available for this configuration.

    TAC Authored

    Contributed by Cisco Engineers

    • Shankar Vemulapalli
      Cisco TAC Engineer

    Was this Document Helpful?

    FeedbackFeedback

    Contact Cisco

    This Document Applies to These Products