Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-72865

Detect common network issues using the latency checkup

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • CNV Network
    • netissues-checkup
    • Product / Portfolio Work
    • 77
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • To Do
    • CNV-66545Detect common network issues using the latency checkup

      Goal

      Help support teams detect common networking issues using a checkup:

      • Check for MTU fragmentation between VMs by running ping -f -l <mtu - proto headers>
      • Check for MTU segmentation between a VM and a remote server
      • Use iperf to measure the bandwidth between 2 VMs, or 2 hosts
      • Check for routing issues trying to connect to a remote server, or gateway/DNS server
      • Measure the stun time

      User Stories

      • High-Level goal-based user story, with context.
        "As a <VM owner/cluster administrator>, I want <to Achieve Some Goal>, so that <Some Reason/Context>."
      • another user story

      Non-Requirements

      • List of things not included in this epic, to alleviate any doubt raised during the grooming process.

      Notes

      • This could be an extension of the latency checkup, but also of the self-validation checkup - we should consider both. The deciding factor would be - is it an absolute must that the user supplies attributes, or can we deduce it ourselves. There is also some overlap with CNV-67610

              phoracek@redhat.com Petr Horacek
              phoracek@redhat.com Petr Horacek
              Yoss Segev Yoss Segev
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: