openstack team mailing list archive

[Ajiva Fan <aji.zqfan@xxxxxxxxx>]

thank you for your help

i guess you point a way to figure out whether the switcher is working
correctly or not
after i add a vlan 5 to eth1 and an ip addr to it, the switcher works
fine, ping get reply

so the switch trunk port seems no problem

but br105 got a 10.0.12.{4,6}/24 as well, and also vlan105@eht1 is
created by nova-network

here is console output:
# ip addr show br105
br105: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
    link/ether fa:16:3e:3b:cd:60 brd ff:ff:ff:ff:ff:ff
    inet 10.0.12.4/24 brd 10.0.12.255 scope global br105
    inet6 fe80::9890:d8ff:fe8f:48a9/64 scope link
       valid_lft forever preferred_lft forever

#ip addr show vlan105
vlan105@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
master br105 state UP
    link/ether fa:16:3e:3b:cd:60 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::f816:3eff:fe3b:cd60/64 scope link
       valid_lft forever preferred_lft forever

#brctl show
bridge name	bridge id		STP enabled	interfaces
br105		8000.fa163e3bcd60	no		vlan105
							vnet0
virbr0		8000.000000000000	yes

here is nova.conf network section:
# cat /etc/nova/nova.conf
...
network_manager=nova.network.manager.VlanManager
vlan_interface=eth1
vlan_start=100
force_dhcp_release=True
dhcpbridge_flagfile=/etc/nova/nova.conf
dhcpbridge=/usr/bin/nova-dhcpbridge
firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
public_interface=eth0
fixed_range=10.0.0.0/16
multi_host=true
routing_source_ip=172.16.1.13
my_ip=172.16.1.13
flat_injected=false
...


may be somewhere i'm wrong, i think ifconfig eth0.5 may be eth1.5
i run ifconfig eth0.5 10.2.2.2/24 it reports eth0.5: ERROR while
getting interface flags: No such device, i think this is because vlan
is added on eth1 not eth0, if i'm wrong please let me know, thanks
again

---------------
You could do:

on host connected to port 22 on the switch
vconfig add eth1 5
ifconfig eth0.5 10.2.2.2/24

on host connected on port 23
vconfig add eth1 5
ifconfig eth0.5 10.2.2.3/24

and then try to ping through the switch (ping 10.2.2.2) in order
switch to rule it out.