Table of Contents
Advertisement
Discarded Outbound Frames
The following discard reasons are defined for outbound frames:
•
Invalid Frame Header Tag
The frame had an invalid internal frame header tag (note that this internal
frame header tag is not the same as the VLAN tag).
•
Unknown Ring Number
An explorer frame was discarded because one or two ring numbers are required
for the RIF expansion and at least one of the required ring numbers was
unknown. The ring number must either be configured for the CRF or learned
from an incoming explorer frame.
•
Inactive Virtual Port
The virtual port was disabled.
•
Blocked Virtual Port
The virtual port was not in forwarding state. The blocked state may have been
permanent (because the spanning tree protocol detected multiple parallel
paths) or transient (during network topology changes).
•
Filtered By DSAP Filter
A frame was discarded because of a protocol (DSAP or protocol type) filter.
•
Frame Too Large
The frame was larger than the maximum frame size, which has been
configured for the virtual port. Please refer to the table of maximum frame
sizes in Chapter 3, section "Virtual Port Configuration" on page 18.
•
Invalid Route
An explorer frame was not transmitted because the ring number of the HSTR
port appears earlier than the last ring number in the RIF.
For the following error conditions, the transmission is aborted:
•
Unknown Ring Number
•
Frame Too Large
•
Invalid Route
This is because transmission has already begun at the time the error condition is
detected. The receiver on the other end will therefore count these frames as RX
aborts.
CrossFire 8650/8651 UEM Guide to Operation, DOC-7090 v. 1.0
33
4. Statistics
Advertisement
Table of Contents
