<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Sep 27, 2017 at 4:25 PM, Michael Burman <span dir="ltr"><<a href="mailto:mburman@redhat.com" target="_blank">mburman@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div>Hello Gianluca,<br><br></div>Not sure i fully understood, but, if the host's IP has changes and the vlan then the correct flow will be:<br><br></div>1) Remove the host <br></div>2) Edit the management network with vlan tag - the vlan you need/want<br></div>3) Add/install the host - make sure you using the correct/new IP(if using IP) or the correct FQDN(if has changed).<br><br></div>Note that doing things manually on the host such as changing ovirtmgmt's configuration without the engine or vdsm may cause problems and will not persist the changes during reboots. If the host's IP has changed or it's FQDN then you must install the host again. <br><br></div>Cheers)<br></div><div class="gmail_extra"><span class="HOEnZb"><font color="#888888"><div class="m_4677787421954493818gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"></div></div>
</font></span></div>
</blockquote></div><br></div><div class="gmail_extra">Original situation was:</div><div class="gmail_extra"><br></div><div class="gmail_extra">1 DC</div><div class="gmail_extra">1 Cluster: CLA with 2 hosts: host1 and host2</div><div class="gmail_extra">ovirtmgmt defined on vlan10</div><div class="gmail_extra"><br></div><div class="gmail_extra">engine is an external server on VLAN5 that can reach VLAN10 of hosts</div><div class="gmail_extra">So far so good</div><div class="gmail_extra"><br></div><div class="gmail_extra">Need to add another host that is in another physical server room. Here VLAN10 is not present, so I cannot set ovirtmgmt</div><div class="gmail_extra">If I understand correctly, the VLAN assigned to ovirtmgmt is a DC property: I cannot have different vlans assigned to ovirtmgmt in different clusters of the same DC, correct?</div><div class="gmail_extra"><br></div><div class="gmail_extra">So the path:</div><div class="gmail_extra">Create a second cluster CLB and define on it the logical network ovirtmgmt2 on VLAN20 and set it as the mgmt network for that cluster</div><div class="gmail_extra">Add the new host host3 to CLB.</div><div class="gmail_extra"><br></div><div class="gmail_extra">So far so good: the engine on VLAN5 is able to manage the hosts of CLA ad CLB with their mgmt networks in VLAN10 and VLAN20</div><div class="gmail_extra"><br></div><div class="gmail_extra">Now it is decided to create a new VLAN30 that is transportable across the the 2 physical locations and to have host1, host2, host3 to be part of a new CLC cluster where the mgmt network is now on VLAN30</div><div class="gmail_extra"><br></div><div class="gmail_extra">Can I simplify operations, as many VMs are already in place in CLA and CLB?</div><div class="gmail_extra">So the question arises:</div><div class="gmail_extra"><br></div><div class="gmail_extra">the 3 hosts were added originally using their dns hostname and not their IP address.</div><div class="gmail_extra">Can I change my dns settings so that the engine resolves the hostnames with the new IPs and change vlan of ovirtmgmt?</div><div class="gmail_extra"><br></div><div class="gmail_extra">And if I decide to start from scratch with this new cluster CLC on VLAN30, can I retain my old 3 hostnames (resolving to their new IPs)? How?</div><div class="gmail_extra"><br></div><div class="gmail_extra">Hope I was able to clarify a bit the scenario</div><div class="gmail_extra"><br></div><div class="gmail_extra">Gianluca </div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div></div>