![]() ![]() If a mismatch is detected, the test exits with an error. Each packet is compared with its original for length and content. ![]() If the system is extremely busy, the drop tolerance should be increased. The user can set the drop tolerance between 0 percent and 99 percent. The test allows a percentage of the packets to be dropped. Some packet drops are to be expected especially on a heavily loaded system. The third phase attempts to send many packets through the loop. If the length and content of the packets do not match exactly, the test exits with an error.ģ. If a packet is returned, the result is compared to the original. If no packets are detected after five attempts, the test exits with an error. ![]() The second phase attempts to send and receive one packet. If activity is detected, serialtest exits with an error.Ģ. If no activity is detected for at least four seconds, the test proceeds to the next phase. The first phase looks for activity on the port. The synchronous test runs in three phases:ġ. The user can select the loopback paths to use and the clock rate. Data is written and read in checksum-protected packets. This mode uses the synchronous hdlc-framing interface as described in the zsh(7D) and se_hdlc(7D) man pages. Note - Synchronous mode is not supported on x86 platforms. If no errors or timeouts are detected, the rest of the data is simultaneously written and read, then compared for data integrity. The test writes and reads data through the loopback path and compares the data to the original data. You can select the loopback paths to use, the amount of data to transfer, and the baud rate to be used for the transfer. The termio(7I) interface is used for configuring port characteristics. This mode uses the asynchronous communication protocol as described in the zs(7D)and se(7D) man pages. Note - Only asynchronous testing is available on x86 platforms. Serialtest Asynchronous and Synchronous Testing Asynchronous Testing Intervention mode must be enabled to run this test. The maximum baud rate supported on x86 platforms is 115200. The internal loopback and synchronous modes of this test are not supported on x86 platforms. Note - serialtest supports x86 platforms that use the Solaris OS. The operating system shows two ports, but physically there is only one port. Note - The 16550 UART can support two devices but some systems only carry one physical port (TTYS1 or TTYB, /dev/term/b, known as COM2 in the x86 environment). The 16550 device only works in asynchronous mode. Note - serialtest supports testing the asy driver (16550 UART). However, the x86 UART driver does not support internal loopback and synchronous mode. Data is written and read in asynchronous and synchronous modes using various loopback paths. The serialtest checks the system on-board serial ports ( su, zs, zsh, se, se_hdlc, asy), and any multiterminal interface (ALM2) boards ( mcp). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |