Filter
Top Products
6
6-18 TCP/IP Ethernet Communications User’s Manual – January 1996
GFK-1004B
Table 6-10. Exception Log Event Codes - Continued
Log Event
Code Possible Cause and Resolution
Event “c”
LLC events
This event is logged when the LLC layer encounters an unexpected condition.
Entry 2 of the logged event contains the error code as shown below.
102 “LAN Transceiver Fault; Attempting Recovery”:
Either the Transceiver or Transceiver cable failed or became disconnected.
Reattach the cable or replace the Transceiver or cable. If SQEErr is
incrementing but LostCarr is not, the Transceiver SQE–test switch may be
set incorrectly. Transceivers used on GEnet must have the IEEE 802.3
SQE_TEST enabled. Use the TALLY L cmd to distinguish whether the SQE
test, done on each transmitted frame, failed (SQEErr) or the transceiver lost
carrier while transmitting (LostCarr). Online operation should resume
within 10 seconds after repair.
103 “LAN Data Memory Exhausted – Check Parms; Resuming”:
The MAC device discarded a receive frame because there was no buffer to
receive the frame into. More input buffers should be allocated to the MAC
by increasing the parameter lrxringlen. The TALLY L cmd will distinguish
whether there were simply no receive buffers (MisdPack) or an excessively
long frame that required chaining of multiple buffers (RbufErr).
105 “LAN Controller Tx Underflow; Attempting Recovery”:
During transmission, the MAC was unable to get data from memory
quickly enough. This indicates a LAN Controller design flaw; it should not
occur. This error may cause loss of both tx and rx messages that are in
process, since the MAC must be reinitialized (done automatically). Online
operation should resume within 10 seconds after repair.
106 “Bad Remote Application Request; Discarded Request”:
An incoming frame was received that exceeded the size specified by the
parameter, lmaxdb. For frame types other than TEST frames, the frame was
discarded; for TEST frames, the data within the frame was discarded and
the frame was processed without data. Check the remote (sending) station
for correct frame length. If the local station must correctly receive frames
of large size, it will be necessary to increase the parameters lmaxdb and
bbuff4 and possibly reallocate data memory via balloc1,balloc2, balloc3, and
balloc4. Consult GE Fanuc if you need assistance.
107 “Bad Remote Application Request; Discarded Request ”:
An unsolicited XID response frame was received. This can be caused by a
protocol error in a remote station.
108 “Bad Remote Application Request; Discarded Request”:
An unsolicited TEST response frame was received. This is usually caused
when a remote station responds too slowly to a TEST Station Manager
command from the reporting station. Increase the value of the TEST
<sch> parameter. If the problem persists and the reporting station is not
sending a TEST cmd, then some remote station on the network is
generating a protocol error.