1 SNMP-REPEATER-MIB DEFINITIONS ::= BEGIN
4 Counter32, Counter64, Integer32, Gauge32, TimeTicks,
5 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, mib-2
7 TimeStamp, DisplayString, MacAddress, TEXTUAL-CONVENTION,
10 OBJECT-GROUP, MODULE-COMPLIANCE
16 snmpRptrMod MODULE-IDENTITY
17 LAST-UPDATED "9609140000Z"
18 ORGANIZATION "IETF HUB MIB Working Group"
20 "WG E-mail: hubmib@hprnd.rose.hp.com
23 Postal: Madge Networks (Israel) Ltd.
24 Atidim Technology Park, Bldg. 3
25 Tel Aviv 61131, Israel
26 Tel: 972-3-6458414, 6458458
28 E-mail: dromasca@madge.com
30 Editor: Kathryn de Graaf
31 Postal: 3Com Corporation
33 Southborough, MA 01772 USA
36 E-mail: kdegraaf@isd.3com.com"
38 "Management information for 802.3 repeaters.
40 The following references are used throughout
44 refers to IEEE 802.3/ISO 8802-3 Information
45 processing systems - Local area networks -
46 Part 3: Carrier sense multiple access with
47 collision detection (CSMA/CD) access method
48 and physical layer specifications (1993).
51 refers to IEEE 802.3u-1995, '10 Mb/s &
52 100 Mb/s Management, Section 30,'
53 Supplement to ANSI/IEEE 802.3.
55 The following terms are used throughout this
56 MIB module. For complete formal definitions,
57 the IEEE 802.3 standards should be consulted
60 System - A managed entity compliant with this
61 MIB, and incorporating at least one managed
64 Chassis - An enclosure for one managed repeater,
65 part of a managed repeater, or several managed
66 repeaters. It typically contains an integral
67 power supply and a variable number of available
70 Repeater-unit - The portion of the repeater set
71 that is inboard of the physical media interfaces.
72 The physical media interfaces (MAUs, AUIs) may be
73 physically separated from the repeater-unit, or
74 they may be integrated into the same physical
77 Trivial repeater-unit - An isolated port that can
80 Group - A recommended, but optional, entity
81 defined by the IEEE 802.3 management standard,
82 in order to support a modular numbering scheme.
83 The classical example allows an implementor to
84 represent field-replaceable units as groups of
85 ports, with the port numbering matching the
86 modular hardware implementation.
88 System interconnect segment - An internal
89 segment allowing interconnection of ports
90 belonging to different physical entities
91 into the same logical manageable repeater.
92 Examples of implementation might be
93 backplane busses in modular hubs, or
94 chaining cables in stacks of hubs.
95 Stack - A scalable system that may include
96 managed repeaters, in which modularity is
97 achieved by interconnecting a number of
100 Module - A building block in a modular
101 chassis. It typically maps into one 'slot';
102 however, the range of configurations may be
103 very large, with several modules entering
104 one slot, or one module covering several
107 REVISION "9309010000Z"
109 "Published as RFC 1516"
110 REVISION "9210010000Z"
112 "Published as RFC 1368"
113 ::= { snmpDot3RptrMgt 5 }
117 snmpDot3RptrMgt OBJECT IDENTIFIER ::= { mib-2 22 }
120 OptMacAddr ::= TEXTUAL-CONVENTION
124 "Either a 6 octet address in the `canonical'
125 order defined by IEEE 802.1a, i.e., as if it
126 were transmitted least significant bit first
127 if a value is available or a zero length string."
129 "See MacAddress in SNMPv2-TC. The only difference
130 is that a zero length string is allowed as a value
131 for OptMacAddr and not for MacAddress."
132 SYNTAX OCTET STRING (SIZE (0 | 6))
136 -- Basic information at the repeater, group, and port level.
139 OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 1 }
141 OBJECT IDENTIFIER ::= { rptrBasicPackage 1 }
143 OBJECT IDENTIFIER ::= { rptrBasicPackage 2 }
145 OBJECT IDENTIFIER ::= { rptrBasicPackage 3 }
147 OBJECT IDENTIFIER ::= { rptrBasicPackage 4 }
149 -- Monitoring information at the repeater, group, and port level.
151 OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 2 }
153 OBJECT IDENTIFIER ::= { rptrMonitorPackage 1 }
155 OBJECT IDENTIFIER ::= { rptrMonitorPackage 2 }
157 OBJECT IDENTIFIER ::= { rptrMonitorPackage 3 }
158 rptrMonitorAllRptrInfo
159 OBJECT IDENTIFIER ::= { rptrMonitorPackage 4 }
161 -- Address tracking information at the repeater, group,
164 OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 3 }
165 rptrAddrTrackRptrInfo
166 OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 1 }
167 rptrAddrTrackGroupInfo
168 -- this subtree is currently unused
169 OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 2 }
170 rptrAddrTrackPortInfo
171 OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 3 }
175 OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 4 }
177 -- this subtree is currently unused
178 OBJECT IDENTIFIER ::= { rptrTopNPackage 1 }
180 -- this subtree is currently unused
181 OBJECT IDENTIFIER ::= { rptrTopNPackage 2 }
183 OBJECT IDENTIFIER ::= { rptrTopNPackage 3 }
186 -- Old version of basic information at the repeater level.
188 -- In a system containing a single managed repeater,
189 -- configuration, status, and control objects for the overall
193 -- The objects contained under the rptrRptrInfo subtree are
194 -- intended for backwards compatibility with implementations of
195 -- RFC 1516 [11]. In newer implementations (both single- and
196 -- multiple-repeater implementations) the rptrInfoTable should
197 -- be implemented. It is the preferred source of this information,
198 -- as it contains the values for all repeaters managed by the
199 -- agent. In all cases, the objects in the rptrRptrInfo subtree
200 -- are duplicates of the corresponding objects in the first entry
201 -- of the rptrInfoTable.
203 rptrGroupCapacity OBJECT-TYPE
204 SYNTAX Integer32 (1..2147483647)
208 "********* THIS OBJECT IS DEPRECATED **********
210 The rptrGroupCapacity is the number of groups
211 that can be contained within the repeater. Within
212 each managed repeater, the groups are uniquely
213 numbered in the range from 1 to rptrGroupCapacity.
215 Some groups may not be present in the repeater, in
216 which case the actual number of groups present
217 will be less than rptrGroupCapacity. The number
218 of groups present will never be greater than
221 Note: In practice, this will generally be the
222 number of field-replaceable units (i.e., modules,
223 cards, or boards) that can fit in the physical
224 repeater enclosure, and the group numbers will
225 correspond to numbers marked on the physical
228 "[IEEE 802.3 Mgt], 30.4.1.1.3,
229 aRepeaterGroupCapacity."
230 ::= { rptrRptrInfo 1 }
232 rptrOperStatus OBJECT-TYPE
234 other(1), -- undefined or unknown
235 ok(2), -- no known failures
236 rptrFailure(3), -- repeater-related failure
237 groupFailure(4), -- group-related failure
238 portFailure(5), -- port-related failure
239 generalFailure(6) -- failure, unspecified type
244 "********* THIS OBJECT IS DEPRECATED **********
246 The rptrOperStatus object indicates the
247 operational state of the repeater. The
248 rptrHealthText object may be consulted for more
249 specific information about the state of the
252 In the case of multiple kinds of failures (e.g.,
253 repeater failure and port failure), the value of
254 this attribute shall reflect the highest priority
255 failure in the following order, listed highest
263 "[IEEE 802.3 Mgt], 30.4.1.1.5, aRepeaterHealthState."
264 ::= { rptrRptrInfo 2 }
266 rptrHealthText OBJECT-TYPE
267 SYNTAX DisplayString (SIZE (0..255))
271 "********* THIS OBJECT IS DEPRECATED **********
273 The health text object is a text string that
274 provides information relevant to the operational
275 state of the repeater. Agents may use this string
276 to provide detailed information on current
277 failures, including how they were detected, and/or
278 instructions for problem resolution. The contents
281 "[IEEE 802.3 Mgt], 30.4.1.1.6, aRepeaterHealthText."
282 ::= { rptrRptrInfo 3 }
284 rptrReset OBJECT-TYPE
289 MAX-ACCESS read-write
292 "********* THIS OBJECT IS DEPRECATED **********
294 Setting this object to reset(2) causes a
295 transition to the START state of Fig 9-2 in
296 section 9 [IEEE 802.3 Std] for a 10Mb/s repeater,
297 and the START state of Fig 27-2 in section 27
298 of that standard for a 100Mb/s repeater.
300 Setting this object to noReset(1) has no effect.
301 The agent will always return the value noReset(1)
302 when this object is read.
304 After receiving a request to set this variable to
305 reset(2), the agent is allowed to delay the reset
306 for a short period. For example, the implementor
307 may choose to delay the reset long enough to allow
308 the SNMP response to be transmitted. In any
309 event, the SNMP response must be transmitted.
311 This action does not reset the management counters
312 defined in this document nor does it affect the
313 portAdminStatus parameters. Included in this
314 action is the execution of a disruptive Self-Test
315 with the following characteristics: a) The nature
316 of the tests is not specified. b) The test resets
317 the repeater but without affecting management
318 information about the repeater. c) The test does
319 not inject packets onto any segment. d) Packets
320 received during the test may or may not be
321 transferred. e) The test does not interfere with
322 management functions.
324 After performing this self-test, the agent will
325 update the repeater health information (including
326 rptrOperStatus and rptrHealthText), and send a
329 "[IEEE 802.3 Mgt], 30.4.1.2.1, acResetRepeater."
330 ::= { rptrRptrInfo 4 }
332 rptrNonDisruptTest OBJECT-TYPE
337 MAX-ACCESS read-write
340 "********* THIS OBJECT IS DEPRECATED **********
342 Setting this object to selfTest(2) causes the
343 repeater to perform a agent-specific, non-
344 disruptive self-test that has the following
345 characteristics: a) The nature of the tests is
346 not specified. b) The test does not change the
347 state of the repeater or management information
348 about the repeater. c) The test does not inject
349 packets onto any segment. d) The test does not
350 prevent the relay of any packets. e) The test
351 does not interfere with management functions.
353 After performing this test, the agent will update
354 the repeater health information (including
355 rptrOperStatus and rptrHealthText) and send a
358 Note that this definition allows returning an
359 'okay' result after doing a trivial test.
361 Setting this object to noSelfTest(1) has no
362 effect. The agent will always return the value
363 noSelfTest(1) when this object is read."
365 "[IEEE 802.3 Mgt], 30.4.1.2.2,
366 acExecuteNonDisruptiveSelfTest."
367 ::= { rptrRptrInfo 5 }
369 rptrTotalPartitionedPorts OBJECT-TYPE
374 "********* THIS OBJECT IS DEPRECATED **********
376 This object returns the total number of ports in
377 the repeater whose current state meets all three
378 of the following criteria: rptrPortOperStatus
379 does not have the value notPresent(3),
380 rptrPortAdminStatus is enabled(1), and
381 rptrPortAutoPartitionState is autoPartitioned(2)."
382 ::= { rptrRptrInfo 6 }
384 -- Basic information at the group level.
386 -- Configuration and status objects for each
387 -- managed group in the system, independent
388 -- of whether there is one or more managed
389 -- repeater-units in the system.
391 rptrGroupTable OBJECT-TYPE
392 SYNTAX SEQUENCE OF RptrGroupEntry
393 MAX-ACCESS not-accessible
396 "Table of descriptive and status information about
397 the groups of ports."
398 ::= { rptrGroupInfo 1 }
400 rptrGroupEntry OBJECT-TYPE
401 SYNTAX RptrGroupEntry
402 MAX-ACCESS not-accessible
405 "An entry in the table, containing information
406 about a single group of ports."
407 INDEX { rptrGroupIndex }
408 ::= { rptrGroupTable 1 }
420 rptrGroupLastOperStatusChange
422 rptrGroupPortCapacity
426 rptrGroupIndex OBJECT-TYPE
427 SYNTAX Integer32 (1..2147483647)
431 "This object identifies the group within the
432 system for which this entry contains
435 "[IEEE 802.3 Mgt], 30.4.2.1.1, aGroupID."
436 ::= { rptrGroupEntry 1 }
438 rptrGroupDescr OBJECT-TYPE
439 SYNTAX DisplayString (SIZE (0..255))
443 "********* THIS OBJECT IS DEPRECATED **********
445 A textual description of the group. This value
446 should include the full name and version
447 identification of the group's hardware type and
448 indicate how the group is differentiated from
449 other types of groups in the repeater. Plug-in
450 Module, Rev A' or 'Barney Rubble 10BASE-T 4-port
451 SIMM socket Version 2.1' are examples of valid
454 It is mandatory that this only contain printable
456 ::= { rptrGroupEntry 2 }
458 rptrGroupObjectID OBJECT-TYPE
459 SYNTAX OBJECT IDENTIFIER
463 "The vendor's authoritative identification of the
464 group. This value may be allocated within the SMI
465 enterprises subtree (1.3.6.1.4.1) and provides a
466 straight-forward and unambiguous means for
467 determining what kind of group is being managed.
469 For example, this object could take the value
470 1.3.6.1.4.1.4242.1.2.14 if vendor 'Flintstones,
471 Inc.' was assigned the subtree 1.3.6.1.4.1.4242,
472 and had assigned the identifier
473 1.3.6.1.4.1.4242.1.2.14 to its 'Wilma Flintstone
474 6-Port FOIRL Plug-in Module.'"
475 ::= { rptrGroupEntry 3 }
477 rptrGroupOperStatus OBJECT-TYPE
489 "An object that indicates the operational status
492 A status of notPresent(4) indicates that the group
493 is temporarily or permanently physically and/or
494 logically not a part of the repeater. It is an
495 implementation-specific matter as to whether the
496 agent effectively removes notPresent entries from
499 A status of operational(2) indicates that the
500 group is functioning, and a status of
501 malfunctioning(3) indicates that the group is
502 malfunctioning in some way."
503 ::= { rptrGroupEntry 4 }
505 rptrGroupLastOperStatusChange OBJECT-TYPE
510 "********* THIS OBJECT IS DEPRECATED **********
512 An object that contains the value of sysUpTime at
513 the time when the last of the following occurred:
514 1) the agent cold- or warm-started;
515 2) the row for the group was created (such
516 as when the group was added to the system); or
517 3) the value of rptrGroupOperStatus for the
520 A value of zero indicates that the group's
521 operational status has not changed since the agent
523 ::= { rptrGroupEntry 5 }
525 rptrGroupPortCapacity OBJECT-TYPE
526 SYNTAX Integer32 (1..2147483647)
530 "The rptrGroupPortCapacity is the number of ports
531 that can be contained within the group. Valid
532 range is 1-2147483647. Within each group, the
533 ports are uniquely numbered in the range from 1 to
534 rptrGroupPortCapacity.
536 Some ports may not be present in the system, in
537 which case the actual number of ports present
538 will be less than the value of rptrGroupPortCapacity.
539 The number of ports present in the group will never
540 be greater than the value of rptrGroupPortCapacity.
542 Note: In practice, this will generally be the
543 number of ports on a module, card, or board, and
544 the port numbers will correspond to numbers marked
545 on the physical embodiment."
547 "IEEE 802.3 Mgt, 30.4.2.1.2, aGroupPortCapacity."
548 ::= { rptrGroupEntry 6 }
551 -- Basic information at the port level.
553 -- Configuration and status objects for
554 -- each managed repeater port in the system,
555 -- independent of whether there is one or more
556 -- managed repeater-units in the system.
558 rptrPortTable OBJECT-TYPE
559 SYNTAX SEQUENCE OF RptrPortEntry
560 MAX-ACCESS not-accessible
563 "Table of descriptive and status information about
564 the repeater ports in the system. The number of
565 entries is independent of the number of repeaters
566 in the managed system."
567 ::= { rptrPortInfo 1 }
569 rptrPortEntry OBJECT-TYPE
571 MAX-ACCESS not-accessible
574 "An entry in the table, containing information
575 about a single port."
576 INDEX { rptrPortGroupIndex, rptrPortIndex }
577 ::= { rptrPortTable 1 }
587 rptrPortAutoPartitionState
595 rptrPortGroupIndex OBJECT-TYPE
596 SYNTAX Integer32 (1..2147483647)
600 "This object identifies the group containing the
601 port for which this entry contains information."
602 ::= { rptrPortEntry 1 }
604 rptrPortIndex OBJECT-TYPE
605 SYNTAX Integer32 (1..2147483647)
609 "This object identifies the port within the group
610 for which this entry contains information. This
611 identifies the port independently from the repeater
612 it may be attached to. The numbering scheme for
613 ports is implementation specific; however, this
614 value can never be greater than
615 rptrGroupPortCapacity for the associated group."
617 "[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID."
618 ::= { rptrPortEntry 2 }
620 rptrPortAdminStatus OBJECT-TYPE
625 MAX-ACCESS read-write
628 "Setting this object to disabled(2) disables the
629 port. A disabled port neither transmits nor
630 receives. Once disabled, a port must be
631 explicitly enabled to restore operation. A port
632 which is disabled when power is lost or when a
633 reset is exerted shall remain disabled when normal
636 The admin status takes precedence over auto-
637 partition and functionally operates between the
638 auto-partition mechanism and the AUI/PMA.
640 Setting this object to enabled(1) enables the port
641 and exerts a BEGIN on the port's auto-partition
644 (In effect, when a port is disabled, the value of
645 rptrPortAutoPartitionState for that port is frozen
646 until the port is next enabled. When the port
647 becomes enabled, the rptrPortAutoPartitionState
648 becomes notAutoPartitioned(1), regardless of its
649 pre-disabling state.)"
651 "[IEEE 802.3 Mgt], 30.4.3.1.2, aPortAdminState
652 and 30.4.3.2.1, acPortAdminControl."
653 ::= { rptrPortEntry 3 }
655 rptrPortAutoPartitionState OBJECT-TYPE
657 notAutoPartitioned(1),
663 "The autoPartitionState flag indicates whether the
664 port is currently partitioned by the repeater's
665 auto-partition protection.
667 The conditions that cause port partitioning are
668 specified in partition state machine in Sections
669 9 and 27 of [IEEE 802.3 Std]. They are not
670 differentiated here."
672 "[IEEE 802.3 Mgt], 30.4.3.1.3, aAutoPartitionState."
673 ::= { rptrPortEntry 4 }
675 rptrPortOperStatus OBJECT-TYPE
684 "This object indicates the port's operational
685 status. The notPresent(3) status indicates the
686 port is physically removed (note this may or may
687 not be possible depending on the type of port.)
688 The operational(1) status indicates that the port
689 is enabled (see rptrPortAdminStatus) and working,
690 even though it might be auto-partitioned (see
691 rptrPortAutoPartitionState).
693 If this object has the value operational(1) and
694 rptrPortAdminStatus is set to disabled(2), it is
695 expected that this object's value will soon change
696 to notOperational(2)."
697 ::= { rptrPortEntry 5 }
699 rptrPortRptrId OBJECT-TYPE
700 SYNTAX Integer32 (0..2147483647)
704 "This object identifies the repeater to
705 which this port belongs. The repeater
706 identified by a particular value of this object
707 is the same as that identified by the same
708 value of rptrInfoId. A value of zero
709 indicates that this port currently is not
710 a member of any repeater."
711 ::= { rptrPortEntry 6 }
714 -- New version of basic information at the repeater level.
716 -- Configuration, status, and control objects for
717 -- each managed repeater in the system.
719 rptrInfoTable OBJECT-TYPE
720 SYNTAX SEQUENCE OF RptrInfoEntry
721 MAX-ACCESS not-accessible
724 "A table of information about each
725 non-trivial repeater. The number of entries
726 depends on the physical configuration of the
728 ::= { rptrAllRptrInfo 1 }
730 rptrInfoEntry OBJECT-TYPE
732 MAX-ACCESS not-accessible
735 "An entry in the table, containing information
736 about a single non-trivial repeater."
738 ::= { rptrInfoTable 1 }
750 rptrInfoPartitionedPorts
756 rptrInfoId OBJECT-TYPE
757 SYNTAX Integer32 (1..2147483647)
761 "This object identifies the repeater for which
762 this entry contains information."
763 ::= { rptrInfoEntry 1 }
765 rptrInfoRptrType OBJECT-TYPE
767 other(1), -- undefined or unknown
769 onehundredMbClassI(3),
770 onehundredMbClassII(4)
775 "The rptrInfoRptrType returns a value that identifies
776 the CSMA/CD repeater type."
778 "[IEEE 802.3 Mgt], 30.4.1.1.2, aRepeaterType."
779 ::= { rptrInfoEntry 2 }
781 rptrInfoOperStatus OBJECT-TYPE
790 "The rptrInfoOperStatus object indicates the
791 operational state of the repeater."
793 "[IEEE 802.3 Mgt], 30.4.1.1.5, aRepeaterHealthState."
794 ::= { rptrInfoEntry 3 }
796 rptrInfoReset OBJECT-TYPE
801 MAX-ACCESS read-write
804 "Setting this object to reset(2) causes a
805 transition to the START state of Fig 9-2 in
806 section 9 [IEEE 802.3 Std] for a 10Mb/s repeater,
807 and to the START state of Fig 27-2 in section 27
808 of that standard for a 100Mb/s repeater.
810 Setting this object to noReset(1) has no effect.
811 The agent will always return the value noReset(1)
812 when this object is read.
814 After receiving a request to set this variable to
815 reset(2), the agent is allowed to delay the reset
816 for a short period. For example, the implementor
817 may choose to delay the reset long enough to allow
818 the SNMP response to be transmitted. In any
819 event, the SNMP response must be transmitted.
821 This action does not reset the management counters
822 defined in this document nor does it affect the
823 portAdminStatus parameters. Included in this
824 action is the execution of a disruptive Self-Test
825 with the following characteristics: a) The nature
826 of the tests is not specified. b) The test resets
827 the repeater but without affecting management
828 information about the repeater. c) The test does
829 not inject packets onto any segment. d) Packets
830 received during the test may or may not be
831 transferred. e) The test does not interfere with
832 management functions.
834 After performing this self-test, the agent will
835 update the repeater health information (including
836 rptrInfoOperStatus), and send a rptrInfoResetEvent
839 "[IEEE 802.3 Mgt], 30.4.1.2.1, acResetRepeater."
840 ::= { rptrInfoEntry 4 }
842 rptrInfoPartitionedPorts OBJECT-TYPE
847 "This object returns the total number of ports in
848 the repeater whose current state meets all three
849 of the following criteria: rptrPortOperStatus
850 does not have the value notPresent(3),
851 rptrPortAdminStatus is enabled(1), and
852 rptrPortAutoPartitionState is autoPartitioned(2)."
853 ::= { rptrInfoEntry 5 }
855 rptrInfoLastChange OBJECT-TYPE
860 "The value of sysUpTime when any of the following
862 1) agent cold- or warm-started;
863 2) this instance of repeater was created
864 (such as when a device or module was
865 added to the system);
866 3) a change in the value of rptrInfoOperStatus;
867 4) ports were added or removed as members of
869 5) any of the counters associated with this
870 repeater had a discontinuity."
871 ::= { rptrInfoEntry 6 }
877 -- Old version of statistics at the repeater level.
879 -- Performance monitoring statistics for the repeater
881 -- In a system containing a single managed repeater-unit,
882 -- the statistics object for the repeater-unit.
884 -- The objects contained under the rptrMonitorRptrInfo subtree are
885 -- intended for backwards compatibility with implementations of
886 -- RFC 1516 [11]. In newer implementations (both single- and
887 -- multiple-repeater implementations), the rptrMonitorTable will
888 -- be implemented. It is the preferred source of this information,
889 -- as it contains the values for all repeaters managed by the
890 -- agent. In all cases, the objects in the rptrMonitorRptrInfo
891 -- subtree are duplicates of the corresponding objects in the
892 -- first entry of the rptrMonitorTable.
895 rptrMonitorTransmitCollisions OBJECT-TYPE
900 "********* THIS OBJECT IS DEPRECATED **********
902 For a clause 9 (10Mb/s) repeater, this counter
903 is incremented every time the repeater state
904 machine enters the TRANSMIT COLLISION state
905 from any state other than ONE PORT LEFT
906 (Ref: Fig 9-2 [IEEE 802.3 Std]).
908 For a clause 27 repeater, this counter is
909 incremented every time the repeater core state
910 diagram enters the Jam state as a result of
911 Activity(ALL) > 1 (fig 27-2 [IEEE 802.3 Std]).
912 The approximate minimum time for rollover of this
913 counter is 16 hours in a 10Mb/s repeater and 1.6
914 hours in a 100Mb/s repeater."
916 "[IEEE 802.3 Mgt], 30.4.1.1.8, aTransmitCollisions."
917 ::= { rptrMonitorRptrInfo 1 }
920 -- Statistics at the group level.
922 -- In a system containing a single managed repeater-unit,
923 -- the statistics objects for each group.
925 rptrMonitorGroupTable OBJECT-TYPE
926 SYNTAX SEQUENCE OF RptrMonitorGroupEntry
927 MAX-ACCESS not-accessible
930 "********* THIS OBJECT IS DEPRECATED **********
932 Table of performance and error statistics for the
933 groups within the repeater. The number of entries
934 is the same as that in the rptrGroupTable."
935 ::= { rptrMonitorGroupInfo 1 }
937 rptrMonitorGroupEntry OBJECT-TYPE
938 SYNTAX RptrMonitorGroupEntry
939 MAX-ACCESS not-accessible
942 "********* THIS OBJECT IS DEPRECATED **********
944 An entry in the table, containing total
945 performance and error statistics for a single
946 group. Regular retrieval of the information in
947 this table provides a means of tracking the
948 performance and health of the networked devices
949 attached to this group's ports.
951 The counters in this table are redundant in the
952 sense that they are the summations of information
953 already available through other objects. However,
954 these sums provide a considerable optimization of
955 network management traffic over the otherwise
956 necessary retrieval of the individual counters
957 included in each sum.
959 Note: Group-level counters are
960 deprecated in this MIB. It is recommended
961 that management applications instead use
962 the repeater-level counters contained in
964 INDEX { rptrMonitorGroupIndex }
965 ::= { rptrMonitorGroupTable 1 }
967 RptrMonitorGroupEntry ::=
969 rptrMonitorGroupIndex
971 rptrMonitorGroupTotalFrames
973 rptrMonitorGroupTotalOctets
975 rptrMonitorGroupTotalErrors
979 rptrMonitorGroupIndex OBJECT-TYPE
980 SYNTAX Integer32 (1..2147483647)
984 "********* THIS OBJECT IS DEPRECATED **********
986 This object identifies the group within the
987 repeater for which this entry contains
989 ::= { rptrMonitorGroupEntry 1 }
991 rptrMonitorGroupTotalFrames OBJECT-TYPE
996 "********* THIS OBJECT IS DEPRECATED **********
998 The total number of frames of valid frame length
999 that have been received on the ports in this group
1000 and for which the FCSError and CollisionEvent
1001 signals were not asserted. This counter is the
1002 summation of the values of the
1003 rptrMonitorPortReadableFrames counters for all of
1004 the ports in the group.
1006 This statistic provides one of the parameters
1007 necessary for obtaining the packet error rate.
1008 The approximate minimum time for rollover of this
1009 counter is 80 hours in a 10Mb/s repeater."
1010 ::= { rptrMonitorGroupEntry 2 }
1012 rptrMonitorGroupTotalOctets OBJECT-TYPE
1014 MAX-ACCESS read-only
1017 "********* THIS OBJECT IS DEPRECATED **********
1019 The total number of octets contained in the valid
1020 frames that have been received on the ports in
1021 this group. This counter is the summation of the
1022 values of the rptrMonitorPortReadableOctets
1023 counters for all of the ports in the group.
1025 This statistic provides an indicator of the total
1026 data transferred. The approximate minimum time
1027 for rollover of this counter is 58 minutes in a
1029 ::= { rptrMonitorGroupEntry 3 }
1031 rptrMonitorGroupTotalErrors OBJECT-TYPE
1033 MAX-ACCESS read-only
1036 "********* THIS OBJECT IS DEPRECATED **********
1038 The total number of errors which have occurred on
1039 all of the ports in this group. This counter is
1040 the summation of the values of the
1041 rptrMonitorPortTotalErrors counters for all of the
1042 ports in the group."
1043 ::= { rptrMonitorGroupEntry 4 }
1046 -- Statistics at the port level.
1049 rptrMonitorPortTable OBJECT-TYPE
1050 SYNTAX SEQUENCE OF RptrMonitorPortEntry
1051 MAX-ACCESS not-accessible
1054 "Table of performance and error statistics for the
1055 ports. The number of entries is the same as that
1056 in the rptrPortTable.
1058 The columnar object rptrMonitorPortLastChange
1059 is used to indicate possible discontinuities
1060 of counter type columnar objects in the table."
1061 ::= { rptrMonitorPortInfo 1 }
1063 rptrMonitorPortEntry OBJECT-TYPE
1064 SYNTAX RptrMonitorPortEntry
1065 MAX-ACCESS not-accessible
1068 "An entry in the table, containing performance and
1069 error statistics for a single port."
1070 INDEX { rptrMonitorPortGroupIndex, rptrMonitorPortIndex }
1071 ::= { rptrMonitorPortTable 1 }
1073 RptrMonitorPortEntry ::=
1075 rptrMonitorPortGroupIndex
1077 rptrMonitorPortIndex
1079 rptrMonitorPortReadableFrames
1081 rptrMonitorPortReadableOctets
1083 rptrMonitorPortFCSErrors
1085 rptrMonitorPortAlignmentErrors
1087 rptrMonitorPortFrameTooLongs
1089 rptrMonitorPortShortEvents
1091 rptrMonitorPortRunts
1093 rptrMonitorPortCollisions
1095 rptrMonitorPortLateEvents
1097 rptrMonitorPortVeryLongEvents
1099 rptrMonitorPortDataRateMismatches
1101 rptrMonitorPortAutoPartitions
1103 rptrMonitorPortTotalErrors
1105 rptrMonitorPortLastChange
1109 rptrMonitorPortGroupIndex OBJECT-TYPE
1110 SYNTAX Integer32 (1..2147483647)
1111 MAX-ACCESS read-only
1114 "This object identifies the group containing the
1115 port for which this entry contains information."
1116 ::= { rptrMonitorPortEntry 1 }
1118 rptrMonitorPortIndex OBJECT-TYPE
1119 SYNTAX Integer32 (1..2147483647)
1120 MAX-ACCESS read-only
1123 "This object identifies the port within the group
1124 for which this entry contains information."
1126 "[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID."
1127 ::= { rptrMonitorPortEntry 2 }
1129 rptrMonitorPortReadableFrames OBJECT-TYPE
1131 MAX-ACCESS read-only
1134 "This object is the number of frames of valid
1135 frame length that have been received on this port.
1136 This counter is incremented by one for each frame
1137 received on this port whose OctetCount is greater
1138 than or equal to minFrameSize and less than or
1139 equal to maxFrameSize (Ref: IEEE 802.3 Std,
1140 4.4.2.1) and for which the FCSError and
1141 CollisionEvent signals are not asserted.
1143 A discontinuity may occur in the value
1144 when the value of object
1145 rptrMonitorPortLastChange changes.
1147 This statistic provides one of the parameters
1148 necessary for obtaining the packet error rate.
1149 The approximate minimum time for rollover of this
1150 counter is 80 hours at 10Mb/s."
1152 "[IEEE 802.3 Mgt], 30.4.3.1.4, aReadableFrames."
1153 ::= { rptrMonitorPortEntry 3 }
1155 rptrMonitorPortReadableOctets OBJECT-TYPE
1157 MAX-ACCESS read-only
1160 "This object is the number of octets contained in
1161 valid frames that have been received on this port.
1162 This counter is incremented by OctetCount for each
1163 frame received on this port which has been
1164 determined to be a readable frame (i.e., including
1165 FCS octets but excluding framing bits and dribble
1168 A discontinuity may occur in the value
1169 when the value of object
1170 rptrMonitorPortLastChange changes.
1172 This statistic provides an indicator of the total
1173 data transferred. The approximate minimum time
1174 for rollover of this counter in a 10Mb/s repeater
1177 For ports receiving traffic at a maximum rate in
1178 a 100Mb/s repeater, this counter can roll over
1179 in less than 6 minutes. Since that amount of time
1180 could be less than a management station's poll cycle
1181 time, in order to avoid a loss of information a
1182 management station is advised to also poll the
1183 rptrMonitorPortUpper32Octets object, or to use the
1184 64-bit counter defined by
1185 rptrMonitorPortHCReadableOctets instead of the
1186 two 32-bit counters."
1188 "[IEEE 802.3 Mgt], 30.4.3.1.5, aReadableOctets."
1189 ::= { rptrMonitorPortEntry 4 }
1191 rptrMonitorPortFCSErrors OBJECT-TYPE
1193 MAX-ACCESS read-only
1196 "This counter is incremented by one for each frame
1197 received on this port with the FCSError signal
1198 asserted and the FramingError and CollisionEvent
1199 signals deasserted and whose OctetCount is greater
1200 than or equal to minFrameSize and less than or
1201 equal to maxFrameSize (Ref: 4.4.2.1, IEEE 802.3
1204 A discontinuity may occur in the value
1205 when the value of object
1206 rptrMonitorPortLastChange changes.
1208 The approximate minimum time for rollover of this
1209 counter is 80 hours at 10Mb/s."
1211 "[IEEE 802.3 Mgt], 30.4.3.1.6,
1212 aFrameCheckSequenceErrors."
1213 ::= { rptrMonitorPortEntry 5 }
1215 rptrMonitorPortAlignmentErrors OBJECT-TYPE
1217 MAX-ACCESS read-only
1220 "This counter is incremented by one for each frame
1221 received on this port with the FCSError and
1222 FramingError signals asserted and CollisionEvent
1223 signal deasserted and whose OctetCount is greater
1224 than or equal to minFrameSize and less than or
1225 equal to maxFrameSize (Ref: IEEE 802.3 Std,
1226 4.4.2.1). If rptrMonitorPortAlignmentErrors is
1227 incremented then the rptrMonitorPortFCSErrors
1228 Counter shall not be incremented for the same
1231 A discontinuity may occur in the value
1232 when the value of object
1233 rptrMonitorPortLastChange changes.
1235 The approximate minimum time for rollover of this
1236 counter is 80 hours at 10Mb/s."
1238 "[IEEE 802.3 Mgt], 30.4.3.1.7, aAlignmentErrors."
1239 ::= { rptrMonitorPortEntry 6 }
1241 rptrMonitorPortFrameTooLongs OBJECT-TYPE
1243 MAX-ACCESS read-only
1246 "This counter is incremented by one for each frame
1247 received on this port whose OctetCount is greater
1248 than maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std).
1249 If rptrMonitorPortFrameTooLongs is incremented
1250 then neither the rptrMonitorPortAlignmentErrors
1251 nor the rptrMonitorPortFCSErrors counter shall be
1252 incremented for the frame.
1254 A discontinuity may occur in the value
1255 when the value of object
1256 rptrMonitorPortLastChange changes.
1258 The approximate minimum time for rollover of this
1259 counter is 61 days in a 10Mb/s repeater."
1261 "[IEEE 802.3 Mgt], 30.4.3.1.8, aFramesTooLong."
1262 ::= { rptrMonitorPortEntry 7 }
1264 rptrMonitorPortShortEvents OBJECT-TYPE
1266 MAX-ACCESS read-only
1269 "This counter is incremented by one for each
1270 CarrierEvent on this port with ActivityDuration
1271 less than ShortEventMaxTime. ShortEventMaxTime is
1272 greater than 74 bit times and less than 82 bit
1273 times. ShortEventMaxTime has tolerances included
1274 to provide for circuit losses between a
1275 conformance test point at the AUI and the
1276 measurement point within the state machine.
1280 ShortEvents may indicate externally
1281 generated noise hits which will cause the repeater
1282 to transmit Runts to its other ports, or propagate
1283 a collision (which may be late) back to the
1284 transmitting DTE and damaged frames to the rest of
1287 Implementors may wish to consider selecting the
1288 ShortEventMaxTime towards the lower end of the
1289 allowed tolerance range to accommodate bit losses
1290 suffered through physical channel devices not
1291 budgeted for within this standard.
1293 The significance of this attribute is different
1294 in 10 and 100 Mb/s collision domains. Clause 9
1295 repeaters perform fragment extension of short
1296 events which would be counted as runts on the
1297 interconnect ports of other repeaters. Clause
1298 27 repeaters do not perform fragment extension.
1300 A discontinuity may occur in the value
1301 when the value of object
1302 rptrMonitorPortLastChange changes.
1304 The approximate minimum time for rollover of this
1305 counter is 16 hours in a 10Mb/s repeater."
1307 "[IEEE 802.3 Mgt], 30.4.3.1.9, aShortEvents."
1308 ::= { rptrMonitorPortEntry 8 }
1310 rptrMonitorPortRunts OBJECT-TYPE
1312 MAX-ACCESS read-only
1315 "This counter is incremented by one for each
1316 CarrierEvent on this port that meets one of the
1317 following two conditions. Only one test need be
1318 made. a) The ActivityDuration is greater than
1319 ShortEventMaxTime and less than ValidPacketMinTime
1320 and the CollisionEvent signal is deasserted. b)
1321 The OctetCount is less than 64, the
1322 ActivityDuration is greater than ShortEventMaxTime
1323 and the CollisionEvent signal is deasserted.
1324 ValidPacketMinTime is greater than or equal to 552
1325 bit times and less than 565 bit times.
1327 An event whose length is greater than 74 bit times
1328 but less than 82 bit times shall increment either
1329 the shortEvents counter or the runts counter but
1330 not both. A CarrierEvent greater than or equal to
1331 552 bit times but less than 565 bit times may or
1332 may not be counted as a runt.
1334 ValidPacketMinTime has tolerances included to
1335 provide for circuit losses between a conformance
1336 test point at the AUI and the measurement point
1337 within the state machine.
1339 Runts usually indicate collision fragments, a
1340 normal network event. In certain situations
1341 associated with large diameter networks a
1342 percentage of collision fragments may exceed
1344 A discontinuity may occur in the value
1345 when the value of object
1346 rptrMonitorPortLastChange changes.
1348 The approximate minimum time for rollover of this
1349 counter is 16 hours in a 10Mb/s repeater."
1351 "[IEEE 802.3 Mgt], 30.4.3.1.10, aRunts."
1352 ::= { rptrMonitorPortEntry 9 }
1354 rptrMonitorPortCollisions OBJECT-TYPE
1356 MAX-ACCESS read-only
1359 "For a clause 9 repeater, this counter is
1360 incremented by one for any CarrierEvent signal
1361 on any port for which the CollisionEvent signal
1362 on this port is asserted. For a clause 27
1363 repeater port the counter increments on entering
1364 the Collision Count Increment state of the
1365 partition state diagram (fig 27-8 of
1368 A discontinuity may occur in the value
1369 when the value of object
1370 rptrMonitorPortLastChange changes.
1372 The approximate minimum time for rollover of this
1373 counter is 16 hours in a 10Mb/s repeater."
1375 "[IEEE 802.3 Mgt], 30.4.3.1.11, aCollisions."
1376 ::= { rptrMonitorPortEntry 10 }
1378 rptrMonitorPortLateEvents OBJECT-TYPE
1380 MAX-ACCESS read-only
1383 "For a clause 9 repeater port, this counter is
1384 incremented by one for each CarrierEvent
1385 on this port in which the CollIn(X)
1386 variable transitions to the value SQE (Ref:
1387 9.6.6.2, IEEE 802.3 Std) while the
1388 ActivityDuration is greater than the
1389 LateEventThreshold. For a clause 27 repeater
1390 port, this counter is incremented by one on
1391 entering the Collision Count Increment state
1392 of the partition state diagram (fig 27-8)
1393 while the ActivityDuration is greater than
1394 the LateEvent- Threshold. Such a CarrierEvent
1395 is counted twice, as both a collision and as a
1398 The LateEventThreshold is greater than 480 bit
1399 times and less than 565 bit times.
1400 LateEventThreshold has tolerances included to
1401 permit an implementation to build a single
1402 threshold to serve as both the LateEventThreshold
1403 and ValidPacketMinTime threshold.
1405 A discontinuity may occur in the value
1406 when the value of object
1407 rptrMonitorPortLastChange changes.
1409 The approximate minimum time for rollover of this
1410 counter is 81 hours in a 10Mb/s repeater."
1412 "[IEEE 802.3 Mgt], 30.4.3.1.12, aLateEvents."
1413 ::= { rptrMonitorPortEntry 11 }
1415 rptrMonitorPortVeryLongEvents OBJECT-TYPE
1417 MAX-ACCESS read-only
1420 "For a clause 9 repeater port, this counter
1421 is incremented by one for each CarrierEvent
1422 whose ActivityDuration is greater than the
1423 MAU Jabber Lockup Protection timer TW3
1424 (Ref: 9.6.1 & 9.6.5, IEEE 802.3 Std).
1426 For a clause 27 repeater port, this counter
1427 is incremented by one on entry to the
1428 Rx Jabber state of the receiver timer state
1429 diagram (fig 27-7). Other counters may
1430 be incremented as appropriate.
1432 A discontinuity may occur in the value
1433 when the value of object
1434 rptrMonitorPortLastChange changes."
1436 "[IEEE 802.3 Mgt], 30.4.3.1.13, aVeryLongEvents."
1437 ::= { rptrMonitorPortEntry 12 }
1439 rptrMonitorPortDataRateMismatches OBJECT-TYPE
1441 MAX-ACCESS read-only
1444 "This counter is incremented by one for each
1445 frame received by this port that meets all
1446 of the conditions required by only one of the
1447 following two measurement methods:
1449 Measurement method A: 1) The CollisionEvent
1450 signal is not asserted (10Mb/s operation) or
1451 the Collision Count Increment state of the
1452 partition state diagram (fig 27-8 of
1453 [IEEE 802.3 Std]) has not been entered
1454 (100Mb/s operation). 2) The ActivityDuration
1455 is greater than ValidPacketMinTime. 3) The
1456 frequency (data rate) is detectably mismatched
1457 from the local transmit frequency.
1459 Measurement method B: 1) The CollisionEvent
1460 signal is not asserted (10Mb/s operation)
1461 or the Collision Count Increment state of the
1462 partition state diagram (fig 27-8 of
1463 [IEEE 802.3 Std]) has not been entered
1464 (100Mb/s operation). 2) The OctetCount is
1465 greater than 63. 3) The frequency (data
1466 rate) is detectably mismatched from the local
1467 transmit frequency. The exact degree of
1468 mismatch is vendor specific and is to be
1469 defined by the vendor for conformance testing.
1471 When this event occurs, other counters whose
1472 increment conditions were satisfied may or may not
1473 also be incremented, at the implementor's
1474 discretion. Whether or not the repeater was able
1475 to maintain data integrity is beyond the scope of
1478 A discontinuity may occur in the value
1479 when the value of object
1480 rptrMonitorPortLastChange changes."
1482 "[IEEE 802.3 Mgt], 30.4.3.1.14, aDataRateMismatches."
1483 ::= { rptrMonitorPortEntry 13 }
1485 rptrMonitorPortAutoPartitions OBJECT-TYPE
1487 MAX-ACCESS read-only
1490 "This counter is incremented by one for
1491 each time the repeater has automatically
1492 partitioned this port.
1494 The conditions that cause a clause 9
1495 repeater port to partition are specified in
1496 the partition state diagram in clause 9 of
1497 [IEEE 802.3 Std]. They are not differentiated
1498 here. A clause 27 repeater port partitions
1499 on entry to the Partition Wait state of the
1500 partition state diagram (fig 27-8 in
1503 A discontinuity may occur in the value
1504 when the value of object
1505 rptrMonitorPortLastChange changes."
1507 "[IEEE 802.3 Mgt], 30.4.3.1.15, aAutoPartitions."
1508 ::= { rptrMonitorPortEntry 14 }
1510 rptrMonitorPortTotalErrors OBJECT-TYPE
1512 MAX-ACCESS read-only
1515 "The total number of errors which have occurred on
1516 this port. This counter is the summation of the
1517 values of other error counters (for the same
1520 rptrMonitorPortFCSErrors,
1521 rptrMonitorPortAlignmentErrors,
1522 rptrMonitorPortFrameTooLongs,
1523 rptrMonitorPortShortEvents,
1524 rptrMonitorPortLateEvents,
1525 rptrMonitorPortVeryLongEvents,
1526 rptrMonitorPortDataRateMismatches, and
1527 rptrMonitorPortSymbolErrors.
1529 This counter is redundant in the sense that it is
1530 the summation of information already available
1531 through other objects. However, it is included
1532 specifically because the regular retrieval of this
1533 object as a means of tracking the health of a port
1534 provides a considerable optimization of network
1535 management traffic over the otherwise necessary
1536 retrieval of the summed counters.
1538 Note that rptrMonitorPortRunts is not included
1539 in this total; this is because runts usually
1540 indicate collision fragments, a normal network
1543 A discontinuity may occur in the value
1544 when the value of object
1545 rptrMonitorPortLastChange changes."
1546 ::= { rptrMonitorPortEntry 15 }
1548 rptrMonitorPortLastChange OBJECT-TYPE
1550 MAX-ACCESS read-only
1553 "The value of sysUpTime when the last of
1554 the following occurred:
1555 1) the agent cold- or warm-started;
1556 2) the row for the port was created
1557 (such as when a device or module was added
1559 3) any condition that would cause one of
1560 the counters for the row to experience
1562 ::= { rptrMonitorPortEntry 16 }
1564 rptrMonitor100PortTable OBJECT-TYPE
1565 SYNTAX SEQUENCE OF RptrMonitor100PortEntry
1566 MAX-ACCESS not-accessible
1569 "Table of additional performance and error
1570 statistics for 100Mb/s ports, above and
1571 beyond those parameters that apply to both
1572 10 and 100Mbps ports. Entries exist only for
1573 ports attached to 100Mbps repeaters.
1575 The columnar object rptrMonitorPortLastChange
1576 is used to indicate possible discontinuities
1577 of counter type columnar objects in this table."
1578 ::= { rptrMonitorPortInfo 2 }
1580 rptrMonitor100PortEntry OBJECT-TYPE
1581 SYNTAX RptrMonitor100PortEntry
1582 MAX-ACCESS not-accessible
1585 "An entry in the table, containing performance
1586 and error statistics for a single 100Mb/s port."
1587 INDEX { rptrMonitorPortGroupIndex, rptrMonitorPortIndex }
1588 ::= { rptrMonitor100PortTable 1 }
1590 RptrMonitor100PortEntry ::=
1592 rptrMonitorPortIsolates
1594 rptrMonitorPortSymbolErrors
1596 rptrMonitorPortUpper32Octets
1598 rptrMonitorPortHCReadableOctets
1602 rptrMonitorPortIsolates OBJECT-TYPE
1604 MAX-ACCESS read-only
1607 "This counter is incremented by one each time that
1608 the repeater port automatically isolates as a
1609 consequence of false carrier events. The conditions
1610 which cause a port to automatically isolate are
1611 defined by the transition from the False Carrier
1612 state to the Link Unstable state of the carrier
1613 integrity state diagram (figure 27-9)
1614 [IEEE 802.3 Standard].
1616 Note: Isolates do not affect the value of
1617 the PortOperStatus object.
1619 A discontinuity may occur in the value
1620 when the value of object
1621 rptrMonitorPortLastChange changes."
1623 "[IEEE 802.3 Mgt], 30.4.3.1.16, aIsolates."
1624 ::= { rptrMonitor100PortEntry 1 }
1626 rptrMonitorPortSymbolErrors OBJECT-TYPE
1628 MAX-ACCESS read-only
1631 "This counter is incremented by one each time when
1632 valid length packet was received at the port and
1633 there was at least one occurrence of an invalid
1634 data symbol. This can increment only once per valid
1635 carrier event. A collision presence at any port of
1636 the repeater containing port N, will not cause this
1637 attribute to increment.
1639 A discontinuity may occur in the value
1640 when the value of object
1641 rptrMonitorPortLastChange changes.
1643 The approximate minimum time for rollover of this
1644 counter is 7.4 hours at 100Mb/s."
1646 "[IEEE 802.3 Mgt], 30.4.3.1.17,
1647 aSymbolErrorDuringPacket."
1648 ::= { rptrMonitor100PortEntry 2 }
1650 rptrMonitorPortUpper32Octets OBJECT-TYPE
1652 MAX-ACCESS read-only
1655 "This object is the number of octets contained in
1656 valid frames that have been received on this port,
1657 modulo 2**32. That is, it contains the upper 32
1658 bits of a 64-bit octets counter, of which the
1659 lower 32 bits are contained in the
1660 rptrMonitorPortReadableOctets object.
1662 This two-counter mechanism is provided for those
1663 network management protocols that do not support
1664 64-bit counters (e.g. SNMP V1) and are used to
1665 manage a repeater type of 100Mb/s.
1667 Conformance clauses for this MIB are defined such
1668 that implementation of this object is not required
1669 in a system which does not support 100Mb/s.
1670 However, systems with mixed 10 and 100Mb/s ports
1671 may implement this object across all ports,
1672 including 10Mb/s. If this object is implemented,
1673 it must be according to the definition in the first
1674 paragraph of this description; that is, the value
1675 of this object MUST be a valid count.
1677 A discontinuity may occur in the value
1678 when the value of object
1679 rptrMonitorPortLastChange changes."
1680 ::= { rptrMonitor100PortEntry 3 }
1682 rptrMonitorPortHCReadableOctets OBJECT-TYPE
1684 MAX-ACCESS read-only
1687 "This object is the number of octets contained in
1688 valid frames that have been received on this port.
1689 This counter is incremented by OctetCount for each
1690 frame received on this port which has been
1691 determined to be a readable frame (i.e., including
1692 FCS octets but excluding framing bits and dribble
1695 This statistic provides an indicator of the total
1698 This counter is a 64-bit version of rptrMonitor-
1699 PortReadableOctets. It should be used by network
1700 management protocols which suppport 64-bit counters
1703 Conformance clauses for this MIB are defined such
1704 that implementation of this object is not required
1705 in a system which does not support 100Mb/s.
1706 However, systems with mixed 10 and 100Mb/s ports
1707 may implement this object across all ports,
1708 including 10Mb/s. If this object is implemented,
1709 it must be according to the definition in the first
1710 paragraph of this description; that is, the value
1711 of this object MUST be a valid count.
1713 A discontinuity may occur in the value
1714 when the value of object
1715 rptrMonitorPortLastChange changes."
1717 "[IEEE 802.3 Mgt], 30.4.3.1.5, aReadableOctets."
1718 ::= { rptrMonitor100PortEntry 4 }
1721 -- New version of statistics at the repeater level.
1723 -- Statistics objects for each managed repeater
1726 rptrMonTable OBJECT-TYPE
1727 SYNTAX SEQUENCE OF RptrMonEntry
1728 MAX-ACCESS not-accessible
1731 "A table of information about each
1732 non-trivial repeater. The number of entries
1733 in this table is the same as the number of
1734 entries in the rptrInfoTable.
1736 The columnar object rptrInfoLastChange is
1737 used to indicate possible discontinuities of
1738 counter type columnar objects in this table."
1739 ::= { rptrMonitorAllRptrInfo 1 }
1741 rptrMonEntry OBJECT-TYPE
1743 MAX-ACCESS not-accessible
1746 "An entry in the table, containing information
1747 about a single non-trivial repeater."
1748 INDEX { rptrInfoId }
1749 ::= { rptrMonTable 1 }
1763 rptrMonTxCollisions OBJECT-TYPE
1765 MAX-ACCESS read-only
1768 "For a clause 9 (10Mb/s) repeater, this counter
1769 is incremented every time the repeater state
1770 machine enters the TRANSMIT COLLISION state
1771 from any state other than ONE PORT LEFT
1772 (Ref: Fig 9-2 [IEEE 802.3 Std]).
1774 For a clause 27 repeater, this counter is
1775 incremented every time the repeater core state
1776 diagram enters the Jam state as a result of
1777 Activity(ALL) > 1 (fig 27-2 [IEEE 802.3 Std]).
1779 The approximate minimum time for rollover of this
1780 counter is 16 hours in a 10Mb/s repeater and 1.6
1781 hours in a 100Mb/s repeater."
1783 "[IEEE 802.3 Mgt], 30.4.1.1.8, aTransmitCollisions"
1784 ::= { rptrMonEntry 1 }
1786 rptrMonTotalFrames OBJECT-TYPE
1788 MAX-ACCESS read-only
1791 "The number of frames of valid frame length
1792 that have been received on the ports in this repeater
1793 and for which the FCSError and CollisionEvent
1794 signals were not asserted. If an implementation
1795 can not obtain a count of frames as seen by
1796 the repeater itself, this counter may be
1797 implemented as the summation of the values of the
1798 rptrMonitorPortReadableFrames counters for all of
1799 the ports in the repeater.
1801 This statistic provides one of the parameters
1802 necessary for obtaining the packet error rate.
1803 The approximate minimum time for rollover of this
1804 counter is 80 hours in a 10Mb/s repeater."
1805 ::= { rptrMonEntry 3 }
1807 rptrMonTotalErrors OBJECT-TYPE
1809 MAX-ACCESS read-only
1812 "The total number of errors which have occurred on
1813 all of the ports in this repeater. The errors
1814 included in this count are the same as those listed
1815 for the rptrMonitorPortTotalErrors counter. If an
1816 implementation can not obtain a count of these
1817 errors as seen by the repeater itself, this counter
1818 may be implemented as the summation of the values of
1819 the rptrMonitorPortTotalErrors counters for all of
1820 the ports in the repeater."
1821 ::= { rptrMonEntry 4 }
1823 rptrMonTotalOctets OBJECT-TYPE
1825 MAX-ACCESS read-only
1828 "The total number of octets contained in the valid
1829 frames that have been received on the ports in
1830 this group. If an implementation can not obtain
1831 a count of octets as seen by the repeater itself,
1832 this counter may be the summation of the
1833 values of the rptrMonitorPortReadableOctets
1834 counters for all of the ports in the group.
1836 This statistic provides an indicator of the total
1837 data transferred. The approximate minimum time
1838 for rollover of this counter in a 10Mb/s repeater
1839 is 58 minutes divided by the number of ports in
1842 For 100Mb/s repeaters processing traffic at a
1843 maximum rate, this counter can roll over in less
1844 than 6 minutes divided by the number of ports in
1845 the repeater. Since that amount of time could
1846 be less than a management station's poll cycle
1847 time, in order to avoid a loss of information a
1848 management station is advised to also poll the
1849 rptrMonUpper32TotalOctets object, or to use the
1850 64-bit counter defined by rptrMonHCTotalOctets
1851 instead of the two 32-bit counters."
1852 ::= { rptrMonEntry 5 }
1854 rptrMon100Table OBJECT-TYPE
1855 SYNTAX SEQUENCE OF RptrMon100Entry
1856 MAX-ACCESS not-accessible
1859 "A table of additional information about each
1860 100Mb/s repeater, augmenting the entries in
1861 the rptrMonTable. Entries exist in this table
1862 only for 100Mb/s repeaters.
1864 The columnar object rptrInfoLastChange is
1865 used to indicate possible discontinuities of
1866 counter type columnar objects in this table."
1867 ::= { rptrMonitorAllRptrInfo 2 }
1869 rptrMon100Entry OBJECT-TYPE
1870 SYNTAX RptrMon100Entry
1871 MAX-ACCESS not-accessible
1874 "An entry in the table, containing information
1875 about a single 100Mbps repeater."
1876 INDEX { rptrInfoId }
1877 ::= { rptrMon100Table 1 }
1881 rptrMonUpper32TotalOctets
1883 rptrMonHCTotalOctets
1887 rptrMonUpper32TotalOctets OBJECT-TYPE
1889 MAX-ACCESS read-only
1892 "The total number of octets contained in the valid
1893 frames that have been received on the ports in
1894 this repeater, modulo 2**32. That is, it contains
1895 the upper 32 bits of a 64-bit counter, of which
1896 the lower 32 bits are contained in the
1897 rptrMonTotalOctets object. If an implementation
1898 can not obtain a count of octets as seen
1899 by the repeater itself, the 64-bit value
1900 may be the summation of the values of the
1901 rptrMonitorPortReadableOctets counters combined
1902 with the corresponding rptrMonitorPortUpper32Octets
1903 counters for all of the ports in the repeater.
1905 This statistic provides an indicator of the total
1906 data transferred within the repeater.
1908 This two-counter mechanism is provided for those
1909 network management protocols that do not support
1910 64-bit counters (e.g. SNMP V1) and are used to
1911 manage a repeater type of 100Mb/s.
1913 Conformance clauses for this MIB are defined such
1914 that implementation of this object is not required
1915 in a system which does not support 100Mb/s.
1916 However, systems with mixed 10 and 100Mb/s ports
1917 may implement this object across all ports,
1918 including 10Mb/s. If this object is implemented,
1919 it must be according to the definition in the first
1920 paragraph of this description; that is, the value
1921 of this object MUST be a valid count."
1922 ::= { rptrMon100Entry 1 }
1924 rptrMonHCTotalOctets OBJECT-TYPE
1926 MAX-ACCESS read-only
1929 "The total number of octets contained in the valid
1930 frames that have been received on the ports in
1931 this group. If a implementation can not obtain
1932 a count of octets as seen by the repeater itself,
1933 this counter may be the summation of the
1934 values of the rptrMonitorPortReadableOctets
1935 counters for all of the ports in the group.
1937 This statistic provides an indicator of the total
1940 This counter is a 64-bit (high-capacity) version
1941 of rptrMonUpper32TotalOctets and rptrMonTotalOctets.
1942 It should be used by network management protocols
1943 which support 64-bit counters (e.g. SNMPv2).
1945 Conformance clauses for this MIB are defined such
1946 that implementation of this object is not required
1947 in a system which does not support 100Mb/s.
1948 However, systems with mixed 10 and 100Mb/s ports
1949 may implement this object across all ports,
1950 including 10Mb/s. If this object is implemented,
1951 it must be according to the definition in the first
1952 paragraph of this description; that is, the value
1953 of this object MUST be a valid count."
1954 ::= { rptrMon100Entry 2 }
1958 -- The Repeater Address Search Table
1960 -- This table provides an active address tracking
1961 -- capability which can be also used to collect the
1962 -- necessary information for mapping the topology
1963 -- of a network. Note that an NMS is required to have
1964 -- read-write access to the table in order to access
1965 -- this function. Section 4, "Topology Mapping",
1966 -- contains a description of an algorithm which can
1967 -- make use of this table, in combination with the
1969 -- forwarding databases of managed bridges/switches
1970 -- in the network, to map network topology.
1973 rptrAddrSearchTable OBJECT-TYPE
1974 SYNTAX SEQUENCE OF RptrAddrSearchEntry
1975 MAX-ACCESS not-accessible
1978 "This table contains one entry per repeater in the
1979 system. It defines objects which allow a network
1980 management application to instruct an agent to watch
1981 for a given MAC address and report which port it
1982 was seen on. Only one address search can be in
1983 progress on each repeater at any one time. Before
1984 starting an address search, a management application
1985 should obtain 'ownership' of the entry in
1986 rptrAddrSearchTable for the repeater that is to
1987 perform the search. This is accomplished with the
1988 rptrAddrSearchLock and rptrAddrSearchStatus as
1992 get(rptrAddrSearchLock, rptrAddrSearchStatus)
1993 while (rptrAddrSearchStatus != notInUse)
1995 /* Loop waiting for objects to be available*/
1997 get(rptrAddrSearchLock, rptrAddrSearchStatus)
2000 /* Try to claim map objects */
2001 lock_value = rptrAddrSearchLock
2002 if ( set(rptrAddrSearchLock = lock_value,
2003 rptrAddrSearchStatus = inUse,
2004 rptrAddrSearchOwner = 'my-IP-address)
2006 /* Another manager got the lock */
2009 /* I have the lock */
2010 set (rptrAddrSearchAddress = <search target>)
2012 wait for rptrAddrSearchState to change from none
2014 if (rptrAddrSearchState == single)
2015 get (rptrAddrSearchGroup, rptrAddrSearchPort)
2016 /* release the lock, making sure not to overwrite
2017 anyone else's lock */
2018 set (rptrAddrSearchLock = lock_value+1,
2019 rptrAddrSearchStatus = notInUse,
2020 rptrAddrSearchOwner = '')
2022 A management station first retrieves the values of
2023 the appropriate instances of the rptrAddrSearchLock
2024 and rptrAddrSearchStatus objects, periodically
2025 repeating the retrieval if necessary, until the value
2026 of rptrAddrSearchStatus is 'notInUse'. The
2027 management station then tries to set the same
2028 instance of the rptrAddrSearchLock object to the
2029 value it just retrieved, the same instance of the
2030 rptrAddrSearchStatus object to 'inUse', and the
2031 corresponding instance of rptrAddrSearchOwner to a
2032 value indicating itself. If the set operation
2033 succeeds, then the management station has obtained
2034 ownership of the rptrAddrSearchEntry, and the value
2035 of rptrAddrSearchLock is incremented by the agent (as
2036 per the semantics of TestAndIncr). Failure of the
2037 set operation indicates that some other manager has
2038 obtained ownership of the rptrAddrSearchEntry.
2040 Once ownership is obtained, the management station
2041 can proceed with the search operation. Note that the
2042 agent will reset rptrAddrSearchStatus to 'notInUse'
2043 if it has been in the 'inUse' state for an abnormally
2044 long period of time, to prevent a misbehaving manager
2045 from permanently locking the entry. It is suggested
2046 that this timeout period be between one and five
2049 When the management station has completed its search
2050 operation, it should free the entry by setting
2051 the instance of the rptrAddrSearchLock object to the
2052 previous value + 1, the instance of the
2053 rptrAddrSearchStatus to 'notInUse', and the instance
2054 of rptrAddrSearchOwner to a zero length string. This
2055 is done to prevent overwriting another station's
2057 ::= { rptrAddrTrackRptrInfo 1 }
2059 rptrAddrSearchEntry OBJECT-TYPE
2060 SYNTAX RptrAddrSearchEntry
2061 MAX-ACCESS not-accessible
2064 "An entry containing objects for invoking an address
2065 search on a repeater."
2066 INDEX { rptrInfoId }
2067 ::= { rptrAddrSearchTable 1 }
2069 RptrAddrSearchEntry ::=
2071 rptrAddrSearchLock TestAndIncr,
2072 rptrAddrSearchStatus INTEGER,
2073 rptrAddrSearchAddress MacAddress,
2074 rptrAddrSearchState INTEGER,
2075 rptrAddrSearchGroup Integer32,
2076 rptrAddrSearchPort Integer32,
2077 rptrAddrSearchOwner OwnerString
2081 rptrAddrSearchLock OBJECT-TYPE
2083 MAX-ACCESS read-write
2086 "This object is used by a management station as an
2087 advisory lock for this rptrAddrSearchEntry."
2088 ::= { rptrAddrSearchEntry 1 }
2090 rptrAddrSearchStatus OBJECT-TYPE
2095 MAX-ACCESS read-write
2098 "This object is used to indicate that some management
2099 station is currently using this rptrAddrSearchEntry.
2100 Cooperating managers should set this object to
2101 'notInUse' when they are finished using this entry.
2102 The agent will automatically set the value of this
2103 object to 'notInUse' if it has been set to 'inUse'
2104 for an unusually long period of time."
2105 ::= { rptrAddrSearchEntry 2 }
2107 rptrAddrSearchAddress OBJECT-TYPE
2109 MAX-ACCESS read-write
2112 "This object is used to search for a specified MAC
2113 address. When this object is set, an address search
2114 begins. This automatically sets the corresponding
2115 instance of the rptrAddrSearchState object to 'none'
2116 and the corresponding instances of the
2117 rptrAddrSearchGroup and rptrAddrSearchPort objects to
2120 When a valid frame is received by this repeater with
2121 a source MAC address which matches the current value
2122 of rptrAddrSearchAddress, the agent will update the
2123 corresponding instances of rptrAddrSearchState,
2124 rptrAddrSearchGroup and rptrAddrSearchPort to reflect
2125 the current status of the search, and the group and
2126 port on which the frame was seen."
2127 ::= { rptrAddrSearchEntry 3 }
2129 rptrAddrSearchState OBJECT-TYPE
2135 MAX-ACCESS read-only
2138 "The current state of the MAC address search on this
2139 repeater. This object is initialized to 'none' when
2140 the corresponding instance of rptrAddrSearchAddress
2141 is set. If the agent detects the address on exactly
2142 one port, it will set this object to 'single', and
2143 set the corresponding instances of
2144 rptrAddrSearchGroup and rptrAddrSearchPort to reflect
2145 the group and port on which the address was heard.
2146 If the agent detects the address on more than one
2147 port, it will set this object to 'multiple'."
2148 ::= { rptrAddrSearchEntry 4 }
2150 rptrAddrSearchGroup OBJECT-TYPE
2151 SYNTAX Integer32 (0..2147483647)
2152 MAX-ACCESS read-only
2155 "The group from which an error-free frame whose
2156 source address is equal to the corresponding instance
2157 of rptrAddrSearchAddress has been received. The
2158 value of this object is undefined when the
2159 corresponding instance of rptrAddrSearchState is
2160 equal to 'none' or 'multiple'."
2161 ::= { rptrAddrSearchEntry 5 }
2163 rptrAddrSearchPort OBJECT-TYPE
2164 SYNTAX Integer32 (0..2147483647)
2165 MAX-ACCESS read-only
2168 "The port rom which an error-free frame whose
2169 source address is equal to the corresponding instance
2170 of rptrAddrSearchAddress has been received. The
2171 value of this object is undefined when the
2172 corresponding instance of rptrAddrSearchState is
2173 equal to 'none' or 'multiple'."
2174 ::= { rptrAddrSearchEntry 6 }
2176 rptrAddrSearchOwner OBJECT-TYPE
2178 MAX-ACCESS read-write
2181 "The entity which currently has 'ownership' of this
2182 rptrAddrSearchEntry."
2183 ::= { rptrAddrSearchEntry 7 }
2187 -- The Port Address Tracking Table
2189 -- This table provides a way for a network management
2190 -- application to passively gather information (using
2191 -- read-only privileges) about which network addresses
2192 -- are connected to which ports of a repeater.
2195 rptrAddrTrackTable OBJECT-TYPE
2196 SYNTAX SEQUENCE OF RptrAddrTrackEntry
2197 MAX-ACCESS not-accessible
2200 "Table of address mapping information about the
2202 ::= { rptrAddrTrackPortInfo 1 }
2204 rptrAddrTrackEntry OBJECT-TYPE
2205 SYNTAX RptrAddrTrackEntry
2206 MAX-ACCESS not-accessible
2209 "An entry in the table, containing address mapping
2210 information about a single port."
2211 INDEX { rptrAddrTrackGroupIndex, rptrAddrTrackPortIndex }
2212 ::= { rptrAddrTrackTable 1 }
2214 RptrAddrTrackEntry ::=
2216 rptrAddrTrackGroupIndex
2218 rptrAddrTrackPortIndex
2220 rptrAddrTrackLastSourceAddress -- DEPRECATED OBJECT
2222 rptrAddrTrackSourceAddrChanges
2224 rptrAddrTrackNewLastSrcAddress
2226 rptrAddrTrackCapacity
2230 rptrAddrTrackGroupIndex OBJECT-TYPE
2231 SYNTAX INTEGER (1..2147483647)
2232 MAX-ACCESS read-only
2235 "This object identifies the group containing the
2236 port for which this entry contains information."
2237 ::= { rptrAddrTrackEntry 1 }
2239 rptrAddrTrackPortIndex OBJECT-TYPE
2240 SYNTAX INTEGER (1..2147483647)
2241 MAX-ACCESS read-only
2244 "This object identifies the port within the group
2245 for which this entry contains information."
2247 "[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID."
2248 ::= { rptrAddrTrackEntry 2 }
2250 rptrAddrTrackLastSourceAddress OBJECT-TYPE
2252 MAX-ACCESS read-only
2255 "********* THIS OBJECT IS DEPRECATED **********
2256 This object is the SourceAddress of the last
2257 readable frame (i.e., counted by
2258 rptrMonitorPortReadableFrames) received by this
2261 This object has been deprecated because its value
2262 is undefined when no frames have been observed on
2263 this port. The replacement object is
2264 rptrAddrTrackNewLastSrcAddress."
2266 "[IEEE 802.3 Mgt], 30.4.3.1.18, aLastSourceAddress."
2267 ::= { rptrAddrTrackEntry 3 }
2269 rptrAddrTrackSourceAddrChanges OBJECT-TYPE
2271 MAX-ACCESS read-only
2274 "This counter is incremented by one for each time
2275 that the rptrAddrTrackLastSourceAddress attribute
2276 for this port has changed.
2278 This may indicate whether a link is connected to a
2279 single DTE or another multi-user segment.
2281 A discontinuity may occur in the value when the
2282 value of object rptrMonitorPortLastChange changes.
2284 The approximate minimum time for rollover of this
2285 counter is 81 hours in a 10Mb/s repeater."
2287 "[IEEE 802.3 Mgt], 30.4.3.1.19, aSourceAddressChanges."
2288 ::= { rptrAddrTrackEntry 4 }
2290 rptrAddrTrackNewLastSrcAddress OBJECT-TYPE
2292 MAX-ACCESS read-only
2295 "This object is the SourceAddress of the last
2296 readable frame (i.e., counted by
2297 rptrMonitorPortReadableFrames) received by this
2298 port. If no frames have been received by this
2299 port since the agent began monitoring the port
2300 activity, the agent shall return a string of
2303 "[IEEE 802.3 Mgt], 30.4.3.1.18, aLastSourceAddress."
2304 ::= { rptrAddrTrackEntry 5 }
2306 rptrAddrTrackCapacity OBJECT-TYPE
2308 MAX-ACCESS read-only
2311 "The maximum number of addresses that can be
2312 detected on this port. This value indicates
2313 to the maximum number of entries in the
2314 rptrExtAddrTrackTable relative to this port.
2316 If this object has the value of 1, the agent
2317 implements only the LastSourceAddress mechanism
2318 described by RFC 1368 or RFC 1516."
2319 ::= { rptrAddrTrackEntry 6 }
2322 -- Table for multiple addresses per port
2324 rptrExtAddrTrackTable OBJECT-TYPE
2325 SYNTAX SEQUENCE OF RptrExtAddrTrackEntry
2326 MAX-ACCESS not-accessible
2329 "A table to extend the address tracking table (i.e.,
2330 rptrAddrTrackTable) with a list of source MAC
2331 addresses that were recently received on each port.
2332 The number of ports is the same as the number
2333 of entries in table rptrPortTable. The number of
2334 entries in this table depends on the agent/repeater
2335 implementation and the number of different
2336 addresses received on each port.
2338 The first entry for each port contains
2339 the same MAC address that is given by the
2340 rptrAddrTrackNewLastSrcAddress for that port.
2342 Entries in this table for a particular port are
2343 retained when that port is switched from one
2344 repeater to another.
2346 The ordering of MAC addresses listed for a
2347 particular port is implementation dependent."
2348 ::= { rptrAddrTrackPortInfo 2 }
2350 rptrExtAddrTrackEntry OBJECT-TYPE
2351 SYNTAX RptrExtAddrTrackEntry
2352 MAX-ACCESS not-accessible
2355 "A row in the table of extended address tracking
2356 information for ports. Entries can not be directly
2357 created or deleted via SNMP operations."
2358 INDEX { rptrAddrTrackGroupIndex,
2359 rptrAddrTrackPortIndex,
2360 rptrExtAddrTrackMacIndex }
2361 ::= { rptrExtAddrTrackTable 1 }
2363 RptrExtAddrTrackEntry ::= SEQUENCE {
2364 rptrExtAddrTrackMacIndex Integer32,
2365 rptrExtAddrTrackSourceAddress MacAddress
2368 rptrExtAddrTrackMacIndex OBJECT-TYPE
2369 SYNTAX Integer32 (1..2147483647)
2370 MAX-ACCESS read-only
2373 "The index of a source MAC address seen on
2376 The ordering of MAC addresses listed for a
2377 particular port is implementation dependent.
2379 There is no implied relationship between a
2380 particular index and a particular MAC
2381 address. The index for a particular MAC
2382 address may change without notice."
2383 ::= { rptrExtAddrTrackEntry 1 }
2385 rptrExtAddrTrackSourceAddress OBJECT-TYPE
2387 MAX-ACCESS read-only
2390 "The source MAC address from a readable frame
2391 (i.e., counted by rptrMonitorPortReadableFrames)
2392 recently received by the port."
2394 "[IEEE 802.3 Mgt], 30.4.3.1.18, aLastSourceAddress."
2395 ::= { rptrExtAddrTrackEntry 2 }
2398 -- The Repeater Top "N" Port Group
2400 -- The Repeater Top N Port group is used to prepare reports that
2401 -- describe a list of ports ordered by one of the statistics in the
2402 -- Repeater Monitor Port Table. The statistic chosen by the
2403 -- management station is sampled over a management
2404 -- station-specified time interval, making the report rate based.
2405 -- The management station also specifies the number of ports that
2408 -- The rptrTopNPortControlTable is used to initiate the generation
2409 -- of a report. The management station may select the parameters
2410 -- of such a report, such as which repeater, which statistic, how
2411 -- many ports, and the start & stop times of the sampling. When
2412 -- the report is prepared, entries are created in the
2413 -- rptrTopNPortTable associated with the relevent
2414 -- rptrTopNControlEntry. These entries are static for
2415 -- each report after it has been prepared.
2417 -- Note that counter discontinuities may appear in some
2418 -- implementations if ports' assignment to repeaters changes
2419 -- during the collection of data for a Top "N" report.
2420 -- A management application could read the corresponding
2421 -- rptrMonitorPortLastChange timestamp in order to check
2422 -- whether a discontinuity occurred.
2425 rptrTopNPortControlTable OBJECT-TYPE
2426 SYNTAX SEQUENCE OF RptrTopNPortControlEntry
2427 MAX-ACCESS not-accessible
2430 "A table of control records for reports on the top `N'
2431 ports for the rate of a selected counter. The number
2432 of entries depends on the configuration of the agent.
2433 The maximum number of entries is implementation
2435 ::= { rptrTopNPortInfo 1 }
2437 rptrTopNPortControlEntry OBJECT-TYPE
2438 SYNTAX RptrTopNPortControlEntry
2439 MAX-ACCESS not-accessible
2442 "A set of parameters that control the creation of a
2443 report of the top N ports according to several metrics."
2444 INDEX { rptrTopNPortControlIndex }
2445 ::= { rptrTopNPortControlTable 1 }
2447 RptrTopNPortControlEntry ::= SEQUENCE {
2448 rptrTopNPortControlIndex
2450 rptrTopNPortRepeaterId
2452 rptrTopNPortRateBase
2454 rptrTopNPortTimeRemaining
2456 rptrTopNPortDuration
2458 rptrTopNPortRequestedSize
2460 rptrTopNPortGrantedSize
2462 rptrTopNPortStartTime
2466 rptrTopNPortRowStatus
2470 rptrTopNPortControlIndex OBJECT-TYPE
2471 SYNTAX Integer32 (1 .. 65535)
2472 MAX-ACCESS read-only
2475 "An index that uniquely identifies an entry in the
2476 rptrTopNPortControl table. Each such entry defines
2477 one top N report prepared for a repeater or system."
2478 ::= { rptrTopNPortControlEntry 1 }
2480 rptrTopNPortRepeaterId OBJECT-TYPE
2481 SYNTAX Integer32 (0..2147483647)
2482 MAX-ACCESS read-create
2485 "Identifies the repeater for which a top N report will
2486 be prepared (see rptrInfoId). If the value of this
2487 object is positive, only ports assigned to this repeater
2488 will be used to form the list in which to order the
2489 Top N table. If this value is zero, all ports will be
2490 eligible for inclusion on the list.
2492 The value of this object may not be modified if the
2493 associated rptrTopNPortRowStatus object is equal to
2495 If, for a particular row in this table, the repeater
2496 specified by the value of this object goes away (is
2497 removed from the rptrInfoTable) while the associated
2498 rptrTopNPortRowStatus object is equal to active(1),
2499 the row in this table is preserved by the agent but
2500 the value of rptrTopNPortRowStatus is changed to
2501 notInService(2), and the agent may time out the row
2502 if appropriate. If the specified repeater comes
2503 back (reappears in the rptrInfoTable) before the row
2504 has been timed out, the management station must set
2505 the value of the rptrTopNPortRowStatus object back
2506 to active(1) if desired (the agent doesn't do this
2508 ::= { rptrTopNPortControlEntry 2 }
2510 rptrTopNPortRateBase OBJECT-TYPE
2522 dataRateMismatches(11),
2528 MAX-ACCESS read-create
2531 "The monitored variable, which the rptrTopNPortRate
2532 variable is based upon.
2534 The value of this object may not be modified if
2535 the associated rptrTopNPortRowStatus object has
2536 a value of active(1)."
2537 ::= { rptrTopNPortControlEntry 3 }
2539 rptrTopNPortTimeRemaining OBJECT-TYPE
2540 SYNTAX Integer32 (0..2147483647)
2541 MAX-ACCESS read-create
2544 "The number of seconds left in the report
2545 currently being collected. When this object
2546 is modified by the management station, a new
2547 collection is started, possibly aborting a
2548 currently running report. The new value is
2549 used as the requested duration of this report,
2550 which is loaded into the associated
2551 rptrTopNPortDuration object.
2553 When this object is set to a non-zero value,
2554 any associated rptrTopNPortEntries shall be
2555 made inaccessible by the agent. While the value
2556 of this object is non-zero, it decrements by one
2557 per second until it reaches zero. During this
2558 time, all associated rptrTopNPortEntries shall
2559 remain inaccessible. At the time that this object
2560 decrements to zero, the report is made accessible
2561 in the rptrTopNPortTable. Thus, the rptrTopNPort
2562 table needs to be created only at the end of the
2563 collection interval.
2565 If the value of this object is set to zero
2566 while the associated report is running, the
2567 running report is aborted and no associated
2568 rptrTopNPortEntries are created."
2570 ::= { rptrTopNPortControlEntry 4 }
2572 rptrTopNPortDuration OBJECT-TYPE
2573 SYNTAX Integer32 (0..2147483647)
2574 MAX-ACCESS read-only
2577 "The number of seconds that this report has
2578 collected during the last sampling interval,
2579 or if this report is currently being collected,
2580 the number of seconds that this report is being
2581 collected during this sampling interval.
2583 When the associated rptrTopNPortTimeRemaining
2584 object is set, this object shall be set by the
2585 agent to the same value and shall not be modified
2586 until the next time the rptrTopNPortTimeRemaining
2589 This value shall be zero if no reports have been
2590 requested for this rptrTopNPortControlEntry."
2591 ::= { rptrTopNPortControlEntry 5 }
2593 rptrTopNPortRequestedSize OBJECT-TYPE
2595 MAX-ACCESS read-create
2598 "The maximum number of repeater ports requested
2599 for the Top N Table.
2601 When this object is created or modified, the
2602 agent should set rptrTopNPortGrantedSize as close
2603 to this object as is possible for the particular
2604 implementation and available resources."
2606 ::= { rptrTopNPortControlEntry 6 }
2608 rptrTopNPortGrantedSize OBJECT-TYPE
2609 SYNTAX Integer32 (0..65535)
2610 MAX-ACCESS read-only
2613 "The maximum number of repeater ports in the
2616 When the associated rptrTopNPortRequestedSize object is
2617 created or modified, the agent should set this object as
2618 closely to the requested value as is possible for the
2619 particular implementation and available resources. The
2620 agent must not lower this value except as a result of a
2621 set to the associated rptrTopNPortRequestedSize object."
2622 ::= { rptrTopNPortControlEntry 7 }
2624 rptrTopNPortStartTime OBJECT-TYPE
2626 MAX-ACCESS read-only
2629 "The value of sysUpTime when this top N report was
2630 last started. In other words, this is the time that
2631 the associated rptrTopNPortTimeRemaining object was
2632 modified to start the requested report.
2634 If the report has not yet been started, the value
2635 of this object is zero."
2636 ::= { rptrTopNPortControlEntry 8 }
2638 rptrTopNPortOwner OBJECT-TYPE
2640 MAX-ACCESS read-create
2643 "The entity that configured this entry and is
2644 using the resources assigned to it."
2645 ::= { rptrTopNPortControlEntry 9 }
2647 rptrTopNPortRowStatus OBJECT-TYPE
2649 MAX-ACCESS read-create
2652 "The status of this row.
2654 If the value of this object is not equal to
2655 active(1), all associated entries in the
2656 rptrTopNPortTable shall be deleted by the
2658 ::= { rptrTopNPortControlEntry 10 }
2663 rptrTopNPortTable OBJECT-TYPE
2664 SYNTAX SEQUENCE OF RptrTopNPortEntry
2665 MAX-ACCESS not-accessible
2668 "A table of reports for the top `N' ports based on
2669 setting of associated control table entries. The
2670 maximum number of entries depends on the number
2671 of entries in table rptrTopNPortControlTable and
2672 the value of object rptrTopNPortGrantedSize for
2675 For each entry in the rptrTopNPortControlTable,
2676 repeater ports with the highest value of
2677 rptrTopNPortRate shall be placed in this table
2678 in decreasing order of that rate until there is
2679 no more room or until there are no more ports."
2680 ::= { rptrTopNPortInfo 2 }
2682 rptrTopNPortEntry OBJECT-TYPE
2683 SYNTAX RptrTopNPortEntry
2684 MAX-ACCESS not-accessible
2687 "A set of statistics for a repeater port that is
2688 part of a top N report."
2689 INDEX { rptrTopNPortControlIndex,
2691 ::= { rptrTopNPortTable 1 }
2693 RptrTopNPortEntry ::= SEQUENCE {
2696 rptrTopNPortGroupIndex
2698 rptrTopNPortPortIndex
2704 rptrTopNPortIndex OBJECT-TYPE
2705 SYNTAX Integer32 (1..65535)
2706 MAX-ACCESS read-only
2709 "An index that uniquely identifies an entry in
2710 the rptrTopNPort table among those in the same
2711 report. This index is between 1 and N, where N
2712 is the number of entries in this report. Increasing
2713 values of rptrTopNPortIndex shall be assigned to
2714 entries with decreasing values of rptrTopNPortRate
2715 until index N is assigned to the entry with the
2716 lowest value of rptrTopNPortRate or there are no
2717 more rptrTopNPortEntries.
2719 No ports are included in a report where their
2720 value of rptrTopNPortRate would be zero."
2721 ::= { rptrTopNPortEntry 1 }
2723 rptrTopNPortGroupIndex OBJECT-TYPE
2724 SYNTAX Integer32 (1..2147483647)
2725 MAX-ACCESS read-only
2728 "This object identifes the group containing
2729 the port for this entry. (See also object
2730 type rptrGroupIndex.)"
2731 ::= { rptrTopNPortEntry 2 }
2733 rptrTopNPortPortIndex OBJECT-TYPE
2734 SYNTAX Integer32 (1..2147483647)
2735 MAX-ACCESS read-only
2738 "The index of the repeater port.
2739 (See object type rptrPortIndex.)"
2740 ::= { rptrTopNPortEntry 3 }
2742 rptrTopNPortRate OBJECT-TYPE
2744 MAX-ACCESS read-only
2747 "The amount of change in the selected variable
2748 during this sampling interval for the identified
2749 port. The selected variable is that port's
2750 instance of the object selected by
2751 rptrTopNPortRateBase."
2752 ::= { rptrTopNPortEntry 4 }
2756 -- Notifications for use by Repeaters
2758 rptrHealth NOTIFICATION-TYPE
2759 OBJECTS { rptrOperStatus }
2762 "********* THIS OBJECT IS DEPRECATED **********
2764 In a system containing a single managed repeater,
2765 the rptrHealth notification conveys information
2766 related to the operational status of the repeater.
2767 It is sent either when the value of
2768 rptrOperStatus changes, or upon completion of a
2769 non-disruptive test.
2771 The rptrHealth notification must contain the
2772 rptrOperStatus object. The agent may optionally
2773 include the rptrHealthText object in the varBind
2774 list. See the rptrOperStatus and rptrHealthText
2775 objects for descriptions of the information that
2778 The agent must throttle the generation of
2779 consecutive rptrHealth traps so that there is at
2780 least a five-second gap between traps of this
2781 type. When traps are throttled, they are dropped,
2782 not queued for sending at a future time. (Note
2783 that 'generating' a trap means sending to all
2784 configured recipients.)"
2786 "[IEEE 802.3 Mgt], 30.4.1.3.1, nRepeaterHealth
2788 ::= { snmpDot3RptrMgt 0 1 }
2790 rptrGroupChange NOTIFICATION-TYPE
2791 OBJECTS { rptrGroupIndex }
2794 "********* THIS OBJECT IS DEPRECATED **********
2796 In a system containing a single managed repeater,
2797 this notification is sent when a change occurs in the
2798 group structure of the repeater. This occurs only
2799 when a group is logically or physically removed
2800 from or added to a repeater. The varBind list
2801 contains the identifier of the group that was
2804 The agent must throttle the generation of
2805 consecutive rptrGroupChange traps for the same
2806 group so that there is at least a five-second gap
2807 between traps of this type. When traps are
2808 throttled, they are dropped, not queued for
2809 sending at a future time. (Note that 'generating'
2810 a trap means sending to all configured
2813 "[IEEE 802.3 Mgt], 30.4.1.3.3, nGroupMapChange
2815 ::= { snmpDot3RptrMgt 0 2 }
2817 rptrResetEvent NOTIFICATION-TYPE
2818 OBJECTS { rptrOperStatus }
2821 "********* THIS OBJECT IS DEPRECATED **********
2823 In a system containing a single managed repeater-unit,
2824 the rptrResetEvent notification conveys information
2825 related to the operational status of the repeater.
2826 This trap is sent on completion of a repeater
2827 reset action. A repeater reset action is defined
2828 as an a transition to the START state of Fig 9-2
2829 in section 9 [IEEE 802.3 Std], when triggered by a
2830 management command (e.g., an SNMP Set on the
2833 The agent must throttle the generation of
2834 consecutive rptrResetEvent traps so that there is
2835 at least a five-second gap between traps of this
2836 type. When traps are throttled, they are dropped,
2837 not queued for sending at a future time. (Note
2838 that 'generating' a trap means sending to all
2839 configured recipients.)
2841 The rptrResetEvent trap is not sent when the agent
2842 restarts and sends an SNMP coldStart or warmStart
2843 trap. However, it is recommended that a repeater
2844 agent send the rptrOperStatus object as an
2845 optional object with its coldStart and warmStart
2848 The rptrOperStatus object must be included in the
2849 varbind list sent with this trap. The agent may
2850 optionally include the rptrHealthText object as
2853 "[IEEE 802.3 Mgt], 30.4.1.3.2, nRepeaterReset
2855 ::= { snmpDot3RptrMgt 0 3 }
2858 -- Notifications for repeaters in a multiple-repeater implementation.
2859 -- An implementation may send either the single-repeater OR
2860 -- multiple-repeater version of these notifications (1 or 4; 2 or 5)
2863 rptrInfoHealth NOTIFICATION-TYPE
2864 OBJECTS { rptrInfoOperStatus }
2867 "In a system containing multiple managed repeaters,
2868 the rptrInfoHealth notification conveys information
2869 related to the operational status of a repeater.
2870 It is sent either when the value of rptrInfoOperStatus
2871 changes, or upon completion of a non-disruptive test.
2873 The agent must throttle the generation of
2874 consecutive rptrInfoHealth notifications for
2875 the same repeater so that there is at least
2876 a five-second gap between notifications of this type.
2877 When notifications are throttled, they are dropped,
2878 not queued for sending at a future time. (Note
2879 that 'generating' a notification means sending
2880 to all configured recipients.)"
2882 "[IEEE 802.3 Mgt], 30.4.1.3.1, nRepeaterHealth
2884 ::= { snmpDot3RptrMgt 0 4 }
2886 rptrInfoResetEvent NOTIFICATION-TYPE
2887 OBJECTS { rptrInfoOperStatus }
2890 "In a system containing multiple managed
2891 repeaters, the rptrInfoResetEvent notification
2892 conveys information related to the operational
2893 status of a repeater. This notification is sent
2894 on completion of a repeater reset action. A
2895 repeater reset action is defined as a transition
2896 to the START state of Fig 9-2 in section 9 of
2897 [IEEE 802.3 Std], when triggered by a management
2898 command (e.g., an SNMP Set on the rptrInfoReset
2901 The agent must throttle the generation of
2902 consecutive rptrInfoResetEvent notifications for
2903 a single repeater so that there is at least
2904 a five-second gap between notifications of
2905 this type. When notifications are throttled,
2906 they are dropped, not queued for sending at
2907 a future time. (Note that 'generating' a
2908 notification means sending to all configured
2911 The rptrInfoResetEvent is not sent when the
2912 agent restarts and sends an SNMP coldStart or
2913 warmStart trap. However, it is recommended that
2914 a repeater agent send the rptrInfoOperStatus
2915 object as an optional object with its coldStart
2916 and warmStart trap PDUs."
2918 "[IEEE 802.3 Mgt], 30.4.1.3.2, nRepeaterReset
2920 ::= { snmpDot3RptrMgt 0 5 }
2923 -- Conformance information
2926 OBJECT IDENTIFIER ::= { snmpRptrMod 1 }
2928 OBJECT IDENTIFIER ::= { snmpRptrModConf 1 }
2930 OBJECT IDENTIFIER ::= { snmpRptrModConf 2 }
2932 OBJECT IDENTIFIER ::= { snmpRptrModConf 3 }
2937 snmpRptrGrpBasic1516 OBJECT-GROUP
2938 OBJECTS { rptrGroupCapacity,
2943 rptrTotalPartitionedPorts,
2948 rptrGroupOperStatus,
2949 rptrGroupLastOperStatusChange,
2950 rptrGroupPortCapacity,
2954 rptrPortAdminStatus,
2955 rptrPortAutoPartitionState,
2956 rptrPortOperStatus }
2959 "********* THIS GROUP IS DEPRECATED **********
2961 Basic group from RFCs 1368 and 1516.
2963 NOTE: this object group is DEPRECATED and replaced
2964 with snmpRptrGrpBasic."
2965 ::= { snmpRptrModObjGrps 1 }
2967 snmpRptrGrpMonitor1516 OBJECT-GROUP
2968 OBJECTS { rptrMonitorTransmitCollisions,
2970 rptrMonitorGroupIndex,
2971 rptrMonitorGroupTotalFrames,
2972 rptrMonitorGroupTotalOctets,
2973 rptrMonitorGroupTotalErrors,
2974 rptrMonitorPortGroupIndex,
2975 rptrMonitorPortIndex,
2976 rptrMonitorPortReadableFrames,
2977 rptrMonitorPortReadableOctets,
2978 rptrMonitorPortFCSErrors,
2979 rptrMonitorPortAlignmentErrors,
2980 rptrMonitorPortFrameTooLongs,
2981 rptrMonitorPortShortEvents,
2982 rptrMonitorPortRunts,
2983 rptrMonitorPortCollisions,
2984 rptrMonitorPortLateEvents,
2985 rptrMonitorPortVeryLongEvents,
2986 rptrMonitorPortDataRateMismatches,
2987 rptrMonitorPortAutoPartitions,
2988 rptrMonitorPortTotalErrors }
2991 "********* THIS GROUP IS DEPRECATED **********
2993 Monitor group from RFCs 1368 and 1516.
2995 NOTE: this object group is DEPRECATED and replaced
2996 with snmpRptrGrpMonitor."
2997 ::= { snmpRptrModObjGrps 2 }
2999 snmpRptrGrpAddrTrack1368 OBJECT-GROUP
3000 OBJECTS { rptrAddrTrackGroupIndex,
3001 rptrAddrTrackPortIndex,
3002 rptrAddrTrackLastSourceAddress,
3003 rptrAddrTrackSourceAddrChanges }
3006 "Address tracking group from RFC 1368.
3008 NOTE: this object group is OBSOLETE and replaced
3009 with snmpRptrGrpAddrTrack1516."
3010 ::= { snmpRptrModObjGrps 3 }
3012 snmpRptrGrpAddrTrack1516 OBJECT-GROUP
3013 OBJECTS { rptrAddrTrackGroupIndex,
3014 rptrAddrTrackPortIndex,
3015 rptrAddrTrackLastSourceAddress,
3016 rptrAddrTrackSourceAddrChanges,
3017 rptrAddrTrackNewLastSrcAddress }
3020 "********* THIS GROUP IS DEPRECATED **********
3021 Address tracking group from RFC 1516.
3023 NOTE: this object group is DEPRECATED and
3024 replaced with snmpRptrGrpAddrTrack."
3025 ::= { snmpRptrModObjGrps 4 }
3027 snmpRptrGrpBasic OBJECT-GROUP
3028 OBJECTS { rptrGroupIndex,
3030 rptrGroupOperStatus,
3031 rptrGroupPortCapacity,
3035 rptrPortAdminStatus,
3036 rptrPortAutoPartitionState,
3044 rptrInfoPartitionedPorts,
3045 rptrInfoLastChange }
3048 "Basic group for a system with one or more
3049 repeater-units in multi-segment (post-RFC 1516)
3050 version of the MIB module."
3051 ::= { snmpRptrModObjGrps 5 }
3053 snmpRptrGrpMonitor OBJECT-GROUP
3054 OBJECTS { rptrMonitorPortGroupIndex,
3055 rptrMonitorPortIndex,
3056 rptrMonitorPortReadableFrames,
3057 rptrMonitorPortReadableOctets,
3058 rptrMonitorPortFCSErrors,
3059 rptrMonitorPortAlignmentErrors,
3060 rptrMonitorPortFrameTooLongs,
3061 rptrMonitorPortShortEvents,
3062 rptrMonitorPortRunts,
3063 rptrMonitorPortCollisions,
3064 rptrMonitorPortLateEvents,
3065 rptrMonitorPortVeryLongEvents,
3066 rptrMonitorPortDataRateMismatches,
3067 rptrMonitorPortAutoPartitions,
3068 rptrMonitorPortTotalErrors,
3069 rptrMonitorPortLastChange,
3071 rptrMonTxCollisions,
3074 rptrMonTotalOctets }
3077 "Monitor group for a system with one or more
3078 repeater-units in multi-segment (post-RFC 1516)
3079 version of the MIB module."
3080 ::= { snmpRptrModObjGrps 6 }
3082 snmpRptrGrpMonitor100 OBJECT-GROUP
3083 OBJECTS { rptrMonitorPortIsolates,
3084 rptrMonitorPortSymbolErrors,
3085 rptrMonitorPortUpper32Octets,
3087 rptrMonUpper32TotalOctets }
3090 "Monitor group for 100Mb/s ports and repeaters
3091 in a system with one or more repeater-units in
3092 multi-segment (post-RFC 1516) version of the MIB
3093 module. Systems which support Counter64 should
3094 also implement snmpRptrGrpMonitor100w64."
3095 ::= { snmpRptrModObjGrps 7 }
3097 snmpRptrGrpMonitor100w64 OBJECT-GROUP
3098 OBJECTS { rptrMonitorPortHCReadableOctets,
3099 rptrMonHCTotalOctets }
3102 "Monitor group for 100Mb/s ports and repeaters in a
3103 system with one or more repeater-units and support
3105 ::= { snmpRptrModObjGrps 8 }
3107 snmpRptrGrpAddrTrack OBJECT-GROUP
3108 OBJECTS { rptrAddrTrackGroupIndex,
3109 rptrAddrTrackPortIndex,
3110 rptrAddrTrackSourceAddrChanges,
3111 rptrAddrTrackNewLastSrcAddress,
3112 rptrAddrTrackCapacity }
3115 "Passive address tracking group for post-RFC 1516
3116 version of the MIB module."
3117 ::= { snmpRptrModObjGrps 9 }
3119 snmpRptrGrpExtAddrTrack OBJECT-GROUP
3120 OBJECTS { rptrExtAddrTrackMacIndex,
3121 rptrExtAddrTrackSourceAddress }
3124 "Extended passive address tracking group for
3125 a system with one or more repeater-units in
3126 post-RFC 1516 version of the MIB module."
3127 ::= { snmpRptrModObjGrps 10 }
3129 snmpRptrGrpRptrAddrSearch OBJECT-GROUP
3130 OBJECTS { rptrAddrSearchLock,
3131 rptrAddrSearchStatus,
3132 rptrAddrSearchAddress,
3133 rptrAddrSearchState,
3134 rptrAddrSearchGroup,
3136 rptrAddrSearchOwner }
3139 "Active MAC address search group and topology
3140 mapping support for repeaters."
3141 ::= { snmpRptrModObjGrps 11 }
3143 snmpRptrGrpTopNPort OBJECT-GROUP
3144 OBJECTS { rptrTopNPortControlIndex,
3145 rptrTopNPortRepeaterId,
3146 rptrTopNPortRateBase,
3147 rptrTopNPortTimeRemaining,
3148 rptrTopNPortDuration,
3149 rptrTopNPortRequestedSize,
3150 rptrTopNPortGrantedSize,
3151 rptrTopNPortStartTime,
3153 rptrTopNPortRowStatus,
3155 rptrTopNPortGroupIndex,
3156 rptrTopNPortPortIndex,
3160 "Top `N' group for repeater ports."
3161 ::= { snmpRptrModObjGrps 12 }
3166 snmpRptrModComplRFC1368 MODULE-COMPLIANCE
3169 "Compliance for RFC 1368.
3171 NOTE: this module compliance is OBSOLETE and
3172 replaced by snmpRptrModComplRFC1516."
3174 MODULE -- this module
3175 MANDATORY-GROUPS { snmpRptrGrpBasic1516 }
3177 GROUP snmpRptrGrpMonitor1516
3179 "Implementation of this optional group is
3180 recommended for systems which have the
3181 instrumentation to do performance monitoring."
3183 GROUP snmpRptrGrpAddrTrack1368
3185 "Implementation of this group is
3186 recommended for systems which have
3187 the necessary instrumentation."
3189 ::= { snmpRptrModCompls 1 }
3191 snmpRptrModComplRFC1516 MODULE-COMPLIANCE
3194 "********* THIS COMPLIANCE IS DEPRECATED **********
3196 Compliance for RFC 1516 and for backwards
3197 compatibility with single-repeater,
3198 10Mb/s-only implementations."
3200 MODULE -- this module
3201 MANDATORY-GROUPS { snmpRptrGrpBasic1516 }
3203 GROUP snmpRptrGrpMonitor1516
3205 "Implementation of this optional group is
3206 recommended for systems which have the
3207 instrumentation to do performance monitoring."
3209 GROUP snmpRptrGrpAddrTrack1516
3211 "Implementation of this group is
3212 recommended for systems which have
3213 the necessary instrumentation."
3214 ::= { snmpRptrModCompls 2 }
3216 snmpRptrModCompl MODULE-COMPLIANCE
3219 "Compliance for the multi-segment version of the
3220 MIB module for a system with one or more
3223 MODULE -- this module
3224 MANDATORY-GROUPS { snmpRptrGrpBasic,
3226 snmpRptrGrpAddrTrack }
3228 GROUP snmpRptrGrpMonitor100
3230 "Implementation of this group is
3231 mandatory for managed systems which
3232 contain 100Mb/s repeaters."
3234 GROUP snmpRptrGrpMonitor100w64
3236 "Implementation of this group is
3237 mandatory for managed systems which
3238 contain 100Mb/s repeaters and which
3239 can support Counter64."
3241 GROUP snmpRptrGrpExtAddrTrack
3243 "Implementation of this group is
3244 recommended for systems which have
3245 the necessary instrumentation to track
3246 MAC addresses of multiple DTEs attached
3247 to a single repeater port."
3249 GROUP snmpRptrGrpRptrAddrSearch
3251 "Implementation of this group is
3252 recommended for systems which allow
3253 read-write access and which have
3254 the necessary instrumentation to
3255 search all incoming data streams
3256 for a particular MAC address."
3258 GROUP snmpRptrGrpTopNPort
3260 "Implementation of this group is
3261 recommended for systems which have
3262 the necessary resources to support
3263 TopN statistics reporting."
3265 ::= { snmpRptrModCompls 3 }
projects / platform / upstream / libsmi.git / blob