VLAN is associated only to the template and not to the pool

Solution Verified - Updated -

Issue

  • We have a RHEV 3.4.2-0.2 installation and we now need to deploy automatic pools from the same template in different VLANs. Having configured the sistem, we have detected that the VLAN association is done with the template and not the pool. So, we need to generate a template for each of the VLANs we need, making their administration quite complex.
  • In parallel, we've noticed that on the level of the virtual machine (once it's generated) we can modify the association to another VLAN. However, as it as an automatic pool, it does not seem valid to be change the given association every time we generare a virtual machine.
  • Is there a way to solve this issue?

Environment

  • Red Hat Enterprise Virtualization 3.4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.