Ask Your Question

Revision history [back]

Use as comment
I want to see analogs of this reports on your Controller&&Network Node :- [root@juno01vhs ~(keystone_admin)]# ip netns exec qrouter-2788c38c-e832-4b96-9244-a36b97d2729c route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 qg-f9ca5a26-63 15.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 qr-86644bd2-66 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 qg-f9ca5a26-63 [root@juno01vhs ~(keystone_admin)]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 br-ex 169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 enp2s0 169.254.0.0 0.0.0.0 255.255.0.0 U 1003 0 0 enp5s1 169.254.0.0 0.0.0.0 255.255.0.0 U 1006 0 0 br-ex 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 enp5s1 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br-ex

Use as comment
I want to see analogs of this reports on your Controller&&Network Node :- :-

[root@juno01vhs ~(keystone_admin)]# ip netns exec qrouter-2788c38c-e832-4b96-9244-a36b97d2729c route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 qg-f9ca5a26-63
15.0.0.0        0.0.0.0         255.255.255.0   U     0      0        0 qr-86644bd2-66
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 qg-f9ca5a26-63
[root@juno01vhs ~(keystone_admin)]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 br-ex
169.254.0.0     0.0.0.0         255.255.0.0     U     1002   0        0 enp2s0
169.254.0.0     0.0.0.0         255.255.0.0     U     1003   0        0 enp5s1
169.254.0.0     0.0.0.0         255.255.0.0     U     1006   0        0 br-ex
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 enp5s1
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 br-ex

br-ex

Use as comment
I want to see analogs of this reports on your Controller&&Network Node :-

[root@juno01vhs ~(keystone_admin)]# ip netns exec qrouter-2788c38c-e832-4b96-9244-a36b97d2729c route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 qg-f9ca5a26-63
15.0.0.0        0.0.0.0         255.255.255.0   U     0      0        0 qr-86644bd2-66
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 qg-f9ca5a26-63
[root@juno01vhs ~(keystone_admin)]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 br-ex
169.254.0.0     0.0.0.0         255.255.0.0     U     1002   0        0 enp2s0
169.254.0.0     0.0.0.0         255.255.0.0     U     1003   0        0 enp5s1
169.254.0.0     0.0.0.0         255.255.0.0     U     1006   0        0 br-ex
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 enp5s1
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 br-ex

And also :

[root@juno01vhs ~(keystone_admin)]# ip netns exec qrouter-2788c38c-e832-4b96-9244-a36b97d2729c ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

