openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #19805
Re: network problem
Either your switch is dropping the packets or they are getting blocked by security group rules. You will have to do some tcpdump on various interfaces to figure out where the packets are getting dropped.
Vish
On Jan 3, 2013, at 11:07 AM, Umar Draz <unix.co@xxxxxxxxx> wrote:
> Hi Vish
>
> Here is updated output.
>
> root@compute1:~# ifconfig
>
> br100 Link encap:Ethernet HWaddr 00:50:56:b2:01:5f
> inet addr:10.10.10.3 Bcast:10.10.10.255 Mask:255.255.255.0
> inet6 addr: fe80::30b0:a8ff:fefe:5a32/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2891 errors:0 dropped:20 overruns:0 frame:0
> TX packets:523 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:158946 (158.9 KB) TX bytes:53844 (53.8 KB)
>
> eth0 Link encap:Ethernet HWaddr 00:50:56:b2:01:5c
> inet addr:63.55.xx.39 Bcast:64.22.82.127 Mask:255.255.255.128
> inet6 addr: fe80::250:56ff:feb2:15c/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:12697 errors:0 dropped:20 overruns:0 frame:0
> TX packets:10651 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:4687350 (4.6 MB) TX bytes:3680637 (3.6 MB)
>
> eth1 Link encap:Ethernet HWaddr 00:50:56:b2:01:5f
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2772 errors:0 dropped:0 overruns:0 frame:0
> TX packets:214 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:181158 (181.1 KB) TX bytes:14768 (14.7 KB)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:88 errors:0 dropped:0 overruns:0 frame:0
> TX packets:88 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:9296 (9.2 KB) TX bytes:9296 (9.2 KB)
>
> vnet0 Link encap:Ethernet HWaddr fe:16:3e:67:b1:59
> inet6 addr: fe80::fc16:3eff:fe67:b159/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:354 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2746 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:500
> RX bytes:38188 (38.1 KB) TX bytes:191306 (191.3 KB)
>
>
> ------------------------------------------------------------------------------------------------
>
> root@compute2:~# ifconfig
>
> br100 Link encap:Ethernet HWaddr 00:50:56:b2:01:60
> inet addr:10.10.10.5 Bcast:10.10.10.255 Mask:255.255.255.0
> inet6 addr: fe80::dc64:3dff:fe5b:f2b0/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:664 errors:0 dropped:0 overruns:0 frame:0
> TX packets:261 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:38164 (38.1 KB) TX bytes:24979 (24.9 KB)
>
> eth0 Link encap:Ethernet HWaddr 00:50:56:b2:01:5a
> inet addr:63.55.xx.40 Bcast:64.22.82.127 Mask:255.255.255.128
> inet6 addr: fe80::250:56ff:feb2:15a/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:3383 errors:0 dropped:1 overruns:0 frame:0
> TX packets:2795 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:1319723 (1.3 MB) TX bytes:1029018 (1.0 MB)
>
> eth1 Link encap:Ethernet HWaddr 00:50:56:b2:01:60
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:617 errors:0 dropped:0 overruns:0 frame:0
> TX packets:116 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:39694 (39.6 KB) TX bytes:7620 (7.6 KB)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:74 errors:0 dropped:0 overruns:0 frame:0
> TX packets:74 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:7798 (7.7 KB) TX bytes:7798 (7.7 KB)
>
> vnet0 Link encap:Ethernet HWaddr fe:16:3e:03:e6:fa
> inet6 addr: fe80::fc16:3eff:fe03:e6fa/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:155 errors:0 dropped:0 overruns:0 frame:0
> TX packets:698 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:500
> RX bytes:15718 (15.7 KB) TX bytes:51677 (51.6 KB)
>
> ---------------------------------------------------------------------------------------------------------------
>
> Now I have 2 virtual machines as follows
>
> 1) 10.10.10.2 on compute1
> 1) 10.10.10.4 on compute2
>
> I can not ping 10.10.10.4 from compute1 node, and same I can not ping 10.10.10.2 from compute 2 node.
>
> But I can ping 10.10.10.3 and 10.10.10.5 from each compute nodes. Above is the output of ifconfig of both nodes.
>
> Best Regards,
>
> Umar
>
>
> On Thu, Jan 3, 2013 at 11:57 PM, Vishvananda Ishaya <vishvananda@xxxxxxxxx> wrote:
> You won't be able to ping the nodes from the controller since it has no ip address on the guest network.
>
> It looks like eth1 is bridged in properly on the compute node you showed, although I don't see it showing up in the interface list. It looks like maybe eth1 is not up? Try:
>
> ifconfig eth1 up
>
> you should be able to ping from 10.10.10.3 - 10.10.10.4 if your eth1s are up and plugged in and your switch isn't filtering traffic.
>
> Vish
>
>
> On Jan 3, 2013, at 10:25 AM, Umar Draz <unix.co@xxxxxxxxx> wrote:
>
>> Hi Vish
>>
>> Here is the ifconfig output of compute node
>>
>> br100 Link encap:Ethernet HWaddr 00:50:56:b2:01:5f
>> inet addr:10.10.10.3 Bcast:10.10.10.255 Mask:255.255.255.0
>> inet6 addr: fe80::c895:59ff:fe29:f708/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:16 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:0
>> RX bytes:1646 (1.6 KB) TX bytes:4194 (4.1 KB)
>> vnet0 Link encap:Ethernet HWaddr fe:16:3e:00:91:2c
>> inet6 addr: fe80::fc16:3eff:fe00:912c/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:16 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:81 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:500
>> RX bytes:1870 (1.8 KB) TX bytes:5820 (5.8 KB)
>> And here is the output of brctl show
>>
>> bridge name bridge id STP enabled interfaces
>> br100 8000.005056b2015f no eth1
>> vnet0
>> the virtual machine ip address is = 10.10.10.5
>>
>> 1) I can ping this ip from compute node but from controller node I can't ping this.
>> 2) But on controller node there is not any br100, brctl show nothing here is the ouput of ifconfig of controller node
>>
>> eth0 Link encap:Ethernet HWaddr 00:50:56:b2:01:58
>> inet addr:63.55.xx.38 Bcast:64.22.82.127 Mask:255.255.255.128
>> inet6 addr: fe80::250:56ff:feb2:158/64 Scope:Link
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:3136 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:2636 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:941305 (941.3 KB) TX bytes:1173739 (1.1 MB)
>>
>> eth1 Link encap:Ethernet HWaddr 00:50:56:b2:01:5e
>> BROADCAST MULTICAST MTU:1500 Metric:1
>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>>
>> Best Regards,
>>
>> Umar
>>
>> On Thu, Jan 3, 2013 at 10:57 PM, Vishvananda Ishaya <vishvananda@xxxxxxxxx> wrote:
>> Based on the below it could be :
>>
>> a) eth1 is not plugged in
>>
>> or
>>
>> b) eth1 is plugged into a switch that is filtering traffic in the 10.10.10.0/24 range
>>
>> or
>>
>> c) br100 is not bridged into eth1
>>
>> (this would appear in brctl show which you didn't send)
>>
>>
>> Vish
>>
>> On Jan 3, 2013, at 9:23 AM, Umar Draz <unix.co@xxxxxxxxx> wrote:
>>
>>> Hi Vish
>>>
>>> Here is .....
>>>
>>>
>>> Controller (nova.conf)
>>> network_manager=nova.network.manager.FlatDHCPManager
>>> force_dhcp_release=True
>>> dhcpbridge_flagfile=/etc/nova/nova.conf
>>> firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
>>> my_ip=63.55.xx.x2
>>> public_interface=eth0
>>> vlan_interface=eth1
>>> flat_network_bridge=br100
>>> flat_interface=eth1
>>> fixed_range=10.10.10.0/24
>>> auto eth0
>>> iface eth0 inet static
>>> address 63.55.xx.x2
>>> netmask 255.255.255.128
>>> gateway 63.55.xx.x1
>>>
>>> auto eth1
>>> iface eth1 inet static
>>> ---------------------------------------------------------------------------------------------
>>>
>>>
>>> Compute (nova.conf)
>>> network_manager=nova.network.manager.FlatDHCPManager
>>> force_dhcp_release=True
>>> dhcpbridge_flagfile=/etc/nova/nova.conf
>>> firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
>>> my_ip=63.55.xx.x3
>>> public_interface=eth0
>>> vlan_interface=eth1
>>> flat_network_bridge=br100
>>> flat_interface=eth1
>>> fixed_range=10.10.10.0/24
>>> auto eth0
>>> iface eth0 inet static
>>> address 63.55.xx.x3
>>> netmask 255.255.255.128
>>> gateway 63.55.xx.x1
>>>
>>> auto eth1
>>> iface eth1 inet static
>>>
>>> -------------------------------------------------------------------------------------------------
>>> Here is the command of network
>>> nova-manage network create --label=myNetwork --fixed_range_v4=10.10.10.0/24 --bridge=br100 --num_networks=1 --multi_host=T
>>>
>>> Best Regards,
>>>
>>> Umar
>>>
>>> On Thu, Jan 3, 2013 at 10:13 PM, Vishvananda Ishaya <vishvananda@xxxxxxxxx> wrote:
>>> Need a little more info:
>>>
>>> a) what does your nova.config look like? Specifically what is the setting for flat_interface?
>>>
>>> b) what command did you use to create your network?
>>>
>>> c) what is the output of brctl show?
>>>
>>> d) what is the output of ip addr show?
>>>
>>> Vish
>>>
>>> On Jan 2, 2013, at 11:11 PM, Umar Draz <unix.co@xxxxxxxxx> wrote:
>>>
>>>> Hi
>>>>
>>>> here is my setup
>>>>
>>>> 1) controller -> 63.73.22.22
>>>> 2) compute-1 - > 63.73.22.23
>>>> 3) compute-2 -> 63.73.22.24
>>>>
>>>> The Local network is 10.10.10.0/24 for virtual machines.
>>>>
>>>> I have created 2 virtual machines. Controller automatically creates 1 Virtual machine on compute-1 and 2nd on compute-2.
>>>>
>>>> 1) Compute-1's Virtual Machine local ip is 10.10.10.3
>>>> 2) Compute-2's Virtual Machine local ip is 10.10.10.4
>>>>
>>>> Now the problem is I can not ping 10.10.10.3 from Compute-2's virtual machine. and Same thing on Compute-1's virtual machine. Even I can not ping or access both virtual machines from controller node.
>>>>
>>>> Compute-1 can only access its own virtual machine and Compute-2 can only access its own virtual machines.
>>>>
>>>> Would you please help me what should I do?
>>>>
>>>> Best Regards,
>>>>
>>>> Umar
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to : openstack@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help : https://help.launchpad.net/ListHelp
>>>
>>>
>>>
>>>
>>> --
>>> Umar Draz
>>> Network Architect
>>
>>
>>
>>
>> --
>> Umar Draz
>> Network Architect
>
>
>
>
> --
> Umar Draz
> Network Architect
References
