User's Guide

Managing HyperFabric
Verifying Communications within the Fabric
Chapter 5
98
• -l specifies that you want to do local loopback testing on a particular adapter. Note
that if you specify this parameter (-l), you must also specify the -c adapter_ID
parameter (described above).
• -s specifies that you want to loopback at the switch port attached to a particular
adapter. Note that if you specify this parameter (-s), you must also specify the
-c adapter_ID parameter (described above).
• -p specifies that you want to send packet_count number of 256-byte packets.
packet_count can be any positive integer. This parameter is useful for building
scripts for debugging or for hardware verification. If you do not specify this
parameter, one packet is sent each second, until you stop the command with a
CTRL-C.
• -? displays the online help for clic_probe.
If you do not specify any of the above parameters, the online help for clic_probe is
displayed.
NOTE Also see the clic_diag command to:
Probe a specific remote node.
Dump and format trace data.
Set the tracing level for the HyperFabric software and firmware.
The clic_diag command is detailed in the Running Diagnostics section of Chapter 6,
Troubleshooting.
Examples of clic_probe
Some examples of using clic_probe are shown below.
• Example 1
If the local node is bently6 and you want to send five packets to verify that the
adapter clic0 (which is on bently6) is able to handle traffic, issue this command:
clic_probe -l -c clic0 -p 5
The generated output could look like this:
CLIC_PROBE: 256 byte packets
Local Loopback: Source and Target Adapter ID: bently6.corp3.com:clic0
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.
256 bytes: seq_num = 5. Packet Acknowledged.
--------- bently6.corp3.com CLIC_PROBE Statistics --------
5 packets transmitted, 5 packets received, 0% packet loss.
• Example 2
If the local node is bently6, and you want to verify communications with the remote
node bently4, issue this command: