Uploaded image for project: 'Fast Datapath Product'
  1. Fast Datapath Product
  2. FDP-1656

CLONE [ovn25.09 fast-datapath-rhel-9] - BGP: connected-as-host redistribution requires an LRP with an IP

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • None
    • None
    • ovn25.09
    • 1
    • False
    • False
    • Hide

      Given a logical router with dynamic routing enabled, redistributing connected-as-host routes, connected to a provider switch via a LRP without an IP address, and a LSP on the switch with IP 192.168.111.180,

      When the OVN northd processes the connected-as-host redistribution,

      Then an Advertised_Route entry is created in the SB database for the LSP's IP address and the route is advertised to the BGP peer without requiring an IP address on the LRP.

      Show
      Given a logical router with dynamic routing enabled, redistributing connected-as-host routes, connected to a provider switch via a LRP without an IP address, and a LSP on the switch with IP 192.168.111.180, When the OVN northd processes the connected-as-host redistribution, Then an Advertised_Route entry is created in the SB database for the LSP's IP address and the route is advertised to the BGP peer without requiring an IP address on the LRP.
    • ovn25.09-25.09.0-beta.20.el9fdp
    • rhel-9
    • None
    • rhel-net-ovn
    • ssg_networking
    • +

       Problem Description:

      I use a topology where a provider switch is connected to a router with dynamic routing through localnet ports. Because of that I have a direct connection between the provider switch and the router that is not used for any real traffic and its purpose is only to advertise routes related to the provider switch - such as NAT entries from routers connected to this switch.

      Because the dummy connection between the router and the provider switch is not used, the LRP from the connection has no IP assigned. This make connected-as-host not picking up addresses from the provider switch because the code assumes and IP address.

      If I add the IP to the LRP then the routes are advertised as intended but including the LRP unused address.

       Impact Assessment: No routes to the LSPs are advertise making the workloads without connectivity

       

       Software Versions: OVN 25.03

        Issue Type: New issue

       

       Reproducibility: 100% reproducible

       

       Reproduction Steps:

      NB DB file attached

      the LSP with IP 192.168.111.180 does not create an Advertised_Route entry

       

       Expected Behavior: The routes from the connected datapaths should be advertised regardless of the LRP IP configuration.

       

       Observed Behavior: LSP addresses do not create Advertised_Routes

              dceara@redhat.com Dumitru Ceara
              ovnteam@redhat.com OVN Team
              Jianlin Shi Jianlin Shi
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: