
Troubleshooting HyperFabric
Running Diagnostics
packet_data or 0x0004 packet_hdr or 0x0008 data_struct or 0x0010
Trace the packet data.
Trace the protocol headers (TCP/UDP/IP).
Trace the HyperFabric software
rcv_path or 0x0020 | Trace the HyperFabric software receive path. |
control or 0x0040 | Trace the HyperFabric software control |
| messages. |
all or 0xffff | Turn on all possible trace levels. Note that this |
| will have a severe impact on performance. |
To find out what the current tracing level is, run this parameter
•
•
•
trace_buffer_size. The buffer is dynamically allocated when tracing is enabled. Also, the buffer is circular, which means that when the end of the buffer is reached, the data wraps around to the beginning of the buffer (and overwrites any previous data). If you do not specify this parameter, a default buffer is created with a size of 64k bytes.
•
/var/adm/clic_ip_drv.trc1).
•
•
If you do not specify any of the above parameters, the online help for clic_diag is displayed.
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
118 | Chapter 6 |