IBM 3745 Problem Determination Manual page 48

o
0 ,
I
o
o
o
Table
1-1
(Page
3
of
5).
Token-Ring External Error Codes
External
Error
Codes
OF
10
11
12
13
Error Description
Physical link INOP due to permanent
beaconing
There is a hard error on the token
ring which has not been recovered
by the beaconing process. Data
transmission to the token ring has
been suspended and all logical links
associated with this physical link
have been I NOPed. The physical
link will remain active and inserted
in the ring and report beaconing
recovery when that occurs
Physical link INOP due to loss of
connection
When the TIC attempted to insert
onto the ring during TIC open time,
the TIC detected a loss of signal
from the ring known as a lobe
media error. The physical link as
well as all of its associated logical
·Iinks are INOPed .. This indicates a
loose or disconnected. cable
between the TIC and the
Multistation Access Unit (MAU). It
may also be a defective cable or a
defective MAU.
Physical link INOP due to
auto-removal process
The TIC removed itself from the
ring after it detected an error
during a self-test. The self-test was
performed as part of the beaconing
process. The physical link as well
as all of its associated logical links
are I.NOPed.
First station inserted on the ring
(ring status: 'SINGLE STATION').
There are no other stations
connected on the ring.
Physical link recovery - beacon
process ended
The token ring has recovered after
a beacon process.
14 Unused
15 Unused
Probable Cause
Token ring LAN
Loose cable
connection
TIC
None
None
User Action
Contact the token ring operator or
administrator to;determine the
cause of the permanent beaconing
condition.
Check all connections. Try to
re-activate the physical link after
checking the connections. If it still
fails, connect the cable to another
plug on the MAU. If that does not
work, replace the cable. If the
problem persists, contact the local
token ring LAN administrator.
This may not be a persistent
problem, so try to re-activate the
physical link and if the problem
persists, contact an IBM service
representative.
If other station are known to be on
the ring, see the Token-Ring
Network Problem Determination
Guide.· Otherwise, no action.
None
Chapter 1. Alarms and Alerts
1-31