Leaked source code of windows server 2003
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

1435 lines
50 KiB

  1. SNMP-REPEATER-MIB DEFINITIONS ::= BEGIN
  2. IMPORTS
  3. Counter, TimeTicks, Gauge
  4. FROM RFC1155-SMI
  5. DisplayString FROM RFC1213-MIB
  6. TRAP-TYPE FROM RFC-1215
  7. OBJECT-TYPE FROM RFC-1212;
  8. snmpDot3RptrMgt OBJECT IDENTIFIER ::= { mib-2 22 }
  9. -- All representations of MAC addresses in this MIB Module use,
  10. -- as a textual convention (i.e., this convention does not affect
  11. -- their encoding), the data type:
  12. MacAddress ::= OCTET STRING (SIZE (6)) -- a 6 octet address in
  13. -- the "canonical" order
  14. -- defined by IEEE 802.1a, i.e., as if it were transmitted least
  15. -- significant bit first.
  16. -- References
  17. --
  18. -- The following references are used throughout this MIB:
  19. --
  20. -- [IEEE 802.3 Std]
  21. -- refers to IEEE 802.3/ISO 8802-3 Information processing
  22. -- systems - Local area networks - Part 3: Carrier sense
  23. -- multiple access with collision detection (CSMA/CD)
  24. -- access method and physical layer specifications
  25. -- (2nd edition, September 21, 1990).
  26. --
  27. -- [IEEE 802.3 Rptr Mgt]
  28. -- refers to IEEE P802.3K, 'Layer Management for 10 Mb/s
  29. -- Baseband Repeaters, Section 19,' Draft Supplement to
  30. -- ANSI/IEEE 802.3, (Draft 8, April 9, 1992)
  31. -- MIB Groups
  32. --
  33. -- The rptrBasicPackage group is mandatory.
  34. -- The rptrMonitorPackage and rptrAddrTrackPackage
  35. -- groups are optional.
  36. rptrBasicPackage
  37. OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 1 }
  38. rptrMonitorPackage
  39. OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 2 }
  40. rptrAddrTrackPackage
  41. OBJECT IDENTIFIER ::= { snmpDot3RptrMgt 3 }
  42. -- object identifiers for organizing the information
  43. -- in the groups by repeater, port-group, and port
  44. rptrRptrInfo
  45. OBJECT IDENTIFIER ::= { rptrBasicPackage 1 }
  46. rptrGroupInfo
  47. OBJECT IDENTIFIER ::= { rptrBasicPackage 2 }
  48. rptrPortInfo
  49. OBJECT IDENTIFIER ::= { rptrBasicPackage 3 }
  50. rptrMonitorRptrInfo
  51. OBJECT IDENTIFIER ::= { rptrMonitorPackage 1 }
  52. rptrMonitorGroupInfo
  53. OBJECT IDENTIFIER ::= { rptrMonitorPackage 2 }
  54. rptrMonitorPortInfo
  55. OBJECT IDENTIFIER ::= { rptrMonitorPackage 3 }
  56. rptrAddrTrackRptrInfo -- this subtree is currently unused
  57. OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 1 }
  58. rptrAddrTrackGroupInfo -- this subtree is currently unused
  59. OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 2 }
  60. rptrAddrTrackPortInfo
  61. OBJECT IDENTIFIER ::= { rptrAddrTrackPackage 3 }
  62. --
  63. -- The BASIC GROUP
  64. --
  65. -- Implementation of the Basic Group is mandatory for all
  66. -- managed repeaters.
  67. --
  68. -- Basic Repeater Information
  69. --
  70. -- Configuration, status, and control objects for the overall
  71. -- repeater
  72. --
  73. rptrGroupCapacity OBJECT-TYPE
  74. SYNTAX INTEGER (1..1024)
  75. ACCESS read-only
  76. STATUS mandatory
  77. DESCRIPTION
  78. "The rptrGroupCapacity is the number of groups
  79. that can be contained within the repeater. Within
  80. each managed repeater, the groups are uniquely
  81. numbered in the range from 1 to rptrGroupCapacity.
  82. Some groups may not be present in the repeater, in
  83. which case the actual number of groups present
  84. will be less than rptrGroupCapacity. The number
  85. of groups present will never be greater than
  86. rptrGroupCapacity.
  87. Note: In practice, this will generally be the
  88. number of field-replaceable units (i.e., modules,
  89. cards, or boards) that can fit in the physical
  90. repeater enclosure, and the group numbers will
  91. correspond to numbers marked on the physical
  92. enclosure."
  93. REFERENCE
  94. "Reference IEEE 802.3 Rptr Mgt, 19.2.3.2,
  95. aRepeaterGroupCapacity."
  96. ::= { rptrRptrInfo 1 }
  97. rptrOperStatus OBJECT-TYPE
  98. SYNTAX INTEGER {
  99. other(1), -- undefined or unknown status
  100. ok(2), -- no known failures
  101. rptrFailure(3), -- repeater-related failure
  102. groupFailure(4), -- group-related failure
  103. portFailure(5), -- port-related failure
  104. generalFailure(6) -- failure, unspecified type
  105. }
  106. ACCESS read-only
  107. STATUS mandatory
  108. DESCRIPTION
  109. "The rptrOperStatus object indicates the
  110. operational state of the repeater. The
  111. rptrHealthText object may be consulted for more
  112. specific information about the state of the
  113. repeater's health.
  114. In the case of multiple kinds of failures (e.g.,
  115. repeater failure and port failure), the value of
  116. this attribute shall reflect the highest priority
  117. failure in the following order, listed highest
  118. priority first:
  119. rptrFailure(3)
  120. groupFailure(4)
  121. portFailure(5)
  122. generalFailure(6)."
  123. REFERENCE
  124. "Reference IEEE 802.3 Rptr Mgt, 19.2.3.2,
  125. aRepeaterHealthState."
  126. ::= { rptrRptrInfo 2 }
  127. rptrHealthText OBJECT-TYPE
  128. SYNTAX DisplayString (SIZE (0..255))
  129. ACCESS read-only
  130. STATUS mandatory
  131. DESCRIPTION
  132. "The health text object is a text string that
  133. provides information relevant to the operational
  134. state of the repeater. Agents may use this string
  135. to provide detailed information on current
  136. failures, including how they were detected, and/or
  137. instructions for problem resolution. The contents
  138. are agent-specific."
  139. REFERENCE
  140. "Reference IEEE 802.3 Rptr Mgt, 19.2.3.2,
  141. aRepeaterHealthText."
  142. ::= { rptrRptrInfo 3 }
  143. rptrReset OBJECT-TYPE
  144. SYNTAX INTEGER {
  145. noReset(1),
  146. reset(2)
  147. }
  148. ACCESS read-write
  149. STATUS mandatory
  150. DESCRIPTION
  151. "Setting this object to reset(2) causes a
  152. transition to the START state of Fig 9-2 in
  153. section 9 [IEEE 802.3 Std].
  154. Setting this object to noReset(1) has no effect.
  155. The agent will always return the value noReset(1)
  156. when this object is read.
  157. After receiving a request to set this variable to
  158. reset(2), the agent is allowed to delay the reset
  159. for a short period. For example, the implementor
  160. may choose to delay the reset long enough to allow
  161. the SNMP response to be transmitted. In any
  162. event, the SNMP response must be transmitted.
  163. This action does not reset the management counters
  164. defined in this document nor does it affect the
  165. portAdminStatus parameters. Included in this
  166. action is the execution of a disruptive Self-Test
  167. with the following characteristics: a) The nature
  168. of the tests is not specified. b) The test resets
  169. the repeater but without affecting management
  170. information about the repeater. c) The test does
  171. not inject packets onto any segment. d) Packets
  172. received during the test may or may not be
  173. transferred. e) The test does not interfere with
  174. management functions.
  175. After performing this self-test, the agent will
  176. update the repeater health information (including
  177. rptrOperStatus and rptrHealthText), and send a
  178. rptrHealth trap."
  179. REFERENCE
  180. "Reference IEEE 802.3 Rptr Mgt, 19.2.3.3,
  181. acResetRepeater."
  182. ::= { rptrRptrInfo 4 }
  183. rptrNonDisruptTest OBJECT-TYPE
  184. SYNTAX INTEGER {
  185. noSelfTest(1),
  186. selfTest(2)
  187. }
  188. ACCESS read-write
  189. STATUS mandatory
  190. DESCRIPTION
  191. "Setting this object to selfTest(2) causes the
  192. repeater to perform a agent-specific, non-
  193. disruptive self-test that has the following
  194. characteristics: a) The nature of the tests is
  195. not specified. b) The test does not change the
  196. state of the repeater or management information
  197. about the repeater. c) The test does not inject
  198. packets onto any segment. d) The test does not
  199. prevent the relay of any packets. e) The test
  200. does not interfere with management functions.
  201. After performing this test, the agent will update
  202. the repeater health information (including
  203. rptrOperStatus and rptrHealthText) and send a
  204. rptrHealth trap.
  205. Note that this definition allows returning an
  206. 'okay' result after doing a trivial test.
  207. Setting this object to noSelfTest(1) has no
  208. effect. The agent will always return the value
  209. noSelfTest(1) when this object is read."
  210. REFERENCE
  211. "Reference IEEE 802.3 Rptr Mgt, 19.2.3.3,
  212. acExecuteNonDisruptiveSelfTest."
  213. ::= { rptrRptrInfo 5 }
  214. rptrTotalPartitionedPorts OBJECT-TYPE
  215. SYNTAX Gauge
  216. ACCESS read-only
  217. STATUS mandatory
  218. DESCRIPTION
  219. "This object returns the total number of ports in
  220. the repeater whose current state meets all three
  221. of the following criteria: rptrPortOperStatus
  222. does not have the value notPresent(3),
  223. rptrPortAdminStatus is enabled(1), and
  224. rptrPortAutoPartitionState is autoPartitioned(2)."
  225. ::= { rptrRptrInfo 6 }
  226. --
  227. -- The Basic Port Group Table
  228. --
  229. rptrGroupTable OBJECT-TYPE
  230. SYNTAX SEQUENCE OF RptrGroupEntry
  231. ACCESS not-accessible
  232. STATUS mandatory
  233. DESCRIPTION
  234. "Table of descriptive and status information about
  235. the groups of ports."
  236. ::= { rptrGroupInfo 1 }
  237. rptrGroupEntry OBJECT-TYPE
  238. SYNTAX RptrGroupEntry
  239. ACCESS not-accessible
  240. STATUS mandatory
  241. DESCRIPTION
  242. "An entry in the table, containing information
  243. about a single group of ports."
  244. INDEX { rptrGroupIndex }
  245. ::= { rptrGroupTable 1 }
  246. RptrGroupEntry ::=
  247. SEQUENCE {
  248. rptrGroupIndex
  249. INTEGER,
  250. rptrGroupDescr
  251. DisplayString,
  252. rptrGroupObjectID
  253. OBJECT IDENTIFIER,
  254. rptrGroupOperStatus
  255. INTEGER,
  256. rptrGroupLastOperStatusChange
  257. TimeTicks,
  258. rptrGroupPortCapacity
  259. INTEGER
  260. }
  261. rptrGroupIndex OBJECT-TYPE
  262. SYNTAX INTEGER (1..1024)
  263. ACCESS read-only
  264. STATUS mandatory
  265. DESCRIPTION
  266. "This object identifies the group within the
  267. repeater for which this entry contains
  268. information. This value is never greater than
  269. rptrGroupCapacity."
  270. REFERENCE
  271. "Reference IEEE 802.3 Rptr Mgt, 19.2.5.2,
  272. aGroupID."
  273. ::= { rptrGroupEntry 1 }
  274. rptrGroupDescr OBJECT-TYPE
  275. SYNTAX DisplayString (SIZE (0..255))
  276. ACCESS read-only
  277. STATUS mandatory
  278. DESCRIPTION
  279. "A textual description of the group. This value
  280. should include the full name and version
  281. identification of the group's hardware type and
  282. indicate how the group is differentiated from
  283. other types of groups in the repeater. Plug-in
  284. Module, Rev A' or 'Barney Rubble 10BASE-T 4-port
  285. SIMM socket Version 2.1' are examples of valid
  286. group descriptions.
  287. It is mandatory that this only contain printable
  288. ASCII characters."
  289. ::= { rptrGroupEntry 2 }
  290. rptrGroupObjectID OBJECT-TYPE
  291. SYNTAX OBJECT IDENTIFIER
  292. ACCESS read-only
  293. STATUS mandatory
  294. DESCRIPTION
  295. "The vendor's authoritative identification of the
  296. group. This value may be allocated within the SMI
  297. enterprises subtree (1.3.6.1.4.1) and provides a
  298. straight-forward and unambiguous means for
  299. determining what kind of group is being managed.
  300. For example, this object could take the value
  301. 1.3.6.1.4.1.4242.1.2.14 if vendor 'Flintstones,
  302. Inc.' was assigned the subtree 1.3.6.1.4.1.4242,
  303. and had assigned the identifier
  304. 1.3.6.1.4.1.4242.1.2.14 to its 'Wilma Flintstone
  305. 6-Port FOIRL Plug-in Module.'"
  306. ::= { rptrGroupEntry 3 }
  307. rptrGroupOperStatus OBJECT-TYPE
  308. SYNTAX INTEGER {
  309. other(1),
  310. operational(2),
  311. malfunctioning(3),
  312. notPresent(4),
  313. underTest(5),
  314. resetInProgress(6)
  315. }
  316. ACCESS read-only
  317. STATUS mandatory
  318. DESCRIPTION
  319. "An object that indicates the operational status
  320. of the group.
  321. A status of notPresent(4) indicates that the group
  322. is temporarily or permanently physically and/or
  323. logically not a part of the repeater. It is an
  324. implementation-specific matter as to whether the
  325. agent effectively removes notPresent entries from
  326. the table.
  327. A status of operational(2) indicates that the
  328. group is functioning, and a status of
  329. malfunctioning(3) indicates that the group is
  330. malfunctioning in some way."
  331. ::= { rptrGroupEntry 4 }
  332. rptrGroupLastOperStatusChange OBJECT-TYPE
  333. SYNTAX TimeTicks
  334. ACCESS read-only
  335. STATUS mandatory
  336. DESCRIPTION
  337. "An object that contains the value of sysUpTime at
  338. the time that the value of the rptrGroupOperStatus
  339. object for this group last changed.
  340. A value of zero indicates that the group's
  341. operational status has not changed since the agent
  342. last restarted."
  343. ::= { rptrGroupEntry 5 }
  344. rptrGroupPortCapacity OBJECT-TYPE
  345. SYNTAX INTEGER (1..1024)
  346. ACCESS read-only
  347. STATUS mandatory
  348. DESCRIPTION
  349. "The rptrGroupPortCapacity is the number of ports
  350. that can be contained within the group. Valid
  351. range is 1-1024. Within each group, the ports are
  352. uniquely numbered in the range from 1 to
  353. rptrGroupPortCapacity.
  354. Note: In practice, this will generally be the
  355. number of ports on a module, card, or board, and
  356. the port numbers will correspond to numbers marked
  357. on the physical embodiment."
  358. REFERENCE
  359. "Reference IEEE 802.3 Rptr Mgt, 19.2.5.2,
  360. aGroupPortCapacity."
  361. ::= { rptrGroupEntry 6 }
  362. --
  363. -- The Basic Port Table
  364. --
  365. rptrPortTable OBJECT-TYPE
  366. SYNTAX SEQUENCE OF RptrPortEntry
  367. ACCESS not-accessible
  368. STATUS mandatory
  369. DESCRIPTION
  370. "Table of descriptive and status information about
  371. the ports."
  372. ::= { rptrPortInfo 1 }
  373. rptrPortEntry OBJECT-TYPE
  374. SYNTAX RptrPortEntry
  375. ACCESS not-accessible
  376. STATUS mandatory
  377. DESCRIPTION
  378. "An entry in the table, containing information
  379. about a single port."
  380. INDEX { rptrPortGroupIndex, rptrPortIndex }
  381. ::= { rptrPortTable 1 }
  382. RptrPortEntry ::=
  383. SEQUENCE {
  384. rptrPortGroupIndex
  385. INTEGER,
  386. rptrPortIndex
  387. INTEGER,
  388. rptrPortAdminStatus
  389. INTEGER,
  390. rptrPortAutoPartitionState
  391. INTEGER,
  392. rptrPortOperStatus
  393. INTEGER
  394. }
  395. rptrPortGroupIndex OBJECT-TYPE
  396. SYNTAX INTEGER (1..1024)
  397. ACCESS read-only
  398. STATUS mandatory
  399. DESCRIPTION
  400. "This object identifies the group containing the
  401. port for which this entry contains information."
  402. ::= { rptrPortEntry 1 }
  403. rptrPortIndex OBJECT-TYPE
  404. SYNTAX INTEGER (1..1024)
  405. ACCESS read-only
  406. STATUS mandatory
  407. DESCRIPTION
  408. "This object identifies the port within the group
  409. for which this entry contains information. This
  410. value can never be greater than
  411. rptrGroupPortCapacity for the associated group."
  412. REFERENCE
  413. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2,
  414. aPortID."
  415. ::= { rptrPortEntry 2 }
  416. rptrPortAdminStatus OBJECT-TYPE
  417. SYNTAX INTEGER {
  418. enabled(1),
  419. disabled(2)
  420. }
  421. ACCESS read-write
  422. STATUS mandatory
  423. DESCRIPTION
  424. "Setting this object to disabled(2) disables the
  425. port. A disabled port neither transmits nor
  426. receives. Once disabled, a port must be
  427. explicitly enabled to restore operation. A port
  428. which is disabled when power is lost or when a
  429. reset is exerted shall remain disabled when normal
  430. operation resumes.
  431. The admin status takes precedence over auto-
  432. partition and functionally operates between the
  433. auto-partition mechanism and the AUI/PMA.
  434. Setting this object to enabled(1) enables the port
  435. and exerts a BEGIN on the port's auto-partition
  436. state machine.
  437. (In effect, when a port is disabled, the value of
  438. rptrPortAutoPartitionState for that port is frozen
  439. until the port is next enabled. When the port
  440. becomes enabled, the rptrPortAutoPartitionState
  441. becomes notAutoPartitioned(1), regardless of its
  442. pre-disabling state.)"
  443. REFERENCE
  444. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2,
  445. aPortAdminState and 19.2.6.3, acPortAdminControl."
  446. ::= { rptrPortEntry 3 }
  447. rptrPortAutoPartitionState OBJECT-TYPE
  448. SYNTAX INTEGER {
  449. notAutoPartitioned(1),
  450. autoPartitioned(2)
  451. }
  452. ACCESS read-only
  453. STATUS mandatory
  454. DESCRIPTION
  455. "The autoPartitionState flag indicates whether the
  456. port is currently partitioned by the repeater's
  457. auto-partition protection.
  458. The conditions that cause port partitioning are
  459. specified in partition state machine in Section 9
  460. [IEEE 802.3 Std]. They are not differentiated
  461. here."
  462. REFERENCE
  463. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2,
  464. aAutoPartitionState."
  465. ::= { rptrPortEntry 4 }
  466. rptrPortOperStatus OBJECT-TYPE
  467. SYNTAX INTEGER {
  468. operational(1),
  469. notOperational(2),
  470. notPresent(3)
  471. }
  472. ACCESS read-only
  473. STATUS mandatory
  474. DESCRIPTION
  475. "This object indicates the port's operational
  476. status. The notPresent(3) status indicates the
  477. port is physically removed (note this may or may
  478. not be possible depending on the type of port.)
  479. The operational(1) status indicates that the port
  480. is enabled (see rptrPortAdminStatus) and working,
  481. even though it might be auto-partitioned (see
  482. rptrPortAutoPartitionState).
  483. If this object has the value operational(1) and
  484. rptrPortAdminStatus is set to disabled(2), it is
  485. expected that this object's value will soon change
  486. to notOperational(2)."
  487. ::= { rptrPortEntry 5 }
  488. --
  489. -- The MONITOR GROUP
  490. --
  491. -- Implementation of this group is optional, but within the
  492. -- group all elements are mandatory. If a managed repeater
  493. -- implements any part of this group, the entire group shall
  494. -- be implemented.
  495. --
  496. -- Repeater Monitor Information
  497. --
  498. -- Performance monitoring statistics for the repeater
  499. --
  500. rptrMonitorTransmitCollisions OBJECT-TYPE
  501. SYNTAX Counter
  502. ACCESS read-only
  503. STATUS mandatory
  504. DESCRIPTION
  505. "This counter is incremented every time the
  506. repeater state machine enters the TRANSMIT
  507. COLLISION state from any state other than ONE PORT
  508. LEFT (Ref: Fig 9-2, IEEE 802.3 Std).
  509. The approximate minimum time for rollover of this
  510. counter is 16 hours."
  511. REFERENCE
  512. "Reference IEEE 802.3 Rptr Mgt, 19.2.3.2,
  513. aTransmitCollisions."
  514. ::= { rptrMonitorRptrInfo 1 }
  515. --
  516. -- The Group Monitor Table
  517. --
  518. rptrMonitorGroupTable OBJECT-TYPE
  519. SYNTAX SEQUENCE OF RptrMonitorGroupEntry
  520. ACCESS not-accessible
  521. STATUS mandatory
  522. DESCRIPTION
  523. "Table of performance and error statistics for the
  524. groups."
  525. ::= { rptrMonitorGroupInfo 1 }
  526. rptrMonitorGroupEntry OBJECT-TYPE
  527. SYNTAX RptrMonitorGroupEntry
  528. ACCESS not-accessible
  529. STATUS mandatory
  530. DESCRIPTION
  531. "An entry in the table, containing total
  532. performance and error statistics for a single
  533. group. Regular retrieval of the information in
  534. this table provides a means of tracking the
  535. performance and health of the networked devices
  536. attached to this group's ports.
  537. The counters in this table are redundant in the
  538. sense that they are the summations of information
  539. already available through other objects. However,
  540. these sums provide a considerable optimization of
  541. network management traffic over the otherwise
  542. necessary retrieval of the individual counters
  543. included in each sum."
  544. INDEX { rptrMonitorGroupIndex }
  545. ::= { rptrMonitorGroupTable 1 }
  546. RptrMonitorGroupEntry ::=
  547. SEQUENCE {
  548. rptrMonitorGroupIndex
  549. INTEGER,
  550. rptrMonitorGroupTotalFrames
  551. Counter,
  552. rptrMonitorGroupTotalOctets
  553. Counter,
  554. rptrMonitorGroupTotalErrors
  555. Counter
  556. }
  557. rptrMonitorGroupIndex OBJECT-TYPE
  558. SYNTAX INTEGER (1..1024)
  559. ACCESS read-only
  560. STATUS mandatory
  561. DESCRIPTION
  562. "This object identifies the group within the
  563. repeater for which this entry contains
  564. information."
  565. ::= { rptrMonitorGroupEntry 1 }
  566. rptrMonitorGroupTotalFrames OBJECT-TYPE
  567. SYNTAX Counter
  568. ACCESS read-only
  569. STATUS mandatory
  570. DESCRIPTION
  571. "The total number of frames of valid frame length
  572. that have been received on the ports in this group
  573. and for which the FCSError and CollisionEvent
  574. signals were not asserted. This counter is the
  575. summation of the values of the
  576. rptrMonitorPortReadableFrames counters for all of
  577. the ports in the group.
  578. This statistic provides one of the parameters
  579. necessary for obtaining the packet error rate.
  580. The approximate minimum time for rollover of this
  581. counter is 80 hours."
  582. ::= { rptrMonitorGroupEntry 2 }
  583. rptrMonitorGroupTotalOctets OBJECT-TYPE
  584. SYNTAX Counter
  585. ACCESS read-only
  586. STATUS mandatory
  587. DESCRIPTION
  588. "The total number of octets contained in the valid
  589. frames that have been received on the ports in
  590. this group. This counter is the summation of the
  591. values of the rptrMonitorPortReadableOctets
  592. counters for all of the ports in the group.
  593. This statistic provides an indicator of the total
  594. data transferred. The approximate minimum time
  595. for rollover of this counter is 58 minutes."
  596. ::= { rptrMonitorGroupEntry 3 }
  597. rptrMonitorGroupTotalErrors OBJECT-TYPE
  598. SYNTAX Counter
  599. ACCESS read-only
  600. STATUS mandatory
  601. DESCRIPTION
  602. "The total number of errors which have occurred on
  603. all of the ports in this group. This counter is
  604. the summation of the values of the
  605. rptrMonitorPortTotalErrors counters for all of the
  606. ports in the group."
  607. ::= { rptrMonitorGroupEntry 4 }
  608. --
  609. -- The Port Monitor Table
  610. --
  611. rptrMonitorPortTable OBJECT-TYPE
  612. SYNTAX SEQUENCE OF RptrMonitorPortEntry
  613. ACCESS not-accessible
  614. STATUS mandatory
  615. DESCRIPTION
  616. "Table of performance and error statistics for the
  617. ports."
  618. ::= { rptrMonitorPortInfo 1 }
  619. rptrMonitorPortEntry OBJECT-TYPE
  620. SYNTAX RptrMonitorPortEntry
  621. ACCESS not-accessible
  622. STATUS mandatory
  623. DESCRIPTION
  624. "An entry in the table, containing performance and
  625. error statistics for a single port."
  626. INDEX { rptrMonitorPortGroupIndex, rptrMonitorPortIndex }
  627. ::= { rptrMonitorPortTable 1 }
  628. RptrMonitorPortEntry ::=
  629. SEQUENCE {
  630. rptrMonitorPortGroupIndex
  631. INTEGER,
  632. rptrMonitorPortIndex
  633. INTEGER,
  634. rptrMonitorPortReadableFrames
  635. Counter,
  636. rptrMonitorPortReadableOctets
  637. Counter,
  638. rptrMonitorPortFCSErrors
  639. Counter,
  640. rptrMonitorPortAlignmentErrors
  641. Counter,
  642. rptrMonitorPortFrameTooLongs
  643. Counter,
  644. rptrMonitorPortShortEvents
  645. Counter,
  646. rptrMonitorPortRunts
  647. Counter,
  648. rptrMonitorPortCollisions
  649. Counter,
  650. rptrMonitorPortLateEvents
  651. Counter,
  652. rptrMonitorPortVeryLongEvents
  653. Counter,
  654. rptrMonitorPortDataRateMismatches
  655. Counter,
  656. rptrMonitorPortAutoPartitions
  657. Counter,
  658. rptrMonitorPortTotalErrors
  659. Counter
  660. }
  661. rptrMonitorPortGroupIndex OBJECT-TYPE
  662. SYNTAX INTEGER (1..1024)
  663. ACCESS read-only
  664. STATUS mandatory
  665. DESCRIPTION
  666. "This object identifies the group containing the
  667. port for which this entry contains information."
  668. ::= { rptrMonitorPortEntry 1 }
  669. rptrMonitorPortIndex OBJECT-TYPE
  670. SYNTAX INTEGER (1..1024)
  671. ACCESS read-only
  672. STATUS mandatory
  673. DESCRIPTION
  674. "This object identifies the port within the group
  675. for which this entry contains information."
  676. REFERENCE
  677. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2,
  678. aPortID."
  679. ::= { rptrMonitorPortEntry 2 }
  680. rptrMonitorPortReadableFrames OBJECT-TYPE
  681. SYNTAX Counter
  682. ACCESS read-only
  683. STATUS mandatory
  684. DESCRIPTION
  685. "This object is the number of frames of valid
  686. frame length that have been received on this port.
  687. This counter is incremented by one for each frame
  688. received on this port whose OctetCount is greater
  689. than or equal to minFrameSize and less than or
  690. equal to maxFrameSize (Ref: IEEE 802.3 Std,
  691. 4.4.2.1) and for which the FCSError and
  692. CollisionEvent signals are not asserted.
  693. This statistic provides one of the parameters
  694. necessary for obtaining the packet error rate.
  695. The approximate minimum time for rollover of this
  696. counter is 80 hours."
  697. REFERENCE
  698. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2,
  699. aReadableFrames."
  700. ::= { rptrMonitorPortEntry 3 }
  701. rptrMonitorPortReadableOctets OBJECT-TYPE
  702. SYNTAX Counter
  703. ACCESS read-only
  704. STATUS mandatory
  705. DESCRIPTION
  706. "This object is the number of octets contained in
  707. valid frames that have been received on this port.
  708. This counter is incremented by OctetCount for each
  709. frame received on this port which has been
  710. determined to be a readable frame (i.e., including
  711. FCS octets but excluding framing bits and dribble
  712. bits).
  713. This statistic provides an indicator of the total
  714. data transferred. The approximate minimum time
  715. for rollover of this counter is 58 minutes."
  716. REFERENCE
  717. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2,
  718. aReadableOctets."
  719. ::= { rptrMonitorPortEntry 4 }
  720. rptrMonitorPortFCSErrors OBJECT-TYPE
  721. SYNTAX Counter
  722. ACCESS read-only
  723. STATUS mandatory
  724. DESCRIPTION
  725. "This counter is incremented by one for each frame
  726. received on this port with the FCSError signal
  727. asserted and the FramingError and CollisionEvent
  728. signals deasserted and whose OctetCount is greater
  729. than or equal to minFrameSize and less than or
  730. equal to maxFrameSize (Ref: 4.4.2.1, IEEE 802.3
  731. Std).
  732. The approximate minimum time for rollover of this
  733. counter is 80 hours."
  734. REFERENCE
  735. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2,
  736. aFrameCheckSequenceErrors."
  737. ::= { rptrMonitorPortEntry 5 }
  738. rptrMonitorPortAlignmentErrors OBJECT-TYPE
  739. SYNTAX Counter
  740. ACCESS read-only
  741. STATUS mandatory
  742. DESCRIPTION
  743. "This counter is incremented by one for each frame
  744. received on this port with the FCSError and
  745. FramingError signals asserted and CollisionEvent
  746. signal deasserted and whose OctetCount is greater
  747. than or equal to minFrameSize and less than or
  748. equal to maxFrameSize (Ref: IEEE 802.3 Std,
  749. 4.4.2.1). If rptrMonitorPortAlignmentErrors is
  750. incremented then the rptrMonitorPortFCSErrors
  751. Counter shall not be incremented for the same
  752. frame.
  753. The approximate minimum time for rollover of this
  754. counter is 80 hours."
  755. REFERENCE
  756. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2,
  757. aAlignmentErrors."
  758. ::= { rptrMonitorPortEntry 6 }
  759. rptrMonitorPortFrameTooLongs OBJECT-TYPE
  760. SYNTAX Counter
  761. ACCESS read-only
  762. STATUS mandatory
  763. DESCRIPTION
  764. "This counter is incremented by one for each frame
  765. received on this port whose OctetCount is greater
  766. than maxFrameSize (Ref: 4.4.2.1, IEEE 802.3 Std).
  767. If rptrMonitorPortFrameTooLongs is incremented
  768. then neither the rptrMonitorPortAlignmentErrors
  769. nor the rptrMonitorPortFCSErrors counter shall be
  770. incremented for the frame.
  771. The approximate minimum time for rollover of this
  772. counter is 61 days."
  773. REFERENCE
  774. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2,
  775. aFramesTooLong."
  776. ::= { rptrMonitorPortEntry 7 }
  777. rptrMonitorPortShortEvents OBJECT-TYPE
  778. SYNTAX Counter
  779. ACCESS read-only
  780. STATUS mandatory
  781. DESCRIPTION
  782. "This counter is incremented by one for each
  783. CarrierEvent on this port with ActivityDuration
  784. less than ShortEventMaxTime. ShortEventMaxTime is
  785. greater than 74 bit times and less than 82 bit
  786. times. ShortEventMaxTime has tolerances included
  787. to provide for circuit losses between a
  788. conformance test point at the AUI and the
  789. measurement point within the state machine.
  790. Note: shortEvents may indicate externally
  791. generated noise hits which will cause the repeater
  792. to transmit Runts to its other ports, or propagate
  793. a collision (which may be late) back to the
  794. transmitting DTE and damaged frames to the rest of
  795. the network.
  796. Implementors may wish to consider selecting the
  797. ShortEventMaxTime towards the lower end of the
  798. allowed tolerance range to accommodate bit losses
  799. suffered through physical channel devices not
  800. budgeted for within this standard.
  801. The approximate minimum time for rollover of this
  802. counter is 16 hours."
  803. REFERENCE
  804. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2,
  805. aShortEvents."
  806. ::= { rptrMonitorPortEntry 8 }
  807. rptrMonitorPortRunts OBJECT-TYPE
  808. SYNTAX Counter
  809. ACCESS read-only
  810. STATUS mandatory
  811. DESCRIPTION
  812. "This counter is incremented by one for each
  813. CarrierEvent on this port that meets one of the
  814. following two conditions. Only one test need be
  815. made. a) The ActivityDuration is greater than
  816. ShortEventMaxTime and less than ValidPacketMinTime
  817. and the CollisionEvent signal is deasserted. b)
  818. The OctetCount is less than 64, the
  819. ActivityDuration is greater than ShortEventMaxTime
  820. and the CollisionEvent signal is deasserted.
  821. ValidPacketMinTime is greater than or equal to 552
  822. bit times and less than 565 bit times.
  823. An event whose length is greater than 74 bit times
  824. but less than 82 bit times shall increment either
  825. the shortEvents counter or the runts counter but
  826. not both. A CarrierEvent greater than or equal to
  827. 552 bit times but less than 565 bit times may or
  828. may not be counted as a runt.
  829. ValidPacketMinTime has tolerances included to
  830. provide for circuit losses between a conformance
  831. test point at the AUI and the measurement point
  832. within the state machine.
  833. Runts usually indicate collision fragments, a
  834. normal network event. In certain situations
  835. associated with large diameter networks a
  836. percentage of collision fragments may exceed
  837. ValidPacketMinTime.
  838. The approximate minimum time for rollover of this
  839. counter is 16 hours."
  840. REFERENCE
  841. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2, aRunts."
  842. ::= { rptrMonitorPortEntry 9 }
  843. rptrMonitorPortCollisions OBJECT-TYPE
  844. SYNTAX Counter
  845. ACCESS read-only
  846. STATUS mandatory
  847. DESCRIPTION
  848. "This counter is incremented by one for any
  849. CarrierEvent signal on any port for which the
  850. CollisionEvent signal on this port is also
  851. asserted.
  852. The approximate minimum time for rollover of this
  853. counter is 16 hours."
  854. REFERENCE
  855. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2,
  856. aCollisions."
  857. ::= { rptrMonitorPortEntry 10 }
  858. rptrMonitorPortLateEvents OBJECT-TYPE
  859. SYNTAX Counter
  860. ACCESS read-only
  861. STATUS mandatory
  862. DESCRIPTION
  863. "This counter is incremented by one for each
  864. CarrierEvent on this port in which the CollIn(X)
  865. variable transitions to the value SQE (Ref:
  866. 9.6.6.2, IEEE 802.3 Std) while the
  867. ActivityDuration is greater than the
  868. LateEventThreshold. Such a CarrierEvent is
  869. counted twice, as both a collision and as a
  870. lateEvent.
  871. The LateEventThreshold is greater than 480 bit
  872. times and less than 565 bit times.
  873. LateEventThreshold has tolerances included to
  874. permit an implementation to build a single
  875. threshold to serve as both the LateEventThreshold
  876. and ValidPacketMinTime threshold.
  877. The approximate minimum time for rollover of this
  878. counter is 81 hours."
  879. REFERENCE
  880. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2,
  881. aLateEvents."
  882. ::= { rptrMonitorPortEntry 11 }
  883. rptrMonitorPortVeryLongEvents OBJECT-TYPE
  884. SYNTAX Counter
  885. ACCESS read-only
  886. STATUS mandatory
  887. DESCRIPTION
  888. "This counter is incremented by one for each
  889. CarrierEvent on this port whose ActivityDuration
  890. is greater than the MAU Jabber Lockup Protection
  891. timer TW3 (Ref: 9.6.1 & 9.6.5, IEEE 802.3 Std).
  892. Other counters may be incremented as appropriate."
  893. REFERENCE
  894. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2,
  895. aVeryLongEvents."
  896. ::= { rptrMonitorPortEntry 12 }
  897. rptrMonitorPortDataRateMismatches OBJECT-TYPE
  898. SYNTAX Counter
  899. ACCESS read-only
  900. STATUS mandatory
  901. DESCRIPTION
  902. "This counter is incremented by one for each frame
  903. received on this port that meets all of the
  904. following conditions: a) The CollisionEvent
  905. signal is not asserted. b) The ActivityDuration
  906. is greater than ValidPacketMinTime. c) The
  907. frequency (data rate) is detectably mismatched
  908. from the local transmit frequency. The exact
  909. degree of mismatch is vendor specific and is to be
  910. defined by the vendor for conformance testing.
  911. When this event occurs, other counters whose
  912. increment conditions were satisfied may or may not
  913. also be incremented, at the implementor's
  914. discretion. Whether or not the repeater was able
  915. to maintain data integrity is beyond the scope of
  916. this standard."
  917. REFERENCE
  918. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2,
  919. aDataRateMismatches."
  920. ::= { rptrMonitorPortEntry 13 }
  921. rptrMonitorPortAutoPartitions OBJECT-TYPE
  922. SYNTAX Counter
  923. ACCESS read-only
  924. STATUS mandatory
  925. DESCRIPTION
  926. "This counter is incremented by one for each time
  927. the repeater has automatically partitioned this
  928. port. The conditions that cause port partitioning
  929. are specified in the partition state machine in
  930. Section 9 [IEEE 802.3 Std]. They are not
  931. differentiated here."
  932. REFERENCE
  933. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2,
  934. aAutoPartitions."
  935. ::= { rptrMonitorPortEntry 14 }
  936. rptrMonitorPortTotalErrors OBJECT-TYPE
  937. SYNTAX Counter
  938. ACCESS read-only
  939. STATUS mandatory
  940. DESCRIPTION
  941. "The total number of errors which have occurred on
  942. this port. This counter is the summation of the
  943. values of other error counters (for the same
  944. port), namely:
  945. rptrMonitorPortFCSErrors,
  946. rptrMonitorPortAlignmentErrors,
  947. rptrMonitorPortFrameTooLongs,
  948. rptrMonitorPortShortEvents,
  949. rptrMonitorPortLateEvents,
  950. rptrMonitorPortVeryLongEvents, and
  951. rptrMonitorPortDataRateMismatches.
  952. This counter is redundant in the sense that it is
  953. the summation of information already available
  954. through other objects. However, it is included
  955. specifically because the regular retrieval of this
  956. object as a means of tracking the health of a port
  957. provides a considerable optimization of network
  958. management traffic over the otherwise necessary
  959. retrieval of the summed counters."
  960. ::= { rptrMonitorPortEntry 15 }
  961. --
  962. -- The ADDRESS TRACKING GROUP
  963. --
  964. -- Implementation of this group is optional; it is appropriate
  965. -- for all systems which have the necessary instrumentation. If a
  966. -- managed repeater implements any part of this group, the entire
  967. -- group shall be implemented.
  968. --
  969. -- The Port Address Tracking Table
  970. --
  971. rptrAddrTrackTable OBJECT-TYPE
  972. SYNTAX SEQUENCE OF RptrAddrTrackEntry
  973. ACCESS not-accessible
  974. STATUS mandatory
  975. DESCRIPTION
  976. "Table of address mapping information about the
  977. ports."
  978. ::= { rptrAddrTrackPortInfo 1 }
  979. rptrAddrTrackEntry OBJECT-TYPE
  980. SYNTAX RptrAddrTrackEntry
  981. ACCESS not-accessible
  982. STATUS mandatory
  983. DESCRIPTION
  984. "An entry in the table, containing address mapping
  985. information about a single port."
  986. INDEX { rptrAddrTrackGroupIndex, rptrAddrTrackPortIndex }
  987. ::= { rptrAddrTrackTable 1 }
  988. RptrAddrTrackEntry ::=
  989. SEQUENCE {
  990. rptrAddrTrackGroupIndex
  991. INTEGER,
  992. rptrAddrTrackPortIndex
  993. INTEGER,
  994. rptrAddrTrackLastSourceAddress -- DEPRECATED OBJECT
  995. MacAddress,
  996. rptrAddrTrackSourceAddrChanges
  997. Counter,
  998. rptrAddrTrackNewLastSrcAddress
  999. OCTET STRING
  1000. }
  1001. rptrAddrTrackGroupIndex OBJECT-TYPE
  1002. SYNTAX INTEGER (1..1024)
  1003. ACCESS read-only
  1004. STATUS mandatory
  1005. DESCRIPTION
  1006. "This object identifies the group containing the
  1007. port for which this entry contains information."
  1008. ::= { rptrAddrTrackEntry 1 }
  1009. rptrAddrTrackPortIndex OBJECT-TYPE
  1010. SYNTAX INTEGER (1..1024)
  1011. ACCESS read-only
  1012. STATUS mandatory
  1013. DESCRIPTION
  1014. "This object identifies the port within the group
  1015. for which this entry contains information."
  1016. REFERENCE
  1017. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2,
  1018. aPortID."
  1019. ::= { rptrAddrTrackEntry 2 }
  1020. rptrAddrTrackLastSourceAddress OBJECT-TYPE
  1021. SYNTAX MacAddress
  1022. ACCESS read-only
  1023. STATUS deprecated
  1024. DESCRIPTION
  1025. "This object is the SourceAddress of the last
  1026. readable frame (i.e., counted by
  1027. rptrMonitorPortReadableFrames) received by this
  1028. port.
  1029. This object has been deprecated because its value
  1030. is undefined when no frames have been observed on
  1031. this port. The replacement object is
  1032. rptrAddrTrackNewLastSrcAddress."
  1033. REFERENCE
  1034. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2,
  1035. aLastSourceAddress."
  1036. ::= { rptrAddrTrackEntry 3 }
  1037. rptrAddrTrackSourceAddrChanges OBJECT-TYPE
  1038. SYNTAX Counter
  1039. ACCESS read-only
  1040. STATUS mandatory
  1041. DESCRIPTION
  1042. "This counter is incremented by one for each time
  1043. that the rptrAddrTrackLastSourceAddress attribute
  1044. for this port has changed.
  1045. This may indicate whether a link is connected to a
  1046. single DTE or another multi-user segment.
  1047. The approximate minimum time for rollover of this
  1048. counter is 81 hours."
  1049. REFERENCE
  1050. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2,
  1051. aSourceAddressChanges."
  1052. ::= { rptrAddrTrackEntry 4 }
  1053. rptrAddrTrackNewLastSrcAddress OBJECT-TYPE
  1054. SYNTAX OCTET STRING (SIZE(0 | 6))
  1055. ACCESS read-only
  1056. STATUS mandatory
  1057. DESCRIPTION
  1058. "This object is the SourceAddress of the last
  1059. readable frame (i.e., counted by
  1060. rptrMonitorPortReadableFrames) received by this
  1061. port. If no frames have been received by this
  1062. port since the agent began monitoring the port
  1063. activity, the agent shall return a string of
  1064. length zero."
  1065. REFERENCE
  1066. "Reference IEEE 802.3 Rptr Mgt, 19.2.6.2,
  1067. aLastSourceAddress."
  1068. ::= { rptrAddrTrackEntry 5 }
  1069. -- Traps for use by Repeaters
  1070. -- Traps are defined using the conventions in RFC 1215 [6].
  1071. rptrHealth TRAP-TYPE
  1072. ENTERPRISE snmpDot3RptrMgt
  1073. VARIABLES { rptrOperStatus }
  1074. DESCRIPTION
  1075. "The rptrHealth trap conveys information related
  1076. to the operational status of the repeater. This
  1077. trap is sent either when the value of
  1078. rptrOperStatus changes, or upon completion of a
  1079. non-disruptive test.
  1080. The rptrHealth trap must contain the
  1081. rptrOperStatus object. The agent may optionally
  1082. include the rptrHealthText object in the varBind
  1083. list. See the rptrOperStatus and rptrHealthText
  1084. objects for descriptions of the information that
  1085. is sent.
  1086. The agent must throttle the generation of
  1087. consecutive rptrHealth traps so that there is at
  1088. least a five-second gap between traps of this
  1089. type. When traps are throttled, they are dropped,
  1090. not queued for sending at a future time. (Note
  1091. that 'generating' a trap means sending to all
  1092. configured recipients.)"
  1093. REFERENCE
  1094. "Reference IEEE 802.3 Rptr Mgt, 19.2.3.4,
  1095. hubHealth notification."
  1096. ::= 1
  1097. rptrGroupChange TRAP-TYPE
  1098. ENTERPRISE snmpDot3RptrMgt
  1099. VARIABLES { rptrGroupIndex }
  1100. DESCRIPTION
  1101. "This trap is sent when a change occurs in the
  1102. group structure of a repeater. This occurs only
  1103. when a group is logically or physically removed
  1104. from or added to a repeater. The varBind list
  1105. contains the identifier of the group that was
  1106. removed or added.
  1107. The agent must throttle the generation of
  1108. consecutive rptrGroupChange traps for the same
  1109. group so that there is at least a five-second gap
  1110. between traps of this type. When traps are
  1111. throttled, they are dropped, not queued for
  1112. sending at a future time. (Note that 'generating'
  1113. a trap means sending to all configured
  1114. recipients.)"
  1115. REFERENCE
  1116. "Reference IEEE 802.3 Rptr Mgt, 19.2.3.4,
  1117. groupMapChange notification."
  1118. ::= 2
  1119. rptrResetEvent TRAP-TYPE
  1120. ENTERPRISE snmpDot3RptrMgt
  1121. VARIABLES { rptrOperStatus }
  1122. DESCRIPTION
  1123. "The rptrResetEvent trap conveys information
  1124. related to the operational status of the repeater.
  1125. This trap is sent on completion of a repeater
  1126. reset action. A repeater reset action is defined
  1127. as an a transition to the START state of Fig 9-2
  1128. in section 9 [IEEE 802.3 Std], when triggered by a
  1129. management command (e.g., an SNMP Set on the
  1130. rptrReset object).
  1131. The agent must throttle the generation of
  1132. consecutive rptrResetEvent traps so that there is
  1133. at least a five-second gap between traps of this
  1134. type. When traps are throttled, they are dropped,
  1135. not queued for sending at a future time. (Note
  1136. that 'generating' a trap means sending to all
  1137. configured recipients.)
  1138. The rptrResetEvent trap is not sent when the agent
  1139. restarts and sends an SNMP coldStart or warmStart
  1140. trap. However, it is recommended that a repeater
  1141. agent send the rptrOperStatus object as an
  1142. optional object with its coldStart and warmStart
  1143. trap PDUs.
  1144. The rptrOperStatus object must be included in the
  1145. varbind list sent with this trap. The agent may
  1146. optionally include the rptrHealthText object as
  1147. well."
  1148. REFERENCE
  1149. "Reference IEEE 802.3 Rptr Mgt, 19.2.3.4, hubReset
  1150. notification."
  1151. ::= 3
  1152. END