show [node node-id] fddi -
station station-name attribute [,attribute...]
all [attributes]
all counters
all identifiers
all status
The station-name can be either a simple name which
identifies a particular station instance, or a wildcard
which identifies multiple station instances.
Examples:
show fddi station * all
show fddi station fddi-0 communication port, station id
1 – Characteristics
o communication port
Name of the hardware port associated with this station, taken
from the corresponding argument in the create directive. You
cannot modify this characteristic.
o smt maximum version id
Highest SMT version ID this station supports. You cannot modify
this characteristic.
o smt minimum version id
Lowest SMT version ID this station supports. You cannot modify
this characteristic.
o smt version id
Currently active SMT version ID for this station. You cannot
modify this characteristic.
o station ID
SMT station ID for this station. You cannot modify this
characteristic.
o type
SMT station type for this station. You cannot modify this
characteristic.
2 – Counters
Unless stated otherwise, counts include both normal and multicast
traffic and all protocol types, service access points (SAPs), and
protocol identifiers.
o configuration changes
Number of times the internal configuration of this station
changed. (Not present in single attached stations (SAS)).
o creation time
Time at which the port was created.
o selftest failures
Total number of times a self-test of the station detected an
error.
o traces received
Number of times the ECM state machine for this station entered
the trace state due to a received trace signal.
3 – Identifier
o name
Simple name assigned to the station when it is created.
4 – Status
o last set station id
The station ID of the station that last performed an SMT Change
/Add/Remove (PMF frame) operation.
o state
Value: Off, on or loopback
Operational state of the station.
o uid
Entity's unique identifier, which is generated when the entity is
created.
5 – link
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
5.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.
5.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.
5.3 – Identifier
o index
An integer that uniquely identifies this link to the parent
station entity.
5.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.
6 – phy_port
show [node node-id] fddi -
station station-name -
phy port port-index attribute [,attribute...]
all [attributes]
all characteristics
all counters
all identifiers
all status
The station-name must be a simple name which uniquely
identifies a particular station instance. The port-index
can be either an integer or a wildcard.
OpenVMS Examples:
show fddi station fddi-0 phy port * all
show fddi station fddi-0 phy port 0 all
Tru64 UNIX Examples:
show fddi station fddi-1 phy port * all
show fddi station fddi-1 phy port 1 all
6.1 – Characteristics
o lem threshold
Value: For n, 10 to the -n th power
Link error monitor threshold.
o phy type
Type of the physical port (A, B, S, or M). This characteristic
cannot be set.
o pmd type
Type of the PDM (transceiver) for this physical port. This
characteristic cannot be set.
ANSI multimode Low power
ANSI multimode type 1 Thinwire
ANSI single mode type 2 Shielded twisted-pair
ANSI SONET Unshielded twisted-pair
6.2 – Counters
o creation time
Time at which the port was created.
o connections completed
Number of times the PHY port entered the in use state, having
completed the initialization process.
o elasticity buffer errors
Number of times the elasticity buffer function had an overflow or
underflow.
o lct rejects
Number of times a connection was rejected due to failure of the
Link Confidence Test at either end of the physical connection.
o lem rejects
Number of times an active connection was disconnected due to
rejection by the Link Error Monitor at this end of the physical
connection, or by expiration of the Noise timer.
o link errors
Total number of raw link error input events seen by the Link
Error Monitor.
6.3 – Identifier
o index
An integer that uniquely identifies this physical port to the
parent station entity.
6.4 – Status
o broken reason
Reason phy port is in broken state, or if in broken state, none.
o estimated link error rate
Default: 15 Value: 0-15
Reports the number of errors during the Link Monitor Test as a
negative power of 10. If there are no errors during the Link
Monitor Test, then the Estimated Link Error Rate is 10(-15th power).
An Estimated Link Error Rate of 15 indicates an excellent/clear
link, 14-10 is a noisy link and around 7 would indicate an
acceptable (failed) link.
o neighbor phy type
Status may be A, B, S, M or unknown.
o reject reason
Reason the phy port is in a failed or watch state. This is not
meaningful when phy port is in some other state.
LCT both Link Confidence Test failed on both sides of the
sides physical connection.
LCT protocol Neighboring physical port has been detected to
error have prematurely exited the link confidence test
(LCT).
LEM reject Link error monitor disconnected this connection
due to the error rate exceeding the LEM threshold.
local LCT Link Confidence Test failed on this end of the
physical connection.
noise reject Noise timer expired because a single noise event
lasted for more than 1.31072 ms.
none No reason.
remote LCT Link Confidence Test failed on the other end of
the physical connection.
remote Neighboring physical port broke the connection for
reject an unknown reason.
standby Physical port and its neighboring physical port
form a redundant physical connection (dual-
homing feature). In a dual-homed configuration,
the B to M connection is the higher priority
physical connection, and the A to M connection
is the standby physical connection. The standby
connection will become active if the B to M
connection is lost.
topology Neighboring physical port's physical port type is
reason an illegal match for this physical port's physical
port type.
trace in Physical port was initializing when a pc-trace
progress occurred. When a pc-trace occurs, any physical
ports that have not yet established a physical
connection are shut down to prevent the topology
from changing.
trace Physical port was momentarily disabled because it
received- received a pc-trace when its own pc-trace function
disabled was disabled. The pc-trace function is enabled by
default. The trace disable switch is not remotely
manageable.
o state
Operational state of the phy port entity (nonsettable).
broken The physical port has failed initialization tests
and is not available for use.
failed Same as waiting, except the physical port has
failed to complete the last connection attempt.
Refer to the physical port's status parameter
reject reason for the reason for connection
failure. Connection attempts will continue until
successful.
internal The physical port has been configured to
loopback internally present all transmitted symbols to
the receive interface. The network connector is
inactive. This allows internally generated test
frames to be looped back for test purposes.
in use The physical port has established a connection and
is fully operational. Communications services are
now available.
off-ready The physical port is waiting to be enabled or has
been disabled by management request.
starting The physical port has received a response from
the neighboring physical port and is exchanging
information and performing the link confidence
test (LCT) prior to completing the connection.
waiting The physical port is beginning to establish a
connection and is waiting for a response from the
neighboring physical port.
watch Same as starting, except the physical port has
failed to complete the last connection attempt.
Refer to the physical port's status parameter,
reject reason for the reason for connection
failure. Connection attempts will continue until
successful.
o uid
Entity's unique identifier, which is generated when the entity is
created.