Thank you for your reply. I could find the answer while tracking existence of ifcfg files!
The cause was execution order of inserting ovs kernel module starting and ovs-db/daemon. I inserted ovs-module after starting ovs-db/daemon. There were some warning and error messages for this at starting ovs-db, but i missed it. After switching the order, ovs properly can load pre-existed bridge and also create a new bridge with the interface. But, Why do you asked me to check /etc/sysconfig/network-scripts/ifcfg-br0 & ifcfg-br1? There are no ifcfg-br# files after load ovs-bridges. Should There be that files after doing kind of 'ovs-vsctl add-br br#'? 2013/5/30 neeraj <nee...@nectechnologies.in> > Just check that you have scripts there for the bridges at > /etc/sysconfig/network-scripts/ifcfg-br0 & ifcfg-br1**** > > ** ** > > *From:* discuss-boun...@openvswitch.org [mailto: > discuss-boun...@openvswitch.org] *On Behalf Of *JinHwan Hwang > *Sent:* Thursday, May 30, 2013 6:11 AM > *To:* discuss@openvswitch.org > *Subject:* [ovs-discuss] can't bring up bridge interfaces created by the > the ovs after rebooting the server**** > > ** ** > > (English is not my first language. Sorry for my poor English )**** > > ** ** > > OS : **** > > Linux nc233 2.6.32-220.17.1.el6.x86_64 #1 SMP Tue May 15 17:16:46 CDT 2012 > x86_64 x86_64 x86_64 GNU/Linux**** > > CentOS release 6.3 (Final)**** > > open vswitch : 1.11.90**** > > ** ** > > I installed the ovs by using source install. At that time it worked > properly. But after rebooting the server, i can't bring up bridge interface > created by the ovs anymore. **** > > ** ** > > There are some mistakes i'm worrying about. When I rebooted the server, I > didn't expected that the ovs setting would disappeared if i don't force it > to exist consistently. Therefore, i didn't configured something about that. > After the reboot, I found that the bridge module and ifconfig setting are > rolled back as if i didn't configured about the ovs. **** > > ** ** > > So, I do rmmod bridge and insmod the ovs modules again. And then started > the ovs db. There were similar with installing from scratch except building > it(literally i copied and pasted command from INSTALL file included in the > distribution). After that, i could find what i configured before. **** > > ** ** > > # ovs-vsctl show**** > > 76d9d6aa-cfce-4868-bf99-7d16bcfe38eb**** > > Bridge "br0"**** > > Port "br0"**** > > Interface "br0"**** > > type: internal**** > > Port "eth1"**** > > Interface "eth1"**** > > ** ** > > # ifconfig **** > > eth0 Link encap:Ethernet HWaddr 5C:F3:FC:29:C7:12**** > > inet addr:172.16.222.233 Bcast:172.16.222.255 > Mask:255.255.255.0**** > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1**** > > RX packets:1415586 errors:0 dropped:0 overruns:0 frame:0**** > > TX packets:4897 errors:0 dropped:0 overruns:0 carrier:0**** > > collisions:0 txqueuelen:1000**** > > RX bytes:120257509 (114.6 MiB) TX bytes:1025583 (1001.5 KiB)*** > * > > Interrupt:17 Memory:91a80000-91aa0000**** > > ** ** > > eth1 Link encap:Ethernet HWaddr 5C:F3:FC:29:C7:13**** > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1**** > > RX packets:1286611 errors:0 dropped:0 overruns:0 frame:0**** > > TX packets:27647 errors:0 dropped:0 overruns:0 carrier:0**** > > collisions:0 txqueuelen:1000**** > > RX bytes:114004322 (108.7 MiB) TX bytes:3728677 (3.5 MiB)**** > > Interrupt:19 Memory:91980000-919a0000**** > > ** ** > > lo Link encap:Local Loopback**** > > inet addr:127.0.0.1 Mask:255.0.0.0**** > > UP LOOPBACK RUNNING MTU:16436 Metric:1**** > > RX packets:1538 errors:0 dropped:0 overruns:0 frame:0**** > > TX packets:1538 errors:0 dropped:0 overruns:0 carrier:0**** > > collisions:0 txqueuelen:0**** > > RX bytes:93110 (90.9 KiB) TX bytes:93110 (90.9 KiB)**** > > ** ** > > usb0 Link encap:Ethernet HWaddr 5E:F3:FC:29:C7:15**** > > 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)**** > > ** ** > > ** ** > > There were no problems until that time, So i tried to bring up the bridge > br0 configured in ovs-vsctl. But it turns out that there are no bridge > named br0.**** > > ** ** > > # ifconfig br0 up**** > > br0: unknown interface: No such device**** > > ** ** > > Furthermore, I can't create new bridge interface by using ovs-vsctl. **** > > I created br2 after configuring newly. But it also returned me same error > as did to br2. **** > > ** ** > > # ovs-vsctl show**** > > 76d9d6aa-cfce-4868-bf99-7d16bcfe38eb**** > > Bridge "br0"**** > > Port "br0"**** > > Interface "br0"**** > > type: internal**** > > Port "eth1"**** > > Interface "eth1"**** > > Bridge "br2"**** > > Port "br2"**** > > Interface "br2"**** > > type: internal**** > > ** ** > > # ifconfig br2 up**** > > br2: unknown interface: No such device**** > > ** ** > > What is wrong with what i did? Is doing nothing before rebooting the ovs a > real critical issue? or there are maybe something wrong with reconfiguring > the ovs? **** > > ** ** > > Thank you for reading.**** > > DISCLAIMER: > ----------------------------------------------------------------------------------------------------------------------- > The contents of this e-mail and any attachment(s) are confidential and > intended > for the named recipient(s) only. > It shall not attach any liability on the originator or NEC or its > affiliates. Any views or opinions presented in > this email are solely those of the author and may not necessarily reflect the > opinions of NEC or its affiliates. > Any form of reproduction, dissemination, copying, disclosure, modification, > distribution and / or publication of > this message without the prior written consent of the author of this e-mail is > strictly prohibited. If you have > received this email in error please delete it and notify the sender > immediately. . > ----------------------------------------------------------------------------------------------------------------------- > >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
