Symptom

This is ideally how the rollback should work after timer expires: RP/0/RSP0/CPU0:AM10-ASR9001-R6(config)#load disk0:AM10-ASR9001-R6_614_5-Remove-VRF.txt [1.load the file] 14371 bytes processsed in 1 sec, current rate 7195 bytes/sec..... 19653 bytes parsed in 2 sec (9811)bytes/sec RP/0/RSP0/CPU0:AM10-ASR9001-R6(config)#commit replace confirm 45 show-error [2. commit replace with rollback timer] Wed Jun 15 11:10:34.815 EDT This commit will replace or remove the entire running configuration. This operation can be service affecting. Do you wish to proceed? [no]: yes RP/0/RSP0/CPU0:Jun 15 11:10:38.786 EDT: config[65899]: %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by user 'vxlan'. Use 'show configuration commit changes 1000000219' to view the changes. [?>3. This is the commit ID after the config is applied] RP/0/RSP0/CPU0:AM10-ASR9001-R6(config)# RP/0/RSP0/CPU0:AM10-ASR9001-R6(config)# RP/0/RSP0/CPU0:Jun 15 11:10:52.262 EDT: cfgmgr_trial_confirm[65921]: %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by user 'vxlan'. Use 'show configuration commit changes 1000000220' to view the changes. [4. This is the actual rollback ? so a new commit ID is generated. After this, auto-rollback is complete, and we are now at baseline config again] However, this does not happen while changing the vrf for interface. the rollback does not happen after the timer expires. So, the running-config is stuck with the changes applied. Below is a log of that happening: RP/0/RSP0/CPU0:AM10-ASR9001-R6(config)#load disk0:AM10-ASR9001-R6_614_4-Change-Int-VRF.txt 14363 bytes processsed in 1 sec, current rate 7182 bytes/sec...... 21165 bytes parsed in 3 sec (7045)bytes/sec RP/0/RSP0/CPU0:AM10-ASR9001-R6(config)#commit replace confirmed 45 show-error Wed Jun 15 11:24:27.880 EDT This commit will replace or remove the entire running configuration. This operation can be service affecting. Do you wish to proceed? [no]: y RP/0/RSP0/CPU0:Jun 15 11:24:31.707 EDT: config[65901]: %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by user 'vxlan'. Use 'show configuration commit changes 1000000223' to view the changes. RP/0/RSP0/CPU0:AM10-ASR9001-R6(config)# there is no rollback.

Conditions

Canging the VRF on an interface

Workaround

Further Problem Description

I also tried commit replace + rollback last 1 RP/0/RSP0/CPU0:AM10-ASR9001-R6(config)#load disk0:AM10-ASR9001-R6_614_4-Change-Int-VRF.txt 14363 bytes processsed in 1 sec, current rate 7182 bytes/sec...... 21165 bytes parsed in 3 sec (7045)bytes/sec RP/0/RSP0/CPU0:AM10-ASR9001-R6(config)#commit replace Thu Jun 16 14:01:02.520 EDT This commit will replace or remove the entire running configuration. This operation can be service affecting. Do you wish to proceed? [no]: y RP/0/RSP0/CPU0:AM10-ASR9001-R6(config)#end RP/0/RSP0/CPU0:AM10-ASR9001-R6#rollback configuration last 1 Thu Jun 16 14:01:17.673 EDT Loading Rollback Changes. Loaded Rollback Changes in 1 sec Committing. Rollback operation failed due to - One or more configuration items failed verification. Running configuration has not been modified. 2 verify and 0 apply errors encountered. RP/0/RSP0/CPU0:AM10-ASR9001-R6#show configuration failed rollback Thu Jun 16 15:16:26.010 EDT !! SEMANTIC ERRORS: This configuration was rejected by !! the system due to semantic errors. The individual !! errors with each failed configuration command can be !! found below. interface TenGigE0/0/2/0.101 vrf MSFTGUEST !!% 'RSI' detected the 'fatal' condition 'The interface's numbered and unnumbered IPv4/IPv6 addresses must be removed prior to changing or deleting the VRF' ! interface TenGigE0/0/2/1.3 vrf MSFTGUEST !!% 'RSI' detected the 'fatal' condition 'The interface's numbered and unnumbered IPv4/IPv6 addresses must be removed prior to changing or deleting the VRF' ! end