Introduction: This document is created for new beginner who wants to improve their CLI speed. Cisco IOS provides some abbreviation commands and shortcuts to speed user interaction, e.g.: user not need to type the entire command to have recognized by IOS, it only requires minimum amount of character that unambiguously define a commands. Examples: In privilege mode there are two commands start with "con" R1#con? configure connect connectedapps So by typing "conf" command the system IOS will recognizes that you want to execute command related to "configure" so it will only take command starts with this character.   R1#conf? configure R1#conf ? confirm Confirm replacement of running-config with a new config file memory Configure from NV memory network Configure from a TFTP network host overwrite-network Overwrite NV memory from TFTP network host replace Replace the running-config with a new config file revert Parameters for reverting the configuration terminal Configure from the terminal <cr> Now if you want to enter into configure terminal and you don’t want to type entire syntax like configure terminal you can just type "conf t" so IOS will recognizes that you want to execute the full "configure terminal" command. R1#conf t Enter configuration commands, one per line. End with CNTL/Z. R1(config)#   Below is some example of the abbreviation commonly used: In privilege mode sh ip int bri  .....show ip interface brief sh proc cpu his ....show process cpu history sh ip os bri     .....show ip ospf brief   In configuration mode int fa0/0.... interface fastethernet0/0   Addition, In IOS there are special keys and combination will allow you faster to use CLI command. Below are the some of the shortcuts i always use. a) Left Arrow: Moves cursor to left b) Right Arrow: Moves cursor to right c) Ctrl+A: This will move the cursor to start of the line   Example: Let's see if i want to execute below command in config mode R1(config)# p route 1.1.1.1 255.255.255.255 10.1.1.1   but by mistake instead of "ip route", i have wrote "p route" so instead of using left arrow,i can use "Ctrl+A" and directly jump into start of the line and do changes as show below R1(config)# p route 1.1.1.1 255.255.255.255 10.1.1.1   d) Ctrl+e=This will move the cursor to end of the line   R1(config)# i p route 1.1.1.1 255.255.255.255 10.1.1.1   e) Ctrl+Z=If you execute this in any line of config mode will allow you to exit to privilege mode example R1#conf t Enter configuration commands, one per line.  End with CNTL/Z. R1(config)#^Z R1#conf t *Sep 24 11:15:31.399: %SYS-5-CONFIG_I: Configured from console by console R1#conf t Enter configuration commands, one per line. End with CNTL/Z. R1(config)#router os 100 R1(config-router)#^Z R1#   f) Backspace=To erase the character to the left side of cursor.   g) Up arrow= It will display previous enter command in reverse chronological order.   h) Down arrow= It will display previous enter command in reverse chronological order .   i)Tab=This will complete the command to last similar characters like if you type "sh" and then press "tab" key ,it will give you full command "show"   ... View more

Introduction: This document created by user discussion and observed user cases. Symptom: When user login to XR platform with Telnet/ssh to the router prints incomplete output and then hangs. It does not respond to "ENTER". It may respond to CTRL-C but this does not restore a complete correct behavior. But they are working via console. Example: RP/0/RSP0/CPU0:BRSPOM1COMM-ASR9K-1#sh logging Mon Sep 2 11:48:28.403 GMT RP/0/RSP0/CPU0:BRSPOM1COMM-ASR9K-1# RP/0/RSP0/CPU0:BRSPOM1COMM-ASR9K-1#dir Mon Sep 2 11:53:11.518 GMT Conditions:    This happens after multiple VTY sessions being opened and closed at the same time, or after a session has been terminated while still receiving output.    Workaround:   1) Using "terminal length 0" is a partial workaround.    Recovery:    1) Create a new telnet/ssh session. FIRST command to execute from this session is “proc restart devc-vty"OR     2) Connect to the router through a Console port recovers by executing "proc restart devc-vty" command. Known Affected Releases: 3.8.2.BASE 3.8.3.17i.BASE 3.8.3.19i.BASE 3.8.3.BASE 3.9.0.BASE 3.9.1.BASE 4.0.0.BASE 4.0.1.BASE Known Fixed Releases: 3.9.2.99i.BASE 4.0.0.99i.BASE Bug Information: CSCte01589 https://tools.cisco.com/bugsearch/bug/CSCte01589   Document Source: https://supportforums.cisco.com/discussion/11917731/commands-not-shows-ssh-asr9k ... View more

Introduction: This document explain "bgp match community" statement used in route-map. Communities are used as flags in order to mark a set of routes in BGP which Upstream routers can then use these flags to apply specific routing polices (for example, local preference)within their network. BGP route can be mark with single or multiple community value. To perform routing policy on the basis of community value, route-map uses to match community value to perform inbound or outbound operation. BGP router receive routes with single community or multiple community value so while using "match community" command in route-map has two options. 1) Route Map: (match community word) 2) Route Map: (match community word exact-match)   Using "match community word" command: When the one of BGP communities value match to the one of communities value in community list, it is match. Using "match community word exact-match" : When exact-match keyword is specified, match happen only when BGP updates have completely same communities value specified in the community list. Let's discussed this more with configuration example: Configuration Example: Topology consists of three routers R1, R2 and R3 configured in AS1, AS2 and AS3 respectively. All basic and BGP configuration has already done shown below in table.R1 is advertising 5 prefixes to R2 and R2 to R3 shown as below: 1.1.1.1/32 and 2.2.2.2/32 with community 11:11 3.3.3.3/32 and 4.4.4.4/32 with community 11:11 22:22 5.5.5.5/32 with community 33:33     R1: hostname R1 ! interface Loopback0  ip address 1.1.1.1 255.255.255.255 ! interface Loopback1  ip address 2.2.2.2 255.255.255.255 ! interface Loopback2  ip address 3.3.3.3 255.255.255.255 ! interface Loopback3  ip address 4.4.4.4 255.255.255.255 ! interface Loopback4  ip address 5.5.5.5 255.255.255.255 end ! interface FastEthernet0/0  ip address 10.1.1.1 255.255.255.252  no sh ! router bgp 1  no bgp default ipv4-unicast  bgp log-neighbor-changes  neighbor 10.1.1.2 remote-as 2  !  address-family ipv4   neighbor 10.1.1.2 activate   neighbor 10.1.1.2 send-community   neighbor 10.1.1.2 route-map TO_R2 out   no auto-summary   no synchronization   network 1.1.1.1 mask 255.255.255.255   network 2.2.2.2 mask 255.255.255.255   network 3.3.3.3 mask 255.255.255.255   network 4.4.4.4 mask 255.255.255.255   network 5.5.5.5 mask 255.255.255.255  exit-address-family ! ip prefix-list L0&L1 seq 5 permit 1.1.1.1/32 ip prefix-list L0&L1 seq 10 permit 2.2.2.2/32 ! ip prefix-list L2&L3 seq 5 permit 3.3.3.3/32 ip prefix-list L2&L3 seq 10 permit 4.4.4.4/32 ! ip prefix-list L4 seq 5 permit 5.5.5.5/32 ! route-map TO_R2 permit 10  match ip address prefix-list L0&L1  set community 11:11 ! route-map TO_R2 permit 20  match ip address prefix-list L2&L3  set community 11:11 22:22 ! route-map TO_R2 permit 30  match ip address prefix-list L4  set community 33:33 ! ip bgp-community new-format ############################################################## R2: hostname R2 ! interface FastEthernet0/0  ip address 10.1.1.2 255.255.255.252  no sh ! interface FastEthernet0/1  ip address 10.1.1.5 255.255.255.252  no sh ! router bgp 2  no bgp default ipv4-unicast  bgp log-neighbor-changes  neighbor 10.1.1.1 remote-as 1  neighbor 10.1.1.6 remote-as 3  !  address-family ipv4   neighbor 10.1.1.1 activate   neighbor 10.1.1.6 activate   neighbor 10.1.1.6 send-community   no auto-summary   no synchronization  exit-address-family ! ip bgp-community new-format ! ############################# R3: hostname R3 ! interface FastEthernet0/0  ip address 10.1.1.6 255.255.255.252  no sh ! router bgp 3  no bgp default ipv4-unicast  bgp log-neighbor-changes  neighbor 10.1.1.5 remote-as 2  !  address-family ipv4   neighbor 10.1.1.5 activate   no auto-summary   no synchronization  exit-address-family ! ip bgp-community new-format ! Verifying BGP neighborship on R2 and R3 is learning 5 routes with community value as mentioned above.   On R2:   R2#sh ip bgp summary | beg Nei Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 10.1.1.1 4 1 182 177 9 0 0 02:42:42 4 10.1.1.6 4 3 161 173 9 0 0 02:36:31 0     On R3:   R3#sh ip bgp community 11:11 exact-match | beg Net Network Next Hop Metric LocPrf Weight Path *> 1.1.1.1/32 10.1.1.5 0 2 1 i *> 2.2.2.2/32 10.1.1.5 0 2 1 i   R3#sh ip bgp community 11:11 22:22 exact-match | beg Net Network Next Hop Metric LocPrf Weight Path *> 3.3.3.3/32 10.1.1.5 0 2 1 i *> 4.4.4.4/32 10.1.1.5 0 2 1 i   R3#sh ip bgp community 33:33 exact-match | beg Net Network Next Hop Metric LocPrf Weight Path *> 5.5.5.5/32 10.1.1.5 0 2 1 i Case1: Configure "match community word" in route-map Here route-map will be configure on R2 to deny routes advertisement that have community value 11:11, so even if prefixes has other community value than 11:11 will be filter by R2 to R3.   Configuring Community-list and Route-map on R2.   ip community-list standard TO_R3_FILTER permit 11:11 route-map TO_R3 deny 10 match community TO_R3_FILTER route-map TO_R3 permit 100 router bgp 2 address-family ipv4 uni neighbor 10.1.1.6 route-map TO_R3 out   Verify:   R3#sh ip bgp | beg Net Network Next Hop Metric LocPrf Weight Path *> 5.5.5.5/32 10.1.1.5 0 2 1 i R3#sh ip bgp community 33:33 exact-match | beg Net Network Next Hop Metric LocPrf Weight Path *> 5.5.5.5/32 10.1.1.5 0 2 1 i   From the above output, R3 is only receiving routes with community 33:33, other routes include 11:11 community value got filter by R2 to R3.   Case2: Configure "match community word exact-match" in route-map. When exact-match keyword is specified, match happen only when BGP updates have completely same communities value specified in the community list. In our case, R2 will be matching community value 11:11 22:22 and forward to R3 other route will be filtered on R2.   Configuring Community-list and route-map on R2:   ip community-list standard TO_R3_FILTER permit 11:11 22:22 route-map TO_R3 permit 10 match community TO_R3_FILTER exact-match router bgp 2 address-family ipv4 uni neighbor 10.1.1.6 route-map TO_R3 out Verify on R3: R3#sh ip bgp | beg Net Network Next Hop Metric LocPrf Weight Path *> 3.3.3.3/32 10.1.1.5 0 2 1 i *> 4.4.4.4/32 10.1.1.5 0 2 1 i R3#sh ip bgp community 11:11 22:22 exact-match | beg Net Network Next Hop Metric LocPrf Weight Path *> 3.3.3.3/32 10.1.1.5 0 2 1 i *> 4.4.4.4/32 10.1.1.5 0 2 1 i ... View more

Introduction: In this document you will be learning on "Configuring Session manager" feature of NX-Os. NX-OS allow several configuration commands to be executed in sequence as a batch in configuration session. Once you create such session, its sequence of command will be executed with commit operation. So you can verify your configuration before applying to box. There are some of the guideline and limitation of this feature like session manager only support ACL and Qos feature, please read more for this Guidelines and Limitations. Configuration Example: In this example, we will be creating configuration session for deploying access-list on nexus 7k. I will be creating acl with name "Test_ACL" N7k1# sh ip access-lists Test_ACL N7k1#   So as you can see we don’t have any ACL on N7K box. Step1: Create configure session: N7k1# configure session test Config Session started, Session ID is 1 Enter configuration commands, one per line. End with CNTL/Z. N7k1( config-s )# Once you type command "configure session <word>”, you can see our normal config mode has changed with (config-s) # prompt. Let's check what option we have under this mode.   N7k1(config-s)# ? abort Abort the current configuration session access-list Configure access control list parameters arp ARP access-list configuration commands class-map Configure a class map commit Commit the current configuration session errdisable Error disable interface Configure interfaces ip Configure IP features ipv6 Configure IPv6 features line Configure a terminal line logging Modify message logging facilities mac MAC configuration commands no Negate a command or set its defaults object-group Configure ACL object groups policy-map Configure a policy map qos QoS Global Commands resequence Resequence a list with sequence numbers save Save the current configuration session to uri system System management commands table-map Configure a table map time-range Define time range entries verify Verify the current configuration session vlan Vlan commands end Go to exec mode exit Exit from command interpreter pop Pop mode from stack or restore from name push Push current mode to stack or save it under name where Shows the cli context you are in N7k1(config-s)# As you can see we have very limited feature option here, major I use this for configuring large ACL so i can configured them in bunch and push them to box in maintenance window time. Configure ACL under "configure session test" N7k1(config-s)# ip access-list Test_ACL N7k1(config-s-acl)# deny tcp any any eq gopher N7k1(config-s-acl)# permit tcp any any eq 443 N7k1(config-s-acl)# permit tcp any any eq 80 N7k1(config-s-acl)# permit tcp any any eq 23 N7k1(config-s-acl)# permit tcp any any eq ftp N7k1(config-s-acl)# permit tcp any any eq ftp-data N7k1(config-s-acl)# exit N7k1(config-s)# int e1/1 N7k1(config-s-if)# ip access-group Test_ACL in N7k1(config-s-if)# ip access-group Test_ACL out N7k1(config-s-if)# exit N7k1(config-s)#end N7k1#   Now end this mode and let's check running config for this acl and interface configuration. N7k1# sh ip access-lists Test_ACL N7k1# N7k1# sh run int e1/1 !Command: show running-config interface Ethernet1/1 !Time: Tue Sep 30 12:24:44 2014 version 6.0(2) interface Ethernet1/1 You can see we have configured ACL and apply to interface but still it hasn't applied to running config of box. Now we will verify our Configure session and applied to running config with "commit" word. N7k1# sh configuration session test config session name test 0001 ip access-list Test_ACL 0002 deny tcp any any eq gopher 0003 permit tcp any any eq 443 0004 permit tcp any any eq 80 0005 permit tcp any any eq 23 0006 permit tcp any any eq ftp 0007 permit tcp any any eq ftp-data 0008 interface Ethernet1/1 0009 ip access-group Test_ACL in 0010 ip access-group Test_ACL out   N7k1# configure session test Config Session started, Session ID is 1 Enter configuration commands, one per line. End with CNTL/Z. N7k1(config-s)# commit Commit Successful   Verifying running config:   N7k1# sh ip access-lists Test_ACL IP access list Test_ACL 10 deny tcp any any eq gopher 20 permit tcp any any eq 443 30 permit tcp any any eq www 40 permit tcp any any eq telnet 50 permit tcp any any eq ftp 60 permit tcp any any eq ftp-data N7k1# sh run int e1/1 !Command: show running-config interface Ethernet1/1 !Time: Tue Sep 30 12:30:45 2014 version 6.0(2) interface Ethernet1/1 ip access-group Test_ACL in ip access-group Test_ACL out Related information: The best way to upload large ACLs to NX-OS Nexus 7009 N7K Configuring Session Manager ... View more

Introduction: This document is created from user discussion. Core Issue: When an AIM-IPS-K9 is installed, a router displayed following message as a part of its boot-up process. Cisco 3845 (revision 1.0) with 221184K/40960K bytes of memory. Processor board ID FCZ133670YY 2 Gigabit Ethernet interfaces 1 terminal line 1 Virtual Private Network (VPN) Module 1 cisco ips sensor(s), ips monitoring on slot O DRAM configuration is 64 bits wide with parity enabled. 447K bytes of NVRAM. 250880K bytes of ATA System CompactFlash (Read/Write) *Feb 11 12:52:17.347: %PSE HW—1—PKT ERROR: preparing paktype of SM CONTROL PACKET *Feb 11 12:52:44.451: %VPN MW—6—INFO LOC: Crypto engine: onboard O State changed to: Initialized *Feb 11 12:52:44.455: %VPN MW—6—INFO LOC: Crypto engine: onboard O State changed to: Enabled   Solution: This message will occur when AIM-IPS-K9 installed and its cosmetic message only. There is no impact to the AIM-IPS-K9 or router .No workaround is required. For more detail, please check CSCsq24774 https://tools.cisco.com/bugsearch/bug/CSCsq24774 Document source: https://supportforums.cisco.com/discussion/12103281/cisco-3845-error-pse-hw-1-pkt-error-preparing-paktype-sm-control-packet ... View more

