CHIPDOT5-MIB
Detailed view of the defined objects, syntax rules, and hierarchical paths.
126
Objects
Active
Status
2
Dependencies
Imported Objects
Objects
126 total| Object Name |
|---|
chipcom OBJECT IDENTIFIER .1.3.6.1.4.1.49 |
RFC1155-SMI Unknown .1.3.6.1.4.1.49 |
chipmib02 OBJECT IDENTIFIER .1.3.6.1.4.1.49.2 |
chipGen OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.1 |
chipEcho OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.2 |
chipProducts OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3 |
online OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1 |
olAgents OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.1 |
olConc OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.2 |
olEnv OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.3 |
olModules OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4 |
olSpecMods OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4 |
ol50nnMCTL OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.3 |
ol51nnMMGT OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.4 |
ol51nnMFIB OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.5 |
ol51nnMUTP OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.6 |
ol51nnMTP OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.7 |
ol51nnMBNC OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.8 |
ol51nnBEE OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.9 |
ol51nnRES OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.10 |
ol51nnREE OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.11 |
ol51nnMAUIF OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.12 |
ol51nnMAUIM OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.13 |
ol5208MTP OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.14 |
ol51nnMFP OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.15 |
ol51nnMFBP OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.16 |
ol51nnMTPL OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.17 |
ol51nnMTPPL OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.18 |
ol52nnMTP OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.19 |
ol52nnMFR OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.20 |
ol51nnMTS OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.21 |
ol51nnMFL OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.22 |
ol50nnMRCTL OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.23 |
ol51nnMFB OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.24 |
ol53nnMMGT OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.25 |
ol53nnMFBMIC OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.26 |
ol53nnMFIBST OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.27 |
ol53nnMSTP OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.28 |
ol51nnMTPCL OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.29 |
ol52nnBTT OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.30 |
ol51nnIx OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.31 |
ol52nnMMGT OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.32 |
ol50nnMHCTL OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.4.4.33 |
olNets OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.5 |
olNet OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.5.1 |
olEnet OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.5.2 |
olTRnet OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.5.3 |
olFDDInet OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.5.4 |
olGroups OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.6 |
olAlarm OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.7 |
olThresh OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.7.1 |
olThreshControl OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.1.7.1.1 |
oebm OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.2 |
midnight OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.3 |
workGroupHub OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.4 |
hubSysGroup OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.4.1 |
hardwareGroup OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.4.2 |
softwareGroup OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.4.3 |
hubGroup OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.4.4 |
boardGroup OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.4.5 |
portGroup OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.4.6 |
alarmGroup OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.4.7 |
emm OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.5 |
chipBridge OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.6 |
trmm OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.7 |
fmm OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.8 |
focus1 OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.9 |
oeim OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.3.10 |
chipExperiment OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.4 |
chipExpTokenRing OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.4.1 |
dot5 OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.4.1.1 |
dot5TableThis table contains Token Ring interface
parameters and state variables, one entry
per 802.5 interface. SEQUENCE OF Dot5Entry .1.3.6.1.4.1.49.2.4.1.1.1 |
dot5EntryA list of Token Ring status and parameter
values for an 802.5 interface. Dot5Entry .1.3.6.1.4.1.49.2.4.1.1.1.1 |
dot5IfIndexThe 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.ro INTEGER .1.3.6.1.4.1.49.2.4.1.1.1.1.1 |
dot5CommandsWhen 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).rw Enumeration .1.3.6.1.4.1.49.2.4.1.1.1.1.2 |
dot5RingStatusThe 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.ro INTEGER .1.3.6.1.4.1.49.2.4.1.1.1.1.3 |
dot5RingStateThe current interface state with respect to
entering or leaving the ring.ro Enumeration .1.3.6.1.4.1.49.2.4.1.1.1.1.4 |
dot5RingOpenStatusThis object indicates the success, or the
reason for failure, of the station's most
recent attempt to enter the ring.ro Enumeration .1.3.6.1.4.1.49.2.4.1.1.1.1.5 |
dot5RingSpeedThe ring's bandwidth.rw Enumeration .1.3.6.1.4.1.49.2.4.1.1.1.1.6 |
dot5UpStreamThe MAC-address of the up stream neighbor
station in the ring.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.49.2.4.1.1.1.1.7 |
dot5ActMonParticipateIf 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.rw Enumeration .1.3.6.1.4.1.49.2.4.1.1.1.1.8 |
dot5FunctionalThe bit mask of all Token Ring functional
addresses for which this interface will
accept frames.rw MacAddress (SNMPv2-TC) .1.3.6.1.4.1.49.2.4.1.1.1.1.9 |
dot5StatsTableA table containing Token Ring statistics,
one entry per 802.5 interface.
All the statistics are defined using the
syntax Counter as 32-bit wrap around counters.
Thus, if an interface's hardware maintains these
statistics in 16-bit counters, then the agent
must read the hardware's counters frequently
enough to prevent loss of significance, in
order to maintain 32-bit counters in software. SEQUENCE OF Dot5StatsEntry .1.3.6.1.4.1.49.2.4.1.1.2 |
dot5StatsEntryAn entry contains the 802.5 statistics for a
particular interface. Dot5StatsEntry .1.3.6.1.4.1.49.2.4.1.1.2.1 |
dot5StatsIfIndexThe 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.ro INTEGER .1.3.6.1.4.1.49.2.4.1.1.2.1.1 |
dot5StatsLineErrorsThis 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.ro Counter .1.3.6.1.4.1.49.2.4.1.1.2.1.2 |
dot5StatsBurstErrorsThis counter is incremented when a station
detects the absence of transitions for five
half-bit timers (burst-five error).ro Counter .1.3.6.1.4.1.49.2.4.1.1.2.1.3 |
dot5StatsACErrorsThis 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.ro Counter .1.3.6.1.4.1.49.2.4.1.1.2.1.4 |
dot5StatsAbortTransErrorsThis counter is incremented when a station
transmits an abort delimiter while transmitting.ro Counter .1.3.6.1.4.1.49.2.4.1.1.2.1.5 |
dot5StatsInternalErrorsThis counter is incremented when a station
recognizes an internal error.ro Counter .1.3.6.1.4.1.49.2.4.1.1.2.1.6 |
dot5StatsLostFrameErrorsThis 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.ro Counter .1.3.6.1.4.1.49.2.4.1.1.2.1.7 |
dot5StatsReceiveCongestionsThis 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.ro Counter .1.3.6.1.4.1.49.2.4.1.1.2.1.8 |
dot5StatsFrameCopiedErrorsThis 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.ro Counter .1.3.6.1.4.1.49.2.4.1.1.2.1.9 |
dot5StatsTokenErrorsThis counter is incremented when a station
acting as the active monitor recognizes an
error condition that needs a token transmitted.ro Counter .1.3.6.1.4.1.49.2.4.1.1.2.1.10 |
dot5StatsSoftErrorsThe 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.ro Counter .1.3.6.1.4.1.49.2.4.1.1.2.1.11 |
dot5StatsHardErrorsThe 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.ro Counter .1.3.6.1.4.1.49.2.4.1.1.2.1.12 |
dot5StatsSignalLossThe number of times this interface has
detected the loss of signal condition from
the ring.ro Counter .1.3.6.1.4.1.49.2.4.1.1.2.1.13 |
dot5StatsTransmitBeaconsThe number of times this interface has
transmitted a beacon frame.ro Counter .1.3.6.1.4.1.49.2.4.1.1.2.1.14 |
dot5StatsRecoverysThe 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.ro Counter .1.3.6.1.4.1.49.2.4.1.1.2.1.15 |
dot5StatsLobeWiresThe 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.ro Counter .1.3.6.1.4.1.49.2.4.1.1.2.1.16 |
dot5StatsRemovesThe 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.ro Counter .1.3.6.1.4.1.49.2.4.1.1.2.1.17 |
dot5StatsSinglesThe 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.ro Counter .1.3.6.1.4.1.49.2.4.1.1.2.1.18 |
dot5StatsFreqErrorsThe number of times the interface has detected
that the frequency of the incoming signal differs
from the expected frequency by more than that
ispecified by the IEEE 802.5 standard, see
chapter 7 in [10].ro Counter .1.3.6.1.4.1.49.2.4.1.1.2.1.19 |
dot5Tests OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.4.1.1.3 |
testInsertFunc OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.4.1.1.3.1 |
dot5ChipSets OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.4.1.1.4 |
chipSetIBM16 OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.4.1.1.4.1 |
chipSetTItms380 OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.4.1.1.4.2 |
chipSetTItms380c16 OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.4.1.1.4.3 |
dot5TimerTableThis table contains Token Ring interface
timer values, one entry per 802.5 interface. SEQUENCE OF Dot5TimerEntry .1.3.6.1.4.1.49.2.4.1.1.5 |
dot5TimerEntryA list of Token Ring timer values for an 802.5
interface. Dot5TimerEntry .1.3.6.1.4.1.49.2.4.1.1.5.1 |
dot5TimerIfIndexThe 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.ro INTEGER .1.3.6.1.4.1.49.2.4.1.1.5.1.1 |
dot5TimerReturnRepeatThe 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.ro INTEGER .1.3.6.1.4.1.49.2.4.1.1.5.1.2 |
dot5TimerHoldingMaximum 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.ro INTEGER .1.3.6.1.4.1.49.2.4.1.1.5.1.3 |
dot5TimerQueuePDUThe 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.ro INTEGER .1.3.6.1.4.1.49.2.4.1.1.5.1.4 |
dot5TimerValidTransmitThe 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.ro INTEGER .1.3.6.1.4.1.49.2.4.1.1.5.1.5 |
dot5TimerNoTokenThe 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.ro INTEGER .1.3.6.1.4.1.49.2.4.1.1.5.1.6 |
dot5TimerActiveMonThe 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.ro INTEGER .1.3.6.1.4.1.49.2.4.1.1.5.1.7 |
dot5TimerStandbyMonThe 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.ro INTEGER .1.3.6.1.4.1.49.2.4.1.1.5.1.8 |
dot5TimerErrorReportThe 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.ro INTEGER .1.3.6.1.4.1.49.2.4.1.1.5.1.9 |
dot5TimerBeaconTransmitThe 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.ro INTEGER .1.3.6.1.4.1.49.2.4.1.1.5.1.10 |
dot5TimerBeaconReceiveThe 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.ro INTEGER .1.3.6.1.4.1.49.2.4.1.1.5.1.11 |
dot1dBridge OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.4.14 |
chipTTY OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.5 |
chipTFTP OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.6 |
chipDownload OBJECT IDENTIFIER .1.3.6.1.4.1.49.2.7 |