Novell-LANalyzer-TR-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for Novell-LANalyzer-TR-MIB.
180
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
180 total| Object Name |
|---|
novell OBJECT IDENTIFIER .1.3.6.1.4.1.23 |
RFC1271-MIB Unknown .1.3.6.1.4.1.23 |
productType OBJECT IDENTIFIER .1.3.6.1.4.1.23.1 |
mibDoc OBJECT IDENTIFIER .1.3.6.1.4.1.23.2 |
ringrmon-mib OBJECT IDENTIFIER .1.3.6.1.4.1.23.2.15 |
tokenRingBeaconingThe SNMP trap that is generated when the token ring network
starts beaconing. TRAP-TYPE .1.3.6.1.4.1.23.2.15.0.4 |
tokenRingConfigurationChangeThe SNMP trap that is generated when the a host has entered
or exited the token ring network. TRAP-TYPE .1.3.6.1.4.1.23.2.15.0.5 |
tokenRingStatistics OBJECT IDENTIFIER .1.3.6.1.4.1.23.2.15.1 |
tokenRingStatsTableA list of token ring statistics entries. SEQUENCE OF TokenRingStatsEntry .1.3.6.1.4.1.23.2.15.1.1 |
tokenRingStatsEntryA collection of statistics kept for a particular token ring
interface. TokenRingStatsEntry .1.3.6.1.4.1.23.2.15.1.1.1 |
tokenRingStatsIndexThe value of this object uniquely identifies this
tokenRingStat entry.ro INTEGER ( 1..65535 ) .1.3.6.1.4.1.23.2.15.1.1.1.1 |
tokenRingStatsDataSourceThis object contains the identifier for the source of the
data that this tokenRingStats entry is set up to analyze.
The identifier is defined to contain the name of the
instance that this entry receives data from.
This object may not be modified unless the associated
tokenRingStatsEntry object is equal to invalid(4).rw OBJECT IDENTIFIER .1.3.6.1.4.1.23.2.15.1.1.1.2 |
tokenRingStatsDropEventsThe total number of events in which packets are dropped by
the probe due to lack of resources. Note that this is not
necessarily the number of packets dropped, it is just the
number of times this condition has been detected.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.3 |
tokenRingStatsDataOctetsThe total number of good NON-MAC octets received on the
network, excluding framing bits but including FCS octets.
In contrast to etherStatsOctets, octets from bad packets
are not counted.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.4 |
tokenRingStatsDataPktsThe total number of good NON-MAC packets received on the
network. In contrast to etherStatsPkts, bad packets are not
counted.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.5 |
tokenRingStatsBroadcastDataPktsThe total number of good NON-MAC packets received that were
direct to the broadcast address. Note that bad broadcast
packets are not counted.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.6 |
tokenRingStatsMulticastDataPktsThe total number of good NON-MAC packets received that were
directed to a local or global multicast or functional
address. Note that bad mutlicast packets are not counted.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.7 |
tokenRingStatsMACOctetsThe total number of good MAC octets received on the network,
excluding framing bits but including FCS octets. Same as
tokenRingStatsDataOctets, octets from bad MAC packets are
not counted.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.8 |
tokenRingStatsMACPktsThe total number of good MAC packets received on the network,
including unicast, multicast and broadcast MAC packets. Same
as tokenRingStatsDataPkts, bad MAC packets are not counted.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.9 |
tokenRingStatsRingPurgesThe total number of times that the ring enters the ring purge
state from normal ring state. Ring purge occurs when the
active monitor station detects a type 2 soft errors.
The ring purge state that comes from the monitor contention
or beacon state is not counted.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.10 |
tokenRingStatsMonitorContentionsThe total number of times that the ring enters the monitor
contention state from normal ring state or ring purge state.
Monitor contention occurs when a type 3 soft error occurs
in the network. The monitor contention state that comes
from the beacon state is not counted.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.11 |
tokenRingStatsBeaconsThe total number of times that the ring enters the beaconing
state. Beaconing occurs when a type 4 soft error or hard
error occurs in the network.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.12 |
tokenRingStatsLostMonitorsThe total number of monitor errors reported by the Report
Monitor Error MAC frame. It occurs when the standby monitor
fails to detect a good token in 2.6 seconds, or no ring poll
process is executed in 15 seconds. The standby monitor
assumes that the active monitor is not present or not
functioning. Lost monitor is a type 3 error and will cause
the detect station to initiate the monitor contention
process.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.13 |
tokenRingStatsDuplicateMonitorsThe total number of duplicate monitor errors reported by the
Report Monitor Error MAC frame. When an active monitor
detects a ring purge frame or an active monitor present
frame from other station, it realizes another active monitor
in the ring. This station reports duplicate monitor to the
Ring Error Monitor and becomes a standby monitor.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.14 |
tokenRingStatsDuplicateAddressesThe total number of duplicate address errors reported by the
Report Monitor Error MAC frame. It is generated by the
station when it detects other stations using its own address.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.15 |
tokenRingStatsRingPollFailuresThe total number of Report Ring Poll Failure MAC frames
received. It is generated when the active monitor cannot
see a ring poll cycle completed within a time limit. The
MAC address of the last station in the incomplete ring poll
cycle is saved in the tokenRingNetwork table for reference.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.16 |
tokenRingStatsLineErrorsThe total number of line errors reported to the Ring Error
Monitor. Line error means packet contains incorrect CRC or
code violation. Line error is isolated error. It is a
type 1 error and no ring recovery is performed.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.17 |
tokenRingStatsInternalErrorsThe total number of adapter internal errors reported to the
Ring Error Monitor. Internal error indicates that a station
recognizes a recoverable internal error. Internal error is
isolated error. It is a type 1 error and no ring recovery
is performed.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.18 |
tokenRingStatsBurstErrorsThe total number of burst errors reported to the Ring Error
Monitor. Burst error indicates that a station detects the
absence of transitions for five half-bit times. Burst error
is isolated error. It is a type 2 error and the active
monitor will purge the ring.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.19 |
tokenRingStatsACErrorsThe total number of AC errors reported to the Ring Error
Monitor. AC error indicates that a station cannot interpret
the address recognition bit or the frame copied bit. AC error
is isolated error. It is a type 1 error and no ring recovery
is performed.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.20 |
tokenRingStatsAbortDelimitersThe total number of abort delimiters reported to the Ring
Error Monitor. Abort delimiter indicates that a station
aborts a transmission. Abort delimiter is isolated error.
It is a type 1 error and no ring recovery is performed.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.21 |
tokenRingStatsLostFrameErrorsThe total number of lost frame errors reported to the Ring
Error Monitor. Lost frame error indicates that the end
delimiter of a frame is lost in the network. Lost frame
error is non-isolated error. It is a type 2 error and the
active monitor will purge the ring.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.22 |
tokenRingStatsReceiveCongestionsThe total number of receive congestion errors reported to the
Ring Error Monitor. Receive congestion error indicates that
a station recognizes a frame addressed to its specific address,
but has no available buffer space. Receive congestion error
is non-isolated error. It is a type 1 error and no ring
recovery is performed.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.23 |
tokenRingStatsFrameCopiedErrorsThe total number of frame copied errors reported to the
Ring Error Monitor. Frame copied error indicates that a
station recognizes a frame addressed to its specific address
and detects that the FS field A bits are set to 1. It
implies either a line hit or duplicate address. Frame copied
error is non-isolated error. It is a type 1 error and no
ring recovery is performed.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.24 |
tokenRingStatsFrequencyErrorsThe total number of frequency errors reported to the Ring
Error Monitor. Frequency error indicates that a station
detects that the frequency of the incoming signal differs by
more than the standard specified margin. Frequency error is
non-isolated error. It is a type 3 error and will cause the
detect station initiating monitor contention process.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.25 |
tokenRingStatsTokenErrorsThe total number of token errors reported to the Ring Error
Monitor. Token error indicates that the Active Monitor
station recognizes an error condition that needs a token
transmitted. Token error is non-isolated error. It is a
type 2 error and the active monitor will purge the ring.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.26 |
tokenRingStatsDataPktsUndersizePktsThe total number of packets received that were between 0 and
17 octets in length inclusive, excluding framing bits but
including FCS octets. Packets in this category are too short.
It is the counterpart of runt packets in Ethernet RMON.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.27 |
tokenRingStatsDataPkts18to63OctetsThe total number of data packets received that were between
18 and 63 octets in length inclusive, excluding framing bits
but including FCS octets. It is the counterpart of
etherStatsPkts64Octets in Ethernet RMON. In contrast to
Ethernet, error packets are not counted.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.28 |
tokenRingStatsDataPkts64to127OctetsThe total number of data packets received that were between
64 and 127 octets in length inclusive, excluding framing bits
but including FCS octets. It is the counterpart of
etherStatsPkts65to127Octets in Ethernet RMON. In contrast
to Ethernet, error packets are not counted.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.29 |
tokenRingStatsDataPkts128to255OctetsThe total number of data packets received that were between
128 and 255 octets in length inclusive, excluding framing bits
but including FCS octets. It is the counterpart of
etherStatsPkts128to255Octets in Ethernet RMON. In contrast
to Ethernet, error packets are not counted.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.30 |
tokenRingStatsDataPkts256to511OctetsThe total number of data packets received that were between
256 and 511 octets in length inclusive, excluding framing
bits but including FCS octets. It is the counterpart of
etherStatsPkts256to511Octets in Ethernet RMON. In contrast
to Ethernet, error packets are not counted.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.31 |
tokenRingStatsDataPkts512to1023OctetsThe total number of data packets received that were between
512 and 1023 octets in length inclusive, excluding framing
bits but including FCS octets. It is the counterpart of
etherStatsPkts512to1023Octets in Ethernet RMON. In contrast
to Ethernet, error packets are not counted.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.32 |
tokenRingStatsDataPkts1024to2047OctetsThe total number of data packets received that were between
1024 and 2047 octets in length inclusive, excluding framing
bits but including FCS octets. It is the superset of
etherStatsPkts1024to1518Octets in Ethernet RMON. In contrast
to Ethernet, error packets are not counted.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.33 |
tokenRingStatsDataPkts2048to4608OctetsThe total number of data packets (excluding error packets)
received that were between 2048 and 4608 octets in length
inclusive, excluding framing bits but including FCS octets.
Note that error packets in this length range is not counted.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.34 |
tokenRingStatsDataPkts4609to18000OctetsThe total number of data packets (excluding error packets)
received that were between 4609 and 18000 octets in length
inclusive, excluding framing bits but including FCS octets.
Note that error packets in this length range is not counted.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.35 |
tokenRingStatsDataPktsMoreThan18000OctetsThe total number of data packets (excluding error packets)
received that were more than 18000 in length, excluding
framing bits but including FCS octets. Note that error
packets in this length range is not counted.ro Counter .1.3.6.1.4.1.23.2.15.1.1.1.36 |
tokenRingStatsOwnerAn administratively assigned name for the management station
that configured this entry and is therefore using the
resources assigned to it. This object contains a NVT
octet string up to 127 characters.
In some cases the agent itself will configure an entry.
In this case, the agent is responsible for the resources and
this object shall be set to a string starting with 'monitor'.rw OwnerString .1.3.6.1.4.1.23.2.15.1.1.1.37 |
tokenRingStatsStatusThe status of this tokenRingStats entry.rw EntryStatus .1.3.6.1.4.1.23.2.15.1.1.1.38 |
tokenRingHistory OBJECT IDENTIFIER .1.3.6.1.4.1.23.2.15.2 |
tokenRingHistoryTableA list of token ring statistics entries. SEQUENCE OF TokenRingHistoryEntry .1.3.6.1.4.1.23.2.15.2.1 |
tokenRingHistoryEntryA collection of history statistics
kept for a particular token ring
interface. TokenRingHistoryEntry .1.3.6.1.4.1.23.2.15.2.1.1 |
tokenRingHistoryIndexThe history of which this entry is a part. The
history identified by a particular value of this
index is the same history as identified
by the same value of historyControlIndex.ro INTEGER .1.3.6.1.4.1.23.2.15.2.1.1.1 |
tokenRingHistoryStartIndexAn index that uniquely identifies the particular
sample this entry represents among all samples
associated with the same historyControlEntry.
This index starts at 1 and increases by one
as each new sample is taken.ro INTEGER .1.3.6.1.4.1.23.2.15.2.1.1.2 |
tokenRingHistoryIntervalStartThe value of sysUpTime at the start of the interval
over which this sample was measured. If the probe
keeps track of the time of day, it should start
the first sample of the history at a time such that
when the next hour of the day begins, a sample is
started at that instant. Note that following this
rule may require the probe to delay collecting the
first sample of the history, as each sample must be
of the same interval. Also note that the sample which
is currently being collected is not accessible in this
table until the end of its interval.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.23.2.15.2.1.1.3 |
tokenRingHistoryDropEventsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.4 |
tokenRingHistoryDataOctetsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.5 |
tokenRingHistoryDataPktsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.6 |
tokenRingHistoryBroadcastDataPktsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.7 |
tokenRingHistoryMulticastDataPktsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.8 |
tokenRingHistoryMACOctetsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.9 |
tokenRingHistoryMACPktsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.10 |
tokenRingHistoryRingPurgesro Counter .1.3.6.1.4.1.23.2.15.2.1.1.11 |
tokenRingHistoryMonitorContentionsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.12 |
tokenRingHistoryBeaconsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.13 |
tokenRingHistoryLostMonitorsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.14 |
tokenRingHistoryDuplicateMonitorsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.15 |
tokenRingHistoryDuplicateAddressesro Counter .1.3.6.1.4.1.23.2.15.2.1.1.16 |
tokenRingHistoryRingPollFailuresro Counter .1.3.6.1.4.1.23.2.15.2.1.1.17 |
tokenRingHistoryLineErrorsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.18 |
tokenRingHistoryInternalErrorsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.19 |
tokenRingHistoryBurstErrorsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.20 |
tokenRingHistoryACErrorsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.21 |
tokenRingHistoryAbortDelimitersro Counter .1.3.6.1.4.1.23.2.15.2.1.1.22 |
tokenRingHistoryLostFrameErrorsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.23 |
tokenRingHistoryReceiveCongestionsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.24 |
tokenRingHistoryFrameCopiedErrorsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.25 |
tokenRingHistoryFrequencyErrorsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.26 |
tokenRingHistoryTokenErrorsro Counter .1.3.6.1.4.1.23.2.15.2.1.1.27 |
tokenRingHistoryUtilizationro INTEGER .1.3.6.1.4.1.23.2.15.2.1.1.28 |
tokenRing OBJECT IDENTIFIER .1.3.6.1.4.1.23.2.15.3 |
tokenRingControlTableA list of token ring configuration control entries. SEQUENCE OF TokenRingControlEntry .1.3.6.1.4.1.23.2.15.3.1 |
tokenRingControlEntryA list of parameters that sets up a command buffer
and two event pointers for the manager who has
created this instance. TokenRingControlEntry .1.3.6.1.4.1.23.2.15.3.1.1 |
tokenRingControlIndexAn index that uniquely identifies an entry in the
tokenRingControl table. Each entry contains a
command buffer for the management station to issue
a command and two event indexes for specifying the
actions to be done when the ring starts beaconing
and a host has entered or exited the ring.ro INTEGER ( 1..65535 ) .1.3.6.1.4.1.23.2.15.3.1.1.1 |
tokenRingControlIfIndexThis object contains the board interface number
which is identical to the ifIndex object in the
interface table of MIB-I or MIB-II.rw INTEGER .1.3.6.1.4.1.23.2.15.3.1.1.2 |
tokenRingControlCommandStatusThe object contains the result of the most recent
test, or the value none(1) if no tests have been
requested since last reset.
After the manager issues a new command, the agent
will turn the status to inProgress(3) and start
executing. Meanwhile, the manager polls this object
until a completion status is returned. Then it
proceeds to read the result.rw Enumeration .1.3.6.1.4.1.23.2.15.3.1.1.3 |
tokenRingControlCommandTypeThe object specifies the operation to act upon the
target station requested by the manager. The agent
only accepts unicast address from the management
station. If non-unicast address is specified, the
notSupported(4) value will be written to the
tokenRingControlCommandStatus object. Note that
the agent does not check the specified address with
the host table. In other words, the management
station can specify a non-existing MAC address in
the command.
The removeStation(1) command requests the agent to
send the Remove Ring Station MAC frame to the target
station that deinserts the target station from the
ring.
The testStation(2) command requests the agent to send
the Transmit Forward MAC frame to the tagart station.
The agent then monitors the response frames from the
target station. If the expected response frame is
not detected, the agent will write the failed(7)
value to the tokenRingControlCommandStatus object.
Otherwise, the success(2) value will be written to.
The requestStationAddress(3) command requests the
agent to send the Request Station Address MAC frame
to the target station. This command is to update
the address assignments of the target station in the
host table.
The requestStationState(4) command requests the agent
to send the Request Station State MAC frame to the
target station. This command is to update the state
information of the target station in the host table.
The requestStationAttachment(5) command requests the
agent to send the Request Station Attachment MAC
frame to the target station. This command is to
update the configuration information about the host
attachment unit of the target station in the host
table.rw Enumeration .1.3.6.1.4.1.23.2.15.3.1.1.4 |
tokenRingControlCommandTargetAddressThis object contains the MAC address of the target
station requested by the manager. The value must be
an unicast address. Multicast, functional or
broadcast address is not allowed. Note that the
proxy agent does not check whether the address is in
the host table or not.rw MacAddress (SNMPv2-TC) .1.3.6.1.4.1.23.2.15.3.1.1.5 |
tokenRingControlBeaconEventIndexThe value of this object identifies the event that
is configured to be generated when the ring to which
this interface board is connected starts beaconing.
The beacon event is generated only when the ring
enters the beacon state. The beacon event will not
be generated again unless the ring has exited the
beacon state. The agent reports the failure domain
and the beacon level in the first detected beacon
frame to the management station. The information may
not be the most accurate because the failure domain
takes time to converge and the beacon level can be
elevated. The station can poll the tokenRingNetwork
table to read the current status of the ring.rw INTEGER ( 0..65535 ) .1.3.6.1.4.1.23.2.15.3.1.1.6 |
tokenRingControlConfigEventIndexThe value of this object identifies the event that
is configured to be generated when a station has
entered or exited the ring that this interface board
is connected to.
This control table does not establish any flow
control mechanism with the management station. If a
group of stations enter or exit the ring at the same
time and the link between the management station and
the agent is slow, some events may be lost.rw INTEGER ( 0..65535 ) .1.3.6.1.4.1.23.2.15.3.1.1.7 |
tokenRingControlOwnerAn administratively assigned name for the management
station that configured this entry and is therefore
using the resources assigned to it.
In some cases the agent itself will configure an
entry. In this case, the agent is responsible for
the resources and this object shall be set to a
string starting with 'monitor'.rw OwnerString .1.3.6.1.4.1.23.2.15.3.1.1.8 |
tokenRingControlStatusThe status of this entry.rw EntryStatus .1.3.6.1.4.1.23.2.15.3.1.1.9 |
tokenRingNetworkTableThe ring level information about the token ring
networks in this machine. SEQUENCE OF TokenRingNetworkEntry .1.3.6.1.4.1.23.2.15.3.2 |
tokenRingNetworkEntryThe current state of this token ring network. TokenRingNetworkEntry .1.3.6.1.4.1.23.2.15.3.2.1 |
tokenRingNetworkIfIndexThis object contains the board interface number
which is identical to the ifIndex object in the
interface table of MIB-I or MIB-II.ro INTEGER .1.3.6.1.4.1.23.2.15.3.2.1.1 |
tokenRingNetworkLastResetTimeThis object contains the sysUpTime when the data
base of this group is created or last reset.ro TimeTicks ( 1..65535 ) .1.3.6.1.4.1.23.2.15.3.2.1.2 |
tokenRingNetworkRingNumberThe ring number of which this interface board
connects to. If the ring number is not known, it
should be set to zero.ro INTEGER ( 0..4095 ) .1.3.6.1.4.1.23.2.15.3.2.1.3 |
tokenRingNetworkMediaSpeedThe media speed of the ring. The value is either
4 or 16. Other values are not allowed.ro Enumeration .1.3.6.1.4.1.23.2.15.3.2.1.4 |
tokenRingNetworkBridgesThe number of bridges in the host table. The bridge
is referred to the device which supports the bridge
functional address.ro INTEGER .1.3.6.1.4.1.23.2.15.3.2.1.5 |
tokenRingNetworkActiveStationsThe number of active stations in the host table.
The active stations are participating in the ring
poll process.ro INTEGER .1.3.6.1.4.1.23.2.15.3.2.1.6 |
tokenRingNetworkInactiveStationsThe number of inactive stations in the host table.
The inactive stations are not inserted in the ring
or are not participating in the ring poll process.
Note that the station became inactive before the
tokenRingNetworkLastResetTime cannot be detected by
the agent.ro INTEGER .1.3.6.1.4.1.23.2.15.3.2.1.7 |
tokenRingNetworkLastEnterMACAddressThe MAC address of the token ring station that
has entered this ring most recently.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.23.2.15.3.2.1.8 |
tokenRingNetworkLastExitMACAddressThe MAC address of the token ring station that
has left this ring most recently.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.23.2.15.3.2.1.9 |
tokenRingNetworkStateThe state of the ring of which this entry is a part.ro Enumeration .1.3.6.1.4.1.23.2.15.3.2.1.10 |
tokenRingNetworkStateCauseThe cause of this state transition. It is required
to give the best estimation of the cause. When this
interface just enters the ring, this object is
initialized to initiatState(2). If no hint is
available, then it sets the cause to notClear(1).ro Enumeration .1.3.6.1.4.1.23.2.15.3.2.1.11 |
tokenRingNetworkStateSenderMACAddressThe MAC address of the station which initiates
the state transition.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.23.2.15.3.2.1.12 |
tokenRingNetworkStateUpstreamNeighborMACAddressThe MAC address in the upstream neighbor address
subvector of the MAC protocol frame. Some MAC
protocol frames, such as ring purge frame, do not
contain that subvector, then the MAC address
contained in this object is irrelevant.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.23.2.15.3.2.1.13 |
tokenRingNetworkHostOrderChangesThe count of the index in the host table that has
changed since this table is created. The host table
contains active and inactive stations which are
arranged in sequential order. This counter roughly
estimates the number of times that the hosts have
changed their port connections.ro Counter .1.3.6.1.4.1.23.2.15.3.2.1.14 |
tokenRingNetworkActiveMonitorChangesThe number of times that the active monitor changes
station since this table is created.ro Counter .1.3.6.1.4.1.23.2.15.3.2.1.15 |
tokenRingHostTableA list of token ring host table entries. SEQUENCE OF TokenRingHostEntry .1.3.6.1.4.1.23.2.15.3.3 |
tokenRingHostEntryThe information of the host that has been discovered
on this interface. TokenRingHostEntry .1.3.6.1.4.1.23.2.15.3.3.1 |
tokenRingHostIfIndexThis object contains the board interface number
which is identical to the ifIndex object in the
interface table of MIB-I or MIB-II.ro INTEGER .1.3.6.1.4.1.23.2.15.3.3.1.1 |
tokenRingHostIndexAn index that defines the relative order of the
hosts in this ring starting from the Active Monitor
station. The active monitor station contains the
value of 1. The rest of the stations are arranged
in sequential order relative to the active monitor
station.
When a station becomes inactive, its entry is not
meant to be deleted. The value in the
tokenRingHostStatus is changed to inactive.
The delete algorithm is implementation specific.
If a station becomes active and its entry is already
in the host table, then the value of the
tokenRingHostStatus object is changed to active.
In addition, if the relative order of the host
entries has changed, it shall increment the
tokenRingNetworkHostOrderChange counter in the
tokenRingNetwork table by one.
On the other hand, if a station becomes active and
its entry is not in the host table, then a new entry
must be created. The new entry is inserted right
after its upstream neighbor station. The
tokenRingNetworkHostOrderChange counter in the
tokenRingNetwork table shall not be increment.
If the active monitor changes station and the
relative position of the host entries is unchanged,
then the tokenRingNetworkHostOrderChange object in
the tokenRingNetwork table shall not be increment.ro INTEGER ( 1..65535 ) .1.3.6.1.4.1.23.2.15.3.3.1.2 |
tokenRingHostStatusThe host table contains active and inactive stations.
An active station is currently participating in the
ring poll process. An inactive station is vice
versa. The inactive station can be a previous
active station which has exited the ring, or a
station which is in the ring but does not
participate in the ring poll process.ro Enumeration .1.3.6.1.4.1.23.2.15.3.3.1.3 |
tokenRingHostLastEnterTimeThe sysUpTime that the station has entered the ring
most recently or when the host entry is created.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.23.2.15.3.3.1.4 |
tokenRingHostLastExitTimeThe sysUpTime that the station has exited the ring
most recently. When this object is created, it
shall reset its value to 0. It indicates that the
station has never exited since creation.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.23.2.15.3.3.1.5 |
tokenRingHostMACAddressThe station's MAC address to which this entry is
belonged.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.23.2.15.3.3.1.6 |
tokenRingHostPhysicalDropNumberThe station's physical drop number of which this
entry is belonged. If the value of this object is
not assigned, then it is defaulted to four zeros.ro OCTET STRING .1.3.6.1.4.1.23.2.15.3.3.1.7 |
tokenRingHostSoftErrorReportTimerValueThe time interval of the host station that the
Report Soft Error MAC frame is generated. The
default value is two seconds. The value is in
units of millisecond.ro INTEGER ( 0..65535 ) .1.3.6.1.4.1.23.2.15.3.3.1.8 |
tokenRingHostGroupAddressesThe group address of this station.ro INTEGER .1.3.6.1.4.1.23.2.15.3.3.1.9 |
tokenRingHostFunctionalAddressesThe functional address of the station. The
functional address is assigned in the bit map
fashion. The first two bytes are always 'C0-00' in
hex. and the first bit of the third byte is always
zero. The following 31 bits are defined as follows:
00-00-00-01 : Active Monitor.
00-00-00-02 : Ring Parameter Server.
00-00-00-04 :
00-00-00-08 : Ring Error Monitor.
00-00-00-10 : Configuration Report Server.
00-00-00-20 :
00-00-00-40 :
00-00-00-80 : NetBIOS.
00-00-01-00 : Bridge.
00-00-02-00 :
00-00-04-00 :
00-00-08-00 :
00-00-10-00 :
00-00-20-00 : IBM LAN Network Manager.
00-00-40-00 :
00-00-80-00 :
The bit range between 00-01-00-00 and 40-00-00-00
are not administrated by IEEE. They are defined by
users. Below lists a couple of popular assignments:
00-80-00-00 : Novell NetWare.
40-00-00-00 : Apple TokenTalk Broadcast.ro INTEGER .1.3.6.1.4.1.23.2.15.3.3.1.10 |
tokenRingHostAuthorizedFunctionClassSource classes for which the host is enabled to
transmit. Valid range is '0000 0000 0000 0000'b
to '1111 1111 1111 1111'b. Each bit 0 to 15
corresponds to function class '0000'b to '1111'b.
Bit value '1'b means function class is enabled.
Defined function classes are the following:
'00'H : Ring Station.
'01'H : LLC Manager.
'04'H : Configuration Report Server.
'05'H : Ring Parameter Server.
'06'H : Ring Error Monitor.ro INTEGER ( 0..65535 ) .1.3.6.1.4.1.23.2.15.3.3.1.11 |
tokenRingHostAuthorizedAccessPriorityMaximum allowed token priority with which the
attached product is allowed to transmit.ro INTEGER ( 0..7 ) .1.3.6.1.4.1.23.2.15.3.3.1.12 |
tokenRingHostAdapterSoftwareLevelThe adapter software level of this station.
The interpretation of the value in this object is
vendor specific.ro OCTET STRING .1.3.6.1.4.1.23.2.15.3.3.1.13 |
tokenRingHostAdapterStatusVectorThe adapter status vector of this station.
The interpretation of the value in this object is
vendor specific.ro OCTET STRING .1.3.6.1.4.1.23.2.15.3.3.1.14 |
tokenRingHostProductIDThe product identification of this station.
The content is defined by vendor.ro OCTET STRING .1.3.6.1.4.1.23.2.15.3.3.1.15 |
tokenRingHostLostMonitorsThe total number of monitor errors reported by the Report
Monitor Error MAC frame. It occurs when the standby monitor
fails to detect a good token in 2.6 seconds, or no ring poll
process is executed in 15 seconds. The standby monitor
assumes that the active monitor is not present or not
functioning. Lost monitor is a type 3 error and will cause
the detect station to initiate the monitor contention
process.ro Counter .1.3.6.1.4.1.23.2.15.3.3.1.16 |
tokenRingHostDuplicateMonitorsThe total number of duplicate monitor errors reported by
the Report Monitor Error MAC frame. When an active monitor
detects a ring purge frame or an active monitor present frame
from other station, it realizes another active monitor in
the ring. This station reports duplicate monitor to the
Ring Error Monitor and becomes a standby monitor.ro Counter .1.3.6.1.4.1.23.2.15.3.3.1.17 |
tokenRingHostDuplicateAddressesThe total number of duplicate address errors reported by
the Report Monitor Error MAC frame. It is generated by the
station when it detects other stations using its MAC address.ro Counter .1.3.6.1.4.1.23.2.15.3.3.1.18 |
tokenRingHostRingPollFailuresThe total number of Report Ring Poll Failure MAC frames
received. It is generated when the active monitor cannot
see a ring poll cycle completed within a time limit. The
MAC address of the last station in the incomplete ring poll
cycle is saved in the tokenRingNetwork table for reference.ro Counter .1.3.6.1.4.1.23.2.15.3.3.1.19 |
tokenRingHostInLineErrorsThe total number of line errors reported to the Ring Error
Monitor. Line error means packet contains incorrect CRC
or code violation. Line error is isolated error. It is a
type 1 error and no ring recovery is performed.ro Counter .1.3.6.1.4.1.23.2.15.3.3.1.20 |
tokenRingHostInternalErrorsThe total number of adapter internal errors reported to the
Ring Error Monitor. Internal error indicates that a station
recognizes a recoverable internal error. Internal error is
isolated error. It is a type 1 error and no ring recovery
is performed.ro Counter .1.3.6.1.4.1.23.2.15.3.3.1.21 |
tokenRingHostInBurstErrorsThe total number of burst errors reported to the Ring Error
Monitor. Burst error indicates that a station detects the
absence of transitions for five half-bit times. Burst error
is isolated error. It is a type 2 error and will casue
the active monitor purging the ring.ro Counter .1.3.6.1.4.1.23.2.15.3.3.1.22 |
tokenRingHostACErrorsThe total number of AC errors reported to the Ring Error
Monitor. AC error indicates that a station cannot interpret
the address recognition bit or the frame copied bit. AC
error is isolated error. It is a type 1 error and no ring
recovery is performed.ro Counter .1.3.6.1.4.1.23.2.15.3.3.1.23 |
tokenRingHostAbortDelimitersThe number of abort delimiters reported to the Ring Error
Monitor. Abort delimiter indicates that a station aborts
a transmission. Abort delimiter is isolated error. It is a
type 1 error and no ring recovery is performed.ro Counter .1.3.6.1.4.1.23.2.15.3.3.1.24 |
tokenRingHostLostFrameErrorsThe number of lost frame errors reported to the Ring Error
Monitor. Lost frame error indicates that the end delimiter
of a frame is lost in the network. Lost frame error is
non-isolated error. It is a type 2 error and the active
monitor will purge the ring.ro Counter .1.3.6.1.4.1.23.2.15.3.3.1.25 |
tokenRingHostReceiveCongestionsThe number of receive congestions reported to the Ring Error
Monitor. Receive congestion error indicates that a station
recognizes a frame addressed to its specific address, but
has no available buffer space. Receive congestion error is
non-isolated error. It is a type 1 error and no ring
recovery is performed.ro Counter .1.3.6.1.4.1.23.2.15.3.3.1.26 |
tokenRingHostFrameCopiedErrorsThe number of frame copied errors reported to the Ring Error
Monitor. Frame copied error indicates that a station
recognizes a frame addressed to its specific address and
detects that the A bits in Frame Status byte are set to 1.
It implies either a line hit or duplicate address. Frame
copied error is non-isolated error. It is a type 1 error
and no ring recovery is performed.ro Counter .1.3.6.1.4.1.23.2.15.3.3.1.27 |
tokenRingHostFrequencyErrorsThe number of frequency errors reported to the Ring Error
Monitor. Frequency error indicates that a station detects
that the frequency of the incoming signal differs by more
than the standard specified margin. Frequency error is
non-isolated error. It is a type 3 error and will cause the
detect station initiating monitor contention process.ro Counter .1.3.6.1.4.1.23.2.15.3.3.1.28 |
tokenRingHostTokenErrorsThe total number of token errors reported to the Ring Error
Monitor. Token error indicates that the Active Monitor
station recognizes an error condition that needs a token
transmitted. Token error is non-isolated error. It is a
type 2 error and the active monitor will purge the ring.ro Counter .1.3.6.1.4.1.23.2.15.3.3.1.29 |
tokenRingHostOutLineErrorsThe total number of line errors reported to the Ring Error
Monitor. Line error means packet contains incorrect CRC
or code violation. Line error is isolated error. It is a
type 1 error and no ring recovery is performed.ro Counter .1.3.6.1.4.1.23.2.15.3.3.1.30 |
tokenRingHostOutBurstErrorsThe total number of burst errors reported to the Ring Error
Monitor. Burst error indicates that a station detects the
absence of transitions for five half-bit times. Burst error
is isolated error. It is a type 2 error and will casue
the active monitor purging the ring.ro Counter .1.3.6.1.4.1.23.2.15.3.3.1.31 |
tokenRingHostInBeaconsro Counter .1.3.6.1.4.1.23.2.15.3.3.1.32 |
tokenRingHostOutBeaconsro Counter .1.3.6.1.4.1.23.2.15.3.3.1.33 |
tokenRingHostInsertionsro Counter .1.3.6.1.4.1.23.2.15.3.3.1.34 |
tokenRingOrderTableA list of token ring host table entries. SEQUENCE OF TokenRingOrderEntry .1.3.6.1.4.1.23.2.15.3.4 |
tokenRingOrderEntryThe information of the host that has been discovered
on this interface. TokenRingOrderEntry .1.3.6.1.4.1.23.2.15.3.4.1 |
tokenRingOrderIfIndexThis object contains the board interface number
which is identical to the ifIndex object in the
interface table of MIB-I or MIB-II.ro INTEGER .1.3.6.1.4.1.23.2.15.3.4.1.1 |
tokenRingOrderIndexAn index that defines the relative order of the
hosts in this ring starting from the Active Monitor
station. The active monitor station contains the
value of 1. The rest of the stations are arranged
in sequential order relative to the active monitor
station.
When a station becomes inactive, its entry is not
meant to be deleted. The value in the
tokenRingOrderStatus is changed to inactive.
The delete algorithm is implementation specific.
If a station becomes active and its entry is already
in the host table, then the value of the
tokenRingOrderStatus object is changed to active.
In addition, if the relative order of the host
entries has changed, it shall increment the
tokenRingNetworkHostOrderChange counter in the
tokenRingNetwork table by one.
On the other hand, if a station becomes active and
its entry is not in the host table, then a new entry
must be created. The new entry is inserted right
after its upstream neighbor station. The
tokenRingNetworkHostOrderChange counter in the
tokenRingNetwork table shall not be increment.
If the active monitor changes station and the
relative position of the host entries is unchanged,
then the tokenRingNetworkHostOrderChange object in
the tokenRingNetwork table shall not be increment.ro INTEGER ( 1..65535 ) .1.3.6.1.4.1.23.2.15.3.4.1.2 |
tokenRingOrderStatusThe host table contains active and inactive stations.
An active station is currently participating in the
ring poll process. An inactive station is vice
versa. The inactive station can be a previous
active station which has exited the ring, or a
station which is in the ring but does not
participate in the ring poll process.ro Enumeration .1.3.6.1.4.1.23.2.15.3.4.1.3 |
tokenRingOrderLastEnterTimeThe sysUpTime that the station has entered the ring
most recently or when the host entry is created.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.23.2.15.3.4.1.4 |
tokenRingOrderLastExitTimeThe sysUpTime that the station has exited the ring
most recently. When this object is created, it
shall reset its value to 0. It indicates that the
station has never exited since creation.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.23.2.15.3.4.1.5 |
tokenRingOrderMACAddressThe station's MAC address to which this entry is
belonged.ro MacAddress (SNMPv2-TC) .1.3.6.1.4.1.23.2.15.3.4.1.6 |
tokenRingOrderPhysicalDropNumberThe station's physical drop number of which this
entry is belonged. If the value of this object is
not assigned, then it is defaulted to four zeros.ro OCTET STRING .1.3.6.1.4.1.23.2.15.3.4.1.7 |
tokenRingOrderSoftErrorReportTimerValueThe time interval of the host station that the
Report Soft Error MAC frame is generated. The
default value is two seconds. The value is in
units of millisecond.ro INTEGER ( 0..65535 ) .1.3.6.1.4.1.23.2.15.3.4.1.8 |
tokenRingOrderGroupAddressesThe group address of this station.ro INTEGER .1.3.6.1.4.1.23.2.15.3.4.1.9 |
tokenRingOrderFunctionalAddressesThe functional address of the station. The
functional address is assigned in the bit map
fashion. The first two bytes are always 'C0-00' in
hex. and the first bit of the third byte is always
zero. The following 31 bits are defined as follows:
00-00-00-01 : Active Monitor.
00-00-00-02 : Ring Parameter Server.
00-00-00-04 :
00-00-00-08 : Ring Error Monitor.
00-00-00-10 : Configuration Report Server.
00-00-00-20 :
00-00-00-40 :
00-00-00-80 : NetBIOS.
00-00-01-00 : Bridge.
00-00-02-00 :
00-00-04-00 :
00-00-08-00 :
00-00-10-00 :
00-00-20-00 : IBM LAN Network Manager.
00-00-40-00 :
00-00-80-00 :
The bit range between 00-01-00-00 and 40-00-00-00
are not administrated by IEEE. They are defined by
users. Below lists a couple of popular assignments:
00-80-00-00 : Novell NetWare.
40-00-00-00 : Apple TokenTalk Broadcast.ro INTEGER .1.3.6.1.4.1.23.2.15.3.4.1.10 |
tokenRingOrderAuthorizedFunctionClassSource classes for which the host is enabled to
transmit. Valid range is '0000 0000 0000 0000'b
to '1111 1111 1111 1111'b. Each bit 0 to 15
corresponds to function class '0000'b to '1111'b.
Bit value '1'b means function class is enabled.
Defined function classes are the following:
'00'H : Ring Station.
'01'H : LLC Manager.
'04'H : Configuration Report Server.
'05'H : Ring Parameter Server.
'06'H : Ring Error Monitor.ro INTEGER ( 0..65535 ) .1.3.6.1.4.1.23.2.15.3.4.1.11 |
tokenRingOrderAuthorizedAccessPriorityMaximum allowed token priority with which the
attached product is allowed to transmit.ro INTEGER ( 0..7 ) .1.3.6.1.4.1.23.2.15.3.4.1.12 |
tokenRingOrderAdapterSoftwareLevelThe adapter software level of this station.
The interpretation of the value in this object is
vendor specific.ro OCTET STRING .1.3.6.1.4.1.23.2.15.3.4.1.13 |
tokenRingOrderAdapterStatusVectorThe adapter status vector of this station.
The interpretation of the value in this object is
vendor specific.ro OCTET STRING .1.3.6.1.4.1.23.2.15.3.4.1.14 |
tokenRingOrderProductIDThe product identification of this station.
The content is defined by vendor.ro OCTET STRING .1.3.6.1.4.1.23.2.15.3.4.1.15 |
tokenRingOrderLostMonitorsThe total number of monitor errors reported by the Report
Monitor Error MAC frame. It occurs when the standby monitor
fails to detect a good token in 2.6 seconds, or no ring poll
process is executed in 15 seconds. The standby monitor
assumes that the active monitor is not present or not
functioning. Lost monitor is a type 3 error and will cause
the detect station to initiate the monitor contention
process.ro Counter .1.3.6.1.4.1.23.2.15.3.4.1.16 |
tokenRingOrderDuplicateMonitorsThe total number of duplicate monitor errors reported by
the Report Monitor Error MAC frame. When an active monitor
detects a ring purge frame or an active monitor present frame
from other station, it realizes another active monitor in
the ring. This station reports duplicate monitor to the
Ring Error Monitor and becomes a standby monitor.ro Counter .1.3.6.1.4.1.23.2.15.3.4.1.17 |
tokenRingOrderDuplicateAddressesThe total number of duplicate address errors reported by
the Report Monitor Error MAC frame. It is generated by the
station when it detects other stations using its MAC address.ro Counter .1.3.6.1.4.1.23.2.15.3.4.1.18 |
tokenRingOrderRingPollFailuresThe total number of Report Ring Poll Failure MAC frames
received. It is generated when the active monitor cannot
see a ring poll cycle completed within a time limit. The
MAC address of the last station in the incomplete ring poll
cycle is saved in the tokenRingNetwork table for reference.ro Counter .1.3.6.1.4.1.23.2.15.3.4.1.19 |
tokenRingOrderInLineErrorsThe total number of line errors reported to the Ring Error
Monitor. Line error means packet contains incorrect CRC
or code violation. Line error is isolated error. It is a
type 1 error and no ring recovery is performed.ro Counter .1.3.6.1.4.1.23.2.15.3.4.1.20 |
tokenRingOrderInternalErrorsThe total number of adapter internal errors reported to the
Ring Error Monitor. Internal error indicates that a station
recognizes a recoverable internal error. Internal error is
isolated error. It is a type 1 error and no ring recovery
is performed.ro Counter .1.3.6.1.4.1.23.2.15.3.4.1.21 |
tokenRingOrderInBurstErrorsThe total number of burst errors reported to the Ring Error
Monitor. Burst error indicates that a station detects the
absence of transitions for five half-bit times. Burst error
is isolated error. It is a type 2 error and will casue
the active monitor purging the ring.ro Counter .1.3.6.1.4.1.23.2.15.3.4.1.22 |
tokenRingOrderACErrorsThe total number of AC errors reported to the Ring Error
Monitor. AC error indicates that a station cannot interpret
the address recognition bit or the frame copied bit. AC
error is isolated error. It is a type 1 error and no ring
recovery is performed.ro Counter .1.3.6.1.4.1.23.2.15.3.4.1.23 |
tokenRingOrderAbortDelimitersThe number of abort delimiters reported to the Ring Error
Monitor. Abort delimiter indicates that a station aborts
a transmission. Abort delimiter is isolated error. It is a
type 1 error and no ring recovery is performed.ro Counter .1.3.6.1.4.1.23.2.15.3.4.1.24 |
tokenRingOrderLostFrameErrorsThe number of lost frame errors reported to the Ring Error
Monitor. Lost frame error indicates that the end delimiter
of a frame is lost in the network. Lost frame error is
non-isolated error. It is a type 2 error and the active
monitor will purge the ring.ro Counter .1.3.6.1.4.1.23.2.15.3.4.1.25 |
tokenRingOrderReceiveCongestionsThe number of receive congestions reported to the Ring Error
Monitor. Receive congestion error indicates that a station
recognizes a frame addressed to its specific address, but
has no available buffer space. Receive congestion error is
non-isolated error. It is a type 1 error and no ring
recovery is performed.ro Counter .1.3.6.1.4.1.23.2.15.3.4.1.26 |
tokenRingOrderFrameCopiedErrorsThe number of frame copied errors reported to the Ring Error
Monitor. Frame copied error indicates that a station
recognizes a frame addressed to its specific address and
detects that the A bits in Frame Status byte are set to 1.
It implies either a line hit or duplicate address. Frame
copied error is non-isolated error. It is a type 1 error
and no ring recovery is performed.ro Counter .1.3.6.1.4.1.23.2.15.3.4.1.27 |
tokenRingOrderFrequencyErrorsThe number of frequency errors reported to the Ring Error
Monitor. Frequency error indicates that a station detects
that the frequency of the incoming signal differs by more
than the standard specified margin. Frequency error is
non-isolated error. It is a type 3 error and will cause the
detect station initiating monitor contention process.ro Counter .1.3.6.1.4.1.23.2.15.3.4.1.28 |
tokenRingOrderTokenErrorsThe total number of token errors reported to the Ring Error
Monitor. Token error indicates that the Active Monitor
station recognizes an error condition that needs a token
transmitted. Token error is non-isolated error. It is a
type 2 error and the active monitor will purge the ring.ro Counter .1.3.6.1.4.1.23.2.15.3.4.1.29 |
tokenRingOrderOutLineErrorsThe total number of line errors reported to the Ring Error
Monitor. Line error means packet contains incorrect CRC
or code violation. Line error is isolated error. It is a
type 1 error and no ring recovery is performed.ro Counter .1.3.6.1.4.1.23.2.15.3.4.1.30 |
tokenRingOrderOutBurstErrorsThe total number of burst errors reported to the Ring Error
Monitor. Burst error indicates that a station detects the
absence of transitions for five half-bit times. Burst error
is isolated error. It is a type 2 error and will casue
the active monitor purging the ring.ro Counter .1.3.6.1.4.1.23.2.15.3.4.1.31 |
tokenRingOrderInBeaconsro Counter .1.3.6.1.4.1.23.2.15.3.4.1.32 |
tokenRingOrderOutBeaconsro Counter .1.3.6.1.4.1.23.2.15.3.4.1.33 |
tokenRingOrderInsertionsro Counter .1.3.6.1.4.1.23.2.15.3.4.1.34 |