configure the OVSDB server to listen for incoming connections from OVSDB controllers.
| schema | OVSDB schema. |
| hardware_vtep | Specifies Hardware VXLAN Tunnel End-Point (VTEP). |
| add | Add to the local OVSDB server. |
| delete | Delete from the local OVSDB server. |
| connection | Specifies OVSDB connection. |
| server | Specifies to wait for incoming connections. |
| tcp | Specifies unencrypted TCP connection to remote server. |
| ssl | Specifies encrypted connection using SSL/TLS to remote server. |
| ipaddress local_ip | Specifies IP address of local VLAN (Virtual LAN) to listen on (default is 0.0.0.0). |
| port local_port | Specifies TCP port number to listen on. |
N/A.
You can configure the OVSDB server to listen for incoming connections from OVSDB controllers. A switch in factory default configuration does not listen on any local ports. The OVSDB server in ExtremeXOS listens for incoming connections from managers listed in the relevant manager tables of the OVSDB database being served. For example, if the manager table in the Hardware VTEP database has an entry for PTCP:6640, then ExtremXOS listens for connections on that port number.
When using SSL for OVSDB connections, an SSL certificate must be configured on ExtremeXOS. It is recommended that all CLI-configured OVSDB connections should be either client or server connections; client and server OVSDB connections should not be configured simultaneously.
configure ovsdb schema hardware_vtep add connection server tcp port 6640
configure ovsdb schema hardware_vtep delete connection server tcp port 6640
This command was first available in ExtremeXOS release 22.1.
This command is supported on the Summit X770, X670-G2, and ExtremeSwitching X590, X870, X690 series switches, and stacks with X590, X770, X670-G2, X870, and X690 slots only.
Print
this page
Email this topic
Feedback
View PDF
Download EPUB