← Back to team overview

yahoo-eng-team team mailing list archive

  1. yahoo-eng-team team
  2. Mailing list archive
  3. Message #42800

[Bug 1523031] [NEW] Neighbor table entry for router missing with Linux bridge + L3HA + L2 population

  Thread Previous • Date Previous • • Thread Next 
Public bug reported:

Using Linux bridge, L3HA, and L2 population on Liberty, the neighbor
table (ip neigh show) on the compute node lacks an entry for the router
IP address. For example, using a router with 172.16.1.1 and instance
with 172.16.1.4:

On the node with the L3 agent containing the router:

# ip neigh show
169.254.192.1 dev vxlan-476 lladdr fa:16:3e:9b:d5:6f PERMANENT
10.4.30.11 dev eth1 lladdr bc:76:4e:04:3c:59 REACHABLE
10.4.11.11 dev eth0 lladdr bc:76:4e:04:d0:75 REACHABLE
172.16.1.4 dev vxlan-466 lladdr fa:16:3e:ad:44:df PERMANENT
10.4.30.31 dev eth1 lladdr bc:76:4e:05:1f:5f STALE
10.4.11.31 dev eth0 lladdr bc:76:4e:04:38:4c STALE
10.4.30.1 dev eth1 lladdr bc:76:4e:04:41:62 STALE
10.4.11.1 dev eth0 lladdr bc:76:4e:04:77:72 DELAY
172.16.1.2 dev vxlan-466 lladdr fa:16:3e:a0:83:a5 PERMANENT

# ip netns exec qrouter-1521b4b1-7de9-4ed0-be19-69ac02ccf520 ping 172.16.1.4
PING 172.16.1.4 (172.16.1.4) 56(84) bytes of data.
...

On the node with the instance:

# ip neigh show
172.16.1.2 dev vxlan-466 lladdr fa:16:3e:a0:83:a5 PERMANENT
10.4.11.1 dev eth0 lladdr bc:76:4e:04:77:72 DELAY
172.16.1.3 dev vxlan-466 lladdr fa:16:3e:41:3b:de PERMANENT
10.4.30.1 dev eth1 lladdr bc:76:4e:04:41:62 STALE
10.4.11.12 dev eth0 lladdr bc:76:4e:05:e2:f8 STALE
10.4.30.12 dev eth1 lladdr bc:76:4e:05:76:d1 STALE
10.4.11.41 dev eth0 lladdr bc:76:4e:05:e3:6a STALE
10.4.11.11 dev eth0 lladdr bc:76:4e:04:d0:75 REACHABLE
10.4.30.11 dev eth1 lladdr bc:76:4e:04:3c:59 STALE

172.16.1.2 and 172.16.1.3 belong to DHCP agents. I can access the
instance from within both DHCP agent namespaces.

On the node with the instance, I manually add a neighbor entry for the
router:

# ip neigh replace 172.16.1.1 lladdr fa:16:3e:0a:d4:39 dev vxlan-466 nud
permanent

On the node with the L3 agent containing the router:

# ip netns exec qrouter-1521b4b1-7de9-4ed0-be19-69ac02ccf520 ping 172.16.1.4
64 bytes from 172.16.1.4: icmp_seq=1 ttl=64 time=2.21 ms
64 bytes from 172.16.1.4: icmp_seq=2 ttl=64 time=45.9 ms
64 bytes from 172.16.1.4: icmp_seq=3 ttl=64 time=1.23 ms
64 bytes from 172.16.1.4: icmp_seq=4 ttl=64 time=0.975 ms

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1523031

Title:
  Neighbor table entry for router missing with Linux bridge + L3HA + L2
  population

Status in neutron:
  New

Bug description:
  Using Linux bridge, L3HA, and L2 population on Liberty, the neighbor
  table (ip neigh show) on the compute node lacks an entry for the
  router IP address. For example, using a router with 172.16.1.1 and
  instance with 172.16.1.4:

  On the node with the L3 agent containing the router:

  # ip neigh show
  169.254.192.1 dev vxlan-476 lladdr fa:16:3e:9b:d5:6f PERMANENT
  10.4.30.11 dev eth1 lladdr bc:76:4e:04:3c:59 REACHABLE
  10.4.11.11 dev eth0 lladdr bc:76:4e:04:d0:75 REACHABLE
  172.16.1.4 dev vxlan-466 lladdr fa:16:3e:ad:44:df PERMANENT
  10.4.30.31 dev eth1 lladdr bc:76:4e:05:1f:5f STALE
  10.4.11.31 dev eth0 lladdr bc:76:4e:04:38:4c STALE
  10.4.30.1 dev eth1 lladdr bc:76:4e:04:41:62 STALE
  10.4.11.1 dev eth0 lladdr bc:76:4e:04:77:72 DELAY
  172.16.1.2 dev vxlan-466 lladdr fa:16:3e:a0:83:a5 PERMANENT

  # ip netns exec qrouter-1521b4b1-7de9-4ed0-be19-69ac02ccf520 ping 172.16.1.4
  PING 172.16.1.4 (172.16.1.4) 56(84) bytes of data.
  ...

  On the node with the instance:

  # ip neigh show
  172.16.1.2 dev vxlan-466 lladdr fa:16:3e:a0:83:a5 PERMANENT
  10.4.11.1 dev eth0 lladdr bc:76:4e:04:77:72 DELAY
  172.16.1.3 dev vxlan-466 lladdr fa:16:3e:41:3b:de PERMANENT
  10.4.30.1 dev eth1 lladdr bc:76:4e:04:41:62 STALE
  10.4.11.12 dev eth0 lladdr bc:76:4e:05:e2:f8 STALE
  10.4.30.12 dev eth1 lladdr bc:76:4e:05:76:d1 STALE
  10.4.11.41 dev eth0 lladdr bc:76:4e:05:e3:6a STALE
  10.4.11.11 dev eth0 lladdr bc:76:4e:04:d0:75 REACHABLE
  10.4.30.11 dev eth1 lladdr bc:76:4e:04:3c:59 STALE

  172.16.1.2 and 172.16.1.3 belong to DHCP agents. I can access the
  instance from within both DHCP agent namespaces.

  On the node with the instance, I manually add a neighbor entry for the
  router:

  # ip neigh replace 172.16.1.1 lladdr fa:16:3e:0a:d4:39 dev vxlan-466
  nud permanent

  On the node with the L3 agent containing the router:

  # ip netns exec qrouter-1521b4b1-7de9-4ed0-be19-69ac02ccf520 ping 172.16.1.4
  64 bytes from 172.16.1.4: icmp_seq=1 ttl=64 time=2.21 ms
  64 bytes from 172.16.1.4: icmp_seq=2 ttl=64 time=45.9 ms
  64 bytes from 172.16.1.4: icmp_seq=3 ttl=64 time=1.23 ms
  64 bytes from 172.16.1.4: icmp_seq=4 ttl=64 time=0.975 ms

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1523031/+subscriptions

Follow ups

  Thread Previous • Date Previous • • Thread Next