H3C Technologies H3C S6800 Series Switches - Manual (Page 66)

58
Configuring the VTEP as an OVSDB VTEP
Overview
An H3C network virtualization controller (NVC) can use the Open vSwitch Database (OVSDB)
management protocol to deploy and manage VXLANs on VTEPs. To work with an NVC, you must
configure the VTEP as an OVSDB VTEP.
Protocols and standards
RFC 7047, The Open vSwitch Database Management Protocol
OVSDB configuration task list
Tasks at a glance
(Required.) Establishing an OVSDB connection with a controller :
• Establishing an active SSL connection to a controller
• Listening for SSL connection requests from controllers
• Establishing an active TCP connection to a controller
• Listening for TCP connection requests from controllers
(Required.) Enabling the OVSDB server
(Required.) Enabling VTEP mode
(Required.) Specifying a global source address for VXLAN tunnels
(Required.) Specifying a VTEP access port
(Optional.) Disabling source MAC check
(Optional.) Disabling remote-MAC address learning
(Optional.) Enabling flood proxy on all multicast VXLAN tunnels
Configuration prerequisites
Before you configure the VTEP as an OVSDB-VTEP, enable L2VPN by using the l2vpn enable command.
For more information, see MPLS L2VPN commands in MPLS Command Reference.
Establishing an OVSDB connection with a controller
The device supports the following types OVSDB connections:
• Active SSL connection—The device initiates an SSL connection to the controller.