I just fixed the problem partially; the ping can arrive at br-tun/br-int on Network Node from a vm on Compute Node now.
The qrouter, however, still cannot respond to the ping. I tried to do tcpdump on the corresponding Ethernet port in the qrouter, and nothing was captured. Best regards Byeong-Gi KIM 2014-06-16 13:08 GMT+09:00 BYEONG-GI KIM <[email protected]>: > Dear Yang, > > Thank you for the reply. > > I've checked the connection between aqrouter and a vm like this way; > > 1. ping from qrouter to br-ext in order to identify the external network > is set correctly: it works fine. > 2. ping from a vm where locates in an internal network to a qrouter which > connects with the network: it doesn't work. In detail, I used tcpdump on > each bridge to check the connection status. The ping (ICMP Request message) > arrived at br-int/br-tun on the Compute Node successfully. The ping, > however, could not arrive at br-int/br-tun on the Network Node. The Request > messsage could arrive at the Ethernet port for Internal Network on the > Network Node. I also checked the connection by a reverse way; The ping from > qrouter even could not be delivered to br-int on the Network Node. Of > course I set up the firewall rule properly... > > My Networking set up is GRE and I deployed my openstack testbed > environment using VMware workstation. I've been trying to deploy two > external networks using multiple l3 agents, and the multiple l3 agents are > running on same node (Network Node). The status of the router_interface for > connection between Internal Network and the corresponding qrouter is shown > as DOWN on dashboard. > > I don't know how to solve this problem. I tried to re-create external > network/subnet/qrouter according to the > http://www.gossamer-threads.com/lists/openstack/dev/36353?do=post_view_flat, > but still doesn't work. > > Should the router_id in l3-agent.ini file indicate id which can find 'ip > netns' on Network Node or indicate id which can find 'neutron router-list' > on Controller Node? As you know, the ids are a little different; > qrouter-xxxx or just xxxx > > Anyway, the setting up multiple external networks makes me upset now. :( > > Best regards > > Byeong-Gi Kim > > > > > 2014-06-16 11:11 GMT+09:00 Alex Yang <[email protected]>: > > Hi Kim, >> >> You should check the firewall rule of the vm at first. Then, If the >> qrouter and vm are not in the same host, you should check the connection of >> tunnel between the two host by using ovs-vsctl show. >> Using tcpdump to inspect the packets in br-ext, br-int is also useful. >> >> >> >> 2014-06-13 14:51 GMT+08:00 BYEONG-GI KIM <[email protected]>: >> >>> Hello. >>> >>> I created two external networks using multiple l3 agents by referring to >>> both >>> http://docs.openstack.org/admin-guide-cloud/content/adv_cfg_l3_agent_multi_extnet.html >>> and https://answers.launchpad.net/neutron/+question/236230, and it >>> seems work fine... >>> >>> When I tried to ping from a qrouter, which connects with both an >>> external network called "external1" and an internal network, to a vm where >>> located in the internal network, however, the ping could not be sent >>> successfully. >>> >>> The qrouter can ping to br-ex, and another qrouter which connects with >>> the second external network named "external2" also can ping to br-ex-2. The >>> problem is that status for connection between each qrouter and internal >>> network has been "DOWN" instead of "ACTIVE"... >>> >>> Did anybody suffer from such problem and solve it? I'd appreciate any >>> help and comments for solving it. >>> >>> Thanks in advance. >>> >>> Best regards >>> >>> Byeong-Gi KIM >>> >>> >>> _______________________________________________ >>> Mailing list: >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>> Post to : [email protected] >>> Unsubscribe : >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>> >>> >> >> >> -- >> 杨雨 >> Email: [email protected] >> GitHub: https://github.com/AlexYangYu >> Weibo: http://www.weibo.com/alexyangyu >> > >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
