Thanks Romain. That's a typo, with type "gre" it will be still failed.
And the log complains "File exists"
[root@xenserver-frank1 ~]# ovs create interface name=test
options:"remote_ip=192.168.152.22 key=2" type=gre
e0f8369c-bd5c-41b9-8e22-8d6b58e11429
[root@xenserver-frank1 ~]# ovs create port name=test
interfaces=[e0f8369c-bd5c-41b9-8e22-8d6b58e11429]
13abaf54-155c-4954-951f-4e7da1f48b8e
[root@xenserver-frank1 ~]# ovs add bridge xapi7 ports
13abaf54-155c-4954-951f-4e7da1f48b8e
The log says:
Jan 18 10:57:23|11332|bridge|INFO|created port test on bridge xapi7
Jan 18 10:57:23|11333|bridge|WARN|could not create iface test: File exists
Jan 18 10:57:23|11334|bridge|WARN|bridge xapi7: port test has no
interfaces, dropping
On 01/16/2011 04:25 PM, Romain Lenglet wrote:
Hi Frank,
You don't create the GRE ports correctly.
The options and type are incorrect. See below.
On Fri, Jan 14, 2011 at 7:22 AM, Frank <[email protected]
<mailto:[email protected]>> wrote:
On 01/04/2011 02:34 PM, Jesse Gross wrote:
On Thu, Dec 30, 2010 at 6:00 PM, Frank<[email protected]
<mailto:[email protected]>> wrote:
Hi guys:
I just try to create two GRE tunnels between two hosts,
the result is I
can't do this.
vswitch complains "could not create iface test: File
exists" when
creating second tunnel.
I did set different GRE keys for tunnels.
I google and get some articles said it's possible to
create multiple GRE
tunnels with same src/dst.
I am curious what technical barrier prevents our doing
since GRE key is
an natural tag to distinguish different tunnels.
You can have multiple tunnels between the same endpoints if
they are
distinguished by key. Please post your interface config.
I am sorry for late reply. I create tunnels as below (ovs is alias
of ovs-vsctl):
[root@xenserver-frank4 ~]# ovs list interface 1-2
_uuid : ebc0d114-d258-4670-9965-8a5a0491b0b9
external_ids : {}
ingress_policing_burst: 0
ingress_policing_rate: 0
mac : []
name : "1-2"
ofport : 8
options : {remote_ip="192.168.152.22 key=1"}
Those options should read {remote_ip="192.168.152.22", key="1"}.
statistics : {collisions=0, rx_bytes=894703,
rx_crc_err=0, rx_dropped=0, rx_errors=0, rx_frame_err=0,
rx_over_err=0, rx_packets=12083, tx_bytes=28882506, tx_dropped=0,
tx_errors=0, tx_packets=21760}
status : {}
type : gre
[root@xenserver-frank4 ~]# ovs create interface name=test
options:"remote_ip=192.168.152.22 key=2"
So I suggest trying something like:
ovs create interface name=test 'options:remote_ip="192.168.152.22",
key="2"'
to create the interface with correct options.
74c1e2e3-da43-4ae4-86e7-048de205f974
[root@xenserver-frank4 ~]# ovs create port name=test
interfaces=[74c1e2e3-da43-4ae4-86e7-048de205f974]
3dc08a5c-102c-45c6-9891-9692d2d4a8e3
[root@xenserver-frank4 ~]# ovs add bridge xapi7 ports
3dc08a5c-102c-45c6-9891-9692d2d4a8e3
[root@xenserver-frank4 ~]# ovs list interface test
_uuid : 74c1e2e3-da43-4ae4-86e7-048de205f974
external_ids : {}
ingress_policing_burst: 0
ingress_policing_rate: 0
mac : []
name : test
ofport : []
options : {remote_ip="192.168.152.22 key=2"}
statistics : {}
status : {}
type : ""
This type is wrong. It should be "gre" for a GRE port.
You have to pass the correct type when creating the interface above.
Actually I already had a tunnel to "192.168.152.22" with key = 1.
we can see the secondary creation was failed even I set the key=2.
In ovs-vswitchd.log, here are:
Jan 13 14:18:31|02259|netdev|WARN|failed to get flags for network
device test: No such device
Jan 13 14:18:31|02260|bridge|WARN|could not create iface test: No
such device
Jan 13 14:18:31|02261|bridge|WARN|bridge xapi7: port test has no
interfaces, dropping
_______________________________________________
discuss mailing list
[email protected] <mailto:[email protected]>
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
