Thanks Slawek. Is it possible to define two vlan ranges for one physnet for example 200 to 300 and 3500 to 3600?
Ammad
On Thu, Dec 16, 2021 at 12:42 PM Slawek Kaplonski skaplons@redhat.com wrote:
Hi,
On środa, 15 grudnia 2021 22:19:23 CET Ammad Syed wrote:
Hi,
I am using neutron xena release with OVN. I have currently defined the
vlan
range "network_vlan_ranges = vlannet1:3500:3600" in ml2_conf.ini.
I have set bridge mapping via ovs with the below command.
ovs-vsctl set open . external-ids:ovn-bridge-mappings=vlannet1:br-vlan
Now I have to add a new vlan range. Can anyone confirm the syntax of ml2_conf.ini and bridge mapping.
network_vlan_ranges = vlannet1:3500:3600,vlannet2:300:400
That syntax is correct. This config option is comma-separated list of physnets and ranges as You did above.
ovs-vsctl set open . external-ids:ovn-bridge-mappings=vlannet1:br-vlan,vlannet2:br-vlan
Need to confirm the correct way to add new vlan range if the server is currently live ? Can we use the same bridge with two different mapping
i.e
vlannet1 and vlannet2 ?
No. On bridge can be mapped to one physical network. We even had proposal to change it recently: https://bugs.launchpad.net/neutron/+bug/1952867 but finally we decided that we don't want to allow that.
Ammad
-- Slawek Kaplonski Principal Software Engineer Red Hat