Este contenido no está disponible en el idioma seleccionado.
Appendix A. Multus prerequisites validation tool
Multus CNI is a container network interface that provides a pluggable application programming interface to configure network interfaces in Linux containers. It is considered a meta-plug-in: a CNI plug-in that can run other CNI plug-ins. The Multus prerequisites validation tool should be used to validate the OpenShift configuration, NetworkAttachmentDefinitions, and underlying network compatibility before installing OpenShift Data Foundation.
This is an interactive tool to help support in-the-field debug and resolution of common configuration issues that affect Multus clusters. It runs a validation test that determines whether the current NetworkAttachmentDefinition, and system configurations support OpenShift Data Foundation with Multus.
It is a long-running test. It starts up a web server and many clients to verify that Multus network communication works properly.
It does not perform any load testing. Networks that cannot support high volumes of Ceph traffic might still encounter runtime issues. This might be noticeable with high I/O load or during OSD rebalancing (for example, during node/disk failure or during OpenShift Data Foundation upgrade). Therefore, it is recommended to perform network load testing to ensure that base network configurations meet user requirements. To know more about OSD rebalancing refer to the documentation.
A.1. How to use Multus prerequisites validation tool Copiar enlaceEnlace copiado en el portapapeles!
Run the validation tool from an OpenShift administrator shell after Multus NetworkAttachmentDefinitions are configured and the OpenShift Data Foundation operator is installed but before an OpenShift Data Foundation StorageCluster is installed.
Procedure
To run the validation tool, first access the
rook-ceph-operatorpod using theoc rshcommand:oc rsh <rook-ceph-operator-pod-name>
$ oc rsh <rook-ceph-operator-pod-name>Copy to Clipboard Copied! Toggle word wrap Toggle overflow The tool provides extensive help text.
Run the tool.
./rook multus validation run -h
$ ./rook multus validation run -hCopy to Clipboard Copied! Toggle word wrap Toggle overflow When you run the tool, you get the most up-to-date version of the tool.
Validation tool configuration file
The tool supports a configuration file that allows configuring the number of test daemons on different types of nodes. The config file can be used to test CSI+Ceph+OSD placement on storage nodes while simultaneously testing only CSI placement on non-storage nodes. The tool has built-in config file examples with commented documentation to help get started more quickly.
./rook multus validation config -h
$ ./rook multus validation config -h
A.2. Troubleshooting validation tool Copiar enlaceEnlace copiado en el portapapeles!
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 describecommand 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_*andip_netns_exec_*_route_*from container namespaces
-
A.3. How to get help Copiar enlaceEnlace copiado en el portapapeles!
If you are having trouble resolving the issue based on these troubleshooting steps described in the previous section, a substantial amount of information should be collected for getting help.
The tool will list resources that should be collected into an archive file in this case. For OpenShift and OpenShift Data Foundation, the following OpenShift tools contains the information needed for further debugging:
- Network diagrams
- ODF must-gather
- OCP must-gather
- OCP must-gather network logs
- SOS reports from all nodes on which test pods are running (https://access.redhat.com/solutions/3530881)
Multus is highly integrated among various product layers, and issues are most likely to be related to configuration or the physical hardware environment rather than product bugs. Initial investigation at the engineering layer will involve ODF, OpenShift, and possibly RHEL networking experts to rule out configuration or environment.
- General Multus bugs/help: OCP Jira: https://issues.redhat.com/projects/OCPBUGSM
- ODF Multus bugs: ODF jira: https://issues.redhat.com/projects/DFBUGS
- Contact Red Hat customer Support.