# Revision history [back]

Don't touch br-int. The openvswitch agent configures it. See the 2nd diagram at https://docs.openstack.org/ocata/networking-guide/deploy-ovs-selfservice.html#architecture - there is an additional bridge, br-tun.

You map the VXLAN network to ens1f1 by providing the interface's IP address in the openvswitch.ini file:

[ovs]


See the same web page, a bit further down. Your br-ex is called br-provider on that page, and your ens1f1 is interface 3.

Don't touch br-int. br-int. The openvswitch agent configures it. See the 2nd diagram at https://docs.openstack.org/ocata/networking-guide/deploy-ovs-selfservice.html#architecture - there is an additional bridge, br-tun.br-tun.

You map the VXLAN network to ens1f1 ens1f1 by providing the interface's IP address in the openvswitch.ini file:openvswitch.ini file on the compute node:

[ovs]


See the same web page, a bit further down. Your br-ex is called br-provider on that page, and your ens1f1 is interface 3.

Don't touch br-int. The openvswitch agent configures it. See the 2nd diagram at https://docs.openstack.org/ocata/networking-guide/deploy-ovs-selfservice.html#architecture - there is an additional bridge, br-tun. (don't touch that either).

You map the VXLAN network to ens1f1 by providing the interface's IP address in the openvswitch.ini file on the compute node:

[ovs]


See the same web page, a bit further down. Your br-ex is called br-provider on that page, and your ens1f1 is interface 3.

Don't touch br-int. The openvswitch agent configures it. See the 2nd diagram at https://docs.openstack.org/ocata/networking-guide/deploy-ovs-selfservice.html#architecture - there is an additional bridge, br-tun (don't touch that either).

You map the VXLAN network to ens1f1 by providing the interface's IP address in the openvswitch.ini file on the compute node:

[ovs]

[ovs]