show [node node-id] fddi -
station station-name -
link link-index attribute [,attribute...]
all [attributes]
all counters
all identifiers
all status
The station-name must be a simple name which uniquely
identifies a particular station instance. The link-index
can be either an integer or a wildcard.
OpenVMS Examples:
show fddi station fddi-0 link * all
show fddi station fddi-0 link 0 all
show fddi station fddi-0 link 0 -
requested trt, restricted token timeout
Tru64 UNIX Examples:
show fddi station fddi-1 link * all
show fddi station fddi-1 link 1 all
show fddi station fddi-1 link 1 -
requested trt, restricted token timeout
1 – Characteristics
o link address
MAC address assigned during manufacture of the communication
hardware that is associated with the station (read-only).
o requested trt
Default: 8.0 Value: 1-65535
Requested token rotation timer.
o restricted token timeout
Default: 1000 Value: 1-65535
Length limit of a restricted token dialog.
o ring purger enable
Default: True Value: True or false
Controls whether this station is eligible to be a ring purger and
should participate in the ring purger election.
o valid transmission time
Default: 3.4 Value: 1-65535
Valid transmission time.
2 – Counters
o block check errors
Number of times a received frame containing an integral number of
octets failed the FCS check.
o creation time
Time at which the station was created.
o directed beacons received
Number of times the link detected the directed beacon process.
o duplicate address test failures
Number of times the duplicate address test failed (detected that
the link address was a duplicate).
o duplicate tokens detected
Number of times the MAC address test failed (detected that the
link address was a duplicate).
o error count
Total number of frames that were in error with the E indicator
reset, indicating that the error occurred between the upstream
MAC and this one.
o fci strip errors
Number of times a frame content independent strip operation
(bridge strip) was terminated by receipt of a token.
o frame count
Total number of frames seen by this link, other than tokens.
o frame status errors
Number of times a received frame had the E indicator in error
(missing or set) and the FCS was correct.
o lost count
Counter lost count.
o multicast octets received
Number of multicast data octets that were successfully received
in multicast frames of type LLC, implementer, reserved, or SMT.
The count does not include the MAC envelope.
o multicast octets sent
Number of multicast data octets that were successfully sent in
multicast frames of type LLC, implementer, reserved, or SMT. The
count does not include the MAC envelope.
o multicast pdus received
Number of multicast frames that were successfully received of
type LLC, implementer, reserved, or SMT.
o multicast pdus sent
Number of multicast frames that were successfully sent of type
LLC, implementer, reserved, or SMT.
o octets received
Number of octets successfully received in frames of type LLC,
implementer, reserved, or SMT. The count does not include the MAC
envelope.
o octets sent
Number of octets successfully sent in frames of type LLC,
implementer, reserved, or SMT. The count does not include the
MAC envelope.
o pdu length errors
Number of times a received frame had an invalid length, either
too long or short for the type, or had an alignment error (odd
number of symbols).
o pdus received
Number of frames successfully received in frames of type LLC,
implementer, reserved, or SMT.
o pdus sent
Number of frames successfully sent in frames of type LLC,
implementer, reserved, or SMT.
o receive data overruns
Number of times the hardware lost one or more consecutive, only
partially complete incoming frames because it was unable to keep
up with the medium rate. An example is overrun of a bit or octet
FIFO queue because of inability to copy data from adapter to host
promptly. In conjunction with total frames received, provides a
measure of hardware resource and bandwidth failures.
o ring beacons initiated
Number of times the ring beacon process was initiated by this
link.
o ring initializations initiated
Number of times a ring reinitialization was initiated by this
link.
o ring initializations received
Number of times a ring reinitialization was initiated by some
other link.
o ring purge errors
Number of times the ring purger received a token while still in
the ring purge state.
o token count
Number of times a token has been seen by this link.
o transmit underruns
Number of times a transmit underrun occurred. This indicates the
transmit FIFO became empty during frame transmission.
o traces initiated
Number of times the pc trace process was initiated by this link.
o transmit failures
Number of times a transmit error, other than underrun, occurred.
This does not include errors in transmitting MAC type frames.
o unavailable link buffers
Number of times a complete, fully received frame was discarded
because no link buffer was available. In conjunction with total
frames received, provides a measure of station-buffer-related
receive problems.
o unavailable user buffers
Number of times no user buffer was available for an incoming
frame that passed all filtering for the port. These are the
buffers supplied by users on receive requests. In conjunction
with total frames received, provides a measure of user-buffer-
related receive problems.
o unrecognized individual destination pdus
Number of times a received LLC frame with an individual
destination MAC address was discarded because there was no
port with the Ethernet protocol type, SNAP protocol identifier,
or LLC SAP address enabled. Only frames containing individual
destination MAC addresses are counted.
o unrecognized multicast destination pdus
Number of times a received LLC frame with a multicast destination
MAC address was discarded because there was no port with the
Ethernet protocol type, SNAP protocol identifier, or LLC SAP
address enabled. Only frames containing multicast destination MAC
addresses are counted.
3 – Identifier
o index
An integer that uniquely identifies this link to the parent
station entity.
4 – Status
o downstream neighbor
MAC address of the downstream neighbor, if known.
o duplicate address flag
Summary output of the duplicate address test algorithm.
o frame strip mode
Current frame stripping mode of the MAC.
SA match Source address match mode of the frame stripping
algorithm matches the source address of the frame with
the MAC's MyLongAddress (MLA), and if a match is found,
the frame is removed from the token ring.
FCI The FCIS mode counts the number of frames transmitted
strip since the reception of a token, and strips equal number
of frames.
o loopback
This is true if the link has been set up to receive frames
transmitted by it. This allows loopback testing either on the
ring or with one of the PHY port loopback modes.
o negotiated trt
Negotiated token rotation timer.
o old downstream neighbor
Previous value of the downstream neighbor.
o old upstream neighbor
Previous value of the upstream neighbor.
o ring error reason
Reason code for the most recent link error.
duplicate Duplicate address algorithm detected a duplicate
address address.
detected
duplicate A duplicate token was detected on the ring.
token
detected
no error No errors have occurred on this ring.
ring init Ring initialization was initiated by this link to
initiated initialize the ring and create a token.
ring init Ring initialization was initiated by some other
received link to initialize the ring and create a token.
ring Ring beaconing process was initiated by this link.
beaconing This process in initiated as a result of serious
initiated ring failure, such as loss of signal or jabbering
station transmitting in violation of the protocol.
This indicates to other links on the LAN that
corrective action may be required.
ring purge Link received a token while performing a ring
error purge operation.
FCI strip Frame content independent strip operation was
error terminated by the receipt of a token.
ring op Ring state has been continually changing from
oscillation operational to initializing.
directed Link received particular beacon data.
beacon
received
PC trace PC-trace was initiated by this link.
initiated
PC trace PC-trace was initiated by some other link.
received
o ring latency
Current ring latency as measured by this link entity.
o ring purger state
State of the ring purger election process.
candidate The Link's Ring Purger process is participating in
the Ring Purger election algorithm as a candidate
to become the Ring Purger.
nonpurger The Link's Ring Purger process is in an idle state
listening for periodic Purger Hello frames.
off The Link's Ring Purger process is disabled.
purger The Link's Ring Purger process is performing the
function of removing no owner frames and duplicate
token from the ring. In this state, the process
transmits periodic Purger Hello frames.
o state
State of the link entity.
broken Attempt to turn the link on failed the
initialization test, or link was on, but failure
was detected.
off-ready FDDI Data Link communication services are not
available.
off-fault State entered when a link entity detects
recovery conditions that indicate faulty ring.
on-ring init Physical layer service is available and the link
entity enabled.
on-ring run Link detected that the Ring Initialization has
been successfully completed and the ring is
operational.
o uid
Entity's unique identifier, which is generated when the entity is
created.
o upstream neighbor
MAC address of the upstream neighbor, if known.
o upstream neighbor duplicate address flag
Default: false Value: True or false
Upstream neighbor's reported result of its duplicate address
test.