[
https://issues.apache.org/jira/browse/CLOUDSTACK-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630200#comment-13630200
]
danny webb commented on CLOUDSTACK-2008:
----------------------------------------
ok, it seems this is still an issue if you let cloudstack do the config. So I
have blown away my install and am starting from scratch:
my virt host before the install has only 2 devices:
[root@slo-cnkvm001 ~]# ifconfig -a bond0
bond0 Link encap:Ethernet HWaddr 00:17:A4:77:48:2C
inet6 addr: fe80::217:a4ff:fe77:482c/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:779329 errors:0 dropped:0 overruns:0 frame:0
TX packets:272393 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:69545398 (66.3 MiB) TX bytes:149721368 (142.7 MiB)
[root@slo-cnkvm001 ~]# ifconfig -a bond0.60
bond0.60 Link encap:Ethernet HWaddr 00:17:A4:77:48:2C
inet addr:172.18.102.5 Bcast:172.18.102.255 Mask:255.255.255.0
inet6 addr: fe80::217:a4ff:fe77:482c/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:288102 errors:0 dropped:0 overruns:0 frame:0
TX packets:229952 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:30596209 (29.1 MiB) TX bytes:144701944 (137.9 MiB)
and no non-standard bridges. note that the only IP is bound to bond0.60, as
this host exists on a trunked interface whose default VLAN isn't one I want to
be using.
full details here: http://pastebin.com/aysPKGu2
I then do an advanced zone:
Zone: Slough
Guest Cidr: left as default, not going to use it.
Public = vlan 70 nameif cloud-dmz ip address 172.18.103.1 255.255.255.0
public
Management = vlan 60 nameif cloud-admin ip address 172.18.102.1
255.255.255.0 management
Guest net = vlan 50 nameif cloud-internal ip address 172.18.101.1
255.255.255.0 zone guest cidr
after intitial setup I have this one the virt host:
[root@slo-cnkvm002 ~]# brctl show
bridge name bridge id STP enabled interfaces
cloud0 8000.000000000000 no
cloudbr0 8000.0017a4774830 no bond0.60
virbr0 8000.5254001db6bc yes virbr0-nic
cloud0 Link encap:Ethernet HWaddr B2:EF:86:35:1B:FC
inet addr:169.254.0.1 Bcast:169.254.255.255 Mask:255.255.0.0
inet6 addr: fe80::b0ef:86ff:fe35:1bfc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
cloudbr0 Link encap:Ethernet HWaddr 00:17:A4:77:48:30
inet addr:172.18.102.6 Bcast:172.18.102.255 Mask:255.255.255.0
inet6 addr: fe80::217:a4ff:fe77:4830/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1052 errors:0 dropped:0 overruns:0 frame:0
TX packets:681 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:144230 (140.8 KiB) TX bytes:151059 (147.5 KiB)
I enable the zone and wait for the system VMs to come online.
once that is done I got to infrastructure -> zone -> physical network -> guest
and add these 2 networks
vlan 80 ip address 10.10.10.0 255.255.255.0
vlan 90 ip address 10.10.11.0 255.255.255.0
then I create a guest, and in doing so it creates this interface:
cloudVirBr80 8000.0017a4774830 no bond0.60.80
so moral of the story is, try starting off with a virt host with its root eth
device on a vlan tagged interface. that seems to break the setup later on.
> guest network vlan tag chain issue
> ----------------------------------
>
> Key: CLOUDSTACK-2008
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2008
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
> Affects Versions: 4.0.1
> Environment: centos 6.4
> HP BL460 G1
> Reporter: danny webb
> Priority: Minor
>
> Hi,
> I have setup a cloudstack instance where my "root" eth device is a vlan
> tagged bond0.60 (as the network I am on has a different default VLAN id than
> my test vlans).
> so I am setup like this:
> bond0.60 / cloudbr0 == management network / ip of box (bond0 == nothing)
>
> bond0.60 Link encap:Ethernet HWaddr 00:17:A4:77:48:3C
> inet6 addr: fe80::217:a4ff:fe77:483c/64 Scope:Link
> UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
> RX packets:37189 errors:0 dropped:0 overruns:0 frame:0
> TX packets:34030 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:4476334 (4.2 MiB) TX bytes:31055747 (29.6 MiB)
> cloudbr0 Link encap:Ethernet HWaddr 00:17:A4:77:48:3C
> inet addr:172.18.102.8 Bcast:172.18.102.255 Mask:255.255.255.0
> inet6 addr: fe80::217:a4ff:fe77:483c/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:36531 errors:0 dropped:0 overruns:0 frame:0
> TX packets:32606 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:4435824 (4.2 MiB) TX bytes:30976056 (29.5 MiB)
>
> when it went to setup a new guest network (with a vlan id of 80) it created
> it ontop of the bond0.60 like:
>
> bond0.60.80 Link encap:Ethernet HWaddr 00:17:A4:77:48:3C
> inet6 addr: fe80::217:a4ff:fe77:483c/64 Scope:Link
> UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:13777 (13.4 KiB)
>
> [root@slo-cnkvm004 ~]# brctl show
> bridge name bridge id STP enabled interfaces
> cloud0 8000.000000000000 no
> cloudVirBr80 8000.0017a477483c no
> bond0.60.80
>
> which doesn't seem to work and I am pretty sure is syntactically wrong. I
> can't ping any guests that come up on that network. When creating new
> devices it should I believe be creating them off of the base eth device (ie
> eth0, or bond0).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
