log is as follows :
[root@hc_2c519_1_1_7 /]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:27:19:97:59:81
inet6 addr: fe80::227:19ff:fe97:5981/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:188 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:50102 (48.9 KiB) TX bytes:2520 (2.4 KiB)
Interrupt:17 Base address:0xe000
[root@hc_2c519_1_1_7 scripts]# ./network-bridge start netdev=eth0
Nothing to flush.
Waiting for peth0 to negotiate link.
can't add peth0 to bridge eth0: Invalid argument
[root@hc_2c519_1_1_7 scripts]# ifconfig
peth0 Link encap:Ethernet HWaddr 00:27:19:97:59:81
inet6 addr: fe80::227:19ff:fe97:5981/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:190 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:50635 (49.4 KiB) TX bytes:2988 (2.9 KiB)
Interrupt:17 Base address:0xe000
[root@hc_2c519_1_1_7 scripts]# brctl show
bridge name bridge id STP enabled interfaces
eth0 0000.92260d642648 no
[root@hc_2c519_1_1_7 scripts]# ovs-vsctl list-br
tmpbridge
[root@hc_2c519_1_1_7 scripts]# ovs-vsctl list port
_uuid : 43a78955-2e5d-4f8c-adbc-c87154e722d9
bond_downdelay : 0
bond_fake_iface : false
bond_mode : []
bond_updelay : 0
external_ids : {}
fake_bridge : false
interfaces : [5a7bcca7-841f-460e-8c93-f73d825781ae]
lacp : []
mac : []
name : tmpbridge
other_config : {}
qos : []
statistics : {}
status : {}
tag : []
trunks : []
vlan_mode : []
Jesse Gross <je...@nicira.com>
2012-03-09 10:17
收件人
lv.erc...@zte.com.cn
抄送
discuss@openvswitch.org
主题
Re: bridge renaming issue with Xen
2012/3/8 <lv.erc...@zte.com.cn>:
>
> Hi，all：
>
> I have a question about xen using ovs to ask for your advice.
>
> When Xen networking start , I want to rename the physical network
adapter
> 'eth0' to 'peth0', and create a bridge 'eth0
> ', add the port 'peth0' to bridge 'eth0'. With the linux bridge , the
xen
> script 'network-bridge' work well, but when using the ovs bridge to
create
> bridge , the xen script 'network-bridge' doesn't work.
>
> with the way discussed before in the mail list, I changed the
network-bridge
> script like this：
>> ip link set ${tdev} name ${bridge}
>> # usually tdev=tmpbridge, bridge=eth0
>> /usr/local/bin/ovs-vsctl set Interface ${tdev} name=${bridge}
>> /usr/local/bin/ovs-vsctl set Port ${tdev} name=${bridge}
>> /usr/local/bin/ovs-vsctl set Bridge ${tdev} name=${bridge}
>
> after executed the network-bridge, using the 'brctl show' command ,the
> result is as:
> [root@vnet_tecs scripts]# brctl show
> bridge name bridge id STP enabled interfaces
> eth0 0000.1e3ce1d5604e no
>
> the port 'peth0' was not added to the bridge 'eth0'.
What does the log say?
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is
solely property of the sender's organization. This mail communication is
confidential. Recipients named above are obligated to maintain secrecy and are
not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. If
you have received this email in error please notify the originator of the
message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
