In my case i have to update
also vlan table on CS database because after few minutes/hours,
CS update again VMware port group to original vlan_id.
Regards
Il 19/12/2013 16:17, tawfiq zidi ha
scritto:
Hi ,
Hi ,
Well I found the Way to resolve this Problem :).
You have to update vmware traffic label with the VLAN number.
Thank you for Help.
On Wed, Dec 18, 2013 at 3:03 PM, tawfiq zidi wrote:
> Thank you for Replying.
>
> I'm using Vmware Esxi 5.0 with vCenter in my installation.
>
> I see that
Thank you for Replying.
I'm using Vmware Esxi 5.0 with vCenter in my installation.
I see that each time a vRouter Create , a control port is Created as:
cloud.private.untagged.0.1-vSwitch
Is it possible to always tag this port with VLAN 20 ?
On Sun, Dec 15, 2013 at 8:37 PM, Marty Sweet wrote:
Depending on the hypervisor (for example this would work with KVM), you
could still tag management traffic down to each host, just manually setting
up a network interface (ex. privatebr0) and set the 'KVM Traffic label'
accordingly.
Not sure how effective this would be with other hypervisors.
Exam
I believe the management range for a pod has to be untagged. It does seem
like a legacy requirement at this point. You might want to file a feature
enhancement ticket @ https://issues.apache.org/jira/secure/Dashboard.jspa
On Sun, Dec 15, 2013 at 5:37 AM, tawfiq zidi wrote:
> Hi,
>
> Is it possi
Hi,
Is it possible to tag a specific VLAN for a POD range ?
*For example a want to tag a VLAN (20) for private addesses
172.16.0.0/24for POD1.
The default installation always gives untagged VLAN.
