2.2.57. selftest
2.2.57. selftest
Run appliance self tests.
Description
The appliance self tests are used to verify the correct function of hardware components.
Normal SGW operations might be disrupted during the test(s).
The outcome of the throughput crypto accelerator tests are dependent on configuration values. If the
number of large buffers (LocalReassSettings->LocalReass_NumLarge) too low, it might lower
throughput result. In the field 'Drop/Fail', the 'Drop' column contains the number of packets that
were dropped before ever reaching the crypto accelerator and the 'Fail' column contains the number
of packets that for some reason failed encryption. The 'Pkt In/Out' field shows the total number of
packets sent to, and returned from the accelerator.
The interface tests 'traffic' and 'throughput' are dependent on the settings for the NIC ring sizes and
possibly also license limitations. The 'traffic' test uses a uniform random distribution of six packet
sizes between 60 and 1518 bytes. The content of each received packet is validated. The 'throughput'
test uses only the largest packet size, and does not validate the contents of the received packets.
Example 2.12. Interface ping test between all interfaces
selftest -ping
Example 2.13. Interface ping test between interfaces 'if1' and 'if2'
selftest -ping -interfaces=if1,if2
Example 2.14. Start a 30 min burn-in duration test, testing RAM, storage media and
crypto the accelerator
selftest -burnin -minutes 30 -media -memory -cryptoaccel
Usage
selftest -memory [-num=<Integer>]
Check the sanity of the RAM.
selftest -media [-size=<Integer>]
Check the sanity of the disk drive.
selftest -mac
Check if there are MAC address collisions on the interfaces.
64
Chapter 2. Command Reference