Network verification does not work with Netgear gs108e switch

Bug #1291655 reported by Vladimir Kozhukalov on 2014-03-12
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Medium
Vladimir Kozhukalov

Bug Description

It turned out that some network equipment filters out IP packages which have fake headers. Our current implementation tries to send probing packages with 1.0.0.0 ip address either as a source and as a destination. It is because we don't care about L3 when we verify L2 connectivity. However, if we put for example something like 10.0.0.1 as a source and 10.0.0.2 as a destination, verification works fine. The problem appears at least with Netgear gs108e switch. If nodes are connected to each other directly, problem disappears.

Changed in fuel:
status: New → Triaged
assignee: nobody → Vladimir Kozhukalov (kozhukalov)

Fix proposed to branch: master
Review: https://review.openstack.org/80364

Changed in fuel:
status: Triaged → In Progress
Mike Scherbakov (mihgen) on 2014-03-20
Changed in fuel:
milestone: none → 5.0
importance: Undecided → Medium

Looks like it is better to have IP addresses for netchecker probe packets set in settings.yaml

Reviewed: https://review.openstack.org/80364
Committed: https://git.openstack.org/cgit/stackforge/fuel-web/commit/?id=36ba000ff6589781fa3918a4762631ad9bcc7d8c
Submitter: Jenkins
Branch: master

commit 36ba000ff6589781fa3918a4762631ad9bcc7d8c
Author: Vladimir Kozhukalov <email address hidden>
Date: Thu Mar 13 22:32:51 2014 +0400

    Subs 1.0.0.0 -> 198.18.1.[1|2] in network checker

    It turned out that some network equipment filters
    out those fake addresses 1.0.0.0 which we used for
    network checker probing packages. 198.18.1.0/24 is
    one of those ranges which are reserved for benchmarking
    network connectivities http://tools.ietf.org/html/rfc2544,
    so it seems to be appropriate to use
    those addresses for this case by default.

    Change-Id: Iddb7e71de8746c5e55de5468fadc0b6d45c93800
    Closes-Bug: #1291655

Changed in fuel:
status: In Progress → Fix Committed
Dmitry Pyzhov (dpyzhov) on 2014-03-26
tags: added: backports-4.1.1
Dmitry Pyzhov (dpyzhov) on 2014-03-27
Changed in fuel:
milestone: 5.0 → 4.1.1
status: Fix Committed → In Progress
status: In Progress → Triaged
Changed in fuel:
status: Triaged → In Progress

Reviewed: https://review.openstack.org/84544
Committed: https://git.openstack.org/cgit/stackforge/fuel-main/commit/?id=5714f2a3cf56ebdc124e9555dfff0fe274e84bdd
Submitter: Jenkins
Branch: stable/4.1

commit 5714f2a3cf56ebdc124e9555dfff0fe274e84bdd
Author: Dmitry Borodaenko <email address hidden>
Date: Tue Apr 1 13:33:46 2014 -0700

    Subs 1.0.0.0 -> 198.18.1.[1|2] in network checker

    It turned out that some network equipment filters
    out those fake addresses 1.0.0.0 which we used for
    network checker probing packages. 198.18.1.0/24 is
    one of those ranges which are reserved for benchmarking
    network connectivities http://tools.ietf.org/html/rfc2544,
    so it seems to be appropriate to use
    those addresses for this case by default.

    Change-Id: I616b524db0675d752279bdf294aaba486d253336
    Closes-Bug: #1291655
    Signed-off-by: Dmitry Borodaenko <email address hidden>

Dmitry Pyzhov (dpyzhov) on 2014-04-03
Changed in fuel:
status: In Progress → Fix Committed
Mike Scherbakov (mihgen) on 2014-05-08
tags: added: release-notes
Meg McRoberts (dreidellhasa) wrote :

Marked as fixed issue in 5.0 Release Notes

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers