Filter
Top Products
Troubleshooting
6-6 Vanguard Multiport 4520CP Controller User’s Guide
Troubleshooting with mset (async only)
You can run mset when you are receiving data corruption errors on incoming data,
such as
• Receiver Overruns: This occurs when the chip’s FIFO is full, more data has
arrived, and the system could not respond to the interrupt fast enough.
• Frame Errors: The data received was missing a stop bit.
• Parity Errors: The parity check was wrong.
• Dropped Characters: The OS did not have enough memory to handle the incom-
ing data.
To run mset
3. Log on as root
4. Change to the appropriate directory:
system# cd /opt/AURAase
5. Type the following:
system# ./mset <device_name> -statschk
This prints a list of board/port numbers that have detected receiver overruns,
frame errors, parity errors, or dropped characters. The output looks similar to
the following:
The following channels have detected errors:
Board 1, port: 3, 4
Board 2, port: 2
This indicates that the port labeled “3” and the port labeled “4” of the first board
has detected errors and the port labeled “2” on the second board has detected
errors.
6. To report the error statistics for the specified asynchronous port, enter:
system# ./mset <device_name> -stats
This example shows 5 characters received with parity errors. It also shows that
the port received 3021 characters and transmitted 21 characters.
receiver overruns: <0>
receiver frame errors: <0>
receiver parity errors: <5>
receiver chars dropped: <0>
received chars: <3021>
transmitted chars: <21>