<div dir="ltr"><div>A little more information, or a completely different problem...I just realized my network node can't ping its public gateway. (Instead of <a href="http://7.7.7.0/24">7.7.7.0/24</a>, I am using <a href="http://10.42.36.0/23">10.42.36.0/23</a>. My gateway is .1 (and has non-redundant IP of .10), and my Network Node IP is .130). This did work at one time.<br>
<br><span style="font-family:courier new,monospace">root@os-network:~# ping 10.42.36.1<br>PING 10.42.36.1 (10.42.36.1) 56(84) bytes of data.<br>From 10.42.36.130 icmp_seq=1 Destination Host Unreachable<br>From 10.42.36.130 icmp_seq=2 Destination Host Unreachable<br>
>From 10.42.36.130 icmp_seq=3 Destination Host Unreachable<br>^C<br>--- 10.42.36.1 ping statistics ---<br>5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4023ms<br>pipe 3<br>root@os-network:~# arp -an<br>
? (10.42.36.1) at <incomplete> on qg-28108125-11<br>? (10.10.10.2) at 00:50:56:81:25:73 [ether] on eth1<br>? (10.42.38.11) at 40:55:39:25:a5:c1 [ether] on eth3<br>? (192.168.0.1) at 00:50:56:81:48:02 [ether] on eth0<br>
? (10.5.5.4) at fa:16:3e:95:94:9c [ether] on tap45ffdc5f-da<br>? (10.42.36.10) at <incomplete> on qg-28108125-11<br>? (10.5.5.3) at fa:16:3e:8d:6d:13 [ether] on tap45ffdc5f-da<br>? (10.42.38.1) at 00:07:b4:01:b5:01 [ether] on eth3<br>
root@os-network:~#</span><br><br></div>Nor does it work the other way:<br><br><br>From my gateway:<br><br><span style="font-family:courier new,monospace">sniktc-nx10A-7010-KXDC-E12# sho run int vlan402<br><br>!Command: show running-config interface Vlan402<br>
!Time: Fri Mar 8 14:11:45 2013<br><br>version 5.1(3)<br><br>interface Vlan402<br> vrf member Enterprise<br> no ip redirects<br> ip address <a href="http://10.42.4.10/22">10.42.4.10/22</a><br> ip router eigrp 1<br> ip pim sparse-mode<br>
glbp 402<br> ip 10.42.4.1<br> priority 200<br> authentication text KXDCglbp402<br> no shutdown<br> mtu 9216<br><br>sniktc-nx10A-7010-KXDC-E12# ping 10.42.36.130 vrf Enterprise source 10.42.36.10<br>PING 10.42.36.130 (10.42.36.130) from <a href="http://10.42.36.10">10.42.36.10</a>: 56 data bytes<br>
Request 0 timed out<br>Request 1 timed out<br>Request 2 timed out<br>Request 3 timed out<br>Request 4 timed out<br><br>--- 10.42.36.130 ping statistics ---<br>5 packets transmitted, 0 packets received, 100.00% packet loss<br>
sniktc-nx10A-7010-KXDC-E12# </span><br><br><br><br><span style="font-family:courier new,monospace">root@os-network:~# ifconfig qg-28108125-11<br>qg-28108125-11 Link encap:Ethernet HWaddr fa:16:3e:a9:a3:4c <br> inet addr:10.42.36.130 Bcast:10.42.37.255 Mask:255.255.254.0<br>
inet6 addr: fe80::f816:3eff:fea9:a34c/64 Scope:Link<br> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br> RX packets:34 errors:0 dropped:0 overruns:0 frame:0<br> TX packets:354 errors:0 dropped:0 overruns:0 carrier:0<br>
collisions:0 txqueuelen:0 <br> RX bytes:4840 (4.8 KB) TX bytes:22619 (22.6 KB)<br><br>root@os-network:~# ovs-vsctl show<br>e232f8c8-1cb8-4cf5-9de5-49f41e59fd38<br> Bridge br-tun<br> Port patch-int<br>
Interface patch-int<br> type: patch<br> options: {peer=patch-tun}<br> Port br-tun<br> Interface br-tun<br> type: internal<br> Port "gre-2"<br>
Interface "gre-2"<br> type: gre<br> options: {in_key=flow, out_key=flow, remote_ip="10.10.10.2"}<br> Bridge br-ex<br> Port "qg-28108125-11"<br>
Interface "qg-28108125-11"<br> type: internal<br> Port br-ex<br> Interface br-ex<br> type: internal<br> Port "eth2"<br> Interface "eth2"<br>
Bridge br-int<br> Port patch-tun<br> Interface patch-tun<br> type: patch<br> options: {peer=patch-int}<br> Port br-int<br> Interface br-int<br> type: internal<br>
Port "tap45ffdc5f-da"<br> tag: 1<br> Interface "tap45ffdc5f-da"<br> type: internal<br> Port "qr-9f9041ce-65"<br> tag: 1<br> Interface "qr-9f9041ce-65"<br>
type: internal<br> ovs_version: "1.4.0+build0"<br>root@os-network:~# </span><br><div class="gmail_extra"><br></div><div class="gmail_extra">I suppose something has gone wrong inside quantum on the network node? Is there a good way to blow everything away and rebuild? I tried the following, but the quantum-networking script doesn't really work this way, as it assumes it is creating items (and getting the uuids in return), which doesn't work the second time through.<br>
<br><span style="font-family:courier new,monospace">ovs-vsctl del-br br-int<br>ovs-vsctl del-br br-ex<br><br>service openvswitch-switch restart<br><br>ovs-vsctl add-br br-int<br>ovs-vsctl add-br br-ex<br>ovs-vsctl add-port br-ex eth2<br>
ip link set up br-ex <br><br>service quantum-plugin-openvswitch-agent restart<br>service quantum-dhcp-agent restart<br>service quantum-l3-agent restart<br><br>sh ./quantum-networking-filled.sh<br><br>service quantum-l3-agent restart</span><br>
<br><br></div><div class="gmail_extra">Here is what quantum looks like right now-- note the additional provider-routers, I'm guessing from failed runs of the quantum-networking script. Note also ...771's external gateway of ...3de0, which isn't showing up anywhere...could that be the problem? Should that be subnet ...06f6? <br>
<br><span style="font-family:courier new,monospace">root@os-network:~# quantum subnet-list<br>+--------------------------------------+------+---------------+--------------------------------------------------+<br>| id | name | cidr | allocation_pools |<br>
+--------------------------------------+------+---------------+--------------------------------------------------+<br>| 0617c874-9a95-40dc-ae4f-bb44eec806f6 | | <a href="http://10.5.5.0/24">10.5.5.0/24</a> | {"start": "10.5.5.2", "end": "10.5.5.254"} |<br>
| cde12bce-eeed-4041-87e3-5a1b905b3c98 | | <a href="http://10.42.36.0/23">10.42.36.0/23</a> | {"start": "10.42.36.130", "end": "10.42.36.150"} |<br>+--------------------------------------+------+---------------+--------------------------------------------------+<br>
root@os-network:~# quantum router-list<br>+--------------------------------------+-----------------+--------------------------------------------------------+<br>| id | name | external_gateway_info |<br>
+--------------------------------------+-----------------+--------------------------------------------------------+<br>| 8b8e7a08-16ba-4ab0-9800-88d0b17b6771 | provider-router | {"network_id": "e00341e1-3e59-4b8b-8c3a-7b227b423dc0"} |<br>
| 76fb89b9-ec11-4cad-ab0f-e160c3f0d4e7 | provider-router | null |<br>| af76d59e-22b2-4fbd-a95d-0b891824957e | provider-router | null |<br>
+--------------------------------------+-----------------+--------------------------------------------------------+<br>root@os-network:~# quantum port-list<br>+--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+<br>
| id | name | mac_address | fixed_ips |<br>+--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+<br>
| 9f9041ce-654d-4706-a208-60cf5fca5d90 | | fa:16:3e:e2:38:da | {"subnet_id": "0617c874-9a95-40dc-ae4f-bb44eec806f6", "ip_address": "10.5.5.1"} |<br>| 28108125-119c-4ce4-a3a3-537639589791 | | fa:16:3e:a9:a3:4c | {"subnet_id": "cde12bce-eeed-4041-87e3-5a1b905b3c98", "ip_address": "10.42.36.130"} |<br>
| 45ffdc5f-dad9-444a-aff4-3d39b607f828 | | fa:16:3e:36:2e:54 | {"subnet_id": "0617c874-9a95-40dc-ae4f-bb44eec806f6", "ip_address": "10.5.5.2"} |<br>| fe6d3b06-c27d-40a4-bba2-7b5d6060799a | | fa:16:3e:8d:6d:13 | {"subnet_id": "0617c874-9a95-40dc-ae4f-bb44eec806f6", "ip_address": "10.5.5.3"} |<br>
| 2c6f106f-de2a-46d1-afbd-b6d42a3557b3 | | fa:16:3e:95:94:9c | {"subnet_id": "0617c874-9a95-40dc-ae4f-bb44eec806f6", "ip_address": "10.5.5.4"} |<br>+--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+<br>
root@os-network:~# </span><br><br><br><br></div></div>