No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs on the product.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
OVSDB_CLIENT/3/hwOvsdbCfgFailureEvent

OVSDB_CLIENT/3/hwOvsdbCfgFailureEvent

Message

OVSDB_CLIENT/3/hwOvsdbCfgFailureEvent: Failed to deliver OVSDB configurations.(Reason=[Reason], Detail=[Detail])

Description

The OVSDB client fails to deliver the configuration.

Parameters

Parameter Name Parameter Meaning

Reason

Reason why the OVSDB client fails to deliver the configuration.

Detail

Detailed information about the configuration.

Possible Causes

  • Cause 1: Failed to create interface-name because main-interface has been added to an Eth-Trunk.
  • Cause 2: The number of BDs exceeds the upper limit (8000).
  • Cause 3: The BD to which the Layer 2 sub-interface is added does not exist.
  • Cause 4: interface-name does not exist.
  • Cause 5: The BFD session exists.
  • Cause 6: Another encapsulation type has been configured on interface-name.
  • Cause 7: The VLAN has been used by the main interface.

Procedure

  • Cause 1: Failed to create interface-name because main-interface has been added to an Eth-Trunk.

    • Run the undo eth-trunk command in the interface view to remove the main interface from the Eth-Trunk.
    • Use another interface as the Layer 2 sub-interface. You can run the display interface brief command to view the physical interface that has been added to the Eth-Trunk.

  • Cause 2: The number of BDs exceeds the upper limit (8000).
    1. Run the display bridge-domain command to view the information about BD configurations.

      • If the value of State is Down, it indicates that the BD is not used. Go to step 2.
      • If the value of State is Up, it indicates that the BD is in use. In this case, you need to re-plan the BD information.

    2. Run the undo bridge-domain bd-id command to delete the BD.
  • Cause 3: The BD to which the Layer 2 sub-interface is added does not exist.

    When a Layer 2 sub-interface is added to a BD, the BD does not exist. In this case, the VMware NSX controller fails to create a BD, and you need to deliver the configuration again.

  • Cause 4: interface-name does not exist.

    The Layer 2 sub-interface does not exist. In this case, the VMware NSX controller fails to create a Layer 2 sub-interface, and you need to deliver the configuration again.

  • Cause 5: The BFD session exists.

    This problem does not affect service operation, and no action is required.

  • Cause 6: Another encapsulation type has been configured on interface-name.

    Delete the traffic type that has been configured on the Layer 2 sub-interface.

  • Cause 7: The VLAN has been used by the main interface.
    1. Run the display current-configuration | section include interface-name command to view the VLAN ID that has been used on the interface.

    2. Plan a VLAN that is not used and deliver the VLAN on the VMware NSX controller.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 123602

Downloads: 90

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next