| dot5IfIndex |
.1.3.6.1.3.4.1.1.1 |
|
The value of this object identifies the
802.5 interface for which this entry
contains management information. The
value of this object for a particular
interface has the same value as the
ifIndex object, defined in [4,6],
for the same interface.
|
| dot5Commands |
.1.3.6.1.3.4.1.1.2 |
|
When this object is set to the value of
open(2), the station should go into the
open state. The progress and success of
the open is given by the values of the
objects dot5RingState and
dot5RingOpenStatus.
When this object is set to the value
of reset(3), then the station should do
a reset. On a reset, all MIB counters
should retain their values, if possible.
Other side affects are dependent on the
hardware chip set.
When this object is set to the value
of close(4), the station should go into
the stopped state by removing itself
from the ring.
Setting this object to a value of
no-op(1) has no effect.
When read, this object always has a
value of no-op(1).
|
| dot5RingStatus |
.1.3.6.1.3.4.1.1.3 |
|
The current interface status which can
be used to diagnose fluctuating problems
that can occur on token rings, after a
station has successfully been added to
the ring.
Before an open is completed, this
object has the value for the 'no status'
condition. The dot5RingState and
dot5RingOpenStatus objects provide for
debugging problems when the station
can not even enter the ring.
The object's value is a sum of
values, one for each currently applicable
condition. The following values are
defined for various conditions:
0 = No Problems detected
32 = Ring Recovery
64 = Single Station
256 = Remove Received
512 = reserved
1024 = Auto-Removal Error
2048 = Lobe Wire Fault
4096 = Transmit Beacon
8192 = Soft Error
16384 = Hard Error
32768 = Signal Loss
131072 = no status, open not completed.
|
| dot5RingState |
.1.3.6.1.3.4.1.1.4 |
|
The current interface state with respect
to entering or leaving the ring.
|
| dot5RingOpenStatus |
.1.3.6.1.3.4.1.1.5 |
|
This object indicates the success, or the
reason for failure, of the station's most
recent attempt to enter the ring.
|
| dot5RingSpeed |
.1.3.6.1.3.4.1.1.6 |
|
The ring's bandwidth.
|
| dot5UpStream |
.1.3.6.1.3.4.1.1.7 |
|
The MAC-address of the up stream neighbor
station in the ring.
|
| dot5ActMonParticipate |
.1.3.6.1.3.4.1.1.8 |
|
If this object has a value of true(1) then
this interface will participate in the
active monitor selection process. If the
value is false(2) then it will not.
Setting this object might not have an
effect until the next time the interface
is opened.
|
| dot5Functional |
.1.3.6.1.3.4.1.1.9 |
|
The bit mask of all Token Ring functional
addresses for which this interface will
accept frames.
|
| dot5StatsIfIndex |
.1.3.6.1.3.4.2.1.1 |
|
The value of this object identifies the
802.5 interface for which this entry
contains management information. The
value of this object for a particular
interface has the same value as the
ifIndex object, defined in [4,6], for
the same interface.
|
| dot5StatsLineErrors |
.1.3.6.1.3.4.2.1.2 |
|
This counter is incremented when a frame
or token is copied or repeated by a
station, the E bit is zero in the frame
or token and one of the following
conditions exists: 1) there is a
non-data bit (J or K bit) between the SD
and the ED of the frame or token, or
2) there is an FCS error in the frame.
|
| dot5StatsBurstErrors |
.1.3.6.1.3.4.2.1.3 |
|
This counter is incremented when a station
detects the absence of transitions for five
half-bit timers (burst-five error).
|
| dot5StatsACErrors |
.1.3.6.1.3.4.2.1.4 |
|
This counter is incremented when a station
receives an AMP or SMP frame in which A is
equal to C is equal to 0, and then receives
another SMP frame with A is equal to C is
equal to 0 without first receiving an AMP
frame. It denotes a station that cannot set
the AC bits properly.
|
| dot5StatsAbortTransErrors |
.1.3.6.1.3.4.2.1.5 |
|
This counter is incremented when a station
transmits an abort delimiter while
transmitting.
|
| dot5StatsInternalErrors |
.1.3.6.1.3.4.2.1.6 |
|
This counter is incremented when a station
recognizes an internal error.
|
| dot5StatsLostFrameErrors |
.1.3.6.1.3.4.2.1.7 |
|
This counter is incremented when a station
is transmitting and its TRR timer expires.
This condition denotes a condition where a
transmitting station in strip mode does not
receive the trailer of the frame before the
TRR timer goes off.
|
| dot5StatsReceiveCongestions |
.1.3.6.1.3.4.2.1.8 |
|
This counter is incremented when a station
recognizes a frame addressed to its
specific address, but has no available
buffer space indicating that the station
is congested.
|
| dot5StatsFrameCopiedErrors |
.1.3.6.1.3.4.2.1.9 |
|
This counter is incremented when a station
recognizes a frame addressed to its
specific address and detects that the FS
field A bits are set to 1 indicating a
possible line hit or duplicate address.
|
| dot5StatsTokenErrors |
.1.3.6.1.3.4.2.1.10 |
|
This counter is incremented when a station
acting as the active monitor recognizes an
error condition that needs a token
transmitted.
|
| dot5StatsSoftErrors |
.1.3.6.1.3.4.2.1.11 |
|
The number of Soft Errors the interface
has detected. It directly corresponds to
the number of Report Error MAC frames
that this interface has transmitted.
Soft Errors are those which are
recoverable by the MAC layer protocols.
|
| dot5StatsHardErrors |
.1.3.6.1.3.4.2.1.12 |
|
The number of times this interface has
detected an immediately recoverable
fatal error. It denotes the number of
times this interface is either
transmitting or receiving beacon MAC
frames.
|
| dot5StatsSignalLoss |
.1.3.6.1.3.4.2.1.13 |
|
The number of times this interface has
detected the loss of signal condition from
the ring.
|
| dot5StatsTransmitBeacons |
.1.3.6.1.3.4.2.1.14 |
|
The number of times this interface has
transmitted a beacon frame.
|
| dot5StatsRecoverys |
.1.3.6.1.3.4.2.1.15 |
|
The number of Claim Token MAC frames
received or transmitted after the interface
has received a Ring Purge MAC frame. This
counter signifies the number of times the
ring has been purged and is being recovered
back into a normal operating state.
|
| dot5StatsLobeWires |
.1.3.6.1.3.4.2.1.16 |
|
The number of times the interface has
detected an open or short circuit in the
lobe data path. The adapter will be closed
and dot5RingState will signify this
condition.
|
| dot5StatsRemoves |
.1.3.6.1.3.4.2.1.17 |
|
The number of times the interface has
received a Remove Ring Station MAC frame
request. When this frame is received
the interface will enter the close state
and dot5RingState will signify this
condition.
|
| dot5StatsSingles |
.1.3.6.1.3.4.2.1.18 |
|
The number of times the interface has
sensed that it is the only station on the
ring. This will happen if the interface
is the first one up on a ring, or if
there is a hardware problem.
|
| dot5StatsFreqErrors |
.1.3.6.1.3.4.2.1.19 |
|
The number of times the interface has
detected that the frequency of the
incoming signal differs from the expected
frequency by more than that specified by
the IEEE 802.5 standard, see chapter 7
in [10].
|
| dot5TimerIfIndex |
.1.3.6.1.3.4.5.1.1 |
|
The value of this object identifies the
802.5 interface for which this entry
contains timer values. The value of
this object for a particular interface
has the same value as the ifIndex
object, defined in [4,6], for the same
interface.
|
| dot5TimerReturnRepeat |
.1.3.6.1.3.4.5.1.2 |
|
The time-out value used to ensure the
interface will return to Repeat State, in
units of 100 micro-seconds. The value
should be greater than the maximum ring
latency.
Implementors are encouraged to provide
read-write access to this object if that is
possible/useful in their system, but giving
due consideration to the dangers of
write-able timers.
|
| dot5TimerHolding |
.1.3.6.1.3.4.5.1.3 |
|
Maximum period of time a station is
permitted to transmit frames after capturing
a token, in units of 100 micro-seconds.
Implementors are encouraged to provide
read-write access to this object if that is
possible/useful in their system, but giving
due consideration to the dangers of
write-able timers.
|
| dot5TimerQueuePDU |
.1.3.6.1.3.4.5.1.4 |
|
The time-out value for enqueuing of an SMP
PDU after reception of an AMP or SMP
frame in which the A and C bits were
equal to 0, in units of 100
micro-seconds.
Implementors are encouraged to provide
read-write access to this object if that is
possible/useful in their system, but giving
due consideration to the dangers of
write-able timers.
|
| dot5TimerValidTransmit |
.1.3.6.1.3.4.5.1.5 |
|
The time-out value used by the active
monitor to detect the absence of valid
transmissions, in units of 100
micro-seconds.
Implementors are encouraged to provide
read-write access to this object if that is
possible/useful in their system, but giving
due consideration to the dangers of
write-able timers.
|
| dot5TimerNoToken |
.1.3.6.1.3.4.5.1.6 |
|
The time-out value used to recover from
various-related error situations [9].
If N is the maximum number of stations on
the ring, the value of this timer is
normally:
dot5TimerReturnRepeat + N*dot5TimerHolding.
Implementors are encouraged to provide
read-write access to this object if that is
possible/useful in their system, but giving
due consideration to the dangers of
write-able timers.
|
| dot5TimerActiveMon |
.1.3.6.1.3.4.5.1.7 |
|
The time-out value used by the active
monitor to stimulate the enqueuing of an
AMP PDU for transmission, in units of
100 micro-seconds.
Implementors are encouraged to provide
read-write access to this object if that is
possible/useful in their system, but giving
due consideration to the dangers of
write-able timers.
|
| dot5TimerStandbyMon |
.1.3.6.1.3.4.5.1.8 |
|
The time-out value used by the stand-by
monitors to ensure that there is an active
monitor on the ring and to detect a
continuous stream of tokens, in units of
100 micro-seconds.
Implementors are encouraged to provide
read-write access to this object if that is
possible/useful in their system, but giving
due consideration to the dangers of
write-able timers.
|
| dot5TimerErrorReport |
.1.3.6.1.3.4.5.1.9 |
|
The time-out value which determines how
often a station shall send a Report Error
MAC frame to report its error counters,
in units of 100 micro-seconds.
Implementors are encouraged to provide
read-write access to this object if that is
possible/useful in their system, but giving
due consideration to the dangers of
write-able timers.
|
| dot5TimerBeaconTransmit |
.1.3.6.1.3.4.5.1.10 |
|
The time-out value which determines how
long a station shall remain in the state
of transmitting Beacon frames before
entering the Bypass state, in units of
100 micro-seconds.
Implementors are encouraged to provide
read-write access to this object if that is
possible/useful in their system, but giving
due consideration to the dangers of
write-able timers.
|
| dot5TimerBeaconReceive |
.1.3.6.1.3.4.5.1.11 |
|
The time-out value which determines how
long a station shall receive Beacon
frames from its downstream neighbor
before entering the Bypass state, in
units of 100 micro-seconds.
Implementors are encouraged to provide
read-write access to this object if that is
possible/useful in their system, but giving
due consideration to the dangers of
write-able timers.
|
