UDPLITE-MIB 21 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548
  1. UDPLITE-MIB DEFINITIONS ::= BEGIN
  2. IMPORTS
  3. MODULE-IDENTITY,
  4. OBJECT-TYPE,
  5. mib-2, Unsigned32,
  6. Counter32, Counter64 FROM SNMPv2-SMI -- [RFC2578]
  7. TimeStamp FROM SNMPv2-TC -- [RFC2579]
  8. MODULE-COMPLIANCE,
  9. OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
  10. InetAddress,
  11. InetAddressType,
  12. InetPortNumber FROM INET-ADDRESS-MIB; -- [RFC4001]
  13. udpliteMIB MODULE-IDENTITY
  14. LAST-UPDATED "200712180000Z" -- 18 December 2007
  15. ORGANIZATION "IETF TSV Working Group (TSVWG)"
  16. CONTACT-INFO
  17. "IETF TSV Working Group
  18. http://www.ietf.org/html.charters/tsvwg-charter.html
  19. Mailing List: tsvwg@ietf.org
  20. Gerrit Renker, Godred Fairhurst
  21. Electronics Research Group
  22. School of Engineering, University of Aberdeen
  23. Fraser Noble Building, Aberdeen AB24 3UE, UK"
  24. DESCRIPTION
  25. "The MIB module for managing UDP-Lite implementations.
  26. Copyright (C) The IETF Trust (2008). This version of
  27. this MIB module is part of RFC 5097; see the RFC
  28. itself for full legal notices."
  29. REVISION "200712180000Z" -- 18 December 2007
  30. DESCRIPTION
  31. "Initial SMIv2 revision, based on the format of the UDP
  32. MIB module (RFC 4113) and published as RFC 5097."
  33. ::= { mib-2 170 }
  34. udplite OBJECT IDENTIFIER ::= { udpliteMIB 1 }
  35. udpliteInDatagrams OBJECT-TYPE -- as in UDP-MIB
  36. SYNTAX Counter64
  37. MAX-ACCESS read-only
  38. STATUS current
  39. DESCRIPTION
  40. "The total number of UDP-Lite datagrams that were
  41. delivered to UDP-Lite users.
  42. Discontinuities in the value of this counter can occur
  43. at re-initialisation of the management system, and at
  44. other times as indicated by the value of
  45. udpliteStatsDiscontinuityTime."
  46. ::= { udplite 1 }
  47. udpliteInPartialCov OBJECT-TYPE -- new in UDP-Lite
  48. SYNTAX Counter64
  49. MAX-ACCESS read-only
  50. STATUS current
  51. DESCRIPTION
  52. "The total number of UDP-Lite datagrams that were
  53. delivered to UDP-Lite users (applications) and whose
  54. checksum coverage was strictly less than the datagram
  55. length.
  56. Discontinuities in the value of this counter can occur
  57. at re-initialisation of the management system, and at
  58. other times as indicated by the value of
  59. udpliteStatsDiscontinuityTime."
  60. ::= { udplite 2 }
  61. udpliteNoPorts OBJECT-TYPE -- as in UDP-MIB
  62. SYNTAX Counter32
  63. MAX-ACCESS read-only
  64. STATUS current
  65. DESCRIPTION
  66. "The total number of received UDP-Lite datagrams for
  67. which there was no listener at the destination port.
  68. Discontinuities in the value of this counter can occur
  69. at re-initialisation of the management system, and at
  70. other times as indicated by the value of
  71. udpliteStatsDiscontinuityTime."
  72. ::= { udplite 3 }
  73. udpliteInErrors OBJECT-TYPE -- as in UDP-MIB
  74. SYNTAX Counter32
  75. MAX-ACCESS read-only
  76. STATUS current
  77. DESCRIPTION
  78. "The number of received UDP-Lite datagrams that could not
  79. be delivered for reasons other than the lack of an
  80. application at the destination port.
  81. Discontinuities in the value of this counter can occur
  82. at re-initialisation of the management system, and at
  83. other times as indicated by the value of
  84. udpliteStatsDiscontinuityTime."
  85. ::= { udplite 4 }
  86. udpliteInBadChecksum OBJECT-TYPE -- new in UDP-Lite
  87. SYNTAX Counter32
  88. MAX-ACCESS read-only
  89. STATUS current
  90. DESCRIPTION
  91. "The number of received UDP-Lite datagrams whose checksum
  92. could not be validated. This includes illegal checksum
  93. coverage values, as their use would lead to incorrect
  94. checksums.
  95. Discontinuities in the value of this counter can occur
  96. at re-initialisation of the management system, and at
  97. other times as indicated by the value of
  98. udpliteStatsDiscontinuityTime."
  99. REFERENCE "RFC 3828, section 3.1"
  100. ::= { udplite 5 }
  101. udpliteOutDatagrams OBJECT-TYPE -- as in UDP-MIB
  102. SYNTAX Counter64
  103. MAX-ACCESS read-only
  104. STATUS current
  105. DESCRIPTION
  106. "The total number of UDP-Lite datagrams sent from this
  107. entity.
  108. Discontinuities in the value of this counter can occur
  109. at re-initialisation of the management system, and at
  110. other times as indicated by the value of
  111. udpliteStatsDiscontinuityTime."
  112. ::= { udplite 6 }
  113. udpliteOutPartialCov OBJECT-TYPE -- new in UDP-Lite
  114. SYNTAX Counter64
  115. MAX-ACCESS read-only
  116. STATUS current
  117. DESCRIPTION
  118. "The total number of udpliteOutDatagrams whose
  119. checksum coverage was strictly less than the
  120. datagram length.
  121. Discontinuities in the value of this counter can occur
  122. at re-initialisation of the management system, and at
  123. other times as indicated by the value of
  124. udpliteStatsDiscontinuityTime."
  125. ::= { udplite 7 }
  126. udpliteEndpointTable OBJECT-TYPE
  127. SYNTAX SEQUENCE OF UdpLiteEndpointEntry
  128. MAX-ACCESS not-accessible
  129. STATUS current
  130. DESCRIPTION
  131. "A table containing information about this entity's
  132. UDP-Lite endpoints on which a local application is
  133. currently accepting or sending datagrams.
  134. The address type in this table represents the address
  135. type used for the communication, irrespective of the
  136. higher-layer abstraction. For example, an application
  137. using IPv6 'sockets' to communicate via IPv4 between
  138. ::ffff:10.0.0.1 and ::ffff:10.0.0.2 would use
  139. InetAddressType ipv4(1).
  140. Like the udpTable in RFC 4113, this table also allows
  141. the representation of an application that completely
  142. specifies both local and remote addresses and ports. A
  143. listening application is represented in three possible
  144. ways:
  145. 1) An application that is willing to accept both IPv4
  146. and IPv6 datagrams is represented by a
  147. udpliteEndpointLocalAddressType of unknown(0) and a
  148. udpliteEndpointLocalAddress of ''h (a zero-length
  149. octet-string).
  150. 2) An application that is willing to accept only IPv4
  151. or only IPv6 datagrams is represented by a
  152. udpliteEndpointLocalAddressType of the appropriate
  153. address type and a udpliteEndpointLocalAddress of
  154. '0.0.0.0' or '::' respectively.
  155. 3) An application that is listening for datagrams only
  156. for a specific IP address but from any remote
  157. system is represented by a
  158. udpliteEndpointLocalAddressType of the appropriate
  159. address type, with udpliteEndpointLocalAddress
  160. specifying the local address.
  161. In all cases where the remote address is a wildcard,
  162. the udpliteEndpointRemoteAddressType is unknown(0),
  163. the udpliteEndpointRemoteAddress is ''h (a zero-length
  164. octet-string), and the udpliteEndpointRemotePort is 0.
  165. If the operating system is demultiplexing UDP-Lite
  166. packets by remote address/port, or if the application
  167. has 'connected' the socket specifying a default remote
  168. address/port, the udpliteEndpointRemote* values should
  169. be used to reflect this."
  170. ::= { udplite 8 }
  171. udpliteEndpointEntry OBJECT-TYPE
  172. SYNTAX UdpLiteEndpointEntry
  173. MAX-ACCESS not-accessible
  174. STATUS current
  175. DESCRIPTION
  176. "Information about a particular current UDP-Lite endpoint.
  177. Implementers need to pay attention to the sizes of
  178. udpliteEndpointLocalAddress/RemoteAddress, as Object
  179. Identifiers (OIDs) of column instances in this table must
  180. have no more than 128 sub-identifiers in order to remain
  181. accessible with SNMPv1, SNMPv2c, and SNMPv3."
  182. INDEX { udpliteEndpointLocalAddressType,
  183. udpliteEndpointLocalAddress,
  184. udpliteEndpointLocalPort,
  185. udpliteEndpointRemoteAddressType,
  186. udpliteEndpointRemoteAddress,
  187. udpliteEndpointRemotePort,
  188. udpliteEndpointInstance }
  189. ::= { udpliteEndpointTable 1 }
  190. UdpLiteEndpointEntry ::= SEQUENCE {
  191. udpliteEndpointLocalAddressType InetAddressType,
  192. udpliteEndpointLocalAddress InetAddress,
  193. udpliteEndpointLocalPort InetPortNumber,
  194. udpliteEndpointRemoteAddressType InetAddressType,
  195. udpliteEndpointRemoteAddress InetAddress,
  196. udpliteEndpointRemotePort InetPortNumber,
  197. udpliteEndpointInstance Unsigned32,
  198. udpliteEndpointProcess Unsigned32,
  199. udpliteEndpointMinCoverage Unsigned32,
  200. udpliteEndpointViolCoverage Counter32
  201. }
  202. udpliteEndpointLocalAddressType OBJECT-TYPE
  203. SYNTAX InetAddressType
  204. MAX-ACCESS not-accessible
  205. STATUS current
  206. DESCRIPTION
  207. "The address type of udpliteEndpointLocalAddress. Only
  208. IPv4, IPv4z, IPv6, and IPv6z addresses are expected, or
  209. unknown(0) if datagrams for all local IP addresses are
  210. accepted."
  211. ::= { udpliteEndpointEntry 1 }
  212. udpliteEndpointLocalAddress OBJECT-TYPE
  213. SYNTAX InetAddress
  214. MAX-ACCESS not-accessible
  215. STATUS current
  216. DESCRIPTION
  217. "The local IP address for this UDP-Lite endpoint.
  218. The value of this object can be represented in three
  219. possible ways, depending on the characteristics of the
  220. listening application:
  221. 1. For an application that is willing to accept both
  222. IPv4 and IPv6 datagrams, the value of this object
  223. must be ''h (a zero-length octet-string), with
  224. the value of the corresponding instance of the
  225. EndpointLocalAddressType object being unknown(0).
  226. 2. For an application that is willing to accept only
  227. IPv4 or only IPv6 datagrams, the value of this
  228. object must be '0.0.0.0' or '::', respectively,
  229. while the corresponding instance of the
  230. EndpointLocalAddressType object represents the
  231. appropriate address type.
  232. 3. For an application that is listening for data
  233. destined only to a specific IP address, the value
  234. of this object is the specific IP address for
  235. which this node is receiving packets, with the
  236. corresponding instance of the
  237. EndpointLocalAddressType object representing the
  238. appropriate address type.
  239. As this object is used in the index for the
  240. udpliteEndpointTable, implementors should be careful
  241. not to create entries that would result in OIDs with
  242. more than 128 sub-identifiers; this is because of SNMP
  243. and SMI limitations."
  244. ::= { udpliteEndpointEntry 2 }
  245. udpliteEndpointLocalPort OBJECT-TYPE
  246. SYNTAX InetPortNumber
  247. MAX-ACCESS not-accessible
  248. STATUS current
  249. DESCRIPTION
  250. "The local port number for this UDP-Lite endpoint."
  251. ::= { udpliteEndpointEntry 3 }
  252. udpliteEndpointRemoteAddressType OBJECT-TYPE
  253. SYNTAX InetAddressType
  254. MAX-ACCESS not-accessible
  255. STATUS current
  256. DESCRIPTION
  257. "The address type of udpliteEndpointRemoteAddress. Only
  258. IPv4, IPv4z, IPv6, and IPv6z addresses are expected, or
  259. unknown(0) if datagrams for all remote IP addresses are
  260. accepted. Also, note that some combinations of
  261. udpliteEndpointLocalAdressType and
  262. udpliteEndpointRemoteAddressType are not supported. In
  263. particular, if the value of this object is not
  264. unknown(0), it is expected to always refer to the
  265. same IP version as udpliteEndpointLocalAddressType."
  266. ::= { udpliteEndpointEntry 4 }
  267. udpliteEndpointRemoteAddress OBJECT-TYPE
  268. SYNTAX InetAddress
  269. MAX-ACCESS not-accessible
  270. STATUS current
  271. DESCRIPTION
  272. "The remote IP address for this UDP-Lite endpoint. If
  273. datagrams from any remote system are to be accepted,
  274. this value is ''h (a zero-length octet-string).
  275. Otherwise, it has the type described by
  276. udpliteEndpointRemoteAddressType and is the address of
  277. the remote system from which datagrams are to be
  278. accepted (or to which all datagrams will be sent).
  279. As this object is used in the index for the
  280. udpliteEndpointTable, implementors should be careful
  281. not to create entries that would result in OIDs with
  282. more than 128 sub-identifiers; this is because of SNMP
  283. and SMI limitations."
  284. ::= { udpliteEndpointEntry 5 }
  285. udpliteEndpointRemotePort OBJECT-TYPE
  286. SYNTAX InetPortNumber
  287. MAX-ACCESS not-accessible
  288. STATUS current
  289. DESCRIPTION
  290. "The remote port number for this UDP-Lite endpoint. If
  291. datagrams from any remote system are to be accepted,
  292. this value is zero."
  293. ::= { udpliteEndpointEntry 6 }
  294. udpliteEndpointInstance OBJECT-TYPE
  295. SYNTAX Unsigned32 (1..'ffffffff'h)
  296. MAX-ACCESS not-accessible
  297. STATUS current
  298. DESCRIPTION
  299. "The instance of this tuple. This object is used to
  300. distinguish among multiple processes 'connected' to
  301. the same UDP-Lite endpoint. For example, on a system
  302. implementing the BSD sockets interface, this would be
  303. used to support the SO_REUSEADDR and SO_REUSEPORT
  304. socket options."
  305. ::= { udpliteEndpointEntry 7 }
  306. udpliteEndpointProcess OBJECT-TYPE
  307. SYNTAX Unsigned32
  308. MAX-ACCESS read-only
  309. STATUS current
  310. DESCRIPTION
  311. "A unique value corresponding to a piece of software
  312. running on this endpoint.
  313. If this endpoint is associated with more than one piece
  314. of software, the agent should choose one of these. As
  315. long as the representative piece of software
  316. is running and still associated with the endpoint,
  317. subsequent reads will consistently return the same
  318. value. The implementation may use any algorithm
  319. satisfying these constraints (e.g., choosing the entity
  320. with the oldest start time).
  321. This identifier is platform-specific. Wherever possible,
  322. it should use the system's native, unique identification
  323. number as the value.
  324. If the SYSAPPL-MIB module is available, the value should
  325. be the same as sysApplElmtRunIndex. If not available, an
  326. alternative should be used (e.g., the hrSWRunIndex of the
  327. HOST-RESOURCES-MIB module).
  328. If it is not possible to uniquely identify the pieces of
  329. software associated with this endpoint, then the value
  330. zero should be used. (Note that zero is otherwise a
  331. valid value for sysApplElmtRunIndex.)"
  332. ::= { udpliteEndpointEntry 8 }
  333. udpliteEndpointMinCoverage OBJECT-TYPE -- new in UDP-Lite
  334. SYNTAX Unsigned32
  335. MAX-ACCESS read-only
  336. STATUS current
  337. DESCRIPTION
  338. "The minimum checksum coverage expected by this endpoint.
  339. A value of 0 indicates that only fully covered datagrams
  340. are accepted."
  341. REFERENCE "RFC 3828, section 3.1"
  342. ::= { udpliteEndpointEntry 9 }
  343. udpliteEndpointViolCoverage OBJECT-TYPE -- new / optional in UDP-Lite
  344. SYNTAX Counter32
  345. MAX-ACCESS read-only
  346. STATUS current
  347. DESCRIPTION
  348. "The number of datagrams received by this endpoint whose
  349. checksum coverage violated the minimum coverage threshold
  350. set for this connection (i.e., all valid datagrams whose
  351. checksum coverage was strictly smaller than the minimum,
  352. as defined in RFC 3828).
  353. Discontinuities in the value of this counter can occur
  354. at re-initialisation of the management system, and at
  355. other times as indicated by the value of
  356. udpliteStatsDiscontinuityTime."
  357. ::= { udpliteEndpointEntry 10 }
  358. udpliteStatsDiscontinuityTime OBJECT-TYPE
  359. SYNTAX TimeStamp
  360. MAX-ACCESS read-only
  361. STATUS current
  362. DESCRIPTION
  363. "The value of sysUpTime at the most recent occasion at
  364. which one or more of the UDP-Lite counters suffered a
  365. discontinuity.
  366. A value of zero indicates no such discontinuity has
  367. occurred since the last re-initialisation of the local
  368. management subsystem."
  369. ::= { udplite 9 }
  370. -- Conformance Information
  371. udpliteMIBConformance OBJECT IDENTIFIER ::= { udpliteMIB 2 }
  372. udpliteMIBCompliance MODULE-COMPLIANCE
  373. STATUS current
  374. DESCRIPTION
  375. "The compliance statement for systems that implement
  376. UDP-Lite.
  377. There are a number of INDEX objects that cannot be
  378. represented in the form of OBJECT clauses in SMIv2,
  379. but for which we have the following compliance
  380. requirements, expressed in OBJECT clause form in this
  381. description clause:
  382. -- OBJECT udpliteEndpointLocalAddressType
  383. -- SYNTAX InetAddressType { unknown(0), ipv4(1),
  384. -- ipv6(2), ipv4z(3),
  385. -- ipv6z(4) }
  386. -- DESCRIPTION
  387. -- Support for dns(16) is not required.
  388. -- OBJECT udpliteEndpointLocalAddress
  389. -- SYNTAX InetAddress (SIZE(0|4|8|16|20))
  390. -- DESCRIPTION
  391. -- Support is only required for zero-length
  392. -- octet-strings, and for scoped and unscoped
  393. -- IPv4 and IPv6 addresses.
  394. -- OBJECT udpliteEndpointRemoteAddressType
  395. -- SYNTAX InetAddressType { unknown(0), ipv4(1),
  396. -- ipv6(2), ipv4z(3),
  397. -- ipv6z(4) }
  398. -- DESCRIPTION
  399. -- Support for dns(16) is not required.
  400. -- OBJECT udpliteEndpointRemoteAddress
  401. -- SYNTAX InetAddress (SIZE(0|4|8|16|20))
  402. -- DESCRIPTION
  403. -- Support is only required for zero-length
  404. -- octet-strings, and for scoped and unscoped
  405. -- IPv4 and IPv6 addresses.
  406. "
  407. MODULE -- this module
  408. MANDATORY-GROUPS { udpliteBaseGroup,
  409. udplitePartialCsumGroup,
  410. udpliteEndpointGroup }
  411. GROUP udpliteAppGroup
  412. DESCRIPTION
  413. "This group is optional and provides supplementary
  414. information about the effectiveness of using minimum
  415. checksum coverage thresholds on endpoints."
  416. ::= { udpliteMIBConformance 1 }
  417. udpliteMIBGroups OBJECT IDENTIFIER ::= { udpliteMIBConformance 2 }
  418. udpliteBaseGroup OBJECT-GROUP -- as in UDP
  419. OBJECTS { udpliteInDatagrams, udpliteNoPorts, udpliteInErrors,
  420. udpliteOutDatagrams, udpliteStatsDiscontinuityTime }
  421. STATUS current
  422. DESCRIPTION
  423. "The group of objects providing for counters of
  424. basic UDP-like statistics."
  425. ::= { udpliteMIBGroups 1 }
  426. udplitePartialCsumGroup OBJECT-GROUP -- specific to UDP-Lite
  427. OBJECTS { udpliteInPartialCov,
  428. udpliteInBadChecksum,
  429. udpliteOutPartialCov }
  430. STATUS current
  431. DESCRIPTION
  432. "The group of objects providing for counters of
  433. transport layer statistics exclusive to UDP-Lite."
  434. ::= { udpliteMIBGroups 2 }
  435. udpliteEndpointGroup OBJECT-GROUP
  436. OBJECTS { udpliteEndpointProcess, udpliteEndpointMinCoverage }
  437. STATUS current
  438. DESCRIPTION
  439. "The group of objects providing for the IP version
  440. independent management of UDP-Lite 'endpoints'."
  441. ::= { udpliteMIBGroups 3 }
  442. udpliteAppGroup OBJECT-GROUP
  443. OBJECTS { udpliteEndpointViolCoverage }
  444. STATUS current
  445. DESCRIPTION
  446. "The group of objects that provide application-level
  447. information for the configuration management of
  448. UDP-Lite 'endpoints'."
  449. ::= { udpliteMIBGroups 4 }
  450. END