Displaying the Transaction History
You can display the list of executed transactions by using the transaction-show command. For example in this case committed transaction 20 corresponds to a command in which port 12 was disabled:
CLI (network-admin@switch) > transaction-show
command: port-config-modify port 12 disable
undo-command: port-config-modify port 12 enable
The Netvisor ONE transaction log file contains the list of commands corresponding to the executed transactions as well as the undo command(s) required to undo each transaction. Commands are shown in the transaction-show output for informational purposes only.
Each transaction can have a local, cluster or fabric scope. For example acceptance of the EULA is a transaction that is local to each device:
CLI (network-admin@switch) > transaction-show transaction-scope local
command: switch-setup-modify eula-accepted true eula_timestamp 2019-06-02,21:50:35
undo-command: switch-setup-modify eula-accepted false eula_timestamp 1969-12-31,16:00:00
On the other hand, for instance transactions of VLAN creation and deletion are usually (but not necessarily always) executed with a fabric scope. Other objects such as vNETs are created and deleted with a fabric scope too, as shown in the example below:
CLI (network-admin@switch) > transaction-show transaction-scope fabric
command: vlan-create id 100 type public vxlan-mode standard scope fabric stats
undo-command: vlan-delete id 100
command: vnet-create id c00025b:1 name vn1 scope fabric vrg c00025b:0 vlan-type public vlans 5 config-admin create-vnet-mgr vnet-mgr-storage-pool rpool vnet_mgr_id c00025b:0 vnet_mgr_zone_id c00025b:1 vnet_mgr_location 1 vrg_created_by_vnet true admin_role c00025b:400
undo-command: vnet-delete name vn1
command: vlan-delete id 100
undo-command: vlan-create id 100 type public hw-vpn 0 hw-mcast-group 0 replicators "" repl-vtep :: in_hw false public-vlan 100 user_public_id 0 public_id_set_by_user false scope fabric description vlan-100 label "vlan 100" active yes stats uses_refcnt no refcnt 0 vrg 0:0 ports 1-69 untagged-ports none send-ports 21,23,31-34,53,57,61,65,69,272-275 active-edge-ports 272 non-auto-ports none ports-specified false initialized true flags ""
command: vnet-delete name vn1
undo-command: vnet-create id c00025b:1 name vn1 scope fabric vrg c00025b:0 vlan-type public vlans 5 config-admin admin 40000 create-vnet-mgr vnet-mgr-name vn1-mgr vnet-mgr-storage-pool rpool vnet_mgr_id c00025b:0 vnet_mgr_zone_id c00025b:1 vnet_mgr_location 1 vrg_created_by_vnet true global false allow_admin_access false admin_role c00025b:400
In case of clusters (that is, pairs of redundant devices described in more detail later in this guide) certain transactions are applied to both nodes as if they were a single logical device.
You can choose the transaction information format for a node by typing the transaction-show command followed by the format parameter to choose a tabular or a vertical output. For example:
CLI (network-admin@switch) > transaction-show format all layout vertical
command: --unrecoverable-- vlan-delete id 22
undo-command: --unrecoverable-- vlan-create id 22 nvid a000030:16 scope fabric name vlan-22 active yes stats vrg 0:0 ports 1-72,128-129,255 untagged-ports none send-ports 31,41,47-48,51,65-66 active-edge-ports none ports-specified false flags
command: vlan-create id 35 scope fabric stats ports-specified true
Please note that, in this command’s output, the scope parameter indicates which set of transactions are displayed, as each scope has an independent set of transactions associated with it. As shown in this example, Netvisor ONE uses fabric as the default scope unless another scope is specified.
Also note that you should not copy and paste commands and undo-commands from this output because they may include information that does not apply to a different context. As a matter of fact, as mentioned earlier, Netvisor ONE displays the fields for informational purposes only so as to allow you to see exactly what happens to the configuration when you roll forward or roll back the transaction ID.
Once you decide which node to modify and the transaction to roll forward or roll back to, you can use the transaction-rollforward-to or transaction-rollback-to commands to re-run the command (roll forward) or undo the command (roll back) on the node being troubleshooted, or even in a broader scope, as described in the following sections.