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.

6261 lines
211 KiB

  1. --- /dev/null
  2. +++ b/mibs/BGP4-MIB.txt
  3. @@ -0,0 +1,929 @@
  4. + BGP4-MIB DEFINITIONS ::= BEGIN
  5. +
  6. + IMPORTS
  7. + MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
  8. + IpAddress, Integer32, Counter32, Gauge32, mib-2
  9. + FROM SNMPv2-SMI
  10. + MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
  11. + FROM SNMPv2-CONF;
  12. +
  13. + bgp MODULE-IDENTITY
  14. + LAST-UPDATED "9902100000Z"
  15. + ORGANIZATION "IETF IDR Working Group"
  16. + CONTACT-INFO "E-mail: idr@merit.net
  17. +
  18. + Susan Hares (Editor)
  19. + Merit Network
  20. + 4251 Plymouth Road
  21. + Suite C
  22. + Ann Arbor, MI 48105-2785
  23. + Tel: +1 734 936 2095
  24. + Fax: +1 734 647 3185
  25. + E-mail: skh@merit.edu
  26. +
  27. + Jeff Johnson (Editor)
  28. + RedBack Networks, Inc.
  29. + 1389 Moffett Park Drive
  30. + Sunnyvale, CA 94089-1134
  31. + Tel: +1 408 548 3516
  32. + Fax: +1 408 548 3599
  33. + E-mail: jeff@redback.com"
  34. + DESCRIPTION
  35. + "The MIB module for BGP-4."
  36. + REVISION "9902100000Z"
  37. + DESCRIPTION
  38. + "Corrected duplicate OBJECT IDENTIFIER
  39. + assignment in the conformance information."
  40. + REVISION "9601080000Z"
  41. + DESCRIPTION
  42. + "1) Fixed the definitions of the traps to
  43. + make them equivalent to their initial
  44. + definition in RFC 1269.
  45. + 2) Added compliance and conformance info."
  46. + ::= { mib-2 15 }
  47. +
  48. + bgpVersion OBJECT-TYPE
  49. + SYNTAX OCTET STRING (SIZE (1..255))
  50. + MAX-ACCESS read-only
  51. + STATUS current
  52. + DESCRIPTION
  53. + "Vector of supported BGP protocol version
  54. + numbers. Each peer negotiates the version
  55. + from this vector. Versions are identified
  56. + via the string of bits contained within this
  57. + object. The first octet contains bits 0 to
  58. + 7, the second octet contains bits 8 to 15,
  59. + and so on, with the most significant bit
  60. + referring to the lowest bit number in the
  61. + octet (e.g., the MSB of the first octet
  62. + refers to bit 0). If a bit, i, is present
  63. + and set, then the version (i+1) of the BGP
  64. + is supported."
  65. + ::= { bgp 1 }
  66. +
  67. + bgpLocalAs OBJECT-TYPE
  68. + SYNTAX INTEGER (0..65535)
  69. + MAX-ACCESS read-only
  70. + STATUS current
  71. + DESCRIPTION
  72. + "The local autonomous system number."
  73. + ::= { bgp 2 }
  74. +
  75. +
  76. +
  77. + -- BGP Peer table. This table contains, one entry per BGP
  78. + -- peer, information about the BGP peer.
  79. +
  80. + bgpPeerTable OBJECT-TYPE
  81. + SYNTAX SEQUENCE OF BgpPeerEntry
  82. + MAX-ACCESS not-accessible
  83. + STATUS current
  84. + DESCRIPTION
  85. + "BGP peer table. This table contains,
  86. + one entry per BGP peer, information about the
  87. + connections with BGP peers."
  88. + ::= { bgp 3 }
  89. +
  90. + bgpPeerEntry OBJECT-TYPE
  91. + SYNTAX BgpPeerEntry
  92. + MAX-ACCESS not-accessible
  93. + STATUS current
  94. + DESCRIPTION
  95. + "Entry containing information about the
  96. + connection with a BGP peer."
  97. + INDEX { bgpPeerRemoteAddr }
  98. + ::= { bgpPeerTable 1 }
  99. +
  100. + BgpPeerEntry ::= SEQUENCE {
  101. + bgpPeerIdentifier
  102. + IpAddress,
  103. + bgpPeerState
  104. + INTEGER,
  105. + bgpPeerAdminStatus
  106. + INTEGER,
  107. + bgpPeerNegotiatedVersion
  108. + Integer32,
  109. + bgpPeerLocalAddr
  110. + IpAddress,
  111. + bgpPeerLocalPort
  112. + INTEGER,
  113. + bgpPeerRemoteAddr
  114. + IpAddress,
  115. + bgpPeerRemotePort
  116. + INTEGER,
  117. + bgpPeerRemoteAs
  118. + INTEGER,
  119. + bgpPeerInUpdates
  120. + Counter32,
  121. + bgpPeerOutUpdates
  122. + Counter32,
  123. + bgpPeerInTotalMessages
  124. + Counter32,
  125. + bgpPeerOutTotalMessages
  126. + Counter32,
  127. + bgpPeerLastError
  128. + OCTET STRING,
  129. + bgpPeerFsmEstablishedTransitions
  130. + Counter32,
  131. + bgpPeerFsmEstablishedTime
  132. + Gauge32,
  133. + bgpPeerConnectRetryInterval
  134. + INTEGER,
  135. + bgpPeerHoldTime
  136. + INTEGER,
  137. + bgpPeerKeepAlive
  138. + INTEGER,
  139. + bgpPeerHoldTimeConfigured
  140. + INTEGER,
  141. + bgpPeerKeepAliveConfigured
  142. + INTEGER,
  143. + bgpPeerMinASOriginationInterval
  144. + INTEGER,
  145. + bgpPeerMinRouteAdvertisementInterval
  146. + INTEGER,
  147. + bgpPeerInUpdateElapsedTime
  148. + Gauge32
  149. + }
  150. +
  151. + bgpPeerIdentifier OBJECT-TYPE
  152. + SYNTAX IpAddress
  153. + MAX-ACCESS read-only
  154. + STATUS current
  155. + DESCRIPTION
  156. + "The BGP Identifier of this entry's BGP peer."
  157. + ::= { bgpPeerEntry 1 }
  158. +
  159. + bgpPeerState OBJECT-TYPE
  160. + SYNTAX INTEGER {
  161. + idle(1),
  162. + connect(2),
  163. + active(3),
  164. + opensent(4),
  165. + openconfirm(5),
  166. + established(6)
  167. + }
  168. + MAX-ACCESS read-only
  169. + STATUS current
  170. + DESCRIPTION
  171. + "The BGP peer connection state."
  172. + ::= { bgpPeerEntry 2 }
  173. +
  174. + bgpPeerAdminStatus OBJECT-TYPE
  175. + SYNTAX INTEGER {
  176. + stop(1),
  177. + start(2)
  178. + }
  179. + MAX-ACCESS read-write
  180. + STATUS current
  181. + DESCRIPTION
  182. + "The desired state of the BGP connection. A
  183. + transition from 'stop' to 'start' will cause
  184. + the BGP Start Event to be generated. A
  185. + transition from 'start' to 'stop' will cause
  186. + the BGP Stop Event to be generated. This
  187. + parameter can be used to restart BGP peer
  188. + connections. Care should be used in providing
  189. + write access to this object without adequate
  190. + authentication."
  191. + ::= { bgpPeerEntry 3 }
  192. +
  193. + bgpPeerNegotiatedVersion OBJECT-TYPE
  194. + SYNTAX Integer32
  195. + MAX-ACCESS read-only
  196. + STATUS current
  197. + DESCRIPTION
  198. + "The negotiated version of BGP running between
  199. + the two peers."
  200. + ::= { bgpPeerEntry 4 }
  201. +
  202. + bgpPeerLocalAddr OBJECT-TYPE
  203. + SYNTAX IpAddress
  204. + MAX-ACCESS read-only
  205. + STATUS current
  206. + DESCRIPTION
  207. + "The local IP address of this entry's BGP
  208. + connection."
  209. + ::= { bgpPeerEntry 5 }
  210. +
  211. + bgpPeerLocalPort OBJECT-TYPE
  212. + SYNTAX INTEGER (0..65535)
  213. + MAX-ACCESS read-only
  214. + STATUS current
  215. + DESCRIPTION
  216. + "The local port for the TCP connection between
  217. + the BGP peers."
  218. + ::= { bgpPeerEntry 6 }
  219. +
  220. + bgpPeerRemoteAddr OBJECT-TYPE
  221. + SYNTAX IpAddress
  222. + MAX-ACCESS read-only
  223. + STATUS current
  224. + DESCRIPTION
  225. + "The remote IP address of this entry's BGP
  226. + peer."
  227. + ::= { bgpPeerEntry 7 }
  228. +
  229. + bgpPeerRemotePort OBJECT-TYPE
  230. + SYNTAX INTEGER (0..65535)
  231. + MAX-ACCESS read-only
  232. + STATUS current
  233. + DESCRIPTION
  234. + "The remote port for the TCP connection between
  235. + the BGP peers. Note that the objects
  236. + bgpPeerLocalAddr, bgpPeerLocalPort,
  237. + bgpPeerRemoteAddr and bgpPeerRemotePort
  238. + provide the appropriate reference to the
  239. + standard MIB TCP connection table."
  240. + ::= { bgpPeerEntry 8 }
  241. +
  242. + bgpPeerRemoteAs OBJECT-TYPE
  243. + SYNTAX INTEGER (0..65535)
  244. + MAX-ACCESS read-only
  245. + STATUS current
  246. + DESCRIPTION
  247. + "The remote autonomous system number."
  248. + ::= { bgpPeerEntry 9 }
  249. +
  250. + bgpPeerInUpdates OBJECT-TYPE
  251. + SYNTAX Counter32
  252. + MAX-ACCESS read-only
  253. + STATUS current
  254. + DESCRIPTION
  255. + "The number of BGP UPDATE messages received on
  256. + this connection. This object should be
  257. + initialized to zero (0) when the connection is
  258. + established."
  259. + ::= { bgpPeerEntry 10 }
  260. +
  261. + bgpPeerOutUpdates OBJECT-TYPE
  262. + SYNTAX Counter32
  263. + MAX-ACCESS read-only
  264. + STATUS current
  265. + DESCRIPTION
  266. + "The number of BGP UPDATE messages transmitted
  267. + on this connection. This object should be
  268. + initialized to zero (0) when the connection is
  269. + established."
  270. + ::= { bgpPeerEntry 11 }
  271. +
  272. + bgpPeerInTotalMessages OBJECT-TYPE
  273. + SYNTAX Counter32
  274. + MAX-ACCESS read-only
  275. + STATUS current
  276. + DESCRIPTION
  277. + "The total number of messages received from the
  278. + remote peer on this connection. This object
  279. + should be initialized to zero when the
  280. + connection is established."
  281. + ::= { bgpPeerEntry 12 }
  282. +
  283. + bgpPeerOutTotalMessages OBJECT-TYPE
  284. + SYNTAX Counter32
  285. + MAX-ACCESS read-only
  286. + STATUS current
  287. + DESCRIPTION
  288. + "The total number of messages transmitted to
  289. + the remote peer on this connection. This object
  290. + should be initialized to zero when the
  291. + connection is established."
  292. + ::= { bgpPeerEntry 13 }
  293. +
  294. + bgpPeerLastError OBJECT-TYPE
  295. + SYNTAX OCTET STRING (SIZE (2))
  296. + MAX-ACCESS read-only
  297. + STATUS current
  298. + DESCRIPTION
  299. + "The last error code and subcode seen by this
  300. + peer on this connection. If no error has
  301. + occurred, this field is zero. Otherwise, the
  302. + first byte of this two byte OCTET STRING
  303. + contains the error code, and the second byte
  304. + contains the subcode."
  305. + ::= { bgpPeerEntry 14 }
  306. +
  307. + bgpPeerFsmEstablishedTransitions OBJECT-TYPE
  308. + SYNTAX Counter32
  309. + MAX-ACCESS read-only
  310. + STATUS current
  311. + DESCRIPTION
  312. + "The total number of times the BGP FSM
  313. + transitioned into the established state."
  314. + ::= { bgpPeerEntry 15 }
  315. +
  316. + bgpPeerFsmEstablishedTime OBJECT-TYPE
  317. + SYNTAX Gauge32
  318. + MAX-ACCESS read-only
  319. + STATUS current
  320. + DESCRIPTION
  321. + "This timer indicates how long (in seconds) this
  322. + peer has been in the Established state or how long
  323. + since this peer was last in the Established state.
  324. + It is set to zero when a new peer is configured or
  325. + the router is booted."
  326. + ::= { bgpPeerEntry 16 }
  327. +
  328. + bgpPeerConnectRetryInterval OBJECT-TYPE
  329. + SYNTAX INTEGER (1..65535)
  330. + MAX-ACCESS read-write
  331. + STATUS current
  332. + DESCRIPTION
  333. + "Time interval in seconds for the ConnectRetry
  334. + timer. The suggested value for this timer is
  335. + 120 seconds."
  336. + ::= { bgpPeerEntry 17 }
  337. +
  338. + bgpPeerHoldTime OBJECT-TYPE
  339. + SYNTAX INTEGER ( 0 | 3..65535 )
  340. + MAX-ACCESS read-only
  341. + STATUS current
  342. + DESCRIPTION
  343. + "Time interval in seconds for the Hold Timer
  344. + established with the peer. The value of this
  345. + object is calculated by this BGP speaker by
  346. + using the smaller of the value in
  347. + bgpPeerHoldTimeConfigured and the Hold Time
  348. + received in the OPEN message. This value
  349. + must be at lease three seconds if it is not
  350. + zero (0) in which case the Hold Timer has
  351. + not been established with the peer, or, the
  352. + value of bgpPeerHoldTimeConfigured is zero (0)."
  353. + ::= { bgpPeerEntry 18 }
  354. +
  355. + bgpPeerKeepAlive OBJECT-TYPE
  356. + SYNTAX INTEGER ( 0 | 1..21845 )
  357. + MAX-ACCESS read-only
  358. + STATUS current
  359. + DESCRIPTION
  360. + "Time interval in seconds for the KeepAlive
  361. + timer established with the peer. The value of
  362. + this object is calculated by this BGP speaker
  363. + such that, when compared with bgpPeerHoldTime,
  364. + it has the same proportion as what
  365. + bgpPeerKeepAliveConfigured has when compared
  366. + with bgpPeerHoldTimeConfigured. If the value
  367. + of this object is zero (0), it indicates that
  368. + the KeepAlive timer has not been established
  369. + with the peer, or, the value of
  370. + bgpPeerKeepAliveConfigured is zero (0)."
  371. + ::= { bgpPeerEntry 19 }
  372. +
  373. + bgpPeerHoldTimeConfigured OBJECT-TYPE
  374. + SYNTAX INTEGER ( 0 | 3..65535 )
  375. + MAX-ACCESS read-write
  376. + STATUS current
  377. + DESCRIPTION
  378. + "Time interval in seconds for the Hold Time
  379. + configured for this BGP speaker with this peer.
  380. + This value is placed in an OPEN message sent to
  381. + this peer by this BGP speaker, and is compared
  382. + with the Hold Time field in an OPEN message
  383. + received from the peer when determining the Hold
  384. + Time (bgpPeerHoldTime) with the peer. This value
  385. + must not be less than three seconds if it is not
  386. + zero (0) in which case the Hold Time is NOT to be
  387. + established with the peer. The suggested value for
  388. + this timer is 90 seconds."
  389. + ::= { bgpPeerEntry 20 }
  390. +
  391. + bgpPeerKeepAliveConfigured OBJECT-TYPE
  392. + SYNTAX INTEGER ( 0 | 1..21845 )
  393. + MAX-ACCESS read-write
  394. + STATUS current
  395. + DESCRIPTION
  396. + "Time interval in seconds for the KeepAlive timer
  397. + configured for this BGP speaker with this peer.
  398. + The value of this object will only determine the
  399. + KEEPALIVE messages' frequency relative to the value
  400. + specified in bgpPeerHoldTimeConfigured; the actual
  401. + time interval for the KEEPALIVE messages is
  402. + indicated by bgpPeerKeepAlive. A reasonable
  403. + maximum value for this timer would be configured to
  404. + be one third of that of bgpPeerHoldTimeConfigured.
  405. + If the value of this object is zero (0), no
  406. + periodical KEEPALIVE messages are sent to the peer
  407. + after the BGP connection has been established. The
  408. + suggested value for this timer is 30 seconds."
  409. + ::= { bgpPeerEntry 21 }
  410. +
  411. + bgpPeerMinASOriginationInterval OBJECT-TYPE
  412. + SYNTAX INTEGER (1..65535)
  413. + MAX-ACCESS read-write
  414. + STATUS current
  415. + DESCRIPTION
  416. + "Time interval in seconds for the
  417. + MinASOriginationInterval timer.
  418. + The suggested value for this timer is 15 seconds."
  419. + ::= { bgpPeerEntry 22 }
  420. +
  421. + bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE
  422. + SYNTAX INTEGER (1..65535)
  423. + MAX-ACCESS read-write
  424. + STATUS current
  425. + DESCRIPTION
  426. + "Time interval in seconds for the
  427. + MinRouteAdvertisementInterval timer.
  428. + The suggested value for this timer is 30 seconds."
  429. + ::= { bgpPeerEntry 23 }
  430. +
  431. + bgpPeerInUpdateElapsedTime OBJECT-TYPE
  432. + SYNTAX Gauge32
  433. + MAX-ACCESS read-only
  434. + STATUS current
  435. + DESCRIPTION
  436. + "Elapsed time in seconds since the last BGP
  437. + UPDATE message was received from the peer.
  438. + Each time bgpPeerInUpdates is incremented,
  439. + the value of this object is set to zero (0)."
  440. + ::= { bgpPeerEntry 24 }
  441. +
  442. +
  443. +
  444. + bgpIdentifier OBJECT-TYPE
  445. + SYNTAX IpAddress
  446. + MAX-ACCESS read-only
  447. + STATUS current
  448. + DESCRIPTION
  449. + "The BGP Identifier of local system."
  450. + ::= { bgp 4 }
  451. +
  452. +
  453. +
  454. + -- Received Path Attribute Table. This table contains,
  455. + -- one entry per path to a network, path attributes
  456. + -- received from all peers running BGP version 3 or less.
  457. + -- This table is obsolete, having been replaced in
  458. + -- functionality with the bgp4PathAttrTable.
  459. +
  460. + bgpRcvdPathAttrTable OBJECT-TYPE
  461. + SYNTAX SEQUENCE OF BgpPathAttrEntry
  462. + MAX-ACCESS not-accessible
  463. + STATUS obsolete
  464. + DESCRIPTION
  465. + "The BGP Received Path Attribute Table contains
  466. + information about paths to destination networks
  467. + received from all peers running BGP version 3 or
  468. + less."
  469. + ::= { bgp 5 }
  470. +
  471. + bgpPathAttrEntry OBJECT-TYPE
  472. + SYNTAX BgpPathAttrEntry
  473. + MAX-ACCESS not-accessible
  474. + STATUS obsolete
  475. + DESCRIPTION
  476. + "Information about a path to a network."
  477. + INDEX { bgpPathAttrDestNetwork,
  478. + bgpPathAttrPeer }
  479. + ::= { bgpRcvdPathAttrTable 1 }
  480. +
  481. + BgpPathAttrEntry ::= SEQUENCE {
  482. + bgpPathAttrPeer
  483. + IpAddress,
  484. + bgpPathAttrDestNetwork
  485. + IpAddress,
  486. + bgpPathAttrOrigin
  487. + INTEGER,
  488. + bgpPathAttrASPath
  489. + OCTET STRING,
  490. + bgpPathAttrNextHop
  491. + IpAddress,
  492. + bgpPathAttrInterASMetric
  493. + Integer32
  494. + }
  495. +
  496. + bgpPathAttrPeer OBJECT-TYPE
  497. + SYNTAX IpAddress
  498. + MAX-ACCESS read-only
  499. + STATUS obsolete
  500. + DESCRIPTION
  501. + "The IP address of the peer where the path
  502. + information was learned."
  503. + ::= { bgpPathAttrEntry 1 }
  504. +
  505. + bgpPathAttrDestNetwork OBJECT-TYPE
  506. + SYNTAX IpAddress
  507. + MAX-ACCESS read-only
  508. + STATUS obsolete
  509. + DESCRIPTION
  510. + "The address of the destination network."
  511. + ::= { bgpPathAttrEntry 2 }
  512. +
  513. + bgpPathAttrOrigin OBJECT-TYPE
  514. + SYNTAX INTEGER {
  515. + igp(1),-- networks are interior
  516. + egp(2),-- networks learned via EGP
  517. + incomplete(3) -- undetermined
  518. + }
  519. + MAX-ACCESS read-only
  520. + STATUS obsolete
  521. + DESCRIPTION
  522. + "The ultimate origin of the path information."
  523. + ::= { bgpPathAttrEntry 3 }
  524. +
  525. + bgpPathAttrASPath OBJECT-TYPE
  526. + SYNTAX OCTET STRING (SIZE (2..255))
  527. + MAX-ACCESS read-only
  528. + STATUS obsolete
  529. + DESCRIPTION
  530. + "The set of ASs that must be traversed to reach
  531. + the network. This object is probably best
  532. + represented as SEQUENCE OF INTEGER. For SMI
  533. + compatibility, though, it is represented as
  534. + OCTET STRING. Each AS is represented as a pair
  535. + of octets according to the following algorithm:
  536. +
  537. + first-byte-of-pair = ASNumber / 256;
  538. + second-byte-of-pair = ASNumber & 255;"
  539. + ::= { bgpPathAttrEntry 4 }
  540. +
  541. + bgpPathAttrNextHop OBJECT-TYPE
  542. + SYNTAX IpAddress
  543. + MAX-ACCESS read-only
  544. + STATUS obsolete
  545. + DESCRIPTION
  546. + "The address of the border router that should
  547. + be used for the destination network."
  548. + ::= { bgpPathAttrEntry 5 }
  549. +
  550. + bgpPathAttrInterASMetric OBJECT-TYPE
  551. + SYNTAX Integer32
  552. + MAX-ACCESS read-only
  553. + STATUS obsolete
  554. + DESCRIPTION
  555. + "The optional inter-AS metric. If this
  556. + attribute has not been provided for this route,
  557. + the value for this object is 0."
  558. + ::= { bgpPathAttrEntry 6 }
  559. +
  560. +
  561. +
  562. + -- BGP-4 Received Path Attribute Table. This table contains,
  563. + -- one entry per path to a network, path attributes
  564. + -- received from all peers running BGP-4.
  565. +
  566. + bgp4PathAttrTable OBJECT-TYPE
  567. + SYNTAX SEQUENCE OF Bgp4PathAttrEntry
  568. + MAX-ACCESS not-accessible
  569. + STATUS current
  570. + DESCRIPTION
  571. + "The BGP-4 Received Path Attribute Table contains
  572. + information about paths to destination networks
  573. + received from all BGP4 peers."
  574. + ::= { bgp 6 }
  575. +
  576. + bgp4PathAttrEntry OBJECT-TYPE
  577. + SYNTAX Bgp4PathAttrEntry
  578. + MAX-ACCESS not-accessible
  579. + STATUS current
  580. + DESCRIPTION
  581. + "Information about a path to a network."
  582. + INDEX { bgp4PathAttrIpAddrPrefix,
  583. + bgp4PathAttrIpAddrPrefixLen,
  584. + bgp4PathAttrPeer }
  585. + ::= { bgp4PathAttrTable 1 }
  586. +
  587. + Bgp4PathAttrEntry ::= SEQUENCE {
  588. + bgp4PathAttrPeer
  589. + IpAddress,
  590. + bgp4PathAttrIpAddrPrefixLen
  591. + INTEGER,
  592. + bgp4PathAttrIpAddrPrefix
  593. + IpAddress,
  594. + bgp4PathAttrOrigin
  595. + INTEGER,
  596. + bgp4PathAttrASPathSegment
  597. + OCTET STRING,
  598. + bgp4PathAttrNextHop
  599. + IpAddress,
  600. + bgp4PathAttrMultiExitDisc
  601. + INTEGER,
  602. + bgp4PathAttrLocalPref
  603. + INTEGER,
  604. + bgp4PathAttrAtomicAggregate
  605. + INTEGER,
  606. + bgp4PathAttrAggregatorAS
  607. + INTEGER,
  608. + bgp4PathAttrAggregatorAddr
  609. + IpAddress,
  610. + bgp4PathAttrCalcLocalPref
  611. + INTEGER,
  612. + bgp4PathAttrBest
  613. + INTEGER,
  614. + bgp4PathAttrUnknown
  615. + OCTET STRING
  616. + }
  617. +
  618. + bgp4PathAttrPeer OBJECT-TYPE
  619. + SYNTAX IpAddress
  620. + MAX-ACCESS read-only
  621. + STATUS current
  622. + DESCRIPTION
  623. + "The IP address of the peer where the path
  624. + information was learned."
  625. + ::= { bgp4PathAttrEntry 1 }
  626. + bgp4PathAttrIpAddrPrefixLen OBJECT-TYPE
  627. + SYNTAX INTEGER (0..32)
  628. + MAX-ACCESS read-only
  629. + STATUS current
  630. + DESCRIPTION
  631. + "Length in bits of the IP address prefix in the
  632. + Network Layer Reachability Information field."
  633. + ::= { bgp4PathAttrEntry 2 }
  634. +
  635. + bgp4PathAttrIpAddrPrefix OBJECT-TYPE
  636. + SYNTAX IpAddress
  637. + MAX-ACCESS read-only
  638. + STATUS current
  639. + DESCRIPTION
  640. + "An IP address prefix in the Network Layer
  641. + Reachability Information field. This object
  642. + is an IP address containing the prefix with
  643. + length specified by bgp4PathAttrIpAddrPrefixLen.
  644. + Any bits beyond the length specified by
  645. + bgp4PathAttrIpAddrPrefixLen are zeroed."
  646. + ::= { bgp4PathAttrEntry 3 }
  647. +
  648. + bgp4PathAttrOrigin OBJECT-TYPE
  649. + SYNTAX INTEGER {
  650. + igp(1),-- networks are interior
  651. + egp(2),-- networks learned via EGP
  652. + incomplete(3) -- undetermined
  653. + }
  654. + MAX-ACCESS read-only
  655. + STATUS current
  656. + DESCRIPTION
  657. + "The ultimate origin of the path information."
  658. + ::= { bgp4PathAttrEntry 4 }
  659. +
  660. + bgp4PathAttrASPathSegment OBJECT-TYPE
  661. + SYNTAX OCTET STRING (SIZE (2..255))
  662. + MAX-ACCESS read-only
  663. + STATUS current
  664. + DESCRIPTION
  665. + "The sequence of AS path segments. Each AS
  666. + path segment is represented by a triple
  667. + <type, length, value>.
  668. +
  669. + The type is a 1-octet field which has two
  670. + possible values:
  671. + 1 AS_SET: unordered set of ASs a
  672. + route in the UPDATE message
  673. + has traversed
  674. + 2 AS_SEQUENCE: ordered set of ASs
  675. + a route in the UPDATE message
  676. + has traversed.
  677. +
  678. + The length is a 1-octet field containing the
  679. + number of ASs in the value field.
  680. +
  681. + The value field contains one or more AS
  682. + numbers, each AS is represented in the octet
  683. + string as a pair of octets according to the
  684. + following algorithm:
  685. +
  686. + first-byte-of-pair = ASNumber / 256;
  687. + second-byte-of-pair = ASNumber & 255;"
  688. + ::= { bgp4PathAttrEntry 5 }
  689. +
  690. + bgp4PathAttrNextHop OBJECT-TYPE
  691. + SYNTAX IpAddress
  692. + MAX-ACCESS read-only
  693. + STATUS current
  694. + DESCRIPTION
  695. + "The address of the border router that should
  696. + be used for the destination network."
  697. + ::= { bgp4PathAttrEntry 6 }
  698. +
  699. + bgp4PathAttrMultiExitDisc OBJECT-TYPE
  700. + SYNTAX INTEGER (-1..2147483647)
  701. + MAX-ACCESS read-only
  702. + STATUS current
  703. + DESCRIPTION
  704. + "This metric is used to discriminate between
  705. + multiple exit points to an adjacent autonomous
  706. + system. A value of -1 indicates the absence of
  707. + this attribute."
  708. + ::= { bgp4PathAttrEntry 7 }
  709. +
  710. + bgp4PathAttrLocalPref OBJECT-TYPE
  711. + SYNTAX INTEGER (-1..2147483647)
  712. + MAX-ACCESS read-only
  713. + STATUS current
  714. + DESCRIPTION
  715. + "The originating BGP4 speaker's degree of
  716. + preference for an advertised route. A value of
  717. + -1 indicates the absence of this attribute."
  718. + ::= { bgp4PathAttrEntry 8 }
  719. +
  720. + bgp4PathAttrAtomicAggregate OBJECT-TYPE
  721. + SYNTAX INTEGER {
  722. + lessSpecificRrouteNotSelected(1),
  723. + lessSpecificRouteSelected(2)
  724. + }
  725. + MAX-ACCESS read-only
  726. + STATUS current
  727. + DESCRIPTION
  728. + "Whether or not a system has selected
  729. + a less specific route without selecting a
  730. + more specific route."
  731. + ::= { bgp4PathAttrEntry 9 }
  732. +
  733. + bgp4PathAttrAggregatorAS OBJECT-TYPE
  734. + SYNTAX INTEGER (0..65535)
  735. + MAX-ACCESS read-only
  736. + STATUS current
  737. + DESCRIPTION
  738. + "The AS number of the last BGP4 speaker that
  739. + performed route aggregation. A value of zero (0)
  740. + indicates the absence of this attribute."
  741. + ::= { bgp4PathAttrEntry 10 }
  742. +
  743. + bgp4PathAttrAggregatorAddr OBJECT-TYPE
  744. + SYNTAX IpAddress
  745. + MAX-ACCESS read-only
  746. + STATUS current
  747. + DESCRIPTION
  748. + "The IP address of the last BGP4 speaker that
  749. + performed route aggregation. A value of
  750. + 0.0.0.0 indicates the absence of this attribute."
  751. + ::= { bgp4PathAttrEntry 11 }
  752. +
  753. + bgp4PathAttrCalcLocalPref OBJECT-TYPE
  754. + SYNTAX INTEGER (-1..2147483647)
  755. + MAX-ACCESS read-only
  756. + STATUS current
  757. + DESCRIPTION
  758. + "The degree of preference calculated by the
  759. + receiving BGP4 speaker for an advertised route.
  760. + A value of -1 indicates the absence of this
  761. + attribute."
  762. + ::= { bgp4PathAttrEntry 12 }
  763. +
  764. + bgp4PathAttrBest OBJECT-TYPE
  765. + SYNTAX INTEGER {
  766. + false(1),-- not chosen as best route
  767. + true(2) -- chosen as best route
  768. + }
  769. + MAX-ACCESS read-only
  770. + STATUS current
  771. + DESCRIPTION
  772. + "An indication of whether or not this route
  773. + was chosen as the best BGP4 route."
  774. + ::= { bgp4PathAttrEntry 13 }
  775. +
  776. + bgp4PathAttrUnknown OBJECT-TYPE
  777. + SYNTAX OCTET STRING (SIZE(0..255))
  778. + MAX-ACCESS read-only
  779. + STATUS current
  780. + DESCRIPTION
  781. + "One or more path attributes not understood
  782. + by this BGP4 speaker. Size zero (0) indicates
  783. + the absence of such attribute(s). Octets
  784. + beyond the maximum size, if any, are not
  785. + recorded by this object."
  786. + ::= { bgp4PathAttrEntry 14 }
  787. +
  788. +
  789. + -- Traps.
  790. +
  791. + -- note that in RFC 1657, bgpTraps was incorrectly
  792. + -- assigned a value of { bgp 7 }, and each of the
  793. + -- traps had the bgpPeerRemoteAddr object inappropriately
  794. + -- removed from their OBJECTS clause. The following
  795. + -- definitions restore the semantics of the traps as
  796. + -- they were initially defined in RFC 1269.
  797. +
  798. + -- { bgp 7 } is unused
  799. +
  800. + bgpTraps OBJECT IDENTIFIER ::= { bgp 0 }
  801. +
  802. + bgpEstablished NOTIFICATION-TYPE
  803. + OBJECTS { bgpPeerRemoteAddr,
  804. + bgpPeerLastError,
  805. + bgpPeerState }
  806. + STATUS current
  807. + DESCRIPTION
  808. + "The BGP Established event is generated when
  809. + the BGP FSM enters the ESTABLISHED state."
  810. + ::= { bgpTraps 1 }
  811. +
  812. + bgpBackwardTransition NOTIFICATION-TYPE
  813. + OBJECTS { bgpPeerRemoteAddr,
  814. + bgpPeerLastError,
  815. + bgpPeerState }
  816. + STATUS current
  817. + DESCRIPTION
  818. + "The BGPBackwardTransition Event is generated
  819. + when the BGP FSM moves from a higher numbered
  820. + state to a lower numbered state."
  821. + ::= { bgpTraps 2 }
  822. +
  823. + -- conformance information
  824. +
  825. + bgpMIBConformance OBJECT IDENTIFIER ::= { bgp 8 }
  826. + bgpMIBCompliances OBJECT IDENTIFIER ::= { bgpMIBConformance 1 }
  827. + bgpMIBGroups OBJECT IDENTIFIER ::= { bgpMIBConformance 2 }
  828. +
  829. + -- compliance statements
  830. +
  831. + bgpMIBCompliance MODULE-COMPLIANCE
  832. + STATUS current
  833. + DESCRIPTION
  834. + "The compliance statement for entities which
  835. + implement the BGP4 mib."
  836. + MODULE -- this module
  837. + MANDATORY-GROUPS { bgp4MIBGlobalsGroup,
  838. + bgp4MIBPeerGroup,
  839. + bgp4MIBPathAttrGroup,
  840. + bgp4MIBNotificationGroup }
  841. + ::= { bgpMIBCompliances 1 }
  842. +
  843. + -- units of conformance
  844. +
  845. + bgp4MIBGlobalsGroup OBJECT-GROUP
  846. + OBJECTS { bgpVersion,
  847. + bgpLocalAs,
  848. + bgpIdentifier }
  849. + STATUS current
  850. + DESCRIPTION
  851. + "A collection of objects providing information
  852. + on global BGP state."
  853. + ::= { bgpMIBGroups 1 }
  854. +
  855. + bgp4MIBPeerGroup OBJECT-GROUP
  856. + OBJECTS { bgpPeerIdentifier,
  857. + bgpPeerState,
  858. + bgpPeerAdminStatus,
  859. + bgpPeerNegotiatedVersion,
  860. + bgpPeerLocalAddr,
  861. + bgpPeerLocalPort,
  862. + bgpPeerRemoteAddr,
  863. + bgpPeerRemotePort,
  864. + bgpPeerRemoteAs,
  865. + bgpPeerInUpdates,
  866. + bgpPeerOutUpdates,
  867. + bgpPeerInTotalMessages,
  868. + bgpPeerOutTotalMessages,
  869. + bgpPeerLastError,
  870. + bgpPeerFsmEstablishedTransitions,
  871. + bgpPeerFsmEstablishedTime,
  872. + bgpPeerConnectRetryInterval,
  873. + bgpPeerHoldTime,
  874. + bgpPeerKeepAlive,
  875. + bgpPeerHoldTimeConfigured,
  876. + bgpPeerKeepAliveConfigured,
  877. + bgpPeerMinASOriginationInterval,
  878. + bgpPeerMinRouteAdvertisementInterval,
  879. + bgpPeerInUpdateElapsedTime }
  880. + STATUS current
  881. + DESCRIPTION
  882. + "A collection of objects for managing
  883. + BGP peers."
  884. + ::= { bgpMIBGroups 2 }
  885. +
  886. + bgp4MIBRcvdPathAttrGroup OBJECT-GROUP
  887. + OBJECTS { bgpPathAttrPeer,
  888. + bgpPathAttrDestNetwork,
  889. + bgpPathAttrOrigin,
  890. + bgpPathAttrASPath,
  891. + bgpPathAttrNextHop,
  892. + bgpPathAttrInterASMetric }
  893. + STATUS obsolete
  894. + DESCRIPTION
  895. + "A collection of objects for managing BGP
  896. + path entries.
  897. +
  898. + This conformance group is obsolete,
  899. + replaced by bgp4MIBPathAttrGroup."
  900. + ::= { bgpMIBGroups 3 }
  901. +
  902. + bgp4MIBPathAttrGroup OBJECT-GROUP
  903. + OBJECTS { bgp4PathAttrPeer,
  904. + bgp4PathAttrIpAddrPrefixLen,
  905. + bgp4PathAttrIpAddrPrefix,
  906. + bgp4PathAttrOrigin,
  907. + bgp4PathAttrASPathSegment,
  908. + bgp4PathAttrNextHop,
  909. + bgp4PathAttrMultiExitDisc,
  910. + bgp4PathAttrLocalPref,
  911. + bgp4PathAttrAtomicAggregate,
  912. + bgp4PathAttrAggregatorAS,
  913. + bgp4PathAttrAggregatorAddr,
  914. + bgp4PathAttrCalcLocalPref,
  915. + bgp4PathAttrBest,
  916. + bgp4PathAttrUnknown }
  917. + STATUS current
  918. + DESCRIPTION
  919. + "A collection of objects for managing
  920. + BGP path entries."
  921. + ::= { bgpMIBGroups 4 }
  922. +
  923. + bgp4MIBNotificationGroup NOTIFICATION-GROUP
  924. + NOTIFICATIONS { bgpEstablished,
  925. + bgpBackwardTransition }
  926. + STATUS current
  927. + DESCRIPTION
  928. + "A collection of notifications for signaling
  929. + changes in BGP peer relationships."
  930. + ::= { bgpMIBGroups 5 }
  931. +
  932. + END
  933. --- /dev/null
  934. +++ b/mibs/BRIDGE-MIB.txt
  935. @@ -0,0 +1,1075 @@
  936. +BRIDGE-MIB DEFINITIONS ::= BEGIN
  937. +
  938. +IMPORTS
  939. + Counter, TimeTicks
  940. + FROM RFC1155-SMI
  941. + mib-2
  942. + FROM RFC1213-MIB
  943. + OBJECT-TYPE
  944. + FROM RFC-1212
  945. + TRAP-TYPE
  946. + FROM RFC-1215;
  947. +
  948. +-- All representations of MAC addresses in this MIB Module
  949. +-- use, as a textual convention (i.e. this convention does
  950. +-- not affect their encoding), the data type:
  951. +MacAddress ::= OCTET STRING (SIZE (6)) -- a 6 octet address
  952. + -- in the
  953. + -- "canonical"
  954. + -- order
  955. +-- defined by IEEE 802.1a, i.e., as if it were transmitted
  956. +-- least significant bit first, even though 802.5 (in
  957. +-- contrast to other n802.x protocols) requires MAC
  958. +-- addresses to be transmitted most significant bit first.
  959. +--
  960. +-- 16-bit addresses, if needed, are represented by setting
  961. +-- their upper 4 octets to all 0's, i.e., AAFF would be
  962. +-- represented as 00000000AAFF.
  963. +
  964. +-- Similarly, all representations of Bridge-Id in this MIB
  965. +-- Module use, as a textual convention (i.e. this
  966. +-- convention does not affect their encoding), the data
  967. +-- type:
  968. +BridgeId ::= OCTET STRING (SIZE (8)) -- the
  969. + -- Bridge-Identifier
  970. + -- as used in the
  971. + -- Spanning Tree
  972. +-- Protocol to uniquely identify a bridge. Its first two
  973. +-- octets (in network byte order) contain a priority
  974. +-- value and its last 6 octets contain the MAC address
  975. +-- used to refer to a bridge in a unique fashion
  976. +-- (typically, the numerically smallest MAC address
  977. +-- of all ports on the bridge).
  978. +
  979. +-- Several objects in this MIB module represent values of
  980. +-- timers used by the Spanning Tree Protocol. In this
  981. +-- MIB, these timers have values in units of hundreths of
  982. +-- a second (i.e. 1/100 secs).
  983. +-- These timers, when stored in a Spanning Tree Protocol's
  984. +-- BPDU, are in units of 1/256 seconds. Note, however,
  985. +-- that 802.1D-1990 specifies a settable granularity of
  986. +-- no more than 1 second for these timers. To avoid
  987. +-- ambiguity, a data type is defined here as a textual
  988. +-- convention and all representation of these timers
  989. +-- in this MIB module are defined using this data type. An
  990. +-- algorithm is also defined for converting between the
  991. +-- different units, to ensure a timer's value is not
  992. +-- distorted by multiple conversions.
  993. +-- The data type is:
  994. +
  995. +Timeout ::= INTEGER -- a STP timer in units of 1/100 seconds
  996. +
  997. +-- To convert a Timeout value into a value in units of
  998. +-- 1/256 seconds, the following algorithm should be used:
  999. +--
  1000. +-- b = floor( (n * 256) / 100)
  1001. +--
  1002. +-- where:
  1003. +-- floor = quotient [ignore remainder]
  1004. +-- n is the value in 1/100 second units
  1005. +-- b is the value in 1/256 second units
  1006. +--
  1007. +-- To convert the value from 1/256 second units back to
  1008. +-- 1/100 seconds, the following algorithm should be used:
  1009. +--
  1010. +-- n = ceiling( (b * 100) / 256)
  1011. +--
  1012. +-- where:
  1013. +-- ceiling = quotient [if remainder is 0], or
  1014. +-- quotient + 1 [if remainder is non-zero]
  1015. +-- n is the value in 1/100 second units
  1016. +-- b is the value in 1/256 second units
  1017. +--
  1018. +-- Note: it is important that the arithmetic operations are
  1019. +-- done in the order specified (i.e., multiply first, divide
  1020. +-- second).
  1021. +
  1022. + dot1dBridge OBJECT IDENTIFIER ::= { mib-2 17 }
  1023. +
  1024. +-- groups in the Bridge MIB
  1025. +
  1026. +dot1dBase OBJECT IDENTIFIER ::= { dot1dBridge 1 }
  1027. +
  1028. +dot1dStp OBJECT IDENTIFIER ::= { dot1dBridge 2 }
  1029. +
  1030. +dot1dSr OBJECT IDENTIFIER ::= { dot1dBridge 3 }
  1031. +-- separately documented
  1032. +
  1033. +dot1dTp OBJECT IDENTIFIER ::= { dot1dBridge 4 }
  1034. +
  1035. +dot1dStatic OBJECT IDENTIFIER ::= { dot1dBridge 5 }
  1036. +
  1037. +-- the dot1dBase group
  1038. +
  1039. +-- Implementation of the dot1dBase group is mandatory for all
  1040. +-- bridges.
  1041. +
  1042. +dot1dBaseBridgeAddress OBJECT-TYPE
  1043. + SYNTAX MacAddress
  1044. + ACCESS read-only
  1045. + STATUS mandatory
  1046. + DESCRIPTION
  1047. + "The MAC address used by this bridge when it must
  1048. + be referred to in a unique fashion. It is
  1049. + recommended that this be the numerically smallest
  1050. + MAC address of all ports that belong to this
  1051. + bridge. However it is only required to be unique.
  1052. + When concatenated with dot1dStpPriority a unique
  1053. + BridgeIdentifier is formed which is used in the
  1054. + Spanning Tree Protocol."
  1055. + REFERENCE
  1056. + "IEEE 802.1D-1990: Sections 6.4.1.1.3 and 3.12.5"
  1057. + ::= { dot1dBase 1 }
  1058. +
  1059. +dot1dBaseNumPorts OBJECT-TYPE
  1060. + SYNTAX INTEGER
  1061. + ACCESS read-only
  1062. + STATUS mandatory
  1063. + DESCRIPTION
  1064. + "The number of ports controlled by this bridging
  1065. + entity."
  1066. + REFERENCE
  1067. + "IEEE 802.1D-1990: Section 6.4.1.1.3"
  1068. + ::= { dot1dBase 2 }
  1069. +
  1070. +dot1dBaseType OBJECT-TYPE
  1071. + SYNTAX INTEGER {
  1072. + unknown(1),
  1073. + transparent-only(2),
  1074. + sourceroute-only(3),
  1075. + srt(4)
  1076. + }
  1077. + ACCESS read-only
  1078. + STATUS mandatory
  1079. + DESCRIPTION
  1080. + "Indicates what type of bridging this bridge can
  1081. + perform. If a bridge is actually performing a
  1082. + certain type of bridging this will be indicated by
  1083. + entries in the port table for the given type."
  1084. + ::= { dot1dBase 3 }
  1085. +
  1086. +-- The Generic Bridge Port Table
  1087. +
  1088. +dot1dBasePortTable OBJECT-TYPE
  1089. + SYNTAX SEQUENCE OF Dot1dBasePortEntry
  1090. + ACCESS not-accessible
  1091. + STATUS mandatory
  1092. + DESCRIPTION
  1093. + "A table that contains generic information about
  1094. + every port that is associated with this bridge.
  1095. + Transparent, source-route, and srt ports are
  1096. + included."
  1097. + ::= { dot1dBase 4 }
  1098. +
  1099. +dot1dBasePortEntry OBJECT-TYPE
  1100. + SYNTAX Dot1dBasePortEntry
  1101. + ACCESS not-accessible
  1102. + STATUS mandatory
  1103. + DESCRIPTION
  1104. + "A list of information for each port of the
  1105. + bridge."
  1106. + REFERENCE
  1107. + "IEEE 802.1D-1990: Section 6.4.2, 6.6.1"
  1108. + INDEX { dot1dBasePort }
  1109. + ::= { dot1dBasePortTable 1 }
  1110. +
  1111. +Dot1dBasePortEntry ::=
  1112. + SEQUENCE {
  1113. + dot1dBasePort
  1114. + INTEGER,
  1115. + dot1dBasePortIfIndex
  1116. + INTEGER,
  1117. + dot1dBasePortCircuit
  1118. +
  1119. + OBJECT IDENTIFIER,
  1120. + dot1dBasePortDelayExceededDiscards
  1121. + Counter,
  1122. + dot1dBasePortMtuExceededDiscards
  1123. + Counter
  1124. + }
  1125. +
  1126. +dot1dBasePort OBJECT-TYPE
  1127. + SYNTAX INTEGER (1..65535)
  1128. + ACCESS read-only
  1129. + STATUS mandatory
  1130. + DESCRIPTION
  1131. + "The port number of the port for which this entry
  1132. + contains bridge management information."
  1133. + ::= { dot1dBasePortEntry 1 }
  1134. +
  1135. +dot1dBasePortIfIndex OBJECT-TYPE
  1136. + SYNTAX INTEGER
  1137. + ACCESS read-only
  1138. + STATUS mandatory
  1139. + DESCRIPTION
  1140. + "The value of the instance of the ifIndex object,
  1141. + defined in MIB-II, for the interface corresponding
  1142. + to this port."
  1143. + ::= { dot1dBasePortEntry 2 }
  1144. +
  1145. +dot1dBasePortCircuit OBJECT-TYPE
  1146. + SYNTAX OBJECT IDENTIFIER
  1147. + ACCESS read-only
  1148. + STATUS mandatory
  1149. + DESCRIPTION
  1150. + "For a port which (potentially) has the same value
  1151. + of dot1dBasePortIfIndex as another port on the
  1152. + same bridge, this object contains the name of an
  1153. + object instance unique to this port. For example,
  1154. + in the case where multiple ports correspond one-
  1155. + to-one with multiple X.25 virtual circuits, this
  1156. + value might identify an (e.g., the first) object
  1157. + instance associated with the X.25 virtual circuit
  1158. + corresponding to this port.
  1159. +
  1160. + For a port which has a unique value of
  1161. + dot1dBasePortIfIndex, this object can have the
  1162. + value { 0 0 }."
  1163. + ::= { dot1dBasePortEntry 3 }
  1164. +
  1165. +dot1dBasePortDelayExceededDiscards OBJECT-TYPE
  1166. + SYNTAX Counter
  1167. +
  1168. + ACCESS read-only
  1169. + STATUS mandatory
  1170. + DESCRIPTION
  1171. + "The number of frames discarded by this port due
  1172. + to excessive transit delay through the bridge. It
  1173. + is incremented by both transparent and source
  1174. + route bridges."
  1175. + REFERENCE
  1176. + "IEEE 802.1D-1990: Section 6.6.1.1.3"
  1177. + ::= { dot1dBasePortEntry 4 }
  1178. +
  1179. +dot1dBasePortMtuExceededDiscards OBJECT-TYPE
  1180. + SYNTAX Counter
  1181. + ACCESS read-only
  1182. + STATUS mandatory
  1183. + DESCRIPTION
  1184. + "The number of frames discarded by this port due
  1185. + to an excessive size. It is incremented by both
  1186. + transparent and source route bridges."
  1187. + REFERENCE
  1188. + "IEEE 802.1D-1990: Section 6.6.1.1.3"
  1189. + ::= { dot1dBasePortEntry 5 }
  1190. +
  1191. +-- the dot1dStp group
  1192. +
  1193. +-- Implementation of the dot1dStp group is optional. It is
  1194. +-- implemented by those bridges that support the Spanning Tree
  1195. +-- Protocol.
  1196. +
  1197. +dot1dStpProtocolSpecification OBJECT-TYPE
  1198. + SYNTAX INTEGER {
  1199. + unknown(1),
  1200. + decLb100(2),
  1201. + ieee8021d(3)
  1202. + }
  1203. + ACCESS read-only
  1204. + STATUS mandatory
  1205. + DESCRIPTION
  1206. + "An indication of what version of the Spanning
  1207. + Tree Protocol is being run. The value
  1208. + 'decLb100(2)' indicates the DEC LANbridge 100
  1209. + Spanning Tree protocol. IEEE 802.1d
  1210. + implementations will return 'ieee8021d(3)'. If
  1211. + future versions of the IEEE Spanning Tree Protocol
  1212. + are released that are incompatible with the
  1213. + current version a new value will be defined."
  1214. +
  1215. + ::= { dot1dStp 1 }
  1216. +
  1217. +dot1dStpPriority OBJECT-TYPE
  1218. + SYNTAX INTEGER (0..65535)
  1219. + ACCESS read-write
  1220. + STATUS mandatory
  1221. + DESCRIPTION
  1222. + "The value of the write-able portion of the Bridge
  1223. + ID, i.e., the first two octets of the (8 octet
  1224. + long) Bridge ID. The other (last) 6 octets of the
  1225. + Bridge ID are given by the value of
  1226. + dot1dBaseBridgeAddress."
  1227. + REFERENCE
  1228. + "IEEE 802.1D-1990: Section 4.5.3.7"
  1229. + ::= { dot1dStp 2 }
  1230. +
  1231. +dot1dStpTimeSinceTopologyChange OBJECT-TYPE
  1232. + SYNTAX TimeTicks
  1233. + ACCESS read-only
  1234. + STATUS mandatory
  1235. + DESCRIPTION
  1236. + "The time (in hundredths of a second) since the
  1237. + last time a topology change was detected by the
  1238. + bridge entity."
  1239. + REFERENCE
  1240. + "IEEE 802.1D-1990: Section 6.8.1.1.3"
  1241. + ::= { dot1dStp 3 }
  1242. +
  1243. +dot1dStpTopChanges OBJECT-TYPE
  1244. + SYNTAX Counter
  1245. + ACCESS read-only
  1246. + STATUS mandatory
  1247. + DESCRIPTION
  1248. + "The total number of topology changes detected by
  1249. + this bridge since the management entity was last
  1250. + reset or initialized."
  1251. + REFERENCE
  1252. + "IEEE 802.1D-1990: Section 6.8.1.1.3"
  1253. + ::= { dot1dStp 4 }
  1254. +
  1255. +dot1dStpDesignatedRoot OBJECT-TYPE
  1256. + SYNTAX BridgeId
  1257. + ACCESS read-only
  1258. + STATUS mandatory
  1259. + DESCRIPTION
  1260. + "The bridge identifier of the root of the spanning
  1261. + tree as determined by the Spanning Tree Protocol
  1262. + as executed by this node. This value is used as
  1263. +
  1264. + the Root Identifier parameter in all Configuration
  1265. + Bridge PDUs originated by this node."
  1266. + REFERENCE
  1267. + "IEEE 802.1D-1990: Section 4.5.3.1"
  1268. + ::= { dot1dStp 5 }
  1269. +
  1270. +dot1dStpRootCost OBJECT-TYPE
  1271. + SYNTAX INTEGER
  1272. + ACCESS read-only
  1273. + STATUS mandatory
  1274. + DESCRIPTION
  1275. + "The cost of the path to the root as seen from
  1276. + this bridge."
  1277. + REFERENCE
  1278. + "IEEE 802.1D-1990: Section 4.5.3.2"
  1279. + ::= { dot1dStp 6 }
  1280. +
  1281. +dot1dStpRootPort OBJECT-TYPE
  1282. + SYNTAX INTEGER
  1283. + ACCESS read-only
  1284. + STATUS mandatory
  1285. + DESCRIPTION
  1286. + "The port number of the port which offers the
  1287. + lowest cost path from this bridge to the root
  1288. + bridge."
  1289. + REFERENCE
  1290. + "IEEE 802.1D-1990: Section 4.5.3.3"
  1291. + ::= { dot1dStp 7 }
  1292. +
  1293. +dot1dStpMaxAge OBJECT-TYPE
  1294. + SYNTAX Timeout
  1295. + ACCESS read-only
  1296. + STATUS mandatory
  1297. + DESCRIPTION
  1298. + "The maximum age of Spanning Tree Protocol
  1299. + information learned from the network on any port
  1300. + before it is discarded, in units of hundredths of
  1301. + a second. This is the actual value that this
  1302. + bridge is currently using."
  1303. + REFERENCE
  1304. + "IEEE 802.1D-1990: Section 4.5.3.4"
  1305. + ::= { dot1dStp 8 }
  1306. +
  1307. +dot1dStpHelloTime OBJECT-TYPE
  1308. + SYNTAX Timeout
  1309. + ACCESS read-only
  1310. + STATUS mandatory
  1311. + DESCRIPTION
  1312. +
  1313. + "The amount of time between the transmission of
  1314. + Configuration bridge PDUs by this node on any port
  1315. + when it is the root of the spanning tree or trying
  1316. + to become so, in units of hundredths of a second.
  1317. + This is the actual value that this bridge is
  1318. + currently using."
  1319. + REFERENCE
  1320. + "IEEE 802.1D-1990: Section 4.5.3.5"
  1321. + ::= { dot1dStp 9 }
  1322. +
  1323. +dot1dStpHoldTime OBJECT-TYPE
  1324. + SYNTAX INTEGER
  1325. + ACCESS read-only
  1326. + STATUS mandatory
  1327. + DESCRIPTION
  1328. + "This time value determines the interval length
  1329. + during which no more than two Configuration bridge
  1330. + PDUs shall be transmitted by this node, in units
  1331. + of hundredths of a second."
  1332. + REFERENCE
  1333. + "IEEE 802.1D-1990: Section 4.5.3.14"
  1334. + ::= { dot1dStp 10 }
  1335. +
  1336. +dot1dStpForwardDelay OBJECT-TYPE
  1337. + SYNTAX Timeout
  1338. + ACCESS read-only
  1339. + STATUS mandatory
  1340. + DESCRIPTION
  1341. + "This time value, measured in units of hundredths
  1342. + of a second, controls how fast a port changes its
  1343. + spanning state when moving towards the Forwarding
  1344. + state. The value determines how long the port
  1345. + stays in each of the Listening and Learning
  1346. + states, which precede the Forwarding state. This
  1347. + value is also used, when a topology change has
  1348. + been detected and is underway, to age all dynamic
  1349. + entries in the Forwarding Database. [Note that
  1350. + this value is the one that this bridge is
  1351. + currently using, in contrast to
  1352. + dot1dStpBridgeForwardDelay which is the value that
  1353. + this bridge and all others would start using
  1354. + if/when this bridge were to become the root.]"
  1355. + REFERENCE
  1356. + "IEEE 802.1D-1990: Section 4.5.3.6"
  1357. + ::= { dot1dStp 11 }
  1358. +
  1359. +dot1dStpBridgeMaxAge OBJECT-TYPE
  1360. + SYNTAX Timeout (600..4000)
  1361. +
  1362. + ACCESS read-write
  1363. + STATUS mandatory
  1364. + DESCRIPTION
  1365. + "The value that all bridges use for MaxAge when
  1366. + this bridge is acting as the root. Note that
  1367. + 802.1D-1990 specifies that the range for this
  1368. + parameter is related to the value of
  1369. + dot1dStpBridgeHelloTime. The granularity of this
  1370. + timer is specified by 802.1D-1990 to be 1 second.
  1371. + An agent may return a badValue error if a set is
  1372. + attempted to a value which is not a whole number
  1373. + of seconds."
  1374. + REFERENCE
  1375. + "IEEE 802.1D-1990: Section 4.5.3.8"
  1376. + ::= { dot1dStp 12 }
  1377. +
  1378. +dot1dStpBridgeHelloTime OBJECT-TYPE
  1379. + SYNTAX Timeout (100..1000)
  1380. + ACCESS read-write
  1381. + STATUS mandatory
  1382. + DESCRIPTION
  1383. + "The value that all bridges use for HelloTime when
  1384. + this bridge is acting as the root. The
  1385. + granularity of this timer is specified by 802.1D-
  1386. + 1990 to be 1 second. An agent may return a
  1387. + badValue error if a set is attempted to a value
  1388. + which is not a whole number of seconds."
  1389. + REFERENCE
  1390. + "IEEE 802.1D-1990: Section 4.5.3.9"
  1391. + ::= { dot1dStp 13 }
  1392. +
  1393. +dot1dStpBridgeForwardDelay OBJECT-TYPE
  1394. + SYNTAX Timeout (400..3000)
  1395. + ACCESS read-write
  1396. + STATUS mandatory
  1397. + DESCRIPTION
  1398. + "The value that all bridges use for ForwardDelay
  1399. + when this bridge is acting as the root. Note that
  1400. + 802.1D-1990 specifies that the range for this
  1401. + parameter is related to the value of
  1402. + dot1dStpBridgeMaxAge. The granularity of this
  1403. + timer is specified by 802.1D-1990 to be 1 second.
  1404. + An agent may return a badValue error if a set is
  1405. + attempted to a value which is not a whole number
  1406. + of seconds."
  1407. + REFERENCE
  1408. + "IEEE 802.1D-1990: Section 4.5.3.10"
  1409. + ::= { dot1dStp 14 }
  1410. +
  1411. +-- The Spanning Tree Port Table
  1412. +
  1413. +dot1dStpPortTable OBJECT-TYPE
  1414. + SYNTAX SEQUENCE OF Dot1dStpPortEntry
  1415. + ACCESS not-accessible
  1416. + STATUS mandatory
  1417. + DESCRIPTION
  1418. + "A table that contains port-specific information
  1419. + for the Spanning Tree Protocol."
  1420. + ::= { dot1dStp 15 }
  1421. +
  1422. +dot1dStpPortEntry OBJECT-TYPE
  1423. + SYNTAX Dot1dStpPortEntry
  1424. + ACCESS not-accessible
  1425. + STATUS mandatory
  1426. + DESCRIPTION
  1427. + "A list of information maintained by every port
  1428. + about the Spanning Tree Protocol state for that
  1429. + port."
  1430. + INDEX { dot1dStpPort }
  1431. + ::= { dot1dStpPortTable 1 }
  1432. +
  1433. +Dot1dStpPortEntry ::=
  1434. + SEQUENCE {
  1435. + dot1dStpPort
  1436. + INTEGER,
  1437. + dot1dStpPortPriority
  1438. + INTEGER,
  1439. + dot1dStpPortState
  1440. + INTEGER,
  1441. + dot1dStpPortEnable
  1442. + INTEGER,
  1443. + dot1dStpPortPathCost
  1444. + INTEGER,
  1445. + dot1dStpPortDesignatedRoot
  1446. + BridgeId,
  1447. + dot1dStpPortDesignatedCost
  1448. + INTEGER,
  1449. + dot1dStpPortDesignatedBridge
  1450. + BridgeId,
  1451. + dot1dStpPortDesignatedPort
  1452. + OCTET STRING,
  1453. + dot1dStpPortForwardTransitions
  1454. + Counter
  1455. + }
  1456. +
  1457. +dot1dStpPort OBJECT-TYPE
  1458. + SYNTAX INTEGER (1..65535)
  1459. +
  1460. + ACCESS read-only
  1461. + STATUS mandatory
  1462. + DESCRIPTION
  1463. + "The port number of the port for which this entry
  1464. + contains Spanning Tree Protocol management
  1465. + information."
  1466. + REFERENCE
  1467. + "IEEE 802.1D-1990: Section 6.8.2.1.2"
  1468. + ::= { dot1dStpPortEntry 1 }
  1469. +
  1470. +dot1dStpPortPriority OBJECT-TYPE
  1471. + SYNTAX INTEGER (0..255)
  1472. + ACCESS read-write
  1473. + STATUS mandatory
  1474. + DESCRIPTION
  1475. + "The value of the priority field which is
  1476. + contained in the first (in network byte order)
  1477. + octet of the (2 octet long) Port ID. The other
  1478. + octet of the Port ID is given by the value of
  1479. + dot1dStpPort."
  1480. + REFERENCE
  1481. + "IEEE 802.1D-1990: Section 4.5.5.1"
  1482. + ::= { dot1dStpPortEntry 2 }
  1483. +
  1484. +dot1dStpPortState OBJECT-TYPE
  1485. + SYNTAX INTEGER {
  1486. + disabled(1),
  1487. + blocking(2),
  1488. + listening(3),
  1489. + learning(4),
  1490. + forwarding(5),
  1491. + broken(6)
  1492. + }
  1493. + ACCESS read-only
  1494. + STATUS mandatory
  1495. + DESCRIPTION
  1496. + "The port's current state as defined by
  1497. + application of the Spanning Tree Protocol. This
  1498. + state controls what action a port takes on
  1499. + reception of a frame. If the bridge has detected
  1500. + a port that is malfunctioning it will place that
  1501. + port into the broken(6) state. For ports which
  1502. + are disabled (see dot1dStpPortEnable), this object
  1503. + will have a value of disabled(1)."
  1504. + REFERENCE
  1505. + "IEEE 802.1D-1990: Section 4.5.5.2"
  1506. + ::= { dot1dStpPortEntry 3 }
  1507. +
  1508. +dot1dStpPortEnable OBJECT-TYPE
  1509. + SYNTAX INTEGER {
  1510. + enabled(1),
  1511. + disabled(2)
  1512. + }
  1513. + ACCESS read-write
  1514. + STATUS mandatory
  1515. + DESCRIPTION
  1516. + "The enabled/disabled status of the port."
  1517. + REFERENCE
  1518. + "IEEE 802.1D-1990: Section 4.5.5.2"
  1519. + ::= { dot1dStpPortEntry 4 }
  1520. +
  1521. +dot1dStpPortPathCost OBJECT-TYPE
  1522. + SYNTAX INTEGER (1..65535)
  1523. + ACCESS read-write
  1524. + STATUS mandatory
  1525. + DESCRIPTION
  1526. + "The contribution of this port to the path cost of
  1527. + paths towards the spanning tree root which include
  1528. + this port. 802.1D-1990 recommends that the
  1529. + default value of this parameter be in inverse
  1530. + proportion to the speed of the attached LAN."
  1531. + REFERENCE
  1532. + "IEEE 802.1D-1990: Section 4.5.5.3"
  1533. + ::= { dot1dStpPortEntry 5 }
  1534. +
  1535. +dot1dStpPortDesignatedRoot OBJECT-TYPE
  1536. + SYNTAX BridgeId
  1537. + ACCESS read-only
  1538. + STATUS mandatory
  1539. + DESCRIPTION
  1540. + "The unique Bridge Identifier of the Bridge
  1541. + recorded as the Root in the Configuration BPDUs
  1542. + transmitted by the Designated Bridge for the
  1543. + segment to which the port is attached."
  1544. + REFERENCE
  1545. + "IEEE 802.1D-1990: Section 4.5.5.4"
  1546. + ::= { dot1dStpPortEntry 6 }
  1547. +
  1548. +dot1dStpPortDesignatedCost OBJECT-TYPE
  1549. + SYNTAX INTEGER
  1550. + ACCESS read-only
  1551. + STATUS mandatory
  1552. + DESCRIPTION
  1553. + "The path cost of the Designated Port of the
  1554. + segment connected to this port. This value is
  1555. + compared to the Root Path Cost field in received
  1556. +
  1557. + bridge PDUs."
  1558. + REFERENCE
  1559. + "IEEE 802.1D-1990: Section 4.5.5.5"
  1560. + ::= { dot1dStpPortEntry 7 }
  1561. +
  1562. +dot1dStpPortDesignatedBridge OBJECT-TYPE
  1563. + SYNTAX BridgeId
  1564. + ACCESS read-only
  1565. + STATUS mandatory
  1566. + DESCRIPTION
  1567. + "The Bridge Identifier of the bridge which this
  1568. + port considers to be the Designated Bridge for
  1569. + this port's segment."
  1570. + REFERENCE
  1571. + "IEEE 802.1D-1990: Section 4.5.5.6"
  1572. + ::= { dot1dStpPortEntry 8 }
  1573. +
  1574. +dot1dStpPortDesignatedPort OBJECT-TYPE
  1575. + SYNTAX OCTET STRING (SIZE (2))
  1576. + ACCESS read-only
  1577. + STATUS mandatory
  1578. + DESCRIPTION
  1579. + "The Port Identifier of the port on the Designated
  1580. + Bridge for this port's segment."
  1581. + REFERENCE
  1582. + "IEEE 802.1D-1990: Section 4.5.5.7"
  1583. + ::= { dot1dStpPortEntry 9 }
  1584. +
  1585. +dot1dStpPortForwardTransitions OBJECT-TYPE
  1586. + SYNTAX Counter
  1587. + ACCESS read-only
  1588. + STATUS mandatory
  1589. + DESCRIPTION
  1590. + "The number of times this port has transitioned
  1591. + from the Learning state to the Forwarding state."
  1592. + ::= { dot1dStpPortEntry 10 }
  1593. +
  1594. +-- the dot1dTp group
  1595. +
  1596. +-- Implementation of the dot1dTp group is optional. It is
  1597. +-- implemented by those bridges that support the transparent
  1598. +-- bridging mode. A transparent or SRT bridge will implement
  1599. +-- this group.
  1600. +
  1601. +dot1dTpLearnedEntryDiscards OBJECT-TYPE
  1602. + SYNTAX Counter
  1603. +
  1604. + ACCESS read-only
  1605. + STATUS mandatory
  1606. + DESCRIPTION
  1607. + "The total number of Forwarding Database entries,
  1608. + which have been or would have been learnt, but
  1609. + have been discarded due to a lack of space to
  1610. + store them in the Forwarding Database. If this
  1611. + counter is increasing, it indicates that the
  1612. + Forwarding Database is regularly becoming full (a
  1613. + condition which has unpleasant performance effects
  1614. + on the subnetwork). If this counter has a
  1615. + significant value but is not presently increasing,
  1616. + it indicates that the problem has been occurring
  1617. + but is not persistent."
  1618. + REFERENCE
  1619. + "IEEE 802.1D-1990: Section 6.7.1.1.3"
  1620. + ::= { dot1dTp 1 }
  1621. +
  1622. +dot1dTpAgingTime OBJECT-TYPE
  1623. + SYNTAX INTEGER (10..1000000)
  1624. + ACCESS read-write
  1625. + STATUS mandatory
  1626. + DESCRIPTION
  1627. + "The timeout period in seconds for aging out
  1628. + dynamically learned forwarding information.
  1629. + 802.1D-1990 recommends a default of 300 seconds."
  1630. + REFERENCE
  1631. + "IEEE 802.1D-1990: Section 6.7.1.1.3"
  1632. + ::= { dot1dTp 2 }
  1633. +
  1634. +-- The Forwarding Database for Transparent Bridges
  1635. +
  1636. +dot1dTpFdbTable OBJECT-TYPE
  1637. + SYNTAX SEQUENCE OF Dot1dTpFdbEntry
  1638. + ACCESS not-accessible
  1639. + STATUS mandatory
  1640. + DESCRIPTION
  1641. + "A table that contains information about unicast
  1642. + entries for which the bridge has forwarding and/or
  1643. + filtering information. This information is used
  1644. + by the transparent bridging function in
  1645. + determining how to propagate a received frame."
  1646. + ::= { dot1dTp 3 }
  1647. +
  1648. +dot1dTpFdbEntry OBJECT-TYPE
  1649. + SYNTAX Dot1dTpFdbEntry
  1650. + ACCESS not-accessible
  1651. + STATUS mandatory
  1652. + DESCRIPTION
  1653. + "Information about a specific unicast MAC address
  1654. + for which the bridge has some forwarding and/or
  1655. + filtering information."
  1656. + INDEX { dot1dTpFdbAddress }
  1657. + ::= { dot1dTpFdbTable 1 }
  1658. +
  1659. +Dot1dTpFdbEntry ::=
  1660. + SEQUENCE {
  1661. + dot1dTpFdbAddress
  1662. + MacAddress,
  1663. + dot1dTpFdbPort
  1664. + INTEGER,
  1665. + dot1dTpFdbStatus
  1666. + INTEGER
  1667. + }
  1668. +
  1669. +dot1dTpFdbAddress OBJECT-TYPE
  1670. + SYNTAX MacAddress
  1671. + ACCESS read-only
  1672. + STATUS mandatory
  1673. + DESCRIPTION
  1674. + "A unicast MAC address for which the bridge has
  1675. + forwarding and/or filtering information."
  1676. + REFERENCE
  1677. + "IEEE 802.1D-1990: Section 3.9.1, 3.9.2"
  1678. + ::= { dot1dTpFdbEntry 1 }
  1679. +
  1680. +dot1dTpFdbPort OBJECT-TYPE
  1681. + SYNTAX INTEGER
  1682. + ACCESS read-only
  1683. + STATUS mandatory
  1684. + DESCRIPTION
  1685. + "Either the value '0', or the port number of the
  1686. + port on which a frame having a source address
  1687. + equal to the value of the corresponding instance
  1688. + of dot1dTpFdbAddress has been seen. A value of
  1689. + '0' indicates that the port number has not been
  1690. + learned but that the bridge does have some
  1691. + forwarding/filtering information about this
  1692. + address (e.g. in the dot1dStaticTable).
  1693. + Implementors are encouraged to assign the port
  1694. + value to this object whenever it is learned even
  1695. + for addresses for which the corresponding value of
  1696. + dot1dTpFdbStatus is not learned(3)."
  1697. + ::= { dot1dTpFdbEntry 2 }
  1698. +
  1699. +dot1dTpFdbStatus OBJECT-TYPE
  1700. + SYNTAX INTEGER {
  1701. + other(1),
  1702. + invalid(2),
  1703. + learned(3),
  1704. + self(4),
  1705. + mgmt(5)
  1706. + }
  1707. + ACCESS read-only
  1708. + STATUS mandatory
  1709. + DESCRIPTION
  1710. + "The status of this entry. The meanings of the
  1711. + values are:
  1712. + other(1) : none of the following. This would
  1713. + include the case where some other
  1714. + MIB object (not the corresponding
  1715. + instance of dot1dTpFdbPort, nor an
  1716. + entry in the dot1dStaticTable) is
  1717. + being used to determine if and how
  1718. + frames addressed to the value of
  1719. + the corresponding instance of
  1720. + dot1dTpFdbAddress are being
  1721. + forwarded.
  1722. + invalid(2) : this entry is not longer valid
  1723. + (e.g., it was learned but has since
  1724. + aged-out), but has not yet been
  1725. + flushed from the table.
  1726. + learned(3) : the value of the corresponding
  1727. + instance of dot1dTpFdbPort was
  1728. + learned, and is being used.
  1729. + self(4) : the value of the corresponding
  1730. + instance of dot1dTpFdbAddress
  1731. + represents one of the bridge's
  1732. + addresses. The corresponding
  1733. + instance of dot1dTpFdbPort
  1734. + indicates which of the bridge's
  1735. + ports has this address.
  1736. + mgmt(5) : the value of the corresponding
  1737. + instance of dot1dTpFdbAddress is
  1738. + also the value of an existing
  1739. + instance of dot1dStaticAddress."
  1740. + ::= { dot1dTpFdbEntry 3 }
  1741. +
  1742. +-- Port Table for Transparent Bridges
  1743. +
  1744. +dot1dTpPortTable OBJECT-TYPE
  1745. + SYNTAX SEQUENCE OF Dot1dTpPortEntry
  1746. + ACCESS not-accessible
  1747. + STATUS mandatory
  1748. + DESCRIPTION
  1749. + "A table that contains information about every
  1750. + port that is associated with this transparent
  1751. + bridge."
  1752. + ::= { dot1dTp 4 }
  1753. +
  1754. +dot1dTpPortEntry OBJECT-TYPE
  1755. + SYNTAX Dot1dTpPortEntry
  1756. + ACCESS not-accessible
  1757. + STATUS mandatory
  1758. + DESCRIPTION
  1759. + "A list of information for each port of a
  1760. + transparent bridge."
  1761. + INDEX { dot1dTpPort }
  1762. + ::= { dot1dTpPortTable 1 }
  1763. +
  1764. +Dot1dTpPortEntry ::=
  1765. + SEQUENCE {
  1766. + dot1dTpPort
  1767. + INTEGER,
  1768. + dot1dTpPortMaxInfo
  1769. + INTEGER,
  1770. + dot1dTpPortInFrames
  1771. + Counter,
  1772. + dot1dTpPortOutFrames
  1773. + Counter,
  1774. + dot1dTpPortInDiscards
  1775. + Counter
  1776. + }
  1777. +
  1778. +dot1dTpPort OBJECT-TYPE
  1779. + SYNTAX INTEGER (1..65535)
  1780. + ACCESS read-only
  1781. + STATUS mandatory
  1782. + DESCRIPTION
  1783. + "The port number of the port for which this entry
  1784. + contains Transparent bridging management
  1785. + information."
  1786. + ::= { dot1dTpPortEntry 1 }
  1787. +
  1788. +-- It would be nice if we could use ifMtu as the size of the
  1789. +-- largest INFO field, but we can't because ifMtu is defined
  1790. +-- to be the size that the (inter-)network layer can use which
  1791. +-- can differ from the MAC layer (especially if several layers
  1792. +-- of encapsulation are used).
  1793. +
  1794. +dot1dTpPortMaxInfo OBJECT-TYPE
  1795. + SYNTAX INTEGER
  1796. + ACCESS read-only
  1797. + STATUS mandatory
  1798. + DESCRIPTION
  1799. + "The maximum size of the INFO (non-MAC) field that
  1800. + this port will receive or transmit."
  1801. + ::= { dot1dTpPortEntry 2 }
  1802. +
  1803. +dot1dTpPortInFrames OBJECT-TYPE
  1804. + SYNTAX Counter
  1805. + ACCESS read-only
  1806. + STATUS mandatory
  1807. + DESCRIPTION
  1808. + "The number of frames that have been received by
  1809. + this port from its segment. Note that a frame
  1810. + received on the interface corresponding to this
  1811. + port is only counted by this object if and only if
  1812. + it is for a protocol being processed by the local
  1813. + bridging function, including bridge management
  1814. + frames."
  1815. + REFERENCE
  1816. + "IEEE 802.1D-1990: Section 6.6.1.1.3"
  1817. + ::= { dot1dTpPortEntry 3 }
  1818. +
  1819. +dot1dTpPortOutFrames OBJECT-TYPE
  1820. + SYNTAX Counter
  1821. + ACCESS read-only
  1822. + STATUS mandatory
  1823. + DESCRIPTION
  1824. + "The number of frames that have been transmitted
  1825. + by this port to its segment. Note that a frame
  1826. + transmitted on the interface corresponding to this
  1827. + port is only counted by this object if and only if
  1828. + it is for a protocol being processed by the local
  1829. + bridging function, including bridge management
  1830. + frames."
  1831. + REFERENCE
  1832. + "IEEE 802.1D-1990: Section 6.6.1.1.3"
  1833. + ::= { dot1dTpPortEntry 4 }
  1834. +
  1835. +dot1dTpPortInDiscards OBJECT-TYPE
  1836. + SYNTAX Counter
  1837. + ACCESS read-only
  1838. + STATUS mandatory
  1839. + DESCRIPTION
  1840. + "Count of valid frames received which were
  1841. + discarded (i.e., filtered) by the Forwarding
  1842. + Process."
  1843. + REFERENCE
  1844. + "IEEE 802.1D-1990: Section 6.6.1.1.3"
  1845. + ::= { dot1dTpPortEntry 5 }
  1846. +-- The Static (Destination-Address Filtering) Database
  1847. +
  1848. +-- Implementation of this group is optional.
  1849. +
  1850. +dot1dStaticTable OBJECT-TYPE
  1851. + SYNTAX SEQUENCE OF Dot1dStaticEntry
  1852. + ACCESS not-accessible
  1853. + STATUS mandatory
  1854. + DESCRIPTION
  1855. + "A table containing filtering information
  1856. + configured into the bridge by (local or network)
  1857. + management specifying the set of ports to which
  1858. + frames received from specific ports and containing
  1859. + specific destination addresses are allowed to be
  1860. + forwarded. The value of zero in this table as the
  1861. + port number from which frames with a specific
  1862. + destination address are received, is used to
  1863. + specify all ports for which there is no specific
  1864. + entry in this table for that particular
  1865. + destination address. Entries are valid for
  1866. + unicast and for group/broadcast addresses."
  1867. + REFERENCE
  1868. + "IEEE 802.1D-1990: Section 6.7.2"
  1869. + ::= { dot1dStatic 1 }
  1870. +
  1871. +dot1dStaticEntry OBJECT-TYPE
  1872. + SYNTAX Dot1dStaticEntry
  1873. + ACCESS not-accessible
  1874. + STATUS mandatory
  1875. + DESCRIPTION
  1876. + "Filtering information configured into the bridge
  1877. + by (local or network) management specifying the
  1878. + set of ports to which frames received from a
  1879. + specific port and containing a specific
  1880. + destination address are allowed to be forwarded."
  1881. + REFERENCE
  1882. + "IEEE 802.1D-1990: Section 6.7.2"
  1883. + INDEX { dot1dStaticAddress, dot1dStaticReceivePort }
  1884. + ::= { dot1dStaticTable 1 }
  1885. +
  1886. +Dot1dStaticEntry ::=
  1887. + SEQUENCE {
  1888. + dot1dStaticAddress
  1889. + MacAddress,
  1890. + dot1dStaticReceivePort
  1891. + INTEGER,
  1892. + dot1dStaticAllowedToGoTo
  1893. + OCTET STRING,
  1894. + dot1dStaticStatus
  1895. + INTEGER
  1896. + }
  1897. +
  1898. +dot1dStaticAddress OBJECT-TYPE
  1899. + SYNTAX MacAddress
  1900. + ACCESS read-write
  1901. + STATUS mandatory
  1902. + DESCRIPTION
  1903. + "The destination MAC address in a frame to which
  1904. + this entry's filtering information applies. This
  1905. + object can take the value of a unicast address, a
  1906. + group address or the broadcast address."
  1907. + REFERENCE
  1908. + "IEEE 802.1D-1990: Section 3.9.1, 3.9.2"
  1909. + ::= { dot1dStaticEntry 1 }
  1910. +
  1911. +dot1dStaticReceivePort OBJECT-TYPE
  1912. + SYNTAX INTEGER
  1913. + ACCESS read-write
  1914. + STATUS mandatory
  1915. + DESCRIPTION
  1916. + "Either the value '0', or the port number of the
  1917. + port from which a frame must be received in order
  1918. + for this entry's filtering information to apply.
  1919. + A value of zero indicates that this entry applies
  1920. + on all ports of the bridge for which there is no
  1921. + other applicable entry."
  1922. + ::= { dot1dStaticEntry 2 }
  1923. +
  1924. +dot1dStaticAllowedToGoTo OBJECT-TYPE
  1925. + SYNTAX OCTET STRING
  1926. + ACCESS read-write
  1927. + STATUS mandatory
  1928. + DESCRIPTION
  1929. + "The set of ports to which frames received from a
  1930. + specific port and destined for a specific MAC
  1931. +
  1932. + address, are allowed to be forwarded. Each octet
  1933. + within the value of this object specifies a set of
  1934. + eight ports, with the first octet specifying ports
  1935. + 1 through 8, the second octet specifying ports 9
  1936. + through 16, etc. Within each octet, the most
  1937. + significant bit represents the lowest numbered
  1938. + port, and the least significant bit represents the
  1939. + highest numbered port. Thus, each port of the
  1940. + bridge is represented by a single bit within the
  1941. + value of this object. If that bit has a value of
  1942. + '1' then that port is included in the set of
  1943. + ports; the port is not included if its bit has a
  1944. + value of '0'. (Note that the setting of the bit
  1945. + corresponding to the port from which a frame is
  1946. + received is irrelevant.) The default value of
  1947. + this object is a string of ones of appropriate
  1948. + length."
  1949. + ::= { dot1dStaticEntry 3 }
  1950. +
  1951. +dot1dStaticStatus OBJECT-TYPE
  1952. + SYNTAX INTEGER {
  1953. + other(1),
  1954. + invalid(2),
  1955. + permanent(3),
  1956. + deleteOnReset(4),
  1957. + deleteOnTimeout(5)
  1958. + }
  1959. + ACCESS read-write
  1960. + STATUS mandatory
  1961. + DESCRIPTION
  1962. + "This object indicates the status of this entry.
  1963. + The default value is permanent(3).
  1964. + other(1) - this entry is currently in use but
  1965. + the conditions under which it will
  1966. + remain so are different from each of the
  1967. + following values.
  1968. + invalid(2) - writing this value to the object
  1969. + removes the corresponding entry.
  1970. + permanent(3) - this entry is currently in use
  1971. + and will remain so after the next reset
  1972. + of the bridge.
  1973. + deleteOnReset(4) - this entry is currently in
  1974. + use and will remain so until the next
  1975. + reset of the bridge.
  1976. + deleteOnTimeout(5) - this entry is currently
  1977. + in use and will remain so until it is
  1978. + aged out."
  1979. +
  1980. + ::= { dot1dStaticEntry 4 }
  1981. +
  1982. +-- Traps for use by Bridges
  1983. +
  1984. +-- Traps for the Spanning Tree Protocol
  1985. +
  1986. +newRoot TRAP-TYPE
  1987. + ENTERPRISE dot1dBridge
  1988. + DESCRIPTION
  1989. + "The newRoot trap indicates that the sending agent
  1990. + has become the new root of the Spanning Tree; the
  1991. + trap is sent by a bridge soon after its election
  1992. + as the new root, e.g., upon expiration of the
  1993. + Topology Change Timer immediately subsequent to
  1994. + its election. Implementation of this trap is
  1995. + optional."
  1996. + ::= 1
  1997. +
  1998. +topologyChange TRAP-TYPE
  1999. + ENTERPRISE dot1dBridge
  2000. + DESCRIPTION
  2001. + "A topologyChange trap is sent by a bridge when
  2002. + any of its configured ports transitions from the
  2003. + Learning state to the Forwarding state, or from
  2004. + the Forwarding state to the Blocking state. The
  2005. + trap is not sent if a newRoot trap is sent for the
  2006. + same transition. Implementation of this trap is
  2007. + optional."
  2008. + ::= 2
  2009. +
  2010. +END
  2011. --- /dev/null
  2012. +++ b/mibs/GNOME-SMI.txt
  2013. @@ -0,0 +1,88 @@
  2014. +GNOME-SMI DEFINITIONS ::= BEGIN
  2015. +
  2016. +IMPORTS
  2017. + MODULE-IDENTITY,
  2018. + OBJECT-IDENTITY,
  2019. + enterprises
  2020. + FROM SNMPv2-SMI;
  2021. +
  2022. +gnome MODULE-IDENTITY
  2023. + LAST-UPDATED "200709070000Z"
  2024. + ORGANIZATION "GNOME project"
  2025. + CONTACT-INFO
  2026. + "GNU Network Object Model Environment project
  2027. +
  2028. + see http://www.gnome.org for contact persons of a particular
  2029. + area or subproject of GNOME.
  2030. +
  2031. + Administrative contact for MIB module:
  2032. +
  2033. + Jochen Friedrich
  2034. + Ramsaystr. 9
  2035. + 63450 Hanau
  2036. + Germany
  2037. +
  2038. + email: jochen@scram.de"
  2039. + DESCRIPTION
  2040. + "The Structure of GNOME."
  2041. +
  2042. + -- revision history
  2043. +
  2044. + REVISION "200709070000Z" -- Sep 07, 2007
  2045. + DESCRIPTION
  2046. + "Fixed wrong enterprise number (how comes this
  2047. + typo was unnoticed for so long?)."
  2048. +
  2049. + REVISION "200505070000Z" -- May 07, 2005
  2050. + DESCRIPTION
  2051. + "Added gnomeLDAP subtree for LDAP definitions."
  2052. +
  2053. + REVISION "200312070000Z" -- December 07, 2003
  2054. + DESCRIPTION
  2055. + "Added gnomeSysadmin subtree for GNOME project system administration.
  2056. + Updated contact info."
  2057. +
  2058. + REVISION "9809010000Z" -- September 01, 1998
  2059. + DESCRIPTION
  2060. + "Initial version."
  2061. +
  2062. + ::= { enterprises 3319 } -- assigned by IANA
  2063. +
  2064. +gnomeProducts OBJECT-IDENTITY
  2065. + STATUS current
  2066. + DESCRIPTION
  2067. + "gnomeProducts is the root OBJECT IDENTIFIER from
  2068. + which sysObjectID values are assigned."
  2069. + ::= { gnome 1 }
  2070. +
  2071. +gnomeMgmt OBJECT-IDENTITY
  2072. + STATUS current
  2073. + DESCRIPTION
  2074. + "gnomeMgmt defines the subtree for production GNOME related
  2075. + MIB registrations."
  2076. + ::= { gnome 2 }
  2077. +
  2078. +gnomeTest OBJECT-IDENTITY
  2079. + STATUS current
  2080. + DESCRIPTION
  2081. + "gnomeTest defines the subtree for testing GNOME related
  2082. + MIB registrations."
  2083. + ::= { gnome 3 }
  2084. +
  2085. +gnomeSysadmin OBJECT-IDENTITY
  2086. + STATUS current
  2087. + DESCRIPTION
  2088. + "gnomeSysadmin defines the subtree for GNOME related Sysadmin
  2089. + MIB registrations."
  2090. + ::= { gnome 4 }
  2091. +
  2092. +gnomeLDAP OBJECT-IDENTITY
  2093. + STATUS current
  2094. + DESCRIPTION
  2095. + "gnomeLDAP defines the subtree for GNOME related LDAP
  2096. + registrations."
  2097. + ::= { gnome 5 }
  2098. +
  2099. +-- more to come if necessary.
  2100. +
  2101. +END
  2102. --- /dev/null
  2103. +++ b/mibs/OSPF-MIB.txt
  2104. @@ -0,0 +1,2723 @@
  2105. +OSPF-MIB DEFINITIONS ::= BEGIN
  2106. +
  2107. + IMPORTS
  2108. + MODULE-IDENTITY, OBJECT-TYPE, Counter32, Gauge32,
  2109. + Integer32, IpAddress
  2110. + FROM SNMPv2-SMI
  2111. + TEXTUAL-CONVENTION, TruthValue, RowStatus
  2112. + FROM SNMPv2-TC
  2113. + MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
  2114. + mib-2 FROM RFC1213-MIB;
  2115. +
  2116. +-- This MIB module uses the extended OBJECT-TYPE macro as
  2117. +-- defined in [9].
  2118. +
  2119. +ospf MODULE-IDENTITY
  2120. + LAST-UPDATED "9501201225Z" -- Fri Jan 20 12:25:50 PST 1995
  2121. + ORGANIZATION "IETF OSPF Working Group"
  2122. + CONTACT-INFO
  2123. + " Fred Baker
  2124. + Postal: Cisco Systems
  2125. + 519 Lado Drive
  2126. + Santa Barbara, California 93111
  2127. + Tel: +1 805 681 0115
  2128. + E-Mail: fred@cisco.com
  2129. +
  2130. + Rob Coltun
  2131. + Postal: RainbowBridge Communications
  2132. + Tel: (301) 340-9416
  2133. + E-Mail: rcoltun@rainbow-bridge.com"
  2134. + DESCRIPTION
  2135. + "The MIB module to describe the OSPF Version 2
  2136. + Protocol"
  2137. + ::= { mib-2 14 }
  2138. +
  2139. +-- The Area ID, in OSPF, has the same format as an IP Address,
  2140. +-- but has the function of defining a summarization point for
  2141. +-- Link State Advertisements
  2142. +
  2143. +AreaID ::= TEXTUAL-CONVENTION
  2144. + STATUS current
  2145. + DESCRIPTION
  2146. + "An OSPF Area Identifier."
  2147. + SYNTAX IpAddress
  2148. +
  2149. +
  2150. +-- The Router ID, in OSPF, has the same format as an IP Address,
  2151. +-- but identifies the router independent of its IP Address.
  2152. +
  2153. +RouterID ::= TEXTUAL-CONVENTION
  2154. + STATUS current
  2155. + DESCRIPTION
  2156. + "A OSPF Router Identifier."
  2157. + SYNTAX IpAddress
  2158. +
  2159. +
  2160. +-- The OSPF Metric is defined as an unsigned value in the range
  2161. +
  2162. +Metric ::= TEXTUAL-CONVENTION
  2163. + STATUS current
  2164. + DESCRIPTION
  2165. + "The OSPF Internal Metric."
  2166. + SYNTAX Integer32 (0..'FFFF'h)
  2167. +
  2168. +BigMetric ::= TEXTUAL-CONVENTION
  2169. + STATUS current
  2170. + DESCRIPTION
  2171. + "The OSPF External Metric."
  2172. + SYNTAX Integer32 (0..'FFFFFF'h)
  2173. +
  2174. +-- Status Values
  2175. +
  2176. +Status ::= TEXTUAL-CONVENTION
  2177. + STATUS current
  2178. + DESCRIPTION
  2179. + "The status of an interface: 'enabled' indicates that
  2180. + it is willing to communicate with other OSPF Routers,
  2181. + while 'disabled' indicates that it is not."
  2182. + SYNTAX INTEGER { enabled (1), disabled (2) }
  2183. +
  2184. +-- Time Durations measured in seconds
  2185. +
  2186. +PositiveInteger ::= TEXTUAL-CONVENTION
  2187. + STATUS current
  2188. + DESCRIPTION
  2189. + "A positive integer. Values in excess are precluded as
  2190. + unnecessary and prone to interoperability issues."
  2191. + SYNTAX Integer32 (0..'7FFFFFFF'h)
  2192. +
  2193. +HelloRange ::= TEXTUAL-CONVENTION
  2194. + STATUS current
  2195. + DESCRIPTION
  2196. + "The range of intervals on which hello messages are
  2197. + exchanged."
  2198. + SYNTAX Integer32 (1..'FFFF'h)
  2199. +
  2200. +UpToMaxAge ::= TEXTUAL-CONVENTION
  2201. + STATUS current
  2202. + DESCRIPTION
  2203. + "The values that one might find or configure for
  2204. + variables bounded by the maximum age of an LSA."
  2205. + SYNTAX Integer32 (0..3600)
  2206. +
  2207. +
  2208. +-- The range of ifIndex
  2209. +
  2210. +InterfaceIndex ::= TEXTUAL-CONVENTION
  2211. + STATUS current
  2212. + DESCRIPTION
  2213. + "The range of ifIndex."
  2214. + SYNTAX Integer32
  2215. +
  2216. +
  2217. +-- Potential Priorities for the Designated Router Election
  2218. +
  2219. +DesignatedRouterPriority ::= TEXTUAL-CONVENTION
  2220. + STATUS current
  2221. + DESCRIPTION
  2222. + "The values defined for the priority of a system for
  2223. + becoming the designated router."
  2224. + SYNTAX Integer32 (0..'FF'h)
  2225. +
  2226. +TOSType ::= TEXTUAL-CONVENTION
  2227. + STATUS current
  2228. + DESCRIPTION
  2229. + "Type of Service is defined as a mapping to the IP Type of
  2230. + Service Flags as defined in the IP Forwarding Table MIB
  2231. +
  2232. + +-----+-----+-----+-----+-----+-----+-----+-----+
  2233. + | | | |
  2234. + | PRECEDENCE | TYPE OF SERVICE | 0 |
  2235. + | | | |
  2236. + +-----+-----+-----+-----+-----+-----+-----+-----+
  2237. +
  2238. + IP TOS IP TOS
  2239. + Field Policy Field Policy
  2240. +
  2241. + Contents Code Contents Code
  2242. + 0 0 0 0 ==> 0 0 0 0 1 ==> 2
  2243. + 0 0 1 0 ==> 4 0 0 1 1 ==> 6
  2244. + 0 1 0 0 ==> 8 0 1 0 1 ==> 10
  2245. + 0 1 1 0 ==> 12 0 1 1 1 ==> 14
  2246. + 1 0 0 0 ==> 16 1 0 0 1 ==> 18
  2247. + 1 0 1 0 ==> 20 1 0 1 1 ==> 22
  2248. + 1 1 0 0 ==> 24 1 1 0 1 ==> 26
  2249. + 1 1 1 0 ==> 28 1 1 1 1 ==> 30
  2250. +
  2251. + The remaining values are left for future definition."
  2252. + SYNTAX Integer32 (0..30)
  2253. +
  2254. +
  2255. +-- OSPF General Variables
  2256. +
  2257. +-- These parameters apply globally to the Router's
  2258. +-- OSPF Process.
  2259. +
  2260. +ospfGeneralGroup OBJECT IDENTIFIER ::= { ospf 1 }
  2261. +
  2262. +
  2263. + ospfRouterId OBJECT-TYPE
  2264. + SYNTAX RouterID
  2265. + MAX-ACCESS read-write
  2266. + STATUS current
  2267. + DESCRIPTION
  2268. + "A 32-bit integer uniquely identifying the
  2269. + router in the Autonomous System.
  2270. +
  2271. + By convention, to ensure uniqueness, this
  2272. + should default to the value of one of the
  2273. + router's IP interface addresses."
  2274. + REFERENCE
  2275. + "OSPF Version 2, C.1 Global parameters"
  2276. + ::= { ospfGeneralGroup 1 }
  2277. +
  2278. +
  2279. + ospfAdminStat OBJECT-TYPE
  2280. + SYNTAX Status
  2281. + MAX-ACCESS read-write
  2282. + STATUS current
  2283. + DESCRIPTION
  2284. + "The administrative status of OSPF in the
  2285. + router. The value 'enabled' denotes that the
  2286. + OSPF Process is active on at least one inter-
  2287. + face; 'disabled' disables it on all inter-
  2288. + faces."
  2289. + ::= { ospfGeneralGroup 2 }
  2290. +
  2291. + ospfVersionNumber OBJECT-TYPE
  2292. + SYNTAX INTEGER { version2 (2) }
  2293. + MAX-ACCESS read-only
  2294. + STATUS current
  2295. + DESCRIPTION
  2296. + "The current version number of the OSPF proto-
  2297. + col is 2."
  2298. + REFERENCE
  2299. + "OSPF Version 2, Title"
  2300. + ::= { ospfGeneralGroup 3 }
  2301. +
  2302. +
  2303. + ospfAreaBdrRtrStatus OBJECT-TYPE
  2304. + SYNTAX TruthValue
  2305. + MAX-ACCESS read-only
  2306. + STATUS current
  2307. + DESCRIPTION
  2308. + "A flag to note whether this router is an area
  2309. + border router."
  2310. + REFERENCE
  2311. + "OSPF Version 2, Section 3 Splitting the AS into
  2312. + Areas"
  2313. + ::= { ospfGeneralGroup 4 }
  2314. +
  2315. +
  2316. + ospfASBdrRtrStatus OBJECT-TYPE
  2317. + SYNTAX TruthValue
  2318. + MAX-ACCESS read-write
  2319. + STATUS current
  2320. + DESCRIPTION
  2321. + "A flag to note whether this router is config-
  2322. + ured as an Autonomous System border router."
  2323. + REFERENCE
  2324. + "OSPF Version 2, Section 3.3 Classification of
  2325. + routers"
  2326. + ::= { ospfGeneralGroup 5 }
  2327. +
  2328. + ospfExternLsaCount OBJECT-TYPE
  2329. + SYNTAX Gauge32
  2330. + MAX-ACCESS read-only
  2331. + STATUS current
  2332. + DESCRIPTION
  2333. + "The number of external (LS type 5) link-state
  2334. + advertisements in the link-state database."
  2335. + REFERENCE
  2336. + "OSPF Version 2, Appendix A.4.5 AS external link
  2337. + advertisements"
  2338. + ::= { ospfGeneralGroup 6 }
  2339. +
  2340. +
  2341. + ospfExternLsaCksumSum OBJECT-TYPE
  2342. + SYNTAX Integer32
  2343. + MAX-ACCESS read-only
  2344. + STATUS current
  2345. + DESCRIPTION
  2346. + "The 32-bit unsigned sum of the LS checksums of
  2347. + the external link-state advertisements con-
  2348. + tained in the link-state database. This sum
  2349. + can be used to determine if there has been a
  2350. + change in a router's link state database, and
  2351. + to compare the link-state database of two
  2352. + routers."
  2353. + ::= { ospfGeneralGroup 7 }
  2354. +
  2355. +
  2356. + ospfTOSSupport OBJECT-TYPE
  2357. + SYNTAX TruthValue
  2358. + MAX-ACCESS read-write
  2359. + STATUS current
  2360. + DESCRIPTION
  2361. + "The router's support for type-of-service rout-
  2362. + ing."
  2363. + REFERENCE
  2364. + "OSPF Version 2, Appendix F.1.2 Optional TOS
  2365. + support"
  2366. + ::= { ospfGeneralGroup 8 }
  2367. +
  2368. + ospfOriginateNewLsas OBJECT-TYPE
  2369. + SYNTAX Counter32
  2370. + MAX-ACCESS read-only
  2371. + STATUS current
  2372. + DESCRIPTION
  2373. + "The number of new link-state advertisements
  2374. + that have been originated. This number is in-
  2375. + cremented each time the router originates a new
  2376. + LSA."
  2377. + ::= { ospfGeneralGroup 9 }
  2378. +
  2379. +
  2380. + ospfRxNewLsas OBJECT-TYPE
  2381. + SYNTAX Counter32
  2382. + MAX-ACCESS read-only
  2383. + STATUS current
  2384. + DESCRIPTION
  2385. + "The number of link-state advertisements re-
  2386. + ceived determined to be new instantiations.
  2387. + This number does not include newer instantia-
  2388. + tions of self-originated link-state advertise-
  2389. + ments."
  2390. + ::= { ospfGeneralGroup 10 }
  2391. +
  2392. + ospfExtLsdbLimit OBJECT-TYPE
  2393. + SYNTAX Integer32 (-1..'7FFFFFFF'h)
  2394. + MAX-ACCESS read-write
  2395. + STATUS current
  2396. + DESCRIPTION
  2397. + "The maximum number of non-default AS-
  2398. + external-LSAs entries that can be stored in the
  2399. + link-state database. If the value is -1, then
  2400. + there is no limit.
  2401. +
  2402. + When the number of non-default AS-external-LSAs
  2403. + in a router's link-state database reaches
  2404. + ospfExtLsdbLimit, the router enters Overflow-
  2405. + State. The router never holds more than
  2406. + ospfExtLsdbLimit non-default AS-external-LSAs
  2407. + in its database. OspfExtLsdbLimit MUST be set
  2408. + identically in all routers attached to the OSPF
  2409. + backbone and/or any regular OSPF area. (i.e.,
  2410. + OSPF stub areas and NSSAs are excluded)."
  2411. + DEFVAL { -1 }
  2412. + ::= { ospfGeneralGroup 11 }
  2413. +
  2414. + ospfMulticastExtensions OBJECT-TYPE
  2415. + SYNTAX Integer32
  2416. + MAX-ACCESS read-write
  2417. + STATUS current
  2418. + DESCRIPTION
  2419. + "A Bit Mask indicating whether the router is
  2420. + forwarding IP multicast (Class D) datagrams
  2421. + based on the algorithms defined in the Multi-
  2422. + cast Extensions to OSPF.
  2423. +
  2424. + Bit 0, if set, indicates that the router can
  2425. + forward IP multicast datagrams in the router's
  2426. + directly attached areas (called intra-area mul-
  2427. + ticast routing).
  2428. +
  2429. + Bit 1, if set, indicates that the router can
  2430. + forward IP multicast datagrams between OSPF
  2431. + areas (called inter-area multicast routing).
  2432. +
  2433. + Bit 2, if set, indicates that the router can
  2434. + forward IP multicast datagrams between Auto-
  2435. + nomous Systems (called inter-AS multicast rout-
  2436. + ing).
  2437. +
  2438. + Only certain combinations of bit settings are
  2439. + allowed, namely: 0 (no multicast forwarding is
  2440. + enabled), 1 (intra-area multicasting only), 3
  2441. + (intra-area and inter-area multicasting), 5
  2442. + (intra-area and inter-AS multicasting) and 7
  2443. + (multicasting everywhere). By default, no mul-
  2444. + ticast forwarding is enabled."
  2445. + DEFVAL { 0 }
  2446. + ::= { ospfGeneralGroup 12 }
  2447. +
  2448. + ospfExitOverflowInterval OBJECT-TYPE
  2449. + SYNTAX PositiveInteger
  2450. + MAX-ACCESS read-write
  2451. + STATUS current
  2452. + DESCRIPTION
  2453. + "The number of seconds that, after entering
  2454. + OverflowState, a router will attempt to leave
  2455. + OverflowState. This allows the router to again
  2456. + originate non-default AS-external-LSAs. When
  2457. + set to 0, the router will not leave Overflow-
  2458. + State until restarted."
  2459. + DEFVAL { 0 }
  2460. + ::= { ospfGeneralGroup 13 }
  2461. +
  2462. +
  2463. + ospfDemandExtensions OBJECT-TYPE
  2464. + SYNTAX TruthValue
  2465. + MAX-ACCESS read-write
  2466. + STATUS current
  2467. + DESCRIPTION
  2468. + "The router's support for demand routing."
  2469. + REFERENCE
  2470. + "OSPF Version 2, Appendix on Demand Routing"
  2471. + ::= { ospfGeneralGroup 14 }
  2472. +
  2473. +
  2474. +-- The OSPF Area Data Structure contains information
  2475. +-- regarding the various areas. The interfaces and
  2476. +-- virtual links are configured as part of these areas.
  2477. +-- Area 0.0.0.0, by definition, is the Backbone Area
  2478. +
  2479. +
  2480. + ospfAreaTable OBJECT-TYPE
  2481. + SYNTAX SEQUENCE OF OspfAreaEntry
  2482. + MAX-ACCESS not-accessible
  2483. + STATUS current
  2484. + DESCRIPTION
  2485. + "Information describing the configured parame-
  2486. + ters and cumulative statistics of the router's
  2487. + attached areas."
  2488. + REFERENCE
  2489. + "OSPF Version 2, Section 6 The Area Data Struc-
  2490. + ture"
  2491. + ::= { ospf 2 }
  2492. +
  2493. +
  2494. + ospfAreaEntry OBJECT-TYPE
  2495. + SYNTAX OspfAreaEntry
  2496. + MAX-ACCESS not-accessible
  2497. + STATUS current
  2498. + DESCRIPTION
  2499. + "Information describing the configured parame-
  2500. + ters and cumulative statistics of one of the
  2501. + router's attached areas."
  2502. + INDEX { ospfAreaId }
  2503. + ::= { ospfAreaTable 1 }
  2504. +
  2505. +OspfAreaEntry ::=
  2506. + SEQUENCE {
  2507. + ospfAreaId
  2508. + AreaID,
  2509. + ospfAuthType
  2510. + Integer32,
  2511. + ospfImportAsExtern
  2512. + INTEGER,
  2513. + ospfSpfRuns
  2514. + Counter32,
  2515. + ospfAreaBdrRtrCount
  2516. + Gauge32,
  2517. + ospfAsBdrRtrCount
  2518. + Gauge32,
  2519. + ospfAreaLsaCount
  2520. + Gauge32,
  2521. + ospfAreaLsaCksumSum
  2522. + Integer32,
  2523. + ospfAreaSummary
  2524. + INTEGER,
  2525. + ospfAreaStatus
  2526. + RowStatus
  2527. + }
  2528. +
  2529. + ospfAreaId OBJECT-TYPE
  2530. + SYNTAX AreaID
  2531. + MAX-ACCESS read-only
  2532. + STATUS current
  2533. + DESCRIPTION
  2534. + "A 32-bit integer uniquely identifying an area.
  2535. + Area ID 0.0.0.0 is used for the OSPF backbone."
  2536. + REFERENCE
  2537. + "OSPF Version 2, Appendix C.2 Area parameters"
  2538. + ::= { ospfAreaEntry 1 }
  2539. +
  2540. +
  2541. + ospfAuthType OBJECT-TYPE
  2542. + SYNTAX Integer32
  2543. + -- none (0),
  2544. + -- simplePassword (1)
  2545. + -- md5 (2)
  2546. + -- reserved for specification by IANA (> 2)
  2547. + MAX-ACCESS read-create
  2548. + STATUS obsolete
  2549. + DESCRIPTION
  2550. + "The authentication type specified for an area.
  2551. + Additional authentication types may be assigned
  2552. + locally on a per Area basis."
  2553. + REFERENCE
  2554. + "OSPF Version 2, Appendix E Authentication"
  2555. + DEFVAL { 0 } -- no authentication, by default
  2556. + ::= { ospfAreaEntry 2 }
  2557. +
  2558. + ospfImportAsExtern OBJECT-TYPE
  2559. + SYNTAX INTEGER {
  2560. + importExternal (1),
  2561. + importNoExternal (2),
  2562. + importNssa (3)
  2563. + }
  2564. + MAX-ACCESS read-create
  2565. + STATUS current
  2566. + DESCRIPTION
  2567. + "The area's support for importing AS external
  2568. + link- state advertisements."
  2569. + REFERENCE
  2570. + "OSPF Version 2, Appendix C.2 Area parameters"
  2571. + DEFVAL { importExternal }
  2572. + ::= { ospfAreaEntry 3 }
  2573. +
  2574. +
  2575. + ospfSpfRuns OBJECT-TYPE
  2576. + SYNTAX Counter32
  2577. + MAX-ACCESS read-only
  2578. + STATUS current
  2579. + DESCRIPTION
  2580. + "The number of times that the intra-area route
  2581. + table has been calculated using this area's
  2582. + link-state database. This is typically done
  2583. + using Dijkstra's algorithm."
  2584. + ::= { ospfAreaEntry 4 }
  2585. +
  2586. +
  2587. + ospfAreaBdrRtrCount OBJECT-TYPE
  2588. + SYNTAX Gauge32
  2589. + MAX-ACCESS read-only
  2590. + STATUS current
  2591. + DESCRIPTION
  2592. + "The total number of area border routers reach-
  2593. + able within this area. This is initially zero,
  2594. + and is calculated in each SPF Pass."
  2595. + ::= { ospfAreaEntry 5 }
  2596. +
  2597. + ospfAsBdrRtrCount OBJECT-TYPE
  2598. + SYNTAX Gauge32
  2599. + MAX-ACCESS read-only
  2600. + STATUS current
  2601. + DESCRIPTION
  2602. + "The total number of Autonomous System border
  2603. + routers reachable within this area. This is
  2604. + initially zero, and is calculated in each SPF
  2605. + Pass."
  2606. + ::= { ospfAreaEntry 6 }
  2607. +
  2608. +
  2609. + ospfAreaLsaCount OBJECT-TYPE
  2610. + SYNTAX Gauge32
  2611. + MAX-ACCESS read-only
  2612. + STATUS current
  2613. + DESCRIPTION
  2614. + "The total number of link-state advertisements
  2615. + in this area's link-state database, excluding
  2616. + AS External LSA's."
  2617. + ::= { ospfAreaEntry 7 }
  2618. +
  2619. +
  2620. + ospfAreaLsaCksumSum OBJECT-TYPE
  2621. + SYNTAX Integer32
  2622. + MAX-ACCESS read-only
  2623. + STATUS current
  2624. + DESCRIPTION
  2625. + "The 32-bit unsigned sum of the link-state ad-
  2626. + vertisements' LS checksums contained in this
  2627. + area's link-state database. This sum excludes
  2628. + external (LS type 5) link-state advertisements.
  2629. + The sum can be used to determine if there has
  2630. + been a change in a router's link state data-
  2631. + base, and to compare the link-state database of
  2632. + two routers."
  2633. + DEFVAL { 0 }
  2634. + ::= { ospfAreaEntry 8 }
  2635. +
  2636. + ospfAreaSummary OBJECT-TYPE
  2637. + SYNTAX INTEGER {
  2638. + noAreaSummary (1),
  2639. + sendAreaSummary (2)
  2640. + }
  2641. + MAX-ACCESS read-create
  2642. + STATUS current
  2643. + DESCRIPTION
  2644. + "The variable ospfAreaSummary controls the im-
  2645. + port of summary LSAs into stub areas. It has
  2646. + no effect on other areas.
  2647. +
  2648. + If it is noAreaSummary, the router will neither
  2649. + originate nor propagate summary LSAs into the
  2650. + stub area. It will rely entirely on its de-
  2651. + fault route.
  2652. +
  2653. + If it is sendAreaSummary, the router will both
  2654. + summarize and propagate summary LSAs."
  2655. + DEFVAL { noAreaSummary }
  2656. + ::= { ospfAreaEntry 9 }
  2657. +
  2658. +
  2659. + ospfAreaStatus OBJECT-TYPE
  2660. + SYNTAX RowStatus
  2661. + MAX-ACCESS read-create
  2662. + STATUS current
  2663. + DESCRIPTION
  2664. + "This variable displays the status of the en-
  2665. + try. Setting it to 'invalid' has the effect of
  2666. + rendering it inoperative. The internal effect
  2667. + (row removal) is implementation dependent."
  2668. + ::= { ospfAreaEntry 10 }
  2669. +
  2670. +
  2671. +-- OSPF Area Default Metric Table
  2672. +
  2673. +-- The OSPF Area Default Metric Table describes the metrics
  2674. +-- that a default Area Border Router will advertise into a
  2675. +-- Stub area.
  2676. +
  2677. +
  2678. + ospfStubAreaTable OBJECT-TYPE
  2679. + SYNTAX SEQUENCE OF OspfStubAreaEntry
  2680. + MAX-ACCESS not-accessible
  2681. + STATUS current
  2682. + DESCRIPTION
  2683. + "The set of metrics that will be advertised by
  2684. + a default Area Border Router into a stub area."
  2685. + REFERENCE
  2686. + "OSPF Version 2, Appendix C.2, Area Parameters"
  2687. + ::= { ospf 3 }
  2688. +
  2689. +
  2690. + ospfStubAreaEntry OBJECT-TYPE
  2691. + SYNTAX OspfStubAreaEntry
  2692. + MAX-ACCESS not-accessible
  2693. + STATUS current
  2694. + DESCRIPTION
  2695. + "The metric for a given Type of Service that
  2696. + will be advertised by a default Area Border
  2697. + Router into a stub area."
  2698. + REFERENCE
  2699. + "OSPF Version 2, Appendix C.2, Area Parameters"
  2700. + INDEX { ospfStubAreaId, ospfStubTOS }
  2701. + ::= { ospfStubAreaTable 1 }
  2702. +
  2703. +OspfStubAreaEntry ::=
  2704. + SEQUENCE {
  2705. + ospfStubAreaId
  2706. + AreaID,
  2707. + ospfStubTOS
  2708. + TOSType,
  2709. + ospfStubMetric
  2710. + BigMetric,
  2711. + ospfStubStatus
  2712. + RowStatus,
  2713. + ospfStubMetricType
  2714. + INTEGER
  2715. + }
  2716. +
  2717. + ospfStubAreaId OBJECT-TYPE
  2718. + SYNTAX AreaID
  2719. + MAX-ACCESS read-only
  2720. + STATUS current
  2721. + DESCRIPTION
  2722. + "The 32 bit identifier for the Stub Area. On
  2723. + creation, this can be derived from the in-
  2724. + stance."
  2725. + ::= { ospfStubAreaEntry 1 }
  2726. +
  2727. +
  2728. + ospfStubTOS OBJECT-TYPE
  2729. + SYNTAX TOSType
  2730. + MAX-ACCESS read-only
  2731. + STATUS current
  2732. + DESCRIPTION
  2733. + "The Type of Service associated with the
  2734. + metric. On creation, this can be derived from
  2735. + the instance."
  2736. + ::= { ospfStubAreaEntry 2 }
  2737. +
  2738. +
  2739. + ospfStubMetric OBJECT-TYPE
  2740. + SYNTAX BigMetric
  2741. + MAX-ACCESS read-create
  2742. + STATUS current
  2743. + DESCRIPTION
  2744. + "The metric value applied at the indicated type
  2745. + of service. By default, this equals the least
  2746. + metric at the type of service among the inter-
  2747. + faces to other areas."
  2748. + ::= { ospfStubAreaEntry 3 }
  2749. +
  2750. +
  2751. + ospfStubStatus OBJECT-TYPE
  2752. + SYNTAX RowStatus
  2753. + MAX-ACCESS read-create
  2754. + STATUS current
  2755. + DESCRIPTION
  2756. + "This variable displays the status of the en-
  2757. + try. Setting it to 'invalid' has the effect of
  2758. + rendering it inoperative. The internal effect
  2759. + (row removal) is implementation dependent."
  2760. + ::= { ospfStubAreaEntry 4 }
  2761. +
  2762. + ospfStubMetricType OBJECT-TYPE
  2763. + SYNTAX INTEGER {
  2764. + ospfMetric (1), -- OSPF Metric
  2765. + comparableCost (2), -- external type 1
  2766. + nonComparable (3) -- external type 2
  2767. + }
  2768. + MAX-ACCESS read-create
  2769. + STATUS current
  2770. + DESCRIPTION
  2771. + "This variable displays the type of metric ad-
  2772. + vertised as a default route."
  2773. + DEFVAL { ospfMetric }
  2774. + ::= { ospfStubAreaEntry 5 }
  2775. +
  2776. +-- OSPF Link State Database
  2777. +
  2778. +-- The Link State Database contains the Link State
  2779. +-- Advertisements from throughout the areas that the
  2780. +-- device is attached to.
  2781. +
  2782. +
  2783. + ospfLsdbTable OBJECT-TYPE
  2784. + SYNTAX SEQUENCE OF OspfLsdbEntry
  2785. + MAX-ACCESS not-accessible
  2786. + STATUS current
  2787. + DESCRIPTION
  2788. + "The OSPF Process's Link State Database."
  2789. + REFERENCE
  2790. + "OSPF Version 2, Section 12 Link State Adver-
  2791. + tisements"
  2792. + ::= { ospf 4 }
  2793. +
  2794. +
  2795. + ospfLsdbEntry OBJECT-TYPE
  2796. + SYNTAX OspfLsdbEntry
  2797. + MAX-ACCESS not-accessible
  2798. + STATUS current
  2799. + DESCRIPTION
  2800. + "A single Link State Advertisement."
  2801. + INDEX { ospfLsdbAreaId, ospfLsdbType,
  2802. + ospfLsdbLsid, ospfLsdbRouterId }
  2803. + ::= { ospfLsdbTable 1 }
  2804. +
  2805. +OspfLsdbEntry ::=
  2806. + SEQUENCE {
  2807. + ospfLsdbAreaId
  2808. + AreaID,
  2809. + ospfLsdbType
  2810. + INTEGER,
  2811. + ospfLsdbLsid
  2812. + IpAddress,
  2813. + ospfLsdbRouterId
  2814. + RouterID,
  2815. + ospfLsdbSequence
  2816. + Integer32,
  2817. + ospfLsdbAge
  2818. + Integer32,
  2819. + ospfLsdbChecksum
  2820. + Integer32,
  2821. + ospfLsdbAdvertisement
  2822. + OCTET STRING
  2823. + }
  2824. + ospfLsdbAreaId OBJECT-TYPE
  2825. + SYNTAX AreaID
  2826. + MAX-ACCESS read-only
  2827. + STATUS current
  2828. + DESCRIPTION
  2829. + "The 32 bit identifier of the Area from which
  2830. + the LSA was received."
  2831. + REFERENCE
  2832. + "OSPF Version 2, Appendix C.2 Area parameters"
  2833. + ::= { ospfLsdbEntry 1 }
  2834. +
  2835. +-- External Link State Advertisements are permitted
  2836. +-- for backward compatibility, but should be displayed in
  2837. +-- the ospfExtLsdbTable rather than here.
  2838. +
  2839. + ospfLsdbType OBJECT-TYPE
  2840. + SYNTAX INTEGER {
  2841. + routerLink (1),
  2842. + networkLink (2),
  2843. + summaryLink (3),
  2844. + asSummaryLink (4),
  2845. + asExternalLink (5), -- but see ospfExtLsdbTable
  2846. + multicastLink (6),
  2847. + nssaExternalLink (7)
  2848. + }
  2849. + MAX-ACCESS read-only
  2850. + STATUS current
  2851. + DESCRIPTION
  2852. + "The type of the link state advertisement.
  2853. + Each link state type has a separate advertise-
  2854. + ment format."
  2855. + REFERENCE
  2856. + "OSPF Version 2, Appendix A.4.1 The Link State
  2857. + Advertisement header"
  2858. + ::= { ospfLsdbEntry 2 }
  2859. +
  2860. + ospfLsdbLsid OBJECT-TYPE
  2861. + SYNTAX IpAddress
  2862. + MAX-ACCESS read-only
  2863. + STATUS current
  2864. + DESCRIPTION
  2865. + "The Link State ID is an LS Type Specific field
  2866. + containing either a Router ID or an IP Address;
  2867. + it identifies the piece of the routing domain
  2868. + that is being described by the advertisement."
  2869. + REFERENCE
  2870. + "OSPF Version 2, Section 12.1.4 Link State ID"
  2871. + ::= { ospfLsdbEntry 3 }
  2872. + ospfLsdbRouterId OBJECT-TYPE
  2873. + SYNTAX RouterID
  2874. + MAX-ACCESS read-only
  2875. + STATUS current
  2876. + DESCRIPTION
  2877. + "The 32 bit number that uniquely identifies the
  2878. + originating router in the Autonomous System."
  2879. + REFERENCE
  2880. + "OSPF Version 2, Appendix C.1 Global parameters"
  2881. + ::= { ospfLsdbEntry 4 }
  2882. +
  2883. +-- Note that the OSPF Sequence Number is a 32 bit signed
  2884. +-- integer. It starts with the value '80000001'h,
  2885. +-- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h
  2886. +-- Thus, a typical sequence number will be very negative.
  2887. +
  2888. + ospfLsdbSequence OBJECT-TYPE
  2889. + SYNTAX Integer32
  2890. + MAX-ACCESS read-only
  2891. + STATUS current
  2892. + DESCRIPTION
  2893. + "The sequence number field is a signed 32-bit
  2894. + integer. It is used to detect old and dupli-
  2895. + cate link state advertisements. The space of
  2896. + sequence numbers is linearly ordered. The
  2897. + larger the sequence number the more recent the
  2898. + advertisement."
  2899. + REFERENCE
  2900. + "OSPF Version 2, Section 12.1.6 LS sequence
  2901. + number"
  2902. + ::= { ospfLsdbEntry 5 }
  2903. +
  2904. +
  2905. + ospfLsdbAge OBJECT-TYPE
  2906. + SYNTAX Integer32 -- Should be 0..MaxAge
  2907. + MAX-ACCESS read-only
  2908. + STATUS current
  2909. + DESCRIPTION
  2910. + "This field is the age of the link state adver-
  2911. + tisement in seconds."
  2912. + REFERENCE
  2913. + "OSPF Version 2, Section 12.1.1 LS age"
  2914. + ::= { ospfLsdbEntry 6 }
  2915. +
  2916. + ospfLsdbChecksum OBJECT-TYPE
  2917. + SYNTAX Integer32
  2918. + MAX-ACCESS read-only
  2919. + STATUS current
  2920. + DESCRIPTION
  2921. + "This field is the checksum of the complete
  2922. + contents of the advertisement, excepting the
  2923. + age field. The age field is excepted so that
  2924. + an advertisement's age can be incremented
  2925. + without updating the checksum. The checksum
  2926. + used is the same that is used for ISO connec-
  2927. + tionless datagrams; it is commonly referred to
  2928. + as the Fletcher checksum."
  2929. + REFERENCE
  2930. + "OSPF Version 2, Section 12.1.7 LS checksum"
  2931. + ::= { ospfLsdbEntry 7 }
  2932. +
  2933. +
  2934. + ospfLsdbAdvertisement OBJECT-TYPE
  2935. + SYNTAX OCTET STRING (SIZE (1..65535))
  2936. + MAX-ACCESS read-only
  2937. + STATUS current
  2938. + DESCRIPTION
  2939. + "The entire Link State Advertisement, including
  2940. + its header."
  2941. + REFERENCE
  2942. + "OSPF Version 2, Section 12 Link State Adver-
  2943. + tisements"
  2944. + ::= { ospfLsdbEntry 8 }
  2945. +
  2946. +
  2947. +-- Address Range Table
  2948. +
  2949. +-- The Address Range Table acts as an adjunct to the Area
  2950. +-- Table; It describes those Address Range Summaries that
  2951. +-- are configured to be propagated from an Area to reduce
  2952. +-- the amount of information about it which is known beyond
  2953. +-- its borders.
  2954. +
  2955. + ospfAreaRangeTable OBJECT-TYPE
  2956. + SYNTAX SEQUENCE OF OspfAreaRangeEntry
  2957. + MAX-ACCESS not-accessible
  2958. + STATUS obsolete
  2959. + DESCRIPTION
  2960. + "A range if IP addresses specified by an IP
  2961. + address/IP network mask pair. For example,
  2962. + class B address range of X.X.X.X with a network
  2963. + mask of 255.255.0.0 includes all IP addresses
  2964. + from X.X.0.0 to X.X.255.255"
  2965. + REFERENCE
  2966. + "OSPF Version 2, Appendix C.2 Area parameters"
  2967. + ::= { ospf 5 }
  2968. + ospfAreaRangeEntry OBJECT-TYPE
  2969. + SYNTAX OspfAreaRangeEntry
  2970. + MAX-ACCESS not-accessible
  2971. + STATUS obsolete
  2972. + DESCRIPTION
  2973. + "A range if IP addresses specified by an IP
  2974. + address/IP network mask pair. For example,
  2975. + class B address range of X.X.X.X with a network
  2976. + mask of 255.255.0.0 includes all IP addresses
  2977. + from X.X.0.0 to X.X.255.255"
  2978. + REFERENCE
  2979. + "OSPF Version 2, Appendix C.2 Area parameters"
  2980. + INDEX { ospfAreaRangeAreaId, ospfAreaRangeNet }
  2981. + ::= { ospfAreaRangeTable 1 }
  2982. +
  2983. +OspfAreaRangeEntry ::=
  2984. + SEQUENCE {
  2985. + ospfAreaRangeAreaId
  2986. + AreaID,
  2987. + ospfAreaRangeNet
  2988. + IpAddress,
  2989. + ospfAreaRangeMask
  2990. + IpAddress,
  2991. + ospfAreaRangeStatus
  2992. + RowStatus,
  2993. + ospfAreaRangeEffect
  2994. + INTEGER
  2995. + }
  2996. +
  2997. + ospfAreaRangeAreaId OBJECT-TYPE
  2998. + SYNTAX AreaID
  2999. + MAX-ACCESS read-only
  3000. + STATUS obsolete
  3001. + DESCRIPTION
  3002. + "The Area the Address Range is to be found
  3003. + within."
  3004. + REFERENCE
  3005. + "OSPF Version 2, Appendix C.2 Area parameters"
  3006. + ::= { ospfAreaRangeEntry 1 }
  3007. +
  3008. +
  3009. + ospfAreaRangeNet OBJECT-TYPE
  3010. + SYNTAX IpAddress
  3011. + MAX-ACCESS read-only
  3012. + STATUS obsolete
  3013. + DESCRIPTION
  3014. + "The IP Address of the Net or Subnet indicated
  3015. + by the range."
  3016. + REFERENCE
  3017. + "OSPF Version 2, Appendix C.2 Area parameters"
  3018. + ::= { ospfAreaRangeEntry 2 }
  3019. +
  3020. +
  3021. + ospfAreaRangeMask OBJECT-TYPE
  3022. + SYNTAX IpAddress
  3023. + MAX-ACCESS read-create
  3024. + STATUS obsolete
  3025. + DESCRIPTION
  3026. + "The Subnet Mask that pertains to the Net or
  3027. + Subnet."
  3028. + REFERENCE
  3029. + "OSPF Version 2, Appendix C.2 Area parameters"
  3030. + ::= { ospfAreaRangeEntry 3 }
  3031. +
  3032. + ospfAreaRangeStatus OBJECT-TYPE
  3033. + SYNTAX RowStatus
  3034. + MAX-ACCESS read-create
  3035. + STATUS obsolete
  3036. + DESCRIPTION
  3037. + "This variable displays the status of the en-
  3038. + try. Setting it to 'invalid' has the effect of
  3039. + rendering it inoperative. The internal effect
  3040. + (row removal) is implementation dependent."
  3041. + ::= { ospfAreaRangeEntry 4 }
  3042. +
  3043. +
  3044. + ospfAreaRangeEffect OBJECT-TYPE
  3045. + SYNTAX INTEGER {
  3046. + advertiseMatching (1),
  3047. + doNotAdvertiseMatching (2)
  3048. + }
  3049. + MAX-ACCESS read-create
  3050. + STATUS obsolete
  3051. + DESCRIPTION
  3052. + "Subnets subsumed by ranges either trigger the
  3053. + advertisement of the indicated summary (adver-
  3054. + tiseMatching), or result in the subnet's not
  3055. + being advertised at all outside the area."
  3056. + DEFVAL { advertiseMatching }
  3057. + ::= { ospfAreaRangeEntry 5 }
  3058. +
  3059. +
  3060. +
  3061. +-- OSPF Host Table
  3062. +
  3063. +-- The Host/Metric Table indicates what hosts are directly
  3064. +-- attached to the Router, and what metrics and types of
  3065. +-- service should be advertised for them.
  3066. +
  3067. + ospfHostTable OBJECT-TYPE
  3068. + SYNTAX SEQUENCE OF OspfHostEntry
  3069. + MAX-ACCESS not-accessible
  3070. + STATUS current
  3071. + DESCRIPTION
  3072. + "The list of Hosts, and their metrics, that the
  3073. + router will advertise as host routes."
  3074. + REFERENCE
  3075. + "OSPF Version 2, Appendix C.6 Host route param-
  3076. + eters"
  3077. + ::= { ospf 6 }
  3078. +
  3079. +
  3080. + ospfHostEntry OBJECT-TYPE
  3081. + SYNTAX OspfHostEntry
  3082. + MAX-ACCESS not-accessible
  3083. + STATUS current
  3084. + DESCRIPTION
  3085. + "A metric to be advertised, for a given type of
  3086. + service, when a given host is reachable."
  3087. + INDEX { ospfHostIpAddress, ospfHostTOS }
  3088. + ::= { ospfHostTable 1 }
  3089. +
  3090. +OspfHostEntry ::=
  3091. + SEQUENCE {
  3092. + ospfHostIpAddress
  3093. + IpAddress,
  3094. + ospfHostTOS
  3095. + TOSType,
  3096. + ospfHostMetric
  3097. + Metric,
  3098. + ospfHostStatus
  3099. + RowStatus,
  3100. + ospfHostAreaID
  3101. + AreaID
  3102. + }
  3103. +
  3104. + ospfHostIpAddress OBJECT-TYPE
  3105. + SYNTAX IpAddress
  3106. + MAX-ACCESS read-only
  3107. + STATUS current
  3108. + DESCRIPTION
  3109. + "The IP Address of the Host."
  3110. + REFERENCE
  3111. + "OSPF Version 2, Appendix C.6 Host route parame-
  3112. + ters"
  3113. + ::= { ospfHostEntry 1 }
  3114. +
  3115. +
  3116. + ospfHostTOS OBJECT-TYPE
  3117. + SYNTAX TOSType
  3118. + MAX-ACCESS read-only
  3119. + STATUS current
  3120. + DESCRIPTION
  3121. + "The Type of Service of the route being config-
  3122. + ured."
  3123. + REFERENCE
  3124. + "OSPF Version 2, Appendix C.6 Host route parame-
  3125. + ters"
  3126. + ::= { ospfHostEntry 2 }
  3127. +
  3128. +
  3129. + ospfHostMetric OBJECT-TYPE
  3130. + SYNTAX Metric
  3131. + MAX-ACCESS read-create
  3132. + STATUS current
  3133. + DESCRIPTION
  3134. + "The Metric to be advertised."
  3135. + REFERENCE
  3136. + "OSPF Version 2, Appendix C.6 Host route parame-
  3137. + ters"
  3138. + ::= { ospfHostEntry 3 }
  3139. +
  3140. + ospfHostStatus OBJECT-TYPE
  3141. + SYNTAX RowStatus
  3142. + MAX-ACCESS read-create
  3143. + STATUS current
  3144. + DESCRIPTION
  3145. + "This variable displays the status of the en-
  3146. + try. Setting it to 'invalid' has the effect of
  3147. + rendering it inoperative. The internal effect
  3148. + (row removal) is implementation dependent."
  3149. + ::= { ospfHostEntry 4 }
  3150. +
  3151. +
  3152. + ospfHostAreaID OBJECT-TYPE
  3153. + SYNTAX AreaID
  3154. + MAX-ACCESS read-only
  3155. + STATUS current
  3156. + DESCRIPTION
  3157. + "The Area the Host Entry is to be found within.
  3158. + By default, the area that a subsuming OSPF in-
  3159. + terface is in, or 0.0.0.0"
  3160. + REFERENCE
  3161. + "OSPF Version 2, Appendix C.2 Area parameters"
  3162. + ::= { ospfHostEntry 5 }
  3163. +
  3164. +
  3165. +-- OSPF Interface Table
  3166. +
  3167. +-- The OSPF Interface Table augments the ipAddrTable
  3168. +-- with OSPF specific information.
  3169. +
  3170. + ospfIfTable OBJECT-TYPE
  3171. + SYNTAX SEQUENCE OF OspfIfEntry
  3172. + MAX-ACCESS not-accessible
  3173. + STATUS current
  3174. + DESCRIPTION
  3175. + "The OSPF Interface Table describes the inter-
  3176. + faces from the viewpoint of OSPF."
  3177. + REFERENCE
  3178. + "OSPF Version 2, Appendix C.3 Router interface
  3179. + parameters"
  3180. + ::= { ospf 7 }
  3181. +
  3182. +
  3183. + ospfIfEntry OBJECT-TYPE
  3184. + SYNTAX OspfIfEntry
  3185. + MAX-ACCESS not-accessible
  3186. + STATUS current
  3187. + DESCRIPTION
  3188. + "The OSPF Interface Entry describes one inter-
  3189. + face from the viewpoint of OSPF."
  3190. + INDEX { ospfIfIpAddress, ospfAddressLessIf }
  3191. + ::= { ospfIfTable 1 }
  3192. +
  3193. +OspfIfEntry ::=
  3194. + SEQUENCE {
  3195. + ospfIfIpAddress
  3196. + IpAddress,
  3197. + ospfAddressLessIf
  3198. + Integer32,
  3199. + ospfIfAreaId
  3200. + AreaID,
  3201. + ospfIfType
  3202. + INTEGER,
  3203. + ospfIfAdminStat
  3204. + Status,
  3205. + ospfIfRtrPriority
  3206. + DesignatedRouterPriority,
  3207. + ospfIfTransitDelay
  3208. + UpToMaxAge,
  3209. + ospfIfRetransInterval
  3210. + UpToMaxAge,
  3211. + ospfIfHelloInterval
  3212. + HelloRange,
  3213. + ospfIfRtrDeadInterval
  3214. + PositiveInteger,
  3215. + ospfIfPollInterval
  3216. + PositiveInteger,
  3217. + ospfIfState
  3218. + INTEGER,
  3219. + ospfIfDesignatedRouter
  3220. + IpAddress,
  3221. + ospfIfBackupDesignatedRouter
  3222. + IpAddress,
  3223. + ospfIfEvents
  3224. + Counter32,
  3225. + ospfIfAuthType
  3226. + INTEGER,
  3227. + ospfIfAuthKey
  3228. + OCTET STRING,
  3229. + ospfIfStatus
  3230. + RowStatus,
  3231. + ospfIfMulticastForwarding
  3232. + INTEGER,
  3233. + ospfIfDemand
  3234. + TruthValue
  3235. + }
  3236. +
  3237. + ospfIfIpAddress OBJECT-TYPE
  3238. + SYNTAX IpAddress
  3239. + MAX-ACCESS read-only
  3240. + STATUS current
  3241. + DESCRIPTION
  3242. + "The IP address of this OSPF interface."
  3243. + ::= { ospfIfEntry 1 }
  3244. +
  3245. + ospfAddressLessIf OBJECT-TYPE
  3246. + SYNTAX Integer32
  3247. + MAX-ACCESS read-only
  3248. + STATUS current
  3249. + DESCRIPTION
  3250. + "For the purpose of easing the instancing of
  3251. + addressed and addressless interfaces; This
  3252. + variable takes the value 0 on interfaces with
  3253. + IP Addresses, and the corresponding value of
  3254. + ifIndex for interfaces having no IP Address."
  3255. + ::= { ospfIfEntry 2 }
  3256. + ospfIfAreaId OBJECT-TYPE
  3257. + SYNTAX AreaID
  3258. + MAX-ACCESS read-create
  3259. + STATUS current
  3260. + DESCRIPTION
  3261. + "A 32-bit integer uniquely identifying the area
  3262. + to which the interface connects. Area ID
  3263. + 0.0.0.0 is used for the OSPF backbone."
  3264. + DEFVAL { '00000000'H } -- 0.0.0.0
  3265. + ::= { ospfIfEntry 3 }
  3266. +
  3267. + ospfIfType OBJECT-TYPE
  3268. + SYNTAX INTEGER {
  3269. + broadcast (1),
  3270. + nbma (2),
  3271. + pointToPoint (3),
  3272. + pointToMultipoint (5)
  3273. + }
  3274. + MAX-ACCESS read-create
  3275. + STATUS current
  3276. + DESCRIPTION
  3277. + "The OSPF interface type.
  3278. +
  3279. + By way of a default, this field may be intuited
  3280. + from the corresponding value of ifType. Broad-
  3281. + cast LANs, such as Ethernet and IEEE 802.5,
  3282. + take the value 'broadcast', X.25 and similar
  3283. + technologies take the value 'nbma', and links
  3284. + that are definitively point to point take the
  3285. + value 'pointToPoint'."
  3286. + ::= { ospfIfEntry 4 }
  3287. +
  3288. +
  3289. + ospfIfAdminStat OBJECT-TYPE
  3290. + SYNTAX Status
  3291. + MAX-ACCESS read-create
  3292. + STATUS current
  3293. + DESCRIPTION
  3294. + "The OSPF interface's administrative status.
  3295. + The value formed on the interface, and the in-
  3296. + terface will be advertised as an internal route
  3297. + to some area. The value 'disabled' denotes
  3298. + that the interface is external to OSPF."
  3299. + DEFVAL { enabled }
  3300. + ::= { ospfIfEntry 5 }
  3301. +
  3302. + ospfIfRtrPriority OBJECT-TYPE
  3303. + SYNTAX DesignatedRouterPriority
  3304. + MAX-ACCESS read-create
  3305. + STATUS current
  3306. + DESCRIPTION
  3307. + "The priority of this interface. Used in
  3308. + multi-access networks, this field is used in
  3309. + the designated router election algorithm. The
  3310. + value 0 signifies that the router is not eligi-
  3311. + ble to become the designated router on this
  3312. + particular network. In the event of a tie in
  3313. + this value, routers will use their Router ID as
  3314. + a tie breaker."
  3315. + DEFVAL { 1 }
  3316. + ::= { ospfIfEntry 6 }
  3317. +
  3318. +
  3319. + ospfIfTransitDelay OBJECT-TYPE
  3320. + SYNTAX UpToMaxAge
  3321. + MAX-ACCESS read-create
  3322. + STATUS current
  3323. + DESCRIPTION
  3324. + "The estimated number of seconds it takes to
  3325. + transmit a link state update packet over this
  3326. + interface."
  3327. + DEFVAL { 1 }
  3328. + ::= { ospfIfEntry 7 }
  3329. +
  3330. +
  3331. + ospfIfRetransInterval OBJECT-TYPE
  3332. + SYNTAX UpToMaxAge
  3333. + MAX-ACCESS read-create
  3334. + STATUS current
  3335. + DESCRIPTION
  3336. + "The number of seconds between link-state ad-
  3337. + vertisement retransmissions, for adjacencies
  3338. + belonging to this interface. This value is
  3339. + also used when retransmitting database descrip-
  3340. + tion and link-state request packets."
  3341. + DEFVAL { 5 }
  3342. + ::= { ospfIfEntry 8 }
  3343. +
  3344. +
  3345. + ospfIfHelloInterval OBJECT-TYPE
  3346. + SYNTAX HelloRange
  3347. + MAX-ACCESS read-create
  3348. + STATUS current
  3349. + DESCRIPTION
  3350. + "The length of time, in seconds, between the
  3351. + Hello packets that the router sends on the in-
  3352. + terface. This value must be the same for all
  3353. + routers attached to a common network."
  3354. + DEFVAL { 10 }
  3355. + ::= { ospfIfEntry 9 }
  3356. +
  3357. +
  3358. + ospfIfRtrDeadInterval OBJECT-TYPE
  3359. + SYNTAX PositiveInteger
  3360. + MAX-ACCESS read-create
  3361. + STATUS current
  3362. + DESCRIPTION
  3363. + "The number of seconds that a router's Hello
  3364. + packets have not been seen before it's neigh-
  3365. + bors declare the router down. This should be
  3366. + some multiple of the Hello interval. This
  3367. + value must be the same for all routers attached
  3368. + to a common network."
  3369. + DEFVAL { 40 }
  3370. + ::= { ospfIfEntry 10 }
  3371. +
  3372. +
  3373. + ospfIfPollInterval OBJECT-TYPE
  3374. + SYNTAX PositiveInteger
  3375. + MAX-ACCESS read-create
  3376. + STATUS current
  3377. + DESCRIPTION
  3378. + "The larger time interval, in seconds, between
  3379. + the Hello packets sent to an inactive non-
  3380. + broadcast multi- access neighbor."
  3381. + DEFVAL { 120 }
  3382. + ::= { ospfIfEntry 11 }
  3383. +
  3384. +
  3385. + ospfIfState OBJECT-TYPE
  3386. + SYNTAX INTEGER {
  3387. + down (1),
  3388. + loopback (2),
  3389. + waiting (3),
  3390. + pointToPoint (4),
  3391. + designatedRouter (5),
  3392. + backupDesignatedRouter (6),
  3393. + otherDesignatedRouter (7)
  3394. + }
  3395. + MAX-ACCESS read-only
  3396. + STATUS current
  3397. + DESCRIPTION
  3398. + "The OSPF Interface State."
  3399. + DEFVAL { down }
  3400. + ::= { ospfIfEntry 12 }
  3401. +
  3402. +
  3403. + ospfIfDesignatedRouter OBJECT-TYPE
  3404. + SYNTAX IpAddress
  3405. + MAX-ACCESS read-only
  3406. + STATUS current
  3407. + DESCRIPTION
  3408. + "The IP Address of the Designated Router."
  3409. + DEFVAL { '00000000'H } -- 0.0.0.0
  3410. + ::= { ospfIfEntry 13 }
  3411. +
  3412. +
  3413. + ospfIfBackupDesignatedRouter OBJECT-TYPE
  3414. + SYNTAX IpAddress
  3415. + MAX-ACCESS read-only
  3416. + STATUS current
  3417. + DESCRIPTION
  3418. + "The IP Address of the Backup Designated
  3419. + Router."
  3420. + DEFVAL { '00000000'H } -- 0.0.0.0
  3421. + ::= { ospfIfEntry 14 }
  3422. +
  3423. + ospfIfEvents OBJECT-TYPE
  3424. + SYNTAX Counter32
  3425. + MAX-ACCESS read-only
  3426. + STATUS current
  3427. + DESCRIPTION
  3428. + "The number of times this OSPF interface has
  3429. + changed its state, or an error has occurred."
  3430. + ::= { ospfIfEntry 15 }
  3431. +
  3432. +
  3433. + ospfIfAuthKey OBJECT-TYPE
  3434. + SYNTAX OCTET STRING (SIZE (0..256))
  3435. + MAX-ACCESS read-create
  3436. + STATUS current
  3437. + DESCRIPTION
  3438. + "The Authentication Key. If the Area's Author-
  3439. + ization Type is simplePassword, and the key
  3440. + length is shorter than 8 octets, the agent will
  3441. + left adjust and zero fill to 8 octets.
  3442. +
  3443. + Note that unauthenticated interfaces need no
  3444. + authentication key, and simple password authen-
  3445. + tication cannot use a key of more than 8 oc-
  3446. + tets. Larger keys are useful only with authen-
  3447. + tication mechanisms not specified in this docu-
  3448. + ment.
  3449. +
  3450. + When read, ospfIfAuthKey always returns an Oc-
  3451. + tet String of length zero."
  3452. + REFERENCE
  3453. + "OSPF Version 2, Section 9 The Interface Data
  3454. + Structure"
  3455. + DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0
  3456. + ::= { ospfIfEntry 16 }
  3457. +
  3458. + ospfIfStatus OBJECT-TYPE
  3459. + SYNTAX RowStatus
  3460. + MAX-ACCESS read-create
  3461. + STATUS current
  3462. + DESCRIPTION
  3463. + "This variable displays the status of the en-
  3464. + try. Setting it to 'invalid' has the effect of
  3465. + rendering it inoperative. The internal effect
  3466. + (row removal) is implementation dependent."
  3467. + ::= { ospfIfEntry 17 }
  3468. +
  3469. +
  3470. + ospfIfMulticastForwarding OBJECT-TYPE
  3471. + SYNTAX INTEGER {
  3472. + blocked (1), -- no multicast forwarding
  3473. + multicast (2), -- using multicast address
  3474. + unicast (3) -- to each OSPF neighbor
  3475. + }
  3476. + MAX-ACCESS read-create
  3477. + STATUS current
  3478. + DESCRIPTION
  3479. + "The way multicasts should forwarded on this
  3480. + interface; not forwarded, forwarded as data
  3481. + link multicasts, or forwarded as data link uni-
  3482. + casts. Data link multicasting is not meaning-
  3483. + ful on point to point and NBMA interfaces, and
  3484. + setting ospfMulticastForwarding to 0 effective-
  3485. + ly disables all multicast forwarding."
  3486. + DEFVAL { blocked }
  3487. + ::= { ospfIfEntry 18 }
  3488. +
  3489. +
  3490. + ospfIfDemand OBJECT-TYPE
  3491. + SYNTAX TruthValue
  3492. + MAX-ACCESS read-create
  3493. + STATUS current
  3494. + DESCRIPTION
  3495. + "Indicates whether Demand OSPF procedures (hel-
  3496. + lo supression to FULL neighbors and setting the
  3497. + DoNotAge flag on proogated LSAs) should be per-
  3498. + formed on this interface."
  3499. + DEFVAL { false }
  3500. + ::= { ospfIfEntry 19 }
  3501. +
  3502. +
  3503. + ospfIfAuthType OBJECT-TYPE
  3504. + SYNTAX INTEGER (0..255)
  3505. + -- none (0),
  3506. + -- simplePassword (1)
  3507. + -- md5 (2)
  3508. + -- reserved for specification by IANA (> 2)
  3509. + MAX-ACCESS read-create
  3510. + STATUS current
  3511. + DESCRIPTION
  3512. + "The authentication type specified for an in-
  3513. + terface. Additional authentication types may
  3514. + be assigned locally."
  3515. + REFERENCE
  3516. + "OSPF Version 2, Appendix E Authentication"
  3517. + DEFVAL { 0 } -- no authentication, by default
  3518. + ::= { ospfIfEntry 20 }
  3519. +
  3520. +
  3521. +-- OSPF Interface Metric Table
  3522. +
  3523. +-- The Metric Table describes the metrics to be advertised
  3524. +-- for a specified interface at the various types of service.
  3525. +-- As such, this table is an adjunct of the OSPF Interface
  3526. +-- Table.
  3527. +
  3528. +-- Types of service, as defined by RFC 791, have the ability
  3529. +-- to request low delay, high bandwidth, or reliable linkage.
  3530. +
  3531. +-- For the purposes of this specification, the measure of
  3532. +-- bandwidth
  3533. +
  3534. +-- Metric = 10^8 / ifSpeed
  3535. +
  3536. +-- is the default value. For multiple link interfaces, note
  3537. +-- that ifSpeed is the sum of the individual link speeds.
  3538. +-- This yields a number having the following typical values:
  3539. +
  3540. +-- Network Type/bit rate Metric
  3541. +
  3542. +-- >= 100 MBPS 1
  3543. +-- Ethernet/802.3 10
  3544. +-- E1 48
  3545. +-- T1 (ESF) 65
  3546. +-- 64 KBPS 1562
  3547. +-- 56 KBPS 1785
  3548. +-- 19.2 KBPS 5208
  3549. +-- 9.6 KBPS 10416
  3550. +
  3551. +-- Routes that are not specified use the default (TOS 0) metric
  3552. +
  3553. + ospfIfMetricTable OBJECT-TYPE
  3554. + SYNTAX SEQUENCE OF OspfIfMetricEntry
  3555. + MAX-ACCESS not-accessible
  3556. + STATUS current
  3557. + DESCRIPTION
  3558. + "The TOS metrics for a non-virtual interface
  3559. + identified by the interface index."
  3560. + REFERENCE
  3561. + "OSPF Version 2, Appendix C.3 Router interface
  3562. + parameters"
  3563. + ::= { ospf 8 }
  3564. +
  3565. + ospfIfMetricEntry OBJECT-TYPE
  3566. + SYNTAX OspfIfMetricEntry
  3567. + MAX-ACCESS not-accessible
  3568. + STATUS current
  3569. + DESCRIPTION
  3570. + "A particular TOS metric for a non-virtual in-
  3571. + terface identified by the interface index."
  3572. + REFERENCE
  3573. + "OSPF Version 2, Appendix C.3 Router interface
  3574. + parameters"
  3575. + INDEX { ospfIfMetricIpAddress,
  3576. + ospfIfMetricAddressLessIf,
  3577. + ospfIfMetricTOS }
  3578. + ::= { ospfIfMetricTable 1 }
  3579. +
  3580. +OspfIfMetricEntry ::=
  3581. + SEQUENCE {
  3582. + ospfIfMetricIpAddress
  3583. + IpAddress,
  3584. + ospfIfMetricAddressLessIf
  3585. + Integer32,
  3586. + ospfIfMetricTOS
  3587. + TOSType,
  3588. + ospfIfMetricValue
  3589. + Metric,
  3590. + ospfIfMetricStatus
  3591. + RowStatus
  3592. + }
  3593. +
  3594. + ospfIfMetricIpAddress OBJECT-TYPE
  3595. + SYNTAX IpAddress
  3596. + MAX-ACCESS read-only
  3597. + STATUS current
  3598. + DESCRIPTION
  3599. + "The IP address of this OSPF interface. On row
  3600. + creation, this can be derived from the in-
  3601. + stance."
  3602. + ::= { ospfIfMetricEntry 1 }
  3603. +
  3604. + ospfIfMetricAddressLessIf OBJECT-TYPE
  3605. + SYNTAX Integer32
  3606. + MAX-ACCESS read-only
  3607. + STATUS current
  3608. + DESCRIPTION
  3609. + "For the purpose of easing the instancing of
  3610. + addressed and addressless interfaces; This
  3611. + variable takes the value 0 on interfaces with
  3612. + IP Addresses, and the value of ifIndex for in-
  3613. + terfaces having no IP Address. On row crea-
  3614. + tion, this can be derived from the instance."
  3615. + ::= { ospfIfMetricEntry 2 }
  3616. +
  3617. +
  3618. + ospfIfMetricTOS OBJECT-TYPE
  3619. + SYNTAX TOSType
  3620. + MAX-ACCESS read-only
  3621. + STATUS current
  3622. + DESCRIPTION
  3623. + "The type of service metric being referenced.
  3624. + On row creation, this can be derived from the
  3625. + instance."
  3626. + ::= { ospfIfMetricEntry 3 }
  3627. +
  3628. +
  3629. + ospfIfMetricValue OBJECT-TYPE
  3630. + SYNTAX Metric
  3631. + MAX-ACCESS read-create
  3632. + STATUS current
  3633. + DESCRIPTION
  3634. + "The metric of using this type of service on
  3635. + this interface. The default value of the TOS 0
  3636. + Metric is 10^8 / ifSpeed."
  3637. + ::= { ospfIfMetricEntry 4 }
  3638. +
  3639. + ospfIfMetricStatus OBJECT-TYPE
  3640. + SYNTAX RowStatus
  3641. + MAX-ACCESS read-create
  3642. + STATUS current
  3643. + DESCRIPTION
  3644. + "This variable displays the status of the en-
  3645. + try. Setting it to 'invalid' has the effect of
  3646. + rendering it inoperative. The internal effect
  3647. + (row removal) is implementation dependent."
  3648. + ::= { ospfIfMetricEntry 5 }
  3649. +
  3650. +
  3651. +-- OSPF Virtual Interface Table
  3652. +
  3653. +-- The Virtual Interface Table describes the virtual
  3654. +-- links that the OSPF Process is configured to
  3655. +-- carry on.
  3656. +
  3657. + ospfVirtIfTable OBJECT-TYPE
  3658. + SYNTAX SEQUENCE OF OspfVirtIfEntry
  3659. + MAX-ACCESS not-accessible
  3660. + STATUS current
  3661. + DESCRIPTION
  3662. + "Information about this router's virtual inter-
  3663. + faces."
  3664. + REFERENCE
  3665. + "OSPF Version 2, Appendix C.4 Virtual link
  3666. + parameters"
  3667. + ::= { ospf 9 }
  3668. +
  3669. +
  3670. + ospfVirtIfEntry OBJECT-TYPE
  3671. + SYNTAX OspfVirtIfEntry
  3672. + MAX-ACCESS not-accessible
  3673. + STATUS current
  3674. + DESCRIPTION
  3675. + "Information about a single Virtual Interface."
  3676. + INDEX { ospfVirtIfAreaId, ospfVirtIfNeighbor }
  3677. + ::= { ospfVirtIfTable 1 }
  3678. +
  3679. +OspfVirtIfEntry ::=
  3680. + SEQUENCE {
  3681. + ospfVirtIfAreaId
  3682. + AreaID,
  3683. + ospfVirtIfNeighbor
  3684. + RouterID,
  3685. + ospfVirtIfTransitDelay
  3686. + UpToMaxAge,
  3687. + ospfVirtIfRetransInterval
  3688. + UpToMaxAge,
  3689. + ospfVirtIfHelloInterval
  3690. + HelloRange,
  3691. + ospfVirtIfRtrDeadInterval
  3692. + PositiveInteger,
  3693. + ospfVirtIfState
  3694. + INTEGER,
  3695. + ospfVirtIfEvents
  3696. + Counter32,
  3697. + ospfVirtIfAuthType
  3698. + INTEGER,
  3699. + ospfVirtIfAuthKey
  3700. + OCTET STRING,
  3701. + ospfVirtIfStatus
  3702. + RowStatus
  3703. + }
  3704. +
  3705. + ospfVirtIfAreaId OBJECT-TYPE
  3706. + SYNTAX AreaID
  3707. + MAX-ACCESS read-only
  3708. + STATUS current
  3709. + DESCRIPTION
  3710. + "The Transit Area that the Virtual Link
  3711. + traverses. By definition, this is not 0.0.0.0"
  3712. + ::= { ospfVirtIfEntry 1 }
  3713. +
  3714. +
  3715. + ospfVirtIfNeighbor OBJECT-TYPE
  3716. + SYNTAX RouterID
  3717. + MAX-ACCESS read-only
  3718. + STATUS current
  3719. + DESCRIPTION
  3720. + "The Router ID of the Virtual Neighbor."
  3721. + ::= { ospfVirtIfEntry 2 }
  3722. +
  3723. +
  3724. + ospfVirtIfTransitDelay OBJECT-TYPE
  3725. + SYNTAX UpToMaxAge
  3726. + MAX-ACCESS read-create
  3727. + STATUS current
  3728. + DESCRIPTION
  3729. + "The estimated number of seconds it takes to
  3730. + transmit a link- state update packet over this
  3731. + interface."
  3732. + DEFVAL { 1 }
  3733. + ::= { ospfVirtIfEntry 3 }
  3734. +
  3735. +
  3736. + ospfVirtIfRetransInterval OBJECT-TYPE
  3737. + SYNTAX UpToMaxAge
  3738. + MAX-ACCESS read-create
  3739. + STATUS current
  3740. + DESCRIPTION
  3741. + "The number of seconds between link-state ad-
  3742. + vertisement retransmissions, for adjacencies
  3743. + belonging to this interface. This value is
  3744. + also used when retransmitting database descrip-
  3745. + tion and link-state request packets. This
  3746. + value should be well over the expected round-
  3747. + trip time."
  3748. + DEFVAL { 5 }
  3749. + ::= { ospfVirtIfEntry 4 }
  3750. +
  3751. +
  3752. + ospfVirtIfHelloInterval OBJECT-TYPE
  3753. + SYNTAX HelloRange
  3754. + MAX-ACCESS read-create
  3755. + STATUS current
  3756. + DESCRIPTION
  3757. + "The length of time, in seconds, between the
  3758. + Hello packets that the router sends on the in-
  3759. + terface. This value must be the same for the
  3760. + virtual neighbor."
  3761. + DEFVAL { 10 }
  3762. + ::= { ospfVirtIfEntry 5 }
  3763. +
  3764. +
  3765. + ospfVirtIfRtrDeadInterval OBJECT-TYPE
  3766. + SYNTAX PositiveInteger
  3767. + MAX-ACCESS read-create
  3768. + STATUS current
  3769. + DESCRIPTION
  3770. + "The number of seconds that a router's Hello
  3771. + packets have not been seen before it's neigh-
  3772. + bors declare the router down. This should be
  3773. + some multiple of the Hello interval. This
  3774. + value must be the same for the virtual neigh-
  3775. + bor."
  3776. + DEFVAL { 60 }
  3777. + ::= { ospfVirtIfEntry 6 }
  3778. +
  3779. +
  3780. + ospfVirtIfState OBJECT-TYPE
  3781. + SYNTAX INTEGER {
  3782. + down (1), -- these use the same encoding
  3783. + pointToPoint (4) -- as the ospfIfTable
  3784. + }
  3785. + MAX-ACCESS read-only
  3786. + STATUS current
  3787. + DESCRIPTION
  3788. + "OSPF virtual interface states."
  3789. + DEFVAL { down }
  3790. + ::= { ospfVirtIfEntry 7 }
  3791. +
  3792. +
  3793. + ospfVirtIfEvents OBJECT-TYPE
  3794. + SYNTAX Counter32
  3795. + MAX-ACCESS read-only
  3796. + STATUS current
  3797. + DESCRIPTION
  3798. + "The number of state changes or error events on
  3799. + this Virtual Link"
  3800. + ::= { ospfVirtIfEntry 8 }
  3801. +
  3802. +
  3803. + ospfVirtIfAuthKey OBJECT-TYPE
  3804. + SYNTAX OCTET STRING (SIZE(0..256))
  3805. + MAX-ACCESS read-create
  3806. + STATUS current
  3807. + DESCRIPTION
  3808. + "If Authentication Type is simplePassword, the
  3809. + device will left adjust and zero fill to 8 oc-
  3810. + tets.
  3811. +
  3812. + Note that unauthenticated interfaces need no
  3813. + authentication key, and simple password authen-
  3814. + tication cannot use a key of more than 8 oc-
  3815. + tets. Larger keys are useful only with authen-
  3816. + tication mechanisms not specified in this docu-
  3817. + ment.
  3818. +
  3819. + When read, ospfVifAuthKey always returns a
  3820. + string of length zero."
  3821. + REFERENCE
  3822. + "OSPF Version 2, Section 9 The Interface Data
  3823. + Structure"
  3824. + DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0
  3825. + ::= { ospfVirtIfEntry 9 }
  3826. +
  3827. +
  3828. + ospfVirtIfStatus OBJECT-TYPE
  3829. + SYNTAX RowStatus
  3830. + MAX-ACCESS read-create
  3831. + STATUS current
  3832. + DESCRIPTION
  3833. + "This variable displays the status of the en-
  3834. + try. Setting it to 'invalid' has the effect of
  3835. + rendering it inoperative. The internal effect
  3836. + (row removal) is implementation dependent."
  3837. + ::= { ospfVirtIfEntry 10 }
  3838. +
  3839. +
  3840. + ospfVirtIfAuthType OBJECT-TYPE
  3841. + SYNTAX INTEGER (0..255)
  3842. + -- none (0),
  3843. + -- simplePassword (1)
  3844. + -- md5 (2)
  3845. + -- reserved for specification by IANA (> 2)
  3846. + MAX-ACCESS read-create
  3847. + STATUS current
  3848. + DESCRIPTION
  3849. + "The authentication type specified for a virtu-
  3850. + al interface. Additional authentication types
  3851. + may be assigned locally."
  3852. + REFERENCE
  3853. + "OSPF Version 2, Appendix E Authentication"
  3854. + DEFVAL { 0 } -- no authentication, by default
  3855. + ::= { ospfVirtIfEntry 11 }
  3856. +
  3857. +
  3858. +-- OSPF Neighbor Table
  3859. +
  3860. +-- The OSPF Neighbor Table describes all neighbors in
  3861. +-- the locality of the subject router.
  3862. +
  3863. + ospfNbrTable OBJECT-TYPE
  3864. + SYNTAX SEQUENCE OF OspfNbrEntry
  3865. + MAX-ACCESS not-accessible
  3866. + STATUS current
  3867. + DESCRIPTION
  3868. + "A table of non-virtual neighbor information."
  3869. + REFERENCE
  3870. + "OSPF Version 2, Section 10 The Neighbor Data
  3871. + Structure"
  3872. + ::= { ospf 10 }
  3873. +
  3874. +
  3875. + ospfNbrEntry OBJECT-TYPE
  3876. + SYNTAX OspfNbrEntry
  3877. + MAX-ACCESS not-accessible
  3878. + STATUS current
  3879. + DESCRIPTION
  3880. + "The information regarding a single neighbor."
  3881. + REFERENCE
  3882. + "OSPF Version 2, Section 10 The Neighbor Data
  3883. + Structure"
  3884. + INDEX { ospfNbrIpAddr, ospfNbrAddressLessIndex }
  3885. + ::= { ospfNbrTable 1 }
  3886. +
  3887. +OspfNbrEntry ::=
  3888. + SEQUENCE {
  3889. + ospfNbrIpAddr
  3890. + IpAddress,
  3891. + ospfNbrAddressLessIndex
  3892. + InterfaceIndex,
  3893. + ospfNbrRtrId
  3894. + RouterID,
  3895. + ospfNbrOptions
  3896. + Integer32,
  3897. + ospfNbrPriority
  3898. + DesignatedRouterPriority,
  3899. + ospfNbrState
  3900. + INTEGER,
  3901. + ospfNbrEvents
  3902. + Counter32,
  3903. + ospfNbrLsRetransQLen
  3904. + Gauge32,
  3905. + ospfNbmaNbrStatus
  3906. + RowStatus,
  3907. + ospfNbmaNbrPermanence
  3908. + INTEGER,
  3909. + ospfNbrHelloSuppressed
  3910. + TruthValue
  3911. + }
  3912. +
  3913. + ospfNbrIpAddr OBJECT-TYPE
  3914. + SYNTAX IpAddress
  3915. + MAX-ACCESS read-only
  3916. + STATUS current
  3917. + DESCRIPTION
  3918. + "The IP address this neighbor is using in its
  3919. + IP Source Address. Note that, on addressless
  3920. + links, this will not be 0.0.0.0, but the ad-
  3921. + dress of another of the neighbor's interfaces."
  3922. + ::= { ospfNbrEntry 1 }
  3923. +
  3924. +
  3925. + ospfNbrAddressLessIndex OBJECT-TYPE
  3926. + SYNTAX InterfaceIndex
  3927. + MAX-ACCESS read-only
  3928. + STATUS current
  3929. + DESCRIPTION
  3930. + "On an interface having an IP Address, zero.
  3931. + On addressless interfaces, the corresponding
  3932. + value of ifIndex in the Internet Standard MIB.
  3933. + On row creation, this can be derived from the
  3934. + instance."
  3935. + ::= { ospfNbrEntry 2 }
  3936. +
  3937. +
  3938. + ospfNbrRtrId OBJECT-TYPE
  3939. + SYNTAX RouterID
  3940. + MAX-ACCESS read-only
  3941. + STATUS current
  3942. + DESCRIPTION
  3943. + "A 32-bit integer (represented as a type IpAd-
  3944. + dress) uniquely identifying the neighboring
  3945. + router in the Autonomous System."
  3946. + DEFVAL { '00000000'H } -- 0.0.0.0
  3947. + ::= { ospfNbrEntry 3 }
  3948. +
  3949. +
  3950. + ospfNbrOptions OBJECT-TYPE
  3951. + SYNTAX Integer32
  3952. + MAX-ACCESS read-only
  3953. + STATUS current
  3954. + DESCRIPTION
  3955. + "A Bit Mask corresponding to the neighbor's op-
  3956. + tions field.
  3957. +
  3958. + Bit 0, if set, indicates that the system will
  3959. + operate on Type of Service metrics other than
  3960. + TOS 0. If zero, the neighbor will ignore all
  3961. + metrics except the TOS 0 metric.
  3962. +
  3963. + Bit 1, if set, indicates that the associated
  3964. + area accepts and operates on external informa-
  3965. + tion; if zero, it is a stub area.
  3966. +
  3967. + Bit 2, if set, indicates that the system is ca-
  3968. + pable of routing IP Multicast datagrams; i.e.,
  3969. + that it implements the Multicast Extensions to
  3970. + OSPF.
  3971. +
  3972. + Bit 3, if set, indicates that the associated
  3973. + area is an NSSA. These areas are capable of
  3974. + carrying type 7 external advertisements, which
  3975. + are translated into type 5 external advertise-
  3976. + ments at NSSA borders."
  3977. + REFERENCE
  3978. + "OSPF Version 2, Section 12.1.2 Options"
  3979. + DEFVAL { 0 }
  3980. + ::= { ospfNbrEntry 4 }
  3981. +
  3982. +
  3983. + ospfNbrPriority OBJECT-TYPE
  3984. + SYNTAX DesignatedRouterPriority
  3985. + MAX-ACCESS read-create
  3986. + STATUS current
  3987. + DESCRIPTION
  3988. + "The priority of this neighbor in the designat-
  3989. + ed router election algorithm. The value 0 sig-
  3990. + nifies that the neighbor is not eligible to be-
  3991. + come the designated router on this particular
  3992. + network."
  3993. + DEFVAL { 1 }
  3994. + ::= { ospfNbrEntry 5 }
  3995. +
  3996. +
  3997. + ospfNbrState OBJECT-TYPE
  3998. + SYNTAX INTEGER {
  3999. + down (1),
  4000. + attempt (2),
  4001. + init (3),
  4002. + twoWay (4),
  4003. + exchangeStart (5),
  4004. + exchange (6),
  4005. + loading (7),
  4006. + full (8)
  4007. + }
  4008. + MAX-ACCESS read-only
  4009. + STATUS current
  4010. + DESCRIPTION
  4011. + "The State of the relationship with this Neigh-
  4012. + bor."
  4013. + REFERENCE
  4014. + "OSPF Version 2, Section 10.1 Neighbor States"
  4015. + DEFVAL { down }
  4016. + ::= { ospfNbrEntry 6 }
  4017. +
  4018. +
  4019. + ospfNbrEvents OBJECT-TYPE
  4020. + SYNTAX Counter32
  4021. + MAX-ACCESS read-only
  4022. + STATUS current
  4023. + DESCRIPTION
  4024. + "The number of times this neighbor relationship
  4025. + has changed state, or an error has occurred."
  4026. + ::= { ospfNbrEntry 7 }
  4027. +
  4028. +
  4029. + ospfNbrLsRetransQLen OBJECT-TYPE
  4030. + SYNTAX Gauge32
  4031. + MAX-ACCESS read-only
  4032. + STATUS current
  4033. + DESCRIPTION
  4034. + "The current length of the retransmission
  4035. + queue."
  4036. + ::= { ospfNbrEntry 8 }
  4037. +
  4038. +
  4039. + ospfNbmaNbrStatus OBJECT-TYPE
  4040. + SYNTAX RowStatus
  4041. + MAX-ACCESS read-create
  4042. + STATUS current
  4043. + DESCRIPTION
  4044. + "This variable displays the status of the en-
  4045. + try. Setting it to 'invalid' has the effect of
  4046. + rendering it inoperative. The internal effect
  4047. + (row removal) is implementation dependent."
  4048. + ::= { ospfNbrEntry 9 }
  4049. +
  4050. +
  4051. + ospfNbmaNbrPermanence OBJECT-TYPE
  4052. + SYNTAX INTEGER {
  4053. + dynamic (1), -- learned through protocol
  4054. + permanent (2) -- configured address
  4055. + }
  4056. + MAX-ACCESS read-only
  4057. + STATUS current
  4058. + DESCRIPTION
  4059. + "This variable displays the status of the en-
  4060. + try. 'dynamic' and 'permanent' refer to how
  4061. + the neighbor became known."
  4062. + DEFVAL { permanent }
  4063. + ::= { ospfNbrEntry 10 }
  4064. +
  4065. +
  4066. + ospfNbrHelloSuppressed OBJECT-TYPE
  4067. + SYNTAX TruthValue
  4068. + MAX-ACCESS read-only
  4069. + STATUS current
  4070. + DESCRIPTION
  4071. + "Indicates whether Hellos are being suppressed
  4072. + to the neighbor"
  4073. + ::= { ospfNbrEntry 11 }
  4074. +
  4075. +
  4076. +-- OSPF Virtual Neighbor Table
  4077. +
  4078. +-- This table describes all virtual neighbors.
  4079. +-- Since Virtual Links are configured in the
  4080. +-- virtual interface table, this table is read-only.
  4081. +
  4082. + ospfVirtNbrTable OBJECT-TYPE
  4083. + SYNTAX SEQUENCE OF OspfVirtNbrEntry
  4084. + MAX-ACCESS not-accessible
  4085. + STATUS current
  4086. + DESCRIPTION
  4087. + "A table of virtual neighbor information."
  4088. + REFERENCE
  4089. + "OSPF Version 2, Section 15 Virtual Links"
  4090. + ::= { ospf 11 }
  4091. +
  4092. +
  4093. + ospfVirtNbrEntry OBJECT-TYPE
  4094. + SYNTAX OspfVirtNbrEntry
  4095. + MAX-ACCESS not-accessible
  4096. + STATUS current
  4097. + DESCRIPTION
  4098. + "Virtual neighbor information."
  4099. + INDEX { ospfVirtNbrArea, ospfVirtNbrRtrId }
  4100. + ::= { ospfVirtNbrTable 1 }
  4101. +
  4102. +OspfVirtNbrEntry ::=
  4103. + SEQUENCE {
  4104. + ospfVirtNbrArea
  4105. + AreaID,
  4106. + ospfVirtNbrRtrId
  4107. + RouterID,
  4108. + ospfVirtNbrIpAddr
  4109. + IpAddress,
  4110. + ospfVirtNbrOptions
  4111. + Integer32,
  4112. + ospfVirtNbrState
  4113. + INTEGER,
  4114. + ospfVirtNbrEvents
  4115. + Counter32,
  4116. + ospfVirtNbrLsRetransQLen
  4117. + Gauge32,
  4118. + ospfVirtNbrHelloSuppressed
  4119. + TruthValue
  4120. + }
  4121. +
  4122. + ospfVirtNbrArea OBJECT-TYPE
  4123. + SYNTAX AreaID
  4124. + MAX-ACCESS read-only
  4125. + STATUS current
  4126. + DESCRIPTION
  4127. + "The Transit Area Identifier."
  4128. + ::= { ospfVirtNbrEntry 1 }
  4129. +
  4130. +
  4131. + ospfVirtNbrRtrId OBJECT-TYPE
  4132. + SYNTAX RouterID
  4133. + MAX-ACCESS read-only
  4134. + STATUS current
  4135. + DESCRIPTION
  4136. + "A 32-bit integer uniquely identifying the
  4137. + neighboring router in the Autonomous System."
  4138. + ::= { ospfVirtNbrEntry 2 }
  4139. +
  4140. +
  4141. + ospfVirtNbrIpAddr OBJECT-TYPE
  4142. + SYNTAX IpAddress
  4143. + MAX-ACCESS read-only
  4144. + STATUS current
  4145. + DESCRIPTION
  4146. + "The IP address this Virtual Neighbor is us-
  4147. + ing."
  4148. + ::= { ospfVirtNbrEntry 3 }
  4149. +
  4150. +
  4151. + ospfVirtNbrOptions OBJECT-TYPE
  4152. + SYNTAX Integer32
  4153. + MAX-ACCESS read-only
  4154. + STATUS current
  4155. + DESCRIPTION
  4156. + "A Bit Mask corresponding to the neighbor's op-
  4157. + tions field.
  4158. +
  4159. + Bit 1, if set, indicates that the system will
  4160. + operate on Type of Service metrics other than
  4161. + TOS 0. If zero, the neighbor will ignore all
  4162. + metrics except the TOS 0 metric.
  4163. +
  4164. + Bit 2, if set, indicates that the system is
  4165. + Network Multicast capable; ie, that it imple-
  4166. + ments OSPF Multicast Routing."
  4167. + ::= { ospfVirtNbrEntry 4 }
  4168. + ospfVirtNbrState OBJECT-TYPE
  4169. + SYNTAX INTEGER {
  4170. + down (1),
  4171. + attempt (2),
  4172. + init (3),
  4173. + twoWay (4),
  4174. + exchangeStart (5),
  4175. + exchange (6),
  4176. + loading (7),
  4177. + full (8)
  4178. + }
  4179. + MAX-ACCESS read-only
  4180. + STATUS current
  4181. + DESCRIPTION
  4182. + "The state of the Virtual Neighbor Relation-
  4183. + ship."
  4184. + ::= { ospfVirtNbrEntry 5 }
  4185. +
  4186. +
  4187. + ospfVirtNbrEvents OBJECT-TYPE
  4188. + SYNTAX Counter32
  4189. + MAX-ACCESS read-only
  4190. + STATUS current
  4191. + DESCRIPTION
  4192. + "The number of times this virtual link has
  4193. + changed its state, or an error has occurred."
  4194. + ::= { ospfVirtNbrEntry 6 }
  4195. +
  4196. +
  4197. + ospfVirtNbrLsRetransQLen OBJECT-TYPE
  4198. + SYNTAX Gauge32
  4199. + MAX-ACCESS read-only
  4200. + STATUS current
  4201. + DESCRIPTION
  4202. + "The current length of the retransmission
  4203. + queue."
  4204. + ::= { ospfVirtNbrEntry 7 }
  4205. +
  4206. +
  4207. + ospfVirtNbrHelloSuppressed OBJECT-TYPE
  4208. + SYNTAX TruthValue
  4209. + MAX-ACCESS read-only
  4210. + STATUS current
  4211. + DESCRIPTION
  4212. + "Indicates whether Hellos are being suppressed
  4213. + to the neighbor"
  4214. + ::= { ospfVirtNbrEntry 8 }
  4215. +
  4216. +-- OSPF Link State Database, External
  4217. +
  4218. +-- The Link State Database contains the Link State
  4219. +-- Advertisements from throughout the areas that the
  4220. +-- device is attached to.
  4221. +
  4222. +-- This table is identical to the OSPF LSDB Table in
  4223. +-- format, but contains only External Link State
  4224. +-- Advertisements. The purpose is to allow external
  4225. +-- LSAs to be displayed once for the router rather
  4226. +-- than once in each non-stub area.
  4227. +
  4228. + ospfExtLsdbTable OBJECT-TYPE
  4229. + SYNTAX SEQUENCE OF OspfExtLsdbEntry
  4230. + MAX-ACCESS not-accessible
  4231. + STATUS current
  4232. + DESCRIPTION
  4233. + "The OSPF Process's Links State Database."
  4234. + REFERENCE
  4235. + "OSPF Version 2, Section 12 Link State Adver-
  4236. + tisements"
  4237. + ::= { ospf 12 }
  4238. +
  4239. +
  4240. + ospfExtLsdbEntry OBJECT-TYPE
  4241. + SYNTAX OspfExtLsdbEntry
  4242. + MAX-ACCESS not-accessible
  4243. + STATUS current
  4244. + DESCRIPTION
  4245. + "A single Link State Advertisement."
  4246. + INDEX { ospfExtLsdbType, ospfExtLsdbLsid, ospfExtLsdbRouterId }
  4247. + ::= { ospfExtLsdbTable 1 }
  4248. +
  4249. +OspfExtLsdbEntry ::=
  4250. + SEQUENCE {
  4251. + ospfExtLsdbType
  4252. + INTEGER,
  4253. + ospfExtLsdbLsid
  4254. + IpAddress,
  4255. + ospfExtLsdbRouterId
  4256. + RouterID,
  4257. + ospfExtLsdbSequence
  4258. + Integer32,
  4259. + ospfExtLsdbAge
  4260. + Integer32,
  4261. + ospfExtLsdbChecksum
  4262. + Integer32,
  4263. + ospfExtLsdbAdvertisement
  4264. + OCTET STRING
  4265. + }
  4266. +
  4267. + ospfExtLsdbType OBJECT-TYPE
  4268. + SYNTAX INTEGER {
  4269. + asExternalLink (5)
  4270. + }
  4271. + MAX-ACCESS read-only
  4272. + STATUS current
  4273. + DESCRIPTION
  4274. + "The type of the link state advertisement.
  4275. + Each link state type has a separate advertise-
  4276. + ment format."
  4277. + REFERENCE
  4278. + "OSPF Version 2, Appendix A.4.1 The Link State
  4279. + Advertisement header"
  4280. + ::= { ospfExtLsdbEntry 1 }
  4281. +
  4282. +
  4283. + ospfExtLsdbLsid OBJECT-TYPE
  4284. + SYNTAX IpAddress
  4285. + MAX-ACCESS read-only
  4286. + STATUS current
  4287. + DESCRIPTION
  4288. + "The Link State ID is an LS Type Specific field
  4289. + containing either a Router ID or an IP Address;
  4290. + it identifies the piece of the routing domain
  4291. + that is being described by the advertisement."
  4292. + REFERENCE
  4293. + "OSPF Version 2, Section 12.1.4 Link State ID"
  4294. + ::= { ospfExtLsdbEntry 2 }
  4295. +
  4296. +
  4297. + ospfExtLsdbRouterId OBJECT-TYPE
  4298. + SYNTAX RouterID
  4299. + MAX-ACCESS read-only
  4300. + STATUS current
  4301. + DESCRIPTION
  4302. + "The 32 bit number that uniquely identifies the
  4303. + originating router in the Autonomous System."
  4304. + REFERENCE
  4305. + "OSPF Version 2, Appendix C.1 Global parameters"
  4306. + ::= { ospfExtLsdbEntry 3 }
  4307. +
  4308. +-- Note that the OSPF Sequence Number is a 32 bit signed
  4309. +-- integer. It starts with the value '80000001'h,
  4310. +-- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h
  4311. +-- Thus, a typical sequence number will be very negative.
  4312. + ospfExtLsdbSequence OBJECT-TYPE
  4313. + SYNTAX Integer32
  4314. + MAX-ACCESS read-only
  4315. + STATUS current
  4316. + DESCRIPTION
  4317. + "The sequence number field is a signed 32-bit
  4318. + integer. It is used to detect old and dupli-
  4319. + cate link state advertisements. The space of
  4320. + sequence numbers is linearly ordered. The
  4321. + larger the sequence number the more recent the
  4322. + advertisement."
  4323. + REFERENCE
  4324. + "OSPF Version 2, Section 12.1.6 LS sequence
  4325. + number"
  4326. + ::= { ospfExtLsdbEntry 4 }
  4327. +
  4328. +
  4329. + ospfExtLsdbAge OBJECT-TYPE
  4330. + SYNTAX Integer32 -- Should be 0..MaxAge
  4331. + MAX-ACCESS read-only
  4332. + STATUS current
  4333. + DESCRIPTION
  4334. + "This field is the age of the link state adver-
  4335. + tisement in seconds."
  4336. + REFERENCE
  4337. + "OSPF Version 2, Section 12.1.1 LS age"
  4338. + ::= { ospfExtLsdbEntry 5 }
  4339. +
  4340. +
  4341. + ospfExtLsdbChecksum OBJECT-TYPE
  4342. + SYNTAX Integer32
  4343. + MAX-ACCESS read-only
  4344. + STATUS current
  4345. + DESCRIPTION
  4346. + "This field is the checksum of the complete
  4347. + contents of the advertisement, excepting the
  4348. + age field. The age field is excepted so that
  4349. + an advertisement's age can be incremented
  4350. + without updating the checksum. The checksum
  4351. + used is the same that is used for ISO connec-
  4352. + tionless datagrams; it is commonly referred to
  4353. + as the Fletcher checksum."
  4354. + REFERENCE
  4355. + "OSPF Version 2, Section 12.1.7 LS checksum"
  4356. + ::= { ospfExtLsdbEntry 6 }
  4357. +
  4358. +
  4359. + ospfExtLsdbAdvertisement OBJECT-TYPE
  4360. + SYNTAX OCTET STRING (SIZE(36))
  4361. + MAX-ACCESS read-only
  4362. + STATUS current
  4363. + DESCRIPTION
  4364. + "The entire Link State Advertisement, including
  4365. + its header."
  4366. + REFERENCE
  4367. + "OSPF Version 2, Section 12 Link State Adver-
  4368. + tisements"
  4369. + ::= { ospfExtLsdbEntry 7 }
  4370. +
  4371. +
  4372. +-- OSPF Use of the CIDR Route Table
  4373. +
  4374. +ospfRouteGroup OBJECT IDENTIFIER ::= { ospf 13 }
  4375. +
  4376. +-- The IP Forwarding Table defines a number of objects for use by
  4377. +-- the routing protocol to externalize its information. Most of
  4378. +-- the variables (ipForwardDest, ipForwardMask, ipForwardPolicy,
  4379. +-- ipForwardNextHop, ipForwardIfIndex, ipForwardType,
  4380. +-- ipForwardProto, ipForwardAge, and ipForwardNextHopAS) are
  4381. +-- defined there.
  4382. +
  4383. +-- Those that leave some discretion are defined here.
  4384. +
  4385. +-- ipCidrRouteProto is, of course, ospf (13).
  4386. +
  4387. +-- ipCidrRouteAge is the time since the route was first calculated,
  4388. +-- as opposed to the time since the last SPF run.
  4389. +
  4390. +-- ipCidrRouteInfo is an OBJECT IDENTIFIER for use by the routing
  4391. +-- protocol. The following values shall be found there depending
  4392. +-- on the way the route was calculated.
  4393. +
  4394. +ospfIntraArea OBJECT IDENTIFIER ::= { ospfRouteGroup 1 }
  4395. +ospfInterArea OBJECT IDENTIFIER ::= { ospfRouteGroup 2 }
  4396. +ospfExternalType1 OBJECT IDENTIFIER ::= { ospfRouteGroup 3 }
  4397. +ospfExternalType2 OBJECT IDENTIFIER ::= { ospfRouteGroup 4 }
  4398. +
  4399. +-- ipCidrRouteMetric1 is, by definition, the primary routing
  4400. +-- metric. Therefore, it should be the metric that route
  4401. +-- selection is based on. For intra-area and inter-area routes,
  4402. +-- it is an OSPF metric. For External Type 1 (comparable value)
  4403. +-- routes, it is an OSPF metric plus the External Metric. For
  4404. +-- external Type 2 (non-comparable value) routes, it is the
  4405. +-- external metric.
  4406. +
  4407. +-- ipCidrRouteMetric2 is, by definition, a secondary routing
  4408. +-- metric. Therefore, it should be the metric that breaks a tie
  4409. +-- among routes having equal metric1 values and the same
  4410. +-- calculation rule. For intra-area, inter-area routes, and
  4411. +-- External Type 1 (comparable value) routes, it is unused. For
  4412. +-- external Type 2 (non-comparable value) routes, it is the metric
  4413. +-- to the AS border router.
  4414. +
  4415. +-- ipCidrRouteMetric3, ipCidrRouteMetric4, and ipCidrRouteMetric5 are
  4416. +-- unused.
  4417. +
  4418. +--
  4419. +-- The OSPF Area Aggregate Table
  4420. +--
  4421. +-- This table replaces the OSPF Area Summary Table, being an
  4422. +-- extension of that for CIDR routers.
  4423. +
  4424. + ospfAreaAggregateTable OBJECT-TYPE
  4425. + SYNTAX SEQUENCE OF OspfAreaAggregateEntry
  4426. + MAX-ACCESS not-accessible
  4427. + STATUS current
  4428. + DESCRIPTION
  4429. + "A range of IP addresses specified by an IP
  4430. + address/IP network mask pair. For example,
  4431. + class B address range of X.X.X.X with a network
  4432. + mask of 255.255.0.0 includes all IP addresses
  4433. + from X.X.0.0 to X.X.255.255. Note that if
  4434. + ranges are configured such that one range sub-
  4435. + sumes another range (e.g., 10.0.0.0 mask
  4436. + 255.0.0.0 and 10.1.0.0 mask 255.255.0.0), the
  4437. + most specific match is the preferred one."
  4438. + REFERENCE
  4439. + "OSPF Version 2, Appendix C.2 Area parameters"
  4440. + ::= { ospf 14 }
  4441. +
  4442. +
  4443. + ospfAreaAggregateEntry OBJECT-TYPE
  4444. + SYNTAX OspfAreaAggregateEntry
  4445. + MAX-ACCESS not-accessible
  4446. + STATUS current
  4447. + DESCRIPTION
  4448. + "A range of IP addresses specified by an IP
  4449. + address/IP network mask pair. For example,
  4450. + class B address range of X.X.X.X with a network
  4451. + mask of 255.255.0.0 includes all IP addresses
  4452. + from X.X.0.0 to X.X.255.255. Note that if
  4453. + ranges are range configured such that one range
  4454. + subsumes another range (e.g., 10.0.0.0 mask
  4455. + 255.0.0.0 and 10.1.0.0 mask 255.255.0.0), the
  4456. + most specific match is the preferred one."
  4457. + REFERENCE
  4458. + "OSPF Version 2, Appendix C.2 Area parameters"
  4459. + INDEX { ospfAreaAggregateAreaID, ospfAreaAggregateLsdbType,
  4460. + ospfAreaAggregateNet, ospfAreaAggregateMask }
  4461. + ::= { ospfAreaAggregateTable 1 }
  4462. +
  4463. +
  4464. +OspfAreaAggregateEntry ::=
  4465. + SEQUENCE {
  4466. + ospfAreaAggregateAreaID
  4467. + AreaID,
  4468. + ospfAreaAggregateLsdbType
  4469. + INTEGER,
  4470. + ospfAreaAggregateNet
  4471. + IpAddress,
  4472. + ospfAreaAggregateMask
  4473. + IpAddress,
  4474. + ospfAreaAggregateStatus
  4475. + RowStatus,
  4476. + ospfAreaAggregateEffect
  4477. + INTEGER
  4478. + }
  4479. +
  4480. + ospfAreaAggregateAreaID OBJECT-TYPE
  4481. + SYNTAX AreaID
  4482. + MAX-ACCESS read-only
  4483. + STATUS current
  4484. + DESCRIPTION
  4485. + "The Area the Address Aggregate is to be found
  4486. + within."
  4487. + REFERENCE
  4488. + "OSPF Version 2, Appendix C.2 Area parameters"
  4489. + ::= { ospfAreaAggregateEntry 1 }
  4490. +
  4491. +
  4492. + ospfAreaAggregateLsdbType OBJECT-TYPE
  4493. + SYNTAX INTEGER {
  4494. + summaryLink (3),
  4495. + nssaExternalLink (7)
  4496. + }
  4497. + MAX-ACCESS read-only
  4498. + STATUS current
  4499. + DESCRIPTION
  4500. + "The type of the Address Aggregate. This field
  4501. + specifies the Lsdb type that this Address Ag-
  4502. + gregate applies to."
  4503. + REFERENCE
  4504. + "OSPF Version 2, Appendix A.4.1 The Link State
  4505. + Advertisement header"
  4506. + ::= { ospfAreaAggregateEntry 2 }
  4507. +
  4508. +
  4509. + ospfAreaAggregateNet OBJECT-TYPE
  4510. + SYNTAX IpAddress
  4511. + MAX-ACCESS read-only
  4512. + STATUS current
  4513. + DESCRIPTION
  4514. + "The IP Address of the Net or Subnet indicated
  4515. + by the range."
  4516. + REFERENCE
  4517. + "OSPF Version 2, Appendix C.2 Area parameters"
  4518. + ::= { ospfAreaAggregateEntry 3 }
  4519. +
  4520. +
  4521. + ospfAreaAggregateMask OBJECT-TYPE
  4522. + SYNTAX IpAddress
  4523. + MAX-ACCESS read-only
  4524. + STATUS current
  4525. + DESCRIPTION
  4526. + "The Subnet Mask that pertains to the Net or
  4527. + Subnet."
  4528. + REFERENCE
  4529. + "OSPF Version 2, Appendix C.2 Area parameters"
  4530. + ::= { ospfAreaAggregateEntry 4 }
  4531. +
  4532. +
  4533. + ospfAreaAggregateStatus OBJECT-TYPE
  4534. + SYNTAX RowStatus
  4535. + MAX-ACCESS read-create
  4536. + STATUS current
  4537. + DESCRIPTION
  4538. + "This variable displays the status of the en-
  4539. + try. Setting it to 'invalid' has the effect of
  4540. + rendering it inoperative. The internal effect
  4541. + (row removal) is implementation dependent."
  4542. + ::= { ospfAreaAggregateEntry 5 }
  4543. +
  4544. +
  4545. + ospfAreaAggregateEffect OBJECT-TYPE
  4546. + SYNTAX INTEGER {
  4547. + advertiseMatching (1),
  4548. + doNotAdvertiseMatching (2)
  4549. + }
  4550. + MAX-ACCESS read-create
  4551. + STATUS current
  4552. + DESCRIPTION
  4553. + "Subnets subsumed by ranges either trigger the
  4554. + advertisement of the indicated aggregate (ad-
  4555. + vertiseMatching), or result in the subnet's not
  4556. + being advertised at all outside the area."
  4557. + DEFVAL { advertiseMatching }
  4558. + ::= { ospfAreaAggregateEntry 6 }
  4559. +
  4560. +
  4561. +-- conformance information
  4562. +
  4563. +ospfConformance OBJECT IDENTIFIER ::= { ospf 15 }
  4564. +
  4565. +ospfGroups OBJECT IDENTIFIER ::= { ospfConformance 1 }
  4566. +ospfCompliances OBJECT IDENTIFIER ::= { ospfConformance 2 }
  4567. +
  4568. +-- compliance statements
  4569. +
  4570. + ospfCompliance MODULE-COMPLIANCE
  4571. + STATUS current
  4572. + DESCRIPTION
  4573. + "The compliance statement "
  4574. + MODULE -- this module
  4575. + MANDATORY-GROUPS {
  4576. + ospfBasicGroup,
  4577. + ospfAreaGroup,
  4578. + ospfStubAreaGroup,
  4579. + ospfIfGroup,
  4580. + ospfIfMetricGroup,
  4581. + ospfVirtIfGroup,
  4582. + ospfNbrGroup,
  4583. + ospfVirtNbrGroup,
  4584. + ospfAreaAggregateGroup
  4585. + }
  4586. + ::= { ospfCompliances 1 }
  4587. +
  4588. +
  4589. +-- units of conformance
  4590. +
  4591. + ospfBasicGroup OBJECT-GROUP
  4592. + OBJECTS {
  4593. + ospfRouterId,
  4594. + ospfAdminStat,
  4595. + ospfVersionNumber,
  4596. + ospfAreaBdrRtrStatus,
  4597. + ospfASBdrRtrStatus,
  4598. + ospfExternLsaCount,
  4599. + ospfExternLsaCksumSum,
  4600. + ospfTOSSupport,
  4601. + ospfOriginateNewLsas,
  4602. + ospfRxNewLsas,
  4603. + ospfExtLsdbLimit,
  4604. + ospfMulticastExtensions,
  4605. + ospfExitOverflowInterval,
  4606. + ospfDemandExtensions
  4607. + }
  4608. + STATUS current
  4609. + DESCRIPTION
  4610. + "These objects are required for OSPF systems."
  4611. + ::= { ospfGroups 1 }
  4612. +
  4613. +
  4614. + ospfAreaGroup OBJECT-GROUP
  4615. + OBJECTS {
  4616. + ospfAreaId,
  4617. + ospfImportAsExtern,
  4618. + ospfSpfRuns,
  4619. + ospfAreaBdrRtrCount,
  4620. + ospfAsBdrRtrCount,
  4621. + ospfAreaLsaCount,
  4622. + ospfAreaLsaCksumSum,
  4623. + ospfAreaSummary,
  4624. + ospfAreaStatus
  4625. + }
  4626. + STATUS current
  4627. + DESCRIPTION
  4628. + "These objects are required for OSPF systems
  4629. + supporting areas."
  4630. + ::= { ospfGroups 2 }
  4631. +
  4632. +
  4633. + ospfStubAreaGroup OBJECT-GROUP
  4634. + OBJECTS {
  4635. + ospfStubAreaId,
  4636. + ospfStubTOS,
  4637. + ospfStubMetric,
  4638. + ospfStubStatus,
  4639. + ospfStubMetricType
  4640. + }
  4641. + STATUS current
  4642. + DESCRIPTION
  4643. + "These objects are required for OSPF systems
  4644. + supporting stub areas."
  4645. + ::= { ospfGroups 3 }
  4646. +
  4647. +
  4648. + ospfLsdbGroup OBJECT-GROUP
  4649. + OBJECTS {
  4650. + ospfLsdbAreaId,
  4651. + ospfLsdbType,
  4652. + ospfLsdbLsid,
  4653. + ospfLsdbRouterId,
  4654. + ospfLsdbSequence,
  4655. + ospfLsdbAge,
  4656. + ospfLsdbChecksum,
  4657. + ospfLsdbAdvertisement
  4658. + }
  4659. + STATUS current
  4660. + DESCRIPTION
  4661. + "These objects are required for OSPF systems
  4662. + that display their link state database."
  4663. + ::= { ospfGroups 4 }
  4664. +
  4665. +
  4666. + ospfAreaRangeGroup OBJECT-GROUP
  4667. + OBJECTS {
  4668. + ospfAreaRangeAreaId,
  4669. + ospfAreaRangeNet,
  4670. + ospfAreaRangeMask,
  4671. + ospfAreaRangeStatus,
  4672. + ospfAreaRangeEffect
  4673. + }
  4674. + STATUS obsolete
  4675. + DESCRIPTION
  4676. + "These objects are required for non-CIDR OSPF
  4677. + systems that support multiple areas."
  4678. + ::= { ospfGroups 5 }
  4679. +
  4680. +
  4681. + ospfHostGroup OBJECT-GROUP
  4682. + OBJECTS {
  4683. + ospfHostIpAddress,
  4684. + ospfHostTOS,
  4685. + ospfHostMetric,
  4686. + ospfHostStatus,
  4687. + ospfHostAreaID
  4688. + }
  4689. + STATUS current
  4690. + DESCRIPTION
  4691. + "These objects are required for OSPF systems
  4692. + that support attached hosts."
  4693. + ::= { ospfGroups 6 }
  4694. +
  4695. +
  4696. + ospfIfGroup OBJECT-GROUP
  4697. + OBJECTS {
  4698. + ospfIfIpAddress,
  4699. + ospfAddressLessIf,
  4700. + ospfIfAreaId,
  4701. + ospfIfType,
  4702. + ospfIfAdminStat,
  4703. + ospfIfRtrPriority,
  4704. + ospfIfTransitDelay,
  4705. + ospfIfRetransInterval,
  4706. + ospfIfHelloInterval,
  4707. + ospfIfRtrDeadInterval,
  4708. + ospfIfPollInterval,
  4709. + ospfIfState,
  4710. + ospfIfDesignatedRouter,
  4711. + ospfIfBackupDesignatedRouter,
  4712. + ospfIfEvents,
  4713. + ospfIfAuthType,
  4714. + ospfIfAuthKey,
  4715. + ospfIfStatus,
  4716. + ospfIfMulticastForwarding,
  4717. + ospfIfDemand
  4718. + }
  4719. + STATUS current
  4720. + DESCRIPTION
  4721. + "These objects are required for OSPF systems."
  4722. + ::= { ospfGroups 7 }
  4723. +
  4724. +
  4725. + ospfIfMetricGroup OBJECT-GROUP
  4726. + OBJECTS {
  4727. + ospfIfMetricIpAddress,
  4728. + ospfIfMetricAddressLessIf,
  4729. + ospfIfMetricTOS,
  4730. + ospfIfMetricValue,
  4731. + ospfIfMetricStatus
  4732. + }
  4733. + STATUS current
  4734. + DESCRIPTION
  4735. + "These objects are required for OSPF systems."
  4736. + ::= { ospfGroups 8 }
  4737. +
  4738. +
  4739. + ospfVirtIfGroup OBJECT-GROUP
  4740. + OBJECTS {
  4741. + ospfVirtIfAreaId,
  4742. + ospfVirtIfNeighbor,
  4743. + ospfVirtIfTransitDelay,
  4744. + ospfVirtIfRetransInterval,
  4745. + ospfVirtIfHelloInterval,
  4746. + ospfVirtIfRtrDeadInterval,
  4747. + ospfVirtIfState,
  4748. + ospfVirtIfEvents,
  4749. + ospfVirtIfAuthType,
  4750. + ospfVirtIfAuthKey,
  4751. + ospfVirtIfStatus
  4752. + }
  4753. + STATUS current
  4754. + DESCRIPTION
  4755. + "These objects are required for OSPF systems."
  4756. + ::= { ospfGroups 9 }
  4757. +
  4758. +
  4759. + ospfNbrGroup OBJECT-GROUP
  4760. + OBJECTS {
  4761. + ospfNbrIpAddr,
  4762. + ospfNbrAddressLessIndex,
  4763. + ospfNbrRtrId,
  4764. + ospfNbrOptions,
  4765. + ospfNbrPriority,
  4766. + ospfNbrState,
  4767. + ospfNbrEvents,
  4768. + ospfNbrLsRetransQLen,
  4769. + ospfNbmaNbrStatus,
  4770. + ospfNbmaNbrPermanence,
  4771. + ospfNbrHelloSuppressed
  4772. + }
  4773. + STATUS current
  4774. + DESCRIPTION
  4775. + "These objects are required for OSPF systems."
  4776. + ::= { ospfGroups 10 }
  4777. +
  4778. +
  4779. + ospfVirtNbrGroup OBJECT-GROUP
  4780. + OBJECTS {
  4781. + ospfVirtNbrArea,
  4782. + ospfVirtNbrRtrId,
  4783. + ospfVirtNbrIpAddr,
  4784. + ospfVirtNbrOptions,
  4785. + ospfVirtNbrState,
  4786. + ospfVirtNbrEvents,
  4787. + ospfVirtNbrLsRetransQLen,
  4788. + ospfVirtNbrHelloSuppressed
  4789. + }
  4790. + STATUS current
  4791. + DESCRIPTION
  4792. + "These objects are required for OSPF systems."
  4793. + ::= { ospfGroups 11 }
  4794. +
  4795. +
  4796. + ospfExtLsdbGroup OBJECT-GROUP
  4797. + OBJECTS {
  4798. + ospfExtLsdbType,
  4799. + ospfExtLsdbLsid,
  4800. + ospfExtLsdbRouterId,
  4801. + ospfExtLsdbSequence,
  4802. + ospfExtLsdbAge,
  4803. + ospfExtLsdbChecksum,
  4804. + ospfExtLsdbAdvertisement
  4805. + }
  4806. + STATUS current
  4807. + DESCRIPTION
  4808. + "These objects are required for OSPF systems
  4809. + that display their link state database."
  4810. + ::= { ospfGroups 12 }
  4811. +
  4812. +
  4813. + ospfAreaAggregateGroup OBJECT-GROUP
  4814. + OBJECTS {
  4815. + ospfAreaAggregateAreaID,
  4816. + ospfAreaAggregateLsdbType,
  4817. + ospfAreaAggregateNet,
  4818. + ospfAreaAggregateMask,
  4819. + ospfAreaAggregateStatus,
  4820. + ospfAreaAggregateEffect
  4821. + }
  4822. + STATUS current
  4823. + DESCRIPTION
  4824. + "These objects are required for OSPF systems."
  4825. + ::= { ospfGroups 13 }
  4826. +
  4827. +END
  4828. --- /dev/null
  4829. +++ b/mibs/OSPF-TRAP-MIB.txt
  4830. @@ -0,0 +1,443 @@
  4831. +OSPF-TRAP-MIB DEFINITIONS ::= BEGIN
  4832. +
  4833. + IMPORTS
  4834. + MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, IpAddress
  4835. + FROM SNMPv2-SMI
  4836. + MODULE-COMPLIANCE, OBJECT-GROUP
  4837. + FROM SNMPv2-CONF
  4838. + ospfRouterId, ospfIfIpAddress, ospfAddressLessIf, ospfIfState,
  4839. + ospfVirtIfAreaId, ospfVirtIfNeighbor, ospfVirtIfState,
  4840. + ospfNbrIpAddr, ospfNbrAddressLessIndex, ospfNbrRtrId,
  4841. + ospfNbrState, ospfVirtNbrArea, ospfVirtNbrRtrId, ospfVirtNbrState,
  4842. + ospfLsdbType, ospfLsdbLsid, ospfLsdbRouterId, ospfLsdbAreaId,
  4843. + ospfExtLsdbLimit, ospf
  4844. + FROM OSPF-MIB;
  4845. +
  4846. + ospfTrap MODULE-IDENTITY
  4847. + LAST-UPDATED "9501201225Z" -- Fri Jan 20 12:25:50 PST 1995
  4848. + ORGANIZATION "IETF OSPF Working Group"
  4849. + CONTACT-INFO
  4850. + " Fred Baker
  4851. + Postal: Cisco Systems
  4852. + 519 Lado Drive
  4853. + Santa Barbara, California 93111
  4854. + Tel: +1 805 681 0115
  4855. + E-Mail: fred@cisco.com
  4856. +
  4857. + Rob Coltun
  4858. + Postal: RainbowBridge Communications
  4859. + Tel: (301) 340-9416
  4860. + E-Mail: rcoltun@rainbow-bridge.com"
  4861. + DESCRIPTION
  4862. + "The MIB module to describe traps for the OSPF
  4863. + Version 2 Protocol."
  4864. + ::= { ospf 16 }
  4865. +
  4866. +-- Trap Support Objects
  4867. +
  4868. +-- The following are support objects for the OSPF traps.
  4869. +
  4870. +ospfTrapControl OBJECT IDENTIFIER ::= { ospfTrap 1 }
  4871. +ospfTraps OBJECT IDENTIFIER ::= { ospfTrap 2 }
  4872. +
  4873. + ospfSetTrap OBJECT-TYPE
  4874. + SYNTAX OCTET STRING (SIZE(4))
  4875. + MAX-ACCESS read-write
  4876. + STATUS current
  4877. + DESCRIPTION
  4878. + "A four-octet string serving as a bit map for
  4879. + the trap events defined by the OSPF traps. This
  4880. + object is used to enable and disable specific
  4881. + OSPF traps where a 1 in the bit field
  4882. + represents enabled. The right-most bit (least
  4883. + significant) represents trap 0."
  4884. + ::= { ospfTrapControl 1 }
  4885. +
  4886. +
  4887. + ospfConfigErrorType OBJECT-TYPE
  4888. + SYNTAX INTEGER {
  4889. + badVersion (1),
  4890. + areaMismatch (2),
  4891. + unknownNbmaNbr (3), -- Router is Dr eligible
  4892. + unknownVirtualNbr (4),
  4893. + authTypeMismatch(5),
  4894. + authFailure (6),
  4895. + netMaskMismatch (7),
  4896. + helloIntervalMismatch (8),
  4897. + deadIntervalMismatch (9),
  4898. + optionMismatch (10) }
  4899. + MAX-ACCESS read-only
  4900. + STATUS current
  4901. + DESCRIPTION
  4902. + "Potential types of configuration conflicts.
  4903. + Used by the ospfConfigError and ospfConfigVir-
  4904. + tError traps."
  4905. + ::= { ospfTrapControl 2 }
  4906. +
  4907. +
  4908. + ospfPacketType OBJECT-TYPE
  4909. + SYNTAX INTEGER {
  4910. + hello (1),
  4911. + dbDescript (2),
  4912. + lsReq (3),
  4913. + lsUpdate (4),
  4914. + lsAck (5) }
  4915. + MAX-ACCESS read-only
  4916. + STATUS current
  4917. + DESCRIPTION
  4918. + "OSPF packet types."
  4919. + ::= { ospfTrapControl 3 }
  4920. +
  4921. +
  4922. + ospfPacketSrc OBJECT-TYPE
  4923. + SYNTAX IpAddress
  4924. + MAX-ACCESS read-only
  4925. + STATUS current
  4926. + DESCRIPTION
  4927. + "The IP address of an inbound packet that can-
  4928. + not be identified by a neighbor instance."
  4929. + ::= { ospfTrapControl 4 }
  4930. +
  4931. +
  4932. +-- Traps
  4933. +
  4934. +
  4935. + ospfIfStateChange NOTIFICATION-TYPE
  4936. + OBJECTS {
  4937. + ospfRouterId, -- The originator of the trap
  4938. + ospfIfIpAddress,
  4939. + ospfAddressLessIf,
  4940. + ospfIfState -- The new state
  4941. + }
  4942. + STATUS current
  4943. + DESCRIPTION
  4944. + "An ospfIfStateChange trap signifies that there
  4945. + has been a change in the state of a non-virtual
  4946. + OSPF interface. This trap should be generated
  4947. + when the interface state regresses (e.g., goes
  4948. + from Dr to Down) or progresses to a terminal
  4949. + state (i.e., Point-to-Point, DR Other, Dr, or
  4950. + Backup)."
  4951. + ::= { ospfTraps 16 }
  4952. +
  4953. +
  4954. + ospfVirtIfStateChange NOTIFICATION-TYPE
  4955. + OBJECTS {
  4956. + ospfRouterId, -- The originator of the trap
  4957. + ospfVirtIfAreaId,
  4958. + ospfVirtIfNeighbor,
  4959. + ospfVirtIfState -- The new state
  4960. + }
  4961. + STATUS current
  4962. + DESCRIPTION
  4963. + "An ospfIfStateChange trap signifies that there
  4964. + has been a change in the state of an OSPF vir-
  4965. + tual interface.
  4966. + This trap should be generated when the inter-
  4967. + face state regresses (e.g., goes from Point-
  4968. + to-Point to Down) or progresses to a terminal
  4969. + state (i.e., Point-to-Point)."
  4970. + ::= { ospfTraps 1 }
  4971. +
  4972. +
  4973. + ospfNbrStateChange NOTIFICATION-TYPE
  4974. + OBJECTS {
  4975. + ospfRouterId, -- The originator of the trap
  4976. + ospfNbrIpAddr,
  4977. + ospfNbrAddressLessIndex,
  4978. + ospfNbrRtrId,
  4979. + ospfNbrState -- The new state
  4980. + }
  4981. + STATUS current
  4982. + DESCRIPTION
  4983. + "An ospfNbrStateChange trap signifies that
  4984. + there has been a change in the state of a non-
  4985. + virtual OSPF neighbor. This trap should be
  4986. + generated when the neighbor state regresses
  4987. + (e.g., goes from Attempt or Full to 1-Way or
  4988. + Down) or progresses to a terminal state (e.g.,
  4989. + 2-Way or Full). When an neighbor transitions
  4990. + from or to Full on non-broadcast multi-access
  4991. + and broadcast networks, the trap should be gen-
  4992. + erated by the designated router. A designated
  4993. + router transitioning to Down will be noted by
  4994. + ospfIfStateChange."
  4995. + ::= { ospfTraps 2 }
  4996. +
  4997. +
  4998. + ospfVirtNbrStateChange NOTIFICATION-TYPE
  4999. + OBJECTS {
  5000. + ospfRouterId, -- The originator of the trap
  5001. + ospfVirtNbrArea,
  5002. + ospfVirtNbrRtrId,
  5003. + ospfVirtNbrState -- The new state
  5004. + }
  5005. + STATUS current
  5006. + DESCRIPTION
  5007. + "An ospfIfStateChange trap signifies that there
  5008. + has been a change in the state of an OSPF vir-
  5009. + tual neighbor. This trap should be generated
  5010. + when the neighbor state regresses (e.g., goes
  5011. + from Attempt or Full to 1-Way or Down) or
  5012. + progresses to a terminal state (e.g., Full)."
  5013. + ::= { ospfTraps 3 }
  5014. + ospfIfConfigError NOTIFICATION-TYPE
  5015. + OBJECTS {
  5016. + ospfRouterId, -- The originator of the trap
  5017. + ospfIfIpAddress,
  5018. + ospfAddressLessIf,
  5019. + ospfPacketSrc, -- The source IP address
  5020. + ospfConfigErrorType, -- Type of error
  5021. + ospfPacketType
  5022. + }
  5023. + STATUS current
  5024. + DESCRIPTION
  5025. + "An ospfIfConfigError trap signifies that a
  5026. + packet has been received on a non-virtual in-
  5027. + terface from a router whose configuration
  5028. + parameters conflict with this router's confi-
  5029. + guration parameters. Note that the event op-
  5030. + tionMismatch should cause a trap only if it
  5031. + prevents an adjacency from forming."
  5032. + ::= { ospfTraps 4 }
  5033. +
  5034. +
  5035. + ospfVirtIfConfigError NOTIFICATION-TYPE
  5036. + OBJECTS {
  5037. + ospfRouterId, -- The originator of the trap
  5038. + ospfVirtIfAreaId,
  5039. + ospfVirtIfNeighbor,
  5040. + ospfConfigErrorType, -- Type of error
  5041. + ospfPacketType
  5042. + }
  5043. + STATUS current
  5044. + DESCRIPTION
  5045. + "An ospfConfigError trap signifies that a pack-
  5046. + et has been received on a virtual interface
  5047. + from a router whose configuration parameters
  5048. + conflict with this router's configuration
  5049. + parameters. Note that the event optionMismatch
  5050. + should cause a trap only if it prevents an ad-
  5051. + jacency from forming."
  5052. + ::= { ospfTraps 5 }
  5053. +
  5054. +
  5055. + ospfIfAuthFailure NOTIFICATION-TYPE
  5056. + OBJECTS {
  5057. + ospfRouterId, -- The originator of the trap
  5058. + ospfIfIpAddress,
  5059. + ospfAddressLessIf,
  5060. + ospfPacketSrc, -- The source IP address
  5061. + ospfConfigErrorType, -- authTypeMismatch or
  5062. + -- authFailure
  5063. + ospfPacketType
  5064. + }
  5065. + STATUS current
  5066. + DESCRIPTION
  5067. + "An ospfIfAuthFailure trap signifies that a
  5068. + packet has been received on a non-virtual in-
  5069. + terface from a router whose authentication key
  5070. + or authentication type conflicts with this
  5071. + router's authentication key or authentication
  5072. + type."
  5073. + ::= { ospfTraps 6 }
  5074. +
  5075. +
  5076. + ospfVirtIfAuthFailure NOTIFICATION-TYPE
  5077. + OBJECTS {
  5078. + ospfRouterId, -- The originator of the trap
  5079. + ospfVirtIfAreaId,
  5080. + ospfVirtIfNeighbor,
  5081. + ospfConfigErrorType, -- authTypeMismatch or
  5082. + -- authFailure
  5083. + ospfPacketType
  5084. + }
  5085. + STATUS current
  5086. + DESCRIPTION
  5087. + "An ospfVirtIfAuthFailure trap signifies that a
  5088. + packet has been received on a virtual interface
  5089. + from a router whose authentication key or au-
  5090. + thentication type conflicts with this router's
  5091. + authentication key or authentication type."
  5092. + ::= { ospfTraps 7 }
  5093. +
  5094. +
  5095. + ospfIfRxBadPacket NOTIFICATION-TYPE
  5096. + OBJECTS {
  5097. + ospfRouterId, -- The originator of the trap
  5098. + ospfIfIpAddress,
  5099. + ospfAddressLessIf,
  5100. + ospfPacketSrc, -- The source IP address
  5101. + ospfPacketType
  5102. + }
  5103. + STATUS current
  5104. + DESCRIPTION
  5105. + "An ospfIfRxBadPacket trap signifies that an
  5106. + OSPF packet has been received on a non-virtual
  5107. + interface that cannot be parsed."
  5108. + ::= { ospfTraps 8 }
  5109. +
  5110. + ospfVirtIfRxBadPacket NOTIFICATION-TYPE
  5111. + OBJECTS {
  5112. + ospfRouterId, -- The originator of the trap
  5113. + ospfVirtIfAreaId,
  5114. + ospfVirtIfNeighbor,
  5115. + ospfPacketType
  5116. + }
  5117. + STATUS current
  5118. + DESCRIPTION
  5119. + "An ospfRxBadPacket trap signifies that an OSPF
  5120. + packet has been received on a virtual interface
  5121. + that cannot be parsed."
  5122. + ::= { ospfTraps 9 }
  5123. +
  5124. +
  5125. + ospfTxRetransmit NOTIFICATION-TYPE
  5126. + OBJECTS {
  5127. + ospfRouterId, -- The originator of the trap
  5128. + ospfIfIpAddress,
  5129. + ospfAddressLessIf,
  5130. + ospfNbrRtrId, -- Destination
  5131. + ospfPacketType,
  5132. + ospfLsdbType,
  5133. + ospfLsdbLsid,
  5134. + ospfLsdbRouterId
  5135. + }
  5136. + STATUS current
  5137. + DESCRIPTION
  5138. + "An ospfTxRetransmit trap signifies than an
  5139. + OSPF packet has been retransmitted on a non-
  5140. + virtual interface. All packets that may be re-
  5141. + transmitted are associated with an LSDB entry.
  5142. + The LS type, LS ID, and Router ID are used to
  5143. + identify the LSDB entry."
  5144. + ::= { ospfTraps 10 }
  5145. +
  5146. +
  5147. + ospfVirtIfTxRetransmit NOTIFICATION-TYPE
  5148. + OBJECTS {
  5149. + ospfRouterId, -- The originator of the trap
  5150. + ospfVirtIfAreaId,
  5151. + ospfVirtIfNeighbor,
  5152. + ospfPacketType,
  5153. + ospfLsdbType,
  5154. + ospfLsdbLsid,
  5155. + ospfLsdbRouterId
  5156. + }
  5157. + STATUS current
  5158. + DESCRIPTION
  5159. + "An ospfTxRetransmit trap signifies than an
  5160. + OSPF packet has been retransmitted on a virtual
  5161. + interface. All packets that may be retransmit-
  5162. + ted are associated with an LSDB entry. The LS
  5163. + type, LS ID, and Router ID are used to identify
  5164. + the LSDB entry."
  5165. + ::= { ospfTraps 11 }
  5166. +
  5167. +
  5168. + ospfOriginateLsa NOTIFICATION-TYPE
  5169. + OBJECTS {
  5170. + ospfRouterId, -- The originator of the trap
  5171. + ospfLsdbAreaId, -- 0.0.0.0 for AS Externals
  5172. + ospfLsdbType,
  5173. + ospfLsdbLsid,
  5174. + ospfLsdbRouterId
  5175. + }
  5176. + STATUS current
  5177. + DESCRIPTION
  5178. + "An ospfOriginateLsa trap signifies that a new
  5179. + LSA has been originated by this router. This
  5180. + trap should not be invoked for simple refreshes
  5181. + of LSAs (which happesn every 30 minutes), but
  5182. + instead will only be invoked when an LSA is
  5183. + (re)originated due to a topology change. Addi-
  5184. + tionally, this trap does not include LSAs that
  5185. + are being flushed because they have reached
  5186. + MaxAge."
  5187. + ::= { ospfTraps 12 }
  5188. +
  5189. +
  5190. + ospfMaxAgeLsa NOTIFICATION-TYPE
  5191. + OBJECTS {
  5192. + ospfRouterId, -- The originator of the trap
  5193. + ospfLsdbAreaId, -- 0.0.0.0 for AS Externals
  5194. + ospfLsdbType,
  5195. + ospfLsdbLsid,
  5196. + ospfLsdbRouterId
  5197. + }
  5198. + STATUS current
  5199. + DESCRIPTION
  5200. + "An ospfMaxAgeLsa trap signifies that one of
  5201. + the LSA in the router's link-state database has
  5202. + aged to MaxAge."
  5203. + ::= { ospfTraps 13 }
  5204. +
  5205. +
  5206. + ospfLsdbOverflow NOTIFICATION-TYPE
  5207. + OBJECTS {
  5208. + ospfRouterId, -- The originator of the trap
  5209. + ospfExtLsdbLimit
  5210. + }
  5211. + STATUS current
  5212. + DESCRIPTION
  5213. + "An ospfLsdbOverflow trap signifies that the
  5214. + number of LSAs in the router's link-state data-
  5215. + base has exceeded ospfExtLsdbLimit."
  5216. + ::= { ospfTraps 14 }
  5217. +
  5218. +
  5219. + ospfLsdbApproachingOverflow NOTIFICATION-TYPE
  5220. + OBJECTS {
  5221. + ospfRouterId, -- The originator of the trap
  5222. + ospfExtLsdbLimit
  5223. + }
  5224. + STATUS current
  5225. + DESCRIPTION
  5226. + "An ospfLsdbApproachingOverflow trap signifies
  5227. + that the number of LSAs in the router's link-
  5228. + state database has exceeded ninety percent of
  5229. + ospfExtLsdbLimit."
  5230. + ::= { ospfTraps 15 }
  5231. +
  5232. +
  5233. +-- conformance information
  5234. +
  5235. +ospfTrapConformance OBJECT IDENTIFIER ::= { ospfTrap 3 }
  5236. +
  5237. +ospfTrapGroups OBJECT IDENTIFIER ::= { ospfTrapConformance 1 }
  5238. +ospfTrapCompliances OBJECT IDENTIFIER ::= { ospfTrapConformance 2 }
  5239. +
  5240. +-- compliance statements
  5241. +
  5242. + ospfTrapCompliance MODULE-COMPLIANCE
  5243. + STATUS current
  5244. + DESCRIPTION
  5245. + "The compliance statement "
  5246. + MODULE -- this module
  5247. + MANDATORY-GROUPS { ospfTrapControlGroup }
  5248. +
  5249. +
  5250. + GROUP ospfTrapControlGroup
  5251. + DESCRIPTION
  5252. + "This group is optional but recommended for all
  5253. + OSPF systems"
  5254. + ::= { ospfTrapCompliances 1 }
  5255. +
  5256. +
  5257. +-- units of conformance
  5258. +
  5259. + ospfTrapControlGroup OBJECT-GROUP
  5260. + OBJECTS {
  5261. + ospfSetTrap,
  5262. + ospfConfigErrorType,
  5263. + ospfPacketType,
  5264. + ospfPacketSrc
  5265. + }
  5266. + STATUS current
  5267. + DESCRIPTION
  5268. + "These objects are required to control traps
  5269. + from OSPF systems."
  5270. + ::= { ospfTrapGroups 1 }
  5271. +
  5272. +
  5273. +END
  5274. --- /dev/null
  5275. +++ b/mibs/RIPv2-MIB.txt
  5276. @@ -0,0 +1,530 @@
  5277. + RIPv2-MIB DEFINITIONS ::= BEGIN
  5278. +
  5279. + IMPORTS
  5280. + MODULE-IDENTITY, OBJECT-TYPE, Counter32,
  5281. + TimeTicks, IpAddress FROM SNMPv2-SMI
  5282. + TEXTUAL-CONVENTION, RowStatus FROM SNMPv2-TC
  5283. + MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
  5284. + mib-2 FROM RFC1213-MIB;
  5285. +
  5286. + -- This MIB module uses the extended OBJECT-TYPE macro as
  5287. + -- defined in [9].
  5288. +
  5289. + rip2 MODULE-IDENTITY
  5290. + LAST-UPDATED "9407272253Z" -- Wed Jul 27 22:53:04 PDT 1994
  5291. + ORGANIZATION "IETF RIP-II Working Group"
  5292. + CONTACT-INFO
  5293. + " Fred Baker
  5294. + Postal: Cisco Systems
  5295. + 519 Lado Drive
  5296. + Santa Barbara, California 93111
  5297. + Tel: +1 805 681 0115
  5298. + E-Mail: fbaker@cisco.com
  5299. +
  5300. + Postal: Gary Malkin
  5301. + Xylogics, Inc.
  5302. + 53 Third Avenue
  5303. + Burlington, MA 01803
  5304. +
  5305. + Phone: (617) 272-8140
  5306. + EMail: gmalkin@Xylogics.COM"
  5307. + DESCRIPTION
  5308. + "The MIB module to describe the RIP2 Version 2 Protocol"
  5309. + ::= { mib-2 23 }
  5310. +
  5311. + -- RIP-2 Management Information Base
  5312. +
  5313. + -- the RouteTag type represents the contents of the
  5314. + -- Route Domain field in the packet header or route entry.
  5315. + -- The use of the Route Domain is deprecated.
  5316. +
  5317. + RouteTag ::= TEXTUAL-CONVENTION
  5318. + STATUS current
  5319. + DESCRIPTION
  5320. + "the RouteTag type represents the contents of the Route Domain
  5321. + field in the packet header or route entry"
  5322. + SYNTAX OCTET STRING (SIZE (2))
  5323. +
  5324. +--4.1 Global Counters
  5325. +
  5326. +-- The RIP-2 Globals Group.
  5327. +-- Implementation of this group is mandatory for systems
  5328. +-- which implement RIP-2.
  5329. +
  5330. +-- These counters are intended to facilitate debugging quickly
  5331. +-- changing routes or failing neighbors
  5332. +
  5333. +rip2Globals OBJECT IDENTIFIER ::= { rip2 1 }
  5334. +
  5335. + rip2GlobalRouteChanges OBJECT-TYPE
  5336. + SYNTAX Counter32
  5337. + MAX-ACCESS read-only
  5338. + STATUS current
  5339. + DESCRIPTION
  5340. + "The number of route changes made to the IP Route
  5341. + Database by RIP. This does not include the refresh
  5342. + of a route's age."
  5343. + ::= { rip2Globals 1 }
  5344. +
  5345. + rip2GlobalQueries OBJECT-TYPE
  5346. + SYNTAX Counter32
  5347. + MAX-ACCESS read-only
  5348. + STATUS current
  5349. + DESCRIPTION
  5350. + "The number of responses sent to RIP queries
  5351. + from other systems."
  5352. + ::= { rip2Globals 2 }
  5353. +
  5354. +--4.2 RIP Interface Tables
  5355. +
  5356. +-- RIP Interfaces Groups
  5357. +-- Implementation of these Groups is mandatory for systems
  5358. +-- which implement RIP-2.
  5359. +
  5360. +-- The RIP Interface Status Table.
  5361. +
  5362. + rip2IfStatTable OBJECT-TYPE
  5363. + SYNTAX SEQUENCE OF Rip2IfStatEntry
  5364. + MAX-ACCESS not-accessible
  5365. + STATUS current
  5366. + DESCRIPTION
  5367. + "A list of subnets which require separate
  5368. + status monitoring in RIP."
  5369. + ::= { rip2 2 }
  5370. +
  5371. + rip2IfStatEntry OBJECT-TYPE
  5372. + SYNTAX Rip2IfStatEntry
  5373. + MAX-ACCESS not-accessible
  5374. + STATUS current
  5375. + DESCRIPTION
  5376. + "A Single Routing Domain in a single Subnet."
  5377. + INDEX { rip2IfStatAddress }
  5378. + ::= { rip2IfStatTable 1 }
  5379. +
  5380. + Rip2IfStatEntry ::=
  5381. + SEQUENCE {
  5382. + rip2IfStatAddress
  5383. + IpAddress,
  5384. + rip2IfStatRcvBadPackets
  5385. + Counter32,
  5386. + rip2IfStatRcvBadRoutes
  5387. + Counter32,
  5388. + rip2IfStatSentUpdates
  5389. + Counter32,
  5390. + rip2IfStatStatus
  5391. + RowStatus
  5392. + }
  5393. +
  5394. + rip2IfStatAddress OBJECT-TYPE
  5395. + SYNTAX IpAddress
  5396. + MAX-ACCESS read-only
  5397. + STATUS current
  5398. + DESCRIPTION
  5399. + "The IP Address of this system on the indicated
  5400. + subnet. For unnumbered interfaces, the value 0.0.0.N,
  5401. + where the least significant 24 bits (N) is the ifIndex
  5402. + for the IP Interface in network byte order."
  5403. + ::= { rip2IfStatEntry 1 }
  5404. +
  5405. + rip2IfStatRcvBadPackets OBJECT-TYPE
  5406. + SYNTAX Counter32
  5407. + MAX-ACCESS read-only
  5408. + STATUS current
  5409. + DESCRIPTION
  5410. + "The number of RIP response packets received by
  5411. + the RIP process which were subsequently discarded
  5412. + for any reason (e.g. a version 0 packet, or an
  5413. + unknown command type)."
  5414. + ::= { rip2IfStatEntry 2 }
  5415. +
  5416. + rip2IfStatRcvBadRoutes OBJECT-TYPE
  5417. + SYNTAX Counter32
  5418. + MAX-ACCESS read-only
  5419. + STATUS current
  5420. + DESCRIPTION
  5421. + "The number of routes, in valid RIP packets,
  5422. + which were ignored for any reason (e.g. unknown
  5423. + address family, or invalid metric)."
  5424. + ::= { rip2IfStatEntry 3 }
  5425. +
  5426. + rip2IfStatSentUpdates OBJECT-TYPE
  5427. + SYNTAX Counter32
  5428. + MAX-ACCESS read-only
  5429. + STATUS current
  5430. + DESCRIPTION
  5431. + "The number of triggered RIP updates actually
  5432. + sent on this interface. This explicitly does
  5433. + NOT include full updates sent containing new
  5434. + information."
  5435. + ::= { rip2IfStatEntry 4 }
  5436. +
  5437. + rip2IfStatStatus OBJECT-TYPE
  5438. + SYNTAX RowStatus
  5439. + MAX-ACCESS read-create
  5440. + STATUS current
  5441. + DESCRIPTION
  5442. + "Writing invalid has the effect of deleting
  5443. + this interface."
  5444. + ::= { rip2IfStatEntry 5 }
  5445. +
  5446. +-- The RIP Interface Configuration Table.
  5447. +
  5448. + rip2IfConfTable OBJECT-TYPE
  5449. + SYNTAX SEQUENCE OF Rip2IfConfEntry
  5450. + MAX-ACCESS not-accessible
  5451. + STATUS current
  5452. + DESCRIPTION
  5453. + "A list of subnets which require separate
  5454. + configuration in RIP."
  5455. + ::= { rip2 3 }
  5456. +
  5457. + rip2IfConfEntry OBJECT-TYPE
  5458. + SYNTAX Rip2IfConfEntry
  5459. + MAX-ACCESS not-accessible
  5460. + STATUS current
  5461. + DESCRIPTION
  5462. + "A Single Routing Domain in a single Subnet."
  5463. + INDEX { rip2IfConfAddress }
  5464. + ::= { rip2IfConfTable 1 }
  5465. +
  5466. + Rip2IfConfEntry ::=
  5467. + SEQUENCE {
  5468. + rip2IfConfAddress
  5469. + IpAddress,
  5470. + rip2IfConfDomain
  5471. + RouteTag,
  5472. + rip2IfConfAuthType
  5473. + INTEGER,
  5474. + rip2IfConfAuthKey
  5475. + OCTET STRING (SIZE(0..16)),
  5476. + rip2IfConfSend
  5477. + INTEGER,
  5478. + rip2IfConfReceive
  5479. + INTEGER,
  5480. + rip2IfConfDefaultMetric
  5481. + INTEGER,
  5482. + rip2IfConfStatus
  5483. + RowStatus,
  5484. + rip2IfConfSrcAddress
  5485. + IpAddress
  5486. + }
  5487. +
  5488. + rip2IfConfAddress OBJECT-TYPE
  5489. + SYNTAX IpAddress
  5490. + MAX-ACCESS read-only
  5491. + STATUS current
  5492. + DESCRIPTION
  5493. + "The IP Address of this system on the indicated
  5494. + subnet. For unnumbered interfaces, the value 0.0.0.N,
  5495. + where the least significant 24 bits (N) is the ifIndex
  5496. + for the IP Interface in network byte order."
  5497. + ::= { rip2IfConfEntry 1 }
  5498. +
  5499. + rip2IfConfDomain OBJECT-TYPE
  5500. + SYNTAX RouteTag
  5501. + MAX-ACCESS read-create
  5502. + STATUS obsolete
  5503. + DESCRIPTION
  5504. + "Value inserted into the Routing Domain field
  5505. + of all RIP packets sent on this interface."
  5506. + DEFVAL { '0000'h }
  5507. + ::= { rip2IfConfEntry 2 }
  5508. +
  5509. + rip2IfConfAuthType OBJECT-TYPE
  5510. + SYNTAX INTEGER {
  5511. + noAuthentication (1),
  5512. + simplePassword (2),
  5513. + md5 (3)
  5514. + }
  5515. + MAX-ACCESS read-create
  5516. + STATUS current
  5517. + DESCRIPTION
  5518. + "The type of Authentication used on this
  5519. + interface."
  5520. + DEFVAL { noAuthentication }
  5521. + ::= { rip2IfConfEntry 3 }
  5522. +
  5523. + rip2IfConfAuthKey OBJECT-TYPE
  5524. + SYNTAX OCTET STRING (SIZE(0..16))
  5525. + MAX-ACCESS read-create
  5526. + STATUS current
  5527. + DESCRIPTION
  5528. + "The value to be used as the Authentication Key
  5529. + whenever the corresponding instance of
  5530. + rip2IfConfAuthType has a value other than
  5531. + noAuthentication. A modification of the corresponding
  5532. + instance of rip2IfConfAuthType does not modify
  5533. + the rip2IfConfAuthKey value. If a string shorter
  5534. + than 16 octets is supplied, it will be left-
  5535. + justified and padded to 16 octets, on the right,
  5536. + with nulls (0x00).
  5537. +
  5538. + Reading this object always results in an OCTET
  5539. + STRING of length zero; authentication may not
  5540. + be bypassed by reading the MIB object."
  5541. + DEFVAL { ''h }
  5542. + ::= { rip2IfConfEntry 4 }
  5543. +
  5544. + rip2IfConfSend OBJECT-TYPE
  5545. + SYNTAX INTEGER {
  5546. + doNotSend (1),
  5547. + ripVersion1 (2),
  5548. + rip1Compatible (3),
  5549. + ripVersion2 (4),
  5550. + ripV1Demand (5),
  5551. + ripV2Demand (6)
  5552. + }
  5553. + MAX-ACCESS read-create
  5554. + STATUS current
  5555. + DESCRIPTION
  5556. + "What the router sends on this interface.
  5557. + ripVersion1 implies sending RIP updates compliant
  5558. + with RFC 1058. rip1Compatible implies
  5559. + broadcasting RIP-2 updates using RFC 1058 route
  5560. + subsumption rules. ripVersion2 implies
  5561. + multicasting RIP-2 updates. ripV1Demand indicates
  5562. + the use of Demand RIP on a WAN interface under RIP
  5563. + Version 1 rules. ripV2Demand indicates the use of
  5564. + Demand RIP on a WAN interface under Version 2 rules."
  5565. + DEFVAL { rip1Compatible }
  5566. + ::= { rip2IfConfEntry 5 }
  5567. +
  5568. + rip2IfConfReceive OBJECT-TYPE
  5569. + SYNTAX INTEGER {
  5570. + rip1 (1),
  5571. + rip2 (2),
  5572. + rip1OrRip2 (3),
  5573. + doNotRecieve (4)
  5574. + }
  5575. + MAX-ACCESS read-create
  5576. + STATUS current
  5577. + DESCRIPTION
  5578. + "This indicates which version of RIP updates
  5579. + are to be accepted. Note that rip2 and
  5580. + rip1OrRip2 implies reception of multicast
  5581. + packets."
  5582. + DEFVAL { rip1OrRip2 }
  5583. + ::= { rip2IfConfEntry 6 }
  5584. +
  5585. + rip2IfConfDefaultMetric OBJECT-TYPE
  5586. + SYNTAX INTEGER ( 0..15 )
  5587. + MAX-ACCESS read-create
  5588. + STATUS current
  5589. + DESCRIPTION
  5590. + "This variable indicates the metric that is to
  5591. + be used for the default route entry in RIP updates
  5592. + originated on this interface. A value of zero
  5593. + indicates that no default route should be
  5594. + originated; in this case, a default route via
  5595. + another router may be propagated."
  5596. + ::= { rip2IfConfEntry 7 }
  5597. +
  5598. + rip2IfConfStatus OBJECT-TYPE
  5599. + SYNTAX RowStatus
  5600. + MAX-ACCESS read-create
  5601. + STATUS current
  5602. + DESCRIPTION
  5603. + "Writing invalid has the effect of deleting
  5604. + this interface."
  5605. + ::= { rip2IfConfEntry 8 }
  5606. +
  5607. + rip2IfConfSrcAddress OBJECT-TYPE
  5608. + SYNTAX IpAddress
  5609. + MAX-ACCESS read-create
  5610. + STATUS current
  5611. + DESCRIPTION
  5612. + "The IP Address this system will use as a source
  5613. + address on this interface. If it is a numbered
  5614. + interface, this MUST be the same value as
  5615. + rip2IfConfAddress. On unnumbered interfaces,
  5616. + it must be the value of rip2IfConfAddress for
  5617. + some interface on the system."
  5618. + ::= { rip2IfConfEntry 9 }
  5619. +
  5620. +--4.3 Peer Table
  5621. +
  5622. +-- Peer Table
  5623. +
  5624. +-- The RIP Peer Group
  5625. +-- Implementation of this Group is Optional
  5626. +
  5627. +-- This group provides information about active peer
  5628. +-- relationships intended to assist in debugging. An
  5629. +-- active peer is a router from which a valid RIP
  5630. +-- updated has been heard in the last 180 seconds.
  5631. +
  5632. + rip2PeerTable OBJECT-TYPE
  5633. + SYNTAX SEQUENCE OF Rip2PeerEntry
  5634. + MAX-ACCESS not-accessible
  5635. + STATUS current
  5636. + DESCRIPTION
  5637. + "A list of RIP Peers."
  5638. + ::= { rip2 4 }
  5639. +
  5640. + rip2PeerEntry OBJECT-TYPE
  5641. + SYNTAX Rip2PeerEntry
  5642. + MAX-ACCESS not-accessible
  5643. + STATUS current
  5644. + DESCRIPTION
  5645. + "Information regarding a single routing peer."
  5646. + INDEX { rip2PeerAddress, rip2PeerDomain }
  5647. + ::= { rip2PeerTable 1 }
  5648. +
  5649. + Rip2PeerEntry ::=
  5650. + SEQUENCE {
  5651. + rip2PeerAddress
  5652. + IpAddress,
  5653. + rip2PeerDomain
  5654. + RouteTag,
  5655. + rip2PeerLastUpdate
  5656. + TimeTicks,
  5657. + rip2PeerVersion
  5658. + INTEGER,
  5659. + rip2PeerRcvBadPackets
  5660. + Counter32,
  5661. + rip2PeerRcvBadRoutes
  5662. + Counter32
  5663. + }
  5664. +
  5665. + rip2PeerAddress OBJECT-TYPE
  5666. + SYNTAX IpAddress
  5667. + MAX-ACCESS read-only
  5668. + STATUS current
  5669. + DESCRIPTION
  5670. + "The IP Address that the peer is using as its source
  5671. + address. Note that on an unnumbered link, this may
  5672. + not be a member of any subnet on the system."
  5673. + ::= { rip2PeerEntry 1 }
  5674. +
  5675. + rip2PeerDomain OBJECT-TYPE
  5676. + SYNTAX RouteTag
  5677. + MAX-ACCESS read-only
  5678. + STATUS current
  5679. + DESCRIPTION
  5680. + "The value in the Routing Domain field in RIP
  5681. + packets received from the peer. As domain suuport
  5682. + is deprecated, this must be zero."
  5683. + ::= { rip2PeerEntry 2 }
  5684. +
  5685. + rip2PeerLastUpdate OBJECT-TYPE
  5686. + SYNTAX TimeTicks
  5687. + MAX-ACCESS read-only
  5688. + STATUS current
  5689. + DESCRIPTION
  5690. + "The value of sysUpTime when the most recent
  5691. + RIP update was received from this system."
  5692. + ::= { rip2PeerEntry 3 }
  5693. +
  5694. + rip2PeerVersion OBJECT-TYPE
  5695. + SYNTAX INTEGER ( 0..255 )
  5696. + MAX-ACCESS read-only
  5697. + STATUS current
  5698. + DESCRIPTION
  5699. + "The RIP version number in the header of the
  5700. + last RIP packet received."
  5701. + ::= { rip2PeerEntry 4 }
  5702. +
  5703. + rip2PeerRcvBadPackets OBJECT-TYPE
  5704. + SYNTAX Counter32
  5705. + MAX-ACCESS read-only
  5706. + STATUS current
  5707. + DESCRIPTION
  5708. + "The number of RIP response packets from this
  5709. + peer discarded as invalid."
  5710. + ::= { rip2PeerEntry 5 }
  5711. +
  5712. +
  5713. + rip2PeerRcvBadRoutes OBJECT-TYPE
  5714. + SYNTAX Counter32
  5715. + MAX-ACCESS read-only
  5716. + STATUS current
  5717. + DESCRIPTION
  5718. + "The number of routes from this peer that were
  5719. + ignored because the entry format was invalid."
  5720. + ::= { rip2PeerEntry 6 }
  5721. +
  5722. +-- conformance information
  5723. +
  5724. +rip2Conformance OBJECT IDENTIFIER ::= { rip2 5 }
  5725. +
  5726. +rip2Groups OBJECT IDENTIFIER ::= { rip2Conformance 1 }
  5727. +rip2Compliances OBJECT IDENTIFIER ::= { rip2Conformance 2 }
  5728. +
  5729. +-- compliance statements
  5730. +rip2Compliance MODULE-COMPLIANCE
  5731. + STATUS current
  5732. + DESCRIPTION
  5733. + "The compliance statement "
  5734. + MODULE -- this module
  5735. + MANDATORY-GROUPS {
  5736. + rip2GlobalGroup,
  5737. + rip2IfStatGroup,
  5738. + rip2IfConfGroup,
  5739. + rip2PeerGroup
  5740. + }
  5741. + GROUP rip2GlobalGroup
  5742. + DESCRIPTION
  5743. + "This group defines global controls for RIP-II systems."
  5744. + GROUP rip2IfStatGroup
  5745. + DESCRIPTION
  5746. + "This group defines interface statistics for RIP-II systems."
  5747. + GROUP rip2IfConfGroup
  5748. + DESCRIPTION
  5749. + "This group defines interface configuration for RIP-II systems."
  5750. + GROUP rip2PeerGroup
  5751. + DESCRIPTION
  5752. + "This group defines peer information for RIP-II systems."
  5753. + ::= { rip2Compliances 1 }
  5754. +
  5755. +-- units of conformance
  5756. +
  5757. +rip2GlobalGroup OBJECT-GROUP
  5758. + OBJECTS {
  5759. + rip2GlobalRouteChanges,
  5760. + rip2GlobalQueries
  5761. + }
  5762. + STATUS current
  5763. + DESCRIPTION
  5764. + "This group defines global controls for RIP-II systems."
  5765. + ::= { rip2Groups 1 }
  5766. +rip2IfStatGroup OBJECT-GROUP
  5767. + OBJECTS {
  5768. + rip2IfStatAddress,
  5769. + rip2IfStatRcvBadPackets,
  5770. + rip2IfStatRcvBadRoutes,
  5771. + rip2IfStatSentUpdates,
  5772. + rip2IfStatStatus
  5773. + }
  5774. + STATUS current
  5775. + DESCRIPTION
  5776. + "This group defines interface statistics for RIP-II systems."
  5777. + ::= { rip2Groups 2 }
  5778. +rip2IfConfGroup OBJECT-GROUP
  5779. + OBJECTS {
  5780. + rip2IfConfAddress,
  5781. + rip2IfConfAuthType,
  5782. + rip2IfConfAuthKey,
  5783. + rip2IfConfSend,
  5784. + rip2IfConfReceive,
  5785. + rip2IfConfDefaultMetric,
  5786. + rip2IfConfStatus,
  5787. + rip2IfConfSrcAddress
  5788. + }
  5789. + STATUS current
  5790. + DESCRIPTION
  5791. + "This group defines interface configuration for RIP-II systems."
  5792. + ::= { rip2Groups 3 }
  5793. +rip2PeerGroup OBJECT-GROUP
  5794. + OBJECTS {
  5795. + rip2PeerAddress,
  5796. + rip2PeerDomain,
  5797. + rip2PeerLastUpdate,
  5798. + rip2PeerVersion,
  5799. + rip2PeerRcvBadPackets,
  5800. + rip2PeerRcvBadRoutes
  5801. + }
  5802. + STATUS current
  5803. + DESCRIPTION
  5804. + "This group defines peer information for RIP-II systems."
  5805. + ::= { rip2Groups 4 }
  5806. +END
  5807. --- /dev/null
  5808. +++ b/mibs/SOURCE-ROUTING-MIB.txt
  5809. @@ -0,0 +1,452 @@
  5810. +SOURCE-ROUTING-MIB DEFINITIONS ::= BEGIN
  5811. +
  5812. +IMPORTS
  5813. + Counter, Gauge
  5814. + FROM RFC1155-SMI
  5815. + dot1dBridge, dot1dSr
  5816. + FROM BRIDGE-MIB
  5817. + OBJECT-TYPE
  5818. + FROM RFC-1212;
  5819. +
  5820. +-- groups in the SR MIB
  5821. +
  5822. +-- dot1dSr is imported from the Bridge MIB
  5823. +
  5824. +dot1dPortPair OBJECT IDENTIFIER ::= { dot1dBridge 10 }
  5825. +
  5826. +-- the dot1dSr group
  5827. +
  5828. +-- this group is implemented by those bridges that
  5829. +-- support the source route bridging mode, including Source
  5830. +-- Routing and SRT bridges.
  5831. +
  5832. +dot1dSrPortTable OBJECT-TYPE
  5833. + SYNTAX SEQUENCE OF Dot1dSrPortEntry
  5834. + ACCESS not-accessible
  5835. + STATUS mandatory
  5836. + DESCRIPTION
  5837. + "A table that contains information about every
  5838. + port that is associated with this source route
  5839. + bridge."
  5840. + ::= { dot1dSr 1 }
  5841. +
  5842. +dot1dSrPortEntry OBJECT-TYPE
  5843. + SYNTAX Dot1dSrPortEntry
  5844. + ACCESS not-accessible
  5845. + STATUS mandatory
  5846. + DESCRIPTION
  5847. + "A list of information for each port of a source
  5848. + route bridge."
  5849. + INDEX { dot1dSrPort }
  5850. +
  5851. + ::= { dot1dSrPortTable 1 }
  5852. +
  5853. +Dot1dSrPortEntry ::=
  5854. + SEQUENCE {
  5855. + dot1dSrPort
  5856. + INTEGER,
  5857. + dot1dSrPortHopCount
  5858. + INTEGER,
  5859. + dot1dSrPortLocalSegment
  5860. + INTEGER,
  5861. + dot1dSrPortBridgeNum
  5862. + INTEGER,
  5863. + dot1dSrPortTargetSegment
  5864. + INTEGER,
  5865. + dot1dSrPortLargestFrame
  5866. + INTEGER,
  5867. + dot1dSrPortSTESpanMode
  5868. + INTEGER,
  5869. + dot1dSrPortSpecInFrames
  5870. + Counter,
  5871. + dot1dSrPortSpecOutFrames
  5872. + Counter,
  5873. + dot1dSrPortApeInFrames
  5874. + Counter,
  5875. + dot1dSrPortApeOutFrames
  5876. + Counter,
  5877. + dot1dSrPortSteInFrames
  5878. + Counter,
  5879. + dot1dSrPortSteOutFrames
  5880. + Counter,
  5881. + dot1dSrPortSegmentMismatchDiscards
  5882. + Counter,
  5883. + dot1dSrPortDuplicateSegmentDiscards
  5884. + Counter,
  5885. + dot1dSrPortHopCountExceededDiscards
  5886. + Counter,
  5887. + dot1dSrPortDupLanIdOrTreeErrors
  5888. + Counter,
  5889. + dot1dSrPortLanIdMismatches
  5890. + Counter
  5891. + }
  5892. +
  5893. +dot1dSrPort OBJECT-TYPE
  5894. + SYNTAX INTEGER (1..65535)
  5895. + ACCESS read-only
  5896. + STATUS mandatory
  5897. + DESCRIPTION
  5898. + "The port number of the port for which this entry
  5899. +
  5900. + contains Source Route management information."
  5901. + ::= { dot1dSrPortEntry 1 }
  5902. +
  5903. +dot1dSrPortHopCount OBJECT-TYPE
  5904. + SYNTAX INTEGER
  5905. + ACCESS read-write
  5906. + STATUS mandatory
  5907. + DESCRIPTION
  5908. + "The maximum number of routing descriptors allowed
  5909. + in an All Paths or Spanning Tree Explorer frames."
  5910. + ::= { dot1dSrPortEntry 2 }
  5911. +
  5912. +dot1dSrPortLocalSegment OBJECT-TYPE
  5913. + SYNTAX INTEGER
  5914. + ACCESS read-write
  5915. + STATUS mandatory
  5916. + DESCRIPTION
  5917. + "The segment number that uniquely identifies the
  5918. + segment to which this port is connected. Current
  5919. + source routing protocols limit this value to the
  5920. + range: 0 through 4095. (The value 0 is used by
  5921. + some management applications for special test
  5922. + cases.) A value of 65535 signifies that no segment
  5923. + number is assigned to this port."
  5924. + ::= { dot1dSrPortEntry 3 }
  5925. +
  5926. +dot1dSrPortBridgeNum OBJECT-TYPE
  5927. + SYNTAX INTEGER
  5928. + ACCESS read-write
  5929. + STATUS mandatory
  5930. + DESCRIPTION
  5931. + "A bridge number uniquely identifies a bridge when
  5932. + more than one bridge is used to span the same two
  5933. + segments. Current source routing protocols limit
  5934. + this value to the range: 0 through 15. A value of
  5935. + 65535 signifies that no bridge number is assigned
  5936. + to this bridge."
  5937. + ::= { dot1dSrPortEntry 4 }
  5938. +
  5939. +dot1dSrPortTargetSegment OBJECT-TYPE
  5940. + SYNTAX INTEGER
  5941. + ACCESS read-write
  5942. + STATUS mandatory
  5943. + DESCRIPTION
  5944. + "The segment number that corresponds to the target
  5945. + segment this port is considered to be connected to
  5946. + by the bridge. Current source routing protocols
  5947. + limit this value to the range: 0 through 4095.
  5948. +
  5949. + (The value 0 is used by some management
  5950. + applications for special test cases.) A value of
  5951. + 65535 signifies that no target segment is assigned
  5952. + to this port."
  5953. + ::= { dot1dSrPortEntry 5 }
  5954. +
  5955. +-- It would be nice if we could use ifMtu as the size of the
  5956. +-- largest frame, but we can't because ifMtu is defined to be
  5957. +-- the size that the (inter-)network layer can use which can
  5958. +-- differ from the MAC layer (especially if several layers of
  5959. +-- encapsulation are used).
  5960. +
  5961. +dot1dSrPortLargestFrame OBJECT-TYPE
  5962. + SYNTAX INTEGER
  5963. + ACCESS read-write
  5964. + STATUS mandatory
  5965. + DESCRIPTION
  5966. + "The maximum size of the INFO field (LLC and
  5967. + above) that this port can send/receive. It does
  5968. + not include any MAC level (framing) octets. The
  5969. + value of this object is used by this bridge to
  5970. + determine whether a modification of the
  5971. + LargestFrame (LF, see [14]) field of the Routing
  5972. + Control field of the Routing Information Field is
  5973. + necessary.
  5974. +
  5975. + 64 valid values are defined by the IEEE 802.5M SRT
  5976. + Addendum: 516, 635, 754, 873, 993, 1112, 1231,
  5977. + 1350, 1470, 1542, 1615, 1688, 1761, 1833, 1906,
  5978. + 1979, 2052, 2345, 2638, 2932, 3225, 3518, 3812,
  5979. + 4105, 4399, 4865, 5331, 5798, 6264, 6730, 7197,
  5980. + 7663, 8130, 8539, 8949, 9358, 9768, 10178, 10587,
  5981. + 10997, 11407, 12199, 12992, 13785, 14578, 15370,
  5982. + 16163, 16956, 17749, 20730, 23711, 26693, 29674,
  5983. + 32655, 35637, 38618, 41600, 44591, 47583, 50575,
  5984. + 53567, 56559, 59551, and 65535.
  5985. +
  5986. + An illegal value will not be accepted by the
  5987. + bridge."
  5988. + ::= { dot1dSrPortEntry 6 }
  5989. +
  5990. +dot1dSrPortSTESpanMode OBJECT-TYPE
  5991. + SYNTAX INTEGER {
  5992. + auto-span(1),
  5993. + disabled(2),
  5994. + forced(3)
  5995. + }
  5996. + ACCESS read-write
  5997. + STATUS mandatory
  5998. + DESCRIPTION
  5999. + "Determines how this port behaves when presented
  6000. + with a Spanning Tree Explorer frame. The value
  6001. + 'disabled(2)' indicates that the port will not
  6002. + accept or send Spanning Tree Explorer packets; any
  6003. + STE packets received will be silently discarded.
  6004. + The value 'forced(3)' indicates the port will
  6005. + always accept and propagate Spanning Tree Explorer
  6006. + frames. This allows a manually configured
  6007. + Spanning Tree for this class of packet to be
  6008. + configured. Note that unlike transparent
  6009. + bridging, this is not catastrophic to the network
  6010. + if there are loops. The value 'auto-span(1)' can
  6011. + only be returned by a bridge that both implements
  6012. + the Spanning Tree Protocol and has use of the
  6013. + protocol enabled on this port. The behavior of the
  6014. + port for Spanning Tree Explorer frames is
  6015. + determined by the state of dot1dStpPortState. If
  6016. + the port is in the 'forwarding' state, the frame
  6017. + will be accepted or propagated. Otherwise, it
  6018. + will be silently discarded."
  6019. + ::= { dot1dSrPortEntry 7 }
  6020. +
  6021. +dot1dSrPortSpecInFrames OBJECT-TYPE
  6022. + SYNTAX Counter
  6023. + ACCESS read-only
  6024. + STATUS mandatory
  6025. + DESCRIPTION
  6026. + "The number of Specifically Routed frames, also
  6027. + referred to as Source Routed Frames, that have
  6028. + been received from this port's segment."
  6029. + ::= { dot1dSrPortEntry 8 }
  6030. +
  6031. +dot1dSrPortSpecOutFrames OBJECT-TYPE
  6032. + SYNTAX Counter
  6033. + ACCESS read-only
  6034. + STATUS mandatory
  6035. + DESCRIPTION
  6036. + "The number of Specifically Routed frames, also
  6037. + referred to as Source Routed Frames, that this
  6038. + port has transmitted on its segment."
  6039. + ::= { dot1dSrPortEntry 9 }
  6040. +
  6041. +dot1dSrPortApeInFrames OBJECT-TYPE
  6042. + SYNTAX Counter
  6043. + ACCESS read-only
  6044. + STATUS mandatory
  6045. + DESCRIPTION
  6046. + "The number of All Paths Explorer frames, also
  6047. + referred to as All Routes Explorer frames, that
  6048. + have been received by this port from its segment."
  6049. + ::= { dot1dSrPortEntry 10 }
  6050. +
  6051. +dot1dSrPortApeOutFrames OBJECT-TYPE
  6052. + SYNTAX Counter
  6053. + ACCESS read-only
  6054. + STATUS mandatory
  6055. + DESCRIPTION
  6056. + "The number of all Paths Explorer Frames, also
  6057. + referred to as All Routes Explorer frames, that
  6058. + have been transmitted by this port on its
  6059. + segment."
  6060. + ::= { dot1dSrPortEntry 11 }
  6061. +
  6062. +dot1dSrPortSteInFrames OBJECT-TYPE
  6063. + SYNTAX Counter
  6064. + ACCESS read-only
  6065. + STATUS mandatory
  6066. + DESCRIPTION
  6067. + "The number of spanning tree explorer frames that
  6068. + have been received by this port from its segment."
  6069. + ::= { dot1dSrPortEntry 12 }
  6070. +
  6071. +dot1dSrPortSteOutFrames OBJECT-TYPE
  6072. + SYNTAX Counter
  6073. + ACCESS read-only
  6074. + STATUS mandatory
  6075. + DESCRIPTION
  6076. + "The number of spanning tree explorer frames that
  6077. + have been transmitted by this port on its
  6078. + segment."
  6079. + ::= { dot1dSrPortEntry 13 }
  6080. +
  6081. +dot1dSrPortSegmentMismatchDiscards OBJECT-TYPE
  6082. + SYNTAX Counter
  6083. + ACCESS read-only
  6084. + STATUS mandatory
  6085. + DESCRIPTION
  6086. + "The number of explorer frames that have been
  6087. + discarded by this port because the routing
  6088. + descriptor field contained an invalid adjacent
  6089. + segment value."
  6090. + ::= { dot1dSrPortEntry 14 }
  6091. +
  6092. +dot1dSrPortDuplicateSegmentDiscards OBJECT-TYPE
  6093. + SYNTAX Counter
  6094. + ACCESS read-only
  6095. + STATUS mandatory
  6096. + DESCRIPTION
  6097. + "The number of frames that have been discarded by
  6098. + this port because the routing descriptor field
  6099. + contained a duplicate segment identifier."
  6100. + ::= { dot1dSrPortEntry 15 }
  6101. +
  6102. +dot1dSrPortHopCountExceededDiscards OBJECT-TYPE
  6103. + SYNTAX Counter
  6104. + ACCESS read-only
  6105. + STATUS mandatory
  6106. + DESCRIPTION
  6107. + "The number of explorer frames that have been
  6108. + discarded by this port because the Routing
  6109. + Information Field has exceeded the maximum route
  6110. + descriptor length."
  6111. + ::= { dot1dSrPortEntry 16 }
  6112. +
  6113. +dot1dSrPortDupLanIdOrTreeErrors OBJECT-TYPE
  6114. + SYNTAX Counter
  6115. + ACCESS read-only
  6116. + STATUS mandatory
  6117. + DESCRIPTION
  6118. + "The number of duplicate LAN IDs or Tree errors.
  6119. + This helps in detection of problems in networks
  6120. + containing older IBM Source Routing Bridges."
  6121. + ::= { dot1dSrPortEntry 17 }
  6122. +
  6123. +dot1dSrPortLanIdMismatches OBJECT-TYPE
  6124. + SYNTAX Counter
  6125. + ACCESS read-only
  6126. + STATUS mandatory
  6127. + DESCRIPTION
  6128. + "The number of ARE and STE frames that were
  6129. + discarded because the last LAN ID in the routing
  6130. + information field did not equal the LAN-in ID.
  6131. + This error can occur in implementations which do
  6132. + only a LAN-in ID and Bridge Number check instead
  6133. + of a LAN-in ID, Bridge Number, and LAN-out ID
  6134. + check before they forward broadcast frames."
  6135. + ::= { dot1dSrPortEntry 18 }
  6136. +
  6137. +-- scalar object in dot1dSr
  6138. +
  6139. +dot1dSrBridgeLfMode OBJECT-TYPE
  6140. + SYNTAX INTEGER {
  6141. + mode3(1),
  6142. + mode6(2)
  6143. + }
  6144. + ACCESS read-write
  6145. + STATUS mandatory
  6146. + DESCRIPTION
  6147. + "Indicates whether the bridge operates using older
  6148. + 3 bit length negotiation fields or the newer 6 bit
  6149. + length field in its RIF."
  6150. + ::= { dot1dSr 2 }
  6151. +
  6152. +-- The Port-Pair Database
  6153. +
  6154. +-- Implementation of this group is optional.
  6155. +
  6156. +-- This group is implemented by those bridges that support
  6157. +-- the direct multiport model of the source route bridging
  6158. +-- mode as defined in the IEEE 802.5 SRT Addendum to
  6159. +-- 802.1d.
  6160. +
  6161. +-- Bridges implementing this group may report 65535 for
  6162. +-- dot1dSrPortBridgeNumber and dot1dSrPortTargetSegment,
  6163. +-- indicating that those objects are not applicable.
  6164. +
  6165. +dot1dPortPairTableSize OBJECT-TYPE
  6166. + SYNTAX Gauge
  6167. + ACCESS read-only
  6168. + STATUS mandatory
  6169. + DESCRIPTION
  6170. + "The total number of entries in the Bridge Port
  6171. + Pair Database."
  6172. + ::= { dot1dPortPair 1 }
  6173. +
  6174. +-- the Bridge Port-Pair table
  6175. +
  6176. +-- this table represents port pairs within a bridge forming
  6177. +-- a unique bridge path, as defined in the IEEE 802.5M SRT
  6178. +-- Addendum.
  6179. +
  6180. +dot1dPortPairTable OBJECT-TYPE
  6181. + SYNTAX SEQUENCE OF Dot1dPortPairEntry
  6182. + ACCESS not-accessible
  6183. + STATUS mandatory
  6184. + DESCRIPTION
  6185. + "A table that contains information about every
  6186. +
  6187. + port pair database entity associated with this
  6188. + source routing bridge."
  6189. + ::= { dot1dPortPair 2 }
  6190. +
  6191. +dot1dPortPairEntry OBJECT-TYPE
  6192. + SYNTAX Dot1dPortPairEntry
  6193. + ACCESS not-accessible
  6194. + STATUS mandatory
  6195. + DESCRIPTION
  6196. + "A list of information for each port pair entity
  6197. + of a bridge."
  6198. + INDEX { dot1dPortPairLowPort, dot1dPortPairHighPort }
  6199. + ::= { dot1dPortPairTable 1 }
  6200. +
  6201. +Dot1dPortPairEntry ::=
  6202. + SEQUENCE {
  6203. + dot1dPortPairLowPort
  6204. + INTEGER,
  6205. + dot1dPortPairHighPort
  6206. + INTEGER,
  6207. + dot1dPortPairBridgeNum
  6208. + INTEGER,
  6209. + dot1dPortPairBridgeState
  6210. + INTEGER
  6211. + }
  6212. +
  6213. +dot1dPortPairLowPort OBJECT-TYPE
  6214. + SYNTAX INTEGER (1..65535)
  6215. + ACCESS read-write
  6216. + STATUS mandatory
  6217. + DESCRIPTION
  6218. + "The port number of the lower numbered port for
  6219. + which this entry contains port pair database
  6220. + information."
  6221. + ::= { dot1dPortPairEntry 1 }
  6222. +
  6223. +dot1dPortPairHighPort OBJECT-TYPE
  6224. + SYNTAX INTEGER (1..65535)
  6225. + ACCESS read-write
  6226. + STATUS mandatory
  6227. + DESCRIPTION
  6228. + "The port number of the higher numbered port for
  6229. + which this entry contains port pair database
  6230. + information."
  6231. + ::= { dot1dPortPairEntry 2 }
  6232. +
  6233. +dot1dPortPairBridgeNum OBJECT-TYPE
  6234. + SYNTAX INTEGER
  6235. +
  6236. + ACCESS read-write
  6237. + STATUS mandatory
  6238. + DESCRIPTION
  6239. + "A bridge number that uniquely identifies the path
  6240. + provided by this source routing bridge between the
  6241. + segments connected to dot1dPortPairLowPort and
  6242. + dot1dPortPairHighPort. The purpose of bridge
  6243. + number is to disambiguate between multiple paths
  6244. + connecting the same two LANs."
  6245. + ::= { dot1dPortPairEntry 3 }
  6246. +
  6247. +dot1dPortPairBridgeState OBJECT-TYPE
  6248. + SYNTAX INTEGER {
  6249. + enabled(1),
  6250. + disabled(2),
  6251. + invalid(3)
  6252. + }
  6253. + ACCESS read-write
  6254. + STATUS mandatory
  6255. + DESCRIPTION
  6256. + "The state of dot1dPortPairBridgeNum. Writing
  6257. + 'invalid(3)' to this object removes the
  6258. + corresponding entry."
  6259. + ::= { dot1dPortPairEntry 4 }
  6260. +
  6261. +END