Troubleshooting validation tool

If the test fails when you run the validation tool, it suggests some things to check based on the failure condition. This helps to resolve common configuration issues quickly.

• For diagnosing issues with the tool itself, use the --log-level DEBUG for getting additional details.

• If pods are not starting, you can expect the following issues:

  • Problem with NAD configuration.
  • The oc pod describe command contains the error as an event.
  • Some NICs do not support enough virtual ports or VLANs for the additional MAC addresses.

• If pods are starting but not communicating, you can expect the following issues:

  • Network design or configuration might contain errors
  • Network switch might be blocking sub-interface MAC addresses or IPs (check promiscuous mode settings)
  • Switch firewall
  • System or NAD Linux networking configurations might be blocking the traffic

  • SOS report will have good information to look at next

    • ip_netns_exec_*_address_* and ip_netns_exec_*_route_* from container namespaces