Re: [Openstack] [essex vlan]cannot ping vm on other compute node
since i notice that in switcher: sw-31show interface fastEthernet 0/22 trunk PortMode Encapsulation StatusNative vlan Fa0/22 on 802.1q trunking 1 Port Vlans allowed on trunk Fa0/22 1-4094 PortVlans allowed and active in management domain Fa0/22 1,5,7,10-12,16,18-21,27,30,40,50,60,80,88,96,100-101,123,160,192,302-303,600,602,700,800,1000-1001 PortVlans in spanning tree forwarding state and not pruned Fa0/22 1,5,7,10-12,16,18-21,27,30,40,50,60,80,88,96,100-101,123,160,192,302-303,600,602,700,800,1000-1001 the vlan 5 is active in management domain but 105 is not, so i try the same workflow as before but change vlan id 5 to 110, ping gets no reply as vlan105 so may be i should add vlan105 to active list ? sorry i'm a green hand to switcher and got confused. 1) what the different between the allowd list and active list 2) if i should add active list manually, so does the cloud admin, if he create a vlan for a tenant, he should add to switcher active list too? is there any way automatically recoginize the vlan tag and allow it pass? maybe add a range to active list, for example, 100-4000? it's ugly.. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [essex vlan]cannot ping vm on other compute node
Perhaps: interface gigbbit 0/22 switchport mode trunk switchport trunk encapsulation dot1q switchport trunk allowed vlan 1-4094 interface gigbbit 0/23 switchport mode trunk switchport trunk encapsulation dot1q switchport trunk allowed vlan 1-4094 On Wed, Feb 27, 2013 at 12:02 AM, Ajiva Fan aji.zq...@gmail.com wrote: since i notice that in switcher: sw-31show interface fastEthernet 0/22 trunk PortMode Encapsulation StatusNative vlan Fa0/22 on 802.1q trunking 1 Port Vlans allowed on trunk Fa0/22 1-4094 PortVlans allowed and active in management domain Fa0/22 1,5,7,10-12,16,18-21,27,30,40,50,60,80,88,96,100-101,123,160,192,302-303,600,602,700,800,1000-1001 PortVlans in spanning tree forwarding state and not pruned Fa0/22 1,5,7,10-12,16,18-21,27,30,40,50,60,80,88,96,100-101,123,160,192,302-303,600,602,700,800,1000-1001 the vlan 5 is active in management domain but 105 is not, so i try the same workflow as before but change vlan id 5 to 110, ping gets no reply as vlan105 so may be i should add vlan105 to active list ? sorry i'm a green hand to switcher and got confused. 1) what the different between the allowd list and active list 2) if i should add active list manually, so does the cloud admin, if he create a vlan for a tenant, he should add to switcher active list too? is there any way automatically recoginize the vlan tag and allow it pass? maybe add a range to active list, for example, 100-4000? it's ugly.. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [essex vlan]cannot ping vm on other compute node
thank you very much. actullaly, i have already try these command yesterday, it does not work. currently, i find that vlan id in active list and not pruned list can be passed by switcher, vlan id not in the two list cannot will be droped even they are in allowed list. but the network administrator (and the internet pages) tells me that if vlan is in allowed list, it can go through trunk mode port. there is some hardware info may not be useful, but i list it here, hope it will help someone else. cisco catalyst 2950 switcher only hava sw-31(config)#interface gigabitEthernet 0/2? . : 0-2 so i just operate on fastEthernet 0/22 sw-31(config)#interface fastEthernet 0/22? . : 0-24 and 2950 defaultly 1)allowed all vlan id on trunk mode 2)only support 802.1q on trunk mode so the following commands: switchport trunk encapsulation dot1q switchport trunk allowed vlan 1-4094 will not work. On 2/27/13, Aaron Rosen aro...@nicira.com wrote: Perhaps: interface gigbbit 0/22 switchport mode trunk switchport trunk encapsulation dot1q switchport trunk allowed vlan 1-4094 interface gigbbit 0/23 switchport mode trunk switchport trunk encapsulation dot1q switchport trunk allowed vlan 1-4094 On Wed, Feb 27, 2013 at 12:02 AM, Ajiva Fan aji.zq...@gmail.com wrote: since i notice that in switcher: sw-31show interface fastEthernet 0/22 trunk PortMode Encapsulation StatusNative vlan Fa0/22 on 802.1q trunking 1 Port Vlans allowed on trunk Fa0/22 1-4094 PortVlans allowed and active in management domain Fa0/22 1,5,7,10-12,16,18-21,27,30,40,50,60,80,88,96,100-101,123,160,192,302-303,600,602,700,800,1000-1001 PortVlans in spanning tree forwarding state and not pruned Fa0/22 1,5,7,10-12,16,18-21,27,30,40,50,60,80,88,96,100-101,123,160,192,302-303,600,602,700,800,1000-1001 the vlan 5 is active in management domain but 105 is not, so i try the same workflow as before but change vlan id 5 to 110, ping gets no reply as vlan105 so may be i should add vlan105 to active list ? sorry i'm a green hand to switcher and got confused. 1) what the different between the allowd list and active list 2) if i should add active list manually, so does the cloud admin, if he create a vlan for a tenant, he should add to switcher active list too? is there any way automatically recoginize the vlan tag and allow it pass? maybe add a range to active list, for example, 100-4000? it's ugly.. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [essex vlan]cannot ping vm on other compute node
I'm not sure I followed the thread correctly from the beginning, but I read that you have configured you NIC for private VM networking, in VLAN mode, on VLAN 105. Is that correct? In general trunking all your switch ports used for VM networking will save you the hassle of adding the VLANs you are using in your setup one by one. Also, there's quite a difference between VLAN access mode and trunk mode. I rarely use Cisco switches, but when I do I always put them in trunk mode explicitly. The list of allowed vlan is a sort of filter that you apply on a trunk port. So perhaps you might want to put all your ports in trunk mode and use the vlan range defined in nova.conf as allowed vlan list. Salvatore On 27 February 2013 10:18, Ajiva Fan aji.zq...@gmail.com wrote: thank you very much. actullaly, i have already try these command yesterday, it does not work. currently, i find that vlan id in active list and not pruned list can be passed by switcher, vlan id not in the two list cannot will be droped even they are in allowed list. but the network administrator (and the internet pages) tells me that if vlan is in allowed list, it can go through trunk mode port. there is some hardware info may not be useful, but i list it here, hope it will help someone else. cisco catalyst 2950 switcher only hava sw-31(config)#interface gigabitEthernet 0/2? . : 0-2 so i just operate on fastEthernet 0/22 sw-31(config)#interface fastEthernet 0/22? . : 0-24 and 2950 defaultly 1)allowed all vlan id on trunk mode 2)only support 802.1q on trunk mode so the following commands: switchport trunk encapsulation dot1q switchport trunk allowed vlan 1-4094 will not work. On 2/27/13, Aaron Rosen aro...@nicira.com wrote: Perhaps: interface gigbbit 0/22 switchport mode trunk switchport trunk encapsulation dot1q switchport trunk allowed vlan 1-4094 interface gigbbit 0/23 switchport mode trunk switchport trunk encapsulation dot1q switchport trunk allowed vlan 1-4094 On Wed, Feb 27, 2013 at 12:02 AM, Ajiva Fan aji.zq...@gmail.com wrote: since i notice that in switcher: sw-31show interface fastEthernet 0/22 trunk PortMode Encapsulation StatusNative vlan Fa0/22 on 802.1q trunking 1 Port Vlans allowed on trunk Fa0/22 1-4094 PortVlans allowed and active in management domain Fa0/22 1,5,7,10-12,16,18-21,27,30,40,50,60,80,88,96,100-101,123,160,192,302-303,600,602,700,800,1000-1001 PortVlans in spanning tree forwarding state and not pruned Fa0/22 1,5,7,10-12,16,18-21,27,30,40,50,60,80,88,96,100-101,123,160,192,302-303,600,602,700,800,1000-1001 the vlan 5 is active in management domain but 105 is not, so i try the same workflow as before but change vlan id 5 to 110, ping gets no reply as vlan105 so may be i should add vlan105 to active list ? sorry i'm a green hand to switcher and got confused. 1) what the different between the allowd list and active list 2) if i should add active list manually, so does the cloud admin, if he create a vlan for a tenant, he should add to switcher active list too? is there any way automatically recoginize the vlan tag and allow it pass? maybe add a range to active list, for example, 100-4000? it's ugly.. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [essex vlan]cannot ping vm on other compute node
thanks you for reply
special thanks to Aaron Rosen
the situation is that:
1) openstack is in vlan mode
2) switcher is in trunk mode, all vlan id is allowed
3) vlan in switcher's allowed list, active list and (not pruned) list
can communicate with each other. vlan only in allowed list but not in
the other two list is isolated
4) i tried the way which is from official site guide to set pruned
list but it does not work, the switcher just ignore the prune command
and hold the original config ( i will ask our network administrator
and find more help from cisco site )
now i think openstack is running fine ( at least from my point of view)
and i think swither trunk port is running basically correct
here is my env:
switcher port {22,23}
sw-31#show interfaces fastEthernet 0/22 trunk
PortMode Encapsulation StatusNative vlan
Fa0/22 on 802.1q trunking 1
Port Vlans allowed on trunk
Fa0/22 1-4094
PortVlans allowed and active in management domain
Fa0/22
1,5,7,10-12,16,18-21,27,30,40,50,60,80,88,96,100-101,123,160,192,302-303,600,602,700,800,1000-1001
PortVlans in spanning tree forwarding state and not pruned
Fa0/22
1,5,7,10-12,16,18-21,27,30,40,50,60,80,88,96,100-101,123,160,192,302-303,600,602,700,800,1000-1001
from openstack control node terminal:
# nova-manage network create --label admin-network-01
--fixed_range_v4=10.0.12.0/24 --vlan=105 --project_id=admin_id
# nova-manage network create --label admin-network-02
--fixed_range_v4=10.0.13.0/24 --vlan=101 --project_id=admin_id
# nova boot --image cirros --flavor 1 --availability_zone nova:control test01
# nova boot --image cirros --flavor 1 --availability_zone nova:compute test02
now test01 and test02 get two vlan ip addr, and control node and
compute node get two bridge
NOTE: *** vlan101 *** is in switcher's active list and spanning tree
forwarding state and not pruned list, but vlan105 is not, vlan105
just in allowed list
control node:
br105 10.0.12.6
br101 10.0.13.6
compute node
br105 10.0.12.4
br101 10.0.13.4
from control node i can ping 10.0.13.4 but cannot ping 10.0.12.4
so the root cause may be the active list and the pruned list of switcher
is there any one meet such problem?
maybe i'm fool or i'm just fooled by some odd issue
please help me
On 2/27/13, Salvatore Orlando sorla...@nicira.com wrote:
I'm not sure I followed the thread correctly from the beginning, but I
read that you have configured you NIC for private VM networking, in
VLAN mode, on VLAN 105.
Is that correct?
In general trunking all your switch ports used for VM networking will
save you the hassle of adding the VLANs you are using in your setup
one by one.
Also, there's quite a difference between VLAN access mode and trunk
mode. I rarely use Cisco switches, but when I do I always put them in
trunk mode explicitly.
The list of allowed vlan is a sort of filter that you apply on a trunk
port. So perhaps you might want to put all your ports in trunk mode
and use the vlan range defined in nova.conf as allowed vlan list.
Salvatore
On 27 February 2013 10:18, Ajiva Fan aji.zq...@gmail.com wrote:
thank you very much.
actullaly, i have already try these command yesterday, it does not work.
currently, i find that vlan id in active list and not pruned list can
be passed by switcher, vlan id not in the two list cannot will be
droped even they are in allowed list.
but the network administrator (and the internet pages) tells me that
if vlan is in allowed list, it can go through trunk mode port.
there is some hardware info may not be useful, but i list it here,
hope it will help someone else.
cisco catalyst 2950 switcher only hava
sw-31(config)#interface gigabitEthernet 0/2?
. : 0-2
so i just operate on fastEthernet 0/22
sw-31(config)#interface fastEthernet 0/22?
. : 0-24
and 2950 defaultly
1)allowed all vlan id on trunk mode
2)only support 802.1q on trunk mode
so the following commands:
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1-4094
will not work.
On 2/27/13, Aaron Rosen aro...@nicira.com wrote:
Perhaps:
interface gigbbit 0/22
switchport mode trunk
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1-4094
interface gigbbit 0/23
switchport mode trunk
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1-4094
On Wed, Feb 27, 2013 at 12:02 AM, Ajiva Fan aji.zq...@gmail.com wrote:
since i notice that in switcher:
sw-31show interface fastEthernet 0/22 trunk
PortMode Encapsulation StatusNative vlan
Fa0/22 on 802.1q trunking 1
Port Vlans allowed on trunk
Fa0/22 1-4094
PortVlans allowed and active in management domain
Fa0/22
1,5,7,10-12,16,18-21,27,30,40,50,60,80,88,96,100-101,123,160,192,302-303,600,602,700,800,1000-1001
PortVlans in spanning tree forwarding state and not pruned
Fa0/22
Re: [Openstack] [essex vlan]cannot ping vm on other compute node
Try these commands:
Conf term
Vlan 105
State active
George
-Original Message-
From: openstack-bounces+george.mihaiescu=q9@lists.launchpad.net
[mailto:openstack-bounces+george.mihaiescu=q9@lists.launchpad.net] On
Behalf Of Ajiva Fan
Sent: Wednesday, February 27, 2013 5:23 AM
To: Salvatore Orlando
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] [essex vlan]cannot ping vm on other compute node
thanks you for reply
special thanks to Aaron Rosen
the situation is that:
1) openstack is in vlan mode
2) switcher is in trunk mode, all vlan id is allowed
3) vlan in switcher's allowed list, active list and (not pruned) list
can communicate with each other. vlan only in allowed list but not in
the other two list is isolated
4) i tried the way which is from official site guide to set pruned
list but it does not work, the switcher just ignore the prune command
and hold the original config ( i will ask our network administrator
and find more help from cisco site )
now i think openstack is running fine ( at least from my point of view)
and i think swither trunk port is running basically correct
here is my env:
switcher port {22,23}
sw-31#show interfaces fastEthernet 0/22 trunk
PortMode Encapsulation StatusNative vlan
Fa0/22 on 802.1q trunking 1
Port Vlans allowed on trunk
Fa0/22 1-4094
PortVlans allowed and active in management domain
Fa0/22
1,5,7,10-12,16,18-21,27,30,40,50,60,80,88,96,100-101,123,160,192,302-303,600,602,700,800,1000-1001
PortVlans in spanning tree forwarding state and not pruned
Fa0/22
1,5,7,10-12,16,18-21,27,30,40,50,60,80,88,96,100-101,123,160,192,302-303,600,602,700,800,1000-1001
from openstack control node terminal:
# nova-manage network create --label admin-network-01
--fixed_range_v4=10.0.12.0/24 --vlan=105 --project_id=admin_id
# nova-manage network create --label admin-network-02
--fixed_range_v4=10.0.13.0/24 --vlan=101 --project_id=admin_id
# nova boot --image cirros --flavor 1 --availability_zone nova:control test01
# nova boot --image cirros --flavor 1 --availability_zone nova:compute test02
now test01 and test02 get two vlan ip addr, and control node and
compute node get two bridge
NOTE: *** vlan101 *** is in switcher's active list and spanning tree
forwarding state and not pruned list, but vlan105 is not, vlan105
just in allowed list
control node:
br105 10.0.12.6
br101 10.0.13.6
compute node
br105 10.0.12.4
br101 10.0.13.4
from control node i can ping 10.0.13.4 but cannot ping 10.0.12.4
so the root cause may be the active list and the pruned list of switcher
is there any one meet such problem?
maybe i'm fool or i'm just fooled by some odd issue
please help me
On 2/27/13, Salvatore Orlando sorla...@nicira.com wrote:
I'm not sure I followed the thread correctly from the beginning, but I
read that you have configured you NIC for private VM networking, in
VLAN mode, on VLAN 105.
Is that correct?
In general trunking all your switch ports used for VM networking will
save you the hassle of adding the VLANs you are using in your setup
one by one.
Also, there's quite a difference between VLAN access mode and trunk
mode. I rarely use Cisco switches, but when I do I always put them in
trunk mode explicitly.
The list of allowed vlan is a sort of filter that you apply on a trunk
port. So perhaps you might want to put all your ports in trunk mode
and use the vlan range defined in nova.conf as allowed vlan list.
Salvatore
On 27 February 2013 10:18, Ajiva Fan aji.zq...@gmail.com wrote:
thank you very much.
actullaly, i have already try these command yesterday, it does not work.
currently, i find that vlan id in active list and not pruned list can
be passed by switcher, vlan id not in the two list cannot will be
droped even they are in allowed list.
but the network administrator (and the internet pages) tells me that
if vlan is in allowed list, it can go through trunk mode port.
there is some hardware info may not be useful, but i list it here,
hope it will help someone else.
cisco catalyst 2950 switcher only hava
sw-31(config)#interface gigabitEthernet 0/2?
. : 0-2
so i just operate on fastEthernet 0/22
sw-31(config)#interface fastEthernet 0/22?
. : 0-24
and 2950 defaultly
1)allowed all vlan id on trunk mode
2)only support 802.1q on trunk mode
so the following commands:
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1-4094
will not work.
On 2/27/13, Aaron Rosen aro...@nicira.com wrote:
Perhaps:
interface gigbbit 0/22
switchport mode trunk
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1-4094
interface gigbbit 0/23
switchport mode trunk
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1-4094
On Wed, Feb 27, 2013 at 12:02 AM, Ajiva Fan aji.zq...@gmail.com wrote:
since i notice that in switcher:
sw-31show interface fastEthernet 0/22
Re: [Openstack] [essex vlan]cannot ping vm on other compute node
thank you, Kevin S, and also thanks George i did this command in the beginning of the time when i meet this problem, and it failed because sw-31(config)#vlan 105 VTP VLAN configuration not allowed when device is in CLIENT mode. meanwhile i'm guided to a wrong way by our network administrator, since i'm very new to switcher config. yes, by add a vlan id to switch, the problem is solved. and switcher must be putted to vtp server mode. the client mode just copy vlan config from a server, so any configure about vlan is ignored. ps: i followed this qa on cisco site: https://learningnetwork.cisco.com/thread/15990 thank you very much for your help ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [essex vlan]cannot ping vm on other compute node
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. 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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [essex vlan]cannot ping vm on other compute node
On Tue, Feb 26, 2013 at 11:02 PM, Aaron Rosen aro...@nicira.com wrote: inline On Tue, Feb 26, 2013 at 10:51 PM, Ajiva Fan aji.zq...@gmail.com 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. ** In order to rule the switch 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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [essex vlan]cannot ping vm on other compute node
inline On Tue, Feb 26, 2013 at 10:51 PM, Ajiva Fan aji.zq...@gmail.com 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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [essex vlan]cannot ping vm on other compute node
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. 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.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
