rfc2108.txt
来自「RFC 的详细文档！」· 文本 代码 · 共 1,751 行 · 第 1/5 页
TXT
1,751 行
"The autoPartitionState flag indicates whether the
port is currently partitioned by the repeater's
auto-partition protection.
The conditions that cause port partitioning are
specified in partition state machine in Sections
9 and 27 of [IEEE 802.3 Std]. They are not
differentiated here."
REFERENCE
de Graaf, et. al. Standards Track [Page 19]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
"[IEEE 802.3 Mgt], 30.4.3.1.3, aAutoPartitionState."
::= { rptrPortEntry 4 }
rptrPortOperStatus OBJECT-TYPE
SYNTAX INTEGER {
operational(1),
notOperational(2),
notPresent(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the port's operational
status. The notPresent(3) status indicates the
port is physically removed (note this may or may
not be possible depending on the type of port.)
The operational(1) status indicates that the port
is enabled (see rptrPortAdminStatus) and working,
even though it might be auto-partitioned (see
rptrPortAutoPartitionState).
If this object has the value operational(1) and
rptrPortAdminStatus is set to disabled(2), it is
expected that this object's value will soon change
to notOperational(2)."
::= { rptrPortEntry 5 }
rptrPortRptrId OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object identifies the repeater to
which this port belongs. The repeater
identified by a particular value of this object
is the same as that identified by the same
value of rptrInfoId. A value of zero
indicates that this port currently is not
a member of any repeater."
::= { rptrPortEntry 6 }
-- New version of basic information at the repeater level.
--
-- Configuration, status, and control objects for
-- each managed repeater in the system.
rptrInfoTable OBJECT-TYPE
de Graaf, et. al. Standards Track [Page 20]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
SYNTAX SEQUENCE OF RptrInfoEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of information about each
non-trivial repeater. The number of entries
depends on the physical configuration of the
managed system."
::= { rptrAllRptrInfo 1 }
rptrInfoEntry OBJECT-TYPE
SYNTAX RptrInfoEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table, containing information
about a single non-trivial repeater."
INDEX { rptrInfoId }
::= { rptrInfoTable 1 }
RptrInfoEntry ::=
SEQUENCE {
rptrInfoId
Integer32,
rptrInfoRptrType
INTEGER,
rptrInfoOperStatus
INTEGER,
rptrInfoReset
INTEGER,
rptrInfoPartitionedPorts
Gauge32,
rptrInfoLastChange
TimeStamp
}
rptrInfoId OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object identifies the repeater for which
this entry contains information."
::= { rptrInfoEntry 1 }
rptrInfoRptrType OBJECT-TYPE
SYNTAX INTEGER {
other(1), -- undefined or unknown
de Graaf, et. al. Standards Track [Page 21]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
tenMb(2),
onehundredMbClassI(3),
onehundredMbClassII(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The rptrInfoRptrType returns a value that identifies
the CSMA/CD repeater type."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.1.1.2, aRepeaterType."
::= { rptrInfoEntry 2 }
rptrInfoOperStatus OBJECT-TYPE
SYNTAX INTEGER {
other(1),
ok(2),
failure(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The rptrInfoOperStatus object indicates the
operational state of the repeater."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.1.1.5, aRepeaterHealthState."
::= { rptrInfoEntry 3 }
rptrInfoReset OBJECT-TYPE
SYNTAX INTEGER {
noReset(1),
reset(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Setting this object to reset(2) causes a
transition to the START state of Fig 9-2 in
section 9 [IEEE 802.3 Std] for a 10Mb/s repeater,
and to the START state of Fig 27-2 in section 27
of that standard for a 100Mb/s repeater.
Setting this object to noReset(1) has no effect.
The agent will always return the value noReset(1)
when this object is read.
After receiving a request to set this variable to
reset(2), the agent is allowed to delay the reset
de Graaf, et. al. Standards Track [Page 22]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
for a short period. For example, the implementor
may choose to delay the reset long enough to allow
the SNMP response to be transmitted. In any
event, the SNMP response must be transmitted.
This action does not reset the management counters
defined in this document nor does it affect the
portAdminStatus parameters. Included in this
action is the execution of a disruptive Self-Test
with the following characteristics: a) The nature
of the tests is not specified. b) The test resets
the repeater but without affecting management
information about the repeater. c) The test does
not inject packets onto any segment. d) Packets
received during the test may or may not be
transferred. e) The test does not interfere with
management functions.
After performing this self-test, the agent will
update the repeater health information (including
rptrInfoOperStatus), and send a rptrInfoResetEvent
notification."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.1.2.1, acResetRepeater."
::= { rptrInfoEntry 4 }
rptrInfoPartitionedPorts OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object returns the total number of ports in
the repeater whose current state meets all three
of the following criteria: rptrPortOperStatus
does not have the value notPresent(3),
rptrPortAdminStatus is enabled(1), and
rptrPortAutoPartitionState is autoPartitioned(2)."
::= { rptrInfoEntry 5 }
rptrInfoLastChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime when any of the following
conditions occurred:
1) agent cold- or warm-started;
2) this instance of repeater was created
de Graaf, et. al. Standards Track [Page 23]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
(such as when a device or module was
added to the system);
3) a change in the value of rptrInfoOperStatus;
4) ports were added or removed as members of
the repeater; or
5) any of the counters associated with this
repeater had a discontinuity."
::= { rptrInfoEntry 6 }
--
-- Old version of statistics at the repeater level.
--
-- Performance monitoring statistics for the repeater
--
-- In a system containing a single managed repeater-unit,
-- the statistics object for the repeater-unit.
-- The objects contained under the rptrMonitorRptrInfo subtree are
-- intended for backwards compatibility with implementations of
-- RFC 1516 [11]. In newer implementations (both single- and
-- multiple-repeater implementations), the rptrMonitorTable will
-- be implemented. It is the preferred source of this information,
-- as it contains the values for all repeaters managed by the
-- agent. In all cases, the objects in the rptrMonitorRptrInfo
-- subtree are duplicates of the corresponding objects in the
-- first entry of the rptrMonitorTable.
rptrMonitorTransmitCollisions OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
For a clause 9 (10Mb/s) repeater, this counter
is incremented every time the repeater state
machine enters the TRANSMIT COLLISION state
from any state other than ONE PORT LEFT
(Ref: Fig 9-2 [IEEE 802.3 Std]).
For a clause 27 repeater, this counter is
incremented every time the repeater core state
diagram enters the Jam state as a result of
Activity(ALL) > 1 (fig 27-2 [IEEE 802.3 Std]).
de Graaf, et. al. Standards Track [Page 24]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
The approximate minimum time for rollover of this
counter is 16 hours in a 10Mb/s repeater and 1.6
hours in a 100Mb/s repeater."
REFERENCE
"[IEEE 802.3 Mgt], 30.4.1.1.8, aTransmitCollisions."
::= { rptrMonitorRptrInfo 1 }
-- Statistics at the group level.
--
-- In a system containing a single managed repeater-unit,
-- the statistics objects for each group.
rptrMonitorGroupTable OBJECT-TYPE
SYNTAX SEQUENCE OF RptrMonitorGroupEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
Table of performance and error statistics for the
groups within the repeater. The number of entries
is the same as that in the rptrGroupTable."
::= { rptrMonitorGroupInfo 1 }
rptrMonitorGroupEntry OBJECT-TYPE
SYNTAX RptrMonitorGroupEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"********* THIS OBJECT IS DEPRECATED **********
An entry in the table, containing total
performance and error statistics for a single
group. Regular retrieval of the information in
this table provides a means of tracking the
performance and health of the networked devices
attached to this group's ports.
The counters in this table are redundant in the
sense that they are the summations of information
already available through other objects. However,
these sums provide a considerable optimization of
network management traffic over the otherwise
necessary retrieval of the individual counters
included in each sum.
Note: Group-level counters are
de Graaf, et. al. Standards Track [Page 25]
RFC 2108 802.3 Repeater MIB using SMIv2 February 1997
⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?