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 <msweet....@gmail.com> 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.
>
> Example networking on Ubuntu 12.04:
> ==============
> iface management0 inet manual
>  bond-mode active-backup
>  bond-miimon 100
>  bond-slaves none
>  up /sbin/ifenslave      management0 eth0 eth1
>  down /sbin/ifenslave -d management0 eth0 eth1
>
> iface vlan20 inet manual
>  vlan-raw-device management0
>
> iface privatebr0 inet static
>  bridge_ports vlan20
>  bridge_fd 0
>  bridge_stp off
>  bridge_maxwait -1
>  address 172.16.0.12
>  netmask 255.255.255.0
> ==============
>
> Marty
>
>
> On Sun, Dec 15, 2013 at 6:05 PM, Ahmad Emneina <aemne...@gmail.com> wrote:
>
> > 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 <tawfiq.z...@gmail.com>
> > wrote:
> >
> > > 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.
> > >
> >
>

Reply via email to