Applies To:

Show Versions Show Versions

Manual Chapter: Platform Diagnostics platform_diag tests
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Platform Diagnostics platform_diag tests

You can run platform_diag commands on your system using one of these methods:

  • Run all tests by typing platform_diag
  • Run a specific test by typing platform_diag <test-name>
Warning: You should not run these tests on an active system, since these tests stop system daemons from using bigstart stop. This stops traffic to the system and might disable some network interfaces.

Run all platform_diag tests

You can use the platform_diag test without any options to run all tests.
  1. Log in to the command line of the system using an account with root access.
  2. Run all Platform Diagnostics platform_diag tests.
    platform_diag
If the output is Overall Platform Health: PASS, the platform passed all tests. If the output is FAIL, you should consider taking the system out of production to run the End-User Diagnostic (EUD) tests.

Check SSL and compression

You use the platform_diag hwaccel test to check the hardware SSL and compression accelerators installed in the system.
Warning: This test stops system daemons using bigstart stop, stops traffic to the system, and might disable some network interfaces.
  1. Log in to the command line of the system using an account with root access.
  2. Check the integrity of the SSL and compression accelerator hardware installed in the system.
    platform_diag hwaccel
    Note: This command could take a while to complete. You can run bigstart status to see the status of each of the default services. For more information on the bigstart command, see the bigstart manpage.
If the output is PASS, the SSL and compression hardware passed the test. If the output is FAIL, you should consider taking the system out of production to run the End-User Diagnostic (EUD) tests.

Check the packetpath

You can use the platform_diag packetpath test to check the internal paths to test the Ethernet interfaces in the system, including between the front panel switch, HSBs, processors, and more.
Warning: This test stops system daemons using bigstart stop, stops traffic to the system, and might disable some network interfaces.
  1. Log in to the command line of the system using an account with root access.
  2. Check the integrity of the internal paths.
    platform_diag packetpath
    Note: This command could take a while to complete. You can run bigstart status to see the status of each of the default services. For more information on the bigstart command, see the bigstart manpage.
If the output is PASS, the internal packet path works as expected. If the output is FAIL, you should consider taking the system out of production to run the End-User Diagnostic (EUD) tests.
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)