Lucent Technologies R5SI Computer Hardware User Manual


  Open as PDF
of 2643
 
DEFINITY Enterprise Communications Server Release 5
Maintenance and Test for R5vs/si
555-230-123
Issue 1
April 1997
Maintenance Commands and Trouble-Clearing Aids
Page 8-474status link
8
Level 2 I-frames
retransmitted
This is a count of the number of frames that have been
retransmitted in LAPD (Link Access Procedure D) or
X.25 layer 2. In general, this is a measure of link quality.
This count, which could indicate a very noisy link or
synchronization problem, will increment normally if a
Hot Start PEI is done locally.
Level 2 Reset (SABM) This is the number of X.25 SABMs or LAPD SABMs that
have been transmitted. Since SABMs are used to
establish links, every time this count is incremented a
link establishment attempt has failed. If the link is
currently in-service and the count is non-zero after
having been previously cleared by the "clear link
link-no" command, then this condition indicates that the
link has gone down in that interval. Check the Hardware
Error Log for additional information.
Invalid Frame Count This is the number of invalid frames that have been
received. This count is a measure of the link quality and
could indicate a very noisy link or a synchronization
problem. This might increment normally if a Hot Start
PEI is done locally. If an administration error exists, this
counter could be incrementing along with the Level 2
Reset counter. This counter may be incremented by
message retransmissions.
Far-End SABM(E)/DM This value is informational only and no action is
necessary. It is one of eight counters that tell the history
from the last "clear link" command of why the link went
down. In this case, the link went down because the
switch received a SABM from the Far-End.
Protocol Error Detected This value is informational only and no action is
necessary. It is one of eight counters that tell the history
from the last "clear link" command of why the link went
down. In this case, the link went down because the PI
circuit pack detected a Layer 2 protocol error in its
communications with the Far-End of the link.