clear ovsdb commit failures
Syntax
clear ovsdb commit failures <transaction-id>
Description
Remove a transaction from a queue maintained by
a Juniper Networks switch that supports the Open vSwitch
Database (OVSDB) management protocol and Virtual Extensible
LANs (VXLANs). The transaction includes OVSDB-managed VXLANs and associated
logical interfaces that the Juniper Networks switch dynamically configured
and tried to commit but was unable to because of an issue with one
or more of the configurations. In addition to removing the transaction,
entering the clear ovsdb commit failures command causes
the Juniper Networks switch to automatically retry committing all
configurations in the transaction.
If there is an issue with one or more of the configurations in a transaction, this causes all configurations in the transaction, even the ones that are correctly configured, to remain uncommitted and in the queue until you troubleshoot and resolve the configuration issue(s).
You can display an erroneous transaction by entering the show ovsdb commit failures command. In the output that appears,
you must determine which configuration(s) are erroneous and therefore
prevent the Juniper Networks switch from committing the configurations
in the transaction.
Issues that can cause commitment errors include but are not limited to the detection of the same VXLAN name or VXLAN network identifier (VNI) in a dynamically configured VXLAN and in a VXLAN that was previously configured using the Junos OS CLI.
To monitor for issues with dynamically configured OVSDB-managed VXLANs and their associated interfaces, we recommend checking for system log messages and traceoptions files for OVSDB.
After resolving the error(s), enter the clear ovsdb commit
failures command to remove the transaction from the queue and
retry committing all configurations in the transaction.
While an erroneous transaction exists in the queue, the Juniper Networks switch cannot commit the dynamic configurations of additional VXLANs and their associated logical interfaces. The commitment of these VXLANs and logical interfaces remain in a pending state until all VXLAN and logical interface configurations in the erroneous transaction are resolved and successfully committed.
Options
| none | Remove the transaction
that currently appears in the |
| transaction-id | Remove the transaction with the specified numerical ID, and retry committing the configurations in the transaction. |
Required Privilege Level
clear
Sample Output
clear ovsdb commit failures
user@host> clear ovsdb commit failures
clear ovsdb commit failures (Specific Transaction)
user@host> clear ovsdb commit failures 1
Release Information
Command introduced in Junos OS Release 14.1X53-D26.