Specifications

View Menu
40
LICENSED MATERIAL - PROPERTY OF FUJITSU SOFTWARE TECHNOLOGY CORPORATION
RxCrcErr Receipt of CRC errors. Receipt of CRC errors can be caused by the following con-
ditions:
• Internal problems on a remote device.
• Link data corruption caused by a generous number of
InvTxWords on the same line.
• Bad cabling or other electromagnetic interference.
RxFIFOOverRun Receipt of more data than
FIFO has room for.
Contact an authorized service representative if FIFO errors
occur. Any FIFO problem must be attended to immedi-
ately. Internal adjustment will be necessary to correct this
indication.
RxFrameTooLong Receipt of a frame longer
than the set maximum.
This occurrence can be caused by a discrepancy in maxi-
mum settings; the switch setting for maximum frames may
be smaller than the device setting. In this case, the counter
increments in large bursts as full device frames are sent.
Note that not all frames are full frames. For example, com-
mand type frames are usually much smaller than full
frames. Device discovery may complete and appear to
work until large frames are passed.
RxFrameTooShort Receipt of a truncated
short frame.
Truncated short frames should occur infrequently. Possible
causes follow:
• Protocol reset.
• Remote device failure.
• Extreme noise or external disruption (unlikely).
RxLinkResets Receipt of N_Port LR
primitives.
A device has sent N_Port LR primitives to the switch, indi-
cating that protocol errors are occurring. This is a Switch
to device peer level indicating some type of recovery
needed. If frequent resets occur, then a possible credit mis-
match may be a cause. Link failure is also recorded in mes-
sage logs, as well as Trap if set up. For cascade switch
ports in one of the Stealth Modes, a N_Port LR primitive
indicates that a target device has passed a LIP (Loop Ini-
tialization Primitive) propagation to initiator device(s);
that is, the LIP If Storage Added option (in Softek SAN-
View) was enabled.
RxMissingDelims Received FIFO data has a
frame that is not properly
delimited by SOF or EOF.
Missing delimiters in received FIFO data can be caused by
the following conditions:
• Recover event to a very slow or delinquent remote
device (most common).
• A Rcv FIFO overrun.
• Internal corruption or faulty firmware (least common).
Port Link Statistics Columns
Port Link
Statistics
Columns
Occurrences being
Counted
Notes