📄 rfc1231-mib
字号:
DESCRIPTION "This table contains Token Ring interface timer values, one entry per 802.5 interface." ::= { dot5 5 }dot5TimerEntry OBJECT-TYPE SYNTAX Dot5TimerEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "A list of Token Ring timer values for an 802.5 interface." INDEX { dot5TimerIfIndex } ::= { dot5TimerTable 1 }Dot5TimerEntry ::= SEQUENCE { dot5TimerIfIndex INTEGER, dot5TimerReturnRepeat INTEGER, dot5TimerHolding INTEGER, dot5TimerQueuePDU INTEGER, dot5TimerValidTransmit INTEGER, dot5TimerNoToken INTEGER, dot5TimerActiveMon INTEGER, dot5TimerStandbyMon INTEGER, dot5TimerErrorReport INTEGER, dot5TimerBeaconTransmit INTEGER, dot5TimerBeaconReceive INTEGER }dot5TimerIfIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "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." ::= { dot5TimerEntry 1 }dot5TimerReturnRepeat OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "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." ::= { dot5TimerEntry 2 }dot5TimerHolding OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "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." ::= { dot5TimerEntry 3 }dot5TimerQueuePDU OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "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." ::= { dot5TimerEntry 4 }dot5TimerValidTransmit OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "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." ::= { dot5TimerEntry 5 }dot5TimerNoToken OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "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." ::= { dot5TimerEntry 6 }dot5TimerActiveMon OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "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." ::= { dot5TimerEntry 7 }dot5TimerStandbyMon OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "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." ::= { dot5TimerEntry 8 }dot5TimerErrorReport OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "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." ::= { dot5TimerEntry 9 }dot5TimerBeaconTransmit OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "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." ::= { dot5TimerEntry 10 }dot5TimerBeaconReceive OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "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." ::= { dot5TimerEntry 11 }-- 802.5 Interface Testsdot5Tests OBJECT IDENTIFIER ::= { dot5 3 }-- The extensions to the interfaces table proposed in [11]-- define a table object, ifExtnsTestTable, through which a-- network manager can instruct an agent to test an interface-- for various faults. A test to be performed is identified-- (as the value of ifExtnsTestType) via an OBJECT IDENTIFIER.---- The Full-Duplex Loop Back Test is a common test, defined-- in [11] as:---- testFullDuplexLoopBack---- Invoking this test on a 802.5 interface causes the-- interface to check the path from memory through the-- chip set's internal logic and back to memory, thus-- checking the proper functioning of the systems's-- interface to the chip set.-- The Insert Function test is defined by:testInsertFunc OBJECT IDENTIFIER ::= { dot5Tests 1 }-- Invoking this test causes the station to test the insert-- ring logic of the hardware if the station's lobe media-- cable is connected to a wiring concentrator. Note that-- this command inserts the station into the network, and-- thus, could cause problems if the station is connected-- to a operational network.-- 802.5 Hardware Chip Setsdot5ChipSets OBJECT IDENTIFIER ::= { dot5 4 }-- The extensions to the interfaces table proposed in [11]-- define an object, ifExtnsChipSet, with the syntax of-- OBJECT IDENTIFIER, to identify the hardware chip set in-- use by an interface. That definition specifies just-- one applicable object identifier:---- unknownChipSet---- for use as the value of ifExtnsChipSet when the specific-- chip set is unknown.---- This MIB defines the following for use as values of-- ifExtnsChipSet: -- IBM 16/4 Mb/schipSetIBM16 OBJECT IDENTIFIER ::= { dot5ChipSets 1 } -- TI 4Mb/schipSetTItms380 OBJECT IDENTIFIER ::= { dot5ChipSets 2 } -- TI 16/4 Mb/schipSetTItms380c16 OBJECT IDENTIFIER ::= { dot5ChipSets 3 }END
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -