Britt, It seems working. Thanks britt.
I need some more help in this. Still I couldn't ping or ssh to openstack instances from controller node. I read we need to create an external network and add it to router as gateway. Like => http://docs.openstack.org/icehouse/install-guide/install/apt/content/neutron_initial-external-network.html I am using this command to create subnet for external network neutron subnet-create ext-net --name ext-subnet \ --allocation-pool start=203.0.113.101,end=203.0.113.200 \ --disable-dhcp --gateway 203.0.113.1 203.0.113.0/24 But my current network is bit complex 1) My machine local machine Ip => 172.17.4.64 (Its in our internal network of our company with gateway 172.17.4.254) 2) I installed kvm on my local machine and controller node with IP => 192.168.122.54 with gateway 192.168.122.1 3) Openstack instance network is in 192.168.1.101 to 192.168.1.125 with gateway 192.168.1.1 Can you please tell me which IP addresses I have to give while creating above subnet for my external network. On Mon, Nov 24, 2014 at 10:05 PM, Britt Houser (bhouser) <bhou...@cisco.com> wrote: > If you created the br-ex bridge after restarting networking, that might > be the source of your error. Might try restarting networking or rebooting > the VM. You can tell its working if you see br-ex with and IP address in > the output of ifconfig, and if you can ping that address. > > Thx, > britt > > From: Geo Varghese <gvargh...@aqorn.com> > Date: Monday, November 24, 2014 at 8:32 AM > > To: Britt Houser <bhou...@cisco.com> > Cc: "openstack@lists.openstack.org" <openstack@lists.openstack.org>, " > openstack-operat...@lists.openstack.org" < > openstack-operat...@lists.openstack.org> > Subject: Re: [Openstack-operators] While adding external bridge > connection lost to the network node > > Britt, > > Its okay. Thanks a lot your time. > > I just added br-ex successfully. How can we verify its working. Please > check below ovs-vsctl show > > ============= > root@controller:/home/geo# ovs-vsctl show > b97bd565-6196-40f2-8f3e-c8f21c04c98f > Bridge br-ex > Port "eth0" > Interface "eth0" > Port br-ex > Interface br-ex > type: internal > Bridge br-tun > Port br-tun > Interface br-tun > type: internal > Port "gre-c0a87bb3" > Interface "gre-c0a87bb3" > type: gre > options: {in_key=flow, local_ip="192.168.123.54", > out_key=flow, remote_ip="192.168.123.179"} > Port "gre-c0a87a36" > Interface "gre-c0a87a36" > type: gre > options: {in_key=flow, local_ip="192.168.123.54", > out_key=flow, remote_ip="192.168.122.54"} > Port "gre-7f000001" > Interface "gre-7f000001" > type: gre > options: {in_key=flow, local_ip="192.168.123.54", > out_key=flow, remote_ip="127.0.0.1"} > Port patch-int > Interface patch-int > type: patch > options: {peer=patch-tun} > Bridge br-int > fail_mode: secure > Port "qvof64e7b35-cb" > tag: 1 > Interface "qvof64e7b35-cb" > Port "tapbb0d455b-79" > tag: 1 > Interface "tapbb0d455b-79" > type: internal > Port patch-tun > Interface patch-tun > type: patch > options: {peer=patch-int} > Port "qvo887bf763-8d" > tag: 1 > Interface "qvo887bf763-8d" > Port br-int > Interface br-int > type: internal > Port "int-br-eth1" > Interface "int-br-eth1" > Port "tapa72fb9d6-4a" > tag: 2 > Interface "tapa72fb9d6-4a" > type: internal > ovs_version: "2.0.2 > > ============= > > > On Mon, Nov 24, 2014 at 6:22 PM, Britt Houser (bhouser) <bhou...@cisco.com > > wrote: > >> Geo, >> >> Sorry for not getting back sooner. Was out sick. Can you post the >> output of 'ovs-vsctl show'? I didn’t see a br-ex interface in your >> ifconfig output. >> >> Thx, >> britt >> >> >> From: Geo Varghese <gvargh...@aqorn.com> >> Date: Friday, November 21, 2014 at 1:39 PM >> >> To: Britt Houser <bhou...@cisco.com> >> Cc: "openstack@lists.openstack.org" <openstack@lists.openstack.org>, " >> openstack-operat...@lists.openstack.org" < >> openstack-operat...@lists.openstack.org> >> Subject: Re: [Openstack-operators] While adding external bridge >> connection lost to the network node >> >> Britt, >> >> Just tried it but network restart failed if I add these lines. Also IP >> not assigned to bridge when controller restarted. >> >> When try to do following command after this change >> >> ifdown eth0 >> >> Show error in following line in /etc/network/interfaces >> >> iface br-ex inet static >> >> Thanks again for your support. >> >> On Fri, Nov 21, 2014 at 6:05 PM, Britt Houser (bhouser) < >> bhou...@cisco.com> wrote: >> >>> The br-ex config looks right, but you don't want eth0 to DHCP for an >>> address anymore. Once its attached to br-ex, its an L2-only interface >>> (similar to switchport on cisco switch). I think you want something like >>> this for eth0: >>> >>> auto eth0 >>> iface eth0 inet manual >>> pre-up ifconfig $IFACE up >>> post-down ifconfig $IFACE down >>> >>> >>> Thx, >>> britt >>> >>> From: Geo Varghese <gvargh...@aqorn.com> >>> Date: Friday, November 21, 2014 at 7:22 AM >>> To: Britt Houser <bhou...@cisco.com> >>> Cc: "openstack@lists.openstack.org" <openstack@lists.openstack.org>, >>> "openstack-operat...@lists.openstack.org" >>> <openstack-operat...@lists.openstack.org> >>> Subject: Re: [Openstack-operators] While adding external bridge >>> connection lost to the network node >>> >>> >>> Thanks Britt. >>> >>> >>> You mean like this right? >>> >>> cat /etc/network/interfaces >>> ========================= >>> # The loopback network interface >>> auto lo >>> iface lo inet loopback >>> >>> # The primary network interface >>> auto eth0 >>> iface eth0 inet dhcp >>> >>> # The external network interface >>> auto br-ex >>> iface br-ex inet static >>> address 192.168.122.54 >>> netmask 255.255.255.0 >>> gateway 192.168.122.1 >>> dns-nameservers 8.8.8.8 8.8.4.4 >>> ========================================================== >>> >>> >>> >>> On Fri, Nov 21, 2014 at 5:48 PM, Britt Houser (bhouser) >>> <bhou...@cisco.com> wrote: >>> >>> Correct. You need to updated your /etc/interfaces file so that the >>> 192.168.122.54/24 <http://192.168.122.54/24> address gets assigned to >>> br-ex instead of eth0. >>> >>> From: Geo Varghese <gvargh...@aqorn.com> >>> Date: Friday, November 21, 2014 at 7:16 AM >>> To: Britt Houser <bhou...@cisco.com> >>> Cc: "openstack@lists.openstack.org" <openstack@lists.openstack.org>, >>> "openstack-operat...@lists.openstack.org" >>> <openstack-operat...@lists.openstack.org> >>> Subject: Re: [Openstack-operators] While adding external bridge >>> connection >>> lost to the network node >>> >>> >>> Hi Britt, >>> >>> Thanks for the answer. >>> >>> I am using Virtual machine(KVM) for openstack installation. Its a single >>> node installation. >>> >>> >>> Now i can create instance from openstack dahboard and and can login in to >>> the instance from dashboard konsole. >>> >>> But i couln't connect to instance from controller node. >>> >>> Also i couldn't have connection between instances. >>> >>> Ifconfig output from openstack installation node >>> ======================= >>> root@ubuntu:/home/geo# ifconfig >>> br-int Link encap:Ethernet HWaddr 26:73:95:7a:c5:4e >>> inet6 addr: fe80::ec9d:9aff:fe2f:66ab/64 Scope:Link >>> UP BROADCAST RUNNING MTU:1500 Metric:1 >>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:0 >>> RX bytes:0 (0.0 B) TX bytes:648 (648.0 B) >>> >>> br-tun Link encap:Ethernet HWaddr 0e:af:b2:8e:89:44 >>> inet6 addr: fe80::c89f:cfff:fe74:712/64 Scope:Link >>> UP BROADCAST RUNNING MTU:1500 Metric:1 >>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:0 >>> RX bytes:0 (0.0 B) TX bytes:648 (648.0 B) >>> >>> eth0 Link encap:Ethernet HWaddr 52:54:00:d6:4c:4f >>> inet addr:192.168.122.54 Bcast:192.168.122.255 >>> Mask:255.255.255.0 >>> inet6 addr: fe80::5054:ff:fed6:4c4f/64 Scope:Link >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>> RX packets:162 errors:0 dropped:3 overruns:0 frame:0 >>> TX packets:100 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:1000 >>> RX bytes:16187 (16.1 KB) TX bytes:13445 (13.4 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:65536 Metric:1 >>> RX packets:737 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:737 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:0 >>> RX bytes:104803 (104.8 KB) TX bytes:104803 (104.8 KB) >>> >>> tap561bdedf-3e Link encap:Ethernet HWaddr 42:c5:72:1c:3b:99 >>> inet6 addr: fe80::40c5:72ff:fe1c:3b99/64 Scope:Link >>> UP BROADCAST RUNNING MTU:1500 Metric:1 >>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:0 >>> RX bytes:0 (0.0 B) TX bytes:648 (648.0 B) >>> >>> tapde436ec7-3b Link encap:Ethernet HWaddr b6:09:88:dc:f7:5a >>> inet6 addr: fe80::b409:88ff:fedc:f75a/64 Scope:Link >>> UP BROADCAST RUNNING MTU:1500 Metric:1 >>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:0 >>> RX bytes:0 (0.0 B) TX bytes:648 (648.0 B) >>> ====================================== >>> >>> >>> Same eth0 i have used to add br-ex, you mean thats the issue right? >>> >>> >>> On Fri, Nov 21, 2014 at 5:31 PM, Britt Houser (bhouser) >>> <bhou...@cisco.com> wrote: >>> >>> Was the interface you added to br-ex the same interface to which you >>> connected to the box? If so, this is expected. When you add an >>> interface >>> to the bridge you lose IP connectivity to that interface. The IP address >>> which which was assigned to the interface >>> now needs to be assigned to the br-ex bridge, and then you'll have >>> connectivity once again. >>> >>> Thx, >>> britt >>> >>> From: Geo Varghese <gvargh...@aqorn.com> >>> Date: Friday, November 21, 2014 at 1:39 AM >>> To: "openstack@lists.openstack.org" <openstack@lists.openstack.org>, >>> "openstack-operat...@lists.openstack.org" >>> <openstack-operat...@lists.openstack.org> >>> Subject: [Openstack-operators] While adding external bridge connection >>> lost to the network node >>> >>> >>> Hi Team, >>> >>> While adding external bridge connection lost to the network node from >>> other nodes. we couldn't ssh to network node after creating bridge. >>> >>> If we do below steps of following link >>> >>> >>> http://docs.openstack.org/icehouse/install-guide/install/apt/content/neutro >>> n-ml2-network-node.html >>> <http://docs.openstack.org/icehouse/install-guide/install/apt/content/neutron-ml2-network-node.html> >>> >>> =========================================== >>> 3) Add the external bridge: >>> >>> # ovs-vsctl add-br br-ex >>> >>> 4) Add a port to the external bridge that connects to the physical >>> external network interface: >>> >>> Replace INTERFACE_NAME with the actual interface name. For example, eth2 >>> or ens256. >>> >>> # ovs-vsctl add-port br-ex INTERFACE_NAME >>> ============================================= >>> >>> External connection to network node fails. Then we couldn't connect to >>> network node from other machines. >>> >>> Any one faced this issue? >>> >>> Please help us to fix this issue. >>> >>> >>> >>> >>> -- >>> Regards, >>> Geo Varghese >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> -- >>> Regards, >>> Geo Varghese >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> -- >>> Regards, >>> Geo Varghese >>> >>> >> >> >> -- >> -- >> Regards, >> Geo Varghese >> > > > > -- > -- > Regards, > Geo Varghese > -- -- Regards, Geo Varghese
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
