<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hello everyone!</div>
<div> </div>
<div>I want to notice that initially it wasn't a trouble I've encountered myself, a person we used to work together complained that he couldn't get an answer from openstack forums or mailing lists. I tried to look for solution and found that one probably has to alter neutron-lib package and change constants that are defined here: <a href="https://github.com/openstack/neutron-lib/blob/1.13.0/neutron_lib/constants.py#L295" rel="nofollow" title="Follow link">https://github.com/openstack/neutron-lib/blob/1.13.0/neutron_lib/constants.py#L295</a> to adjust the tag range.</div>
<div> </div>
<div>Initial question content was:</div>
<div>
<div>Recently I've encountered a neutron issue related to port tagging mechanism, and wonder if anyone else ever did. The initial source of the issue was, as it seems, identical numeration of external VLANs' tags and OVS (exactly br-int) port tags. The VLAN tagged 222 was added to bridge br-ex and everything worked, but at some point firewall reported unusual traffic. Thus I'd found that there was a loop and 2 qr-* ports with the same tag 222 attached to br-int. After that I deleted them and the loop was gone.</div>
<div> </div>
<div>So the question is what exactly these tags are? The same ethernet frame bits as 802.1Q tags? Where is a pool or something they're taken from? Is there any possibility to form such pool via configs or patches? Has anyone ever encountered such situation?</div>
<div> </div>
<div>If anyone has anything to say on subject we both would be very grateful.</div>
<div> </div>
<div>Thanks in advance,</div>
<div>Maria</div>
</div></div></body></html>