Introduction: This document was created from user discussion. In this discussion user received DEV_SELENE related error on linecard. User was using Cisco7606 and below is the error syntax Sample errors: %DEV_SELENE-DFC2-3-SRAM_ECC: Selene 1 SRAM High Single-bit ECC error, error status: ... %DEV_SELENE-DFC2-3-SRAM_ECC: Selene 1 SRAM Low Single-bit ECC error, error status: ... %DEV_SELENE-DFC2-3-SRAM_ECC: Selene 1 SRAM Low Single-bit ECC error, error status: ... %DEV_SELENE-DFC2-3-SRAM_ECC: Selene 1 SRAM High Multi-bit ECC error, error status: ... %DEV_SELENE-DFC2-3-SRAM_ECC: Selene 1 SRAM Low Single-bit ECC error, error status: ...   Selene is a chip to bridge between two NPU, which connects to GE interfaces each, and Metropolis, which in turn connects to the fabric. The error message indicates that the ingress low priority FIFO queue of the first Selene experience an ECC error.  If there is only one ECC error, the linecard can correct the error. If there are multiple ECC errors on the same packet, the packet will be dropped and that refers to HW failure on the module. Action plan: 1) Verify whether the Multi-bit errors are continued to be observed. If yes, you can proceed with re-seating the module and continue monitoring the performance. 2) If the problem re-surfaces back within the monitoring period, contact TAC to proceed with the RMA for the module replacement.   You can also find “DEV_SELENE” related errors on below link http://www.cisco.com/c/en/us/td/docs/ios/15_0sy/system/messages/15sysmg/sm15sy03.html   Document Source: DEV_SELENE-DFC2-3-SRAM_ECC https://supportforums.cisco.com/discussion/12299696/devselene-dfc2-3-sramecc ... View more

Introduction: This document is created from CSC Discussion. Problem Details: When customer performs ssh <ip> On ASR9k, we see the below messages on the console.   P/0/RSP0/CPU0:Apr 21 05:31:41 : SSHD_[65747]: %SECURITY-SSHD-3-ERR_GENERAL : Failed to allocate pty RP/0/RSP0/CPU0:Apr 21 05:31:43 : devc-vty[181]: %MGBL-TTY-3-KERNEL : Unexpected internal error encountered 'Resource temporarily unavailable' : pkg/bin/devc-vty : (PID=557258) : -Traceback= 4bc37e70 4de37b0c 4de3c3d4 4bc3a2d0 4bc3df28 4bc3540c 4bc3cd00 4ba74650 4ba7514c 4ba702c8 4bc5754c 4bc58464 40000130 40000d18 RP/0/RSP0/CPU0:Apr 21 05:31:43 : devc-vty[181]: %MGBL-VTY-3-SESSION : Error performing TTY session operation 'Checking access parameters for VTY': a194060d, ''tty-server' detected the 'fatal' condition 'TTY SERVER INTERNAL: Unknown error condition': Permission denied' Workaround: 1) Restart the devc-vty process on the active RSP. process restart devc-vty location all 2) Use Telnet Known Affected Releases: 4.2.3.BASE 4.3.2.MGBL   Known Fixed Releases: 4.3.2.SP1 4.3.2.SP2 4.3.2.SP3 4.3.4.9i.BASE 5.1.0.SP1 5.1.1.13i.BASE 5.1.11.8i.BASE 5.1.2.5i.BASE 5.2.0.7i.BASE   Please Contact TAC for more information . Related Bug: CSCuj61034 https://tools.cisco.com/bugsearch/bug/CSCuj61034 Document Source: https://supportforums.cisco.com/discussion/12182226/asr9k-access-ssh-does-not-work ... View more

