PTOPO-MIB 30 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839
  1. PTOPO-MIB DEFINITIONS ::= BEGIN
  2. IMPORTS
  3. MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
  4. Integer32, Counter32, mib-2
  5. FROM SNMPv2-SMI
  6. TEXTUAL-CONVENTION, AutonomousType, RowStatus, TimeStamp, TruthValue
  7. FROM SNMPv2-TC
  8. MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
  9. FROM SNMPv2-CONF
  10. TimeFilter
  11. FROM RMON2-MIB
  12. PhysicalIndex
  13. FROM ENTITY-MIB
  14. AddressFamilyNumbers
  15. FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB;
  16. ptopoMIB MODULE-IDENTITY
  17. LAST-UPDATED "200009210000Z"
  18. ORGANIZATION "IETF; PTOPOMIB Working Group"
  19. CONTACT-INFO
  20. "PTOPOMIB WG Discussion:
  21. ptopo@3com.com
  22. Subscription:
  23. majordomo@3com.com
  24. msg body: [un]subscribe ptopomib
  25. Andy Bierman
  26. Cisco Systems Inc.
  27. 170 West Tasman Drive
  28. San Jose, CA 95134
  29. 408-527-3711
  30. abierman@cisco.com
  31. Kendall S. Jones
  32. Nortel Networks
  33. 4401 Great America Parkway
  34. Santa Clara, CA 95054
  35. 408-495-7356
  36. kejones@nortelnetworks.com"
  37. DESCRIPTION
  38. "The MIB module for physical topology information."
  39. REVISION "200009210000Z"
  40. DESCRIPTION
  41. "Initial Version of the Physical Topology MIB. This version
  42. published as RFC 2922."
  43. ::= { mib-2 79 }
  44. ptopoMIBObjects OBJECT IDENTIFIER ::= { ptopoMIB 1 }
  45. -- MIB groups
  46. ptopoData OBJECT IDENTIFIER ::= { ptopoMIBObjects 1 }
  47. ptopoGeneral OBJECT IDENTIFIER ::= { ptopoMIBObjects 2 }
  48. ptopoConfig OBJECT IDENTIFIER ::= { ptopoMIBObjects 3 }
  49. -- textual conventions
  50. PtopoGenAddr ::= TEXTUAL-CONVENTION
  51. STATUS current
  52. DESCRIPTION
  53. "The value of an address."
  54. SYNTAX OCTET STRING (SIZE (0..20))
  55. PtopoChassisIdType ::= TEXTUAL-CONVENTION
  56. STATUS current
  57. DESCRIPTION
  58. "This TC describes the source of a chassis identifier.
  59. The enumeration 'chasIdEntPhysicalAlias(1)' represents a
  60. chassis identifier based on the value of entPhysicalAlias
  61. for a chassis component (i.e., an entPhysicalClass value of
  62. 'chassis(3)').
  63. The enumeration 'chasIdIfAlias(2)' represents a chassis
  64. identifier based on the value of ifAlias for an interface
  65. on the containing chassis.
  66. The enumeration 'chasIdPortEntPhysicalAlias(3)' represents
  67. a chassis identifier based on the value of entPhysicalAlias
  68. for a port or backplane component (i.e., entPhysicalClass
  69. value of 'port(10)' or 'backplane(4)'), within the
  70. containing chassis.
  71. The enumeration 'chasIdMacAddress(4)' represents a chassis
  72. identifier based on the value of a unicast source MAC
  73. address (encoded in network byte order and IEEE 802.3
  74. canonical bit order), of a port on the containing chassis.
  75. The enumeration 'chasIdPtopoGenAddr(5)' represents a
  76. chassis identifier based on a network address, associated
  77. with a particular chassis. The encoded address is actually
  78. composed of two fields. The first field is a single octet,
  79. representing the IANA AddressFamilyNumbers value for the
  80. specific address type, and the second field is the
  81. PtopoGenAddr address value."
  82. SYNTAX INTEGER {
  83. chasIdEntPhysicalAlias(1),
  84. chasIdIfAlias(2),
  85. chasIdPortEntPhysicalAlias(3),
  86. chasIdMacAddress(4),
  87. chasIdPtopoGenAddr(5)
  88. }
  89. PtopoChassisId ::= TEXTUAL-CONVENTION
  90. STATUS current
  91. DESCRIPTION
  92. "This TC describes the format of a chassis identifier
  93. string. Objects of this type are always used with an
  94. associated PtopoChassisIdType object, which identifies the
  95. format of the particular PtopoChassisId object instance.
  96. If the associated PtopoChassisIdType object has a value of
  97. 'chasIdEntPhysicalAlias(1)', then the octet string
  98. identifies a particular instance of the entPhysicalAlias
  99. object for a chassis component (i.e., an entPhysicalClass
  100. value of 'chassis(3)').
  101. If the associated PtopoChassisIdType object has a value of
  102. 'chasIdIfAlias(2)', then the octet string identifies a
  103. particular instance of the ifAlias object for an interface
  104. on the containing chassis.
  105. If the associated PtopoChassisIdType object has a value of
  106. 'chasIdPortEntPhysicalAlias(3)', then the octet string
  107. identifies a particular instance of the entPhysicalAlias
  108. object for a port or backplane component within the
  109. containing chassis.
  110. If the associated PtopoChassisIdType object has a value of
  111. 'chasIdMacAddress(4)', then this string identifies a
  112. particular unicast source MAC address (encoded in network
  113. byte order and IEEE 802.3 canonical bit order), of a port on
  114. the containing chassis.
  115. If the associated PtopoChassisIdType object has a value of
  116. 'chasIdPtopoGenAddr(5)', then this string identifies a
  117. particular network address, encoded in network byte order,
  118. associated with one or more ports on the containing chassis.
  119. The first octet contains the IANA Address Family Numbers
  120. enumeration value for the specific address type, and octets
  121. 2 through N contain the PtopoGenAddr address value in
  122. network byte order."
  123. SYNTAX OCTET STRING (SIZE (1..32))
  124. PtopoPortIdType ::= TEXTUAL-CONVENTION
  125. STATUS current
  126. DESCRIPTION
  127. "This TC describes the source of a particular type of port
  128. identifier used in the PTOPO MIB.
  129. The enumeration 'portIdIfAlias(1)' represents a port
  130. identifier based on the ifAlias MIB object.
  131. The enumeration 'portIdPortEntPhysicalAlias(2)' represents a
  132. port identifier based on the value of entPhysicalAlias for a
  133. port or backplane component (i.e., entPhysicalClass value of
  134. 'port(10)' or 'backplane(4)'), within the containing
  135. chassis.
  136. The enumeration 'portIdMacAddr(3)' represents a port
  137. identifier based on a unicast source MAC address, which has
  138. been detected by the agent and associated with a particular
  139. port.
  140. The enumeration 'portIdPtopoGenAddr(4)' represents a port
  141. identifier based on a network address, detected by the agent
  142. and associated with a particular port."
  143. SYNTAX INTEGER {
  144. portIdIfAlias(1),
  145. portIdEntPhysicalAlias(2),
  146. portIdMacAddr(3),
  147. portIdPtopoGenAddr(4)
  148. }
  149. PtopoPortId ::= TEXTUAL-CONVENTION
  150. STATUS current
  151. DESCRIPTION
  152. "This TC describes the format of a port identifier string.
  153. Objects of this type are always used with an associated
  154. PtopoPortIdType object, which identifies the format of the
  155. particular PtopoPortId object instance.
  156. If the associated PtopoPortIdType object has a value of
  157. 'portIdIfAlias(1)', then the octet string identifies a
  158. particular instance of the ifAlias object.
  159. If the associated PtopoPortIdType object has a value of
  160. 'portIdEntPhysicalAlias(2)', then the octet string
  161. identifies a particular instance of the entPhysicalAlias
  162. object for a port component (i.e., entPhysicalClass value of
  163. 'port(10)').
  164. If the associated PtopoPortIdType object has a value of
  165. 'portIdMacAddr(3)', then this string identifies a particular
  166. unicast source MAC address associated with the port.
  167. If the associated PtopoPortIdType object has a value of
  168. 'portIdPtopoGenAddr(4)', then this string identifies a
  169. network address associated with the port. The first octet
  170. contains the IANA AddressFamilyNumbers enumeration value for
  171. the specific address type, and octets 2 through N contain
  172. the PtopoGenAddr address value in network byte order."
  173. SYNTAX OCTET STRING (SIZE (1..32))
  174. PtopoAddrSeenState ::= TEXTUAL-CONVENTION
  175. STATUS current
  176. DESCRIPTION
  177. "This TC describes the state of address detection for a
  178. particular type of port identifier used in the PTOPO MIB.
  179. The enumeration 'notUsed(1)' represents an entry for which
  180. the particular MIB object is not applicable to the remote
  181. connection endpoint,
  182. The enumeration 'unknown(2)' represents an entry for which
  183. the particular address collection state is not known.
  184. The enumeration 'oneAddr(3)' represents an entry for which
  185. exactly one source address (of the type indicated by the
  186. particular MIB object), has been detected.
  187. The enumeration 'multiAddr(4)' represents an entry for
  188. which more than one source address (of the type indicated by
  189. the particular MIB object), has been detected.
  190. An agent is expected to set the initial state of the
  191. PtopoAddrSeenState to 'notUsed(1)' or 'unknown(2)'.
  192. Note that the PTOPO MIB does not restrict or specify the
  193. means in which the PtopoAddrSeenState is known to an agent.
  194. In particular, an agent may detect this information through
  195. configuration data, or some means other than directly
  196. monitoring all port traffic."
  197. SYNTAX INTEGER {
  198. notUsed(1),
  199. unknown(2),
  200. oneAddr(3),
  201. multiAddr(4)
  202. }
  203. -- ***********************************************************
  204. --
  205. -- P T O P O D A T A G R O U P
  206. --
  207. -- ***********************************************************
  208. -- Connection Table
  209. ptopoConnTable OBJECT-TYPE
  210. SYNTAX SEQUENCE OF PtopoConnEntry
  211. MAX-ACCESS not-accessible
  212. STATUS current
  213. DESCRIPTION
  214. "This table contains one or more rows per physical network
  215. connection known to this agent. The agent may wish to
  216. ensure that only one ptopoConnEntry is present for each
  217. local port, or it may choose to maintain multiple
  218. ptopoConnEntries for the same local port.
  219. Entries based on lower numbered identifier types are
  220. preferred over higher numbered identifier types, i.e., lower
  221. values of the ptopoConnRemoteChassisType and
  222. ptopoConnRemotePortType objects."
  223. ::= { ptopoData 1 }
  224. ptopoConnEntry OBJECT-TYPE
  225. SYNTAX PtopoConnEntry
  226. MAX-ACCESS not-accessible
  227. STATUS current
  228. DESCRIPTION
  229. "Information about a particular physical network connection.
  230. Entries may be created and deleted in this table, either
  231. manually or by the agent, if a physical topology discovery
  232. process is active."
  233. INDEX {
  234. ptopoConnTimeMark,
  235. ptopoConnLocalChassis,
  236. ptopoConnLocalPort,
  237. ptopoConnIndex
  238. }
  239. ::= { ptopoConnTable 1 }
  240. PtopoConnEntry ::= SEQUENCE {
  241. ptopoConnTimeMark TimeFilter,
  242. ptopoConnLocalChassis PhysicalIndex,
  243. ptopoConnLocalPort PhysicalIndex,
  244. ptopoConnIndex Integer32,
  245. ptopoConnRemoteChassisType PtopoChassisIdType,
  246. ptopoConnRemoteChassis PtopoChassisId,
  247. ptopoConnRemotePortType PtopoPortIdType,
  248. ptopoConnRemotePort PtopoPortId,
  249. ptopoConnDiscAlgorithm AutonomousType,
  250. ptopoConnAgentNetAddrType AddressFamilyNumbers,
  251. ptopoConnAgentNetAddr PtopoGenAddr,
  252. ptopoConnMultiMacSASeen PtopoAddrSeenState,
  253. ptopoConnMultiNetSASeen PtopoAddrSeenState,
  254. ptopoConnIsStatic TruthValue,
  255. ptopoConnLastVerifyTime TimeStamp,
  256. ptopoConnRowStatus RowStatus
  257. }
  258. ptopoConnTimeMark OBJECT-TYPE
  259. SYNTAX TimeFilter
  260. MAX-ACCESS not-accessible
  261. STATUS current
  262. DESCRIPTION
  263. "A TimeFilter for this entry. See the TimeFilter textual
  264. convention in RFC 2021 to see how this works."
  265. ::= { ptopoConnEntry 1 }
  266. ptopoConnLocalChassis OBJECT-TYPE
  267. SYNTAX PhysicalIndex
  268. MAX-ACCESS not-accessible
  269. STATUS current
  270. DESCRIPTION
  271. "The entPhysicalIndex value used to identify the chassis
  272. component associated with the local connection endpoint."
  273. ::= { ptopoConnEntry 2 }
  274. ptopoConnLocalPort OBJECT-TYPE
  275. SYNTAX PhysicalIndex
  276. MAX-ACCESS not-accessible
  277. STATUS current
  278. DESCRIPTION
  279. "The entPhysicalIndex value used to identify the port
  280. component associated with the local connection endpoint."
  281. ::= { ptopoConnEntry 3 }
  282. ptopoConnIndex OBJECT-TYPE
  283. SYNTAX Integer32 (1..2147483647)
  284. MAX-ACCESS not-accessible
  285. STATUS current
  286. DESCRIPTION
  287. "This object represents an arbitrary local integer value
  288. used by this agent to identify a particular connection
  289. instance, unique only for the indicated local connection
  290. endpoint.
  291. A particular ptopoConnIndex value may be reused in the event
  292. an entry is aged out and later re-learned with the same (or
  293. different) remote chassis and port identifiers.
  294. An agent is encouraged to assign monotonically increasing
  295. index values to new entries, starting with one, after each
  296. reboot. It is considered unlikely that the ptopoConnIndex
  297. will wrap between reboots."
  298. ::= { ptopoConnEntry 4 }
  299. ptopoConnRemoteChassisType OBJECT-TYPE
  300. SYNTAX PtopoChassisIdType
  301. MAX-ACCESS read-create
  302. STATUS current
  303. DESCRIPTION
  304. "The type of encoding used to identify the chassis
  305. associated with the remote connection endpoint.
  306. This object may not be modified if the associated
  307. ptopoConnRowStatus object has a value of active(1)."
  308. ::= { ptopoConnEntry 5 }
  309. ptopoConnRemoteChassis OBJECT-TYPE
  310. SYNTAX PtopoChassisId
  311. MAX-ACCESS read-create
  312. STATUS current
  313. DESCRIPTION
  314. "The string value used to identify the chassis component
  315. associated with the remote connection endpoint.
  316. This object may not be modified if the associated
  317. ptopoConnRowStatus object has a value of active(1)."
  318. ::= { ptopoConnEntry 6 }
  319. ptopoConnRemotePortType OBJECT-TYPE
  320. SYNTAX PtopoPortIdType
  321. MAX-ACCESS read-create
  322. STATUS current
  323. DESCRIPTION
  324. "The type of port identifier encoding used in the associated
  325. 'ptopoConnRemotePort' object.
  326. This object may not be modified if the associated
  327. ptopoConnRowStatus object has a value of active(1)."
  328. ::= { ptopoConnEntry 7 }
  329. ptopoConnRemotePort OBJECT-TYPE
  330. SYNTAX PtopoPortId
  331. MAX-ACCESS read-create
  332. STATUS current
  333. DESCRIPTION
  334. "The string value used to identify the port component
  335. associated with the remote connection endpoint.
  336. This object may not be modified if the associated
  337. ptopoConnRowStatus object has a value of active(1)."
  338. ::= { ptopoConnEntry 8 }
  339. ptopoConnDiscAlgorithm OBJECT-TYPE
  340. SYNTAX AutonomousType
  341. MAX-ACCESS read-only
  342. STATUS current
  343. DESCRIPTION
  344. "An indication of the algorithm used to discover the
  345. information contained in this conceptual row.
  346. A value of ptopoDiscoveryLocal indicates this entry was
  347. configured by the local agent, without use of a discovery
  348. protocol.
  349. A value of { 0 0 } indicates this entry was created manually
  350. by an NMS via the associated RowStatus object. "
  351. ::= { ptopoConnEntry 9 }
  352. ptopoConnAgentNetAddrType OBJECT-TYPE
  353. SYNTAX AddressFamilyNumbers
  354. MAX-ACCESS read-create
  355. STATUS current
  356. DESCRIPTION
  357. "This network address type of the associated
  358. ptopoConnNetAddr object, unless that object contains a zero
  359. length string. In such a case, an NMS application should
  360. ignore any returned value for this object.
  361. This object may not be modified if the associated
  362. ptopoConnRowStatus object has a value of active(1)."
  363. ::= { ptopoConnEntry 10 }
  364. ptopoConnAgentNetAddr OBJECT-TYPE
  365. SYNTAX PtopoGenAddr
  366. MAX-ACCESS read-create
  367. STATUS current
  368. DESCRIPTION
  369. "This object identifies a network address which may be used
  370. to reach an SNMP agent entity containing information for the
  371. chassis and port components represented by the associated
  372. 'ptopoConnRemoteChassis' and 'ptopoConnRemotePort' objects.
  373. If no such address is known, then this object shall contain
  374. an empty string.
  375. This object may not be modified if the associated
  376. ptopoConnRowStatus object has a value of active(1)."
  377. ::= { ptopoConnEntry 11 }
  378. ptopoConnMultiMacSASeen OBJECT-TYPE
  379. SYNTAX PtopoAddrSeenState
  380. MAX-ACCESS read-only
  381. STATUS current
  382. DESCRIPTION
  383. "This object indicates if multiple unicast source MAC
  384. addresses have been detected by the agent from the remote
  385. connection endpoint, since the creation of this entry.
  386. If this entry has an associated ptopoConnRemoteChassisType
  387. and/or ptopoConnRemotePortType value other than
  388. 'portIdMacAddr(3)', then the value 'notUsed(1)' is returned.
  389. Otherwise, one of the following conditions must be true:
  390. If the agent has not yet detected any unicast source MAC
  391. addresses from the remote port, then the value 'unknown(2)'
  392. is returned.
  393. If the agent has detected exactly one unicast source MAC
  394. address from the remote port, then the value 'oneAddr(3)' is
  395. returned.
  396. If the agent has detected more than one unicast source MAC
  397. address from the remote port, then the value 'multiAddr(4)'
  398. is returned."
  399. ::= { ptopoConnEntry 12 }
  400. ptopoConnMultiNetSASeen OBJECT-TYPE
  401. SYNTAX PtopoAddrSeenState
  402. MAX-ACCESS read-only
  403. STATUS current
  404. DESCRIPTION
  405. "This object indicates if multiple network layer source
  406. addresses have been detected by the agent from the remote
  407. connection endpoint, since the creation of this entry.
  408. If this entry has an associated ptopoConnRemoteChassisType
  409. or ptopoConnRemotePortType value other than
  410. 'portIdGenAddr(4)' then the value 'notUsed(1)' is returned.
  411. Otherwise, one of the following conditions must be true:
  412. If the agent has not yet detected any network source
  413. addresses of the appropriate type from the remote port, then
  414. the value 'unknown(2)' is returned.
  415. If the agent has detected exactly one network source address
  416. of the appropriate type from the remote port, then the value
  417. 'oneAddr(3)' is returned.
  418. If the agent has detected more than one network source
  419. address (of the same appropriate type) from the remote port,
  420. this the value 'multiAddr(4)' is returned."
  421. ::= { ptopoConnEntry 13 }
  422. ptopoConnIsStatic OBJECT-TYPE
  423. SYNTAX TruthValue
  424. MAX-ACCESS read-create
  425. STATUS current
  426. DESCRIPTION
  427. "This object identifies static ptopoConnEntries. If this
  428. object has the value 'true(1)', then this entry is not
  429. subject to any age-out mechanisms implemented by the agent.
  430. If this object has the value 'false(2)', then this entry is
  431. subject to all age-out mechanisms implemented by the agent.
  432. This object may not be modified if the associated
  433. ptopoConnRowStatus object has a value of active(1)."
  434. DEFVAL { false }
  435. ::= { ptopoConnEntry 14 }
  436. ptopoConnLastVerifyTime OBJECT-TYPE
  437. SYNTAX TimeStamp
  438. MAX-ACCESS read-only
  439. STATUS current
  440. DESCRIPTION
  441. "If the associated value of ptopoConnIsStatic is equal to
  442. 'false(2)', then this object contains the value of sysUpTime
  443. at the time the conceptual row was last verified by the
  444. agent, e.g., via reception of a topology protocol message,
  445. pertaining to the associated remote chassis and port.
  446. If the associated value of ptopoConnIsStatic is equal to
  447. 'true(1)', then this object shall contain the value of
  448. sysUpTime at the time this entry was last activated (i.e.,
  449. ptopoConnRowStatus set to 'active(1)')."
  450. ::= { ptopoConnEntry 15 }
  451. ptopoConnRowStatus OBJECT-TYPE
  452. SYNTAX RowStatus
  453. MAX-ACCESS read-create
  454. STATUS current
  455. DESCRIPTION
  456. "The status of this conceptual row."
  457. ::= { ptopoConnEntry 16 }
  458. -- ***********************************************************
  459. --
  460. -- P T O P O G E N E R A L G R O U P
  461. --
  462. -- ***********************************************************
  463. -- last change time stamp for the whole MIB
  464. ptopoLastChangeTime OBJECT-TYPE
  465. SYNTAX TimeStamp
  466. MAX-ACCESS read-only
  467. STATUS current
  468. DESCRIPTION
  469. "The value of sysUpTime at the time a conceptual row is
  470. created, modified, or deleted in the ptopoConnTable.
  471. An NMS can use this object to reduce polling of the
  472. ptopoData group objects."
  473. ::= { ptopoGeneral 1 }
  474. ptopoConnTabInserts OBJECT-TYPE
  475. SYNTAX Counter32
  476. UNITS "table entries"
  477. MAX-ACCESS read-only
  478. STATUS current
  479. DESCRIPTION
  480. "The number of times an entry has been inserted into the
  481. ptopoConnTable."
  482. ::= { ptopoGeneral 2 }
  483. ptopoConnTabDeletes OBJECT-TYPE
  484. SYNTAX Counter32
  485. UNITS "table entries"
  486. MAX-ACCESS read-only
  487. STATUS current
  488. DESCRIPTION
  489. "The number of times an entry has been deleted from the
  490. ptopoConnTable."
  491. ::= { ptopoGeneral 3 }
  492. ptopoConnTabDrops OBJECT-TYPE
  493. SYNTAX Counter32
  494. UNITS "table entries"
  495. MAX-ACCESS read-only
  496. STATUS current
  497. DESCRIPTION
  498. "The number of times an entry would have been added to the
  499. ptopoConnTable, (e.g., via information learned from a
  500. topology protocol), but was not because of insufficient
  501. resources."
  502. ::= { ptopoGeneral 4 }
  503. ptopoConnTabAgeouts OBJECT-TYPE
  504. SYNTAX Counter32
  505. MAX-ACCESS read-only
  506. STATUS current
  507. DESCRIPTION
  508. "The number of times an entry has been deleted from the
  509. ptopoConnTable because the information timeliness interval
  510. for that entry has expired."
  511. ::= { ptopoGeneral 5 }
  512. -- ***********************************************************
  513. --
  514. -- P T O P O C O N F I G G R O U P
  515. --
  516. -- ***********************************************************
  517. ptopoConfigTrapInterval OBJECT-TYPE
  518. SYNTAX Integer32 (0 | 5..3600)
  519. UNITS "seconds"
  520. MAX-ACCESS read-write
  521. STATUS current
  522. DESCRIPTION
  523. "This object controls the transmission of PTOPO
  524. notifications.
  525. If this object has a value of zero, then no
  526. ptopoConfigChange notifications will be transmitted by the
  527. agent.
  528. If this object has a non-zero value, then the agent must not
  529. generate more than one ptopoConfigChange trap-event in the
  530. indicated period, where a 'trap-event' is the transmission
  531. of a single notification PDU type to a list of notification
  532. destinations. If additional configuration changes occur
  533. within the indicated throttling period, then these trap-
  534. events must be suppressed by the agent. An NMS should
  535. periodically check the value of ptopoLastChangeTime to
  536. detect any missed ptopoConfigChange trap-events, e.g. due to
  537. throttling or transmission loss.
  538. If notification transmission is enabled, the suggested
  539. default throttling period is 60 seconds, but transmission
  540. should be disabled by default.
  541. If the agent is capable of storing non-volatile
  542. configuration, then the value of this object must be
  543. restored after a re-initialization of the management
  544. system."
  545. DEFVAL { 0 }
  546. ::= { ptopoConfig 1 }
  547. ptopoConfigMaxHoldTime OBJECT-TYPE
  548. SYNTAX Integer32 (1..2147483647)
  549. UNITS "seconds"
  550. MAX-ACCESS read-write
  551. STATUS current
  552. DESCRIPTION
  553. "This object specifies the desired time interval for which
  554. an agent will maintain dynamic ptopoConnEntries.
  555. After the specified number of seconds since the last time an
  556. entry was verified, in the absence of new verification
  557. (e.g., receipt of a topology protocol message), the agent
  558. shall remove the entry. Note that entries may not always be
  559. removed immediately, but may possibly be removed at periodic
  560. garbage collection intervals.
  561. This object only affects dynamic ptopoConnEntries, i.e. for
  562. which ptopoConnIsStatic equals 'false(2)'. Static entries
  563. are not aged out.
  564. Note that dynamic ptopoConnEntries may also be removed by
  565. the agent due to the expired timeliness of learned topology
  566. information (e.g., timeliness interval for a remote port
  567. expires). The actual age-out interval for a given entry is
  568. defined by the following formula:
  569. age-out-time =
  570. min(ptopoConfigMaxHoldTime, <entry-specific hold-time>)
  571. where <entry-specific hold-time> is determined by the
  572. discovery algorithm, and may be different for each entry."
  573. DEFVAL { 300 }
  574. ::= { ptopoConfig 2 }
  575. -- PTOPO MIB Notification Definitions
  576. ptopoMIBNotifications OBJECT IDENTIFIER ::= { ptopoMIB 2 }
  577. ptopoMIBTrapPrefix OBJECT IDENTIFIER ::=
  578. { ptopoMIBNotifications 0 }
  579. ptopoConfigChange NOTIFICATION-TYPE
  580. OBJECTS {
  581. ptopoConnTabInserts,
  582. ptopoConnTabDeletes,
  583. ptopoConnTabDrops,
  584. ptopoConnTabAgeouts
  585. }
  586. STATUS current
  587. DESCRIPTION
  588. "A ptopoConfigChange notification is sent when the value of
  589. ptopoLastChangeTime changes. It can be utilized by an NMS to
  590. trigger physical topology table maintenance polls.
  591. Note that transmission of ptopoConfigChange notifications
  592. are throttled by the agent, as specified by the
  593. 'ptopoConfigTrapInterval' object."
  594. ::= { ptopoMIBTrapPrefix 1 }
  595. -- PTOPO Registration Points
  596. ptopoRegistrationPoints OBJECT IDENTIFIER ::= { ptopoMIB 3 }
  597. -- values used with ptopoConnDiscAlgorithm object
  598. ptopoDiscoveryMechanisms OBJECT IDENTIFIER ::=
  599. { ptopoRegistrationPoints 1 }
  600. ptopoDiscoveryLocal OBJECT IDENTIFIER ::=
  601. { ptopoDiscoveryMechanisms 1 }
  602. -- conformance information
  603. ptopoConformance OBJECT IDENTIFIER ::= { ptopoMIB 4 }
  604. ptopoCompliances OBJECT IDENTIFIER ::= { ptopoConformance 1 }
  605. ptopoGroups OBJECT IDENTIFIER ::= { ptopoConformance 2 }
  606. -- compliance statements
  607. ptopoCompliance MODULE-COMPLIANCE
  608. STATUS current
  609. DESCRIPTION
  610. "The compliance statement for SNMP entities which implement
  611. the PTOPO MIB."
  612. MODULE -- this module
  613. MANDATORY-GROUPS {
  614. ptopoDataGroup,
  615. ptopoGeneralGroup,
  616. ptopoConfigGroup,
  617. ptopoNotificationsGroup
  618. }
  619. ::= { ptopoCompliances 1 }
  620. -- MIB groupings
  621. ptopoDataGroup OBJECT-GROUP
  622. OBJECTS {
  623. ptopoConnRemoteChassisType,
  624. ptopoConnRemoteChassis,
  625. ptopoConnRemotePortType,
  626. ptopoConnRemotePort,
  627. ptopoConnDiscAlgorithm,
  628. ptopoConnAgentNetAddrType,
  629. ptopoConnAgentNetAddr,
  630. ptopoConnMultiMacSASeen,
  631. ptopoConnMultiNetSASeen,
  632. ptopoConnIsStatic,
  633. ptopoConnLastVerifyTime,
  634. ptopoConnRowStatus
  635. }
  636. STATUS current
  637. DESCRIPTION
  638. "The collection of objects which are used to represent
  639. physical topology information for which a single agent
  640. provides management information.
  641. This group is mandatory for all implementations of the PTOPO
  642. MIB."
  643. ::= { ptopoGroups 1 }
  644. ptopoGeneralGroup OBJECT-GROUP
  645. OBJECTS {
  646. ptopoLastChangeTime,
  647. ptopoConnTabInserts,
  648. ptopoConnTabDeletes,
  649. ptopoConnTabDrops,
  650. ptopoConnTabAgeouts
  651. }
  652. STATUS current
  653. DESCRIPTION
  654. "The collection of objects which are used to report the
  655. general status of the PTOPO MIB implementation.
  656. This group is mandatory for all agents which implement the
  657. PTOPO MIB."
  658. ::= { ptopoGroups 2 }
  659. ptopoConfigGroup OBJECT-GROUP
  660. OBJECTS {
  661. ptopoConfigTrapInterval,
  662. ptopoConfigMaxHoldTime
  663. }
  664. STATUS current
  665. DESCRIPTION
  666. "The collection of objects which are used to configure the
  667. PTOPO MIB implementation behavior.
  668. This group is mandatory for agents which implement the PTOPO
  669. MIB."
  670. ::= { ptopoGroups 3 }
  671. ptopoNotificationsGroup NOTIFICATION-GROUP
  672. NOTIFICATIONS {
  673. ptopoConfigChange
  674. }
  675. STATUS current
  676. DESCRIPTION
  677. "The collection of notifications used to indicate PTOPO MIB
  678. data consistency and general status information.
  679. This group is mandatory for agents which implement the PTOPO
  680. MIB."
  681. ::= { ptopoGroups 4 }
  682. END