Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-2315

IPFIX export stops working if the connection is reset

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • netobserv-1.9.1
    • netobserv-1.9
    • None
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • NetObserv - Sprint 273
    • None
    • None
    • Hide
      Previously, when configuring an IPFIX exporter, if the collector restarted, the connectivity could be lost and network flows stopped being sent to the collector.
      Now, the connection is restored so that network flows continue to be sent to the collector.
      Show
      Previously, when configuring an IPFIX exporter, if the collector restarted, the connectivity could be lost and network flows stopped being sent to the collector. Now, the connection is restored so that network flows continue to be sent to the collector.

      See upstream: https://github.com/orgs/netobserv/discussions/1649

      To reproduce:

      • start an IPFIX collector *
      • start netobserv with ipfix configured
      • check flows are received
      • re-deploy the collector (e.g. so that the service IP changes)
      • flows aren't received anymore

       

      *: an example of collector can be FLP itself, such as defined here: https://github.com/netobserv/flowlogs-pipeline/blob/main/contrib/kubernetes/ipfix-collector-stdout.yaml 

              jtakvori Joel Takvorian
              jtakvori Joel Takvorian
              None
              None
              None
              Mehul Modi Mehul Modi
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: