USR Ati6 Explained
U.S. Robotics 56K FAX EXT Link Diagnostics...
Chars sent 0 Chars Received 0
Chars lost 0
Octets sent 0 Octets Received 0
Blocks sent 0 Blocks Received 0
Blocks resent 0
Retrains Requested 0 Retrains Granted 0
Line Reversals 0 Blers 0
Link Timeouts 0 Link Naks 0
Data Compression V42BIS 2048/32
Equalization Long
Fallback Enabled
Protocol LAPM/SREJ
Speed 48000/28800
V.90 Peak Speed 49333
Last Call 00:00:00
Disconnect Reason is DTR dropped
Chars sent - This field indicates the number of characters sent through the
modem's DTE interface. This field is not very important in testing, though a value of 0 is probably not a very good sign.
Chars Received - This field indicates the number of characters received
through the modem's DTE interface. This field is not very important in testing, though a value of 0 is probably not a very
good sign.
Chars lost - This field indicates the numbers of characters lost in the
Transmit Buffer due to buffer overruns. A non-zero value here may indicate a Transmit Data Flow Control problem in the
terminal. Try adjusting the modem's FIFO buffers if this is a non-zero value. It should really always be 0, and may
indicate a noise problem, but also may likely be a modem or server issue if the value is not 0.
Octets sent - This field indicates the amount of compressed data sent
by the modem. You can determine the compression ratio by dividing the number of characters sent by the number of octets
sent. Note: Octets sent may be larger than characters sent if using MNP5. MNP5 does compress the data, but it tries to
recompress the data and ends up reporting a higher amount of data sent.
Octets Received - This field indicates the amount of compressed data
sent by the modem. You can determine the compression ratio by dividing the number of characters received by the number of
octets received. Note: Octets received may be larger than characters received if using MNP5. MNP5 does compress the data,
but it tries to recompress the data and ends up reporting a higher amount of data received.
Blocks sent - This field indicates the number of blocks the Error
Control Protocol has sent. This field is not very important in testing, though a value of 0 or a value higher than
Octets sent or characters sent is probably not a very good sign.
Blocks Received - This field indicates the number of blocks the Error
Control Protocol has received. This field is not very important in testing, though a value of 0 is probably not a very
good sign. This field is not very important in testing, though a value of 0 or a value higher than Octets received or
characters received is probably not a very good sign.
Blocks resent - This field indicates the number of Error Control
Protocol blocks that the remote receiver requested and were re-sent. These requests are also counted in the Link Naks field
however is not the only type of block counted in that field. This field can be an indicator of noise problems. If this
field is in the 1000s there could be a serious issue, whereas if it is in the 100s there could be a minor issue. Too many
errors using error control is never a good sign.
Retrains Requested - When the connection quality degrades to the point
where your modem loses synch with the server a retrain is requested by your modem. This is the number of retrains that your
modem requested. If you have more than 2 of these you may have an issue with noise. If you have any over a short
connection this may also indicate an issue with noise.
Retrains Granted - These are the number of retrains actually granted by
the server from the Retrains Requested. If you have more than 2 of these you may have an issue with noise. If you have
any over a short connection this may also indicate an issue with noise.
Line Reversals - This field is for HST
Modulation. This field will not be important for purposes of determining noise through this type of testing.
Blers - This field indicates the number of errors in received Error
Control Protocol and Data blocks. A perfect connection has 0 BLERs and a good connection has less than 20/min or 1200/hour.
A connection can still be considered good with 67/min or 4020/hour, but most connections will have troubles when they reach
this point. If you have an excessive number of BLERs there could be a noise issue.
Link Timeouts - This field indicates the
number of times the Error Control Protocol received no response from the remote server. If this number is in the 100's or
higher this could indicate a noise issue.
Link Naks - This field indicates the number of
times the remote server requested a resend of one or more blocks of varying types of data. A very high number in this field
is also a bad sign. It is hard to determine however as this is the number of requests and not the number of blocks as there
can be multiple blocks of data requested in a single request.
Data Compression - This field indicates
the type of compression used for the last connection. The numbers listed are the compression dictionary size. This field
has no real bearing on determining noise.
Equalization - This field only applies to
HST connections. This field will not be important for purposes of determining noise through this type of testing.
Fallback - Disabled means that the modem did not
or is not capable of negotiation of an online fallback/speed shift. Enabled means that the modem may have or is capable of
negotiation of an online fallback/speed shift. This will unfortunately have no bearing in determining noise.
Protocol - This field indicates the error control
protocol used for the last connection. You should see SOMETHING here, if it is listed as NONE this could be poor for your
connection. Make sure to enable error control in DUN and the Modem Control Panel.
Speed - Recieve Speed/Transmit Speed.
V.90 Peak Speed - This is the highest speed
your modem attained in the last connection.
Last Call - This is how long your last call was
in hours:minutes:seconds.
Disconnect Reason - This is the reason
for your last disconnection. These reasons include:
Break Timeout: Break signal could not be processed.
DISC: The RAS sent the modem a v.42 disconnect frame, hanging up on you.
DTR dropped: Your computer disconnected.
Escape code: +++ escape code was used to disconnect.
Extra Steppe: An invalid v.42bis compression frame was received.
GSTN Cleardown: Someone dropped DTR or the disc frame became corrupted
Illegal Command Code: An invalid v.42bis compression frame was received.
Invalid Codeword: An invalid v.42bis compression frame was received.
LD received: RAS sent an MNP disconnect request.
Loop loss disconnect: Either the remote end hung up or there was so much noise the modem could no
longer communicate with the remote side.
Lost carrier: Most likely a drop due to noise, but it could have been due to the remote end hanging up.
Retransmit Limit: The modem tried to transmit a piece of data that errored out 12 times.
Rootless Tree: An invalid v.42bis compression frame was received.
SABME Timeout: The modems failed link negotiation of the 'v.42 Set Asynchronous Balance Mode Extended'.
Unable to retrain: The modem attempted to retrain several times but failed in doing so, losing connection.
XID Timeout: The modem and RAS failed to negotiate the v.42 detection phase (a.k.a. XID exchange).
This page was last modified on Saturday, 05-Feb-2011 15:13:38 EST.
|