qg-f9ca5a26-63: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.154  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::f816:3eff:fe97:d615  prefixlen 64  scopeid 0x20<link>
        ether fa:16:3e:97:d6:15  txqueuelen 0  (Ethernet)
        RX packets 32310  bytes 25822184 (24.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 18323  bytes 8090941 (7.7 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

qr-86644bd2-66: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 15.0.0.1  netmask 255.255.255.0  broadcast 15.0.0.255
        inet6 fe80::f816:3eff:fe3e:ec5f  prefixlen 64  scopeid 0x20<link>
        ether fa:16:3e:3e:ec:5f  txqueuelen 0  (Ethernet)
        RX packets 19561  bytes 8198310 (7.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 26333  bytes 25189484 (24.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

and also

[root@juno01vhs ~(keystone_admin)]# ip netns exec qdhcp-849dd890-608f-484f-949e-918d679ca206 route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         15.0.0.1        0.0.0.0         UG    0      0        0 tap7ab54cc6-51
15.0.0.0        0.0.0.0         255.255.255.0   U     0      0        0 tap7ab54cc6-51

Use as comment
I want to see analogs of this reports on your Controller&&Network Node :-

[root@juno01vhs ~(keystone_admin)]# ip netns exec qrouter-2788c38c-e832-4b96-9244-a36b97d2729c route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 qg-f9ca5a26-63
15.0.0.0        0.0.0.0         255.255.255.0   U     0      0        0 qr-86644bd2-66
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 qg-f9ca5a26-63
[root@juno01vhs ~(keystone_admin)]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 br-ex
169.254.0.0     0.0.0.0         255.255.0.0     U     1002   0        0 enp2s0
169.254.0.0     0.0.0.0         255.255.0.0     U     1003   0        0 enp5s1
169.254.0.0     0.0.0.0         255.255.0.0     U     1006   0        0 br-ex
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 enp5s1
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 br-ex

And also :I have converted your routing table on Network Node

[root@juno01vhs ~(keystone_admin)]# ip netns exec qrouter-2788c38c-e832-4b96-9244-a36b97d2729c ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

qg-f9ca5a26-63: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.154  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::f816:3eff:fe97:d615  prefixlen 64  scopeid 0x20<link>
        ether fa:16:3e:97:d6:15  txqueuelen 0  (Ethernet)
        RX packets 32310  bytes 25822184 (24.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 18323  bytes 8090941 (7.7 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

qr-86644bd2-66: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 15.0.0.1  netmask 255.255.255.0  broadcast 15.0.0.255
        inet6 fe80::f816:3eff:fe3e:ec5f  prefixlen 64  scopeid 0x20<link>
        ether fa:16:3e:3e:ec:5f  txqueuelen 0  (Ethernet)
        RX packets 19561  bytes 8198310 (7.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 26333  bytes 25189484 (24.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

and also

[root@juno01vhs ~(keystone_admin)]# ip netns exec qdhcp-849dd890-608f-484f-949e-918d679ca206 # route -n
-n 
Kernel IP routing table
table Destination  Gateway  Genmask  Flags Metric Ref  Use Iface
0.0.0.0         15.0.0.1        0.0.0.0   10.0.2.2   0.0.0.0       UG    0      0        0 tap7ab54cc6-51
15.0.0.0        0.0.0.0            0 0 0 p2p1 
10.0.2.0     0.0.0.0   255.255.255.0   U     0      0        0 tap7ab54cc6-51
U     0 0 0 p2p1 
169.254.0.0  0.0.0.0   255.255.0.0    U    1002 0 0 p2p1 
169.254.0.0  0.0.0.0   255.255.0.0    U    1003 0 0 p7p1 
169.254.0.0  0.0.0.0   255.255.0.0    U    1005 0 0 br-ex 
192.168.1.0  0.0.0.0   255.255.255.0  U    0    0 0 br-ex

If my conversion is correct your routing table doesn't have an entry

0.0.0.0   192.168.1.1    0.0.0.0   UG    0      0     0  br-ex

Hence your gateway 192.168.1.1 doesn't route packets from Network Node outside.

Use as comment
I want to see analogs of this reports on your Controller&&Network Node :-

[root@juno01vhs ~(keystone_admin)]# ip netns exec qrouter-2788c38c-e832-4b96-9244-a36b97d2729c route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 qg-f9ca5a26-63
15.0.0.0        0.0.0.0         255.255.255.0   U     0      0        0 qr-86644bd2-66
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 qg-f9ca5a26-63
[root@juno01vhs ~(keystone_admin)]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 br-ex
169.254.0.0     0.0.0.0         255.255.0.0     U     1002   0        0 enp2s0
169.254.0.0     0.0.0.0         255.255.0.0     U     1003   0        0 enp5s1
169.254.0.0     0.0.0.0         255.255.0.0     U     1006   0        0 br-ex
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 enp5s1
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 br-ex

I have converted your routing table on Network Node

# route -n 
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0      10.0.2.2   0.0.0.0       UG         0 0 0 0        0 0     p2p1 
10.0.2.0     0.0.0.0   255.255.255.0  U     0 0 0        0 0     p2p1 
169.254.0.0  0.0.0.0   255.255.0.0    U    1002 0 0      0 0     p2p1 
169.254.0.0  0.0.0.0   255.255.0.0    U    1003 0 0      0 0    p7p1 
169.254.0.0  0.0.0.0   255.255.0.0    U    1005 0 0      0 0    br-ex 
192.168.1.0  0.0.0.0   255.255.255.0  U    0    0 0      0 0    br-ex

If my conversion is correct your routing table doesn't have an entry

0.0.0.0   192.168.1.1    0.0.0.0   UG    0      0     0  br-ex

Hence your gateway 192.168.1.1 doesn't route packets from Network Node outside.

Use as comment
I want to see analogs of this reports on your Controller&&Network Node :-

 [root@juno01vhs ~(keystone_admin)]# ip netns exec qrouter-2788c38c-e832-4b96-9244-a36b97d2729c route -n
 Kernel IP routing table
 Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
 0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 qg-f9ca5a26-63
15.0.0.0    br-ex
    169.254.0.0     0.0.0.0         255.255.0.0     U     1002   0        0 enp2s0
    169.254.0.0     0.0.0.0         255.255.0.0     U     1003   0        0 enp5s1
    169.254.0.0     0.0.0.0         255.255.0.0     U     1006   0        0 br-ex
    172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
    192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 qr-86644bd2-66
enp5s1
    192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 qg-f9ca5a26-63
[root@juno01vhs ~(keystone_admin)]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 br-ex
169.254.0.0     0.0.0.0         255.255.0.0     U     1002   0        0 enp2s0
169.254.0.0     0.0.0.0         255.255.0.0     U     1003   0        0 enp5s1
169.254.0.0     0.0.0.0         255.255.0.0     U     1006   0        0 br-ex
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 enp5s1
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 br-ex

I have converted your routing table on Network Node

Node

    # route -n 
 Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface
 0.0.0.0      10.0.2.2   0.0.0.0       UG    0        0 0     p2p1 
 10.0.2.0     0.0.0.0   255.255.255.0  U     0        0 0     p2p1 
 169.254.0.0  0.0.0.0   255.255.0.0    U    1002      0 0     p2p1 
 169.254.0.0  0.0.0.0   255.255.0.0    U    1003      0 0    p7p1 
 169.254.0.0  0.0.0.0   255.255.0.0    U    1005      0 0    br-ex 
 192.168.1.0  0.0.0.0   255.255.255.0  U    0         0 0    br-ex

If my conversion is correct your routing table doesn't have an entry

0.0.0.0   192.168.1.1    0.0.0.0   UG    0      0     0  br-ex

Hence your gateway 192.168.1.1 doesn't route packets from Network Node outside.
Next issue.I discovered in your reports

ifconfig :-
br-ex: flags=4419<up,broadcast,running,promisc,multicast> mtu 1500 inet 192.168.1.107 netmask 255.255.255.0 broadcast 192.168.1.255

ovs-vsctl show:
 Port "vxlan-c0a8016c" 
Interface "vxlan-c0a8016c" type: vxlan options: {in_key=flow, local_ip="192.168.1.107", out_key=flow, remote_ip="192.168.1.108"}

br-ex is not supposed to be an endpoint of your VXLAN tunnel

Use as comment
I want to see analogs of this reports on your Controller&&Network Node :-

 [root@juno01vhs ~(keystone_admin)]# route -n
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 br-ex
    169.254.0.0     0.0.0.0         255.255.0.0     U     1002   0        0 enp2s0
    169.254.0.0     0.0.0.0         255.255.0.0     U     1003   0        0 enp5s1
    169.254.0.0     0.0.0.0         255.255.0.0     U     1006   0        0 br-ex
    172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
    192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 enp5s1
    192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 br-ex

I have converted your routing table on Network Node

    # route -n 
    Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface
    0.0.0.0      10.0.2.2   0.0.0.0       UG    0        0 0     p2p1 
    10.0.2.0     0.0.0.0   255.255.255.0  U     0        0 0     p2p1 
    169.254.0.0  0.0.0.0   255.255.0.0    U    1002      0 0     p2p1 
    169.254.0.0  0.0.0.0   255.255.0.0    U    1003      0 0    p7p1 
    169.254.0.0  0.0.0.0   255.255.0.0    U    1005      0 0    br-ex 
    192.168.1.0  0.0.0.0   255.255.255.0  U    0         0 0    br-ex

If my conversion is correct your routing table doesn't have an entry

0.0.0.0   192.168.1.1    0.0.0.0   UG    0      0     0  br-ex

Hence your gateway 192.168.1.1 doesn't route packets from Network Node outside.
Next issue.I discovered in your reports

ifconfig :-
br-ex: flags=4419<up,broadcast,running,promisc,multicast> mtu 1500 inet 192.168.1.107 netmask 255.255.255.0 broadcast 192.168.1.255

ovs-vsctl show:
 Port "vxlan-c0a8016c" 
Interface "vxlan-c0a8016c" type: vxlan options: {in_key=flow, local_ip="192.168.1.107", out_key=flow, remote_ip="192.168.1.108"}

br-ex is not supposed to be an endpoint of your VXLAN tunneltunnel Disregard this notice I meant real boxes not VMs

Use as comment
I want to see analogs of this reports on your Controller&&Network Node :-

 [root@juno01vhs ~(keystone_admin)]# route -n
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 br-ex
    169.254.0.0     0.0.0.0         255.255.0.0     U     1002   0        0 enp2s0
    169.254.0.0     0.0.0.0         255.255.0.0     U     1003   0        0 enp5s1
    169.254.0.0     0.0.0.0         255.255.0.0     U     1006   0        0 br-ex
    172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
    192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 enp5s1
    192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 br-ex

I have converted your routing table on Network Node

    # route -n 
    Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface
    0.0.0.0      10.0.2.2   0.0.0.0       UG    0        0 0     p2p1 
    10.0.2.0     0.0.0.0   255.255.255.0  U     0        0 0     p2p1 
    169.254.0.0  0.0.0.0   255.255.0.0    U    1002      0 0     p2p1 
    169.254.0.0  0.0.0.0   255.255.0.0    U    1003      0 0    p7p1 
    169.254.0.0  0.0.0.0   255.255.0.0    U    1005      0 0    br-ex 
    192.168.1.0  0.0.0.0   255.255.255.0  U    0         0 0    br-ex

If my conversion is correct your routing table doesn't have an entry

0.0.0.0   192.168.1.1    0.0.0.0   UG    0      0     0  br-ex

Hence your gateway 192.168.1.1 doesn't route packets from Network Node outside.
Next issue.I

Disregard this notice I meant real boxes not VMs

I discovered in your reports

ifconfig :-
br-ex: flags=4419<up,broadcast,running,promisc,multicast> mtu 1500 inet 192.168.1.107 netmask 255.255.255.0 broadcast 192.168.1.255

ovs-vsctl show:
 Port "vxlan-c0a8016c" 
Interface "vxlan-c0a8016c" type: vxlan options: {in_key=flow, local_ip="192.168.1.107", out_key=flow, remote_ip="192.168.1.108"}

br-ex is not supposed to be an endpoint of your VXLAN tunnel Disregard this notice I meant real boxes not VMstunnel