The FDDI module implements one of multiple possible Link level/Network
level modules in the OSI layered architecture model.
Fiber Distributed Data Interface FDDI is the basis for the second
generation of network interconnect architecture for Digital. The FDDI
module implements one of the multiple possible Link level/Physical level
modules in the OSI layered architecture model. The FDDI Physical level
includes high-speed, 125 megabaud, fiber optic links which may be many
kilometers in length. The FDDI Link level provides a high bandwidth,
100 megabits per second local area network LAN, and uses the ANSI
standard FDDI Token Ring.
The hierarchical relationship of the entities that constitute the FDDI
module:
FDDI
Port
Station
Link
Phy Port
The FDDI module incorporates the functions and operations defined in the
ANSI FDDI Token Ring Media Access Control MAC, the ANSI FDDI Token Ring
Physical Layer Protocol PHY, FDDI Physical Layer Medium Dependent PMD,
Station Management SMT specifications, parts of the ISO 8802-1 IEEE 802.1
Addressing, Internetworking and Network Management, and parts of the ISO
8802-2 IEEE 802.2 Logical Link Control LLC specifications.
The FDDI entity is the top-level entity in the hierarchy of entities
belonging to the FDDI module.
1 – character
VERSION
Version number of the FDDI architecture specification to which the
implementation conforms. You cannot modify this characteristic.
2 – station
An FDDI Station entity represents an access point to the service offered by the FDDI module. The FDDI data link can be monitored and controlled through DNA network management.
2.1 – character
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.
SMT MAXIMUM VERSION ID
Highest SMT version ID this station supports. You cannot modify
this characteristic.
SMT MINIMUM VERSION ID
Lowest SMT version ID this station supports. You cannot modify this
characteristic.
SMT STATION ID
SMT station ID for this station. You cannot modify this
characteristic.
SMT VERSION ID
Currently active SMT version ID for this station. You cannot modify
this characteristic.
TYPE
SMT station type for this station. You cannot modify this
characteristic.
2.2 – counters
Unless stated otherwise, counts include both normal and multicast traffic
and all protocol types, service access points SAPs, and protocol
identifiers.
CONFIGURATION CHANGES
Number of times the internal configuration of this station changed.
Not present in single attached stations SAS.
SELFTEST FAILURES
Total number of times a self-test of the station detected an error.
TRACES RECEIVED
Number of times the ECM state machine for this station entered the
trace state due to a received trace signal.
2.3 – status
LAST SET STATION ID
The station ID of the station that last performed an SMT
Change/Add/Remove PMF frame operation.
STATE
Operational state of the station.
3 – sta_link
The FDDI Station Link entity is a subentity of the FDDI Station entity. The FDDI Station link subentity provides the management view of LLC and the FDDI MAC. FDDI allows stations to be either single MAC or dual MAC and therefore there can be up to two link subentities for each station. In most cases, a station has at least one link entity. Concentrators may have no link entity and are not addressable on the FDDI, though they may be using other communications channels.
3.1 – character
LINK ADDRESS
MAC address assigned during manufacture of the communication
hardware that is associated with the station read-only.
REQUESTED TRT
Default: None Value: 8
Requested token rotation timer.
RESTRICTED TOKEN TIMEOUT
Default: None Value: 1000
Length limit of a restricted token dialog.
RING PURGER ENABLE
Default: None Value: Boolean
Controls whether this station is eligible to be a ring purger and
should participate in the ring purger election.
VALID TRANSMISSION TIME
Default: None Value: 3.4
Valid transmission time.
3.2 – counters
BLOCK CHECK ERRORS
Number of times a received frame containing an integral number of
octets failed the FCS check.
DIRECTED BEACONS RECEIVED
Number of times the link detected the directed beacon process.
DUPLICATE ADDRESS TEST FAILURES
Number of times the duplicate address test failed detected that the
link address was a duplicate.
DUPLICATE TOKENS DETECTED
Number of times the MAC address test failed detected that the link
address was a duplicate.
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.
FCI STRIP ERRORS
Number of times a frame content independent strip operation bridge
strip was terminated by receipt of a token.
FRAME COUNT
Total number of frames seen by this link, other than tokens.
FRAME STATUS ERRORS
Number of times a received frame had the E indicator in error
missing or set and the FCS was correct.
LOST COUNT
Counter lost count.
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.
MULTICAST OCTETS SENT
Number of multicast data octets that were successfully sent in
multicast frames ot type LLC, implementer, reserved, or SMT.
The count does not include the MAC envelope.
MULTICAST PDUS RECEIVED
Number of multicast frames that were successfully received of type
LLC, implementer, reserved, or SMT.
MULTICAST PDUS SENT
Number of multicast frames that were successfully sent of type LLC,
implementer, reserved, or SMT.
OCTETS RECEIVED
Number of octets successfully received in frames of type LLC,
implementer, reserved, or SMT. The count does not include the MAC
envelope.
OCTETS SENT
Number of octets successfully sent in frames of type LLC,
implementer, reserved, or SMT. The count does not include the MAC
envelope.
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.
PDUS RECEIVED
Number of frames successfully received in frames of type LLC,
implementer, reserved, or SMT.
PDUS SENT
Number of frames successfully sent in frames of type LLC,
implementer, reserved, or SMT.
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.
RING BEACONS INITIATED
Number of times the ring beacon process was initiated by this link.
RING INITIALIZATIONS INITIATED
Number of times a ring reinitialization was initiated by this link.
RING INITIALIZATIONS RECEIVED
Number of times a ring reinitialization was initiated by some other
link.
RING PURGE ERRORS
Number of times the ring purger received a token while still in the
ring purge state.
TOKEN COUNT
Number of times a token has been seen by this link.
TRACES INITIATED
Number of times the pc_trace process was initiated by this link.
TRANSMIT FAILURES
Number of times a transmit error, other than underrun, occurred.
This does not include errors in transmitting MAC type frames.
TRANSMIT UNDERRUNS
Number of times a transmit underrun occurred. This indicates the
transmit FIFO became empty during frame transmission.
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.
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.
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.
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.3 – status
DOWNSTREAM NEIGHBOR
MAC address of the downstream neighbor, if known.
DUPLICATE ADDRESS FLAG
Summary output of the duplicate address test algorithm.
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 STRIP - The FCIS mode counts the number of frames
transmitted since the reception of a token, and
strips equal number of frames.
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.
NEGOTIATED TRT
Negotiated token rotation timer.
OLD DOWNSTREAM NEIGHBOR
Previous value of the downstream neighbor.
OLD UPSTREAM NEIGHBOR
Previous value of the upstream neighbor.
RING ERROR REASON
Reason code for the most recent link error.
DIRECTED BEACON RECEIVED - Link received particular beacon data.
DUPLICATE ADDRESS DETECTED - Duplicate address algorithm detected a
duplicate address.
DUPLICATE TOKEN DETECTED - A duplicate token was detected on the
ring.
FCI STRIP ERROR - Frame content independent strip
operation was terminated by the
receipt of a token.
NO ERROR - No errors have occurred on this ring.
PC TRACE INITIATED - PC-trace was initiated by this link.
PC TRACE RECEIVED - PC-trace was initiated by some other
link.
RING BEACONING INITIATED - Ring beaconing process was initiated by
this link. This process in initiated as
a result of serious 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 INIT INITIATED - Ring initialization was initiated by
this link to initialize the ring and
create a token.
RING INIT RECEIVED - Ring initialization was initiated by
some other link to initialize the ring
and create a token.
RING OP OSCILLATION - Ring state has been continually changing
from operational to initializing.
RING PURGE ERROR - Link received a token while performing a
ring purge operation.
RING LATENCY
Current ring latency as measured by this link entity.
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.
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.
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.
OFF-FAULT RECOVERY - State entered when a link entity detects
conditions that indicate faulty ring.
UPSTREAM NEIGHBOR ADDRESS
MAC address of the upstream neighbor, if known.
UPSTREAM NEIGHBOR DUPLICATE ADDRESS FLAG
Upstream neighbor's reported result of its duplicate address test.
4 – st_phy_prt
An FDDI Station PHY Port entity provides the management view of the FDDI Station PHY Port and the FDDI pmd. Each station has at least one PHY port and a concentrator is a device that has at least one phy port of type M. A dual-attached station or dual-attached concentrator has a phy port type A and type B. A single-attached station has a phy port of type B.
4.1 – character
LEM THRESHOLD
Link error monitor threshold.
PHY TYPE
Type of the physical port A, B, S, or M. This characteristic cannot
be set.
PMD TYPE
Type of the PMD transceiver for this physical port. This
characteristic cannot be set.
ANSI SONET - unshielded twisted-pair
ANSI multimode - low power
ANSI multimode type 1 - thinwire
ANSI single mode type 2 - shielded twisted-pair
4.2 – counter
CONNECTIONS COMPLETED
Number of times the PHY port entered the in use state, having
completed the initialization process.
ELASTICITY BUFFER ERRORS
Number of times the elasticity buffer function had an overflow or
underflow.
LCT REJECTS
Number of times a connection was rejected due to failure of the Link
Confidence Test at either end of the physical connection.
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.
LINK ERRORS
Total number of raw link error input events seen by the Link Error
Monitor.
4.3 – status
BROKEN REASON
Reason phy port is in broken state, or if in broken state, none.
ESTIMATED LINK ERROR RATE
Link error monitor current estimate of error rate.
NEIGHBOR PHY TYPE
Status may be A, B, S, M or unknown.
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.
NONE - No 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.
LOCAL LCT - Link Confidence Test failed on this end
of the physical connection.
REMOTE LCT - Link Confidence Test failed on the other
end of the physical connection.
LEM REJECT - Error monitor disconnected this connection
due to the error rate exceeding the LEM
threshold.
NOISE REJECT - Noise timer expired because a single noise event
lasted for more than 1.31072 ms.
REMOTE REJECT - Neighboring physical port broke the
connection for an unknown reason.
LCT BOTH SIDES - Link Confidence Test failed on both sides
of the physical connection.
TOPOLOGY REASON - Neighboring physical port's physical port
type is an illegal match for this physical
port's physical port type.
TRACE IN PROGRESS - Physical port was initializing when a
pc-trace 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.
LCT PROTOCOL ERROR - Neighboring physical port has been
detected to have prematurely exited the
link confidence test LCT.
TRACE RECEIVED-DISABLED - Physical port was momentarily disabled
because it received a pc-trace when its
own pc-trace function was disabled. The
pc-trace function is enabled by default.
The trace disable switch is not remotely
manageable.
STATE
Operational state of the phy port entity nonsettable.
IN USE - The physical port has established a connection
and is fully operational. Communications
services are now available.
BROKEN - The physical port has failed initialization
tests and is not available for use.
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.
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.
WAITING - The physical port is beginning to establish a
connection and is waiting for a response from
the neighboring physical port.
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.
OFF-READY - The physical port is waiting to be enabled or
has been disabled by management request.
INTERNAL LOOPBACK - The physical port has been configured to
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.
5 – port
An FDDI Port entity represents an access point to the service offered by the FDDI module. A client transmits and receives data through a port. Ports are created and deleted by client use of open and close service interface procedures.
5.1 – counters
MULTICAST OCTETS RECEIVED
Number of multicast user data octets successfully received and
available to the data-link user.
MULTICAST OCTETS SENT
Number of multicast user data octets successfully transmitted using
the port.
MULTICAST PDUS RECEIVED
Number of multicast frames successfully received and available to
the data-link user.
MULTICAST PDUS SENT
Number of multicast frames successfully transmitted using the port.
OCTETS RECEIVED
Number of user data octets successfully received and available to
the data-link user.
OCTETS SENT
Number of user data octets successfully transmitted using the port.
PDUS RECEIVED
Number of frames successfully received and available to the data
link user.
PDUS SENT
Number of frames successfully transmitted using the port.
UNAVAILABLE USER BUFFERS
Number of times no user buffer was available at the port for an
incoming frame.
5.2 – status
CLIENT
Name specified by the data link when the port is opened.
ETHERNET PROTOCOL TYPES
Set of Ethernet protocol types that are recognized for this port.
Protocol types for a port may be enabled and disabled by the user at
any time during the port's existence.
LENGTH PRESENT
Indicates whether the data link is to add a length field on
transmit, and both assume the presence of and remove the length
field on receive for Ethernet frames. This attribute is irrelevant
for ISO 8802-3 formatted frames because the length field is always
present. This is specified by the user when the port is opened.
The value true means length fields are added and removed by the
data link.
LINK
Name of the link subentity associated with this port, specified by
the user when the port is opened.
LLC SAP ADDRESSES
Set of SNAP protocol identifiers that are recognized for this port.
LLC SAP addresses for a port may be enabled and disabled by the user
at any time during the port's existence.
LLC SERVICE
LLC PDU processing the data-link user requires from the port,
specified by the user when the port is opened.This is either LLC
Class 1, where the entire LLC protocol is handled by the data link,
or user-supplied LLC, where the user is responsible for operating
part of the LLC protocol.
MAC ADDRESSES
Set of individual and multicast MAC addresses that are recognized
for this port. MAC addresses for a port may be enabled and
disabled by the user at any time during the port's existence.
RECEIVE MODE
Indicates if the port is to receive all frames regardless of format,
Ethernet protocol type, SNAP protocol identifier, LLC SAP address,
or MAC address. Promiscuous receipt is enabled and disabled by the
user. Support of promiscuous mode is optional.
SNAP PROTOCOL IDENTIFIERS
Set of SNAP protocol identifiers that are recognized for this port.
Protocol identifiers for a port may be enabled and disabled by the
user at any time during the port's existence.
TYPE
Type of port LLC or SMT.