transaction-rollback-to
This command is used to roll back the fabric to a specific fabric transaction number. If a failure occurs on the fabric, transactions on nodes in the fabric can become out of synch. Once transactions are out of synch, no further transactions can be executed across the scope of local, fabric, or cluster. Unjoining, and rejoining the fabric causes the node to lose configuration.
As part of a single node transaction recovery, you can roll back the transaction number to a previous one.
Syntax transaction-rollback-to
|
scope local|cluster|fabric |
Specify if you want to rollback the transaction number on a local, cluster, or fabric scope. |
|
tid tid-number |
Specify the transaction number to rollback the transaction. |
|
ignore-error|no-ignore-error |
Specify if you want ignore errors when this command is executed. Use with CAUTION. |
Defaults None
Access CLI
History
|
Version 2.2.3 |
Command introduced. |
|
Version 3.0.0 |
The parameter ignore-error added. |
Usage Use this command to roll back the fabric to a specific transaction ID number. This may be necessary to resynchronize the fabric without forcing nodes to unjoin, and rejoin the fabric. If multiple nodes are out of synch, you must recover each node separately.
Examples To roll back to the fabric transaction ID to 14, use the following syntax:
CLI (network-admin@switch) > transaction-rollback-to transaction-scope fabric tid 14
This command produces output only if an error has occurred during the transaction.
CLI (network-admin@switch) > transaction-rollback-to transaction-scope fabric tid 5
Warning: rolled back transactions are unrecoverable unless another fabric node has them. Proceed? [y/n] y