smilint output for ./SNMP-REPEATER-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| minor error | 1 |
| change recommended | 6 |
| warning | 17 |
| Message Types |
|---|
| Type | Count |
|---|
| group-membership (change recommended) | 5 |
| index-element-accessible (warning) | 12 |
| integer-misuse (warning) | 2 |
| module-identity-registration (change recommended) | 1 |
| node-implicit (warning) | 1 |
| revision-missing (minor error) | 1 |
| type-status-deprecated (warning) | 2 |
Messages:
SNMP-REPEATER-MIB
1: -- extracted from rfc2108.txt
2: -- at Mon Nov 15 17:11:46 1999
18:
19: snmpRptrMod MODULE-IDENTITY
19: change recommended -
warning: uncontrolled MODULE-IDENTITY registration
20: LAST-UPDATED "9609140000Z"
21: ORGANIZATION "IETF HUB MIB Working Group"
22: CONTACT-INFO
23: "WG E-mail: hubmib@hprnd.rose.hp.com
24:
25: Chair: Dan Romascanu
26: Postal: Madge Networks (Israel) Ltd.
27: Atidim Technology Park, Bldg. 3
28: Tel Aviv 61131, Israel
29: Tel: 972-3-6458414, 6458458
30: Fax: 972-3-6487146
31: E-mail: dromasca@madge.com
32:
33: Editor: Kathryn de Graaf
34: Postal: 3Com Corporation
35: 118 Turnpike Rd.
36: Southborough, MA 01772 USA
37: Tel: (508)229-1627
38: Fax: (508)490-5882
39: E-mail: kdegraaf@isd.3com.com"
40: DESCRIPTION
41: "Management information for 802.3 repeaters.
42:
43: The following references are used throughout
44: this MIB module:
45:
46: [IEEE 802.3 Std]
47: refers to IEEE 802.3/ISO 8802-3 Information
48: processing systems - Local area networks -
49: Part 3: Carrier sense multiple access with
50: collision detection (CSMA/CD) access method
51: and physical layer specifications (1993).
52:
53: [IEEE 802.3 Mgt]
54: refers to IEEE 802.3u-1995, '10 Mb/s &
55: 100 Mb/s Management, Section 30,'
56: Supplement to ANSI/IEEE 802.3.
57:
58: The following terms are used throughout this
59: MIB module. For complete formal definitions,
60: the IEEE 802.3 standards should be consulted
61: wherever possible:
62:
63: System - A managed entity compliant with this
64: MIB, and incorporating at least one managed
65: 802.3 repeater.
66:
67: Chassis - An enclosure for one managed repeater,
68: part of a managed repeater, or several managed
69: repeaters. It typically contains an integral
70: power supply and a variable number of available
71: module slots.
72:
73: Repeater-unit - The portion of the repeater set
74: that is inboard of the physical media interfaces.
75: The physical media interfaces (MAUs, AUIs) may be
76: physically separated from the repeater-unit, or
77: they may be integrated into the same physical
78: package.
79:
80: Trivial repeater-unit - An isolated port that can
81: gather statistics.
82:
83: Group - A recommended, but optional, entity
84: defined by the IEEE 802.3 management standard,
85: in order to support a modular numbering scheme.
86: The classical example allows an implementor to
87: represent field-replaceable units as groups of
88: ports, with the port numbering matching the
89: modular hardware implementation.
90:
91: System interconnect segment - An internal
92: segment allowing interconnection of ports
93: belonging to different physical entities
94: into the same logical manageable repeater.
95: Examples of implementation might be
96: backplane busses in modular hubs, or
97: chaining cables in stacks of hubs.
98: Stack - A scalable system that may include
99: managed repeaters, in which modularity is
100: achieved by interconnecting a number of
101: different chassis.
102:
103: Module - A building block in a modular
104: chassis. It typically maps into one 'slot';
105: however, the range of configurations may be
106: very large, with several modules entering
107: one slot, or one module covering several
108: slots.
109: "
110: REVISION "9309010000Z"
111: DESCRIPTION
112: "Published as RFC 1516"
113: REVISION "9210010000Z"
114: DESCRIPTION
115: "Published as RFC 1368"
116: ::= { snmpDot3RptrMgt 5 }
116: minor error -
revision for last update is missing
117:
118:
...
404:
405: rptrGroupEntry OBJECT-TYPE
405: warning -
warning: index element `rptrGroupIndex' of row `rptrGroupEntry' should be not-accessible in SMIv2 MIB
406: SYNTAX RptrGroupEntry
407: MAX-ACCESS not-accessible
408: STATUS current
409: DESCRIPTION
410: "An entry in the table, containing information
411: about a single group of ports."
412: INDEX { rptrGroupIndex }
413: ::= { rptrGroupTable 1 }
414:
415: RptrGroupEntry ::=
416: SEQUENCE {
417: rptrGroupIndex
418: Integer32,
419: rptrGroupDescr
420: DisplayString,
421: rptrGroupObjectID
422: OBJECT IDENTIFIER,
423: rptrGroupOperStatus
424: INTEGER,
425: rptrGroupLastOperStatusChange
426: TimeTicks,
427: rptrGroupPortCapacity
428: Integer32
429: }
...
573:
574: rptrPortEntry OBJECT-TYPE
574: warning -
warning: index element `rptrPortGroupIndex' of row `rptrPortEntry' should be not-accessible in SMIv2 MIB
574: warning -
warning: index element `rptrPortIndex' of row `rptrPortEntry' should be not-accessible in SMIv2 MIB
575: SYNTAX RptrPortEntry
576: MAX-ACCESS not-accessible
577: STATUS current
578: DESCRIPTION
579: "An entry in the table, containing information
580: about a single port."
581:
582: INDEX { rptrPortGroupIndex, rptrPortIndex }
583: ::= { rptrPortTable 1 }
584:
585: RptrPortEntry ::=
586: SEQUENCE {
587: rptrPortGroupIndex
588: Integer32,
589: rptrPortIndex
590: Integer32,
591: rptrPortAdminStatus
592: INTEGER,
593: rptrPortAutoPartitionState
594: INTEGER,
595: rptrPortOperStatus
596: INTEGER,
597: rptrPortRptrId
598: Integer32
599: }
...
736:
737: rptrInfoEntry OBJECT-TYPE
737: warning -
warning: index element `rptrInfoId' of row `rptrInfoEntry' should be not-accessible in SMIv2 MIB
738: SYNTAX RptrInfoEntry
739: MAX-ACCESS not-accessible
740: STATUS current
741: DESCRIPTION
742: "An entry in the table, containing information
743: about a single non-trivial repeater."
744: INDEX { rptrInfoId }
745: ::= { rptrInfoTable 1 }
746:
747: RptrInfoEntry ::=
748: SEQUENCE {
749: rptrInfoId
750: Integer32,
751: rptrInfoRptrType
752: INTEGER,
753: rptrInfoOperStatus
754: INTEGER,
755: rptrInfoReset
756: INTEGER,
757: rptrInfoPartitionedPorts
758: Gauge32,
759: rptrInfoLastChange
760: TimeStamp
761: }
...
943:
944: rptrMonitorGroupEntry OBJECT-TYPE
944: warning -
warning: index element `rptrMonitorGroupIndex' of row `rptrMonitorGroupEntry' should be not-accessible in SMIv2 MIB
945: SYNTAX RptrMonitorGroupEntry
946: MAX-ACCESS not-accessible
947: STATUS deprecated
948: DESCRIPTION
949: "********* THIS OBJECT IS DEPRECATED **********
950:
951: An entry in the table, containing total
952: performance and error statistics for a single
953: group. Regular retrieval of the information in
954: this table provides a means of tracking the
955: performance and health of the networked devices
956: attached to this group's ports.
957:
958: The counters in this table are redundant in the
959: sense that they are the summations of information
960: already available through other objects. However,
961: these sums provide a considerable optimization of
962: network management traffic over the otherwise
963: necessary retrieval of the individual counters
964: included in each sum.
965:
966: Note: Group-level counters are
967: deprecated in this MIB. It is recommended
968: that management applications instead use
969: the repeater-level counters contained in
970: the rptrMonTable."
971: INDEX { rptrMonitorGroupIndex }
972: ::= { rptrMonitorGroupTable 1 }
973:
974: RptrMonitorGroupEntry ::=
975: SEQUENCE {
976: rptrMonitorGroupIndex
977: Integer32,
978: rptrMonitorGroupTotalFrames
979: Counter32,
980: rptrMonitorGroupTotalOctets
981: Counter32,
982: rptrMonitorGroupTotalErrors
983: Counter32
984: }
...
1069:
1070: rptrMonitorPortEntry OBJECT-TYPE
1070: warning -
warning: index element `rptrMonitorPortGroupIndex' of row `rptrMonitorPortEntry' should be not-accessible in SMIv2 MIB
1070: warning -
warning: index element `rptrMonitorPortIndex' of row `rptrMonitorPortEntry' should be not-accessible in SMIv2 MIB
1071: SYNTAX RptrMonitorPortEntry
1072: MAX-ACCESS not-accessible
1073: STATUS current
1074: DESCRIPTION
1075: "An entry in the table, containing performance and
1076: error statistics for a single port."
1077: INDEX { rptrMonitorPortGroupIndex, rptrMonitorPortIndex }
1078: ::= { rptrMonitorPortTable 1 }
1079:
1080: RptrMonitorPortEntry ::=
1081: SEQUENCE {
1082: rptrMonitorPortGroupIndex
1083: Integer32,
1084: rptrMonitorPortIndex
1085: Integer32,
1086: rptrMonitorPortReadableFrames
1087: Counter32,
1088: rptrMonitorPortReadableOctets
1089: Counter32,
1090: rptrMonitorPortFCSErrors
1091: Counter32,
1092: rptrMonitorPortAlignmentErrors
1093: Counter32,
1094: rptrMonitorPortFrameTooLongs
1095: Counter32,
1096: rptrMonitorPortShortEvents
1097: Counter32,
1098: rptrMonitorPortRunts
1099: Counter32,
1100: rptrMonitorPortCollisions
1101: Counter32,
1102: rptrMonitorPortLateEvents
1103: Counter32,
1104: rptrMonitorPortVeryLongEvents
1105: Counter32,
1106: rptrMonitorPortDataRateMismatches
1107: Counter32,
1108: rptrMonitorPortAutoPartitions
1109: Counter32,
1110: rptrMonitorPortTotalErrors
1111: Counter32,
1112: rptrMonitorPortLastChange
1113: TimeStamp
1114: }
...
2182:
2183: rptrAddrSearchOwner OBJECT-TYPE
2183: warning -
warning: type `OwnerString' used by `rptrAddrSearchOwner' is deprecated
2184: SYNTAX OwnerString
2185: MAX-ACCESS read-write
2186: STATUS current
2187: DESCRIPTION
2188: "The entity which currently has 'ownership' of this
2189: rptrAddrSearchEntry."
2190: ::= { rptrAddrSearchEntry 7 }
2191:
2192:
2193: --
2194: -- The Port Address Tracking Table
2195: --
2196: -- This table provides a way for a network management
2197: -- application to passively gather information (using
2198: -- read-only privileges) about which network addresses
2199: -- are connected to which ports of a repeater.
2200: --
...
2210:
2211: rptrAddrTrackEntry OBJECT-TYPE
2211: warning -
warning: index element `rptrAddrTrackGroupIndex' of row `rptrAddrTrackEntry' should be not-accessible in SMIv2 MIB
2211: warning -
warning: index element `rptrAddrTrackPortIndex' of row `rptrAddrTrackEntry' should be not-accessible in SMIv2 MIB
2212: SYNTAX RptrAddrTrackEntry
2213: MAX-ACCESS not-accessible
2214: STATUS current
2215: DESCRIPTION
2216: "An entry in the table, containing address mapping
2217: information about a single port."
2218: INDEX { rptrAddrTrackGroupIndex, rptrAddrTrackPortIndex }
2219: ::= { rptrAddrTrackTable 1 }
2220:
2221: RptrAddrTrackEntry ::=
2222: SEQUENCE {
2223: rptrAddrTrackGroupIndex
2224: INTEGER,
2225: rptrAddrTrackPortIndex
2226: INTEGER,
2227: rptrAddrTrackLastSourceAddress -- DEPRECATED OBJECT
2228: MacAddress,
2229: rptrAddrTrackSourceAddrChanges
2230: Counter32,
2231: rptrAddrTrackNewLastSrcAddress
2232: OptMacAddr,
2233: rptrAddrTrackCapacity
2234: Integer32
2235: }
2236:
2237: rptrAddrTrackGroupIndex OBJECT-TYPE
2238: SYNTAX INTEGER (1..2147483647)
2238: warning -
warning: use Integer32 instead of INTEGER in SMIv2
2239: MAX-ACCESS read-only
2240: STATUS current
2241: DESCRIPTION
2242: "This object identifies the group containing the
2243: port for which this entry contains information."
2244: ::= { rptrAddrTrackEntry 1 }
2245:
2246: rptrAddrTrackPortIndex OBJECT-TYPE
2247: SYNTAX INTEGER (1..2147483647)
2247: warning -
warning: use Integer32 instead of INTEGER in SMIv2
2248: MAX-ACCESS read-only
2249: STATUS current
2250: DESCRIPTION
2251: "This object identifies the port within the group
2252: for which this entry contains information."
2253: REFERENCE
2254: "[IEEE 802.3 Mgt], 30.4.3.1.1, aPortID."
2255: ::= { rptrAddrTrackEntry 2 }
...
2356:
2357: rptrExtAddrTrackEntry OBJECT-TYPE
2357: warning -
warning: index element `rptrExtAddrTrackMacIndex' of row `rptrExtAddrTrackEntry' should be not-accessible in SMIv2 MIB
2358: SYNTAX RptrExtAddrTrackEntry
2359: MAX-ACCESS not-accessible
2360: STATUS current
2361: DESCRIPTION
2362: "A row in the table of extended address tracking
2363: information for ports. Entries can not be directly
2364: created or deleted via SNMP operations."
2365: INDEX { rptrAddrTrackGroupIndex,
2366: rptrAddrTrackPortIndex,
2367: rptrExtAddrTrackMacIndex }
2368: ::= { rptrExtAddrTrackTable 1 }
2369:
2370: RptrExtAddrTrackEntry ::= SEQUENCE {
2371: rptrExtAddrTrackMacIndex Integer32,
2372: rptrExtAddrTrackSourceAddress MacAddress
2373: }
...
2442:
2443: rptrTopNPortControlEntry OBJECT-TYPE
2443: warning -
warning: index element `rptrTopNPortControlIndex' of row `rptrTopNPortControlEntry' should be not-accessible in SMIv2 MIB
2444: SYNTAX RptrTopNPortControlEntry
2445: MAX-ACCESS not-accessible
2446: STATUS current
2447: DESCRIPTION
2448: "A set of parameters that control the creation of a
2449: report of the top N ports according to several metrics."
2450: INDEX { rptrTopNPortControlIndex }
2451: ::= { rptrTopNPortControlTable 1 }
2452:
2453: RptrTopNPortControlEntry ::= SEQUENCE {
2454: rptrTopNPortControlIndex
2455: Integer32,
2456: rptrTopNPortRepeaterId
2457: Integer32,
2458: rptrTopNPortRateBase
2459: INTEGER,
2460: rptrTopNPortTimeRemaining
2461: Integer32,
2462: rptrTopNPortDuration
2463: Integer32,
2464: rptrTopNPortRequestedSize
2465: Integer32,
2466: rptrTopNPortGrantedSize
2467: Integer32,
2468: rptrTopNPortStartTime
2469: TimeStamp,
2470: rptrTopNPortOwner
2471: OwnerString,
2472: rptrTopNPortRowStatus
2473: RowStatus
2474: }
...
2643:
2644: rptrTopNPortOwner OBJECT-TYPE
2644: warning -
warning: type `OwnerString' used by `rptrTopNPortOwner' is deprecated
2645: SYNTAX OwnerString
2646: MAX-ACCESS read-create
2647: STATUS current
2648: DESCRIPTION
2649: "The entity that configured this entry and is
2650: using the resources assigned to it."
2651: ::= { rptrTopNPortControlEntry 9 }
...
2687:
2688: rptrTopNPortEntry OBJECT-TYPE
2688: warning -
warning: index element `rptrTopNPortIndex' of row `rptrTopNPortEntry' should be not-accessible in SMIv2 MIB
2689: SYNTAX RptrTopNPortEntry
2690: MAX-ACCESS not-accessible
2691: STATUS current
2692: DESCRIPTION
2693: "A set of statistics for a repeater port that is
2694: part of a top N report."
2695: INDEX { rptrTopNPortControlIndex,
2696: rptrTopNPortIndex }
2697: ::= { rptrTopNPortTable 1 }
2698:
2699: RptrTopNPortEntry ::= SEQUENCE {
2700: rptrTopNPortIndex
2701: Integer32,
2702: rptrTopNPortGroupIndex
2703: Integer32,
2704: rptrTopNPortPortIndex
2705: Integer32,
2706: rptrTopNPortRate
2707: Gauge32
2708: }
...
2763:
2764: rptrHealth NOTIFICATION-TYPE
2764: change recommended -
warning: notification `rptrHealth' must be contained in at least one conformance group
2765: OBJECTS { rptrOperStatus }
2766: STATUS deprecated
2767: DESCRIPTION
2768: "********* THIS OBJECT IS DEPRECATED **********
2769:
2770: In a system containing a single managed repeater,
2771: the rptrHealth notification conveys information
2772: related to the operational status of the repeater.
2773: It is sent either when the value of
2774: rptrOperStatus changes, or upon completion of a
2775: non-disruptive test.
2776:
2777: The rptrHealth notification must contain the
2778: rptrOperStatus object. The agent may optionally
2779: include the rptrHealthText object in the varBind
2780: list. See the rptrOperStatus and rptrHealthText
2781: objects for descriptions of the information that
2782: is sent.
2783:
2784: The agent must throttle the generation of
2785: consecutive rptrHealth traps so that there is at
2786: least a five-second gap between traps of this
2787: type. When traps are throttled, they are dropped,
2788: not queued for sending at a future time. (Note
2789: that 'generating' a trap means sending to all
2790: configured recipients.)"
2791: REFERENCE
2792: "[IEEE 802.3 Mgt], 30.4.1.3.1, nRepeaterHealth
2793: notification."
2794: ::= { snmpDot3RptrMgt 0 1 }
2794: warning -
warning: implicit node definition
2795:
2796: rptrGroupChange NOTIFICATION-TYPE
2796: change recommended -
warning: notification `rptrGroupChange' must be contained in at least one conformance group
2797: OBJECTS { rptrGroupIndex }
2798: STATUS deprecated
2799: DESCRIPTION
2800: "********* THIS OBJECT IS DEPRECATED **********
2801:
2802: In a system containing a single managed repeater,
2803: this notification is sent when a change occurs in the
2804: group structure of the repeater. This occurs only
2805: when a group is logically or physically removed
2806: from or added to a repeater. The varBind list
2807: contains the identifier of the group that was
2808: removed or added.
2809:
2810: The agent must throttle the generation of
2811: consecutive rptrGroupChange traps for the same
2812: group so that there is at least a five-second gap
2813: between traps of this type. When traps are
2814: throttled, they are dropped, not queued for
2815: sending at a future time. (Note that 'generating'
2816: a trap means sending to all configured
2817: recipients.)"
2818: REFERENCE
2819: "[IEEE 802.3 Mgt], 30.4.1.3.3, nGroupMapChange
2820: notification."
2821: ::= { snmpDot3RptrMgt 0 2 }
2822:
2823: rptrResetEvent NOTIFICATION-TYPE
2823: change recommended -
warning: notification `rptrResetEvent' must be contained in at least one conformance group
2824: OBJECTS { rptrOperStatus }
2825: STATUS deprecated
2826: DESCRIPTION
2827: "********* THIS OBJECT IS DEPRECATED **********
2828:
2829: In a system containing a single managed repeater-unit,
2830: the rptrResetEvent notification conveys information
2831: related to the operational status of the repeater.
2832: This trap is sent on completion of a repeater
2833: reset action. A repeater reset action is defined
2834: as an a transition to the START state of Fig 9-2
2835: in section 9 [IEEE 802.3 Std], when triggered by a
2836: management command (e.g., an SNMP Set on the
2837: rptrReset object).
2838:
2839: The agent must throttle the generation of
2840: consecutive rptrResetEvent traps so that there is
2841: at least a five-second gap between traps of this
2842: type. When traps are throttled, they are dropped,
2843: not queued for sending at a future time. (Note
2844: that 'generating' a trap means sending to all
2845: configured recipients.)
2846:
2847: The rptrResetEvent trap is not sent when the agent
2848: restarts and sends an SNMP coldStart or warmStart
2849: trap. However, it is recommended that a repeater
2850: agent send the rptrOperStatus object as an
2851: optional object with its coldStart and warmStart
2852: trap PDUs.
2853:
2854: The rptrOperStatus object must be included in the
2855: varbind list sent with this trap. The agent may
2856: optionally include the rptrHealthText object as
2857: well."
2858: REFERENCE
2859: "[IEEE 802.3 Mgt], 30.4.1.3.2, nRepeaterReset
2860: notification."
2861: ::= { snmpDot3RptrMgt 0 3 }
2862:
2863:
2864: -- Notifications for repeaters in a multiple-repeater implementation.
2865: -- An implementation may send either the single-repeater OR
2866: -- multiple-repeater version of these notifications (1 or 4; 2 or 5)
2867: -- but not both.
2868:
2869: rptrInfoHealth NOTIFICATION-TYPE
2869: change recommended -
warning: notification `rptrInfoHealth' must be contained in at least one conformance group
2870: OBJECTS { rptrInfoOperStatus }
2871: STATUS current
2872: DESCRIPTION
2873: "In a system containing multiple managed repeaters,
2874: the rptrInfoHealth notification conveys information
2875: related to the operational status of a repeater.
2876: It is sent either when the value of rptrInfoOperStatus
2877: changes, or upon completion of a non-disruptive test.
2878:
2879: The agent must throttle the generation of
2880: consecutive rptrInfoHealth notifications for
2881: the same repeater so that there is at least
2882: a five-second gap between notifications of this type.
2883: When notifications are throttled, they are dropped,
2884: not queued for sending at a future time. (Note
2885: that 'generating' a notification means sending
2886: to all configured recipients.)"
2887: REFERENCE
2888: "[IEEE 802.3 Mgt], 30.4.1.3.1, nRepeaterHealth
2889: notification."
2890: ::= { snmpDot3RptrMgt 0 4 }
2891:
2892: rptrInfoResetEvent NOTIFICATION-TYPE
2892: change recommended -
warning: notification `rptrInfoResetEvent' must be contained in at least one conformance group
2893: OBJECTS { rptrInfoOperStatus }
2894: STATUS current
2895: DESCRIPTION
2896: "In a system containing multiple managed
2897: repeaters, the rptrInfoResetEvent notification
2898: conveys information related to the operational
2899: status of a repeater. This notification is sent
2900: on completion of a repeater reset action. A
2901: repeater reset action is defined as a transition
2902: to the START state of Fig 9-2 in section 9 of
2903: [IEEE 802.3 Std], when triggered by a management
2904: command (e.g., an SNMP Set on the rptrInfoReset
2905: object).
2906:
2907: The agent must throttle the generation of
2908: consecutive rptrInfoResetEvent notifications for
2909: a single repeater so that there is at least
2910: a five-second gap between notifications of
2911: this type. When notifications are throttled,
2912: they are dropped, not queued for sending at
2913: a future time. (Note that 'generating' a
2914: notification means sending to all configured
2915: recipients.)
2916:
2917: The rptrInfoResetEvent is not sent when the
2918: agent restarts and sends an SNMP coldStart or
2919: warmStart trap. However, it is recommended that
2920: a repeater agent send the rptrInfoOperStatus
2921: object as an optional object with its coldStart
2922: and warmStart trap PDUs."
2923: REFERENCE
2924: "[IEEE 802.3 Mgt], 30.4.1.3.2, nRepeaterReset
2925: notification."
2926: ::= { snmpDot3RptrMgt 0 5 }
2927:
2928:
2929: -- Conformance information
2930: