← Back to team overview

openstack team mailing list archive

Re: [essex vlan]cannot ping vm on other compute node

 

inline

On Tue, Feb 26, 2013 at 10:51 PM, Ajiva Fan <aji.zqfan@xxxxxxxxx> wrote:

> greeting, stackers
>
> i deploy essex with flatdhcp, it works for a long time, but currently
> i want to use vlan network, so i deploy a new environment everything
> is same as the previous one, just use vlan network.
>
> here is the probelm:
> i cannot ping vm on other compute node
>
> control node (all-in-one)
> public nic(eth0): 172.16.1.12
> vlan nic(eth1):
> vlan105
> br105 10.0.12.6
> compute node(nova-compute, nova-network)
> public nic(eth0): 172.16.1.13
> vlan nic(eth1):
> vlan105
> br105 10.0.12.4
>
> now i create 2 vm, one is 10.0.12.5 on control node, another one is
> 10.0.12.3 on compute node
>
> i cannot ping 10.0.12.4 from control node, so i cannot ping 10.0.12.3
> neither
>
> using tcpdump -nnxx -i eth1 host 10.0.12.3, i capture ARP package from
> control node with vlan tag 8100 0069 0806 0001 0800 0604, so i think
> it works right so far. but on compute node i use tcpdump -i eth1 host
> 10.0.12.3 and get nothing.
>
> the cables connect to eth1 are plugged into a cisco catalyst 2950
> swither port 22 and 23, working under trunk mode, it allows all vlan
> by default
>
> i guess the problem may be caused by wrong setting of switcher since
> packets are dropped, but i'm not very sure.
>
>
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.


> after two days search answer on the internet, i've no idea how to
> solve this question, so please help me
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

Follow ups

References