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

Configuration Guide - Network Management and Monitoring

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

This document describes the configurations of Network Management and Monitoring, including SNMP, RMON, NETCONF, OpenFlow, LLDP, NQA, Mirroring, Packet Capture, Packet Trace, Path and Connectivity Detection Configuration, NetStream, sFlow, and iPCA.
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).
Licensing Requirements and Limitations for OVSDB

Licensing Requirements and Limitations for OVSDB

Involved Network Elements

Open vSwitch database (OVSDB) connection requires cooperation from the following devices:
  • Controller

    The device can only establish an OVSDB connection with the VMware NSX controller. The VMware NSX controller version is 6.3.3 or later.

  • CE switch

    The device needs to support the OVSDB function.

Licensing Requirements

OVSDB is a basic feature of the switch and is not under license control.

Version Requirements

Table 6-3 Minimum software version supporting OVSDB
Product Minimum Version Required
CE8868EI/CE8861EI V200R005C10
CE8860EI/CE8850EI V200R005C00
CE7850EI/CE7855EI V200R005C00
CE6850HI/CE6850U-HI/CE6851HI/CE6855HI/CE6856HI/CE6860EI/CE6865EI/CE6870EI/CE6875EI V200R005C00

Feature Limitations

  • OVSDB schema is defined based on the vtep.ovsschema table in the open-source open vSwitch. The version is 2.5. For details, see https://github.com/openvswitch/ovs.git.

  • The CE switch can establish an OVSDB connection with the VMware NSX controller only, but cannot establish OVSDB connections with other controllers.

  • No distributed logical router (DLR) can be configured on the logical switch bound to the CE switch.

  • The OVSDB function conflicts with the Ethernet VPN (EVPN) function and therefore, they cannot be configured concurrently.

  • During the interconnection between the CE switch and the VMware NSX controller, bare metal servers and the devices that cannot be virtualized can only be connected to the VXLAN network through one or two stacked CE switches. It is recommended that two CE switches be stacked to improve reliability.

  • After the VMware NSX controller successfully delivers OVSDB schema entries, if the OVSDB client on the CE switch fails to deliver configurations, the VMware NSX controller cannot identify this issue.

  • The OVSDB connection between the device and the controller is established based on Secure Sockets Layer (SSL) encryption. After the device implements an active/standby switchover, the device needs to re-establish an OVSDB connection with the controller.

  • For the device which has established OVSDB connections with a VMware NSX controller cluster, if this device needs to establish OVSDB connections with another VMware NSX controller cluster, run the undo ovsdb server command to disable the OVSDB function globally and delete all OVSDB-related configurations and data, preventing the device from being affected by original OVSDB schema tables.

  • When using the VMware NSX controller to implement VXLAN deployment on the device, you need to manually create NVE interface 1 and configure the IP address of the source VTEP. Otherwise, the VXLAN network cannot be deployed through the VMware NSX controller.

  • When using the VMware NSX controller to implement VXLAN deployment on the device and configuring the access point of the VXLAN service, note that the encapsulation type can only be dot1q or untag, and VLAN 4094 cannot be configured.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075365

Views: 34875

Downloads: 123

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