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.

934 lines
39 KiB

  1. RFC1231-MIB DEFINITIONS ::= BEGIN
  2. -- IEEE 802.5 Token Ring MIB
  3. IMPORTS
  4. experimental
  5. FROM RFC1155-SMI
  6. OBJECT-TYPE
  7. FROM RFC-1212;
  8. -- This MIB Module uses the extended OBJECT-TYPE macro as
  9. -- defined in [9].
  10. dot5 OBJECT IDENTIFIER ::= { experimental 4 }
  11. -- All representations of MAC addresses in this MIB Module
  12. -- use, as a textual convention (i.e. this convention does
  13. -- not affect their encoding), the data type:
  14. MacAddress ::= OCTET STRING (SIZE (6)) -- a 6 octet
  15. -- address in the
  16. -- "canonical" order
  17. -- defined by IEEE 802.1a, i.e., as if it were transmitted
  18. -- least significant bit first, even though 802.5 (in
  19. -- contrast to other 802.x protocols) requires MAC addresses
  20. -- to be transmitted most significant bit first.
  21. --
  22. -- 16-bit addresses, if needed, are represented by setting
  23. -- their upper 4 octets to all 0's, i.e., AAFF would be
  24. -- represented as 00000000AAFF.
  25. -- The Interface Table
  26. -- This table contains state and parameter information which
  27. -- is specific to 802.5 interfaces. It is mandatory that
  28. -- systems having 802.5 interfaces implement this table in
  29. -- addition to the generic interfaces table [4,6] and its
  30. -- generic extensions [11].
  31. dot5Table OBJECT-TYPE
  32. SYNTAX SEQUENCE OF Dot5Entry
  33. ACCESS not-accessible
  34. STATUS mandatory
  35. DESCRIPTION
  36. "This table contains Token Ring interface
  37. parameters and state variables, one entry
  38. per 802.5 interface."
  39. ::= { dot5 1 }
  40. dot5Entry OBJECT-TYPE
  41. SYNTAX Dot5Entry
  42. ACCESS not-accessible
  43. STATUS mandatory
  44. DESCRIPTION
  45. "A list of Token Ring status and parameter
  46. values for an 802.5 interface."
  47. INDEX { dot5IfIndex }
  48. ::= { dot5Table 1 }
  49. Dot5Entry
  50. ::= SEQUENCE {
  51. dot5IfIndex
  52. INTEGER,
  53. dot5Commands
  54. INTEGER,
  55. dot5RingStatus
  56. INTEGER,
  57. dot5RingState
  58. INTEGER,
  59. dot5RingOpenStatus
  60. INTEGER,
  61. dot5RingSpeed
  62. INTEGER,
  63. dot5UpStream
  64. MacAddress,
  65. dot5ActMonParticipate
  66. INTEGER,
  67. dot5Functional
  68. MacAddress
  69. }
  70. dot5IfIndex OBJECT-TYPE
  71. SYNTAX INTEGER
  72. ACCESS read-only
  73. STATUS mandatory
  74. DESCRIPTION
  75. "The value of this object identifies the
  76. 802.5 interface for which this entry
  77. contains management information. The
  78. value of this object for a particular
  79. interface has the same value as the
  80. ifIndex object, defined in [4,6],
  81. for the same interface."
  82. ::= { dot5Entry 1 }
  83. dot5Commands OBJECT-TYPE
  84. SYNTAX INTEGER {
  85. no-op(1),
  86. open(2),
  87. reset(3),
  88. close(4)
  89. }
  90. ACCESS read-write
  91. STATUS mandatory
  92. DESCRIPTION
  93. "When this object is set to the value of
  94. open(2), the station should go into the
  95. open state. The progress and success of
  96. the open is given by the values of the
  97. objects dot5RingState and
  98. dot5RingOpenStatus.
  99. When this object is set to the value
  100. of reset(3), then the station should do
  101. a reset. On a reset, all MIB counters
  102. should retain their values, if possible.
  103. Other side affects are dependent on the
  104. hardware chip set.
  105. When this object is set to the value
  106. of close(4), the station should go into
  107. the stopped state by removing itself
  108. from the ring.
  109. Setting this object to a value of
  110. no-op(1) has no effect.
  111. When read, this object always has a
  112. value of no-op(1)."
  113. ::= { dot5Entry 2 }
  114. dot5RingStatus OBJECT-TYPE
  115. SYNTAX INTEGER
  116. ACCESS read-only
  117. STATUS mandatory
  118. DESCRIPTION
  119. "The current interface status which can
  120. be used to diagnose fluctuating problems
  121. that can occur on token rings, after a
  122. station has successfully been added to
  123. the ring.
  124. Before an open is completed, this
  125. object has the value for the 'no status'
  126. condition. The dot5RingState and
  127. dot5RingOpenStatus objects provide for
  128. debugging problems when the station
  129. can not even enter the ring.
  130. The object's value is a sum of
  131. values, one for each currently applicable
  132. condition. The following values are
  133. defined for various conditions:
  134. 0 = No Problems detected
  135. 32 = Ring Recovery
  136. 64 = Single Station
  137. 256 = Remove Received
  138. 512 = reserved
  139. 1024 = Auto-Removal Error
  140. 2048 = Lobe Wire Fault
  141. 4096 = Transmit Beacon
  142. 8192 = Soft Error
  143. 16384 = Hard Error
  144. 32768 = Signal Loss
  145. 131072 = no status, open not completed."
  146. ::= { dot5Entry 3 }
  147. dot5RingState OBJECT-TYPE
  148. SYNTAX INTEGER {
  149. opened(1),
  150. closed(2),
  151. opening(3),
  152. closing(4),
  153. openFailure(5),
  154. ringFailure(6)
  155. }
  156. ACCESS read-only
  157. STATUS mandatory
  158. DESCRIPTION
  159. "The current interface state with respect
  160. to entering or leaving the ring."
  161. ::= { dot5Entry 4 }
  162. dot5RingOpenStatus OBJECT-TYPE
  163. SYNTAX INTEGER {
  164. noOpen(1), -- no open attempted
  165. badParam(2),
  166. lobeFailed(3),
  167. signalLoss(4),
  168. insertionTimeout(5),
  169. ringFailed(6),
  170. beaconing(7),
  171. duplicateMAC(8),
  172. requestFailed(9),
  173. removeReceived(10),
  174. open(11) -- last open successful
  175. }
  176. ACCESS read-only
  177. STATUS mandatory
  178. DESCRIPTION
  179. "This object indicates the success, or the
  180. reason for failure, of the station's most
  181. recent attempt to enter the ring."
  182. ::= { dot5Entry 5 }
  183. dot5RingSpeed OBJECT-TYPE
  184. SYNTAX INTEGER {
  185. unknown(1),
  186. oneMegabit(2),
  187. fourMegabit(3),
  188. sixteenMegabit(4)
  189. }
  190. ACCESS read-write
  191. STATUS mandatory
  192. DESCRIPTION
  193. "The ring's bandwidth."
  194. ::= { dot5Entry 6 }
  195. dot5UpStream OBJECT-TYPE
  196. SYNTAX MacAddress
  197. ACCESS read-only
  198. STATUS mandatory
  199. DESCRIPTION
  200. "The MAC-address of the up stream neighbor
  201. station in the ring."
  202. ::= { dot5Entry 7 }
  203. dot5ActMonParticipate OBJECT-TYPE
  204. SYNTAX INTEGER {
  205. true(1),
  206. false(2)
  207. }
  208. ACCESS read-write
  209. STATUS mandatory
  210. DESCRIPTION
  211. "If this object has a value of true(1) then
  212. this interface will participate in the
  213. active monitor selection process. If the
  214. value is false(2) then it will not.
  215. Setting this object might not have an
  216. effect until the next time the interface
  217. is opened."
  218. ::= { dot5Entry 8 }
  219. dot5Functional OBJECT-TYPE
  220. SYNTAX MacAddress
  221. ACCESS read-write
  222. STATUS mandatory
  223. DESCRIPTION
  224. "The bit mask of all Token Ring functional
  225. addresses for which this interface will
  226. accept frames."
  227. ::= { dot5Entry 9 }
  228. -- The Statistics Table
  229. -- This table contains statistics and error counter which are
  230. -- specific to 802.5 interfaces. It is mandatory that systems
  231. -- having 802.5 interfaces implement this table.
  232. dot5StatsTable OBJECT-TYPE
  233. SYNTAX SEQUENCE OF Dot5StatsEntry
  234. ACCESS not-accessible
  235. STATUS mandatory
  236. DESCRIPTION
  237. "A table containing Token Ring statistics,
  238. one entry per 802.5 interface.
  239. All the statistics are defined using
  240. the syntax Counter as 32-bit wrap around
  241. counters. Thus, if an interface's
  242. hardware maintains these statistics in
  243. 16-bit counters, then the agent must read
  244. the hardware's counters frequently enough
  245. to prevent loss of significance, in order
  246. to maintain 32-bit counters in software."
  247. ::= { dot5 2 }
  248. dot5StatsEntry OBJECT-TYPE
  249. SYNTAX Dot5StatsEntry
  250. ACCESS not-accessible
  251. STATUS mandatory
  252. DESCRIPTION
  253. "An entry contains the 802.5 statistics
  254. for a particular interface."
  255. INDEX { dot5StatsIfIndex }
  256. ::= { dot5StatsTable 1 }
  257. Dot5StatsEntry
  258. ::= SEQUENCE {
  259. dot5StatsIfIndex
  260. INTEGER,
  261. dot5StatsLineErrors
  262. Counter,
  263. dot5StatsBurstErrors
  264. Counter,
  265. dot5StatsACErrors
  266. Counter,
  267. dot5StatsAbortTransErrors
  268. Counter,
  269. dot5StatsInternalErrors
  270. Counter,
  271. dot5StatsLostFrameErrors
  272. Counter,
  273. dot5StatsReceiveCongestions
  274. Counter,
  275. dot5StatsFrameCopiedErrors
  276. Counter,
  277. dot5StatsTokenErrors
  278. Counter,
  279. dot5StatsSoftErrors
  280. Counter,
  281. dot5StatsHardErrors
  282. Counter,
  283. dot5StatsSignalLoss
  284. Counter,
  285. dot5StatsTransmitBeacons
  286. Counter,
  287. dot5StatsRecoverys
  288. Counter,
  289. dot5StatsLobeWires
  290. Counter,
  291. dot5StatsRemoves
  292. Counter,
  293. dot5StatsSingles
  294. Counter,
  295. dot5StatsFreqErrors
  296. Counter
  297. }
  298. dot5StatsIfIndex OBJECT-TYPE
  299. SYNTAX INTEGER
  300. ACCESS read-only
  301. STATUS mandatory
  302. DESCRIPTION
  303. "The value of this object identifies the
  304. 802.5 interface for which this entry
  305. contains management information. The
  306. value of this object for a particular
  307. interface has the same value as the
  308. ifIndex object, defined in [4,6], for
  309. the same interface."
  310. ::= { dot5StatsEntry 1 }
  311. dot5StatsLineErrors OBJECT-TYPE
  312. SYNTAX Counter
  313. ACCESS read-only
  314. STATUS mandatory
  315. DESCRIPTION
  316. "This counter is incremented when a frame
  317. or token is copied or repeated by a
  318. station, the E bit is zero in the frame
  319. or token and one of the following
  320. conditions exists: 1) there is a
  321. non-data bit (J or K bit) between the SD
  322. and the ED of the frame or token, or
  323. 2) there is an FCS error in the frame."
  324. ::= { dot5StatsEntry 2 }
  325. dot5StatsBurstErrors OBJECT-TYPE
  326. SYNTAX Counter
  327. ACCESS read-only
  328. STATUS mandatory
  329. DESCRIPTION
  330. "This counter is incremented when a station
  331. detects the absence of transitions for five
  332. half-bit timers (burst-five error)."
  333. ::= { dot5StatsEntry 3 }
  334. dot5StatsACErrors OBJECT-TYPE
  335. SYNTAX Counter
  336. ACCESS read-only
  337. STATUS mandatory
  338. DESCRIPTION
  339. "This counter is incremented when a station
  340. receives an AMP or SMP frame in which A is
  341. equal to C is equal to 0, and then receives
  342. another SMP frame with A is equal to C is
  343. equal to 0 without first receiving an AMP
  344. frame. It denotes a station that cannot set
  345. the AC bits properly."
  346. ::= { dot5StatsEntry 4 }
  347. dot5StatsAbortTransErrors OBJECT-TYPE
  348. SYNTAX Counter
  349. ACCESS read-only
  350. STATUS mandatory
  351. DESCRIPTION
  352. "This counter is incremented when a station
  353. transmits an abort delimiter while
  354. transmitting."
  355. ::= { dot5StatsEntry 5 }
  356. dot5StatsInternalErrors OBJECT-TYPE
  357. SYNTAX Counter
  358. ACCESS read-only
  359. STATUS mandatory
  360. DESCRIPTION
  361. "This counter is incremented when a station
  362. recognizes an internal error."
  363. ::= { dot5StatsEntry 6 }
  364. dot5StatsLostFrameErrors OBJECT-TYPE
  365. SYNTAX Counter
  366. ACCESS read-only
  367. STATUS mandatory
  368. DESCRIPTION
  369. "This counter is incremented when a station
  370. is transmitting and its TRR timer expires.
  371. This condition denotes a condition where a
  372. transmitting station in strip mode does not
  373. receive the trailer of the frame before the
  374. TRR timer goes off."
  375. ::= { dot5StatsEntry 7 }
  376. dot5StatsReceiveCongestions OBJECT-TYPE
  377. SYNTAX Counter
  378. ACCESS read-only
  379. STATUS mandatory
  380. DESCRIPTION
  381. "This counter is incremented when a station
  382. recognizes a frame addressed to its
  383. specific address, but has no available
  384. buffer space indicating that the station
  385. is congested."
  386. ::= { dot5StatsEntry 8 }
  387. dot5StatsFrameCopiedErrors OBJECT-TYPE
  388. SYNTAX Counter
  389. ACCESS read-only
  390. STATUS mandatory
  391. DESCRIPTION
  392. "This counter is incremented when a station
  393. recognizes a frame addressed to its
  394. specific address and detects that the FS
  395. field A bits are set to 1 indicating a
  396. possible line hit or duplicate address."
  397. ::= { dot5StatsEntry 9 }
  398. dot5StatsTokenErrors OBJECT-TYPE
  399. SYNTAX Counter
  400. ACCESS read-only
  401. STATUS mandatory
  402. DESCRIPTION
  403. "This counter is incremented when a station
  404. acting as the active monitor recognizes an
  405. error condition that needs a token
  406. transmitted."
  407. ::= { dot5StatsEntry 10 }
  408. dot5StatsSoftErrors OBJECT-TYPE
  409. SYNTAX Counter
  410. ACCESS read-only
  411. STATUS mandatory
  412. DESCRIPTION
  413. "The number of Soft Errors the interface
  414. has detected. It directly corresponds to
  415. the number of Report Error MAC frames
  416. that this interface has transmitted.
  417. Soft Errors are those which are
  418. recoverable by the MAC layer protocols."
  419. ::= { dot5StatsEntry 11 }
  420. dot5StatsHardErrors OBJECT-TYPE
  421. SYNTAX Counter
  422. ACCESS read-only
  423. STATUS mandatory
  424. DESCRIPTION
  425. "The number of times this interface has
  426. detected an immediately recoverable
  427. fatal error. It denotes the number of
  428. times this interface is either
  429. transmitting or receiving beacon MAC
  430. frames."
  431. ::= { dot5StatsEntry 12 }
  432. dot5StatsSignalLoss OBJECT-TYPE
  433. SYNTAX Counter
  434. ACCESS read-only
  435. STATUS mandatory
  436. DESCRIPTION
  437. "The number of times this interface has
  438. detected the loss of signal condition from
  439. the ring."
  440. ::= { dot5StatsEntry 13 }
  441. dot5StatsTransmitBeacons OBJECT-TYPE
  442. SYNTAX Counter
  443. ACCESS read-only
  444. STATUS mandatory
  445. DESCRIPTION
  446. "The number of times this interface has
  447. transmitted a beacon frame."
  448. ::= { dot5StatsEntry 14 }
  449. dot5StatsRecoverys OBJECT-TYPE
  450. SYNTAX Counter
  451. ACCESS read-only
  452. STATUS mandatory
  453. DESCRIPTION
  454. "The number of Claim Token MAC frames
  455. received or transmitted after the interface
  456. has received a Ring Purge MAC frame. This
  457. counter signifies the number of times the
  458. ring has been purged and is being recovered
  459. back into a normal operating state."
  460. ::= { dot5StatsEntry 15 }
  461. dot5StatsLobeWires OBJECT-TYPE
  462. SYNTAX Counter
  463. ACCESS read-only
  464. STATUS mandatory
  465. DESCRIPTION
  466. "The number of times the interface has
  467. detected an open or short circuit in the
  468. lobe data path. The adapter will be closed
  469. and dot5RingState will signify this
  470. condition."
  471. ::= { dot5StatsEntry 16 }
  472. dot5StatsRemoves OBJECT-TYPE
  473. SYNTAX Counter
  474. ACCESS read-only
  475. STATUS mandatory
  476. DESCRIPTION
  477. "The number of times the interface has
  478. received a Remove Ring Station MAC frame
  479. request. When this frame is received
  480. the interface will enter the close state
  481. and dot5RingState will signify this
  482. condition."
  483. ::= { dot5StatsEntry 17 }
  484. dot5StatsSingles OBJECT-TYPE
  485. SYNTAX Counter
  486. ACCESS read-only
  487. STATUS mandatory
  488. DESCRIPTION
  489. "The number of times the interface has
  490. sensed that it is the only station on the
  491. ring. This will happen if the interface
  492. is the first one up on a ring, or if
  493. there is a hardware problem."
  494. ::= { dot5StatsEntry 18 }
  495. dot5StatsFreqErrors OBJECT-TYPE
  496. SYNTAX Counter
  497. ACCESS read-only
  498. STATUS optional
  499. DESCRIPTION
  500. "The number of times the interface has
  501. detected that the frequency of the
  502. incoming signal differs from the expected
  503. frequency by more than that specified by
  504. the IEEE 802.5 standard, see chapter 7
  505. in [10]."
  506. ::= { dot5StatsEntry 19 }
  507. -- The Timer Table
  508. -- This group contains the values of the timers defined in
  509. -- [10] for 802.5 interfaces. It is optional that systems
  510. -- having 802.5 interfaces implement this group.
  511. dot5TimerTable OBJECT-TYPE
  512. SYNTAX SEQUENCE OF Dot5TimerEntry
  513. ACCESS not-accessible
  514. STATUS mandatory
  515. DESCRIPTION
  516. "This table contains Token Ring interface
  517. timer values, one entry per 802.5
  518. interface."
  519. ::= { dot5 5 }
  520. dot5TimerEntry OBJECT-TYPE
  521. SYNTAX Dot5TimerEntry
  522. ACCESS not-accessible
  523. STATUS mandatory
  524. DESCRIPTION
  525. "A list of Token Ring timer values for an
  526. 802.5 interface."
  527. INDEX { dot5TimerIfIndex }
  528. ::= { dot5TimerTable 1 }
  529. Dot5TimerEntry
  530. ::= SEQUENCE {
  531. dot5TimerIfIndex
  532. INTEGER,
  533. dot5TimerReturnRepeat
  534. INTEGER,
  535. dot5TimerHolding
  536. INTEGER,
  537. dot5TimerQueuePDU
  538. INTEGER,
  539. dot5TimerValidTransmit
  540. INTEGER,
  541. dot5TimerNoToken
  542. INTEGER,
  543. dot5TimerActiveMon
  544. INTEGER,
  545. dot5TimerStandbyMon
  546. INTEGER,
  547. dot5TimerErrorReport
  548. INTEGER,
  549. dot5TimerBeaconTransmit
  550. INTEGER,
  551. dot5TimerBeaconReceive
  552. INTEGER
  553. }
  554. dot5TimerIfIndex OBJECT-TYPE
  555. SYNTAX INTEGER
  556. ACCESS read-only
  557. STATUS mandatory
  558. DESCRIPTION
  559. "The value of this object identifies the
  560. 802.5 interface for which this entry
  561. contains timer values. The value of
  562. this object for a particular interface
  563. has the same value as the ifIndex
  564. object, defined in [4,6], for the same
  565. interface."
  566. ::= { dot5TimerEntry 1 }
  567. dot5TimerReturnRepeat OBJECT-TYPE
  568. SYNTAX INTEGER
  569. ACCESS read-only
  570. STATUS mandatory
  571. DESCRIPTION
  572. "The time-out value used to ensure the
  573. interface will return to Repeat State, in
  574. units of 100 micro-seconds. The value
  575. should be greater than the maximum ring
  576. latency.
  577. Implementors are encouraged to provide
  578. read-write access to this object if that is
  579. possible/useful in their system, but giving
  580. due consideration to the dangers of
  581. write-able timers."
  582. ::= { dot5TimerEntry 2 }
  583. dot5TimerHolding OBJECT-TYPE
  584. SYNTAX INTEGER
  585. ACCESS read-only
  586. STATUS mandatory
  587. DESCRIPTION
  588. "Maximum period of time a station is
  589. permitted to transmit frames after capturing
  590. a token, in units of 100 micro-seconds.
  591. Implementors are encouraged to provide
  592. read-write access to this object if that is
  593. possible/useful in their system, but giving
  594. due consideration to the dangers of
  595. write-able timers."
  596. ::= { dot5TimerEntry 3 }
  597. dot5TimerQueuePDU OBJECT-TYPE
  598. SYNTAX INTEGER
  599. ACCESS read-only
  600. STATUS mandatory
  601. DESCRIPTION
  602. "The time-out value for enqueuing of an SMP
  603. PDU after reception of an AMP or SMP
  604. frame in which the A and C bits were
  605. equal to 0, in units of 100
  606. micro-seconds.
  607. Implementors are encouraged to provide
  608. read-write access to this object if that is
  609. possible/useful in their system, but giving
  610. due consideration to the dangers of
  611. write-able timers."
  612. ::= { dot5TimerEntry 4 }
  613. dot5TimerValidTransmit OBJECT-TYPE
  614. SYNTAX INTEGER
  615. ACCESS read-only
  616. STATUS mandatory
  617. DESCRIPTION
  618. "The time-out value used by the active
  619. monitor to detect the absence of valid
  620. transmissions, in units of 100
  621. micro-seconds.
  622. Implementors are encouraged to provide
  623. read-write access to this object if that is
  624. possible/useful in their system, but giving
  625. due consideration to the dangers of
  626. write-able timers."
  627. ::= { dot5TimerEntry 5 }
  628. dot5TimerNoToken OBJECT-TYPE
  629. SYNTAX INTEGER
  630. ACCESS read-only
  631. STATUS mandatory
  632. DESCRIPTION
  633. "The time-out value used to recover from
  634. various-related error situations [9].
  635. If N is the maximum number of stations on
  636. the ring, the value of this timer is
  637. normally:
  638. dot5TimerReturnRepeat + N*dot5TimerHolding.
  639. Implementors are encouraged to provide
  640. read-write access to this object if that is
  641. possible/useful in their system, but giving
  642. due consideration to the dangers of
  643. write-able timers."
  644. ::= { dot5TimerEntry 6 }
  645. dot5TimerActiveMon OBJECT-TYPE
  646. SYNTAX INTEGER
  647. ACCESS read-only
  648. STATUS mandatory
  649. DESCRIPTION
  650. "The time-out value used by the active
  651. monitor to stimulate the enqueuing of an
  652. AMP PDU for transmission, in units of
  653. 100 micro-seconds.
  654. Implementors are encouraged to provide
  655. read-write access to this object if that is
  656. possible/useful in their system, but giving
  657. due consideration to the dangers of
  658. write-able timers."
  659. ::= { dot5TimerEntry 7 }
  660. dot5TimerStandbyMon OBJECT-TYPE
  661. SYNTAX INTEGER
  662. ACCESS read-only
  663. STATUS mandatory
  664. DESCRIPTION
  665. "The time-out value used by the stand-by
  666. monitors to ensure that there is an active
  667. monitor on the ring and to detect a
  668. continuous stream of tokens, in units of
  669. 100 micro-seconds.
  670. Implementors are encouraged to provide
  671. read-write access to this object if that is
  672. possible/useful in their system, but giving
  673. due consideration to the dangers of
  674. write-able timers."
  675. ::= { dot5TimerEntry 8 }
  676. dot5TimerErrorReport OBJECT-TYPE
  677. SYNTAX INTEGER
  678. ACCESS read-only
  679. STATUS mandatory
  680. DESCRIPTION
  681. "The time-out value which determines how
  682. often a station shall send a Report Error
  683. MAC frame to report its error counters,
  684. in units of 100 micro-seconds.
  685. Implementors are encouraged to provide
  686. read-write access to this object if that is
  687. possible/useful in their system, but giving
  688. due consideration to the dangers of
  689. write-able timers."
  690. ::= { dot5TimerEntry 9 }
  691. dot5TimerBeaconTransmit OBJECT-TYPE
  692. SYNTAX INTEGER
  693. ACCESS read-only
  694. STATUS mandatory
  695. DESCRIPTION
  696. "The time-out value which determines how
  697. long a station shall remain in the state
  698. of transmitting Beacon frames before
  699. entering the Bypass state, in units of
  700. 100 micro-seconds.
  701. Implementors are encouraged to provide
  702. read-write access to this object if that is
  703. possible/useful in their system, but giving
  704. due consideration to the dangers of
  705. write-able timers."
  706. ::= { dot5TimerEntry 10 }
  707. dot5TimerBeaconReceive OBJECT-TYPE
  708. SYNTAX INTEGER
  709. ACCESS read-only
  710. STATUS mandatory
  711. DESCRIPTION
  712. "The time-out value which determines how
  713. long a station shall receive Beacon
  714. frames from its downstream neighbor
  715. before entering the Bypass state, in
  716. units of 100 micro-seconds.
  717. Implementors are encouraged to provide
  718. read-write access to this object if that is
  719. possible/useful in their system, but giving
  720. due consideration to the dangers of
  721. write-able timers."
  722. ::= { dot5TimerEntry 11 }
  723. -- 802.5 Interface Tests
  724. dot5Tests OBJECT IDENTIFIER ::= { dot5 3 }
  725. -- The extensions to the interfaces table proposed in [11]
  726. -- define a table object, ifExtnsTestTable, through which a
  727. -- network manager can instruct an agent to test an interface
  728. -- for various faults. A test to be performed is identified
  729. -- (as the value of ifExtnsTestType) via an OBJECT IDENTIFIER.
  730. --
  731. -- The Full-Duplex Loop Back Test is a common test, defined
  732. -- in [11] as:
  733. --
  734. -- testFullDuplexLoopBack
  735. --
  736. -- Invoking this test on a 802.5 interface causes the
  737. -- interface to check the path from memory through the
  738. -- chip set's internal logic and back to memory, thus
  739. -- checking the proper functioning of the systems's
  740. -- interface to the chip set.
  741. -- The Insert Function test is defined by:
  742. testInsertFunc OBJECT IDENTIFIER ::= { dot5Tests 1 }
  743. -- Invoking this test causes the station to test the insert
  744. -- ring logic of the hardware if the station's lobe media
  745. -- cable is connected to a wiring concentrator. Note that
  746. -- this command inserts the station into the network, and
  747. -- thus, could cause problems if the station is connected
  748. -- to a operational network.
  749. -- 802.5 Hardware Chip Sets
  750. dot5ChipSets OBJECT IDENTIFIER ::= { dot5 4 }
  751. -- The extensions to the interfaces table proposed in [11]
  752. -- define an object, ifExtnsChipSet, with the syntax of
  753. -- OBJECT IDENTIFIER, to identify the hardware chip set in
  754. -- use by an interface. That definition specifies just
  755. -- one applicable object identifier:
  756. --
  757. -- unknownChipSet
  758. --
  759. -- for use as the value of ifExtnsChipSet when the specific
  760. -- chip set is unknown.
  761. --
  762. -- This MIB defines the following for use as values of
  763. -- ifExtnsChipSet:
  764. -- IBM 16/4 Mb/s
  765. chipSetIBM16 OBJECT IDENTIFIER ::= { dot5ChipSets 1 }
  766. -- TI 4Mb/s
  767. chipSetTItms380 OBJECT IDENTIFIER ::= { dot5ChipSets 2 }
  768. -- TI 16/4 Mb/s
  769. chipSetTItms380c16 OBJECT IDENTIFIER ::= { dot5ChipSets 3 }
  770. END