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.

5183 lines
173 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/GNOME-SMI.txt
  935. @@ -0,0 +1,88 @@
  936. +GNOME-SMI DEFINITIONS ::= BEGIN
  937. +
  938. +IMPORTS
  939. + MODULE-IDENTITY,
  940. + OBJECT-IDENTITY,
  941. + enterprises
  942. + FROM SNMPv2-SMI;
  943. +
  944. +gnome MODULE-IDENTITY
  945. + LAST-UPDATED "200709070000Z"
  946. + ORGANIZATION "GNOME project"
  947. + CONTACT-INFO
  948. + "GNU Network Object Model Environment project
  949. +
  950. + see http://www.gnome.org for contact persons of a particular
  951. + area or subproject of GNOME.
  952. +
  953. + Administrative contact for MIB module:
  954. +
  955. + Jochen Friedrich
  956. + Ramsaystr. 9
  957. + 63450 Hanau
  958. + Germany
  959. +
  960. + email: jochen@scram.de"
  961. + DESCRIPTION
  962. + "The Structure of GNOME."
  963. +
  964. + -- revision history
  965. +
  966. + REVISION "200709070000Z" -- Sep 07, 2007
  967. + DESCRIPTION
  968. + "Fixed wrong enterprise number (how comes this
  969. + typo was unnoticed for so long?)."
  970. +
  971. + REVISION "200505070000Z" -- May 07, 2005
  972. + DESCRIPTION
  973. + "Added gnomeLDAP subtree for LDAP definitions."
  974. +
  975. + REVISION "200312070000Z" -- December 07, 2003
  976. + DESCRIPTION
  977. + "Added gnomeSysadmin subtree for GNOME project system administration.
  978. + Updated contact info."
  979. +
  980. + REVISION "9809010000Z" -- September 01, 1998
  981. + DESCRIPTION
  982. + "Initial version."
  983. +
  984. + ::= { enterprises 3319 } -- assigned by IANA
  985. +
  986. +gnomeProducts OBJECT-IDENTITY
  987. + STATUS current
  988. + DESCRIPTION
  989. + "gnomeProducts is the root OBJECT IDENTIFIER from
  990. + which sysObjectID values are assigned."
  991. + ::= { gnome 1 }
  992. +
  993. +gnomeMgmt OBJECT-IDENTITY
  994. + STATUS current
  995. + DESCRIPTION
  996. + "gnomeMgmt defines the subtree for production GNOME related
  997. + MIB registrations."
  998. + ::= { gnome 2 }
  999. +
  1000. +gnomeTest OBJECT-IDENTITY
  1001. + STATUS current
  1002. + DESCRIPTION
  1003. + "gnomeTest defines the subtree for testing GNOME related
  1004. + MIB registrations."
  1005. + ::= { gnome 3 }
  1006. +
  1007. +gnomeSysadmin OBJECT-IDENTITY
  1008. + STATUS current
  1009. + DESCRIPTION
  1010. + "gnomeSysadmin defines the subtree for GNOME related Sysadmin
  1011. + MIB registrations."
  1012. + ::= { gnome 4 }
  1013. +
  1014. +gnomeLDAP OBJECT-IDENTITY
  1015. + STATUS current
  1016. + DESCRIPTION
  1017. + "gnomeLDAP defines the subtree for GNOME related LDAP
  1018. + registrations."
  1019. + ::= { gnome 5 }
  1020. +
  1021. +-- more to come if necessary.
  1022. +
  1023. +END
  1024. --- /dev/null
  1025. +++ b/mibs/OSPF-MIB.txt
  1026. @@ -0,0 +1,2723 @@
  1027. +OSPF-MIB DEFINITIONS ::= BEGIN
  1028. +
  1029. + IMPORTS
  1030. + MODULE-IDENTITY, OBJECT-TYPE, Counter32, Gauge32,
  1031. + Integer32, IpAddress
  1032. + FROM SNMPv2-SMI
  1033. + TEXTUAL-CONVENTION, TruthValue, RowStatus
  1034. + FROM SNMPv2-TC
  1035. + MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
  1036. + mib-2 FROM RFC1213-MIB;
  1037. +
  1038. +-- This MIB module uses the extended OBJECT-TYPE macro as
  1039. +-- defined in [9].
  1040. +
  1041. +ospf MODULE-IDENTITY
  1042. + LAST-UPDATED "9501201225Z" -- Fri Jan 20 12:25:50 PST 1995
  1043. + ORGANIZATION "IETF OSPF Working Group"
  1044. + CONTACT-INFO
  1045. + " Fred Baker
  1046. + Postal: Cisco Systems
  1047. + 519 Lado Drive
  1048. + Santa Barbara, California 93111
  1049. + Tel: +1 805 681 0115
  1050. + E-Mail: fred@cisco.com
  1051. +
  1052. + Rob Coltun
  1053. + Postal: RainbowBridge Communications
  1054. + Tel: (301) 340-9416
  1055. + E-Mail: rcoltun@rainbow-bridge.com"
  1056. + DESCRIPTION
  1057. + "The MIB module to describe the OSPF Version 2
  1058. + Protocol"
  1059. + ::= { mib-2 14 }
  1060. +
  1061. +-- The Area ID, in OSPF, has the same format as an IP Address,
  1062. +-- but has the function of defining a summarization point for
  1063. +-- Link State Advertisements
  1064. +
  1065. +AreaID ::= TEXTUAL-CONVENTION
  1066. + STATUS current
  1067. + DESCRIPTION
  1068. + "An OSPF Area Identifier."
  1069. + SYNTAX IpAddress
  1070. +
  1071. +
  1072. +-- The Router ID, in OSPF, has the same format as an IP Address,
  1073. +-- but identifies the router independent of its IP Address.
  1074. +
  1075. +RouterID ::= TEXTUAL-CONVENTION
  1076. + STATUS current
  1077. + DESCRIPTION
  1078. + "A OSPF Router Identifier."
  1079. + SYNTAX IpAddress
  1080. +
  1081. +
  1082. +-- The OSPF Metric is defined as an unsigned value in the range
  1083. +
  1084. +Metric ::= TEXTUAL-CONVENTION
  1085. + STATUS current
  1086. + DESCRIPTION
  1087. + "The OSPF Internal Metric."
  1088. + SYNTAX Integer32 (0..'FFFF'h)
  1089. +
  1090. +BigMetric ::= TEXTUAL-CONVENTION
  1091. + STATUS current
  1092. + DESCRIPTION
  1093. + "The OSPF External Metric."
  1094. + SYNTAX Integer32 (0..'FFFFFF'h)
  1095. +
  1096. +-- Status Values
  1097. +
  1098. +Status ::= TEXTUAL-CONVENTION
  1099. + STATUS current
  1100. + DESCRIPTION
  1101. + "The status of an interface: 'enabled' indicates that
  1102. + it is willing to communicate with other OSPF Routers,
  1103. + while 'disabled' indicates that it is not."
  1104. + SYNTAX INTEGER { enabled (1), disabled (2) }
  1105. +
  1106. +-- Time Durations measured in seconds
  1107. +
  1108. +PositiveInteger ::= TEXTUAL-CONVENTION
  1109. + STATUS current
  1110. + DESCRIPTION
  1111. + "A positive integer. Values in excess are precluded as
  1112. + unnecessary and prone to interoperability issues."
  1113. + SYNTAX Integer32 (0..'7FFFFFFF'h)
  1114. +
  1115. +HelloRange ::= TEXTUAL-CONVENTION
  1116. + STATUS current
  1117. + DESCRIPTION
  1118. + "The range of intervals on which hello messages are
  1119. + exchanged."
  1120. + SYNTAX Integer32 (1..'FFFF'h)
  1121. +
  1122. +UpToMaxAge ::= TEXTUAL-CONVENTION
  1123. + STATUS current
  1124. + DESCRIPTION
  1125. + "The values that one might find or configure for
  1126. + variables bounded by the maximum age of an LSA."
  1127. + SYNTAX Integer32 (0..3600)
  1128. +
  1129. +
  1130. +-- The range of ifIndex
  1131. +
  1132. +InterfaceIndex ::= TEXTUAL-CONVENTION
  1133. + STATUS current
  1134. + DESCRIPTION
  1135. + "The range of ifIndex."
  1136. + SYNTAX Integer32
  1137. +
  1138. +
  1139. +-- Potential Priorities for the Designated Router Election
  1140. +
  1141. +DesignatedRouterPriority ::= TEXTUAL-CONVENTION
  1142. + STATUS current
  1143. + DESCRIPTION
  1144. + "The values defined for the priority of a system for
  1145. + becoming the designated router."
  1146. + SYNTAX Integer32 (0..'FF'h)
  1147. +
  1148. +TOSType ::= TEXTUAL-CONVENTION
  1149. + STATUS current
  1150. + DESCRIPTION
  1151. + "Type of Service is defined as a mapping to the IP Type of
  1152. + Service Flags as defined in the IP Forwarding Table MIB
  1153. +
  1154. + +-----+-----+-----+-----+-----+-----+-----+-----+
  1155. + | | | |
  1156. + | PRECEDENCE | TYPE OF SERVICE | 0 |
  1157. + | | | |
  1158. + +-----+-----+-----+-----+-----+-----+-----+-----+
  1159. +
  1160. + IP TOS IP TOS
  1161. + Field Policy Field Policy
  1162. +
  1163. + Contents Code Contents Code
  1164. + 0 0 0 0 ==> 0 0 0 0 1 ==> 2
  1165. + 0 0 1 0 ==> 4 0 0 1 1 ==> 6
  1166. + 0 1 0 0 ==> 8 0 1 0 1 ==> 10
  1167. + 0 1 1 0 ==> 12 0 1 1 1 ==> 14
  1168. + 1 0 0 0 ==> 16 1 0 0 1 ==> 18
  1169. + 1 0 1 0 ==> 20 1 0 1 1 ==> 22
  1170. + 1 1 0 0 ==> 24 1 1 0 1 ==> 26
  1171. + 1 1 1 0 ==> 28 1 1 1 1 ==> 30
  1172. +
  1173. + The remaining values are left for future definition."
  1174. + SYNTAX Integer32 (0..30)
  1175. +
  1176. +
  1177. +-- OSPF General Variables
  1178. +
  1179. +-- These parameters apply globally to the Router's
  1180. +-- OSPF Process.
  1181. +
  1182. +ospfGeneralGroup OBJECT IDENTIFIER ::= { ospf 1 }
  1183. +
  1184. +
  1185. + ospfRouterId OBJECT-TYPE
  1186. + SYNTAX RouterID
  1187. + MAX-ACCESS read-write
  1188. + STATUS current
  1189. + DESCRIPTION
  1190. + "A 32-bit integer uniquely identifying the
  1191. + router in the Autonomous System.
  1192. +
  1193. + By convention, to ensure uniqueness, this
  1194. + should default to the value of one of the
  1195. + router's IP interface addresses."
  1196. + REFERENCE
  1197. + "OSPF Version 2, C.1 Global parameters"
  1198. + ::= { ospfGeneralGroup 1 }
  1199. +
  1200. +
  1201. + ospfAdminStat OBJECT-TYPE
  1202. + SYNTAX Status
  1203. + MAX-ACCESS read-write
  1204. + STATUS current
  1205. + DESCRIPTION
  1206. + "The administrative status of OSPF in the
  1207. + router. The value 'enabled' denotes that the
  1208. + OSPF Process is active on at least one inter-
  1209. + face; 'disabled' disables it on all inter-
  1210. + faces."
  1211. + ::= { ospfGeneralGroup 2 }
  1212. +
  1213. + ospfVersionNumber OBJECT-TYPE
  1214. + SYNTAX INTEGER { version2 (2) }
  1215. + MAX-ACCESS read-only
  1216. + STATUS current
  1217. + DESCRIPTION
  1218. + "The current version number of the OSPF proto-
  1219. + col is 2."
  1220. + REFERENCE
  1221. + "OSPF Version 2, Title"
  1222. + ::= { ospfGeneralGroup 3 }
  1223. +
  1224. +
  1225. + ospfAreaBdrRtrStatus OBJECT-TYPE
  1226. + SYNTAX TruthValue
  1227. + MAX-ACCESS read-only
  1228. + STATUS current
  1229. + DESCRIPTION
  1230. + "A flag to note whether this router is an area
  1231. + border router."
  1232. + REFERENCE
  1233. + "OSPF Version 2, Section 3 Splitting the AS into
  1234. + Areas"
  1235. + ::= { ospfGeneralGroup 4 }
  1236. +
  1237. +
  1238. + ospfASBdrRtrStatus OBJECT-TYPE
  1239. + SYNTAX TruthValue
  1240. + MAX-ACCESS read-write
  1241. + STATUS current
  1242. + DESCRIPTION
  1243. + "A flag to note whether this router is config-
  1244. + ured as an Autonomous System border router."
  1245. + REFERENCE
  1246. + "OSPF Version 2, Section 3.3 Classification of
  1247. + routers"
  1248. + ::= { ospfGeneralGroup 5 }
  1249. +
  1250. + ospfExternLsaCount OBJECT-TYPE
  1251. + SYNTAX Gauge32
  1252. + MAX-ACCESS read-only
  1253. + STATUS current
  1254. + DESCRIPTION
  1255. + "The number of external (LS type 5) link-state
  1256. + advertisements in the link-state database."
  1257. + REFERENCE
  1258. + "OSPF Version 2, Appendix A.4.5 AS external link
  1259. + advertisements"
  1260. + ::= { ospfGeneralGroup 6 }
  1261. +
  1262. +
  1263. + ospfExternLsaCksumSum OBJECT-TYPE
  1264. + SYNTAX Integer32
  1265. + MAX-ACCESS read-only
  1266. + STATUS current
  1267. + DESCRIPTION
  1268. + "The 32-bit unsigned sum of the LS checksums of
  1269. + the external link-state advertisements con-
  1270. + tained in the link-state database. This sum
  1271. + can be used to determine if there has been a
  1272. + change in a router's link state database, and
  1273. + to compare the link-state database of two
  1274. + routers."
  1275. + ::= { ospfGeneralGroup 7 }
  1276. +
  1277. +
  1278. + ospfTOSSupport OBJECT-TYPE
  1279. + SYNTAX TruthValue
  1280. + MAX-ACCESS read-write
  1281. + STATUS current
  1282. + DESCRIPTION
  1283. + "The router's support for type-of-service rout-
  1284. + ing."
  1285. + REFERENCE
  1286. + "OSPF Version 2, Appendix F.1.2 Optional TOS
  1287. + support"
  1288. + ::= { ospfGeneralGroup 8 }
  1289. +
  1290. + ospfOriginateNewLsas OBJECT-TYPE
  1291. + SYNTAX Counter32
  1292. + MAX-ACCESS read-only
  1293. + STATUS current
  1294. + DESCRIPTION
  1295. + "The number of new link-state advertisements
  1296. + that have been originated. This number is in-
  1297. + cremented each time the router originates a new
  1298. + LSA."
  1299. + ::= { ospfGeneralGroup 9 }
  1300. +
  1301. +
  1302. + ospfRxNewLsas OBJECT-TYPE
  1303. + SYNTAX Counter32
  1304. + MAX-ACCESS read-only
  1305. + STATUS current
  1306. + DESCRIPTION
  1307. + "The number of link-state advertisements re-
  1308. + ceived determined to be new instantiations.
  1309. + This number does not include newer instantia-
  1310. + tions of self-originated link-state advertise-
  1311. + ments."
  1312. + ::= { ospfGeneralGroup 10 }
  1313. +
  1314. + ospfExtLsdbLimit OBJECT-TYPE
  1315. + SYNTAX Integer32 (-1..'7FFFFFFF'h)
  1316. + MAX-ACCESS read-write
  1317. + STATUS current
  1318. + DESCRIPTION
  1319. + "The maximum number of non-default AS-
  1320. + external-LSAs entries that can be stored in the
  1321. + link-state database. If the value is -1, then
  1322. + there is no limit.
  1323. +
  1324. + When the number of non-default AS-external-LSAs
  1325. + in a router's link-state database reaches
  1326. + ospfExtLsdbLimit, the router enters Overflow-
  1327. + State. The router never holds more than
  1328. + ospfExtLsdbLimit non-default AS-external-LSAs
  1329. + in its database. OspfExtLsdbLimit MUST be set
  1330. + identically in all routers attached to the OSPF
  1331. + backbone and/or any regular OSPF area. (i.e.,
  1332. + OSPF stub areas and NSSAs are excluded)."
  1333. + DEFVAL { -1 }
  1334. + ::= { ospfGeneralGroup 11 }
  1335. +
  1336. + ospfMulticastExtensions OBJECT-TYPE
  1337. + SYNTAX Integer32
  1338. + MAX-ACCESS read-write
  1339. + STATUS current
  1340. + DESCRIPTION
  1341. + "A Bit Mask indicating whether the router is
  1342. + forwarding IP multicast (Class D) datagrams
  1343. + based on the algorithms defined in the Multi-
  1344. + cast Extensions to OSPF.
  1345. +
  1346. + Bit 0, if set, indicates that the router can
  1347. + forward IP multicast datagrams in the router's
  1348. + directly attached areas (called intra-area mul-
  1349. + ticast routing).
  1350. +
  1351. + Bit 1, if set, indicates that the router can
  1352. + forward IP multicast datagrams between OSPF
  1353. + areas (called inter-area multicast routing).
  1354. +
  1355. + Bit 2, if set, indicates that the router can
  1356. + forward IP multicast datagrams between Auto-
  1357. + nomous Systems (called inter-AS multicast rout-
  1358. + ing).
  1359. +
  1360. + Only certain combinations of bit settings are
  1361. + allowed, namely: 0 (no multicast forwarding is
  1362. + enabled), 1 (intra-area multicasting only), 3
  1363. + (intra-area and inter-area multicasting), 5
  1364. + (intra-area and inter-AS multicasting) and 7
  1365. + (multicasting everywhere). By default, no mul-
  1366. + ticast forwarding is enabled."
  1367. + DEFVAL { 0 }
  1368. + ::= { ospfGeneralGroup 12 }
  1369. +
  1370. + ospfExitOverflowInterval OBJECT-TYPE
  1371. + SYNTAX PositiveInteger
  1372. + MAX-ACCESS read-write
  1373. + STATUS current
  1374. + DESCRIPTION
  1375. + "The number of seconds that, after entering
  1376. + OverflowState, a router will attempt to leave
  1377. + OverflowState. This allows the router to again
  1378. + originate non-default AS-external-LSAs. When
  1379. + set to 0, the router will not leave Overflow-
  1380. + State until restarted."
  1381. + DEFVAL { 0 }
  1382. + ::= { ospfGeneralGroup 13 }
  1383. +
  1384. +
  1385. + ospfDemandExtensions OBJECT-TYPE
  1386. + SYNTAX TruthValue
  1387. + MAX-ACCESS read-write
  1388. + STATUS current
  1389. + DESCRIPTION
  1390. + "The router's support for demand routing."
  1391. + REFERENCE
  1392. + "OSPF Version 2, Appendix on Demand Routing"
  1393. + ::= { ospfGeneralGroup 14 }
  1394. +
  1395. +
  1396. +-- The OSPF Area Data Structure contains information
  1397. +-- regarding the various areas. The interfaces and
  1398. +-- virtual links are configured as part of these areas.
  1399. +-- Area 0.0.0.0, by definition, is the Backbone Area
  1400. +
  1401. +
  1402. + ospfAreaTable OBJECT-TYPE
  1403. + SYNTAX SEQUENCE OF OspfAreaEntry
  1404. + MAX-ACCESS not-accessible
  1405. + STATUS current
  1406. + DESCRIPTION
  1407. + "Information describing the configured parame-
  1408. + ters and cumulative statistics of the router's
  1409. + attached areas."
  1410. + REFERENCE
  1411. + "OSPF Version 2, Section 6 The Area Data Struc-
  1412. + ture"
  1413. + ::= { ospf 2 }
  1414. +
  1415. +
  1416. + ospfAreaEntry OBJECT-TYPE
  1417. + SYNTAX OspfAreaEntry
  1418. + MAX-ACCESS not-accessible
  1419. + STATUS current
  1420. + DESCRIPTION
  1421. + "Information describing the configured parame-
  1422. + ters and cumulative statistics of one of the
  1423. + router's attached areas."
  1424. + INDEX { ospfAreaId }
  1425. + ::= { ospfAreaTable 1 }
  1426. +
  1427. +OspfAreaEntry ::=
  1428. + SEQUENCE {
  1429. + ospfAreaId
  1430. + AreaID,
  1431. + ospfAuthType
  1432. + Integer32,
  1433. + ospfImportAsExtern
  1434. + INTEGER,
  1435. + ospfSpfRuns
  1436. + Counter32,
  1437. + ospfAreaBdrRtrCount
  1438. + Gauge32,
  1439. + ospfAsBdrRtrCount
  1440. + Gauge32,
  1441. + ospfAreaLsaCount
  1442. + Gauge32,
  1443. + ospfAreaLsaCksumSum
  1444. + Integer32,
  1445. + ospfAreaSummary
  1446. + INTEGER,
  1447. + ospfAreaStatus
  1448. + RowStatus
  1449. + }
  1450. +
  1451. + ospfAreaId OBJECT-TYPE
  1452. + SYNTAX AreaID
  1453. + MAX-ACCESS read-only
  1454. + STATUS current
  1455. + DESCRIPTION
  1456. + "A 32-bit integer uniquely identifying an area.
  1457. + Area ID 0.0.0.0 is used for the OSPF backbone."
  1458. + REFERENCE
  1459. + "OSPF Version 2, Appendix C.2 Area parameters"
  1460. + ::= { ospfAreaEntry 1 }
  1461. +
  1462. +
  1463. + ospfAuthType OBJECT-TYPE
  1464. + SYNTAX Integer32
  1465. + -- none (0),
  1466. + -- simplePassword (1)
  1467. + -- md5 (2)
  1468. + -- reserved for specification by IANA (> 2)
  1469. + MAX-ACCESS read-create
  1470. + STATUS obsolete
  1471. + DESCRIPTION
  1472. + "The authentication type specified for an area.
  1473. + Additional authentication types may be assigned
  1474. + locally on a per Area basis."
  1475. + REFERENCE
  1476. + "OSPF Version 2, Appendix E Authentication"
  1477. + DEFVAL { 0 } -- no authentication, by default
  1478. + ::= { ospfAreaEntry 2 }
  1479. +
  1480. + ospfImportAsExtern OBJECT-TYPE
  1481. + SYNTAX INTEGER {
  1482. + importExternal (1),
  1483. + importNoExternal (2),
  1484. + importNssa (3)
  1485. + }
  1486. + MAX-ACCESS read-create
  1487. + STATUS current
  1488. + DESCRIPTION
  1489. + "The area's support for importing AS external
  1490. + link- state advertisements."
  1491. + REFERENCE
  1492. + "OSPF Version 2, Appendix C.2 Area parameters"
  1493. + DEFVAL { importExternal }
  1494. + ::= { ospfAreaEntry 3 }
  1495. +
  1496. +
  1497. + ospfSpfRuns OBJECT-TYPE
  1498. + SYNTAX Counter32
  1499. + MAX-ACCESS read-only
  1500. + STATUS current
  1501. + DESCRIPTION
  1502. + "The number of times that the intra-area route
  1503. + table has been calculated using this area's
  1504. + link-state database. This is typically done
  1505. + using Dijkstra's algorithm."
  1506. + ::= { ospfAreaEntry 4 }
  1507. +
  1508. +
  1509. + ospfAreaBdrRtrCount OBJECT-TYPE
  1510. + SYNTAX Gauge32
  1511. + MAX-ACCESS read-only
  1512. + STATUS current
  1513. + DESCRIPTION
  1514. + "The total number of area border routers reach-
  1515. + able within this area. This is initially zero,
  1516. + and is calculated in each SPF Pass."
  1517. + ::= { ospfAreaEntry 5 }
  1518. +
  1519. + ospfAsBdrRtrCount OBJECT-TYPE
  1520. + SYNTAX Gauge32
  1521. + MAX-ACCESS read-only
  1522. + STATUS current
  1523. + DESCRIPTION
  1524. + "The total number of Autonomous System border
  1525. + routers reachable within this area. This is
  1526. + initially zero, and is calculated in each SPF
  1527. + Pass."
  1528. + ::= { ospfAreaEntry 6 }
  1529. +
  1530. +
  1531. + ospfAreaLsaCount OBJECT-TYPE
  1532. + SYNTAX Gauge32
  1533. + MAX-ACCESS read-only
  1534. + STATUS current
  1535. + DESCRIPTION
  1536. + "The total number of link-state advertisements
  1537. + in this area's link-state database, excluding
  1538. + AS External LSA's."
  1539. + ::= { ospfAreaEntry 7 }
  1540. +
  1541. +
  1542. + ospfAreaLsaCksumSum OBJECT-TYPE
  1543. + SYNTAX Integer32
  1544. + MAX-ACCESS read-only
  1545. + STATUS current
  1546. + DESCRIPTION
  1547. + "The 32-bit unsigned sum of the link-state ad-
  1548. + vertisements' LS checksums contained in this
  1549. + area's link-state database. This sum excludes
  1550. + external (LS type 5) link-state advertisements.
  1551. + The sum can be used to determine if there has
  1552. + been a change in a router's link state data-
  1553. + base, and to compare the link-state database of
  1554. + two routers."
  1555. + DEFVAL { 0 }
  1556. + ::= { ospfAreaEntry 8 }
  1557. +
  1558. + ospfAreaSummary OBJECT-TYPE
  1559. + SYNTAX INTEGER {
  1560. + noAreaSummary (1),
  1561. + sendAreaSummary (2)
  1562. + }
  1563. + MAX-ACCESS read-create
  1564. + STATUS current
  1565. + DESCRIPTION
  1566. + "The variable ospfAreaSummary controls the im-
  1567. + port of summary LSAs into stub areas. It has
  1568. + no effect on other areas.
  1569. +
  1570. + If it is noAreaSummary, the router will neither
  1571. + originate nor propagate summary LSAs into the
  1572. + stub area. It will rely entirely on its de-
  1573. + fault route.
  1574. +
  1575. + If it is sendAreaSummary, the router will both
  1576. + summarize and propagate summary LSAs."
  1577. + DEFVAL { noAreaSummary }
  1578. + ::= { ospfAreaEntry 9 }
  1579. +
  1580. +
  1581. + ospfAreaStatus OBJECT-TYPE
  1582. + SYNTAX RowStatus
  1583. + MAX-ACCESS read-create
  1584. + STATUS current
  1585. + DESCRIPTION
  1586. + "This variable displays the status of the en-
  1587. + try. Setting it to 'invalid' has the effect of
  1588. + rendering it inoperative. The internal effect
  1589. + (row removal) is implementation dependent."
  1590. + ::= { ospfAreaEntry 10 }
  1591. +
  1592. +
  1593. +-- OSPF Area Default Metric Table
  1594. +
  1595. +-- The OSPF Area Default Metric Table describes the metrics
  1596. +-- that a default Area Border Router will advertise into a
  1597. +-- Stub area.
  1598. +
  1599. +
  1600. + ospfStubAreaTable OBJECT-TYPE
  1601. + SYNTAX SEQUENCE OF OspfStubAreaEntry
  1602. + MAX-ACCESS not-accessible
  1603. + STATUS current
  1604. + DESCRIPTION
  1605. + "The set of metrics that will be advertised by
  1606. + a default Area Border Router into a stub area."
  1607. + REFERENCE
  1608. + "OSPF Version 2, Appendix C.2, Area Parameters"
  1609. + ::= { ospf 3 }
  1610. +
  1611. +
  1612. + ospfStubAreaEntry OBJECT-TYPE
  1613. + SYNTAX OspfStubAreaEntry
  1614. + MAX-ACCESS not-accessible
  1615. + STATUS current
  1616. + DESCRIPTION
  1617. + "The metric for a given Type of Service that
  1618. + will be advertised by a default Area Border
  1619. + Router into a stub area."
  1620. + REFERENCE
  1621. + "OSPF Version 2, Appendix C.2, Area Parameters"
  1622. + INDEX { ospfStubAreaId, ospfStubTOS }
  1623. + ::= { ospfStubAreaTable 1 }
  1624. +
  1625. +OspfStubAreaEntry ::=
  1626. + SEQUENCE {
  1627. + ospfStubAreaId
  1628. + AreaID,
  1629. + ospfStubTOS
  1630. + TOSType,
  1631. + ospfStubMetric
  1632. + BigMetric,
  1633. + ospfStubStatus
  1634. + RowStatus,
  1635. + ospfStubMetricType
  1636. + INTEGER
  1637. + }
  1638. +
  1639. + ospfStubAreaId OBJECT-TYPE
  1640. + SYNTAX AreaID
  1641. + MAX-ACCESS read-only
  1642. + STATUS current
  1643. + DESCRIPTION
  1644. + "The 32 bit identifier for the Stub Area. On
  1645. + creation, this can be derived from the in-
  1646. + stance."
  1647. + ::= { ospfStubAreaEntry 1 }
  1648. +
  1649. +
  1650. + ospfStubTOS OBJECT-TYPE
  1651. + SYNTAX TOSType
  1652. + MAX-ACCESS read-only
  1653. + STATUS current
  1654. + DESCRIPTION
  1655. + "The Type of Service associated with the
  1656. + metric. On creation, this can be derived from
  1657. + the instance."
  1658. + ::= { ospfStubAreaEntry 2 }
  1659. +
  1660. +
  1661. + ospfStubMetric OBJECT-TYPE
  1662. + SYNTAX BigMetric
  1663. + MAX-ACCESS read-create
  1664. + STATUS current
  1665. + DESCRIPTION
  1666. + "The metric value applied at the indicated type
  1667. + of service. By default, this equals the least
  1668. + metric at the type of service among the inter-
  1669. + faces to other areas."
  1670. + ::= { ospfStubAreaEntry 3 }
  1671. +
  1672. +
  1673. + ospfStubStatus OBJECT-TYPE
  1674. + SYNTAX RowStatus
  1675. + MAX-ACCESS read-create
  1676. + STATUS current
  1677. + DESCRIPTION
  1678. + "This variable displays the status of the en-
  1679. + try. Setting it to 'invalid' has the effect of
  1680. + rendering it inoperative. The internal effect
  1681. + (row removal) is implementation dependent."
  1682. + ::= { ospfStubAreaEntry 4 }
  1683. +
  1684. + ospfStubMetricType OBJECT-TYPE
  1685. + SYNTAX INTEGER {
  1686. + ospfMetric (1), -- OSPF Metric
  1687. + comparableCost (2), -- external type 1
  1688. + nonComparable (3) -- external type 2
  1689. + }
  1690. + MAX-ACCESS read-create
  1691. + STATUS current
  1692. + DESCRIPTION
  1693. + "This variable displays the type of metric ad-
  1694. + vertised as a default route."
  1695. + DEFVAL { ospfMetric }
  1696. + ::= { ospfStubAreaEntry 5 }
  1697. +
  1698. +-- OSPF Link State Database
  1699. +
  1700. +-- The Link State Database contains the Link State
  1701. +-- Advertisements from throughout the areas that the
  1702. +-- device is attached to.
  1703. +
  1704. +
  1705. + ospfLsdbTable OBJECT-TYPE
  1706. + SYNTAX SEQUENCE OF OspfLsdbEntry
  1707. + MAX-ACCESS not-accessible
  1708. + STATUS current
  1709. + DESCRIPTION
  1710. + "The OSPF Process's Link State Database."
  1711. + REFERENCE
  1712. + "OSPF Version 2, Section 12 Link State Adver-
  1713. + tisements"
  1714. + ::= { ospf 4 }
  1715. +
  1716. +
  1717. + ospfLsdbEntry OBJECT-TYPE
  1718. + SYNTAX OspfLsdbEntry
  1719. + MAX-ACCESS not-accessible
  1720. + STATUS current
  1721. + DESCRIPTION
  1722. + "A single Link State Advertisement."
  1723. + INDEX { ospfLsdbAreaId, ospfLsdbType,
  1724. + ospfLsdbLsid, ospfLsdbRouterId }
  1725. + ::= { ospfLsdbTable 1 }
  1726. +
  1727. +OspfLsdbEntry ::=
  1728. + SEQUENCE {
  1729. + ospfLsdbAreaId
  1730. + AreaID,
  1731. + ospfLsdbType
  1732. + INTEGER,
  1733. + ospfLsdbLsid
  1734. + IpAddress,
  1735. + ospfLsdbRouterId
  1736. + RouterID,
  1737. + ospfLsdbSequence
  1738. + Integer32,
  1739. + ospfLsdbAge
  1740. + Integer32,
  1741. + ospfLsdbChecksum
  1742. + Integer32,
  1743. + ospfLsdbAdvertisement
  1744. + OCTET STRING
  1745. + }
  1746. + ospfLsdbAreaId OBJECT-TYPE
  1747. + SYNTAX AreaID
  1748. + MAX-ACCESS read-only
  1749. + STATUS current
  1750. + DESCRIPTION
  1751. + "The 32 bit identifier of the Area from which
  1752. + the LSA was received."
  1753. + REFERENCE
  1754. + "OSPF Version 2, Appendix C.2 Area parameters"
  1755. + ::= { ospfLsdbEntry 1 }
  1756. +
  1757. +-- External Link State Advertisements are permitted
  1758. +-- for backward compatibility, but should be displayed in
  1759. +-- the ospfExtLsdbTable rather than here.
  1760. +
  1761. + ospfLsdbType OBJECT-TYPE
  1762. + SYNTAX INTEGER {
  1763. + routerLink (1),
  1764. + networkLink (2),
  1765. + summaryLink (3),
  1766. + asSummaryLink (4),
  1767. + asExternalLink (5), -- but see ospfExtLsdbTable
  1768. + multicastLink (6),
  1769. + nssaExternalLink (7)
  1770. + }
  1771. + MAX-ACCESS read-only
  1772. + STATUS current
  1773. + DESCRIPTION
  1774. + "The type of the link state advertisement.
  1775. + Each link state type has a separate advertise-
  1776. + ment format."
  1777. + REFERENCE
  1778. + "OSPF Version 2, Appendix A.4.1 The Link State
  1779. + Advertisement header"
  1780. + ::= { ospfLsdbEntry 2 }
  1781. +
  1782. + ospfLsdbLsid OBJECT-TYPE
  1783. + SYNTAX IpAddress
  1784. + MAX-ACCESS read-only
  1785. + STATUS current
  1786. + DESCRIPTION
  1787. + "The Link State ID is an LS Type Specific field
  1788. + containing either a Router ID or an IP Address;
  1789. + it identifies the piece of the routing domain
  1790. + that is being described by the advertisement."
  1791. + REFERENCE
  1792. + "OSPF Version 2, Section 12.1.4 Link State ID"
  1793. + ::= { ospfLsdbEntry 3 }
  1794. + ospfLsdbRouterId OBJECT-TYPE
  1795. + SYNTAX RouterID
  1796. + MAX-ACCESS read-only
  1797. + STATUS current
  1798. + DESCRIPTION
  1799. + "The 32 bit number that uniquely identifies the
  1800. + originating router in the Autonomous System."
  1801. + REFERENCE
  1802. + "OSPF Version 2, Appendix C.1 Global parameters"
  1803. + ::= { ospfLsdbEntry 4 }
  1804. +
  1805. +-- Note that the OSPF Sequence Number is a 32 bit signed
  1806. +-- integer. It starts with the value '80000001'h,
  1807. +-- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h
  1808. +-- Thus, a typical sequence number will be very negative.
  1809. +
  1810. + ospfLsdbSequence OBJECT-TYPE
  1811. + SYNTAX Integer32
  1812. + MAX-ACCESS read-only
  1813. + STATUS current
  1814. + DESCRIPTION
  1815. + "The sequence number field is a signed 32-bit
  1816. + integer. It is used to detect old and dupli-
  1817. + cate link state advertisements. The space of
  1818. + sequence numbers is linearly ordered. The
  1819. + larger the sequence number the more recent the
  1820. + advertisement."
  1821. + REFERENCE
  1822. + "OSPF Version 2, Section 12.1.6 LS sequence
  1823. + number"
  1824. + ::= { ospfLsdbEntry 5 }
  1825. +
  1826. +
  1827. + ospfLsdbAge OBJECT-TYPE
  1828. + SYNTAX Integer32 -- Should be 0..MaxAge
  1829. + MAX-ACCESS read-only
  1830. + STATUS current
  1831. + DESCRIPTION
  1832. + "This field is the age of the link state adver-
  1833. + tisement in seconds."
  1834. + REFERENCE
  1835. + "OSPF Version 2, Section 12.1.1 LS age"
  1836. + ::= { ospfLsdbEntry 6 }
  1837. +
  1838. + ospfLsdbChecksum OBJECT-TYPE
  1839. + SYNTAX Integer32
  1840. + MAX-ACCESS read-only
  1841. + STATUS current
  1842. + DESCRIPTION
  1843. + "This field is the checksum of the complete
  1844. + contents of the advertisement, excepting the
  1845. + age field. The age field is excepted so that
  1846. + an advertisement's age can be incremented
  1847. + without updating the checksum. The checksum
  1848. + used is the same that is used for ISO connec-
  1849. + tionless datagrams; it is commonly referred to
  1850. + as the Fletcher checksum."
  1851. + REFERENCE
  1852. + "OSPF Version 2, Section 12.1.7 LS checksum"
  1853. + ::= { ospfLsdbEntry 7 }
  1854. +
  1855. +
  1856. + ospfLsdbAdvertisement OBJECT-TYPE
  1857. + SYNTAX OCTET STRING (SIZE (1..65535))
  1858. + MAX-ACCESS read-only
  1859. + STATUS current
  1860. + DESCRIPTION
  1861. + "The entire Link State Advertisement, including
  1862. + its header."
  1863. + REFERENCE
  1864. + "OSPF Version 2, Section 12 Link State Adver-
  1865. + tisements"
  1866. + ::= { ospfLsdbEntry 8 }
  1867. +
  1868. +
  1869. +-- Address Range Table
  1870. +
  1871. +-- The Address Range Table acts as an adjunct to the Area
  1872. +-- Table; It describes those Address Range Summaries that
  1873. +-- are configured to be propagated from an Area to reduce
  1874. +-- the amount of information about it which is known beyond
  1875. +-- its borders.
  1876. +
  1877. + ospfAreaRangeTable OBJECT-TYPE
  1878. + SYNTAX SEQUENCE OF OspfAreaRangeEntry
  1879. + MAX-ACCESS not-accessible
  1880. + STATUS obsolete
  1881. + DESCRIPTION
  1882. + "A range if IP addresses specified by an IP
  1883. + address/IP network mask pair. For example,
  1884. + class B address range of X.X.X.X with a network
  1885. + mask of 255.255.0.0 includes all IP addresses
  1886. + from X.X.0.0 to X.X.255.255"
  1887. + REFERENCE
  1888. + "OSPF Version 2, Appendix C.2 Area parameters"
  1889. + ::= { ospf 5 }
  1890. + ospfAreaRangeEntry OBJECT-TYPE
  1891. + SYNTAX OspfAreaRangeEntry
  1892. + MAX-ACCESS not-accessible
  1893. + STATUS obsolete
  1894. + DESCRIPTION
  1895. + "A range if IP addresses specified by an IP
  1896. + address/IP network mask pair. For example,
  1897. + class B address range of X.X.X.X with a network
  1898. + mask of 255.255.0.0 includes all IP addresses
  1899. + from X.X.0.0 to X.X.255.255"
  1900. + REFERENCE
  1901. + "OSPF Version 2, Appendix C.2 Area parameters"
  1902. + INDEX { ospfAreaRangeAreaId, ospfAreaRangeNet }
  1903. + ::= { ospfAreaRangeTable 1 }
  1904. +
  1905. +OspfAreaRangeEntry ::=
  1906. + SEQUENCE {
  1907. + ospfAreaRangeAreaId
  1908. + AreaID,
  1909. + ospfAreaRangeNet
  1910. + IpAddress,
  1911. + ospfAreaRangeMask
  1912. + IpAddress,
  1913. + ospfAreaRangeStatus
  1914. + RowStatus,
  1915. + ospfAreaRangeEffect
  1916. + INTEGER
  1917. + }
  1918. +
  1919. + ospfAreaRangeAreaId OBJECT-TYPE
  1920. + SYNTAX AreaID
  1921. + MAX-ACCESS read-only
  1922. + STATUS obsolete
  1923. + DESCRIPTION
  1924. + "The Area the Address Range is to be found
  1925. + within."
  1926. + REFERENCE
  1927. + "OSPF Version 2, Appendix C.2 Area parameters"
  1928. + ::= { ospfAreaRangeEntry 1 }
  1929. +
  1930. +
  1931. + ospfAreaRangeNet OBJECT-TYPE
  1932. + SYNTAX IpAddress
  1933. + MAX-ACCESS read-only
  1934. + STATUS obsolete
  1935. + DESCRIPTION
  1936. + "The IP Address of the Net or Subnet indicated
  1937. + by the range."
  1938. + REFERENCE
  1939. + "OSPF Version 2, Appendix C.2 Area parameters"
  1940. + ::= { ospfAreaRangeEntry 2 }
  1941. +
  1942. +
  1943. + ospfAreaRangeMask OBJECT-TYPE
  1944. + SYNTAX IpAddress
  1945. + MAX-ACCESS read-create
  1946. + STATUS obsolete
  1947. + DESCRIPTION
  1948. + "The Subnet Mask that pertains to the Net or
  1949. + Subnet."
  1950. + REFERENCE
  1951. + "OSPF Version 2, Appendix C.2 Area parameters"
  1952. + ::= { ospfAreaRangeEntry 3 }
  1953. +
  1954. + ospfAreaRangeStatus OBJECT-TYPE
  1955. + SYNTAX RowStatus
  1956. + MAX-ACCESS read-create
  1957. + STATUS obsolete
  1958. + DESCRIPTION
  1959. + "This variable displays the status of the en-
  1960. + try. Setting it to 'invalid' has the effect of
  1961. + rendering it inoperative. The internal effect
  1962. + (row removal) is implementation dependent."
  1963. + ::= { ospfAreaRangeEntry 4 }
  1964. +
  1965. +
  1966. + ospfAreaRangeEffect OBJECT-TYPE
  1967. + SYNTAX INTEGER {
  1968. + advertiseMatching (1),
  1969. + doNotAdvertiseMatching (2)
  1970. + }
  1971. + MAX-ACCESS read-create
  1972. + STATUS obsolete
  1973. + DESCRIPTION
  1974. + "Subnets subsumed by ranges either trigger the
  1975. + advertisement of the indicated summary (adver-
  1976. + tiseMatching), or result in the subnet's not
  1977. + being advertised at all outside the area."
  1978. + DEFVAL { advertiseMatching }
  1979. + ::= { ospfAreaRangeEntry 5 }
  1980. +
  1981. +
  1982. +
  1983. +-- OSPF Host Table
  1984. +
  1985. +-- The Host/Metric Table indicates what hosts are directly
  1986. +-- attached to the Router, and what metrics and types of
  1987. +-- service should be advertised for them.
  1988. +
  1989. + ospfHostTable OBJECT-TYPE
  1990. + SYNTAX SEQUENCE OF OspfHostEntry
  1991. + MAX-ACCESS not-accessible
  1992. + STATUS current
  1993. + DESCRIPTION
  1994. + "The list of Hosts, and their metrics, that the
  1995. + router will advertise as host routes."
  1996. + REFERENCE
  1997. + "OSPF Version 2, Appendix C.6 Host route param-
  1998. + eters"
  1999. + ::= { ospf 6 }
  2000. +
  2001. +
  2002. + ospfHostEntry OBJECT-TYPE
  2003. + SYNTAX OspfHostEntry
  2004. + MAX-ACCESS not-accessible
  2005. + STATUS current
  2006. + DESCRIPTION
  2007. + "A metric to be advertised, for a given type of
  2008. + service, when a given host is reachable."
  2009. + INDEX { ospfHostIpAddress, ospfHostTOS }
  2010. + ::= { ospfHostTable 1 }
  2011. +
  2012. +OspfHostEntry ::=
  2013. + SEQUENCE {
  2014. + ospfHostIpAddress
  2015. + IpAddress,
  2016. + ospfHostTOS
  2017. + TOSType,
  2018. + ospfHostMetric
  2019. + Metric,
  2020. + ospfHostStatus
  2021. + RowStatus,
  2022. + ospfHostAreaID
  2023. + AreaID
  2024. + }
  2025. +
  2026. + ospfHostIpAddress OBJECT-TYPE
  2027. + SYNTAX IpAddress
  2028. + MAX-ACCESS read-only
  2029. + STATUS current
  2030. + DESCRIPTION
  2031. + "The IP Address of the Host."
  2032. + REFERENCE
  2033. + "OSPF Version 2, Appendix C.6 Host route parame-
  2034. + ters"
  2035. + ::= { ospfHostEntry 1 }
  2036. +
  2037. +
  2038. + ospfHostTOS OBJECT-TYPE
  2039. + SYNTAX TOSType
  2040. + MAX-ACCESS read-only
  2041. + STATUS current
  2042. + DESCRIPTION
  2043. + "The Type of Service of the route being config-
  2044. + ured."
  2045. + REFERENCE
  2046. + "OSPF Version 2, Appendix C.6 Host route parame-
  2047. + ters"
  2048. + ::= { ospfHostEntry 2 }
  2049. +
  2050. +
  2051. + ospfHostMetric OBJECT-TYPE
  2052. + SYNTAX Metric
  2053. + MAX-ACCESS read-create
  2054. + STATUS current
  2055. + DESCRIPTION
  2056. + "The Metric to be advertised."
  2057. + REFERENCE
  2058. + "OSPF Version 2, Appendix C.6 Host route parame-
  2059. + ters"
  2060. + ::= { ospfHostEntry 3 }
  2061. +
  2062. + ospfHostStatus OBJECT-TYPE
  2063. + SYNTAX RowStatus
  2064. + MAX-ACCESS read-create
  2065. + STATUS current
  2066. + DESCRIPTION
  2067. + "This variable displays the status of the en-
  2068. + try. Setting it to 'invalid' has the effect of
  2069. + rendering it inoperative. The internal effect
  2070. + (row removal) is implementation dependent."
  2071. + ::= { ospfHostEntry 4 }
  2072. +
  2073. +
  2074. + ospfHostAreaID OBJECT-TYPE
  2075. + SYNTAX AreaID
  2076. + MAX-ACCESS read-only
  2077. + STATUS current
  2078. + DESCRIPTION
  2079. + "The Area the Host Entry is to be found within.
  2080. + By default, the area that a subsuming OSPF in-
  2081. + terface is in, or 0.0.0.0"
  2082. + REFERENCE
  2083. + "OSPF Version 2, Appendix C.2 Area parameters"
  2084. + ::= { ospfHostEntry 5 }
  2085. +
  2086. +
  2087. +-- OSPF Interface Table
  2088. +
  2089. +-- The OSPF Interface Table augments the ipAddrTable
  2090. +-- with OSPF specific information.
  2091. +
  2092. + ospfIfTable OBJECT-TYPE
  2093. + SYNTAX SEQUENCE OF OspfIfEntry
  2094. + MAX-ACCESS not-accessible
  2095. + STATUS current
  2096. + DESCRIPTION
  2097. + "The OSPF Interface Table describes the inter-
  2098. + faces from the viewpoint of OSPF."
  2099. + REFERENCE
  2100. + "OSPF Version 2, Appendix C.3 Router interface
  2101. + parameters"
  2102. + ::= { ospf 7 }
  2103. +
  2104. +
  2105. + ospfIfEntry OBJECT-TYPE
  2106. + SYNTAX OspfIfEntry
  2107. + MAX-ACCESS not-accessible
  2108. + STATUS current
  2109. + DESCRIPTION
  2110. + "The OSPF Interface Entry describes one inter-
  2111. + face from the viewpoint of OSPF."
  2112. + INDEX { ospfIfIpAddress, ospfAddressLessIf }
  2113. + ::= { ospfIfTable 1 }
  2114. +
  2115. +OspfIfEntry ::=
  2116. + SEQUENCE {
  2117. + ospfIfIpAddress
  2118. + IpAddress,
  2119. + ospfAddressLessIf
  2120. + Integer32,
  2121. + ospfIfAreaId
  2122. + AreaID,
  2123. + ospfIfType
  2124. + INTEGER,
  2125. + ospfIfAdminStat
  2126. + Status,
  2127. + ospfIfRtrPriority
  2128. + DesignatedRouterPriority,
  2129. + ospfIfTransitDelay
  2130. + UpToMaxAge,
  2131. + ospfIfRetransInterval
  2132. + UpToMaxAge,
  2133. + ospfIfHelloInterval
  2134. + HelloRange,
  2135. + ospfIfRtrDeadInterval
  2136. + PositiveInteger,
  2137. + ospfIfPollInterval
  2138. + PositiveInteger,
  2139. + ospfIfState
  2140. + INTEGER,
  2141. + ospfIfDesignatedRouter
  2142. + IpAddress,
  2143. + ospfIfBackupDesignatedRouter
  2144. + IpAddress,
  2145. + ospfIfEvents
  2146. + Counter32,
  2147. + ospfIfAuthType
  2148. + INTEGER,
  2149. + ospfIfAuthKey
  2150. + OCTET STRING,
  2151. + ospfIfStatus
  2152. + RowStatus,
  2153. + ospfIfMulticastForwarding
  2154. + INTEGER,
  2155. + ospfIfDemand
  2156. + TruthValue
  2157. + }
  2158. +
  2159. + ospfIfIpAddress OBJECT-TYPE
  2160. + SYNTAX IpAddress
  2161. + MAX-ACCESS read-only
  2162. + STATUS current
  2163. + DESCRIPTION
  2164. + "The IP address of this OSPF interface."
  2165. + ::= { ospfIfEntry 1 }
  2166. +
  2167. + ospfAddressLessIf OBJECT-TYPE
  2168. + SYNTAX Integer32
  2169. + MAX-ACCESS read-only
  2170. + STATUS current
  2171. + DESCRIPTION
  2172. + "For the purpose of easing the instancing of
  2173. + addressed and addressless interfaces; This
  2174. + variable takes the value 0 on interfaces with
  2175. + IP Addresses, and the corresponding value of
  2176. + ifIndex for interfaces having no IP Address."
  2177. + ::= { ospfIfEntry 2 }
  2178. + ospfIfAreaId OBJECT-TYPE
  2179. + SYNTAX AreaID
  2180. + MAX-ACCESS read-create
  2181. + STATUS current
  2182. + DESCRIPTION
  2183. + "A 32-bit integer uniquely identifying the area
  2184. + to which the interface connects. Area ID
  2185. + 0.0.0.0 is used for the OSPF backbone."
  2186. + DEFVAL { '00000000'H } -- 0.0.0.0
  2187. + ::= { ospfIfEntry 3 }
  2188. +
  2189. + ospfIfType OBJECT-TYPE
  2190. + SYNTAX INTEGER {
  2191. + broadcast (1),
  2192. + nbma (2),
  2193. + pointToPoint (3),
  2194. + pointToMultipoint (5)
  2195. + }
  2196. + MAX-ACCESS read-create
  2197. + STATUS current
  2198. + DESCRIPTION
  2199. + "The OSPF interface type.
  2200. +
  2201. + By way of a default, this field may be intuited
  2202. + from the corresponding value of ifType. Broad-
  2203. + cast LANs, such as Ethernet and IEEE 802.5,
  2204. + take the value 'broadcast', X.25 and similar
  2205. + technologies take the value 'nbma', and links
  2206. + that are definitively point to point take the
  2207. + value 'pointToPoint'."
  2208. + ::= { ospfIfEntry 4 }
  2209. +
  2210. +
  2211. + ospfIfAdminStat OBJECT-TYPE
  2212. + SYNTAX Status
  2213. + MAX-ACCESS read-create
  2214. + STATUS current
  2215. + DESCRIPTION
  2216. + "The OSPF interface's administrative status.
  2217. + The value formed on the interface, and the in-
  2218. + terface will be advertised as an internal route
  2219. + to some area. The value 'disabled' denotes
  2220. + that the interface is external to OSPF."
  2221. + DEFVAL { enabled }
  2222. + ::= { ospfIfEntry 5 }
  2223. +
  2224. + ospfIfRtrPriority OBJECT-TYPE
  2225. + SYNTAX DesignatedRouterPriority
  2226. + MAX-ACCESS read-create
  2227. + STATUS current
  2228. + DESCRIPTION
  2229. + "The priority of this interface. Used in
  2230. + multi-access networks, this field is used in
  2231. + the designated router election algorithm. The
  2232. + value 0 signifies that the router is not eligi-
  2233. + ble to become the designated router on this
  2234. + particular network. In the event of a tie in
  2235. + this value, routers will use their Router ID as
  2236. + a tie breaker."
  2237. + DEFVAL { 1 }
  2238. + ::= { ospfIfEntry 6 }
  2239. +
  2240. +
  2241. + ospfIfTransitDelay OBJECT-TYPE
  2242. + SYNTAX UpToMaxAge
  2243. + MAX-ACCESS read-create
  2244. + STATUS current
  2245. + DESCRIPTION
  2246. + "The estimated number of seconds it takes to
  2247. + transmit a link state update packet over this
  2248. + interface."
  2249. + DEFVAL { 1 }
  2250. + ::= { ospfIfEntry 7 }
  2251. +
  2252. +
  2253. + ospfIfRetransInterval OBJECT-TYPE
  2254. + SYNTAX UpToMaxAge
  2255. + MAX-ACCESS read-create
  2256. + STATUS current
  2257. + DESCRIPTION
  2258. + "The number of seconds between link-state ad-
  2259. + vertisement retransmissions, for adjacencies
  2260. + belonging to this interface. This value is
  2261. + also used when retransmitting database descrip-
  2262. + tion and link-state request packets."
  2263. + DEFVAL { 5 }
  2264. + ::= { ospfIfEntry 8 }
  2265. +
  2266. +
  2267. + ospfIfHelloInterval OBJECT-TYPE
  2268. + SYNTAX HelloRange
  2269. + MAX-ACCESS read-create
  2270. + STATUS current
  2271. + DESCRIPTION
  2272. + "The length of time, in seconds, between the
  2273. + Hello packets that the router sends on the in-
  2274. + terface. This value must be the same for all
  2275. + routers attached to a common network."
  2276. + DEFVAL { 10 }
  2277. + ::= { ospfIfEntry 9 }
  2278. +
  2279. +
  2280. + ospfIfRtrDeadInterval OBJECT-TYPE
  2281. + SYNTAX PositiveInteger
  2282. + MAX-ACCESS read-create
  2283. + STATUS current
  2284. + DESCRIPTION
  2285. + "The number of seconds that a router's Hello
  2286. + packets have not been seen before it's neigh-
  2287. + bors declare the router down. This should be
  2288. + some multiple of the Hello interval. This
  2289. + value must be the same for all routers attached
  2290. + to a common network."
  2291. + DEFVAL { 40 }
  2292. + ::= { ospfIfEntry 10 }
  2293. +
  2294. +
  2295. + ospfIfPollInterval OBJECT-TYPE
  2296. + SYNTAX PositiveInteger
  2297. + MAX-ACCESS read-create
  2298. + STATUS current
  2299. + DESCRIPTION
  2300. + "The larger time interval, in seconds, between
  2301. + the Hello packets sent to an inactive non-
  2302. + broadcast multi- access neighbor."
  2303. + DEFVAL { 120 }
  2304. + ::= { ospfIfEntry 11 }
  2305. +
  2306. +
  2307. + ospfIfState OBJECT-TYPE
  2308. + SYNTAX INTEGER {
  2309. + down (1),
  2310. + loopback (2),
  2311. + waiting (3),
  2312. + pointToPoint (4),
  2313. + designatedRouter (5),
  2314. + backupDesignatedRouter (6),
  2315. + otherDesignatedRouter (7)
  2316. + }
  2317. + MAX-ACCESS read-only
  2318. + STATUS current
  2319. + DESCRIPTION
  2320. + "The OSPF Interface State."
  2321. + DEFVAL { down }
  2322. + ::= { ospfIfEntry 12 }
  2323. +
  2324. +
  2325. + ospfIfDesignatedRouter OBJECT-TYPE
  2326. + SYNTAX IpAddress
  2327. + MAX-ACCESS read-only
  2328. + STATUS current
  2329. + DESCRIPTION
  2330. + "The IP Address of the Designated Router."
  2331. + DEFVAL { '00000000'H } -- 0.0.0.0
  2332. + ::= { ospfIfEntry 13 }
  2333. +
  2334. +
  2335. + ospfIfBackupDesignatedRouter OBJECT-TYPE
  2336. + SYNTAX IpAddress
  2337. + MAX-ACCESS read-only
  2338. + STATUS current
  2339. + DESCRIPTION
  2340. + "The IP Address of the Backup Designated
  2341. + Router."
  2342. + DEFVAL { '00000000'H } -- 0.0.0.0
  2343. + ::= { ospfIfEntry 14 }
  2344. +
  2345. + ospfIfEvents OBJECT-TYPE
  2346. + SYNTAX Counter32
  2347. + MAX-ACCESS read-only
  2348. + STATUS current
  2349. + DESCRIPTION
  2350. + "The number of times this OSPF interface has
  2351. + changed its state, or an error has occurred."
  2352. + ::= { ospfIfEntry 15 }
  2353. +
  2354. +
  2355. + ospfIfAuthKey OBJECT-TYPE
  2356. + SYNTAX OCTET STRING (SIZE (0..256))
  2357. + MAX-ACCESS read-create
  2358. + STATUS current
  2359. + DESCRIPTION
  2360. + "The Authentication Key. If the Area's Author-
  2361. + ization Type is simplePassword, and the key
  2362. + length is shorter than 8 octets, the agent will
  2363. + left adjust and zero fill to 8 octets.
  2364. +
  2365. + Note that unauthenticated interfaces need no
  2366. + authentication key, and simple password authen-
  2367. + tication cannot use a key of more than 8 oc-
  2368. + tets. Larger keys are useful only with authen-
  2369. + tication mechanisms not specified in this docu-
  2370. + ment.
  2371. +
  2372. + When read, ospfIfAuthKey always returns an Oc-
  2373. + tet String of length zero."
  2374. + REFERENCE
  2375. + "OSPF Version 2, Section 9 The Interface Data
  2376. + Structure"
  2377. + DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0
  2378. + ::= { ospfIfEntry 16 }
  2379. +
  2380. + ospfIfStatus OBJECT-TYPE
  2381. + SYNTAX RowStatus
  2382. + MAX-ACCESS read-create
  2383. + STATUS current
  2384. + DESCRIPTION
  2385. + "This variable displays the status of the en-
  2386. + try. Setting it to 'invalid' has the effect of
  2387. + rendering it inoperative. The internal effect
  2388. + (row removal) is implementation dependent."
  2389. + ::= { ospfIfEntry 17 }
  2390. +
  2391. +
  2392. + ospfIfMulticastForwarding OBJECT-TYPE
  2393. + SYNTAX INTEGER {
  2394. + blocked (1), -- no multicast forwarding
  2395. + multicast (2), -- using multicast address
  2396. + unicast (3) -- to each OSPF neighbor
  2397. + }
  2398. + MAX-ACCESS read-create
  2399. + STATUS current
  2400. + DESCRIPTION
  2401. + "The way multicasts should forwarded on this
  2402. + interface; not forwarded, forwarded as data
  2403. + link multicasts, or forwarded as data link uni-
  2404. + casts. Data link multicasting is not meaning-
  2405. + ful on point to point and NBMA interfaces, and
  2406. + setting ospfMulticastForwarding to 0 effective-
  2407. + ly disables all multicast forwarding."
  2408. + DEFVAL { blocked }
  2409. + ::= { ospfIfEntry 18 }
  2410. +
  2411. +
  2412. + ospfIfDemand OBJECT-TYPE
  2413. + SYNTAX TruthValue
  2414. + MAX-ACCESS read-create
  2415. + STATUS current
  2416. + DESCRIPTION
  2417. + "Indicates whether Demand OSPF procedures (hel-
  2418. + lo supression to FULL neighbors and setting the
  2419. + DoNotAge flag on proogated LSAs) should be per-
  2420. + formed on this interface."
  2421. + DEFVAL { false }
  2422. + ::= { ospfIfEntry 19 }
  2423. +
  2424. +
  2425. + ospfIfAuthType OBJECT-TYPE
  2426. + SYNTAX INTEGER (0..255)
  2427. + -- none (0),
  2428. + -- simplePassword (1)
  2429. + -- md5 (2)
  2430. + -- reserved for specification by IANA (> 2)
  2431. + MAX-ACCESS read-create
  2432. + STATUS current
  2433. + DESCRIPTION
  2434. + "The authentication type specified for an in-
  2435. + terface. Additional authentication types may
  2436. + be assigned locally."
  2437. + REFERENCE
  2438. + "OSPF Version 2, Appendix E Authentication"
  2439. + DEFVAL { 0 } -- no authentication, by default
  2440. + ::= { ospfIfEntry 20 }
  2441. +
  2442. +
  2443. +-- OSPF Interface Metric Table
  2444. +
  2445. +-- The Metric Table describes the metrics to be advertised
  2446. +-- for a specified interface at the various types of service.
  2447. +-- As such, this table is an adjunct of the OSPF Interface
  2448. +-- Table.
  2449. +
  2450. +-- Types of service, as defined by RFC 791, have the ability
  2451. +-- to request low delay, high bandwidth, or reliable linkage.
  2452. +
  2453. +-- For the purposes of this specification, the measure of
  2454. +-- bandwidth
  2455. +
  2456. +-- Metric = 10^8 / ifSpeed
  2457. +
  2458. +-- is the default value. For multiple link interfaces, note
  2459. +-- that ifSpeed is the sum of the individual link speeds.
  2460. +-- This yields a number having the following typical values:
  2461. +
  2462. +-- Network Type/bit rate Metric
  2463. +
  2464. +-- >= 100 MBPS 1
  2465. +-- Ethernet/802.3 10
  2466. +-- E1 48
  2467. +-- T1 (ESF) 65
  2468. +-- 64 KBPS 1562
  2469. +-- 56 KBPS 1785
  2470. +-- 19.2 KBPS 5208
  2471. +-- 9.6 KBPS 10416
  2472. +
  2473. +-- Routes that are not specified use the default (TOS 0) metric
  2474. +
  2475. + ospfIfMetricTable OBJECT-TYPE
  2476. + SYNTAX SEQUENCE OF OspfIfMetricEntry
  2477. + MAX-ACCESS not-accessible
  2478. + STATUS current
  2479. + DESCRIPTION
  2480. + "The TOS metrics for a non-virtual interface
  2481. + identified by the interface index."
  2482. + REFERENCE
  2483. + "OSPF Version 2, Appendix C.3 Router interface
  2484. + parameters"
  2485. + ::= { ospf 8 }
  2486. +
  2487. + ospfIfMetricEntry OBJECT-TYPE
  2488. + SYNTAX OspfIfMetricEntry
  2489. + MAX-ACCESS not-accessible
  2490. + STATUS current
  2491. + DESCRIPTION
  2492. + "A particular TOS metric for a non-virtual in-
  2493. + terface identified by the interface index."
  2494. + REFERENCE
  2495. + "OSPF Version 2, Appendix C.3 Router interface
  2496. + parameters"
  2497. + INDEX { ospfIfMetricIpAddress,
  2498. + ospfIfMetricAddressLessIf,
  2499. + ospfIfMetricTOS }
  2500. + ::= { ospfIfMetricTable 1 }
  2501. +
  2502. +OspfIfMetricEntry ::=
  2503. + SEQUENCE {
  2504. + ospfIfMetricIpAddress
  2505. + IpAddress,
  2506. + ospfIfMetricAddressLessIf
  2507. + Integer32,
  2508. + ospfIfMetricTOS
  2509. + TOSType,
  2510. + ospfIfMetricValue
  2511. + Metric,
  2512. + ospfIfMetricStatus
  2513. + RowStatus
  2514. + }
  2515. +
  2516. + ospfIfMetricIpAddress OBJECT-TYPE
  2517. + SYNTAX IpAddress
  2518. + MAX-ACCESS read-only
  2519. + STATUS current
  2520. + DESCRIPTION
  2521. + "The IP address of this OSPF interface. On row
  2522. + creation, this can be derived from the in-
  2523. + stance."
  2524. + ::= { ospfIfMetricEntry 1 }
  2525. +
  2526. + ospfIfMetricAddressLessIf OBJECT-TYPE
  2527. + SYNTAX Integer32
  2528. + MAX-ACCESS read-only
  2529. + STATUS current
  2530. + DESCRIPTION
  2531. + "For the purpose of easing the instancing of
  2532. + addressed and addressless interfaces; This
  2533. + variable takes the value 0 on interfaces with
  2534. + IP Addresses, and the value of ifIndex for in-
  2535. + terfaces having no IP Address. On row crea-
  2536. + tion, this can be derived from the instance."
  2537. + ::= { ospfIfMetricEntry 2 }
  2538. +
  2539. +
  2540. + ospfIfMetricTOS OBJECT-TYPE
  2541. + SYNTAX TOSType
  2542. + MAX-ACCESS read-only
  2543. + STATUS current
  2544. + DESCRIPTION
  2545. + "The type of service metric being referenced.
  2546. + On row creation, this can be derived from the
  2547. + instance."
  2548. + ::= { ospfIfMetricEntry 3 }
  2549. +
  2550. +
  2551. + ospfIfMetricValue OBJECT-TYPE
  2552. + SYNTAX Metric
  2553. + MAX-ACCESS read-create
  2554. + STATUS current
  2555. + DESCRIPTION
  2556. + "The metric of using this type of service on
  2557. + this interface. The default value of the TOS 0
  2558. + Metric is 10^8 / ifSpeed."
  2559. + ::= { ospfIfMetricEntry 4 }
  2560. +
  2561. + ospfIfMetricStatus OBJECT-TYPE
  2562. + SYNTAX RowStatus
  2563. + MAX-ACCESS read-create
  2564. + STATUS current
  2565. + DESCRIPTION
  2566. + "This variable displays the status of the en-
  2567. + try. Setting it to 'invalid' has the effect of
  2568. + rendering it inoperative. The internal effect
  2569. + (row removal) is implementation dependent."
  2570. + ::= { ospfIfMetricEntry 5 }
  2571. +
  2572. +
  2573. +-- OSPF Virtual Interface Table
  2574. +
  2575. +-- The Virtual Interface Table describes the virtual
  2576. +-- links that the OSPF Process is configured to
  2577. +-- carry on.
  2578. +
  2579. + ospfVirtIfTable OBJECT-TYPE
  2580. + SYNTAX SEQUENCE OF OspfVirtIfEntry
  2581. + MAX-ACCESS not-accessible
  2582. + STATUS current
  2583. + DESCRIPTION
  2584. + "Information about this router's virtual inter-
  2585. + faces."
  2586. + REFERENCE
  2587. + "OSPF Version 2, Appendix C.4 Virtual link
  2588. + parameters"
  2589. + ::= { ospf 9 }
  2590. +
  2591. +
  2592. + ospfVirtIfEntry OBJECT-TYPE
  2593. + SYNTAX OspfVirtIfEntry
  2594. + MAX-ACCESS not-accessible
  2595. + STATUS current
  2596. + DESCRIPTION
  2597. + "Information about a single Virtual Interface."
  2598. + INDEX { ospfVirtIfAreaId, ospfVirtIfNeighbor }
  2599. + ::= { ospfVirtIfTable 1 }
  2600. +
  2601. +OspfVirtIfEntry ::=
  2602. + SEQUENCE {
  2603. + ospfVirtIfAreaId
  2604. + AreaID,
  2605. + ospfVirtIfNeighbor
  2606. + RouterID,
  2607. + ospfVirtIfTransitDelay
  2608. + UpToMaxAge,
  2609. + ospfVirtIfRetransInterval
  2610. + UpToMaxAge,
  2611. + ospfVirtIfHelloInterval
  2612. + HelloRange,
  2613. + ospfVirtIfRtrDeadInterval
  2614. + PositiveInteger,
  2615. + ospfVirtIfState
  2616. + INTEGER,
  2617. + ospfVirtIfEvents
  2618. + Counter32,
  2619. + ospfVirtIfAuthType
  2620. + INTEGER,
  2621. + ospfVirtIfAuthKey
  2622. + OCTET STRING,
  2623. + ospfVirtIfStatus
  2624. + RowStatus
  2625. + }
  2626. +
  2627. + ospfVirtIfAreaId OBJECT-TYPE
  2628. + SYNTAX AreaID
  2629. + MAX-ACCESS read-only
  2630. + STATUS current
  2631. + DESCRIPTION
  2632. + "The Transit Area that the Virtual Link
  2633. + traverses. By definition, this is not 0.0.0.0"
  2634. + ::= { ospfVirtIfEntry 1 }
  2635. +
  2636. +
  2637. + ospfVirtIfNeighbor OBJECT-TYPE
  2638. + SYNTAX RouterID
  2639. + MAX-ACCESS read-only
  2640. + STATUS current
  2641. + DESCRIPTION
  2642. + "The Router ID of the Virtual Neighbor."
  2643. + ::= { ospfVirtIfEntry 2 }
  2644. +
  2645. +
  2646. + ospfVirtIfTransitDelay OBJECT-TYPE
  2647. + SYNTAX UpToMaxAge
  2648. + MAX-ACCESS read-create
  2649. + STATUS current
  2650. + DESCRIPTION
  2651. + "The estimated number of seconds it takes to
  2652. + transmit a link- state update packet over this
  2653. + interface."
  2654. + DEFVAL { 1 }
  2655. + ::= { ospfVirtIfEntry 3 }
  2656. +
  2657. +
  2658. + ospfVirtIfRetransInterval OBJECT-TYPE
  2659. + SYNTAX UpToMaxAge
  2660. + MAX-ACCESS read-create
  2661. + STATUS current
  2662. + DESCRIPTION
  2663. + "The number of seconds between link-state ad-
  2664. + vertisement retransmissions, for adjacencies
  2665. + belonging to this interface. This value is
  2666. + also used when retransmitting database descrip-
  2667. + tion and link-state request packets. This
  2668. + value should be well over the expected round-
  2669. + trip time."
  2670. + DEFVAL { 5 }
  2671. + ::= { ospfVirtIfEntry 4 }
  2672. +
  2673. +
  2674. + ospfVirtIfHelloInterval OBJECT-TYPE
  2675. + SYNTAX HelloRange
  2676. + MAX-ACCESS read-create
  2677. + STATUS current
  2678. + DESCRIPTION
  2679. + "The length of time, in seconds, between the
  2680. + Hello packets that the router sends on the in-
  2681. + terface. This value must be the same for the
  2682. + virtual neighbor."
  2683. + DEFVAL { 10 }
  2684. + ::= { ospfVirtIfEntry 5 }
  2685. +
  2686. +
  2687. + ospfVirtIfRtrDeadInterval OBJECT-TYPE
  2688. + SYNTAX PositiveInteger
  2689. + MAX-ACCESS read-create
  2690. + STATUS current
  2691. + DESCRIPTION
  2692. + "The number of seconds that a router's Hello
  2693. + packets have not been seen before it's neigh-
  2694. + bors declare the router down. This should be
  2695. + some multiple of the Hello interval. This
  2696. + value must be the same for the virtual neigh-
  2697. + bor."
  2698. + DEFVAL { 60 }
  2699. + ::= { ospfVirtIfEntry 6 }
  2700. +
  2701. +
  2702. + ospfVirtIfState OBJECT-TYPE
  2703. + SYNTAX INTEGER {
  2704. + down (1), -- these use the same encoding
  2705. + pointToPoint (4) -- as the ospfIfTable
  2706. + }
  2707. + MAX-ACCESS read-only
  2708. + STATUS current
  2709. + DESCRIPTION
  2710. + "OSPF virtual interface states."
  2711. + DEFVAL { down }
  2712. + ::= { ospfVirtIfEntry 7 }
  2713. +
  2714. +
  2715. + ospfVirtIfEvents OBJECT-TYPE
  2716. + SYNTAX Counter32
  2717. + MAX-ACCESS read-only
  2718. + STATUS current
  2719. + DESCRIPTION
  2720. + "The number of state changes or error events on
  2721. + this Virtual Link"
  2722. + ::= { ospfVirtIfEntry 8 }
  2723. +
  2724. +
  2725. + ospfVirtIfAuthKey OBJECT-TYPE
  2726. + SYNTAX OCTET STRING (SIZE(0..256))
  2727. + MAX-ACCESS read-create
  2728. + STATUS current
  2729. + DESCRIPTION
  2730. + "If Authentication Type is simplePassword, the
  2731. + device will left adjust and zero fill to 8 oc-
  2732. + tets.
  2733. +
  2734. + Note that unauthenticated interfaces need no
  2735. + authentication key, and simple password authen-
  2736. + tication cannot use a key of more than 8 oc-
  2737. + tets. Larger keys are useful only with authen-
  2738. + tication mechanisms not specified in this docu-
  2739. + ment.
  2740. +
  2741. + When read, ospfVifAuthKey always returns a
  2742. + string of length zero."
  2743. + REFERENCE
  2744. + "OSPF Version 2, Section 9 The Interface Data
  2745. + Structure"
  2746. + DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0
  2747. + ::= { ospfVirtIfEntry 9 }
  2748. +
  2749. +
  2750. + ospfVirtIfStatus OBJECT-TYPE
  2751. + SYNTAX RowStatus
  2752. + MAX-ACCESS read-create
  2753. + STATUS current
  2754. + DESCRIPTION
  2755. + "This variable displays the status of the en-
  2756. + try. Setting it to 'invalid' has the effect of
  2757. + rendering it inoperative. The internal effect
  2758. + (row removal) is implementation dependent."
  2759. + ::= { ospfVirtIfEntry 10 }
  2760. +
  2761. +
  2762. + ospfVirtIfAuthType OBJECT-TYPE
  2763. + SYNTAX INTEGER (0..255)
  2764. + -- none (0),
  2765. + -- simplePassword (1)
  2766. + -- md5 (2)
  2767. + -- reserved for specification by IANA (> 2)
  2768. + MAX-ACCESS read-create
  2769. + STATUS current
  2770. + DESCRIPTION
  2771. + "The authentication type specified for a virtu-
  2772. + al interface. Additional authentication types
  2773. + may be assigned locally."
  2774. + REFERENCE
  2775. + "OSPF Version 2, Appendix E Authentication"
  2776. + DEFVAL { 0 } -- no authentication, by default
  2777. + ::= { ospfVirtIfEntry 11 }
  2778. +
  2779. +
  2780. +-- OSPF Neighbor Table
  2781. +
  2782. +-- The OSPF Neighbor Table describes all neighbors in
  2783. +-- the locality of the subject router.
  2784. +
  2785. + ospfNbrTable OBJECT-TYPE
  2786. + SYNTAX SEQUENCE OF OspfNbrEntry
  2787. + MAX-ACCESS not-accessible
  2788. + STATUS current
  2789. + DESCRIPTION
  2790. + "A table of non-virtual neighbor information."
  2791. + REFERENCE
  2792. + "OSPF Version 2, Section 10 The Neighbor Data
  2793. + Structure"
  2794. + ::= { ospf 10 }
  2795. +
  2796. +
  2797. + ospfNbrEntry OBJECT-TYPE
  2798. + SYNTAX OspfNbrEntry
  2799. + MAX-ACCESS not-accessible
  2800. + STATUS current
  2801. + DESCRIPTION
  2802. + "The information regarding a single neighbor."
  2803. + REFERENCE
  2804. + "OSPF Version 2, Section 10 The Neighbor Data
  2805. + Structure"
  2806. + INDEX { ospfNbrIpAddr, ospfNbrAddressLessIndex }
  2807. + ::= { ospfNbrTable 1 }
  2808. +
  2809. +OspfNbrEntry ::=
  2810. + SEQUENCE {
  2811. + ospfNbrIpAddr
  2812. + IpAddress,
  2813. + ospfNbrAddressLessIndex
  2814. + InterfaceIndex,
  2815. + ospfNbrRtrId
  2816. + RouterID,
  2817. + ospfNbrOptions
  2818. + Integer32,
  2819. + ospfNbrPriority
  2820. + DesignatedRouterPriority,
  2821. + ospfNbrState
  2822. + INTEGER,
  2823. + ospfNbrEvents
  2824. + Counter32,
  2825. + ospfNbrLsRetransQLen
  2826. + Gauge32,
  2827. + ospfNbmaNbrStatus
  2828. + RowStatus,
  2829. + ospfNbmaNbrPermanence
  2830. + INTEGER,
  2831. + ospfNbrHelloSuppressed
  2832. + TruthValue
  2833. + }
  2834. +
  2835. + ospfNbrIpAddr OBJECT-TYPE
  2836. + SYNTAX IpAddress
  2837. + MAX-ACCESS read-only
  2838. + STATUS current
  2839. + DESCRIPTION
  2840. + "The IP address this neighbor is using in its
  2841. + IP Source Address. Note that, on addressless
  2842. + links, this will not be 0.0.0.0, but the ad-
  2843. + dress of another of the neighbor's interfaces."
  2844. + ::= { ospfNbrEntry 1 }
  2845. +
  2846. +
  2847. + ospfNbrAddressLessIndex OBJECT-TYPE
  2848. + SYNTAX InterfaceIndex
  2849. + MAX-ACCESS read-only
  2850. + STATUS current
  2851. + DESCRIPTION
  2852. + "On an interface having an IP Address, zero.
  2853. + On addressless interfaces, the corresponding
  2854. + value of ifIndex in the Internet Standard MIB.
  2855. + On row creation, this can be derived from the
  2856. + instance."
  2857. + ::= { ospfNbrEntry 2 }
  2858. +
  2859. +
  2860. + ospfNbrRtrId OBJECT-TYPE
  2861. + SYNTAX RouterID
  2862. + MAX-ACCESS read-only
  2863. + STATUS current
  2864. + DESCRIPTION
  2865. + "A 32-bit integer (represented as a type IpAd-
  2866. + dress) uniquely identifying the neighboring
  2867. + router in the Autonomous System."
  2868. + DEFVAL { '00000000'H } -- 0.0.0.0
  2869. + ::= { ospfNbrEntry 3 }
  2870. +
  2871. +
  2872. + ospfNbrOptions OBJECT-TYPE
  2873. + SYNTAX Integer32
  2874. + MAX-ACCESS read-only
  2875. + STATUS current
  2876. + DESCRIPTION
  2877. + "A Bit Mask corresponding to the neighbor's op-
  2878. + tions field.
  2879. +
  2880. + Bit 0, if set, indicates that the system will
  2881. + operate on Type of Service metrics other than
  2882. + TOS 0. If zero, the neighbor will ignore all
  2883. + metrics except the TOS 0 metric.
  2884. +
  2885. + Bit 1, if set, indicates that the associated
  2886. + area accepts and operates on external informa-
  2887. + tion; if zero, it is a stub area.
  2888. +
  2889. + Bit 2, if set, indicates that the system is ca-
  2890. + pable of routing IP Multicast datagrams; i.e.,
  2891. + that it implements the Multicast Extensions to
  2892. + OSPF.
  2893. +
  2894. + Bit 3, if set, indicates that the associated
  2895. + area is an NSSA. These areas are capable of
  2896. + carrying type 7 external advertisements, which
  2897. + are translated into type 5 external advertise-
  2898. + ments at NSSA borders."
  2899. + REFERENCE
  2900. + "OSPF Version 2, Section 12.1.2 Options"
  2901. + DEFVAL { 0 }
  2902. + ::= { ospfNbrEntry 4 }
  2903. +
  2904. +
  2905. + ospfNbrPriority OBJECT-TYPE
  2906. + SYNTAX DesignatedRouterPriority
  2907. + MAX-ACCESS read-create
  2908. + STATUS current
  2909. + DESCRIPTION
  2910. + "The priority of this neighbor in the designat-
  2911. + ed router election algorithm. The value 0 sig-
  2912. + nifies that the neighbor is not eligible to be-
  2913. + come the designated router on this particular
  2914. + network."
  2915. + DEFVAL { 1 }
  2916. + ::= { ospfNbrEntry 5 }
  2917. +
  2918. +
  2919. + ospfNbrState OBJECT-TYPE
  2920. + SYNTAX INTEGER {
  2921. + down (1),
  2922. + attempt (2),
  2923. + init (3),
  2924. + twoWay (4),
  2925. + exchangeStart (5),
  2926. + exchange (6),
  2927. + loading (7),
  2928. + full (8)
  2929. + }
  2930. + MAX-ACCESS read-only
  2931. + STATUS current
  2932. + DESCRIPTION
  2933. + "The State of the relationship with this Neigh-
  2934. + bor."
  2935. + REFERENCE
  2936. + "OSPF Version 2, Section 10.1 Neighbor States"
  2937. + DEFVAL { down }
  2938. + ::= { ospfNbrEntry 6 }
  2939. +
  2940. +
  2941. + ospfNbrEvents OBJECT-TYPE
  2942. + SYNTAX Counter32
  2943. + MAX-ACCESS read-only
  2944. + STATUS current
  2945. + DESCRIPTION
  2946. + "The number of times this neighbor relationship
  2947. + has changed state, or an error has occurred."
  2948. + ::= { ospfNbrEntry 7 }
  2949. +
  2950. +
  2951. + ospfNbrLsRetransQLen OBJECT-TYPE
  2952. + SYNTAX Gauge32
  2953. + MAX-ACCESS read-only
  2954. + STATUS current
  2955. + DESCRIPTION
  2956. + "The current length of the retransmission
  2957. + queue."
  2958. + ::= { ospfNbrEntry 8 }
  2959. +
  2960. +
  2961. + ospfNbmaNbrStatus OBJECT-TYPE
  2962. + SYNTAX RowStatus
  2963. + MAX-ACCESS read-create
  2964. + STATUS current
  2965. + DESCRIPTION
  2966. + "This variable displays the status of the en-
  2967. + try. Setting it to 'invalid' has the effect of
  2968. + rendering it inoperative. The internal effect
  2969. + (row removal) is implementation dependent."
  2970. + ::= { ospfNbrEntry 9 }
  2971. +
  2972. +
  2973. + ospfNbmaNbrPermanence OBJECT-TYPE
  2974. + SYNTAX INTEGER {
  2975. + dynamic (1), -- learned through protocol
  2976. + permanent (2) -- configured address
  2977. + }
  2978. + MAX-ACCESS read-only
  2979. + STATUS current
  2980. + DESCRIPTION
  2981. + "This variable displays the status of the en-
  2982. + try. 'dynamic' and 'permanent' refer to how
  2983. + the neighbor became known."
  2984. + DEFVAL { permanent }
  2985. + ::= { ospfNbrEntry 10 }
  2986. +
  2987. +
  2988. + ospfNbrHelloSuppressed OBJECT-TYPE
  2989. + SYNTAX TruthValue
  2990. + MAX-ACCESS read-only
  2991. + STATUS current
  2992. + DESCRIPTION
  2993. + "Indicates whether Hellos are being suppressed
  2994. + to the neighbor"
  2995. + ::= { ospfNbrEntry 11 }
  2996. +
  2997. +
  2998. +-- OSPF Virtual Neighbor Table
  2999. +
  3000. +-- This table describes all virtual neighbors.
  3001. +-- Since Virtual Links are configured in the
  3002. +-- virtual interface table, this table is read-only.
  3003. +
  3004. + ospfVirtNbrTable OBJECT-TYPE
  3005. + SYNTAX SEQUENCE OF OspfVirtNbrEntry
  3006. + MAX-ACCESS not-accessible
  3007. + STATUS current
  3008. + DESCRIPTION
  3009. + "A table of virtual neighbor information."
  3010. + REFERENCE
  3011. + "OSPF Version 2, Section 15 Virtual Links"
  3012. + ::= { ospf 11 }
  3013. +
  3014. +
  3015. + ospfVirtNbrEntry OBJECT-TYPE
  3016. + SYNTAX OspfVirtNbrEntry
  3017. + MAX-ACCESS not-accessible
  3018. + STATUS current
  3019. + DESCRIPTION
  3020. + "Virtual neighbor information."
  3021. + INDEX { ospfVirtNbrArea, ospfVirtNbrRtrId }
  3022. + ::= { ospfVirtNbrTable 1 }
  3023. +
  3024. +OspfVirtNbrEntry ::=
  3025. + SEQUENCE {
  3026. + ospfVirtNbrArea
  3027. + AreaID,
  3028. + ospfVirtNbrRtrId
  3029. + RouterID,
  3030. + ospfVirtNbrIpAddr
  3031. + IpAddress,
  3032. + ospfVirtNbrOptions
  3033. + Integer32,
  3034. + ospfVirtNbrState
  3035. + INTEGER,
  3036. + ospfVirtNbrEvents
  3037. + Counter32,
  3038. + ospfVirtNbrLsRetransQLen
  3039. + Gauge32,
  3040. + ospfVirtNbrHelloSuppressed
  3041. + TruthValue
  3042. + }
  3043. +
  3044. + ospfVirtNbrArea OBJECT-TYPE
  3045. + SYNTAX AreaID
  3046. + MAX-ACCESS read-only
  3047. + STATUS current
  3048. + DESCRIPTION
  3049. + "The Transit Area Identifier."
  3050. + ::= { ospfVirtNbrEntry 1 }
  3051. +
  3052. +
  3053. + ospfVirtNbrRtrId OBJECT-TYPE
  3054. + SYNTAX RouterID
  3055. + MAX-ACCESS read-only
  3056. + STATUS current
  3057. + DESCRIPTION
  3058. + "A 32-bit integer uniquely identifying the
  3059. + neighboring router in the Autonomous System."
  3060. + ::= { ospfVirtNbrEntry 2 }
  3061. +
  3062. +
  3063. + ospfVirtNbrIpAddr OBJECT-TYPE
  3064. + SYNTAX IpAddress
  3065. + MAX-ACCESS read-only
  3066. + STATUS current
  3067. + DESCRIPTION
  3068. + "The IP address this Virtual Neighbor is us-
  3069. + ing."
  3070. + ::= { ospfVirtNbrEntry 3 }
  3071. +
  3072. +
  3073. + ospfVirtNbrOptions OBJECT-TYPE
  3074. + SYNTAX Integer32
  3075. + MAX-ACCESS read-only
  3076. + STATUS current
  3077. + DESCRIPTION
  3078. + "A Bit Mask corresponding to the neighbor's op-
  3079. + tions field.
  3080. +
  3081. + Bit 1, if set, indicates that the system will
  3082. + operate on Type of Service metrics other than
  3083. + TOS 0. If zero, the neighbor will ignore all
  3084. + metrics except the TOS 0 metric.
  3085. +
  3086. + Bit 2, if set, indicates that the system is
  3087. + Network Multicast capable; ie, that it imple-
  3088. + ments OSPF Multicast Routing."
  3089. + ::= { ospfVirtNbrEntry 4 }
  3090. + ospfVirtNbrState OBJECT-TYPE
  3091. + SYNTAX INTEGER {
  3092. + down (1),
  3093. + attempt (2),
  3094. + init (3),
  3095. + twoWay (4),
  3096. + exchangeStart (5),
  3097. + exchange (6),
  3098. + loading (7),
  3099. + full (8)
  3100. + }
  3101. + MAX-ACCESS read-only
  3102. + STATUS current
  3103. + DESCRIPTION
  3104. + "The state of the Virtual Neighbor Relation-
  3105. + ship."
  3106. + ::= { ospfVirtNbrEntry 5 }
  3107. +
  3108. +
  3109. + ospfVirtNbrEvents OBJECT-TYPE
  3110. + SYNTAX Counter32
  3111. + MAX-ACCESS read-only
  3112. + STATUS current
  3113. + DESCRIPTION
  3114. + "The number of times this virtual link has
  3115. + changed its state, or an error has occurred."
  3116. + ::= { ospfVirtNbrEntry 6 }
  3117. +
  3118. +
  3119. + ospfVirtNbrLsRetransQLen OBJECT-TYPE
  3120. + SYNTAX Gauge32
  3121. + MAX-ACCESS read-only
  3122. + STATUS current
  3123. + DESCRIPTION
  3124. + "The current length of the retransmission
  3125. + queue."
  3126. + ::= { ospfVirtNbrEntry 7 }
  3127. +
  3128. +
  3129. + ospfVirtNbrHelloSuppressed OBJECT-TYPE
  3130. + SYNTAX TruthValue
  3131. + MAX-ACCESS read-only
  3132. + STATUS current
  3133. + DESCRIPTION
  3134. + "Indicates whether Hellos are being suppressed
  3135. + to the neighbor"
  3136. + ::= { ospfVirtNbrEntry 8 }
  3137. +
  3138. +-- OSPF Link State Database, External
  3139. +
  3140. +-- The Link State Database contains the Link State
  3141. +-- Advertisements from throughout the areas that the
  3142. +-- device is attached to.
  3143. +
  3144. +-- This table is identical to the OSPF LSDB Table in
  3145. +-- format, but contains only External Link State
  3146. +-- Advertisements. The purpose is to allow external
  3147. +-- LSAs to be displayed once for the router rather
  3148. +-- than once in each non-stub area.
  3149. +
  3150. + ospfExtLsdbTable OBJECT-TYPE
  3151. + SYNTAX SEQUENCE OF OspfExtLsdbEntry
  3152. + MAX-ACCESS not-accessible
  3153. + STATUS current
  3154. + DESCRIPTION
  3155. + "The OSPF Process's Links State Database."
  3156. + REFERENCE
  3157. + "OSPF Version 2, Section 12 Link State Adver-
  3158. + tisements"
  3159. + ::= { ospf 12 }
  3160. +
  3161. +
  3162. + ospfExtLsdbEntry OBJECT-TYPE
  3163. + SYNTAX OspfExtLsdbEntry
  3164. + MAX-ACCESS not-accessible
  3165. + STATUS current
  3166. + DESCRIPTION
  3167. + "A single Link State Advertisement."
  3168. + INDEX { ospfExtLsdbType, ospfExtLsdbLsid, ospfExtLsdbRouterId }
  3169. + ::= { ospfExtLsdbTable 1 }
  3170. +
  3171. +OspfExtLsdbEntry ::=
  3172. + SEQUENCE {
  3173. + ospfExtLsdbType
  3174. + INTEGER,
  3175. + ospfExtLsdbLsid
  3176. + IpAddress,
  3177. + ospfExtLsdbRouterId
  3178. + RouterID,
  3179. + ospfExtLsdbSequence
  3180. + Integer32,
  3181. + ospfExtLsdbAge
  3182. + Integer32,
  3183. + ospfExtLsdbChecksum
  3184. + Integer32,
  3185. + ospfExtLsdbAdvertisement
  3186. + OCTET STRING
  3187. + }
  3188. +
  3189. + ospfExtLsdbType OBJECT-TYPE
  3190. + SYNTAX INTEGER {
  3191. + asExternalLink (5)
  3192. + }
  3193. + MAX-ACCESS read-only
  3194. + STATUS current
  3195. + DESCRIPTION
  3196. + "The type of the link state advertisement.
  3197. + Each link state type has a separate advertise-
  3198. + ment format."
  3199. + REFERENCE
  3200. + "OSPF Version 2, Appendix A.4.1 The Link State
  3201. + Advertisement header"
  3202. + ::= { ospfExtLsdbEntry 1 }
  3203. +
  3204. +
  3205. + ospfExtLsdbLsid OBJECT-TYPE
  3206. + SYNTAX IpAddress
  3207. + MAX-ACCESS read-only
  3208. + STATUS current
  3209. + DESCRIPTION
  3210. + "The Link State ID is an LS Type Specific field
  3211. + containing either a Router ID or an IP Address;
  3212. + it identifies the piece of the routing domain
  3213. + that is being described by the advertisement."
  3214. + REFERENCE
  3215. + "OSPF Version 2, Section 12.1.4 Link State ID"
  3216. + ::= { ospfExtLsdbEntry 2 }
  3217. +
  3218. +
  3219. + ospfExtLsdbRouterId OBJECT-TYPE
  3220. + SYNTAX RouterID
  3221. + MAX-ACCESS read-only
  3222. + STATUS current
  3223. + DESCRIPTION
  3224. + "The 32 bit number that uniquely identifies the
  3225. + originating router in the Autonomous System."
  3226. + REFERENCE
  3227. + "OSPF Version 2, Appendix C.1 Global parameters"
  3228. + ::= { ospfExtLsdbEntry 3 }
  3229. +
  3230. +-- Note that the OSPF Sequence Number is a 32 bit signed
  3231. +-- integer. It starts with the value '80000001'h,
  3232. +-- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h
  3233. +-- Thus, a typical sequence number will be very negative.
  3234. + ospfExtLsdbSequence OBJECT-TYPE
  3235. + SYNTAX Integer32
  3236. + MAX-ACCESS read-only
  3237. + STATUS current
  3238. + DESCRIPTION
  3239. + "The sequence number field is a signed 32-bit
  3240. + integer. It is used to detect old and dupli-
  3241. + cate link state advertisements. The space of
  3242. + sequence numbers is linearly ordered. The
  3243. + larger the sequence number the more recent the
  3244. + advertisement."
  3245. + REFERENCE
  3246. + "OSPF Version 2, Section 12.1.6 LS sequence
  3247. + number"
  3248. + ::= { ospfExtLsdbEntry 4 }
  3249. +
  3250. +
  3251. + ospfExtLsdbAge OBJECT-TYPE
  3252. + SYNTAX Integer32 -- Should be 0..MaxAge
  3253. + MAX-ACCESS read-only
  3254. + STATUS current
  3255. + DESCRIPTION
  3256. + "This field is the age of the link state adver-
  3257. + tisement in seconds."
  3258. + REFERENCE
  3259. + "OSPF Version 2, Section 12.1.1 LS age"
  3260. + ::= { ospfExtLsdbEntry 5 }
  3261. +
  3262. +
  3263. + ospfExtLsdbChecksum OBJECT-TYPE
  3264. + SYNTAX Integer32
  3265. + MAX-ACCESS read-only
  3266. + STATUS current
  3267. + DESCRIPTION
  3268. + "This field is the checksum of the complete
  3269. + contents of the advertisement, excepting the
  3270. + age field. The age field is excepted so that
  3271. + an advertisement's age can be incremented
  3272. + without updating the checksum. The checksum
  3273. + used is the same that is used for ISO connec-
  3274. + tionless datagrams; it is commonly referred to
  3275. + as the Fletcher checksum."
  3276. + REFERENCE
  3277. + "OSPF Version 2, Section 12.1.7 LS checksum"
  3278. + ::= { ospfExtLsdbEntry 6 }
  3279. +
  3280. +
  3281. + ospfExtLsdbAdvertisement OBJECT-TYPE
  3282. + SYNTAX OCTET STRING (SIZE(36))
  3283. + MAX-ACCESS read-only
  3284. + STATUS current
  3285. + DESCRIPTION
  3286. + "The entire Link State Advertisement, including
  3287. + its header."
  3288. + REFERENCE
  3289. + "OSPF Version 2, Section 12 Link State Adver-
  3290. + tisements"
  3291. + ::= { ospfExtLsdbEntry 7 }
  3292. +
  3293. +
  3294. +-- OSPF Use of the CIDR Route Table
  3295. +
  3296. +ospfRouteGroup OBJECT IDENTIFIER ::= { ospf 13 }
  3297. +
  3298. +-- The IP Forwarding Table defines a number of objects for use by
  3299. +-- the routing protocol to externalize its information. Most of
  3300. +-- the variables (ipForwardDest, ipForwardMask, ipForwardPolicy,
  3301. +-- ipForwardNextHop, ipForwardIfIndex, ipForwardType,
  3302. +-- ipForwardProto, ipForwardAge, and ipForwardNextHopAS) are
  3303. +-- defined there.
  3304. +
  3305. +-- Those that leave some discretion are defined here.
  3306. +
  3307. +-- ipCidrRouteProto is, of course, ospf (13).
  3308. +
  3309. +-- ipCidrRouteAge is the time since the route was first calculated,
  3310. +-- as opposed to the time since the last SPF run.
  3311. +
  3312. +-- ipCidrRouteInfo is an OBJECT IDENTIFIER for use by the routing
  3313. +-- protocol. The following values shall be found there depending
  3314. +-- on the way the route was calculated.
  3315. +
  3316. +ospfIntraArea OBJECT IDENTIFIER ::= { ospfRouteGroup 1 }
  3317. +ospfInterArea OBJECT IDENTIFIER ::= { ospfRouteGroup 2 }
  3318. +ospfExternalType1 OBJECT IDENTIFIER ::= { ospfRouteGroup 3 }
  3319. +ospfExternalType2 OBJECT IDENTIFIER ::= { ospfRouteGroup 4 }
  3320. +
  3321. +-- ipCidrRouteMetric1 is, by definition, the primary routing
  3322. +-- metric. Therefore, it should be the metric that route
  3323. +-- selection is based on. For intra-area and inter-area routes,
  3324. +-- it is an OSPF metric. For External Type 1 (comparable value)
  3325. +-- routes, it is an OSPF metric plus the External Metric. For
  3326. +-- external Type 2 (non-comparable value) routes, it is the
  3327. +-- external metric.
  3328. +
  3329. +-- ipCidrRouteMetric2 is, by definition, a secondary routing
  3330. +-- metric. Therefore, it should be the metric that breaks a tie
  3331. +-- among routes having equal metric1 values and the same
  3332. +-- calculation rule. For intra-area, inter-area routes, and
  3333. +-- External Type 1 (comparable value) routes, it is unused. For
  3334. +-- external Type 2 (non-comparable value) routes, it is the metric
  3335. +-- to the AS border router.
  3336. +
  3337. +-- ipCidrRouteMetric3, ipCidrRouteMetric4, and ipCidrRouteMetric5 are
  3338. +-- unused.
  3339. +
  3340. +--
  3341. +-- The OSPF Area Aggregate Table
  3342. +--
  3343. +-- This table replaces the OSPF Area Summary Table, being an
  3344. +-- extension of that for CIDR routers.
  3345. +
  3346. + ospfAreaAggregateTable OBJECT-TYPE
  3347. + SYNTAX SEQUENCE OF OspfAreaAggregateEntry
  3348. + MAX-ACCESS not-accessible
  3349. + STATUS current
  3350. + DESCRIPTION
  3351. + "A range of IP addresses specified by an IP
  3352. + address/IP network mask pair. For example,
  3353. + class B address range of X.X.X.X with a network
  3354. + mask of 255.255.0.0 includes all IP addresses
  3355. + from X.X.0.0 to X.X.255.255. Note that if
  3356. + ranges are configured such that one range sub-
  3357. + sumes another range (e.g., 10.0.0.0 mask
  3358. + 255.0.0.0 and 10.1.0.0 mask 255.255.0.0), the
  3359. + most specific match is the preferred one."
  3360. + REFERENCE
  3361. + "OSPF Version 2, Appendix C.2 Area parameters"
  3362. + ::= { ospf 14 }
  3363. +
  3364. +
  3365. + ospfAreaAggregateEntry OBJECT-TYPE
  3366. + SYNTAX OspfAreaAggregateEntry
  3367. + MAX-ACCESS not-accessible
  3368. + STATUS current
  3369. + DESCRIPTION
  3370. + "A range of IP addresses specified by an IP
  3371. + address/IP network mask pair. For example,
  3372. + class B address range of X.X.X.X with a network
  3373. + mask of 255.255.0.0 includes all IP addresses
  3374. + from X.X.0.0 to X.X.255.255. Note that if
  3375. + ranges are range configured such that one range
  3376. + subsumes another range (e.g., 10.0.0.0 mask
  3377. + 255.0.0.0 and 10.1.0.0 mask 255.255.0.0), the
  3378. + most specific match is the preferred one."
  3379. + REFERENCE
  3380. + "OSPF Version 2, Appendix C.2 Area parameters"
  3381. + INDEX { ospfAreaAggregateAreaID, ospfAreaAggregateLsdbType,
  3382. + ospfAreaAggregateNet, ospfAreaAggregateMask }
  3383. + ::= { ospfAreaAggregateTable 1 }
  3384. +
  3385. +
  3386. +OspfAreaAggregateEntry ::=
  3387. + SEQUENCE {
  3388. + ospfAreaAggregateAreaID
  3389. + AreaID,
  3390. + ospfAreaAggregateLsdbType
  3391. + INTEGER,
  3392. + ospfAreaAggregateNet
  3393. + IpAddress,
  3394. + ospfAreaAggregateMask
  3395. + IpAddress,
  3396. + ospfAreaAggregateStatus
  3397. + RowStatus,
  3398. + ospfAreaAggregateEffect
  3399. + INTEGER
  3400. + }
  3401. +
  3402. + ospfAreaAggregateAreaID OBJECT-TYPE
  3403. + SYNTAX AreaID
  3404. + MAX-ACCESS read-only
  3405. + STATUS current
  3406. + DESCRIPTION
  3407. + "The Area the Address Aggregate is to be found
  3408. + within."
  3409. + REFERENCE
  3410. + "OSPF Version 2, Appendix C.2 Area parameters"
  3411. + ::= { ospfAreaAggregateEntry 1 }
  3412. +
  3413. +
  3414. + ospfAreaAggregateLsdbType OBJECT-TYPE
  3415. + SYNTAX INTEGER {
  3416. + summaryLink (3),
  3417. + nssaExternalLink (7)
  3418. + }
  3419. + MAX-ACCESS read-only
  3420. + STATUS current
  3421. + DESCRIPTION
  3422. + "The type of the Address Aggregate. This field
  3423. + specifies the Lsdb type that this Address Ag-
  3424. + gregate applies to."
  3425. + REFERENCE
  3426. + "OSPF Version 2, Appendix A.4.1 The Link State
  3427. + Advertisement header"
  3428. + ::= { ospfAreaAggregateEntry 2 }
  3429. +
  3430. +
  3431. + ospfAreaAggregateNet OBJECT-TYPE
  3432. + SYNTAX IpAddress
  3433. + MAX-ACCESS read-only
  3434. + STATUS current
  3435. + DESCRIPTION
  3436. + "The IP Address of the Net or Subnet indicated
  3437. + by the range."
  3438. + REFERENCE
  3439. + "OSPF Version 2, Appendix C.2 Area parameters"
  3440. + ::= { ospfAreaAggregateEntry 3 }
  3441. +
  3442. +
  3443. + ospfAreaAggregateMask OBJECT-TYPE
  3444. + SYNTAX IpAddress
  3445. + MAX-ACCESS read-only
  3446. + STATUS current
  3447. + DESCRIPTION
  3448. + "The Subnet Mask that pertains to the Net or
  3449. + Subnet."
  3450. + REFERENCE
  3451. + "OSPF Version 2, Appendix C.2 Area parameters"
  3452. + ::= { ospfAreaAggregateEntry 4 }
  3453. +
  3454. +
  3455. + ospfAreaAggregateStatus OBJECT-TYPE
  3456. + SYNTAX RowStatus
  3457. + MAX-ACCESS read-create
  3458. + STATUS current
  3459. + DESCRIPTION
  3460. + "This variable displays the status of the en-
  3461. + try. Setting it to 'invalid' has the effect of
  3462. + rendering it inoperative. The internal effect
  3463. + (row removal) is implementation dependent."
  3464. + ::= { ospfAreaAggregateEntry 5 }
  3465. +
  3466. +
  3467. + ospfAreaAggregateEffect OBJECT-TYPE
  3468. + SYNTAX INTEGER {
  3469. + advertiseMatching (1),
  3470. + doNotAdvertiseMatching (2)
  3471. + }
  3472. + MAX-ACCESS read-create
  3473. + STATUS current
  3474. + DESCRIPTION
  3475. + "Subnets subsumed by ranges either trigger the
  3476. + advertisement of the indicated aggregate (ad-
  3477. + vertiseMatching), or result in the subnet's not
  3478. + being advertised at all outside the area."
  3479. + DEFVAL { advertiseMatching }
  3480. + ::= { ospfAreaAggregateEntry 6 }
  3481. +
  3482. +
  3483. +-- conformance information
  3484. +
  3485. +ospfConformance OBJECT IDENTIFIER ::= { ospf 15 }
  3486. +
  3487. +ospfGroups OBJECT IDENTIFIER ::= { ospfConformance 1 }
  3488. +ospfCompliances OBJECT IDENTIFIER ::= { ospfConformance 2 }
  3489. +
  3490. +-- compliance statements
  3491. +
  3492. + ospfCompliance MODULE-COMPLIANCE
  3493. + STATUS current
  3494. + DESCRIPTION
  3495. + "The compliance statement "
  3496. + MODULE -- this module
  3497. + MANDATORY-GROUPS {
  3498. + ospfBasicGroup,
  3499. + ospfAreaGroup,
  3500. + ospfStubAreaGroup,
  3501. + ospfIfGroup,
  3502. + ospfIfMetricGroup,
  3503. + ospfVirtIfGroup,
  3504. + ospfNbrGroup,
  3505. + ospfVirtNbrGroup,
  3506. + ospfAreaAggregateGroup
  3507. + }
  3508. + ::= { ospfCompliances 1 }
  3509. +
  3510. +
  3511. +-- units of conformance
  3512. +
  3513. + ospfBasicGroup OBJECT-GROUP
  3514. + OBJECTS {
  3515. + ospfRouterId,
  3516. + ospfAdminStat,
  3517. + ospfVersionNumber,
  3518. + ospfAreaBdrRtrStatus,
  3519. + ospfASBdrRtrStatus,
  3520. + ospfExternLsaCount,
  3521. + ospfExternLsaCksumSum,
  3522. + ospfTOSSupport,
  3523. + ospfOriginateNewLsas,
  3524. + ospfRxNewLsas,
  3525. + ospfExtLsdbLimit,
  3526. + ospfMulticastExtensions,
  3527. + ospfExitOverflowInterval,
  3528. + ospfDemandExtensions
  3529. + }
  3530. + STATUS current
  3531. + DESCRIPTION
  3532. + "These objects are required for OSPF systems."
  3533. + ::= { ospfGroups 1 }
  3534. +
  3535. +
  3536. + ospfAreaGroup OBJECT-GROUP
  3537. + OBJECTS {
  3538. + ospfAreaId,
  3539. + ospfImportAsExtern,
  3540. + ospfSpfRuns,
  3541. + ospfAreaBdrRtrCount,
  3542. + ospfAsBdrRtrCount,
  3543. + ospfAreaLsaCount,
  3544. + ospfAreaLsaCksumSum,
  3545. + ospfAreaSummary,
  3546. + ospfAreaStatus
  3547. + }
  3548. + STATUS current
  3549. + DESCRIPTION
  3550. + "These objects are required for OSPF systems
  3551. + supporting areas."
  3552. + ::= { ospfGroups 2 }
  3553. +
  3554. +
  3555. + ospfStubAreaGroup OBJECT-GROUP
  3556. + OBJECTS {
  3557. + ospfStubAreaId,
  3558. + ospfStubTOS,
  3559. + ospfStubMetric,
  3560. + ospfStubStatus,
  3561. + ospfStubMetricType
  3562. + }
  3563. + STATUS current
  3564. + DESCRIPTION
  3565. + "These objects are required for OSPF systems
  3566. + supporting stub areas."
  3567. + ::= { ospfGroups 3 }
  3568. +
  3569. +
  3570. + ospfLsdbGroup OBJECT-GROUP
  3571. + OBJECTS {
  3572. + ospfLsdbAreaId,
  3573. + ospfLsdbType,
  3574. + ospfLsdbLsid,
  3575. + ospfLsdbRouterId,
  3576. + ospfLsdbSequence,
  3577. + ospfLsdbAge,
  3578. + ospfLsdbChecksum,
  3579. + ospfLsdbAdvertisement
  3580. + }
  3581. + STATUS current
  3582. + DESCRIPTION
  3583. + "These objects are required for OSPF systems
  3584. + that display their link state database."
  3585. + ::= { ospfGroups 4 }
  3586. +
  3587. +
  3588. + ospfAreaRangeGroup OBJECT-GROUP
  3589. + OBJECTS {
  3590. + ospfAreaRangeAreaId,
  3591. + ospfAreaRangeNet,
  3592. + ospfAreaRangeMask,
  3593. + ospfAreaRangeStatus,
  3594. + ospfAreaRangeEffect
  3595. + }
  3596. + STATUS obsolete
  3597. + DESCRIPTION
  3598. + "These objects are required for non-CIDR OSPF
  3599. + systems that support multiple areas."
  3600. + ::= { ospfGroups 5 }
  3601. +
  3602. +
  3603. + ospfHostGroup OBJECT-GROUP
  3604. + OBJECTS {
  3605. + ospfHostIpAddress,
  3606. + ospfHostTOS,
  3607. + ospfHostMetric,
  3608. + ospfHostStatus,
  3609. + ospfHostAreaID
  3610. + }
  3611. + STATUS current
  3612. + DESCRIPTION
  3613. + "These objects are required for OSPF systems
  3614. + that support attached hosts."
  3615. + ::= { ospfGroups 6 }
  3616. +
  3617. +
  3618. + ospfIfGroup OBJECT-GROUP
  3619. + OBJECTS {
  3620. + ospfIfIpAddress,
  3621. + ospfAddressLessIf,
  3622. + ospfIfAreaId,
  3623. + ospfIfType,
  3624. + ospfIfAdminStat,
  3625. + ospfIfRtrPriority,
  3626. + ospfIfTransitDelay,
  3627. + ospfIfRetransInterval,
  3628. + ospfIfHelloInterval,
  3629. + ospfIfRtrDeadInterval,
  3630. + ospfIfPollInterval,
  3631. + ospfIfState,
  3632. + ospfIfDesignatedRouter,
  3633. + ospfIfBackupDesignatedRouter,
  3634. + ospfIfEvents,
  3635. + ospfIfAuthType,
  3636. + ospfIfAuthKey,
  3637. + ospfIfStatus,
  3638. + ospfIfMulticastForwarding,
  3639. + ospfIfDemand
  3640. + }
  3641. + STATUS current
  3642. + DESCRIPTION
  3643. + "These objects are required for OSPF systems."
  3644. + ::= { ospfGroups 7 }
  3645. +
  3646. +
  3647. + ospfIfMetricGroup OBJECT-GROUP
  3648. + OBJECTS {
  3649. + ospfIfMetricIpAddress,
  3650. + ospfIfMetricAddressLessIf,
  3651. + ospfIfMetricTOS,
  3652. + ospfIfMetricValue,
  3653. + ospfIfMetricStatus
  3654. + }
  3655. + STATUS current
  3656. + DESCRIPTION
  3657. + "These objects are required for OSPF systems."
  3658. + ::= { ospfGroups 8 }
  3659. +
  3660. +
  3661. + ospfVirtIfGroup OBJECT-GROUP
  3662. + OBJECTS {
  3663. + ospfVirtIfAreaId,
  3664. + ospfVirtIfNeighbor,
  3665. + ospfVirtIfTransitDelay,
  3666. + ospfVirtIfRetransInterval,
  3667. + ospfVirtIfHelloInterval,
  3668. + ospfVirtIfRtrDeadInterval,
  3669. + ospfVirtIfState,
  3670. + ospfVirtIfEvents,
  3671. + ospfVirtIfAuthType,
  3672. + ospfVirtIfAuthKey,
  3673. + ospfVirtIfStatus
  3674. + }
  3675. + STATUS current
  3676. + DESCRIPTION
  3677. + "These objects are required for OSPF systems."
  3678. + ::= { ospfGroups 9 }
  3679. +
  3680. +
  3681. + ospfNbrGroup OBJECT-GROUP
  3682. + OBJECTS {
  3683. + ospfNbrIpAddr,
  3684. + ospfNbrAddressLessIndex,
  3685. + ospfNbrRtrId,
  3686. + ospfNbrOptions,
  3687. + ospfNbrPriority,
  3688. + ospfNbrState,
  3689. + ospfNbrEvents,
  3690. + ospfNbrLsRetransQLen,
  3691. + ospfNbmaNbrStatus,
  3692. + ospfNbmaNbrPermanence,
  3693. + ospfNbrHelloSuppressed
  3694. + }
  3695. + STATUS current
  3696. + DESCRIPTION
  3697. + "These objects are required for OSPF systems."
  3698. + ::= { ospfGroups 10 }
  3699. +
  3700. +
  3701. + ospfVirtNbrGroup OBJECT-GROUP
  3702. + OBJECTS {
  3703. + ospfVirtNbrArea,
  3704. + ospfVirtNbrRtrId,
  3705. + ospfVirtNbrIpAddr,
  3706. + ospfVirtNbrOptions,
  3707. + ospfVirtNbrState,
  3708. + ospfVirtNbrEvents,
  3709. + ospfVirtNbrLsRetransQLen,
  3710. + ospfVirtNbrHelloSuppressed
  3711. + }
  3712. + STATUS current
  3713. + DESCRIPTION
  3714. + "These objects are required for OSPF systems."
  3715. + ::= { ospfGroups 11 }
  3716. +
  3717. +
  3718. + ospfExtLsdbGroup OBJECT-GROUP
  3719. + OBJECTS {
  3720. + ospfExtLsdbType,
  3721. + ospfExtLsdbLsid,
  3722. + ospfExtLsdbRouterId,
  3723. + ospfExtLsdbSequence,
  3724. + ospfExtLsdbAge,
  3725. + ospfExtLsdbChecksum,
  3726. + ospfExtLsdbAdvertisement
  3727. + }
  3728. + STATUS current
  3729. + DESCRIPTION
  3730. + "These objects are required for OSPF systems
  3731. + that display their link state database."
  3732. + ::= { ospfGroups 12 }
  3733. +
  3734. +
  3735. + ospfAreaAggregateGroup OBJECT-GROUP
  3736. + OBJECTS {
  3737. + ospfAreaAggregateAreaID,
  3738. + ospfAreaAggregateLsdbType,
  3739. + ospfAreaAggregateNet,
  3740. + ospfAreaAggregateMask,
  3741. + ospfAreaAggregateStatus,
  3742. + ospfAreaAggregateEffect
  3743. + }
  3744. + STATUS current
  3745. + DESCRIPTION
  3746. + "These objects are required for OSPF systems."
  3747. + ::= { ospfGroups 13 }
  3748. +
  3749. +END
  3750. --- /dev/null
  3751. +++ b/mibs/OSPF-TRAP-MIB.txt
  3752. @@ -0,0 +1,443 @@
  3753. +OSPF-TRAP-MIB DEFINITIONS ::= BEGIN
  3754. +
  3755. + IMPORTS
  3756. + MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, IpAddress
  3757. + FROM SNMPv2-SMI
  3758. + MODULE-COMPLIANCE, OBJECT-GROUP
  3759. + FROM SNMPv2-CONF
  3760. + ospfRouterId, ospfIfIpAddress, ospfAddressLessIf, ospfIfState,
  3761. + ospfVirtIfAreaId, ospfVirtIfNeighbor, ospfVirtIfState,
  3762. + ospfNbrIpAddr, ospfNbrAddressLessIndex, ospfNbrRtrId,
  3763. + ospfNbrState, ospfVirtNbrArea, ospfVirtNbrRtrId, ospfVirtNbrState,
  3764. + ospfLsdbType, ospfLsdbLsid, ospfLsdbRouterId, ospfLsdbAreaId,
  3765. + ospfExtLsdbLimit, ospf
  3766. + FROM OSPF-MIB;
  3767. +
  3768. + ospfTrap MODULE-IDENTITY
  3769. + LAST-UPDATED "9501201225Z" -- Fri Jan 20 12:25:50 PST 1995
  3770. + ORGANIZATION "IETF OSPF Working Group"
  3771. + CONTACT-INFO
  3772. + " Fred Baker
  3773. + Postal: Cisco Systems
  3774. + 519 Lado Drive
  3775. + Santa Barbara, California 93111
  3776. + Tel: +1 805 681 0115
  3777. + E-Mail: fred@cisco.com
  3778. +
  3779. + Rob Coltun
  3780. + Postal: RainbowBridge Communications
  3781. + Tel: (301) 340-9416
  3782. + E-Mail: rcoltun@rainbow-bridge.com"
  3783. + DESCRIPTION
  3784. + "The MIB module to describe traps for the OSPF
  3785. + Version 2 Protocol."
  3786. + ::= { ospf 16 }
  3787. +
  3788. +-- Trap Support Objects
  3789. +
  3790. +-- The following are support objects for the OSPF traps.
  3791. +
  3792. +ospfTrapControl OBJECT IDENTIFIER ::= { ospfTrap 1 }
  3793. +ospfTraps OBJECT IDENTIFIER ::= { ospfTrap 2 }
  3794. +
  3795. + ospfSetTrap OBJECT-TYPE
  3796. + SYNTAX OCTET STRING (SIZE(4))
  3797. + MAX-ACCESS read-write
  3798. + STATUS current
  3799. + DESCRIPTION
  3800. + "A four-octet string serving as a bit map for
  3801. + the trap events defined by the OSPF traps. This
  3802. + object is used to enable and disable specific
  3803. + OSPF traps where a 1 in the bit field
  3804. + represents enabled. The right-most bit (least
  3805. + significant) represents trap 0."
  3806. + ::= { ospfTrapControl 1 }
  3807. +
  3808. +
  3809. + ospfConfigErrorType OBJECT-TYPE
  3810. + SYNTAX INTEGER {
  3811. + badVersion (1),
  3812. + areaMismatch (2),
  3813. + unknownNbmaNbr (3), -- Router is Dr eligible
  3814. + unknownVirtualNbr (4),
  3815. + authTypeMismatch(5),
  3816. + authFailure (6),
  3817. + netMaskMismatch (7),
  3818. + helloIntervalMismatch (8),
  3819. + deadIntervalMismatch (9),
  3820. + optionMismatch (10) }
  3821. + MAX-ACCESS read-only
  3822. + STATUS current
  3823. + DESCRIPTION
  3824. + "Potential types of configuration conflicts.
  3825. + Used by the ospfConfigError and ospfConfigVir-
  3826. + tError traps."
  3827. + ::= { ospfTrapControl 2 }
  3828. +
  3829. +
  3830. + ospfPacketType OBJECT-TYPE
  3831. + SYNTAX INTEGER {
  3832. + hello (1),
  3833. + dbDescript (2),
  3834. + lsReq (3),
  3835. + lsUpdate (4),
  3836. + lsAck (5) }
  3837. + MAX-ACCESS read-only
  3838. + STATUS current
  3839. + DESCRIPTION
  3840. + "OSPF packet types."
  3841. + ::= { ospfTrapControl 3 }
  3842. +
  3843. +
  3844. + ospfPacketSrc OBJECT-TYPE
  3845. + SYNTAX IpAddress
  3846. + MAX-ACCESS read-only
  3847. + STATUS current
  3848. + DESCRIPTION
  3849. + "The IP address of an inbound packet that can-
  3850. + not be identified by a neighbor instance."
  3851. + ::= { ospfTrapControl 4 }
  3852. +
  3853. +
  3854. +-- Traps
  3855. +
  3856. +
  3857. + ospfIfStateChange NOTIFICATION-TYPE
  3858. + OBJECTS {
  3859. + ospfRouterId, -- The originator of the trap
  3860. + ospfIfIpAddress,
  3861. + ospfAddressLessIf,
  3862. + ospfIfState -- The new state
  3863. + }
  3864. + STATUS current
  3865. + DESCRIPTION
  3866. + "An ospfIfStateChange trap signifies that there
  3867. + has been a change in the state of a non-virtual
  3868. + OSPF interface. This trap should be generated
  3869. + when the interface state regresses (e.g., goes
  3870. + from Dr to Down) or progresses to a terminal
  3871. + state (i.e., Point-to-Point, DR Other, Dr, or
  3872. + Backup)."
  3873. + ::= { ospfTraps 16 }
  3874. +
  3875. +
  3876. + ospfVirtIfStateChange NOTIFICATION-TYPE
  3877. + OBJECTS {
  3878. + ospfRouterId, -- The originator of the trap
  3879. + ospfVirtIfAreaId,
  3880. + ospfVirtIfNeighbor,
  3881. + ospfVirtIfState -- The new state
  3882. + }
  3883. + STATUS current
  3884. + DESCRIPTION
  3885. + "An ospfIfStateChange trap signifies that there
  3886. + has been a change in the state of an OSPF vir-
  3887. + tual interface.
  3888. + This trap should be generated when the inter-
  3889. + face state regresses (e.g., goes from Point-
  3890. + to-Point to Down) or progresses to a terminal
  3891. + state (i.e., Point-to-Point)."
  3892. + ::= { ospfTraps 1 }
  3893. +
  3894. +
  3895. + ospfNbrStateChange NOTIFICATION-TYPE
  3896. + OBJECTS {
  3897. + ospfRouterId, -- The originator of the trap
  3898. + ospfNbrIpAddr,
  3899. + ospfNbrAddressLessIndex,
  3900. + ospfNbrRtrId,
  3901. + ospfNbrState -- The new state
  3902. + }
  3903. + STATUS current
  3904. + DESCRIPTION
  3905. + "An ospfNbrStateChange trap signifies that
  3906. + there has been a change in the state of a non-
  3907. + virtual OSPF neighbor. This trap should be
  3908. + generated when the neighbor state regresses
  3909. + (e.g., goes from Attempt or Full to 1-Way or
  3910. + Down) or progresses to a terminal state (e.g.,
  3911. + 2-Way or Full). When an neighbor transitions
  3912. + from or to Full on non-broadcast multi-access
  3913. + and broadcast networks, the trap should be gen-
  3914. + erated by the designated router. A designated
  3915. + router transitioning to Down will be noted by
  3916. + ospfIfStateChange."
  3917. + ::= { ospfTraps 2 }
  3918. +
  3919. +
  3920. + ospfVirtNbrStateChange NOTIFICATION-TYPE
  3921. + OBJECTS {
  3922. + ospfRouterId, -- The originator of the trap
  3923. + ospfVirtNbrArea,
  3924. + ospfVirtNbrRtrId,
  3925. + ospfVirtNbrState -- The new state
  3926. + }
  3927. + STATUS current
  3928. + DESCRIPTION
  3929. + "An ospfIfStateChange trap signifies that there
  3930. + has been a change in the state of an OSPF vir-
  3931. + tual neighbor. This trap should be generated
  3932. + when the neighbor state regresses (e.g., goes
  3933. + from Attempt or Full to 1-Way or Down) or
  3934. + progresses to a terminal state (e.g., Full)."
  3935. + ::= { ospfTraps 3 }
  3936. + ospfIfConfigError NOTIFICATION-TYPE
  3937. + OBJECTS {
  3938. + ospfRouterId, -- The originator of the trap
  3939. + ospfIfIpAddress,
  3940. + ospfAddressLessIf,
  3941. + ospfPacketSrc, -- The source IP address
  3942. + ospfConfigErrorType, -- Type of error
  3943. + ospfPacketType
  3944. + }
  3945. + STATUS current
  3946. + DESCRIPTION
  3947. + "An ospfIfConfigError trap signifies that a
  3948. + packet has been received on a non-virtual in-
  3949. + terface from a router whose configuration
  3950. + parameters conflict with this router's confi-
  3951. + guration parameters. Note that the event op-
  3952. + tionMismatch should cause a trap only if it
  3953. + prevents an adjacency from forming."
  3954. + ::= { ospfTraps 4 }
  3955. +
  3956. +
  3957. + ospfVirtIfConfigError NOTIFICATION-TYPE
  3958. + OBJECTS {
  3959. + ospfRouterId, -- The originator of the trap
  3960. + ospfVirtIfAreaId,
  3961. + ospfVirtIfNeighbor,
  3962. + ospfConfigErrorType, -- Type of error
  3963. + ospfPacketType
  3964. + }
  3965. + STATUS current
  3966. + DESCRIPTION
  3967. + "An ospfConfigError trap signifies that a pack-
  3968. + et has been received on a virtual interface
  3969. + from a router whose configuration parameters
  3970. + conflict with this router's configuration
  3971. + parameters. Note that the event optionMismatch
  3972. + should cause a trap only if it prevents an ad-
  3973. + jacency from forming."
  3974. + ::= { ospfTraps 5 }
  3975. +
  3976. +
  3977. + ospfIfAuthFailure NOTIFICATION-TYPE
  3978. + OBJECTS {
  3979. + ospfRouterId, -- The originator of the trap
  3980. + ospfIfIpAddress,
  3981. + ospfAddressLessIf,
  3982. + ospfPacketSrc, -- The source IP address
  3983. + ospfConfigErrorType, -- authTypeMismatch or
  3984. + -- authFailure
  3985. + ospfPacketType
  3986. + }
  3987. + STATUS current
  3988. + DESCRIPTION
  3989. + "An ospfIfAuthFailure trap signifies that a
  3990. + packet has been received on a non-virtual in-
  3991. + terface from a router whose authentication key
  3992. + or authentication type conflicts with this
  3993. + router's authentication key or authentication
  3994. + type."
  3995. + ::= { ospfTraps 6 }
  3996. +
  3997. +
  3998. + ospfVirtIfAuthFailure NOTIFICATION-TYPE
  3999. + OBJECTS {
  4000. + ospfRouterId, -- The originator of the trap
  4001. + ospfVirtIfAreaId,
  4002. + ospfVirtIfNeighbor,
  4003. + ospfConfigErrorType, -- authTypeMismatch or
  4004. + -- authFailure
  4005. + ospfPacketType
  4006. + }
  4007. + STATUS current
  4008. + DESCRIPTION
  4009. + "An ospfVirtIfAuthFailure trap signifies that a
  4010. + packet has been received on a virtual interface
  4011. + from a router whose authentication key or au-
  4012. + thentication type conflicts with this router's
  4013. + authentication key or authentication type."
  4014. + ::= { ospfTraps 7 }
  4015. +
  4016. +
  4017. + ospfIfRxBadPacket NOTIFICATION-TYPE
  4018. + OBJECTS {
  4019. + ospfRouterId, -- The originator of the trap
  4020. + ospfIfIpAddress,
  4021. + ospfAddressLessIf,
  4022. + ospfPacketSrc, -- The source IP address
  4023. + ospfPacketType
  4024. + }
  4025. + STATUS current
  4026. + DESCRIPTION
  4027. + "An ospfIfRxBadPacket trap signifies that an
  4028. + OSPF packet has been received on a non-virtual
  4029. + interface that cannot be parsed."
  4030. + ::= { ospfTraps 8 }
  4031. +
  4032. + ospfVirtIfRxBadPacket NOTIFICATION-TYPE
  4033. + OBJECTS {
  4034. + ospfRouterId, -- The originator of the trap
  4035. + ospfVirtIfAreaId,
  4036. + ospfVirtIfNeighbor,
  4037. + ospfPacketType
  4038. + }
  4039. + STATUS current
  4040. + DESCRIPTION
  4041. + "An ospfRxBadPacket trap signifies that an OSPF
  4042. + packet has been received on a virtual interface
  4043. + that cannot be parsed."
  4044. + ::= { ospfTraps 9 }
  4045. +
  4046. +
  4047. + ospfTxRetransmit NOTIFICATION-TYPE
  4048. + OBJECTS {
  4049. + ospfRouterId, -- The originator of the trap
  4050. + ospfIfIpAddress,
  4051. + ospfAddressLessIf,
  4052. + ospfNbrRtrId, -- Destination
  4053. + ospfPacketType,
  4054. + ospfLsdbType,
  4055. + ospfLsdbLsid,
  4056. + ospfLsdbRouterId
  4057. + }
  4058. + STATUS current
  4059. + DESCRIPTION
  4060. + "An ospfTxRetransmit trap signifies than an
  4061. + OSPF packet has been retransmitted on a non-
  4062. + virtual interface. All packets that may be re-
  4063. + transmitted are associated with an LSDB entry.
  4064. + The LS type, LS ID, and Router ID are used to
  4065. + identify the LSDB entry."
  4066. + ::= { ospfTraps 10 }
  4067. +
  4068. +
  4069. + ospfVirtIfTxRetransmit NOTIFICATION-TYPE
  4070. + OBJECTS {
  4071. + ospfRouterId, -- The originator of the trap
  4072. + ospfVirtIfAreaId,
  4073. + ospfVirtIfNeighbor,
  4074. + ospfPacketType,
  4075. + ospfLsdbType,
  4076. + ospfLsdbLsid,
  4077. + ospfLsdbRouterId
  4078. + }
  4079. + STATUS current
  4080. + DESCRIPTION
  4081. + "An ospfTxRetransmit trap signifies than an
  4082. + OSPF packet has been retransmitted on a virtual
  4083. + interface. All packets that may be retransmit-
  4084. + ted are associated with an LSDB entry. The LS
  4085. + type, LS ID, and Router ID are used to identify
  4086. + the LSDB entry."
  4087. + ::= { ospfTraps 11 }
  4088. +
  4089. +
  4090. + ospfOriginateLsa NOTIFICATION-TYPE
  4091. + OBJECTS {
  4092. + ospfRouterId, -- The originator of the trap
  4093. + ospfLsdbAreaId, -- 0.0.0.0 for AS Externals
  4094. + ospfLsdbType,
  4095. + ospfLsdbLsid,
  4096. + ospfLsdbRouterId
  4097. + }
  4098. + STATUS current
  4099. + DESCRIPTION
  4100. + "An ospfOriginateLsa trap signifies that a new
  4101. + LSA has been originated by this router. This
  4102. + trap should not be invoked for simple refreshes
  4103. + of LSAs (which happesn every 30 minutes), but
  4104. + instead will only be invoked when an LSA is
  4105. + (re)originated due to a topology change. Addi-
  4106. + tionally, this trap does not include LSAs that
  4107. + are being flushed because they have reached
  4108. + MaxAge."
  4109. + ::= { ospfTraps 12 }
  4110. +
  4111. +
  4112. + ospfMaxAgeLsa NOTIFICATION-TYPE
  4113. + OBJECTS {
  4114. + ospfRouterId, -- The originator of the trap
  4115. + ospfLsdbAreaId, -- 0.0.0.0 for AS Externals
  4116. + ospfLsdbType,
  4117. + ospfLsdbLsid,
  4118. + ospfLsdbRouterId
  4119. + }
  4120. + STATUS current
  4121. + DESCRIPTION
  4122. + "An ospfMaxAgeLsa trap signifies that one of
  4123. + the LSA in the router's link-state database has
  4124. + aged to MaxAge."
  4125. + ::= { ospfTraps 13 }
  4126. +
  4127. +
  4128. + ospfLsdbOverflow NOTIFICATION-TYPE
  4129. + OBJECTS {
  4130. + ospfRouterId, -- The originator of the trap
  4131. + ospfExtLsdbLimit
  4132. + }
  4133. + STATUS current
  4134. + DESCRIPTION
  4135. + "An ospfLsdbOverflow trap signifies that the
  4136. + number of LSAs in the router's link-state data-
  4137. + base has exceeded ospfExtLsdbLimit."
  4138. + ::= { ospfTraps 14 }
  4139. +
  4140. +
  4141. + ospfLsdbApproachingOverflow NOTIFICATION-TYPE
  4142. + OBJECTS {
  4143. + ospfRouterId, -- The originator of the trap
  4144. + ospfExtLsdbLimit
  4145. + }
  4146. + STATUS current
  4147. + DESCRIPTION
  4148. + "An ospfLsdbApproachingOverflow trap signifies
  4149. + that the number of LSAs in the router's link-
  4150. + state database has exceeded ninety percent of
  4151. + ospfExtLsdbLimit."
  4152. + ::= { ospfTraps 15 }
  4153. +
  4154. +
  4155. +-- conformance information
  4156. +
  4157. +ospfTrapConformance OBJECT IDENTIFIER ::= { ospfTrap 3 }
  4158. +
  4159. +ospfTrapGroups OBJECT IDENTIFIER ::= { ospfTrapConformance 1 }
  4160. +ospfTrapCompliances OBJECT IDENTIFIER ::= { ospfTrapConformance 2 }
  4161. +
  4162. +-- compliance statements
  4163. +
  4164. + ospfTrapCompliance MODULE-COMPLIANCE
  4165. + STATUS current
  4166. + DESCRIPTION
  4167. + "The compliance statement "
  4168. + MODULE -- this module
  4169. + MANDATORY-GROUPS { ospfTrapControlGroup }
  4170. +
  4171. +
  4172. + GROUP ospfTrapControlGroup
  4173. + DESCRIPTION
  4174. + "This group is optional but recommended for all
  4175. + OSPF systems"
  4176. + ::= { ospfTrapCompliances 1 }
  4177. +
  4178. +
  4179. +-- units of conformance
  4180. +
  4181. + ospfTrapControlGroup OBJECT-GROUP
  4182. + OBJECTS {
  4183. + ospfSetTrap,
  4184. + ospfConfigErrorType,
  4185. + ospfPacketType,
  4186. + ospfPacketSrc
  4187. + }
  4188. + STATUS current
  4189. + DESCRIPTION
  4190. + "These objects are required to control traps
  4191. + from OSPF systems."
  4192. + ::= { ospfTrapGroups 1 }
  4193. +
  4194. +
  4195. +END
  4196. --- /dev/null
  4197. +++ b/mibs/RIPv2-MIB.txt
  4198. @@ -0,0 +1,530 @@
  4199. + RIPv2-MIB DEFINITIONS ::= BEGIN
  4200. +
  4201. + IMPORTS
  4202. + MODULE-IDENTITY, OBJECT-TYPE, Counter32,
  4203. + TimeTicks, IpAddress FROM SNMPv2-SMI
  4204. + TEXTUAL-CONVENTION, RowStatus FROM SNMPv2-TC
  4205. + MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
  4206. + mib-2 FROM RFC1213-MIB;
  4207. +
  4208. + -- This MIB module uses the extended OBJECT-TYPE macro as
  4209. + -- defined in [9].
  4210. +
  4211. + rip2 MODULE-IDENTITY
  4212. + LAST-UPDATED "9407272253Z" -- Wed Jul 27 22:53:04 PDT 1994
  4213. + ORGANIZATION "IETF RIP-II Working Group"
  4214. + CONTACT-INFO
  4215. + " Fred Baker
  4216. + Postal: Cisco Systems
  4217. + 519 Lado Drive
  4218. + Santa Barbara, California 93111
  4219. + Tel: +1 805 681 0115
  4220. + E-Mail: fbaker@cisco.com
  4221. +
  4222. + Postal: Gary Malkin
  4223. + Xylogics, Inc.
  4224. + 53 Third Avenue
  4225. + Burlington, MA 01803
  4226. +
  4227. + Phone: (617) 272-8140
  4228. + EMail: gmalkin@Xylogics.COM"
  4229. + DESCRIPTION
  4230. + "The MIB module to describe the RIP2 Version 2 Protocol"
  4231. + ::= { mib-2 23 }
  4232. +
  4233. + -- RIP-2 Management Information Base
  4234. +
  4235. + -- the RouteTag type represents the contents of the
  4236. + -- Route Domain field in the packet header or route entry.
  4237. + -- The use of the Route Domain is deprecated.
  4238. +
  4239. + RouteTag ::= TEXTUAL-CONVENTION
  4240. + STATUS current
  4241. + DESCRIPTION
  4242. + "the RouteTag type represents the contents of the Route Domain
  4243. + field in the packet header or route entry"
  4244. + SYNTAX OCTET STRING (SIZE (2))
  4245. +
  4246. +--4.1 Global Counters
  4247. +
  4248. +-- The RIP-2 Globals Group.
  4249. +-- Implementation of this group is mandatory for systems
  4250. +-- which implement RIP-2.
  4251. +
  4252. +-- These counters are intended to facilitate debugging quickly
  4253. +-- changing routes or failing neighbors
  4254. +
  4255. +rip2Globals OBJECT IDENTIFIER ::= { rip2 1 }
  4256. +
  4257. + rip2GlobalRouteChanges OBJECT-TYPE
  4258. + SYNTAX Counter32
  4259. + MAX-ACCESS read-only
  4260. + STATUS current
  4261. + DESCRIPTION
  4262. + "The number of route changes made to the IP Route
  4263. + Database by RIP. This does not include the refresh
  4264. + of a route's age."
  4265. + ::= { rip2Globals 1 }
  4266. +
  4267. + rip2GlobalQueries OBJECT-TYPE
  4268. + SYNTAX Counter32
  4269. + MAX-ACCESS read-only
  4270. + STATUS current
  4271. + DESCRIPTION
  4272. + "The number of responses sent to RIP queries
  4273. + from other systems."
  4274. + ::= { rip2Globals 2 }
  4275. +
  4276. +--4.2 RIP Interface Tables
  4277. +
  4278. +-- RIP Interfaces Groups
  4279. +-- Implementation of these Groups is mandatory for systems
  4280. +-- which implement RIP-2.
  4281. +
  4282. +-- The RIP Interface Status Table.
  4283. +
  4284. + rip2IfStatTable OBJECT-TYPE
  4285. + SYNTAX SEQUENCE OF Rip2IfStatEntry
  4286. + MAX-ACCESS not-accessible
  4287. + STATUS current
  4288. + DESCRIPTION
  4289. + "A list of subnets which require separate
  4290. + status monitoring in RIP."
  4291. + ::= { rip2 2 }
  4292. +
  4293. + rip2IfStatEntry OBJECT-TYPE
  4294. + SYNTAX Rip2IfStatEntry
  4295. + MAX-ACCESS not-accessible
  4296. + STATUS current
  4297. + DESCRIPTION
  4298. + "A Single Routing Domain in a single Subnet."
  4299. + INDEX { rip2IfStatAddress }
  4300. + ::= { rip2IfStatTable 1 }
  4301. +
  4302. + Rip2IfStatEntry ::=
  4303. + SEQUENCE {
  4304. + rip2IfStatAddress
  4305. + IpAddress,
  4306. + rip2IfStatRcvBadPackets
  4307. + Counter32,
  4308. + rip2IfStatRcvBadRoutes
  4309. + Counter32,
  4310. + rip2IfStatSentUpdates
  4311. + Counter32,
  4312. + rip2IfStatStatus
  4313. + RowStatus
  4314. + }
  4315. +
  4316. + rip2IfStatAddress OBJECT-TYPE
  4317. + SYNTAX IpAddress
  4318. + MAX-ACCESS read-only
  4319. + STATUS current
  4320. + DESCRIPTION
  4321. + "The IP Address of this system on the indicated
  4322. + subnet. For unnumbered interfaces, the value 0.0.0.N,
  4323. + where the least significant 24 bits (N) is the ifIndex
  4324. + for the IP Interface in network byte order."
  4325. + ::= { rip2IfStatEntry 1 }
  4326. +
  4327. + rip2IfStatRcvBadPackets OBJECT-TYPE
  4328. + SYNTAX Counter32
  4329. + MAX-ACCESS read-only
  4330. + STATUS current
  4331. + DESCRIPTION
  4332. + "The number of RIP response packets received by
  4333. + the RIP process which were subsequently discarded
  4334. + for any reason (e.g. a version 0 packet, or an
  4335. + unknown command type)."
  4336. + ::= { rip2IfStatEntry 2 }
  4337. +
  4338. + rip2IfStatRcvBadRoutes OBJECT-TYPE
  4339. + SYNTAX Counter32
  4340. + MAX-ACCESS read-only
  4341. + STATUS current
  4342. + DESCRIPTION
  4343. + "The number of routes, in valid RIP packets,
  4344. + which were ignored for any reason (e.g. unknown
  4345. + address family, or invalid metric)."
  4346. + ::= { rip2IfStatEntry 3 }
  4347. +
  4348. + rip2IfStatSentUpdates OBJECT-TYPE
  4349. + SYNTAX Counter32
  4350. + MAX-ACCESS read-only
  4351. + STATUS current
  4352. + DESCRIPTION
  4353. + "The number of triggered RIP updates actually
  4354. + sent on this interface. This explicitly does
  4355. + NOT include full updates sent containing new
  4356. + information."
  4357. + ::= { rip2IfStatEntry 4 }
  4358. +
  4359. + rip2IfStatStatus OBJECT-TYPE
  4360. + SYNTAX RowStatus
  4361. + MAX-ACCESS read-create
  4362. + STATUS current
  4363. + DESCRIPTION
  4364. + "Writing invalid has the effect of deleting
  4365. + this interface."
  4366. + ::= { rip2IfStatEntry 5 }
  4367. +
  4368. +-- The RIP Interface Configuration Table.
  4369. +
  4370. + rip2IfConfTable OBJECT-TYPE
  4371. + SYNTAX SEQUENCE OF Rip2IfConfEntry
  4372. + MAX-ACCESS not-accessible
  4373. + STATUS current
  4374. + DESCRIPTION
  4375. + "A list of subnets which require separate
  4376. + configuration in RIP."
  4377. + ::= { rip2 3 }
  4378. +
  4379. + rip2IfConfEntry OBJECT-TYPE
  4380. + SYNTAX Rip2IfConfEntry
  4381. + MAX-ACCESS not-accessible
  4382. + STATUS current
  4383. + DESCRIPTION
  4384. + "A Single Routing Domain in a single Subnet."
  4385. + INDEX { rip2IfConfAddress }
  4386. + ::= { rip2IfConfTable 1 }
  4387. +
  4388. + Rip2IfConfEntry ::=
  4389. + SEQUENCE {
  4390. + rip2IfConfAddress
  4391. + IpAddress,
  4392. + rip2IfConfDomain
  4393. + RouteTag,
  4394. + rip2IfConfAuthType
  4395. + INTEGER,
  4396. + rip2IfConfAuthKey
  4397. + OCTET STRING (SIZE(0..16)),
  4398. + rip2IfConfSend
  4399. + INTEGER,
  4400. + rip2IfConfReceive
  4401. + INTEGER,
  4402. + rip2IfConfDefaultMetric
  4403. + INTEGER,
  4404. + rip2IfConfStatus
  4405. + RowStatus,
  4406. + rip2IfConfSrcAddress
  4407. + IpAddress
  4408. + }
  4409. +
  4410. + rip2IfConfAddress OBJECT-TYPE
  4411. + SYNTAX IpAddress
  4412. + MAX-ACCESS read-only
  4413. + STATUS current
  4414. + DESCRIPTION
  4415. + "The IP Address of this system on the indicated
  4416. + subnet. For unnumbered interfaces, the value 0.0.0.N,
  4417. + where the least significant 24 bits (N) is the ifIndex
  4418. + for the IP Interface in network byte order."
  4419. + ::= { rip2IfConfEntry 1 }
  4420. +
  4421. + rip2IfConfDomain OBJECT-TYPE
  4422. + SYNTAX RouteTag
  4423. + MAX-ACCESS read-create
  4424. + STATUS obsolete
  4425. + DESCRIPTION
  4426. + "Value inserted into the Routing Domain field
  4427. + of all RIP packets sent on this interface."
  4428. + DEFVAL { '0000'h }
  4429. + ::= { rip2IfConfEntry 2 }
  4430. +
  4431. + rip2IfConfAuthType OBJECT-TYPE
  4432. + SYNTAX INTEGER {
  4433. + noAuthentication (1),
  4434. + simplePassword (2),
  4435. + md5 (3)
  4436. + }
  4437. + MAX-ACCESS read-create
  4438. + STATUS current
  4439. + DESCRIPTION
  4440. + "The type of Authentication used on this
  4441. + interface."
  4442. + DEFVAL { noAuthentication }
  4443. + ::= { rip2IfConfEntry 3 }
  4444. +
  4445. + rip2IfConfAuthKey OBJECT-TYPE
  4446. + SYNTAX OCTET STRING (SIZE(0..16))
  4447. + MAX-ACCESS read-create
  4448. + STATUS current
  4449. + DESCRIPTION
  4450. + "The value to be used as the Authentication Key
  4451. + whenever the corresponding instance of
  4452. + rip2IfConfAuthType has a value other than
  4453. + noAuthentication. A modification of the corresponding
  4454. + instance of rip2IfConfAuthType does not modify
  4455. + the rip2IfConfAuthKey value. If a string shorter
  4456. + than 16 octets is supplied, it will be left-
  4457. + justified and padded to 16 octets, on the right,
  4458. + with nulls (0x00).
  4459. +
  4460. + Reading this object always results in an OCTET
  4461. + STRING of length zero; authentication may not
  4462. + be bypassed by reading the MIB object."
  4463. + DEFVAL { ''h }
  4464. + ::= { rip2IfConfEntry 4 }
  4465. +
  4466. + rip2IfConfSend OBJECT-TYPE
  4467. + SYNTAX INTEGER {
  4468. + doNotSend (1),
  4469. + ripVersion1 (2),
  4470. + rip1Compatible (3),
  4471. + ripVersion2 (4),
  4472. + ripV1Demand (5),
  4473. + ripV2Demand (6)
  4474. + }
  4475. + MAX-ACCESS read-create
  4476. + STATUS current
  4477. + DESCRIPTION
  4478. + "What the router sends on this interface.
  4479. + ripVersion1 implies sending RIP updates compliant
  4480. + with RFC 1058. rip1Compatible implies
  4481. + broadcasting RIP-2 updates using RFC 1058 route
  4482. + subsumption rules. ripVersion2 implies
  4483. + multicasting RIP-2 updates. ripV1Demand indicates
  4484. + the use of Demand RIP on a WAN interface under RIP
  4485. + Version 1 rules. ripV2Demand indicates the use of
  4486. + Demand RIP on a WAN interface under Version 2 rules."
  4487. + DEFVAL { rip1Compatible }
  4488. + ::= { rip2IfConfEntry 5 }
  4489. +
  4490. + rip2IfConfReceive OBJECT-TYPE
  4491. + SYNTAX INTEGER {
  4492. + rip1 (1),
  4493. + rip2 (2),
  4494. + rip1OrRip2 (3),
  4495. + doNotRecieve (4)
  4496. + }
  4497. + MAX-ACCESS read-create
  4498. + STATUS current
  4499. + DESCRIPTION
  4500. + "This indicates which version of RIP updates
  4501. + are to be accepted. Note that rip2 and
  4502. + rip1OrRip2 implies reception of multicast
  4503. + packets."
  4504. + DEFVAL { rip1OrRip2 }
  4505. + ::= { rip2IfConfEntry 6 }
  4506. +
  4507. + rip2IfConfDefaultMetric OBJECT-TYPE
  4508. + SYNTAX INTEGER ( 0..15 )
  4509. + MAX-ACCESS read-create
  4510. + STATUS current
  4511. + DESCRIPTION
  4512. + "This variable indicates the metric that is to
  4513. + be used for the default route entry in RIP updates
  4514. + originated on this interface. A value of zero
  4515. + indicates that no default route should be
  4516. + originated; in this case, a default route via
  4517. + another router may be propagated."
  4518. + ::= { rip2IfConfEntry 7 }
  4519. +
  4520. + rip2IfConfStatus OBJECT-TYPE
  4521. + SYNTAX RowStatus
  4522. + MAX-ACCESS read-create
  4523. + STATUS current
  4524. + DESCRIPTION
  4525. + "Writing invalid has the effect of deleting
  4526. + this interface."
  4527. + ::= { rip2IfConfEntry 8 }
  4528. +
  4529. + rip2IfConfSrcAddress OBJECT-TYPE
  4530. + SYNTAX IpAddress
  4531. + MAX-ACCESS read-create
  4532. + STATUS current
  4533. + DESCRIPTION
  4534. + "The IP Address this system will use as a source
  4535. + address on this interface. If it is a numbered
  4536. + interface, this MUST be the same value as
  4537. + rip2IfConfAddress. On unnumbered interfaces,
  4538. + it must be the value of rip2IfConfAddress for
  4539. + some interface on the system."
  4540. + ::= { rip2IfConfEntry 9 }
  4541. +
  4542. +--4.3 Peer Table
  4543. +
  4544. +-- Peer Table
  4545. +
  4546. +-- The RIP Peer Group
  4547. +-- Implementation of this Group is Optional
  4548. +
  4549. +-- This group provides information about active peer
  4550. +-- relationships intended to assist in debugging. An
  4551. +-- active peer is a router from which a valid RIP
  4552. +-- updated has been heard in the last 180 seconds.
  4553. +
  4554. + rip2PeerTable OBJECT-TYPE
  4555. + SYNTAX SEQUENCE OF Rip2PeerEntry
  4556. + MAX-ACCESS not-accessible
  4557. + STATUS current
  4558. + DESCRIPTION
  4559. + "A list of RIP Peers."
  4560. + ::= { rip2 4 }
  4561. +
  4562. + rip2PeerEntry OBJECT-TYPE
  4563. + SYNTAX Rip2PeerEntry
  4564. + MAX-ACCESS not-accessible
  4565. + STATUS current
  4566. + DESCRIPTION
  4567. + "Information regarding a single routing peer."
  4568. + INDEX { rip2PeerAddress, rip2PeerDomain }
  4569. + ::= { rip2PeerTable 1 }
  4570. +
  4571. + Rip2PeerEntry ::=
  4572. + SEQUENCE {
  4573. + rip2PeerAddress
  4574. + IpAddress,
  4575. + rip2PeerDomain
  4576. + RouteTag,
  4577. + rip2PeerLastUpdate
  4578. + TimeTicks,
  4579. + rip2PeerVersion
  4580. + INTEGER,
  4581. + rip2PeerRcvBadPackets
  4582. + Counter32,
  4583. + rip2PeerRcvBadRoutes
  4584. + Counter32
  4585. + }
  4586. +
  4587. + rip2PeerAddress OBJECT-TYPE
  4588. + SYNTAX IpAddress
  4589. + MAX-ACCESS read-only
  4590. + STATUS current
  4591. + DESCRIPTION
  4592. + "The IP Address that the peer is using as its source
  4593. + address. Note that on an unnumbered link, this may
  4594. + not be a member of any subnet on the system."
  4595. + ::= { rip2PeerEntry 1 }
  4596. +
  4597. + rip2PeerDomain OBJECT-TYPE
  4598. + SYNTAX RouteTag
  4599. + MAX-ACCESS read-only
  4600. + STATUS current
  4601. + DESCRIPTION
  4602. + "The value in the Routing Domain field in RIP
  4603. + packets received from the peer. As domain suuport
  4604. + is deprecated, this must be zero."
  4605. + ::= { rip2PeerEntry 2 }
  4606. +
  4607. + rip2PeerLastUpdate OBJECT-TYPE
  4608. + SYNTAX TimeTicks
  4609. + MAX-ACCESS read-only
  4610. + STATUS current
  4611. + DESCRIPTION
  4612. + "The value of sysUpTime when the most recent
  4613. + RIP update was received from this system."
  4614. + ::= { rip2PeerEntry 3 }
  4615. +
  4616. + rip2PeerVersion OBJECT-TYPE
  4617. + SYNTAX INTEGER ( 0..255 )
  4618. + MAX-ACCESS read-only
  4619. + STATUS current
  4620. + DESCRIPTION
  4621. + "The RIP version number in the header of the
  4622. + last RIP packet received."
  4623. + ::= { rip2PeerEntry 4 }
  4624. +
  4625. + rip2PeerRcvBadPackets OBJECT-TYPE
  4626. + SYNTAX Counter32
  4627. + MAX-ACCESS read-only
  4628. + STATUS current
  4629. + DESCRIPTION
  4630. + "The number of RIP response packets from this
  4631. + peer discarded as invalid."
  4632. + ::= { rip2PeerEntry 5 }
  4633. +
  4634. +
  4635. + rip2PeerRcvBadRoutes OBJECT-TYPE
  4636. + SYNTAX Counter32
  4637. + MAX-ACCESS read-only
  4638. + STATUS current
  4639. + DESCRIPTION
  4640. + "The number of routes from this peer that were
  4641. + ignored because the entry format was invalid."
  4642. + ::= { rip2PeerEntry 6 }
  4643. +
  4644. +-- conformance information
  4645. +
  4646. +rip2Conformance OBJECT IDENTIFIER ::= { rip2 5 }
  4647. +
  4648. +rip2Groups OBJECT IDENTIFIER ::= { rip2Conformance 1 }
  4649. +rip2Compliances OBJECT IDENTIFIER ::= { rip2Conformance 2 }
  4650. +
  4651. +-- compliance statements
  4652. +rip2Compliance MODULE-COMPLIANCE
  4653. + STATUS current
  4654. + DESCRIPTION
  4655. + "The compliance statement "
  4656. + MODULE -- this module
  4657. + MANDATORY-GROUPS {
  4658. + rip2GlobalGroup,
  4659. + rip2IfStatGroup,
  4660. + rip2IfConfGroup,
  4661. + rip2PeerGroup
  4662. + }
  4663. + GROUP rip2GlobalGroup
  4664. + DESCRIPTION
  4665. + "This group defines global controls for RIP-II systems."
  4666. + GROUP rip2IfStatGroup
  4667. + DESCRIPTION
  4668. + "This group defines interface statistics for RIP-II systems."
  4669. + GROUP rip2IfConfGroup
  4670. + DESCRIPTION
  4671. + "This group defines interface configuration for RIP-II systems."
  4672. + GROUP rip2PeerGroup
  4673. + DESCRIPTION
  4674. + "This group defines peer information for RIP-II systems."
  4675. + ::= { rip2Compliances 1 }
  4676. +
  4677. +-- units of conformance
  4678. +
  4679. +rip2GlobalGroup OBJECT-GROUP
  4680. + OBJECTS {
  4681. + rip2GlobalRouteChanges,
  4682. + rip2GlobalQueries
  4683. + }
  4684. + STATUS current
  4685. + DESCRIPTION
  4686. + "This group defines global controls for RIP-II systems."
  4687. + ::= { rip2Groups 1 }
  4688. +rip2IfStatGroup OBJECT-GROUP
  4689. + OBJECTS {
  4690. + rip2IfStatAddress,
  4691. + rip2IfStatRcvBadPackets,
  4692. + rip2IfStatRcvBadRoutes,
  4693. + rip2IfStatSentUpdates,
  4694. + rip2IfStatStatus
  4695. + }
  4696. + STATUS current
  4697. + DESCRIPTION
  4698. + "This group defines interface statistics for RIP-II systems."
  4699. + ::= { rip2Groups 2 }
  4700. +rip2IfConfGroup OBJECT-GROUP
  4701. + OBJECTS {
  4702. + rip2IfConfAddress,
  4703. + rip2IfConfAuthType,
  4704. + rip2IfConfAuthKey,
  4705. + rip2IfConfSend,
  4706. + rip2IfConfReceive,
  4707. + rip2IfConfDefaultMetric,
  4708. + rip2IfConfStatus,
  4709. + rip2IfConfSrcAddress
  4710. + }
  4711. + STATUS current
  4712. + DESCRIPTION
  4713. + "This group defines interface configuration for RIP-II systems."
  4714. + ::= { rip2Groups 3 }
  4715. +rip2PeerGroup OBJECT-GROUP
  4716. + OBJECTS {
  4717. + rip2PeerAddress,
  4718. + rip2PeerDomain,
  4719. + rip2PeerLastUpdate,
  4720. + rip2PeerVersion,
  4721. + rip2PeerRcvBadPackets,
  4722. + rip2PeerRcvBadRoutes
  4723. + }
  4724. + STATUS current
  4725. + DESCRIPTION
  4726. + "This group defines peer information for RIP-II systems."
  4727. + ::= { rip2Groups 4 }
  4728. +END
  4729. --- /dev/null
  4730. +++ b/mibs/SOURCE-ROUTING-MIB.txt
  4731. @@ -0,0 +1,452 @@
  4732. +SOURCE-ROUTING-MIB DEFINITIONS ::= BEGIN
  4733. +
  4734. +IMPORTS
  4735. + Counter, Gauge
  4736. + FROM RFC1155-SMI
  4737. + dot1dBridge, dot1dSr
  4738. + FROM BRIDGE-MIB
  4739. + OBJECT-TYPE
  4740. + FROM RFC-1212;
  4741. +
  4742. +-- groups in the SR MIB
  4743. +
  4744. +-- dot1dSr is imported from the Bridge MIB
  4745. +
  4746. +dot1dPortPair OBJECT IDENTIFIER ::= { dot1dBridge 10 }
  4747. +
  4748. +-- the dot1dSr group
  4749. +
  4750. +-- this group is implemented by those bridges that
  4751. +-- support the source route bridging mode, including Source
  4752. +-- Routing and SRT bridges.
  4753. +
  4754. +dot1dSrPortTable OBJECT-TYPE
  4755. + SYNTAX SEQUENCE OF Dot1dSrPortEntry
  4756. + ACCESS not-accessible
  4757. + STATUS mandatory
  4758. + DESCRIPTION
  4759. + "A table that contains information about every
  4760. + port that is associated with this source route
  4761. + bridge."
  4762. + ::= { dot1dSr 1 }
  4763. +
  4764. +dot1dSrPortEntry OBJECT-TYPE
  4765. + SYNTAX Dot1dSrPortEntry
  4766. + ACCESS not-accessible
  4767. + STATUS mandatory
  4768. + DESCRIPTION
  4769. + "A list of information for each port of a source
  4770. + route bridge."
  4771. + INDEX { dot1dSrPort }
  4772. +
  4773. + ::= { dot1dSrPortTable 1 }
  4774. +
  4775. +Dot1dSrPortEntry ::=
  4776. + SEQUENCE {
  4777. + dot1dSrPort
  4778. + INTEGER,
  4779. + dot1dSrPortHopCount
  4780. + INTEGER,
  4781. + dot1dSrPortLocalSegment
  4782. + INTEGER,
  4783. + dot1dSrPortBridgeNum
  4784. + INTEGER,
  4785. + dot1dSrPortTargetSegment
  4786. + INTEGER,
  4787. + dot1dSrPortLargestFrame
  4788. + INTEGER,
  4789. + dot1dSrPortSTESpanMode
  4790. + INTEGER,
  4791. + dot1dSrPortSpecInFrames
  4792. + Counter,
  4793. + dot1dSrPortSpecOutFrames
  4794. + Counter,
  4795. + dot1dSrPortApeInFrames
  4796. + Counter,
  4797. + dot1dSrPortApeOutFrames
  4798. + Counter,
  4799. + dot1dSrPortSteInFrames
  4800. + Counter,
  4801. + dot1dSrPortSteOutFrames
  4802. + Counter,
  4803. + dot1dSrPortSegmentMismatchDiscards
  4804. + Counter,
  4805. + dot1dSrPortDuplicateSegmentDiscards
  4806. + Counter,
  4807. + dot1dSrPortHopCountExceededDiscards
  4808. + Counter,
  4809. + dot1dSrPortDupLanIdOrTreeErrors
  4810. + Counter,
  4811. + dot1dSrPortLanIdMismatches
  4812. + Counter
  4813. + }
  4814. +
  4815. +dot1dSrPort OBJECT-TYPE
  4816. + SYNTAX INTEGER (1..65535)
  4817. + ACCESS read-only
  4818. + STATUS mandatory
  4819. + DESCRIPTION
  4820. + "The port number of the port for which this entry
  4821. +
  4822. + contains Source Route management information."
  4823. + ::= { dot1dSrPortEntry 1 }
  4824. +
  4825. +dot1dSrPortHopCount OBJECT-TYPE
  4826. + SYNTAX INTEGER
  4827. + ACCESS read-write
  4828. + STATUS mandatory
  4829. + DESCRIPTION
  4830. + "The maximum number of routing descriptors allowed
  4831. + in an All Paths or Spanning Tree Explorer frames."
  4832. + ::= { dot1dSrPortEntry 2 }
  4833. +
  4834. +dot1dSrPortLocalSegment OBJECT-TYPE
  4835. + SYNTAX INTEGER
  4836. + ACCESS read-write
  4837. + STATUS mandatory
  4838. + DESCRIPTION
  4839. + "The segment number that uniquely identifies the
  4840. + segment to which this port is connected. Current
  4841. + source routing protocols limit this value to the
  4842. + range: 0 through 4095. (The value 0 is used by
  4843. + some management applications for special test
  4844. + cases.) A value of 65535 signifies that no segment
  4845. + number is assigned to this port."
  4846. + ::= { dot1dSrPortEntry 3 }
  4847. +
  4848. +dot1dSrPortBridgeNum OBJECT-TYPE
  4849. + SYNTAX INTEGER
  4850. + ACCESS read-write
  4851. + STATUS mandatory
  4852. + DESCRIPTION
  4853. + "A bridge number uniquely identifies a bridge when
  4854. + more than one bridge is used to span the same two
  4855. + segments. Current source routing protocols limit
  4856. + this value to the range: 0 through 15. A value of
  4857. + 65535 signifies that no bridge number is assigned
  4858. + to this bridge."
  4859. + ::= { dot1dSrPortEntry 4 }
  4860. +
  4861. +dot1dSrPortTargetSegment OBJECT-TYPE
  4862. + SYNTAX INTEGER
  4863. + ACCESS read-write
  4864. + STATUS mandatory
  4865. + DESCRIPTION
  4866. + "The segment number that corresponds to the target
  4867. + segment this port is considered to be connected to
  4868. + by the bridge. Current source routing protocols
  4869. + limit this value to the range: 0 through 4095.
  4870. +
  4871. + (The value 0 is used by some management
  4872. + applications for special test cases.) A value of
  4873. + 65535 signifies that no target segment is assigned
  4874. + to this port."
  4875. + ::= { dot1dSrPortEntry 5 }
  4876. +
  4877. +-- It would be nice if we could use ifMtu as the size of the
  4878. +-- largest frame, but we can't because ifMtu is defined to be
  4879. +-- the size that the (inter-)network layer can use which can
  4880. +-- differ from the MAC layer (especially if several layers of
  4881. +-- encapsulation are used).
  4882. +
  4883. +dot1dSrPortLargestFrame OBJECT-TYPE
  4884. + SYNTAX INTEGER
  4885. + ACCESS read-write
  4886. + STATUS mandatory
  4887. + DESCRIPTION
  4888. + "The maximum size of the INFO field (LLC and
  4889. + above) that this port can send/receive. It does
  4890. + not include any MAC level (framing) octets. The
  4891. + value of this object is used by this bridge to
  4892. + determine whether a modification of the
  4893. + LargestFrame (LF, see [14]) field of the Routing
  4894. + Control field of the Routing Information Field is
  4895. + necessary.
  4896. +
  4897. + 64 valid values are defined by the IEEE 802.5M SRT
  4898. + Addendum: 516, 635, 754, 873, 993, 1112, 1231,
  4899. + 1350, 1470, 1542, 1615, 1688, 1761, 1833, 1906,
  4900. + 1979, 2052, 2345, 2638, 2932, 3225, 3518, 3812,
  4901. + 4105, 4399, 4865, 5331, 5798, 6264, 6730, 7197,
  4902. + 7663, 8130, 8539, 8949, 9358, 9768, 10178, 10587,
  4903. + 10997, 11407, 12199, 12992, 13785, 14578, 15370,
  4904. + 16163, 16956, 17749, 20730, 23711, 26693, 29674,
  4905. + 32655, 35637, 38618, 41600, 44591, 47583, 50575,
  4906. + 53567, 56559, 59551, and 65535.
  4907. +
  4908. + An illegal value will not be accepted by the
  4909. + bridge."
  4910. + ::= { dot1dSrPortEntry 6 }
  4911. +
  4912. +dot1dSrPortSTESpanMode OBJECT-TYPE
  4913. + SYNTAX INTEGER {
  4914. + auto-span(1),
  4915. + disabled(2),
  4916. + forced(3)
  4917. + }
  4918. + ACCESS read-write
  4919. + STATUS mandatory
  4920. + DESCRIPTION
  4921. + "Determines how this port behaves when presented
  4922. + with a Spanning Tree Explorer frame. The value
  4923. + 'disabled(2)' indicates that the port will not
  4924. + accept or send Spanning Tree Explorer packets; any
  4925. + STE packets received will be silently discarded.
  4926. + The value 'forced(3)' indicates the port will
  4927. + always accept and propagate Spanning Tree Explorer
  4928. + frames. This allows a manually configured
  4929. + Spanning Tree for this class of packet to be
  4930. + configured. Note that unlike transparent
  4931. + bridging, this is not catastrophic to the network
  4932. + if there are loops. The value 'auto-span(1)' can
  4933. + only be returned by a bridge that both implements
  4934. + the Spanning Tree Protocol and has use of the
  4935. + protocol enabled on this port. The behavior of the
  4936. + port for Spanning Tree Explorer frames is
  4937. + determined by the state of dot1dStpPortState. If
  4938. + the port is in the 'forwarding' state, the frame
  4939. + will be accepted or propagated. Otherwise, it
  4940. + will be silently discarded."
  4941. + ::= { dot1dSrPortEntry 7 }
  4942. +
  4943. +dot1dSrPortSpecInFrames OBJECT-TYPE
  4944. + SYNTAX Counter
  4945. + ACCESS read-only
  4946. + STATUS mandatory
  4947. + DESCRIPTION
  4948. + "The number of Specifically Routed frames, also
  4949. + referred to as Source Routed Frames, that have
  4950. + been received from this port's segment."
  4951. + ::= { dot1dSrPortEntry 8 }
  4952. +
  4953. +dot1dSrPortSpecOutFrames OBJECT-TYPE
  4954. + SYNTAX Counter
  4955. + ACCESS read-only
  4956. + STATUS mandatory
  4957. + DESCRIPTION
  4958. + "The number of Specifically Routed frames, also
  4959. + referred to as Source Routed Frames, that this
  4960. + port has transmitted on its segment."
  4961. + ::= { dot1dSrPortEntry 9 }
  4962. +
  4963. +dot1dSrPortApeInFrames OBJECT-TYPE
  4964. + SYNTAX Counter
  4965. + ACCESS read-only
  4966. + STATUS mandatory
  4967. + DESCRIPTION
  4968. + "The number of All Paths Explorer frames, also
  4969. + referred to as All Routes Explorer frames, that
  4970. + have been received by this port from its segment."
  4971. + ::= { dot1dSrPortEntry 10 }
  4972. +
  4973. +dot1dSrPortApeOutFrames OBJECT-TYPE
  4974. + SYNTAX Counter
  4975. + ACCESS read-only
  4976. + STATUS mandatory
  4977. + DESCRIPTION
  4978. + "The number of all Paths Explorer Frames, also
  4979. + referred to as All Routes Explorer frames, that
  4980. + have been transmitted by this port on its
  4981. + segment."
  4982. + ::= { dot1dSrPortEntry 11 }
  4983. +
  4984. +dot1dSrPortSteInFrames OBJECT-TYPE
  4985. + SYNTAX Counter
  4986. + ACCESS read-only
  4987. + STATUS mandatory
  4988. + DESCRIPTION
  4989. + "The number of spanning tree explorer frames that
  4990. + have been received by this port from its segment."
  4991. + ::= { dot1dSrPortEntry 12 }
  4992. +
  4993. +dot1dSrPortSteOutFrames OBJECT-TYPE
  4994. + SYNTAX Counter
  4995. + ACCESS read-only
  4996. + STATUS mandatory
  4997. + DESCRIPTION
  4998. + "The number of spanning tree explorer frames that
  4999. + have been transmitted by this port on its
  5000. + segment."
  5001. + ::= { dot1dSrPortEntry 13 }
  5002. +
  5003. +dot1dSrPortSegmentMismatchDiscards OBJECT-TYPE
  5004. + SYNTAX Counter
  5005. + ACCESS read-only
  5006. + STATUS mandatory
  5007. + DESCRIPTION
  5008. + "The number of explorer frames that have been
  5009. + discarded by this port because the routing
  5010. + descriptor field contained an invalid adjacent
  5011. + segment value."
  5012. + ::= { dot1dSrPortEntry 14 }
  5013. +
  5014. +dot1dSrPortDuplicateSegmentDiscards OBJECT-TYPE
  5015. + SYNTAX Counter
  5016. + ACCESS read-only
  5017. + STATUS mandatory
  5018. + DESCRIPTION
  5019. + "The number of frames that have been discarded by
  5020. + this port because the routing descriptor field
  5021. + contained a duplicate segment identifier."
  5022. + ::= { dot1dSrPortEntry 15 }
  5023. +
  5024. +dot1dSrPortHopCountExceededDiscards OBJECT-TYPE
  5025. + SYNTAX Counter
  5026. + ACCESS read-only
  5027. + STATUS mandatory
  5028. + DESCRIPTION
  5029. + "The number of explorer frames that have been
  5030. + discarded by this port because the Routing
  5031. + Information Field has exceeded the maximum route
  5032. + descriptor length."
  5033. + ::= { dot1dSrPortEntry 16 }
  5034. +
  5035. +dot1dSrPortDupLanIdOrTreeErrors OBJECT-TYPE
  5036. + SYNTAX Counter
  5037. + ACCESS read-only
  5038. + STATUS mandatory
  5039. + DESCRIPTION
  5040. + "The number of duplicate LAN IDs or Tree errors.
  5041. + This helps in detection of problems in networks
  5042. + containing older IBM Source Routing Bridges."
  5043. + ::= { dot1dSrPortEntry 17 }
  5044. +
  5045. +dot1dSrPortLanIdMismatches OBJECT-TYPE
  5046. + SYNTAX Counter
  5047. + ACCESS read-only
  5048. + STATUS mandatory
  5049. + DESCRIPTION
  5050. + "The number of ARE and STE frames that were
  5051. + discarded because the last LAN ID in the routing
  5052. + information field did not equal the LAN-in ID.
  5053. + This error can occur in implementations which do
  5054. + only a LAN-in ID and Bridge Number check instead
  5055. + of a LAN-in ID, Bridge Number, and LAN-out ID
  5056. + check before they forward broadcast frames."
  5057. + ::= { dot1dSrPortEntry 18 }
  5058. +
  5059. +-- scalar object in dot1dSr
  5060. +
  5061. +dot1dSrBridgeLfMode OBJECT-TYPE
  5062. + SYNTAX INTEGER {
  5063. + mode3(1),
  5064. + mode6(2)
  5065. + }
  5066. + ACCESS read-write
  5067. + STATUS mandatory
  5068. + DESCRIPTION
  5069. + "Indicates whether the bridge operates using older
  5070. + 3 bit length negotiation fields or the newer 6 bit
  5071. + length field in its RIF."
  5072. + ::= { dot1dSr 2 }
  5073. +
  5074. +-- The Port-Pair Database
  5075. +
  5076. +-- Implementation of this group is optional.
  5077. +
  5078. +-- This group is implemented by those bridges that support
  5079. +-- the direct multiport model of the source route bridging
  5080. +-- mode as defined in the IEEE 802.5 SRT Addendum to
  5081. +-- 802.1d.
  5082. +
  5083. +-- Bridges implementing this group may report 65535 for
  5084. +-- dot1dSrPortBridgeNumber and dot1dSrPortTargetSegment,
  5085. +-- indicating that those objects are not applicable.
  5086. +
  5087. +dot1dPortPairTableSize OBJECT-TYPE
  5088. + SYNTAX Gauge
  5089. + ACCESS read-only
  5090. + STATUS mandatory
  5091. + DESCRIPTION
  5092. + "The total number of entries in the Bridge Port
  5093. + Pair Database."
  5094. + ::= { dot1dPortPair 1 }
  5095. +
  5096. +-- the Bridge Port-Pair table
  5097. +
  5098. +-- this table represents port pairs within a bridge forming
  5099. +-- a unique bridge path, as defined in the IEEE 802.5M SRT
  5100. +-- Addendum.
  5101. +
  5102. +dot1dPortPairTable OBJECT-TYPE
  5103. + SYNTAX SEQUENCE OF Dot1dPortPairEntry
  5104. + ACCESS not-accessible
  5105. + STATUS mandatory
  5106. + DESCRIPTION
  5107. + "A table that contains information about every
  5108. +
  5109. + port pair database entity associated with this
  5110. + source routing bridge."
  5111. + ::= { dot1dPortPair 2 }
  5112. +
  5113. +dot1dPortPairEntry OBJECT-TYPE
  5114. + SYNTAX Dot1dPortPairEntry
  5115. + ACCESS not-accessible
  5116. + STATUS mandatory
  5117. + DESCRIPTION
  5118. + "A list of information for each port pair entity
  5119. + of a bridge."
  5120. + INDEX { dot1dPortPairLowPort, dot1dPortPairHighPort }
  5121. + ::= { dot1dPortPairTable 1 }
  5122. +
  5123. +Dot1dPortPairEntry ::=
  5124. + SEQUENCE {
  5125. + dot1dPortPairLowPort
  5126. + INTEGER,
  5127. + dot1dPortPairHighPort
  5128. + INTEGER,
  5129. + dot1dPortPairBridgeNum
  5130. + INTEGER,
  5131. + dot1dPortPairBridgeState
  5132. + INTEGER
  5133. + }
  5134. +
  5135. +dot1dPortPairLowPort OBJECT-TYPE
  5136. + SYNTAX INTEGER (1..65535)
  5137. + ACCESS read-write
  5138. + STATUS mandatory
  5139. + DESCRIPTION
  5140. + "The port number of the lower numbered port for
  5141. + which this entry contains port pair database
  5142. + information."
  5143. + ::= { dot1dPortPairEntry 1 }
  5144. +
  5145. +dot1dPortPairHighPort OBJECT-TYPE
  5146. + SYNTAX INTEGER (1..65535)
  5147. + ACCESS read-write
  5148. + STATUS mandatory
  5149. + DESCRIPTION
  5150. + "The port number of the higher numbered port for
  5151. + which this entry contains port pair database
  5152. + information."
  5153. + ::= { dot1dPortPairEntry 2 }
  5154. +
  5155. +dot1dPortPairBridgeNum OBJECT-TYPE
  5156. + SYNTAX INTEGER
  5157. +
  5158. + ACCESS read-write
  5159. + STATUS mandatory
  5160. + DESCRIPTION
  5161. + "A bridge number that uniquely identifies the path
  5162. + provided by this source routing bridge between the
  5163. + segments connected to dot1dPortPairLowPort and
  5164. + dot1dPortPairHighPort. The purpose of bridge
  5165. + number is to disambiguate between multiple paths
  5166. + connecting the same two LANs."
  5167. + ::= { dot1dPortPairEntry 3 }
  5168. +
  5169. +dot1dPortPairBridgeState OBJECT-TYPE
  5170. + SYNTAX INTEGER {
  5171. + enabled(1),
  5172. + disabled(2),
  5173. + invalid(3)
  5174. + }
  5175. + ACCESS read-write
  5176. + STATUS mandatory
  5177. + DESCRIPTION
  5178. + "The state of dot1dPortPairBridgeNum. Writing
  5179. + 'invalid(3)' to this object removes the
  5180. + corresponding entry."
  5181. + ::= { dot1dPortPairEntry 4 }
  5182. +
  5183. +END