ovsdb-managed
Syntax
ovsdb-managed;
Hierarchy Level
[edit bridge-domains bridge-domain-name vxlan], [edit routing-instances routing-instance-name bridge-domains bridge-domain-name vxlan], [edit routing-instances routing-instance-name switch-options], [edit routing-instances routing-instance-name vlans vlan-name vxlan], [edit routing-instances routing-instance-name vxlan], [edit switch-options], [edit vlans vlan-name vxlan]
Description
Disable a Juniper Networks device from learning about other Juniper Networks devices that function as hardware virtual tunnel endpoints (VTEPs) in a specified Virtual Extensible LAN (VXLAN) and the media access control (MAC) addresses learned by the hardware VTEPs. Instead, the Juniper Networks device uses the Open vSwitch Database (OVSDB) management protocol to learn about the hardware VTEPs in the VXLAN and the MAC addresses learned by the hardware VTEPs.
The specified VXLAN must have a VXLAN network identifier (VNI)
configured, using the vni statement in the [edit bridge-domains bridge-domain-name vxlan], [edit routing-instance routing-instance-name vxlan], or [edit vlans vlan-name vxlan] hierarchy.
Also, for OVSDB-managed VXLANs, the multicast scheme described
in Understanding How Layer 2 BUM and Layer
3 Routed Multicast Traffic Are Handled with OVSDB is used.
Therefore, specifying the multicast-group statement in
the [edit bridge-domains bridge-domain-name vxlan], [edit routing-instances routing-instance-name vxlan], or [edit vlans vlan-name vxlan] hierarchy has no effect.
Required Privilege Level
admin—To view this statement in the configuration.
admin-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 14.1R2.