Troubleshooting HyperFabric
Running Diagnostics
Example of clic_diag
An example of the clic_diag command is shown below.
If the local node is bently6, and you want to confirm that all of the adapters on bently6 are communicating with the target adapters on bently8, issue this command:
clic_diag -r bently8
The generated output could look like this:
CLIC_PROBE: 256 byte packets
Source adapter id: bently6.corp4.com:clic0
Target adapter id: bently8.corp2.com:clic1
256 | bytes: | seq_num = 0. | Packet Acknowledged. |
256 | bytes: | seq_num = 1. | Packet Acknowledged. |
256 | bytes: | seq_num = 2. | Packet Acknowledged. |
256 | bytes: | seq_num = 3. | Packet Acknowledged. |
256 | bytes: | seq_num = 4. | Packet Acknowledged. |
CLIC_PROBE Statistics | |||
5 packets transmitted, 5 packets received, 0% packet loss. CLIC_PROBE: 256 byte packets
Source adapter id: bently6.corp4.com:clic1
Target adapter id: bently8.corp2.com:clic3
256 bytes: seq_num = 0. Packet Acknowledged.
256 bytes: seq_num = 1. Packet Acknowledged.
256 bytes: seq_num = 2. Packet Acknowledged.
256 bytes: seq_num = 3. Packet Acknowledged.
256 bytes: seq_num = 4. Packet Acknowledged.
5 packets transmitted, 5 packets received, 0% packet loss.
Chapter 5 | 107 |
