<div dir="auto"><br><div class="gmail_extra" dir="auto"><br><div class="gmail_quote">Il 22 gen 2018 7:49 PM, "Staniforth, Paul" <<a href="mailto:P.Staniforth@leedsbeckett.ac.uk" target="_blank">P.Staniforth@leedsbeckett.ac.<wbr>uk</a>> ha scritto:<br type="attribution"><blockquote class="m_1507931259227897633quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr" style="font-size:12pt;color:#000000;background-color:#ffffff;font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Hello,</p>
<p> We have an oVirt 4.1 cluster of 3 ovirt-nodes that currently on the management network don't have VLAN tagging enabled, we would like to enable VLAN tagging and so would be grateful of anyone had an information or experience doing this.</p>
<p><br>
</p>
<p>The management engine is running on a separate host and the 3 hosts are running oVirt Node 4.1.6</p></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Hi Paul, i did the same with the same release.</div><div dir="auto"><br></div><div dir="auto">The trick was to set the tagging also of the default vlan on the switch during the change from untagged to tagged.</div><div dir="auto"><br></div><div dir="auto">In example, if you have to move your ovirtmgmt to vlan 10, you can set your port for serving the network both native and tagged so while changing the ovirtmgmt setup you will not lose the connectivity.</div><div dir="auto"><br></div><div dir="auto">Luca</div><div class="gmail_extra" dir="auto"></div></div>