1 a.m.
Good night,
I'm trying oVirt 3.5 + neutron appliance in BareMetal servers, but I am
facing some problems.
structure:
2 servers with:
oVirt 3.5.1
hundreds 7
4 network adapter
int = 0 + int2 bond0 => public network => ovirtmgmt
int = 1 + int3 bond1 => private network => neutron
Virtual Appliance Neutron:
http://www.ovirt.org/Features/NeutronVirtualAppliance
NOTE: All steps were followed, and checked several times.
Openvswitch configuration:
*[root@ovirt01 network-scripts]# ovs-vsctl show*
62feffa7-3f3a-48f7-9299-0830ebcd8fd8
Bridge br-neutron
Port phy-br-neutron
Interface phy-br-neutron
Port br-neutron
Interface br-neutron
type: internal
Port neutron
Interface neutron
Bridge br-int
fail_mode: secure
Port int-br-neutron
Interface int-br-neutron
Port "qvof206e358-8f"
tag: 1
Interface "qvof206e358-8f"
Port br-int
Interface br-int
type: internal
ovs_version: "2.1.3"
*[root@ovirt02 /]# ovs-vsctl show*
9d40dda2-62ea-4538-9f82-d5babff0837b
Bridge br-int
fail_mode: secure
Port "qvo723ce1c1-56"
tag: 1
Interface "qvo723ce1c1-56"
Port int-br-neutron
Interface int-br-neutron
Port br-int
Interface br-int
type: internal
Bridge br-neutron
Port br-neutron
Interface br-neutron
type: internal
Port neutron
Interface neutron
Port phy-br-neutron
Interface phy-br-neutron
ovs_version: "2.1.3"
*[root@ovirt01 /]# ovs-dpctl show*
system@ovs-system:
lookups: hit:1946392 missed:6566 lost:1
flows: 4
masks: hit:2490944 total:2 hit/pkt:1.28
port 0: ovs-system (internal)
port 1: br-neutron (internal)
port 2: br-int (internal)
port 3: neutron
port 4: int-br-neutron
port 5: phy-br-neutron
port 7: qvof206e358-8f
*[root@ovirt02 /]# ovs-dpctl show*
system@ovs-system:
lookups: hit:2041047 missed:6445 lost:0
flows: 4
masks: hit:2234366 total:2 hit/pkt:1.09
port 0: ovs-system (internal)
port 1: br-neutron (internal)
port 2: br-int (internal)
port 3: int-br-neutron
port 4: phy-br-neutron
port 5: neutron
port 6: qvo723ce1c1-56
*Testing:*
Connectivity between my virtual machines only work when both are running on
the same node, when virtual machines are running on different hosts can not
make a machine ping the other.
*Tcpdump:*
*[root@ovirt01 network-scripts]# tcpdump -e -i neutron -p -n not port nfs*
tcpdump: WARNING: neutron: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on neutron, link-type EN10MB (Ethernet), capture size 65535 bytes
16:57:25.469628 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.4
tell 192.168.100.2, length 28
16:57:26.469565 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.4
tell 192.168.100.2, length 28
16:57:28.469910 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.4
tell 192.168.100.2, length 28
16:57:29.469479 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.4
tell 192.168.100.2, length 28
16:57:30.469472 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.4
tell 192.168.100.2, length 28
16:57:32.469715 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.4
tell 192.168.100.2, length 28
16:57:33.469374 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.4
tell 192.168.100.2, length 28
16:57:34.469367 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.4
tell 192.168.100.2, length 28
16:57:36.469617 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.4
tell 192.168.100.2, length 28
16:57:37.469251 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.4
tell 192.168.100.2, length 28
16:57:38.469258 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.4
tell 192.168.100.2, length 28
*[root@ovirt02 /]# tcpdump -e -i neutron -p -n not port nfs*
tcpdump: WARNING: neutron: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on neutron, link-type EN10MB (Ethernet), capture size 65535 bytes
16:57:23.188238 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.2
tell 192.168.100.4, length 28
16:57:24.187726 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.2
tell 192.168.100.4, length 28
16:57:25.187781 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.2
tell 192.168.100.4, length 28
16:57:27.189224 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.2
tell 192.168.100.4, length 28
16:57:28.188720 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.2
tell 192.168.100.4, length 28
16:57:29.188715 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.2
tell 192.168.100.4, length 28
16:57:31.190152 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.2
tell 192.168.100.4, length 28
16:57:32.189646 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.2
tell 192.168.100.4, length 28
16:57:33.189622 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.2
tell 192.168.100.4, length 28
16:57:35.190959 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.2
tell 192.168.100.4, length 28
16:57:36.190585 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.2
tell 192.168.100.4, length 28
16:57:37.190544 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.2
tell 192.168.100.4, length 28
16:57:39.191885 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.2
tell 192.168.100.4, length 28
16:57:40.191492 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.2
tell 192.168.100.4, length 28
16:57:41.191511 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q (0x8100),
length 46: vlan 1024, p 0, ethertype ARP, Request who-has 192.168.100.2
tell 192.168.100.4, length 28
10:41 a.m.
Hi Eduardo,
May I ask for more details on what you're testing exactly? You're
running "oVirt" VMs? And do these VMs use "external" networks (i.e.
networks that were configured on the Neutron server)?
On 17/02/15 01:00, Eduardo Terzella wrote:
Good night,
I'm trying oVirt 3.5 + neutron appliance in BareMetal servers, but I am
facing some problems.
structure:
2 servers with:
oVirt 3.5.1
hundreds 7
4 network adapter
int = 0 + int2 bond0 => public network => ovirtmgmt
int = 1 + int3 bond1 => private network => neutron
What do you mean by "private"? It does have an IP address that's
accessible from the other host, right?
Virtual Appliance Neutron:
http://www.ovirt.org/Features/NeutronVirtualAppliance
NOTE: All steps were followed, and checked several times.
Openvswitch configuration:
*[root@ovirt01 network-scripts]# ovs-vsctl show*
62feffa7-3f3a-48f7-9299-0830ebcd8fd8
Bridge br-neutron
Port phy-br-neutron
Interface phy-br-neutron
Port br-neutron
Interface br-neutron
type: internal
Port neutron
Interface neutron
Bridge br-int
fail_mode: secure
Port int-br-neutron
Interface int-br-neutron
Port "qvof206e358-8f"
tag: 1
Interface "qvof206e358-8f"
Port br-int
Interface br-int
type: internal
ovs_version: "2.1.3"
*[root@ovirt02 /]# ovs-vsctl show*
9d40dda2-62ea-4538-9f82-d5babff0837b
Bridge br-int
fail_mode: secure
Port "qvo723ce1c1-56"
tag: 1
Interface "qvo723ce1c1-56"
Port int-br-neutron
Interface int-br-neutron
Port br-int
Interface br-int
type: internal
Bridge br-neutron
Port br-neutron
Interface br-neutron
type: internal
Port neutron
Interface neutron
Port phy-br-neutron
Interface phy-br-neutron
ovs_version: "2.1.3"
*[root@ovirt01 /]# ovs-dpctl show*
system@ovs-system:
lookups: hit:1946392 missed:6566 lost:1
flows: 4
masks: hit:2490944 total:2 hit/pkt:1.28
port 0: ovs-system (internal)
port 1: br-neutron (internal)
port 2: br-int (internal)
port 3: neutron
port 4: int-br-neutron
port 5: phy-br-neutron
port 7: qvof206e358-8f
*[root@ovirt02 /]# ovs-dpctl show*
system@ovs-system:
lookups: hit:2041047 missed:6445 lost:0
flows: 4
masks: hit:2234366 total:2 hit/pkt:1.09
port 0: ovs-system (internal)
port 1: br-neutron (internal)
port 2: br-int (internal)
port 3: int-br-neutron
port 4: phy-br-neutron
port 5: neutron
port 6: qvo723ce1c1-56
*Testing:
*
Connectivity between my virtual machines only work when both are running
on the same node, when virtual machines are running on different hosts
can not make a machine ping the other.
*Tcpdump:*
*[root@ovirt01 network-scripts]# tcpdump -e -i neutron -p -n not port nfs*
tcpdump: WARNING: neutron: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on neutron, link-type EN10MB (Ethernet), capture size 65535 bytes
16:57:25.469628 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.4 tell 192.168.100.2, length 28
16:57:26.469565 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.4 tell 192.168.100.2, length 28
16:57:28.469910 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.4 tell 192.168.100.2, length 28
16:57:29.469479 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.4 tell 192.168.100.2, length 28
16:57:30.469472 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.4 tell 192.168.100.2, length 28
16:57:32.469715 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.4 tell 192.168.100.2, length 28
16:57:33.469374 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.4 tell 192.168.100.2, length 28
16:57:34.469367 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.4 tell 192.168.100.2, length 28
16:57:36.469617 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.4 tell 192.168.100.2, length 28
16:57:37.469251 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.4 tell 192.168.100.2, length 28
16:57:38.469258 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.4 tell 192.168.100.2, length 28
*[root@ovirt02 /]# tcpdump -e -i neutron -p -n not port nfs*
tcpdump: WARNING: neutron: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on neutron, link-type EN10MB (Ethernet), capture size 65535 bytes
16:57:23.188238 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.2 tell 192.168.100.4, length 28
16:57:24.187726 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.2 tell 192.168.100.4, length 28
16:57:25.187781 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.2 tell 192.168.100.4, length 28
16:57:27.189224 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.2 tell 192.168.100.4, length 28
16:57:28.188720 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.2 tell 192.168.100.4, length 28
16:57:29.188715 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.2 tell 192.168.100.4, length 28
16:57:31.190152 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.2 tell 192.168.100.4, length 28
16:57:32.189646 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.2 tell 192.168.100.4, length 28
16:57:33.189622 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.2 tell 192.168.100.4, length 28
16:57:35.190959 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.2 tell 192.168.100.4, length 28
16:57:36.190585 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.2 tell 192.168.100.4, length 28
16:57:37.190544 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.2 tell 192.168.100.4, length 28
16:57:39.191885 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.2 tell 192.168.100.4, length 28
16:57:40.191492 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.2 tell 192.168.100.4, length 28
16:57:41.191511 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
(0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
192.168.100.2 tell 192.168.100.4, length 28
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
9:01 p.m.
Hello, Lior.
Thx for replay.
You're running "oVirt" VMs?
Yes my vm running on oVirt.
VM2 with ip: 192.168.100.7 running on ovirt2 (neutron external network
extnet)
VM1 with ip: 192.168.100.6 running on ovirt1 (neutron external network
extnet)
And do these VMs use "external" networks (i.e.
networks that were configured on the Neutron server)?
(neutron) net-list
+--------------------------------------+--------+-------------------------------------------------------+
| id | name |
subnets |
+--------------------------------------+--------+-------------------------------------------------------+
| 7e4cfe2f-84b1-4cca-8e95-07f32a735632 | extnet |
80da5fad-01f5-44f9-b5c3-7f457de25187 192.168.100.0/24 |
+--------------------------------------+--------+-------------------------------------------------------+
(neutron)
(neutron) net-show extnet
+---------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| admin_state_up | True |
| id | 7e4cfe2f-84b1-4cca-8e95-07f32a735632 |
| name | extnet |
| provider:network_type | vlan |
| provider:physical_network | vmnet |
| provider:segmentation_id | 1024 |
| router:external | False |
| shared | False |
| status | ACTIVE |
| subnets | 80da5fad-01f5-44f9-b5c3-7f457de25187 |
| tenant_id | cc807159dae14d43b93c19c6df0cd5f4 |
(neutron) port-list
+--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+
| id | name | mac_address |
fixed_ips
|
+--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+
| 2112f36f-1735-425f-bfa5-771648c911c0 | nic1 | 00:1a:4a:2c:3f:02 |
{"subnet_id": "80da5fad-01f5-44f9-b5c3-7f457de25187",
"ip_address":
"192.168.100.7"} |
| 618cf63f-9b69-4597-8519-06b7beb3f854 | | fa:16:3e:8e:3b:c3 |
{"subnet_id": "80da5fad-01f5-44f9-b5c3-7f457de25187",
"ip_address":
"192.168.100.3"} |
| ad67fa8f-88a3-4845-b5b9-4182ef02991f | | fa:16:3e:ce:57:18 |
{"subnet_id": "80da5fad-01f5-44f9-b5c3-7f457de25187",
"ip_address":
"192.168.100.5"} |
| b74411e8-16be-4e3a-9132-b2d0e3620a77 | nic1 | 00:1a:4a:2c:3f:03 |
{"subnet_id": "80da5fad-01f5-44f9-b5c3-7f457de25187",
"ip_address":
"192.168.100.6"} |
+--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+
Thx for help !!!
2015-02-18 6:41 GMT-02:00 Lior Vernia <lvernia(a)redhat.com>:
Hi Eduardo,
May I ask for more details on what you're testing exactly? You're
running "oVirt" VMs? And do these VMs use "external" networks (i.e.
networks that were configured on the Neutron server)?
On 17/02/15 01:00, Eduardo Terzella wrote:
> Good night,
>
> I'm trying oVirt 3.5 + neutron appliance in BareMetal servers, but I am
> facing some problems.
>
> structure:
>
> 2 servers with:
>
> oVirt 3.5.1
> hundreds 7
> 4 network adapter
> int = 0 + int2 bond0 => public network => ovirtmgmt
> int = 1 + int3 bond1 => private network => neutron
>
What do you mean by "private"? It does have an IP address that's
accessible from the other host, right?
> Virtual Appliance Neutron:
> http://www.ovirt.org/Features/NeutronVirtualAppliance
> NOTE: All steps were followed, and checked several times.
>
> Openvswitch configuration:
>
> *[root@ovirt01 network-scripts]# ovs-vsctl show*
> 62feffa7-3f3a-48f7-9299-0830ebcd8fd8
> Bridge br-neutron
> Port phy-br-neutron
> Interface phy-br-neutron
> Port br-neutron
> Interface br-neutron
> type: internal
> Port neutron
> Interface neutron
> Bridge br-int
> fail_mode: secure
> Port int-br-neutron
> Interface int-br-neutron
> Port "qvof206e358-8f"
> tag: 1
> Interface "qvof206e358-8f"
> Port br-int
> Interface br-int
> type: internal
> ovs_version: "2.1.3"
>
> *[root@ovirt02 /]# ovs-vsctl show*
> 9d40dda2-62ea-4538-9f82-d5babff0837b
> Bridge br-int
> fail_mode: secure
> Port "qvo723ce1c1-56"
> tag: 1
> Interface "qvo723ce1c1-56"
> Port int-br-neutron
> Interface int-br-neutron
> Port br-int
> Interface br-int
> type: internal
> Bridge br-neutron
> Port br-neutron
> Interface br-neutron
> type: internal
> Port neutron
> Interface neutron
> Port phy-br-neutron
> Interface phy-br-neutron
> ovs_version: "2.1.3"
>
> *[root@ovirt01 /]# ovs-dpctl show*
> system@ovs-system:
> lookups: hit:1946392 missed:6566 lost:1
> flows: 4
> masks: hit:2490944 total:2 hit/pkt:1.28
> port 0: ovs-system (internal)
> port 1: br-neutron (internal)
> port 2: br-int (internal)
> port 3: neutron
> port 4: int-br-neutron
> port 5: phy-br-neutron
> port 7: qvof206e358-8f
>
> *[root@ovirt02 /]# ovs-dpctl show*
> system@ovs-system:
> lookups: hit:2041047 missed:6445 lost:0
> flows: 4
> masks: hit:2234366 total:2 hit/pkt:1.09
> port 0: ovs-system (internal)
> port 1: br-neutron (internal)
> port 2: br-int (internal)
> port 3: int-br-neutron
> port 4: phy-br-neutron
> port 5: neutron
> port 6: qvo723ce1c1-56
>
> *Testing:
>
> *
> Connectivity between my virtual machines only work when both are running
> on the same node, when virtual machines are running on different hosts
> can not make a machine ping the other.
>
> *Tcpdump:*
>
> *[root@ovirt01 network-scripts]# tcpdump -e -i neutron -p -n not port
nfs*
> tcpdump: WARNING: neutron: no IPv4 address assigned
> tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode
> listening on neutron, link-type EN10MB (Ethernet), capture size 65535
bytes
> 16:57:25.469628 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:26.469565 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:28.469910 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:29.469479 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:30.469472 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:32.469715 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:33.469374 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:34.469367 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:36.469617 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:37.469251 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:38.469258 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
>
>
>
> *[root@ovirt02 /]# tcpdump -e -i neutron -p -n not port nfs*
> tcpdump: WARNING: neutron: no IPv4 address assigned
> tcpdump: verbose output suppressed, use -v or -vv for full protocol
decode
> listening on neutron, link-type EN10MB (Ethernet), capture size 65535
bytes
> 16:57:23.188238 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:24.187726 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:25.187781 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:27.189224 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:28.188720 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:29.188715 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:31.190152 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:32.189646 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:33.189622 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:35.190959 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:36.190585 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:37.190544 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:39.191885 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:40.191492 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:41.191511 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
>
>
>
>
>
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
8:50 a.m.
Thanks Eduardo. So it seems from your tcpdump that the Neutron bridge is
correctly sending ARP requests. What happens then on bond1 and in your
switch?
On 18/02/15 21:01, Eduardo Terzella wrote:
Hello, Lior.
Thx for replay.
You're running "oVirt" VMs?
Yes my vm running on oVirt.
VM2 with ip: 192.168.100.7 running on ovirt2 (neutron external network
extnet)
VM1 with ip: 192.168.100.6 running on ovirt1 (neutron external network
extnet)
And do these VMs use "external" networks (i.e.
networks that were configured on the Neutron server)?
(neutron) net-list
+--------------------------------------+--------+-------------------------------------------------------+
| id | name |
subnets |
+--------------------------------------+--------+-------------------------------------------------------+
| 7e4cfe2f-84b1-4cca-8e95-07f32a735632 | extnet |
80da5fad-01f5-44f9-b5c3-7f457de25187 192.168.100.0/24
<http://192.168.100.0/24> |
+--------------------------------------+--------+-------------------------------------------------------+
(neutron)
(neutron) net-show extnet
+---------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| admin_state_up | True |
| id | 7e4cfe2f-84b1-4cca-8e95-07f32a735632 |
| name | extnet |
| provider:network_type | vlan |
| provider:physical_network | vmnet |
| provider:segmentation_id | 1024 |
| router:external | False |
| shared | False |
| status | ACTIVE |
| subnets | 80da5fad-01f5-44f9-b5c3-7f457de25187 |
| tenant_id | cc807159dae14d43b93c19c6df0cd5f4 |
(neutron) port-list
+--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+
| id | name | mac_address |
fixed_ips
|
+--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+
| 2112f36f-1735-425f-bfa5-771648c911c0 | nic1 | 00:1a:4a:2c:3f:02 |
{"subnet_id": "80da5fad-01f5-44f9-b5c3-7f457de25187",
"ip_address":
"192.168.100.7"} |
| 618cf63f-9b69-4597-8519-06b7beb3f854 | | fa:16:3e:8e:3b:c3 |
{"subnet_id": "80da5fad-01f5-44f9-b5c3-7f457de25187",
"ip_address":
"192.168.100.3"} |
| ad67fa8f-88a3-4845-b5b9-4182ef02991f | | fa:16:3e:ce:57:18 |
{"subnet_id": "80da5fad-01f5-44f9-b5c3-7f457de25187",
"ip_address":
"192.168.100.5"} |
| b74411e8-16be-4e3a-9132-b2d0e3620a77 | nic1 | 00:1a:4a:2c:3f:03 |
{"subnet_id": "80da5fad-01f5-44f9-b5c3-7f457de25187",
"ip_address":
"192.168.100.6"} |
+--------------------------------------+------+-------------------+--------------------------------------------------------------------------------------+
Thx for help !!!
2015-02-18 6:41 GMT-02:00 Lior Vernia <lvernia(a)redhat.com
<mailto:lvernia@redhat.com>>:
Hi Eduardo,
May I ask for more details on what you're testing exactly? You're
running "oVirt" VMs? And do these VMs use "external" networks
(i.e.
networks that were configured on the Neutron server)?
On 17/02/15 01:00, Eduardo Terzella wrote:
> Good night,
>
> I'm trying oVirt 3.5 + neutron appliance in BareMetal servers, but I am
> facing some problems.
>
> structure:
>
> 2 servers with:
>
> oVirt 3.5.1
> hundreds 7
> 4 network adapter
> int = 0 + int2 bond0 => public network => ovirtmgmt
> int = 1 + int3 bond1 => private network => neutron
>
What do you mean by "private"? It does have an IP address that's
accessible from the other host, right?
> Virtual Appliance Neutron:
> http://www.ovirt.org/Features/NeutronVirtualAppliance
> NOTE: All steps were followed, and checked several times.
>
> Openvswitch configuration:
>
> *[root@ovirt01 network-scripts]# ovs-vsctl show*
> 62feffa7-3f3a-48f7-9299-0830ebcd8fd8
> Bridge br-neutron
> Port phy-br-neutron
> Interface phy-br-neutron
> Port br-neutron
> Interface br-neutron
> type: internal
> Port neutron
> Interface neutron
> Bridge br-int
> fail_mode: secure
> Port int-br-neutron
> Interface int-br-neutron
> Port "qvof206e358-8f"
> tag: 1
> Interface "qvof206e358-8f"
> Port br-int
> Interface br-int
> type: internal
> ovs_version: "2.1.3"
>
> *[root@ovirt02 /]# ovs-vsctl show*
> 9d40dda2-62ea-4538-9f82-d5babff0837b
> Bridge br-int
> fail_mode: secure
> Port "qvo723ce1c1-56"
> tag: 1
> Interface "qvo723ce1c1-56"
> Port int-br-neutron
> Interface int-br-neutron
> Port br-int
> Interface br-int
> type: internal
> Bridge br-neutron
> Port br-neutron
> Interface br-neutron
> type: internal
> Port neutron
> Interface neutron
> Port phy-br-neutron
> Interface phy-br-neutron
> ovs_version: "2.1.3"
>
> *[root@ovirt01 /]# ovs-dpctl show*
> system@ovs-system:
> lookups: hit:1946392 missed:6566 lost:1
> flows: 4
> masks: hit:2490944 total:2 hit/pkt:1.28
> port 0: ovs-system (internal)
> port 1: br-neutron (internal)
> port 2: br-int (internal)
> port 3: neutron
> port 4: int-br-neutron
> port 5: phy-br-neutron
> port 7: qvof206e358-8f
>
> *[root@ovirt02 /]# ovs-dpctl show*
> system@ovs-system:
> lookups: hit:2041047 missed:6445 lost:0
> flows: 4
> masks: hit:2234366 total:2 hit/pkt:1.09
> port 0: ovs-system (internal)
> port 1: br-neutron (internal)
> port 2: br-int (internal)
> port 3: int-br-neutron
> port 4: phy-br-neutron
> port 5: neutron
> port 6: qvo723ce1c1-56
>
> *Testing:
>
> *
> Connectivity between my virtual machines only work when both are running
> on the same node, when virtual machines are running on different hosts
> can not make a machine ping the other.
>
> *Tcpdump:*
>
> *[root@ovirt01 network-scripts]# tcpdump -e -i neutron -p -n not
port nfs*
> tcpdump: WARNING: neutron: no IPv4 address assigned
> tcpdump: verbose output suppressed, use -v or -vv for full
protocol decode
> listening on neutron, link-type EN10MB (Ethernet), capture size
65535 bytes
> 16:57:25.469628 00 <tel:25.469628%2000>:1a:4a:2c:3f:02 >
Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:26.469565 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:28.469910 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:29.469479 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:30.469472 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:32.469715 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:33.469374 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:34.469367 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:36.469617 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:37.469251 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
> 16:57:38.469258 00:1a:4a:2c:3f:02 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.4 tell 192.168.100.2, length 28
>
>
>
> *[root@ovirt02 /]# tcpdump -e -i neutron -p -n not port nfs*
> tcpdump: WARNING: neutron: no IPv4 address assigned
> tcpdump: verbose output suppressed, use -v or -vv for full
protocol decode
> listening on neutron, link-type EN10MB (Ethernet), capture size
65535 bytes
> 16:57:23.188238 00 <tel:23.188238%2000>:1a:4a:2c:3f:03 >
Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:24.187726 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:25.187781 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:27.189224 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:28.188720 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:29.188715 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:31.190152 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:32.189646 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:33.189622 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:35.190959 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:36.190585 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:37.190544 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:39.191885 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:40.191492 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
> 16:57:41.191511 00:1a:4a:2c:3f:03 > Broadcast, ethertype 802.1Q
> (0x8100), length 46: vlan 1024, p 0, ethertype ARP, Request who-has
> 192.168.100.2 tell 192.168.100.4, length 28
>
>
>
>
>
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org <mailto:Users@ovirt.org>
> http://lists.ovirt.org/mailman/listinfo/users
>
3399
days inactive
3405
days old
3 comments
2 participants
participants (2)
-
Eduardo Terzella -
Lior Vernia