Re: Pod VLAN
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 , 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 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. 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 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 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. -- Supernova s.r.l. Via G. Misiticoni, 3 65126 - Pescara ITALY www.netsons.com Domenico De Monte CEO t. (+39) 085 45 100 52 m. (+39) 339 79 033 98 e. d.demo...@netsons.com Netsons® è un marchio registrato dalla Supernova s.r.l. Le informazioni trasmesse sono riservate alla persona o alla società indicata come destinatario, e possono includere contenuti considerati confidenziali. Ogni elaborazione, comunicazione, trasmissione o altro utilizzo, anche azioni conseguenti alla conoscenza di queste informazioni da parte di chiunque non sia espressamente indicato come destinatario è proibita. Nel caso abbiate ricevuto per errore questa comunicazione, siete pregati di darne avviso a info [at] netsons.com ed eliminare ogni stampa ed ogni traccia informatica. Il ricevente dovrà inoltre accertarsi che gli eventuali allegati non contengano virus prima di aprirli. Qualunque opinione o affermazione presentata in questo messaggio è da ritenersi propria dell'autore e non rappresenta necessariamente la posizione della Società. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact: info [at] netsons.com and delete the material from any computer. If this email contains attachments you should ensure they are checked for viruses before opening them. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.
Re: Pod VLAN
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 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. >> >> 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 >> 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 >> > 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. >> > > >> > >> > >
Re: Pod VLAN
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. > > 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 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 > > 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. > > > > > >
Re: Pod VLAN
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 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 > 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. > > >
Re: Pod VLAN
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 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. >
