Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


show ovsdb commit failures



Display configurations of Open vSwitch Database (OVSDB)-managed Virtual Extensible LANs (VXLANs) and associated logical interfaces that the Juniper Networks switch dynamically configured but was unable to commit.

For each OVSDB-managed VXLAN and associated logical interface that you plan to implement in a Junos OS environment, you must configure equivalent entities in NSX Manager or in the NSX API for an NSX environment, or in the Contrail Web user interface for a Contrail environment. The software-defined networking (SDN) controller pushes these configurations to the connected Juniper Networks switch by way of the OVSDB schema for physical devices. After the Juniper Networks switch receives these configurations, it dynamically configures a Junos OS-equivalent VXLAN and associated logical interface, and attempts to commit the configurations.

During the commitment of the dynamic configurations, If there is an issue with one or more of the configurations, all configurations in the transaction, even the ones that are correctly configured, remain uncommitted and are saved in a queue. All configurations in the transaction remain uncommitted and in the queue until you troubleshoot and resolve the configuration issues. After you resolve the configuration issues, you must use the clear ovsdb commit failures command to remove the transaction from the queue and retry committing the configurations.


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.

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.



Display information about an erroneous transaction.


Display information about the transaction with the specified numerical ID.

Required Privilege Level


Output Fields

Table 1 lists the output fields for the show ovsdb commit failures command. Output fields are listed in the approximate order in which they appear.

Table 1: show ovsdb commit failures Output Fields

Field Name

Field Description

Txn ID

ID assigned to a transaction by the Juniper Networks switch.


Name of the VXLAN that the Juniper Networks switch dynamically configured but was unable to commit the configuration of.


Name of an OVSDB-managed physical interface that is associated with the VXLAN.


ID that is assigned to the VXLAN.

Sample Output

show ovsdb commit failures

show ovsdb commit failure (Specific Transaction)

Release Information

Command introduced in Junos OS Release 14.1X53-D26.