Introduction: In this document we will be discussing on NX-OS "Configuration Rollback" feature. The rollback feature allows you to take a snapshot, or user checkpoint, of the Cisco NX-OS configuration and then reapply that configuration to your device at any point without having to reload the device. This checkpoint can be extremely useful when a new change is being tested and want immediate return to an original/stable configuration if any problem occurs. You can also create multiple checkpoints to save different version of your running configuration. When you roll back the running configuration, you can trigger the following rollback types: Atomic: it’s a default type and Implement a rollback only if no errors occur. Best-effort: Implement a rollback and skip any errors. Stop-at-first-failure: Implement a rollback that stops if an error occurs. Verbose: Displays the execution log and allows the user to see the events occurring during configuration rollback.   Please read Guidelines and Limitations for rollback configuration and High Availability Configuration Example: Let's first verify for any checkpoint configured on device. N5K# sh checkpoint summary N5K# We don’t have any checkpoints configure yet. Let's create one N5K# checkpoint ? <CR> WORD Checkpoint name (Max Size 32) description Checkpoint description for the given checkpoint file Create configuration rollback checkpoint to file N5K# checkpoint test description "testing_purpose" ..Done N5K# Verify created checkpoint using “sh checkpoint summary” command N5K# sh checkpoint summary User Checkpoint Summary ------------------------------------------------------------------------------- 1) test: Created by admin Created at Mon, 07:37:22 29 Sep 2014 Size is 5,824 bytes Description: "testing_purpose" N5K# Now let's verify what feature we have enabled and configuration of any one of interface of box. N5K(config)# sh run | in feature feature telnet no feature http-server N5K(config)# sh run int e1/1 !Command: show running-config interface Ethernet1/1 !Time: Mon Sep 29 07:40:53 2014 version 5.1(3)N1(1) interface Ethernet1/1 N5K(config)# As you can see we have only telnet enabled and no configuration on interface e1/1, so let's turn on some feature.   N5K(config)# feature hsrp N5K(config)# feature vrrp N5K(config)# int e1/1 N5K(config-if)# switchport mode trun N5K(config-if)# switchport trunk allowed vlan 150 N5K(config-if)# no sh N5K(config-if)#end   Verify running config N5K# sh run | in feature feature telnet no feature http-server feature vrrp feature hsrp N5K# sh run int e1/1 !Command: show running-config interface Ethernet1/1 !Time: Mon Sep 29 07:43:48 2014 version 5.1(3)N1(1) interface Ethernet1/1 switchport mode trunk switchport trunk allowed vlan 150 N5K#   Check the differences of checkpoint config with running one with “sh diff rollback-patch checkpoint test running-config” command as shown below:   N5K# sh diff rollback-patch checkpoint test running-config Collecting Running-Config #Generating Rollback Patch feature vrrp feature hsrp ! interface Ethernet1/1 switchport mode trunk switchport trunk allowed vlan 150 So you can see the difference between current configuration and created checkpoint and will be extremely useful when you are doing new change and want immediate return to an original/stable configuration if any problem occurs. We will rollback running config to checkpoint:   N5K# rollback running-config checkpoint test Collecting Running-Config Generating Rollback patch for switch profile Rollback Patch is Empty Note: Applying config parallelly may fail Rollback verification Collecting Running-Config #Generating Rollback Patch Executing Rollback Patch Generating Running-config for verification Generating Patch for verification Rollback completed successfully.   Verifying running config:   N5K# sh run int e1/1 !Command: show running-config interface Ethernet1/1 !Time: Mon Sep 29 08:07:28 2014 version 5.1(3)N1(1) interface Ethernet1/1 N5K# sh run | in feature feature telnet no feature http-server N5K#   As discussed above, if you do rollback with verbose keyword will give you events occurring during configuration rollback.   N5K# rollback running-config checkpoint test verbose Collecting Running-Config Generating Rollback patch for switch profile Rollback Patch is Empty Note: Applying config parallelly may fail Rollback verification Collecting Running-Config #Generating Rollback Patch Executing Rollback Patch ======================================================== `config t ` `interface Ethernet1/1` `no switchport trunk allowed vlan` `no switchport mode` `exit` `no feature hsrp` `no feature vrrp` `end` ======================================================== Generating Running-config for verification Generating Patch for verification Rollback completed successfully.   There are some of the limitation like you can’t run checkpoint on storage vdc, also if you enable "feature fcoe" on 5k it will disable rollback as shown below:   N5K# sh diff rollback-patch running-config checkpoint test ERROR: FCOE is enabled. Disabling rollback module   To delete all checkpoints, two things can be done: 1. ‘write erase’ command and reload the switch 2.  ‘clear checkpoint database’ command Hope you like it, share your views and experience with us. Related Information: Nexus7k:Configuring Rollback ... View more