logstash-integration-snmp 4.0.0-java

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (324) hide show
  1. checksums.yaml +7 -0
  2. data/CHANGELOG.md +23 -0
  3. data/CONTRIBUTORS +20 -0
  4. data/Gemfile +11 -0
  5. data/LICENSE +202 -0
  6. data/README.md +89 -0
  7. data/VERSION +1 -0
  8. data/docs/index.asciidoc +202 -0
  9. data/docs/input-snmp.asciidoc +524 -0
  10. data/docs/input-snmptrap.asciidoc +392 -0
  11. data/lib/logstash/inputs/snmp.rb +369 -0
  12. data/lib/logstash/inputs/snmptrap.rb +190 -0
  13. data/lib/logstash/plugin_mixins/snmp/common.rb +197 -0
  14. data/lib/logstash-integration-snmp_jars.rb +6 -0
  15. data/lib/mibs/ietf/ACCOUNTING-CONTROL-MIB.dic +1316 -0
  16. data/lib/mibs/ietf/ADSL-LINE-EXT-MIB.dic +1724 -0
  17. data/lib/mibs/ietf/ADSL-LINE-MIB.dic +7297 -0
  18. data/lib/mibs/ietf/ADSL-TC-MIB.dic +160 -0
  19. data/lib/mibs/ietf/ADSL2-LINE-MIB.dic +8663 -0
  20. data/lib/mibs/ietf/ADSL2-LINE-TC-MIB.dic +1462 -0
  21. data/lib/mibs/ietf/AGENTX-MIB.dic +817 -0
  22. data/lib/mibs/ietf/AGGREGATE-MIB.dic +708 -0
  23. data/lib/mibs/ietf/ALARM-MIB.dic +1734 -0
  24. data/lib/mibs/ietf/APM-MIB.dic +2870 -0
  25. data/lib/mibs/ietf/APPC-MIB.dic +8687 -0
  26. data/lib/mibs/ietf/APPLETALK-MIB.dic +4399 -0
  27. data/lib/mibs/ietf/APPLICATION-MIB.dic +3750 -0
  28. data/lib/mibs/ietf/APPN-DLUR-MIB.dic +972 -0
  29. data/lib/mibs/ietf/APPN-MIB.dic +9364 -0
  30. data/lib/mibs/ietf/APPN-TRAP-MIB.dic +664 -0
  31. data/lib/mibs/ietf/APS-MIB.dic +2430 -0
  32. data/lib/mibs/ietf/ARC-MIB.dic +552 -0
  33. data/lib/mibs/ietf/ATM-ACCOUNTING-INFORMATION-MIB.dic +816 -0
  34. data/lib/mibs/ietf/ATM-MIB.dic +4104 -0
  35. data/lib/mibs/ietf/ATM-TC-MIB.dic +914 -0
  36. data/lib/mibs/ietf/ATM2-MIB.dic +4715 -0
  37. data/lib/mibs/ietf/BFD-STD-MIB.dic +2367 -0
  38. data/lib/mibs/ietf/BFD-TC-STD-MIB.dic +202 -0
  39. data/lib/mibs/ietf/BGP4-MIB.dic +1931 -0
  40. data/lib/mibs/ietf/BLDG-HVAC-MIB.dic +812 -0
  41. data/lib/mibs/ietf/BRIDGE-MIB.dic +2257 -0
  42. data/lib/mibs/ietf/CAPWAP-BASE-MIB.dic +4128 -0
  43. data/lib/mibs/ietf/CAPWAP-DOT11-MIB.dic +482 -0
  44. data/lib/mibs/ietf/CHARACTER-MIB.dic +1140 -0
  45. data/lib/mibs/ietf/CIRCUIT-IF-MIB.dic +493 -0
  46. data/lib/mibs/ietf/CLNS-MIB.dic +1702 -0
  47. data/lib/mibs/ietf/COFFEE-POT-MIB.dic +282 -0
  48. data/lib/mibs/ietf/COPS-CLIENT-MIB.dic +1270 -0
  49. data/lib/mibs/ietf/DECNET-PHIV-MIB.dic +5837 -0
  50. data/lib/mibs/ietf/DIAL-CONTROL-MIB.dic +2139 -0
  51. data/lib/mibs/ietf/DIFFSERV-CONFIG-MIB.dic +378 -0
  52. data/lib/mibs/ietf/DIFFSERV-MIB.dic +5073 -0
  53. data/lib/mibs/ietf/DIRECTORY-SERVER-MIB.dic +1041 -0
  54. data/lib/mibs/ietf/DISMAN-EVENT-MIB.dic +3151 -0
  55. data/lib/mibs/ietf/DISMAN-EXPRESSION-MIB.dic +1716 -0
  56. data/lib/mibs/ietf/DISMAN-NSLOOKUP-MIB.dic +698 -0
  57. data/lib/mibs/ietf/DISMAN-PING-MIB.dic +2635 -0
  58. data/lib/mibs/ietf/DISMAN-SCHEDULE-MIB.dic +1744 -0
  59. data/lib/mibs/ietf/DISMAN-SCRIPT-MIB.dic +2820 -0
  60. data/lib/mibs/ietf/DISMAN-TRACEROUTE-MIB.dic +3239 -0
  61. data/lib/mibs/ietf/DLSW-MIB.dic +5635 -0
  62. data/lib/mibs/ietf/DNS-RESOLVER-MIB.dic +1765 -0
  63. data/lib/mibs/ietf/DNS-SERVER-MIB.dic +1593 -0
  64. data/lib/mibs/ietf/DOCS-BPI-MIB.dic +2634 -0
  65. data/lib/mibs/ietf/DOCS-CABLE-DEVICE-MIB.dic +5042 -0
  66. data/lib/mibs/ietf/DOCS-IETF-BPI2-MIB.dic +5478 -0
  67. data/lib/mibs/ietf/DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB.dic +2447 -0
  68. data/lib/mibs/ietf/DOCS-IETF-QOS-MIB.dic +4886 -0
  69. data/lib/mibs/ietf/DOCS-IETF-SUBMGT-MIB.dic +1331 -0
  70. data/lib/mibs/ietf/DOCS-IF-MIB.dic +7980 -0
  71. data/lib/mibs/ietf/DOT12-IF-MIB.dic +1066 -0
  72. data/lib/mibs/ietf/DOT12-RPTR-MIB.dic +2669 -0
  73. data/lib/mibs/ietf/DOT3-EPON-MIB.dic +3297 -0
  74. data/lib/mibs/ietf/DOT3-OAM-MIB.dic +2830 -0
  75. data/lib/mibs/ietf/DS0-MIB.dic +466 -0
  76. data/lib/mibs/ietf/DS0BUNDLE-MIB.dic +468 -0
  77. data/lib/mibs/ietf/DS1-MIB.dic +4890 -0
  78. data/lib/mibs/ietf/DS3-MIB.dic +2719 -0
  79. data/lib/mibs/ietf/DSA-MIB.dic +888 -0
  80. data/lib/mibs/ietf/DSMON-MIB.dic +6177 -0
  81. data/lib/mibs/ietf/DVB-RCS-MIB.dic +5764 -0
  82. data/lib/mibs/ietf/EBN-MIB.dic +1026 -0
  83. data/lib/mibs/ietf/EFM-CU-MIB.dic +4335 -0
  84. data/lib/mibs/ietf/ENTITY-MIB.dic +2235 -0
  85. data/lib/mibs/ietf/ENTITY-SENSOR-MIB.dic +653 -0
  86. data/lib/mibs/ietf/ENTITY-STATE-MIB.dic +457 -0
  87. data/lib/mibs/ietf/ENTITY-STATE-TC-MIB.dic +260 -0
  88. data/lib/mibs/ietf/ETHER-CHIPSET-MIB.dic +787 -0
  89. data/lib/mibs/ietf/EtherLike-MIB.dic +2548 -0
  90. data/lib/mibs/ietf/FC-MGMT-MIB.dic +3465 -0
  91. data/lib/mibs/ietf/FCIP-MGMT-MIB.dic +1596 -0
  92. data/lib/mibs/ietf/FDDI-SMT73-MIB.dic +3378 -0
  93. data/lib/mibs/ietf/FIBRE-CHANNEL-FE-MIB.dic +2504 -0
  94. data/lib/mibs/ietf/FLOAT-TC-MIB.dic +128 -0
  95. data/lib/mibs/ietf/FLOW-METER-MIB.dic +3201 -0
  96. data/lib/mibs/ietf/FORCES-MIB.dic +598 -0
  97. data/lib/mibs/ietf/FR-ATM-PVC-SERVICE-IWF-MIB.dic +1601 -0
  98. data/lib/mibs/ietf/FR-MFR-MIB.dic +1351 -0
  99. data/lib/mibs/ietf/FRAME-RELAY-DTE-MIB.dic +1688 -0
  100. data/lib/mibs/ietf/FRNETSERV-MIB.dic +3940 -0
  101. data/lib/mibs/ietf/FRSLD-MIB.dic +2580 -0
  102. data/lib/mibs/ietf/Finisher-MIB.dic +1416 -0
  103. data/lib/mibs/ietf/GMPLS-LABEL-STD-MIB.dic +965 -0
  104. data/lib/mibs/ietf/GMPLS-LSR-STD-MIB.dic +693 -0
  105. data/lib/mibs/ietf/GMPLS-TC-STD-MIB.dic +180 -0
  106. data/lib/mibs/ietf/GMPLS-TE-STD-MIB.dic +2542 -0
  107. data/lib/mibs/ietf/GSMP-MIB.dic +2468 -0
  108. data/lib/mibs/ietf/HC-ALARM-MIB.dic +1050 -0
  109. data/lib/mibs/ietf/HC-PerfHist-TC-MIB.dic +310 -0
  110. data/lib/mibs/ietf/HC-RMON-MIB.dic +4456 -0
  111. data/lib/mibs/ietf/HDSL2-SHDSL-LINE-MIB.dic +3955 -0
  112. data/lib/mibs/ietf/HOST-RESOURCES-MIB.dic +2453 -0
  113. data/lib/mibs/ietf/HPR-IP-MIB.dic +640 -0
  114. data/lib/mibs/ietf/HPR-MIB.dic +1959 -0
  115. data/lib/mibs/ietf/IANA-ITU-ALARM-TC-MIB.dic +936 -0
  116. data/lib/mibs/ietf/IF-CAP-STACK-MIB.dic +356 -0
  117. data/lib/mibs/ietf/IF-INVERTED-STACK-MIB.dic +220 -0
  118. data/lib/mibs/ietf/IF-MIB.dic +2753 -0
  119. data/lib/mibs/ietf/IFCP-MGMT-MIB.dic +1717 -0
  120. data/lib/mibs/ietf/IGMP-STD-MIB.dic +809 -0
  121. data/lib/mibs/ietf/INET-ADDRESS-MIB.dic +570 -0
  122. data/lib/mibs/ietf/INTEGRATED-SERVICES-GUARANTEED-MIB.dic +319 -0
  123. data/lib/mibs/ietf/INTEGRATED-SERVICES-MIB.dic +1196 -0
  124. data/lib/mibs/ietf/INTERFACETOPN-MIB.dic +1705 -0
  125. data/lib/mibs/ietf/IP-FORWARD-MIB.dic +1853 -0
  126. data/lib/mibs/ietf/IP-MIB.dic +7064 -0
  127. data/lib/mibs/ietf/IPATM-IPMC-MIB.dic +4830 -0
  128. data/lib/mibs/ietf/IPFIX-MIB.dic +2334 -0
  129. data/lib/mibs/ietf/IPFIX-SELECTOR-MIB.dic +215 -0
  130. data/lib/mibs/ietf/IPMCAST-MIB.dic +3390 -0
  131. data/lib/mibs/ietf/IPMROUTE-STD-MIB.dic +1246 -0
  132. data/lib/mibs/ietf/IPOA-MIB.dic +2372 -0
  133. data/lib/mibs/ietf/IPS-AUTH-MIB.dic +1609 -0
  134. data/lib/mibs/ietf/IPSEC-SPD-MIB.dic +3989 -0
  135. data/lib/mibs/ietf/IPV6-FLOW-LABEL-MIB.dic +110 -0
  136. data/lib/mibs/ietf/IPV6-ICMP-MIB.dic +748 -0
  137. data/lib/mibs/ietf/IPV6-MIB.dic +2028 -0
  138. data/lib/mibs/ietf/IPV6-MLD-MIB.dic +659 -0
  139. data/lib/mibs/ietf/IPV6-TCP-MIB.dic +332 -0
  140. data/lib/mibs/ietf/IPV6-UDP-MIB.dic +209 -0
  141. data/lib/mibs/ietf/ISCSI-MIB.dic +4613 -0
  142. data/lib/mibs/ietf/ISDN-MIB.dic +1796 -0
  143. data/lib/mibs/ietf/ISIS-MIB.dic +6215 -0
  144. data/lib/mibs/ietf/ISNS-MIB.dic +6578 -0
  145. data/lib/mibs/ietf/ITU-ALARM-MIB.dic +665 -0
  146. data/lib/mibs/ietf/ITU-ALARM-TC-MIB.dic +137 -0
  147. data/lib/mibs/ietf/Job-Monitoring-MIB.dic +2519 -0
  148. data/lib/mibs/ietf/L2TP-MIB.dic +4050 -0
  149. data/lib/mibs/ietf/LANGTAG-TC-MIB.dic +104 -0
  150. data/lib/mibs/ietf/LISP-MIB.dic +4067 -0
  151. data/lib/mibs/ietf/LMP-MIB.dic +5166 -0
  152. data/lib/mibs/ietf/MALLOC-MIB.dic +2156 -0
  153. data/lib/mibs/ietf/MAU-MIB.dic +2619 -0
  154. data/lib/mibs/ietf/MIDCOM-MIB.dic +2856 -0
  155. data/lib/mibs/ietf/MIOX25-MIB.dic +828 -0
  156. data/lib/mibs/ietf/MIP-MIB.dic +3473 -0
  157. data/lib/mibs/ietf/MOBILEIPV6-MIB.dic +5228 -0
  158. data/lib/mibs/ietf/MPLS-FTN-STD-MIB.dic +1594 -0
  159. data/lib/mibs/ietf/MPLS-L3VPN-STD-MIB.dic +2548 -0
  160. data/lib/mibs/ietf/MPLS-LC-ATM-STD-MIB.dic +491 -0
  161. data/lib/mibs/ietf/MPLS-LC-FR-STD-MIB.dic +395 -0
  162. data/lib/mibs/ietf/MPLS-LDP-ATM-STD-MIB.dic +1019 -0
  163. data/lib/mibs/ietf/MPLS-LDP-FRAME-RELAY-STD-MIB.dic +862 -0
  164. data/lib/mibs/ietf/MPLS-LDP-GENERIC-STD-MIB.dic +445 -0
  165. data/lib/mibs/ietf/MPLS-LDP-STD-MIB.dic +3657 -0
  166. data/lib/mibs/ietf/MPLS-LSR-STD-MIB.dic +3103 -0
  167. data/lib/mibs/ietf/MPLS-TC-STD-MIB.dic +911 -0
  168. data/lib/mibs/ietf/MPLS-TE-STD-MIB.dic +3673 -0
  169. data/lib/mibs/ietf/MSDP-MIB.dic +1893 -0
  170. data/lib/mibs/ietf/MTA-MIB.dic +1898 -0
  171. data/lib/mibs/ietf/Modem-MIB.dic +2054 -0
  172. data/lib/mibs/ietf/NAT-MIB.dic +3866 -0
  173. data/lib/mibs/ietf/NETWORK-SERVICES-MIB.dic +1034 -0
  174. data/lib/mibs/ietf/NHDP-MIB.dic +3005 -0
  175. data/lib/mibs/ietf/NHRP-MIB.dic +3660 -0
  176. data/lib/mibs/ietf/NOTIFICATION-LOG-MIB.dic +1156 -0
  177. data/lib/mibs/ietf/NTPv4-MIB.dic +1535 -0
  178. data/lib/mibs/ietf/OPT-IF-MIB.dic +8972 -0
  179. data/lib/mibs/ietf/OSPF-MIB.dic +5963 -0
  180. data/lib/mibs/ietf/OSPF-TRAP-MIB.dic +1190 -0
  181. data/lib/mibs/ietf/OSPFV3-MIB.dic +5708 -0
  182. data/lib/mibs/ietf/P-BRIDGE-MIB.dic +1499 -0
  183. data/lib/mibs/ietf/PARALLEL-MIB.dic +476 -0
  184. data/lib/mibs/ietf/PIM-MIB.dic +1393 -0
  185. data/lib/mibs/ietf/PIM-STD-MIB.dic +6819 -0
  186. data/lib/mibs/ietf/PINT-MIB.dic +830 -0
  187. data/lib/mibs/ietf/PKTC-IETF-MTA-MIB.dic +3191 -0
  188. data/lib/mibs/ietf/PKTC-IETF-SIG-MIB.dic +4713 -0
  189. data/lib/mibs/ietf/PMIPV6-MIB.dic +3010 -0
  190. data/lib/mibs/ietf/PMIPV6-TC-MIB.dic +293 -0
  191. data/lib/mibs/ietf/POLICY-BASED-MANAGEMENT-MIB.dic +3316 -0
  192. data/lib/mibs/ietf/POWER-ETHERNET-MIB.dic +959 -0
  193. data/lib/mibs/ietf/PPP-BRIDGE-NCP-MIB.dic +587 -0
  194. data/lib/mibs/ietf/PPP-IP-NCP-MIB.dic +269 -0
  195. data/lib/mibs/ietf/PPP-LCP-MIB.dic +994 -0
  196. data/lib/mibs/ietf/PPP-SEC-MIB.dic +411 -0
  197. data/lib/mibs/ietf/PSAMP-MIB.dic +998 -0
  198. data/lib/mibs/ietf/PTOPO-MIB.dic +1135 -0
  199. data/lib/mibs/ietf/PW-ATM-MIB.dic +1642 -0
  200. data/lib/mibs/ietf/PW-CEP-STD-MIB.dic +3661 -0
  201. data/lib/mibs/ietf/PW-STD-MIB.dic +3592 -0
  202. data/lib/mibs/ietf/PW-TC-STD-MIB.dic +437 -0
  203. data/lib/mibs/ietf/PW-TDM-MIB.dic +1896 -0
  204. data/lib/mibs/ietf/PerfHist-TC-MIB.dic +152 -0
  205. data/lib/mibs/ietf/Printer-MIB.dic +6665 -0
  206. data/lib/mibs/ietf/Q-BRIDGE-MIB.dic +3115 -0
  207. data/lib/mibs/ietf/RADIUS-ACC-CLIENT-MIB.dic +991 -0
  208. data/lib/mibs/ietf/RADIUS-ACC-SERVER-MIB.dic +1183 -0
  209. data/lib/mibs/ietf/RADIUS-AUTH-CLIENT-MIB.dic +1073 -0
  210. data/lib/mibs/ietf/RADIUS-AUTH-SERVER-MIB.dic +1251 -0
  211. data/lib/mibs/ietf/RADIUS-DYNAUTH-CLIENT-MIB.dic +1116 -0
  212. data/lib/mibs/ietf/RADIUS-DYNAUTH-SERVER-MIB.dic +1003 -0
  213. data/lib/mibs/ietf/RAQMON-MIB.dic +2695 -0
  214. data/lib/mibs/ietf/RBRIDGE-MIB.dic +2981 -0
  215. data/lib/mibs/ietf/RDBMS-MIB.dic +1935 -0
  216. data/lib/mibs/ietf/RFC1065-SMI.dic +108 -0
  217. data/lib/mibs/ietf/RFC1155-SMI.dic +118 -0
  218. data/lib/mibs/ietf/RFC1158-MIB.dic +2440 -0
  219. data/lib/mibs/ietf/RFC1213-MIB.dic +3434 -0
  220. data/lib/mibs/ietf/RFC1269-MIB.dic +557 -0
  221. data/lib/mibs/ietf/RFC1271-MIB.dic +4135 -0
  222. data/lib/mibs/ietf/RFC1285-MIB.dic +2842 -0
  223. data/lib/mibs/ietf/RFC1316-MIB.dic +800 -0
  224. data/lib/mibs/ietf/RFC1381-MIB.dic +1347 -0
  225. data/lib/mibs/ietf/RFC1382-MIB.dic +3820 -0
  226. data/lib/mibs/ietf/RFC1414-MIB.dic +214 -0
  227. data/lib/mibs/ietf/RIPv2-MIB.dic +773 -0
  228. data/lib/mibs/ietf/RMON-MIB.dic +5551 -0
  229. data/lib/mibs/ietf/RMON2-MIB.dic +8224 -0
  230. data/lib/mibs/ietf/ROHC-MIB.dic +1613 -0
  231. data/lib/mibs/ietf/ROHC-RTP-MIB.dic +859 -0
  232. data/lib/mibs/ietf/ROHC-UNCOMPRESSED-MIB.dic +267 -0
  233. data/lib/mibs/ietf/RPKI-ROUTER-MIB.dic +1363 -0
  234. data/lib/mibs/ietf/RS-232-MIB.dic +1335 -0
  235. data/lib/mibs/ietf/RSERPOOL-MIB.dic +2501 -0
  236. data/lib/mibs/ietf/RSTP-MIB.dic +427 -0
  237. data/lib/mibs/ietf/RSVP-MIB.dic +4135 -0
  238. data/lib/mibs/ietf/RTP-MIB.dic +1376 -0
  239. data/lib/mibs/ietf/SCSI-MIB.dic +3804 -0
  240. data/lib/mibs/ietf/SCTP-MIB.dic +1924 -0
  241. data/lib/mibs/ietf/SFLOW-MIB.dic +568 -0
  242. data/lib/mibs/ietf/SIP-COMMON-MIB.dic +2769 -0
  243. data/lib/mibs/ietf/SIP-MIB.dic +1438 -0
  244. data/lib/mibs/ietf/SIP-SERVER-MIB.dic +1150 -0
  245. data/lib/mibs/ietf/SIP-TC-MIB.dic +257 -0
  246. data/lib/mibs/ietf/SIP-UA-MIB.dic +268 -0
  247. data/lib/mibs/ietf/SLAPM-MIB.dic +4527 -0
  248. data/lib/mibs/ietf/SMON-MIB.dic +1758 -0
  249. data/lib/mibs/ietf/SNA-NAU-MIB.dic +4042 -0
  250. data/lib/mibs/ietf/SNA-SDLC-MIB.dic +3858 -0
  251. data/lib/mibs/ietf/SNMP-COMMUNITY-MIB.dic +715 -0
  252. data/lib/mibs/ietf/SNMP-FRAMEWORK-MIB.dic +709 -0
  253. data/lib/mibs/ietf/SNMP-MPD-MIB.dic +230 -0
  254. data/lib/mibs/ietf/SNMP-NOTIFICATION-MIB.dic +859 -0
  255. data/lib/mibs/ietf/SNMP-PROXY-MIB.dic +414 -0
  256. data/lib/mibs/ietf/SNMP-REPEATER-MIB.dic +4335 -0
  257. data/lib/mibs/ietf/SNMP-SSH-TM-MIB.dic +447 -0
  258. data/lib/mibs/ietf/SNMP-TARGET-MIB.dic +924 -0
  259. data/lib/mibs/ietf/SNMP-TLS-TM-MIB.dic +1449 -0
  260. data/lib/mibs/ietf/SNMP-TSM-MIB.dic +315 -0
  261. data/lib/mibs/ietf/SNMP-USER-BASED-SM-MIB.dic +1164 -0
  262. data/lib/mibs/ietf/SNMP-USM-AES-MIB.dic +95 -0
  263. data/lib/mibs/ietf/SNMP-USM-DH-OBJECTS-MIB.dic +653 -0
  264. data/lib/mibs/ietf/SNMP-VIEW-BASED-ACM-MIB.dic +1202 -0
  265. data/lib/mibs/ietf/SNMPv2-MIB.dic +1382 -0
  266. data/lib/mibs/ietf/SNMPv2-SMI.dic +223 -0
  267. data/lib/mibs/ietf/SNMPv2-USEC-MIB.dic +405 -0
  268. data/lib/mibs/ietf/SONET-MIB.dic +3308 -0
  269. data/lib/mibs/ietf/SOURCE-ROUTING-MIB.dic +542 -0
  270. data/lib/mibs/ietf/SSPM-MIB.dic +1530 -0
  271. data/lib/mibs/ietf/SYSAPPL-MIB.dic +2092 -0
  272. data/lib/mibs/ietf/T11-FC-FABRIC-ADDR-MGR-MIB.dic +1779 -0
  273. data/lib/mibs/ietf/T11-FC-FABRIC-CONFIG-SERVER-MIB.dic +2822 -0
  274. data/lib/mibs/ietf/T11-FC-FABRIC-LOCK-MIB.dic +700 -0
  275. data/lib/mibs/ietf/T11-FC-FSPF-MIB.dic +1889 -0
  276. data/lib/mibs/ietf/T11-FC-NAME-SERVER-MIB.dic +1775 -0
  277. data/lib/mibs/ietf/T11-FC-ROUTE-MIB.dic +655 -0
  278. data/lib/mibs/ietf/T11-FC-RSCN-MIB.dic +1110 -0
  279. data/lib/mibs/ietf/T11-FC-VIRTUAL-FABRIC-MIB.dic +770 -0
  280. data/lib/mibs/ietf/T11-FC-ZONE-SERVER-MIB.dic +3886 -0
  281. data/lib/mibs/ietf/T11-TC-MIB.dic +110 -0
  282. data/lib/mibs/ietf/TCP-ESTATS-MIB.dic +3926 -0
  283. data/lib/mibs/ietf/TCP-MIB.dic +1319 -0
  284. data/lib/mibs/ietf/TCPIPX-MIB.dic +457 -0
  285. data/lib/mibs/ietf/TE-LINK-STD-MIB.dic +2876 -0
  286. data/lib/mibs/ietf/TE-MIB.dic +2924 -0
  287. data/lib/mibs/ietf/TED-MIB.dic +1749 -0
  288. data/lib/mibs/ietf/TIME-AGGREGATE-MIB.dic +550 -0
  289. data/lib/mibs/ietf/TN3270E-MIB.dic +2785 -0
  290. data/lib/mibs/ietf/TN3270E-RT-MIB.dic +1317 -0
  291. data/lib/mibs/ietf/TOKEN-RING-RMON-MIB.dic +2820 -0
  292. data/lib/mibs/ietf/TOKENRING-MIB.dic +1184 -0
  293. data/lib/mibs/ietf/TOKENRING-STATION-SR-MIB.dic +292 -0
  294. data/lib/mibs/ietf/TRANSPORT-ADDRESS-MIB.dic +610 -0
  295. data/lib/mibs/ietf/TRIP-MIB.dic +3159 -0
  296. data/lib/mibs/ietf/TRIP-TC-MIB.dic +241 -0
  297. data/lib/mibs/ietf/TUNNEL-MIB.dic +1095 -0
  298. data/lib/mibs/ietf/UDP-MIB.dic +751 -0
  299. data/lib/mibs/ietf/UDPLITE-MIB.dic +704 -0
  300. data/lib/mibs/ietf/UPS-MIB.dic +3088 -0
  301. data/lib/mibs/ietf/URI-TC-MIB.dic +193 -0
  302. data/lib/mibs/ietf/UUID-TC-MIB.dic +135 -0
  303. data/lib/mibs/ietf/VDSL-LINE-EXT-MCM-MIB.dic +989 -0
  304. data/lib/mibs/ietf/VDSL-LINE-EXT-SCM-MIB.dic +605 -0
  305. data/lib/mibs/ietf/VDSL-LINE-MIB.dic +4518 -0
  306. data/lib/mibs/ietf/VDSL2-LINE-MIB.dic +11029 -0
  307. data/lib/mibs/ietf/VDSL2-LINE-TC-MIB.dic +3152 -0
  308. data/lib/mibs/ietf/VPN-TC-STD-MIB.dic +121 -0
  309. data/lib/mibs/ietf/VRRP-MIB.dic +1163 -0
  310. data/lib/mibs/ietf/VRRPV3-MIB.dic +1403 -0
  311. data/lib/mibs/ietf/WWW-MIB.dic +1810 -0
  312. data/lib/mibs/logstash/iso.dic +18 -0
  313. data/logstash-integration-snmp.gemspec +40 -0
  314. data/spec/fixtures/RFC1213-MIB.dic +3445 -0
  315. data/spec/fixtures/collision.dic +25 -0
  316. data/spec/integration/inputs/snmp_spec.rb +443 -0
  317. data/spec/integration/inputs/snmptrap_spec.rb +383 -0
  318. data/spec/unit/inputs/common_spec.rb +264 -0
  319. data/spec/unit/inputs/snmp_spec.rb +510 -0
  320. data/spec/unit/inputs/snmptrap_spec.rb +141 -0
  321. data/vendor/jar-dependencies/org/logstash/integrations/plugin/4.0.0/plugin-4.0.0.jar +0 -0
  322. data/vendor/jar-dependencies/org/snakeyaml/snakeyaml-engine/2.7/snakeyaml-engine-2.7.jar +0 -0
  323. data/vendor/jar-dependencies/org/snmp4j/snmp4j/3.8.0/snmp4j-3.8.0.jar +0 -0
  324. metadata +523 -0
@@ -0,0 +1,1449 @@
1
+ # python version 1.0 DO NOT EDIT
2
+ #
3
+ # This python file has been generated by smidump version 0.5.0:
4
+ #
5
+ # smidump -f python SNMP-TLS-TM-MIB
6
+
7
+ FILENAME = "./libsmi-0.5.0/mibs/ietf/SNMP-TLS-TM-MIB"
8
+
9
+ MIB = {
10
+ "moduleName" : "SNMP-TLS-TM-MIB",
11
+
12
+ "SNMP-TLS-TM-MIB" : {
13
+ "nodetype" : "module",
14
+ "language" : "SMIv2",
15
+ "organization" :
16
+ """ISMS Working Group""",
17
+ "contact" :
18
+ """WG-EMail: isms@lists.ietf.org
19
+ Subscribe: isms-request@lists.ietf.org
20
+
21
+ Chairs:
22
+ Juergen Schoenwaelder
23
+ Jacobs University Bremen
24
+ Campus Ring 1
25
+ 28725 Bremen
26
+ Germany
27
+ +49 421 200-3587
28
+ j.schoenwaelder@jacobs-university.de
29
+
30
+ Russ Mundy
31
+ SPARTA, Inc.
32
+ 7110 Samuel Morse Drive
33
+ Columbia, MD 21046
34
+ USA
35
+
36
+ Editor:
37
+ Wes Hardaker
38
+ SPARTA, Inc.
39
+ P.O. Box 382
40
+ Davis, CA 95617
41
+ USA
42
+ ietf@hardakers.net""",
43
+ "description" :
44
+ """
45
+ The TLS Transport Model MIB
46
+
47
+ Copyright (c) 2010 IETF Trust and the persons identified as
48
+ the document authors. All rights reserved.
49
+
50
+ Redistribution and use in source and binary forms, with or
51
+ without modification, is permitted pursuant to, and subject
52
+ to the license terms contained in, the Simplified BSD License
53
+ set forth in Section 4.c of the IETF Trust's Legal Provisions
54
+ Relating to IETF Documents
55
+ (http://trustee.ietf.org/license-info).""",
56
+ "revisions" : (
57
+ {
58
+ "date" : "2010-05-07 00:00",
59
+ "description" :
60
+ """This version of this MIB module is part of
61
+ RFC 5953; see the RFC itself for full legal
62
+ notices.""",
63
+ },
64
+ ),
65
+ "identity node" : "snmpTlstmMIB",
66
+ },
67
+
68
+ "imports" : (
69
+ {"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
70
+ {"module" : "SNMPv2-SMI", "name" : "OBJECT-TYPE"},
71
+ {"module" : "SNMPv2-SMI", "name" : "OBJECT-IDENTITY"},
72
+ {"module" : "SNMPv2-SMI", "name" : "mib-2"},
73
+ {"module" : "SNMPv2-SMI", "name" : "snmpDomains"},
74
+ {"module" : "SNMPv2-SMI", "name" : "Counter32"},
75
+ {"module" : "SNMPv2-SMI", "name" : "Unsigned32"},
76
+ {"module" : "SNMPv2-SMI", "name" : "Gauge32"},
77
+ {"module" : "SNMPv2-SMI", "name" : "NOTIFICATION-TYPE"},
78
+ {"module" : "SNMPv2-TC", "name" : "TEXTUAL-CONVENTION"},
79
+ {"module" : "SNMPv2-TC", "name" : "TimeStamp"},
80
+ {"module" : "SNMPv2-TC", "name" : "RowStatus"},
81
+ {"module" : "SNMPv2-TC", "name" : "StorageType"},
82
+ {"module" : "SNMPv2-TC", "name" : "AutonomousType"},
83
+ {"module" : "SNMPv2-CONF", "name" : "MODULE-COMPLIANCE"},
84
+ {"module" : "SNMPv2-CONF", "name" : "OBJECT-GROUP"},
85
+ {"module" : "SNMPv2-CONF", "name" : "NOTIFICATION-GROUP"},
86
+ {"module" : "SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
87
+ {"module" : "SNMP-TARGET-MIB", "name" : "snmpTargetParamsName"},
88
+ {"module" : "SNMP-TARGET-MIB", "name" : "snmpTargetAddrName"},
89
+ ),
90
+
91
+ "typedefs" : {
92
+ "SnmpTLSAddress" : {
93
+ "basetype" : "OctetString",
94
+ "status" : "current",
95
+ "ranges" : [
96
+ {
97
+ "min" : "1",
98
+ "max" : "255"
99
+ },
100
+ ],
101
+ "range" : {
102
+ "min" : "1",
103
+ "max" : "255"
104
+ },
105
+ "format" : "1a",
106
+ "description" :
107
+ """Represents an IPv4 address, an IPv6 address, or a
108
+ US-ASCII-encoded hostname and port number.
109
+
110
+ An IPv4 address must be in dotted decimal format followed by a
111
+ colon ':' (US-ASCII character 0x3A) and a decimal port number
112
+ in US-ASCII.
113
+
114
+ An IPv6 address must be a colon-separated format (as described
115
+ in RFC 5952), surrounded by square brackets ('[', US-ASCII
116
+ character 0x5B, and ']', US-ASCII character 0x5D), followed by
117
+ a colon ':' (US-ASCII character 0x3A) and a decimal port number
118
+ in US-ASCII.
119
+
120
+ A hostname is always in US-ASCII (as per [RFC1033]);
121
+ internationalized hostnames are encoded in US-ASCII as domain
122
+ names after transformation via the ToASCII operation specified
123
+ in [RFC3490]. The ToASCII operation MUST be performed with the
124
+ UseSTD3ASCIIRules flag set. The hostname is followed by a
125
+ colon ':' (US-ASCII character 0x3A) and a decimal port number
126
+ in US-ASCII. The name SHOULD be fully qualified whenever
127
+ possible.
128
+
129
+ Values of this textual convention may not be directly usable
130
+ as transport-layer addressing information, and may require
131
+ run-time resolution. As such, applications that write them
132
+ must be prepared for handling errors if such values are not
133
+ supported, or cannot be resolved (if resolution occurs at the
134
+ time of the management operation).
135
+
136
+ The DESCRIPTION clause of TransportAddress objects that may
137
+ have SnmpTLSAddress values must fully describe how (and
138
+ when) such names are to be resolved to IP addresses and vice
139
+ versa.
140
+
141
+ This textual convention SHOULD NOT be used directly in object
142
+ definitions since it restricts addresses to a specific
143
+ format. However, if it is used, it MAY be used either on its
144
+ own or in conjunction with TransportAddressType or
145
+ TransportDomain as a pair.
146
+
147
+ When this textual convention is used as a syntax of an index
148
+ object, there may be issues with the limit of 128
149
+ sub-identifiers specified in SMIv2 (STD 58). It is RECOMMENDED
150
+ that all MIB documents using this textual convention make
151
+
152
+
153
+
154
+ explicit any limitations on index component lengths that
155
+ management software must observe. This may be done either by
156
+ including SIZE constraints on the index components or by
157
+ specifying applicable constraints in the conceptual row
158
+ DESCRIPTION clause or in the surrounding documentation.""",
159
+ "reference" :
160
+ """RFC 1033: DOMAIN ADMINISTRATORS OPERATIONS GUIDE
161
+ RFC 3490: Internationalizing Domain Names in Applications
162
+ RFC 5952: A Recommendation for IPv6 Address Text Representation""",
163
+ },
164
+ "SnmpTLSFingerprint" : {
165
+ "basetype" : "OctetString",
166
+ "status" : "current",
167
+ "ranges" : [
168
+ {
169
+ "min" : "0",
170
+ "max" : "255"
171
+ },
172
+ ],
173
+ "range" : {
174
+ "min" : "0",
175
+ "max" : "255"
176
+ },
177
+ "format" : "1x:1x",
178
+ "description" :
179
+ """A fingerprint value that can be used to uniquely reference
180
+ other data of potentially arbitrary length.
181
+
182
+ An SnmpTLSFingerprint value is composed of a 1-octet hashing
183
+ algorithm identifier followed by the fingerprint value. The
184
+ octet value encoded is taken from the IANA TLS HashAlgorithm
185
+ Registry (RFC 5246). The remaining octets are filled using the
186
+ results of the hashing algorithm.
187
+
188
+ This TEXTUAL-CONVENTION allows for a zero-length (blank)
189
+ SnmpTLSFingerprint value for use in tables where the
190
+ fingerprint value may be optional. MIB definitions or
191
+ implementations may refuse to accept a zero-length value as
192
+ appropriate.""",
193
+ "reference" :
194
+ """RFC 5246: The Transport Layer
195
+ Security (TLS) Protocol Version 1.2
196
+ http://www.iana.org/assignments/tls-parameters/""",
197
+ },
198
+ }, # typedefs
199
+
200
+ "nodes" : {
201
+ "snmpTlstmMIB" : {
202
+ "nodetype" : "node",
203
+ "moduleName" : "SNMP-TLS-TM-MIB",
204
+ "oid" : "1.3.6.1.2.1.198",
205
+ "status" : "current",
206
+ }, # node
207
+ "snmpTlstmNotifications" : {
208
+ "nodetype" : "node",
209
+ "moduleName" : "SNMP-TLS-TM-MIB",
210
+ "oid" : "1.3.6.1.2.1.198.0",
211
+ }, # node
212
+ "snmpTlstmIdentities" : {
213
+ "nodetype" : "node",
214
+ "moduleName" : "SNMP-TLS-TM-MIB",
215
+ "oid" : "1.3.6.1.2.1.198.1",
216
+ }, # node
217
+ "snmpTlstmCertToTSNMIdentities" : {
218
+ "nodetype" : "node",
219
+ "moduleName" : "SNMP-TLS-TM-MIB",
220
+ "oid" : "1.3.6.1.2.1.198.1.1",
221
+ }, # node
222
+ "snmpTlstmCertSpecified" : {
223
+ "nodetype" : "node",
224
+ "moduleName" : "SNMP-TLS-TM-MIB",
225
+ "oid" : "1.3.6.1.2.1.198.1.1.1",
226
+ "status" : "current",
227
+ "description" :
228
+ """Directly specifies the tmSecurityName to be used for
229
+ this certificate. The value of the tmSecurityName
230
+ to use is specified in the snmpTlstmCertToTSNData
231
+ column. The snmpTlstmCertToTSNData column must
232
+
233
+
234
+
235
+ contain a non-zero length SnmpAdminString compliant
236
+ value or the mapping described in this row must be
237
+ considered a failure.""",
238
+ }, # node
239
+ "snmpTlstmCertSANRFC822Name" : {
240
+ "nodetype" : "node",
241
+ "moduleName" : "SNMP-TLS-TM-MIB",
242
+ "oid" : "1.3.6.1.2.1.198.1.1.2",
243
+ "status" : "current",
244
+ "description" :
245
+ """Maps a subjectAltName's rfc822Name to a
246
+ tmSecurityName. The local part of the rfc822Name is
247
+ passed unaltered but the host-part of the name must
248
+ be passed in lowercase. This mapping results in a
249
+ 1:1 correspondence between equivalent subjectAltName
250
+ rfc822Name values and tmSecurityName values except
251
+ that the host-part of the name MUST be passed in
252
+ lowercase.
253
+
254
+ Example rfc822Name Field: FooBar@Example.COM
255
+ is mapped to tmSecurityName: FooBar@example.com.""",
256
+ }, # node
257
+ "snmpTlstmCertSANDNSName" : {
258
+ "nodetype" : "node",
259
+ "moduleName" : "SNMP-TLS-TM-MIB",
260
+ "oid" : "1.3.6.1.2.1.198.1.1.3",
261
+ "status" : "current",
262
+ "description" :
263
+ """Maps a subjectAltName's dNSName to a
264
+ tmSecurityName after first converting it to all
265
+ lowercase (RFC 5280 does not specify converting to
266
+ lowercase so this involves an extra step). This
267
+ mapping results in a 1:1 correspondence between
268
+ subjectAltName dNSName values and the tmSecurityName
269
+ values.""",
270
+ "reference" :
271
+ """RFC 5280 - Internet X.509 Public Key Infrastructure
272
+ Certificate and Certificate Revocation
273
+ List (CRL) Profile.""",
274
+ }, # node
275
+ "snmpTlstmCertSANIpAddress" : {
276
+ "nodetype" : "node",
277
+ "moduleName" : "SNMP-TLS-TM-MIB",
278
+ "oid" : "1.3.6.1.2.1.198.1.1.4",
279
+ "status" : "current",
280
+ "description" :
281
+ """Maps a subjectAltName's iPAddress to a
282
+ tmSecurityName by transforming the binary encoded
283
+ address as follows:
284
+
285
+
286
+ 1) for IPv4, the value is converted into a
287
+ decimal-dotted quad address (e.g., '192.0.2.1').
288
+
289
+ 2) for IPv6 addresses, the value is converted into a
290
+ 32-character all lowercase hexadecimal string
291
+ without any colon separators.
292
+
293
+
294
+
295
+
296
+ This mapping results in a 1:1 correspondence between
297
+ subjectAltName iPAddress values and the
298
+ tmSecurityName values.
299
+
300
+ The resulting length of an encoded IPv6 address is
301
+ the maximum length supported by the View-Based
302
+ Access Control Model (VACM). Using both the
303
+ Transport Security Model's support for transport
304
+ prefixes (see the SNMP-TSM-MIB's
305
+ snmpTsmConfigurationUsePrefix object for details)
306
+ will result in securityName lengths that exceed what
307
+ VACM can handle.""",
308
+ }, # node
309
+ "snmpTlstmCertSANAny" : {
310
+ "nodetype" : "node",
311
+ "moduleName" : "SNMP-TLS-TM-MIB",
312
+ "oid" : "1.3.6.1.2.1.198.1.1.5",
313
+ "status" : "current",
314
+ "description" :
315
+ """Maps any of the following fields using the
316
+ corresponding mapping algorithms:
317
+
318
+ |------------+----------------------------|
319
+ | Type | Algorithm |
320
+ |------------+----------------------------|
321
+ | rfc822Name | snmpTlstmCertSANRFC822Name |
322
+ | dNSName | snmpTlstmCertSANDNSName |
323
+ | iPAddress | snmpTlstmCertSANIpAddress |
324
+ |------------+----------------------------|
325
+
326
+ The first matching subjectAltName value found in the
327
+ certificate of the above types MUST be used when
328
+ deriving the tmSecurityName. The mapping algorithm
329
+ specified in the 'Algorithm' column MUST be used to
330
+ derive the tmSecurityName.
331
+
332
+ This mapping results in a 1:1 correspondence between
333
+ subjectAltName values and tmSecurityName values. The
334
+ three sub-mapping algorithms produced by this
335
+ combined algorithm cannot produce conflicting
336
+ results between themselves.""",
337
+ }, # node
338
+ "snmpTlstmCertCommonName" : {
339
+ "nodetype" : "node",
340
+ "moduleName" : "SNMP-TLS-TM-MIB",
341
+ "oid" : "1.3.6.1.2.1.198.1.1.6",
342
+ "status" : "current",
343
+ "description" :
344
+ """Maps a certificate's CommonName to a tmSecurityName
345
+ after converting it to a UTF-8 encoding. The usage
346
+ of CommonNames is deprecated and users are
347
+ encouraged to use subjectAltName mapping methods
348
+
349
+
350
+
351
+
352
+ instead. This mapping results in a 1:1
353
+ correspondence between certificate CommonName values
354
+ and tmSecurityName values.""",
355
+ }, # node
356
+ "snmpTlstmObjects" : {
357
+ "nodetype" : "node",
358
+ "moduleName" : "SNMP-TLS-TM-MIB",
359
+ "oid" : "1.3.6.1.2.1.198.2",
360
+ }, # node
361
+ "snmpTlstmSession" : {
362
+ "nodetype" : "node",
363
+ "moduleName" : "SNMP-TLS-TM-MIB",
364
+ "oid" : "1.3.6.1.2.1.198.2.1",
365
+ }, # node
366
+ "snmpTlstmSessionOpens" : {
367
+ "nodetype" : "scalar",
368
+ "moduleName" : "SNMP-TLS-TM-MIB",
369
+ "oid" : "1.3.6.1.2.1.198.2.1.1",
370
+ "status" : "current",
371
+ "syntax" : {
372
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
373
+ },
374
+ "access" : "readonly",
375
+ "description" :
376
+ """The number of times an openSession() request has been executed
377
+ as a (D)TLS client, regardless of whether it succeeded or
378
+ failed.""",
379
+ }, # scalar
380
+ "snmpTlstmSessionClientCloses" : {
381
+ "nodetype" : "scalar",
382
+ "moduleName" : "SNMP-TLS-TM-MIB",
383
+ "oid" : "1.3.6.1.2.1.198.2.1.2",
384
+ "status" : "current",
385
+ "syntax" : {
386
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
387
+ },
388
+ "access" : "readonly",
389
+ "description" :
390
+ """The number of times a closeSession() request has been
391
+ executed as an (D)TLS client, regardless of whether it
392
+ succeeded or failed.""",
393
+ }, # scalar
394
+ "snmpTlstmSessionOpenErrors" : {
395
+ "nodetype" : "scalar",
396
+ "moduleName" : "SNMP-TLS-TM-MIB",
397
+ "oid" : "1.3.6.1.2.1.198.2.1.3",
398
+ "status" : "current",
399
+ "syntax" : {
400
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
401
+ },
402
+ "access" : "readonly",
403
+ "description" :
404
+ """The number of times an openSession() request failed to open a
405
+ session as a (D)TLS client, for any reason.""",
406
+ }, # scalar
407
+ "snmpTlstmSessionAccepts" : {
408
+ "nodetype" : "scalar",
409
+ "moduleName" : "SNMP-TLS-TM-MIB",
410
+ "oid" : "1.3.6.1.2.1.198.2.1.4",
411
+ "status" : "current",
412
+ "syntax" : {
413
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
414
+ },
415
+ "access" : "readonly",
416
+ "description" :
417
+ """The number of times a (D)TLS server has accepted a new
418
+ connection from a client and has received at least one SNMP
419
+ message through it.""",
420
+ }, # scalar
421
+ "snmpTlstmSessionServerCloses" : {
422
+ "nodetype" : "scalar",
423
+ "moduleName" : "SNMP-TLS-TM-MIB",
424
+ "oid" : "1.3.6.1.2.1.198.2.1.5",
425
+ "status" : "current",
426
+ "syntax" : {
427
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
428
+ },
429
+ "access" : "readonly",
430
+ "description" :
431
+ """The number of times a closeSession() request has been
432
+ executed as an (D)TLS server, regardless of whether it
433
+ succeeded or failed.""",
434
+ }, # scalar
435
+ "snmpTlstmSessionNoSessions" : {
436
+ "nodetype" : "scalar",
437
+ "moduleName" : "SNMP-TLS-TM-MIB",
438
+ "oid" : "1.3.6.1.2.1.198.2.1.6",
439
+ "status" : "current",
440
+ "syntax" : {
441
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
442
+ },
443
+ "access" : "readonly",
444
+ "description" :
445
+ """The number of times an outgoing message was dropped because
446
+ the session associated with the passed tmStateReference was no
447
+ longer (or was never) available.""",
448
+ }, # scalar
449
+ "snmpTlstmSessionInvalidClientCertificates" : {
450
+ "nodetype" : "scalar",
451
+ "moduleName" : "SNMP-TLS-TM-MIB",
452
+ "oid" : "1.3.6.1.2.1.198.2.1.7",
453
+ "status" : "current",
454
+ "syntax" : {
455
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
456
+ },
457
+ "access" : "readonly",
458
+ "description" :
459
+ """The number of times an incoming session was not established
460
+ on an (D)TLS server because the presented client certificate
461
+ was invalid. Reasons for invalidation include, but are not
462
+ limited to, cryptographic validation failures or lack of a
463
+ suitable mapping row in the snmpTlstmCertToTSNTable.""",
464
+ }, # scalar
465
+ "snmpTlstmSessionUnknownServerCertificate" : {
466
+ "nodetype" : "scalar",
467
+ "moduleName" : "SNMP-TLS-TM-MIB",
468
+ "oid" : "1.3.6.1.2.1.198.2.1.8",
469
+ "status" : "current",
470
+ "syntax" : {
471
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
472
+ },
473
+ "access" : "readonly",
474
+ "description" :
475
+ """The number of times an outgoing session was not established
476
+ on an (D)TLS client because the server certificate presented
477
+ by an SNMP over (D)TLS server was invalid because no
478
+ configured fingerprint or Certification Authority (CA) was
479
+ acceptable to validate it.
480
+ This may result because there was no entry in the
481
+ snmpTlstmAddrTable or because no path could be found to a
482
+ known CA.""",
483
+ }, # scalar
484
+ "snmpTlstmSessionInvalidServerCertificates" : {
485
+ "nodetype" : "scalar",
486
+ "moduleName" : "SNMP-TLS-TM-MIB",
487
+ "oid" : "1.3.6.1.2.1.198.2.1.9",
488
+ "status" : "current",
489
+ "syntax" : {
490
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
491
+ },
492
+ "access" : "readonly",
493
+ "description" :
494
+ """The number of times an outgoing session was not established
495
+ on an (D)TLS client because the server certificate presented
496
+ by an SNMP over (D)TLS server could not be validated even if
497
+ the fingerprint or expected validation path was known. That
498
+ is, a cryptographic validation error occurred during
499
+ certificate validation processing.
500
+
501
+ Reasons for invalidation include, but are not
502
+ limited to, cryptographic validation failures.""",
503
+ }, # scalar
504
+ "snmpTlstmSessionInvalidCaches" : {
505
+ "nodetype" : "scalar",
506
+ "moduleName" : "SNMP-TLS-TM-MIB",
507
+ "oid" : "1.3.6.1.2.1.198.2.1.10",
508
+ "status" : "current",
509
+ "syntax" : {
510
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
511
+ },
512
+ "access" : "readonly",
513
+ "description" :
514
+ """The number of outgoing messages dropped because the
515
+ tmStateReference referred to an invalid cache.""",
516
+ }, # scalar
517
+ "snmpTlstmConfig" : {
518
+ "nodetype" : "node",
519
+ "moduleName" : "SNMP-TLS-TM-MIB",
520
+ "oid" : "1.3.6.1.2.1.198.2.2",
521
+ }, # node
522
+ "snmpTlstmCertificateMapping" : {
523
+ "nodetype" : "node",
524
+ "moduleName" : "SNMP-TLS-TM-MIB",
525
+ "oid" : "1.3.6.1.2.1.198.2.2.1",
526
+ }, # node
527
+ "snmpTlstmCertToTSNCount" : {
528
+ "nodetype" : "scalar",
529
+ "moduleName" : "SNMP-TLS-TM-MIB",
530
+ "oid" : "1.3.6.1.2.1.198.2.2.1.1",
531
+ "status" : "current",
532
+ "syntax" : {
533
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Gauge32"},
534
+ },
535
+ "access" : "readonly",
536
+ "description" :
537
+ """A count of the number of entries in the
538
+ snmpTlstmCertToTSNTable.""",
539
+ }, # scalar
540
+ "snmpTlstmCertToTSNTableLastChanged" : {
541
+ "nodetype" : "scalar",
542
+ "moduleName" : "SNMP-TLS-TM-MIB",
543
+ "oid" : "1.3.6.1.2.1.198.2.2.1.2",
544
+ "status" : "current",
545
+ "syntax" : {
546
+ "type" : { "module" :"SNMPv2-TC", "name" : "TimeStamp"},
547
+ },
548
+ "access" : "readonly",
549
+ "description" :
550
+ """The value of sysUpTime.0 when the snmpTlstmCertToTSNTable was
551
+ last modified through any means, or 0 if it has not been
552
+ modified since the command responder was started.""",
553
+ }, # scalar
554
+ "snmpTlstmCertToTSNTable" : {
555
+ "nodetype" : "table",
556
+ "moduleName" : "SNMP-TLS-TM-MIB",
557
+ "oid" : "1.3.6.1.2.1.198.2.2.1.3",
558
+ "status" : "current",
559
+ "description" :
560
+ """This table is used by a (D)TLS server to map the (D)TLS
561
+ client's presented X.509 certificate to a tmSecurityName.
562
+
563
+ On an incoming (D)TLS/SNMP connection, the client's presented
564
+ certificate must either be validated based on an established
565
+ trust anchor, or it must directly match a fingerprint in this
566
+ table. This table does not provide any mechanisms for
567
+ configuring the trust anchors; the transfer of any needed
568
+ trusted certificates for path validation is expected to occur
569
+ through an out-of-band transfer.
570
+
571
+ Once the certificate has been found acceptable (either by path
572
+ validation or directly matching a fingerprint in this table),
573
+ this table is consulted to determine the appropriate
574
+ tmSecurityName to identify with the remote connection. This
575
+ is done by considering each active row from this table in
576
+ prioritized order according to its snmpTlstmCertToTSNID value.
577
+ Each row's snmpTlstmCertToTSNFingerprint value determines
578
+ whether the row is a match for the incoming connection:
579
+
580
+ 1) If the row's snmpTlstmCertToTSNFingerprint value
581
+ identifies the presented certificate, then consider the
582
+ row as a successful match.
583
+
584
+ 2) If the row's snmpTlstmCertToTSNFingerprint value
585
+ identifies a locally held copy of a trusted CA
586
+ certificate and that CA certificate was used to
587
+ validate the path to the presented certificate, then
588
+ consider the row as a successful match.
589
+
590
+ Once a matching row has been found, the
591
+ snmpTlstmCertToTSNMapType value can be used to determine how
592
+ the tmSecurityName to associate with the session should be
593
+
594
+
595
+
596
+ determined. See the snmpTlstmCertToTSNMapType column's
597
+ DESCRIPTION for details on determining the tmSecurityName
598
+ value. If it is impossible to determine a tmSecurityName from
599
+ the row's data combined with the data presented in the
600
+ certificate, then additional rows MUST be searched looking for
601
+ another potential match. If a resulting tmSecurityName mapped
602
+ from a given row is not compatible with the needed
603
+ requirements of a tmSecurityName (e.g., VACM imposes a
604
+ 32-octet-maximum length and the certificate derived
605
+ securityName could be longer), then it must be considered an
606
+ invalid match and additional rows MUST be searched looking for
607
+ another potential match.
608
+
609
+ If no matching and valid row can be found, the connection MUST
610
+ be closed and SNMP messages MUST NOT be accepted over it.
611
+
612
+ Missing values of snmpTlstmCertToTSNID are acceptable and
613
+ implementations should continue to the next highest numbered
614
+ row. It is recommended that administrators skip index values
615
+ to leave room for the insertion of future rows (for example,
616
+ use values of 10 and 20 when creating initial rows).
617
+
618
+ Users are encouraged to make use of certificates with
619
+ subjectAltName fields that can be used as tmSecurityNames so
620
+ that a single root CA certificate can allow all child
621
+ certificate's subjectAltName to map directly to a
622
+ tmSecurityName via a 1:1 transformation. However, this table
623
+ is flexible to allow for situations where existing deployed
624
+ certificate infrastructures do not provide adequate
625
+ subjectAltName values for use as tmSecurityNames.
626
+ Certificates may also be mapped to tmSecurityNames using the
627
+ CommonName portion of the Subject field. However, the usage
628
+ of the CommonName field is deprecated and thus this usage is
629
+ NOT RECOMMENDED. Direct mapping from each individual
630
+ certificate fingerprint to a tmSecurityName is also possible
631
+ but requires one entry in the table per tmSecurityName and
632
+ requires more management operations to completely configure a
633
+ device.""",
634
+ }, # table
635
+ "snmpTlstmCertToTSNEntry" : {
636
+ "nodetype" : "row",
637
+ "moduleName" : "SNMP-TLS-TM-MIB",
638
+ "oid" : "1.3.6.1.2.1.198.2.2.1.3.1",
639
+ "create" : "true",
640
+ "status" : "current",
641
+ "linkage" : [
642
+ "snmpTlstmCertToTSNID",
643
+ ],
644
+ "description" :
645
+ """A row in the snmpTlstmCertToTSNTable that specifies a mapping
646
+ for an incoming (D)TLS certificate to a tmSecurityName to use
647
+ for a connection.""",
648
+ }, # row
649
+ "snmpTlstmCertToTSNID" : {
650
+ "nodetype" : "column",
651
+ "moduleName" : "SNMP-TLS-TM-MIB",
652
+ "oid" : "1.3.6.1.2.1.198.2.2.1.3.1.1",
653
+ "status" : "current",
654
+ "syntax" : {
655
+ "type" : {
656
+ "basetype" : "Unsigned32",
657
+ "ranges" : [
658
+ {
659
+ "min" : "1",
660
+ "max" : "4294967295"
661
+ },
662
+ ],
663
+ "range" : {
664
+ "min" : "1",
665
+ "max" : "4294967295"
666
+ },
667
+ },
668
+ },
669
+ "access" : "noaccess",
670
+ "description" :
671
+ """A unique, prioritized index for the given entry. Lower
672
+ numbers indicate a higher priority.""",
673
+ }, # column
674
+ "snmpTlstmCertToTSNFingerprint" : {
675
+ "nodetype" : "column",
676
+ "moduleName" : "SNMP-TLS-TM-MIB",
677
+ "oid" : "1.3.6.1.2.1.198.2.2.1.3.1.2",
678
+ "status" : "current",
679
+ "syntax" : {
680
+ "type" : {
681
+ "basetype" : "OctetString",
682
+ "parent module" : {
683
+ "name" : "SNMP-TLS-TM-MIB",
684
+ "type" : "SnmpTLSFingerprint",
685
+ },
686
+ "ranges" : [
687
+ {
688
+ "min" : "1",
689
+ "max" : "255"
690
+ },
691
+ ],
692
+ "range" : {
693
+ "min" : "1",
694
+ "max" : "255"
695
+ },
696
+ },
697
+ },
698
+ "access" : "readwrite",
699
+ "description" :
700
+ """A cryptographic hash of a X.509 certificate. The results of
701
+ a successful matching fingerprint to either the trusted CA in
702
+ the certificate validation path or to the certificate itself
703
+ is dictated by the snmpTlstmCertToTSNMapType column.""",
704
+ }, # column
705
+ "snmpTlstmCertToTSNMapType" : {
706
+ "nodetype" : "column",
707
+ "moduleName" : "SNMP-TLS-TM-MIB",
708
+ "oid" : "1.3.6.1.2.1.198.2.2.1.3.1.3",
709
+ "status" : "current",
710
+ "syntax" : {
711
+ "type" : { "module" :"SNMPv2-TC", "name" : "AutonomousType"},
712
+ },
713
+ "access" : "readwrite",
714
+ "default" : "1.3.6.1.2.1.198.1.1.1",
715
+ "description" :
716
+ """Specifies the mapping type for deriving a tmSecurityName from
717
+ a certificate. Details for mapping of a particular type SHALL
718
+ be specified in the DESCRIPTION clause of the OBJECT-IDENTITY
719
+ that describes the mapping. If a mapping succeeds it will
720
+ return a tmSecurityName for use by the TLSTM model and
721
+ processing stops.
722
+
723
+ If the resulting mapped value is not compatible with the
724
+ needed requirements of a tmSecurityName (e.g., VACM imposes a
725
+ 32-octet-maximum length and the certificate derived
726
+
727
+
728
+
729
+
730
+ securityName could be longer), then future rows MUST be
731
+ searched for additional snmpTlstmCertToTSNFingerprint matches
732
+ to look for a mapping that succeeds.
733
+
734
+ Suitable values for assigning to this object that are defined
735
+ within the SNMP-TLS-TM-MIB can be found in the
736
+ snmpTlstmCertToTSNMIdentities portion of the MIB tree.""",
737
+ }, # column
738
+ "snmpTlstmCertToTSNData" : {
739
+ "nodetype" : "column",
740
+ "moduleName" : "SNMP-TLS-TM-MIB",
741
+ "oid" : "1.3.6.1.2.1.198.2.2.1.3.1.4",
742
+ "status" : "current",
743
+ "syntax" : {
744
+ "type" : {
745
+ "basetype" : "OctetString",
746
+ "ranges" : [
747
+ {
748
+ "min" : "0",
749
+ "max" : "1024"
750
+ },
751
+ ],
752
+ "range" : {
753
+ "min" : "0",
754
+ "max" : "1024"
755
+ },
756
+ },
757
+ },
758
+ "access" : "readwrite",
759
+ "default" : "",
760
+ "description" :
761
+ """Auxiliary data used as optional configuration information for
762
+ a given mapping specified by the snmpTlstmCertToTSNMapType
763
+ column. Only some mapping systems will make use of this
764
+ column. The value in this column MUST be ignored for any
765
+ mapping type that does not require data present in this
766
+ column.""",
767
+ }, # column
768
+ "snmpTlstmCertToTSNStorageType" : {
769
+ "nodetype" : "column",
770
+ "moduleName" : "SNMP-TLS-TM-MIB",
771
+ "oid" : "1.3.6.1.2.1.198.2.2.1.3.1.5",
772
+ "status" : "current",
773
+ "syntax" : {
774
+ "type" : { "module" :"SNMPv2-TC", "name" : "StorageType"},
775
+ },
776
+ "access" : "readwrite",
777
+ "default" : "nonVolatile",
778
+ "description" :
779
+ """The storage type for this conceptual row. Conceptual rows
780
+ having the value 'permanent' need not allow write-access to
781
+ any columnar objects in the row.""",
782
+ }, # column
783
+ "snmpTlstmCertToTSNRowStatus" : {
784
+ "nodetype" : "column",
785
+ "moduleName" : "SNMP-TLS-TM-MIB",
786
+ "oid" : "1.3.6.1.2.1.198.2.2.1.3.1.6",
787
+ "status" : "current",
788
+ "syntax" : {
789
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
790
+ },
791
+ "access" : "readwrite",
792
+ "description" :
793
+ """The status of this conceptual row. This object may be used
794
+ to create or remove rows from this table.
795
+
796
+ To create a row in this table, an administrator must set this
797
+ object to either createAndGo(4) or createAndWait(5).
798
+
799
+
800
+
801
+
802
+
803
+
804
+ Until instances of all corresponding columns are appropriately
805
+ configured, the value of the corresponding instance of the
806
+ snmpTlstmParamsRowStatus column is notReady(3).
807
+
808
+ In particular, a newly created row cannot be made active until
809
+ the corresponding snmpTlstmCertToTSNFingerprint,
810
+ snmpTlstmCertToTSNMapType, and snmpTlstmCertToTSNData columns
811
+ have been set.
812
+
813
+ The following objects may not be modified while the
814
+ value of this object is active(1):
815
+ - snmpTlstmCertToTSNFingerprint
816
+ - snmpTlstmCertToTSNMapType
817
+ - snmpTlstmCertToTSNData
818
+ An attempt to set these objects while the value of
819
+ snmpTlstmParamsRowStatus is active(1) will result in
820
+ an inconsistentValue error.""",
821
+ }, # column
822
+ "snmpTlstmParamsCount" : {
823
+ "nodetype" : "scalar",
824
+ "moduleName" : "SNMP-TLS-TM-MIB",
825
+ "oid" : "1.3.6.1.2.1.198.2.2.1.4",
826
+ "status" : "current",
827
+ "syntax" : {
828
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Gauge32"},
829
+ },
830
+ "access" : "readonly",
831
+ "description" :
832
+ """A count of the number of entries in the snmpTlstmParamsTable.""",
833
+ }, # scalar
834
+ "snmpTlstmParamsTableLastChanged" : {
835
+ "nodetype" : "scalar",
836
+ "moduleName" : "SNMP-TLS-TM-MIB",
837
+ "oid" : "1.3.6.1.2.1.198.2.2.1.5",
838
+ "status" : "current",
839
+ "syntax" : {
840
+ "type" : { "module" :"SNMPv2-TC", "name" : "TimeStamp"},
841
+ },
842
+ "access" : "readonly",
843
+ "description" :
844
+ """The value of sysUpTime.0 when the snmpTlstmParamsTable
845
+ was last modified through any means, or 0 if it has not been
846
+ modified since the command responder was started.""",
847
+ }, # scalar
848
+ "snmpTlstmParamsTable" : {
849
+ "nodetype" : "table",
850
+ "moduleName" : "SNMP-TLS-TM-MIB",
851
+ "oid" : "1.3.6.1.2.1.198.2.2.1.6",
852
+ "status" : "current",
853
+ "description" :
854
+ """This table is used by a (D)TLS client when a (D)TLS
855
+ connection is being set up using an entry in the
856
+ SNMP-TARGET-MIB. It extends the SNMP-TARGET-MIB's
857
+ snmpTargetParamsTable with a fingerprint of a certificate to
858
+ use when establishing such a (D)TLS connection.""",
859
+ }, # table
860
+ "snmpTlstmParamsEntry" : {
861
+ "nodetype" : "row",
862
+ "moduleName" : "SNMP-TLS-TM-MIB",
863
+ "oid" : "1.3.6.1.2.1.198.2.2.1.6.1",
864
+ "create" : "true",
865
+ "status" : "current",
866
+ "implied" : "true",
867
+ "linkage" : [
868
+ "snmpTargetParamsName",
869
+ ],
870
+ "description" :
871
+ """A conceptual row containing a fingerprint hash of a locally
872
+ held certificate for a given snmpTargetParamsEntry. The
873
+ values in this row should be ignored if the connection that
874
+ needs to be established, as indicated by the SNMP-TARGET-MIB
875
+ infrastructure, is not a certificate and (D)TLS based
876
+ connection. The connection SHOULD NOT be established if the
877
+ certificate fingerprint stored in this entry does not point to
878
+ a valid locally held certificate or if it points to an
879
+ unusable certificate (such as might happen when the
880
+ certificate's expiration date has been reached).""",
881
+ }, # row
882
+ "snmpTlstmParamsClientFingerprint" : {
883
+ "nodetype" : "column",
884
+ "moduleName" : "SNMP-TLS-TM-MIB",
885
+ "oid" : "1.3.6.1.2.1.198.2.2.1.6.1.1",
886
+ "status" : "current",
887
+ "syntax" : {
888
+ "type" : { "module" :"SNMP-TLS-TM-MIB", "name" : "SnmpTLSFingerprint"},
889
+ },
890
+ "access" : "readwrite",
891
+ "description" :
892
+ """This object stores the hash of the public portion of a
893
+ locally held X.509 certificate. The X.509 certificate, its
894
+ public key, and the corresponding private key will be used
895
+ when initiating a (D)TLS connection as a (D)TLS client.""",
896
+ }, # column
897
+ "snmpTlstmParamsStorageType" : {
898
+ "nodetype" : "column",
899
+ "moduleName" : "SNMP-TLS-TM-MIB",
900
+ "oid" : "1.3.6.1.2.1.198.2.2.1.6.1.2",
901
+ "status" : "current",
902
+ "syntax" : {
903
+ "type" : { "module" :"SNMPv2-TC", "name" : "StorageType"},
904
+ },
905
+ "access" : "readwrite",
906
+ "default" : "nonVolatile",
907
+ "description" :
908
+ """The storage type for this conceptual row. Conceptual rows
909
+ having the value 'permanent' need not allow write-access to
910
+ any columnar objects in the row.""",
911
+ }, # column
912
+ "snmpTlstmParamsRowStatus" : {
913
+ "nodetype" : "column",
914
+ "moduleName" : "SNMP-TLS-TM-MIB",
915
+ "oid" : "1.3.6.1.2.1.198.2.2.1.6.1.3",
916
+ "status" : "current",
917
+ "syntax" : {
918
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
919
+ },
920
+ "access" : "readwrite",
921
+ "description" :
922
+ """The status of this conceptual row. This object may be used
923
+ to create or remove rows from this table.
924
+
925
+ To create a row in this table, an administrator must set this
926
+ object to either createAndGo(4) or createAndWait(5).
927
+
928
+ Until instances of all corresponding columns are appropriately
929
+ configured, the value of the corresponding instance of the
930
+ snmpTlstmParamsRowStatus column is notReady(3).
931
+
932
+ In particular, a newly created row cannot be made active until
933
+ the corresponding snmpTlstmParamsClientFingerprint column has
934
+ been set.
935
+
936
+ The snmpTlstmParamsClientFingerprint object may not be modified
937
+ while the value of this object is active(1).
938
+
939
+ An attempt to set these objects while the value of
940
+ snmpTlstmParamsRowStatus is active(1) will result in
941
+ an inconsistentValue error.""",
942
+ }, # column
943
+ "snmpTlstmAddrCount" : {
944
+ "nodetype" : "scalar",
945
+ "moduleName" : "SNMP-TLS-TM-MIB",
946
+ "oid" : "1.3.6.1.2.1.198.2.2.1.7",
947
+ "status" : "current",
948
+ "syntax" : {
949
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Gauge32"},
950
+ },
951
+ "access" : "readonly",
952
+ "description" :
953
+ """A count of the number of entries in the snmpTlstmAddrTable.""",
954
+ }, # scalar
955
+ "snmpTlstmAddrTableLastChanged" : {
956
+ "nodetype" : "scalar",
957
+ "moduleName" : "SNMP-TLS-TM-MIB",
958
+ "oid" : "1.3.6.1.2.1.198.2.2.1.8",
959
+ "status" : "current",
960
+ "syntax" : {
961
+ "type" : { "module" :"SNMPv2-TC", "name" : "TimeStamp"},
962
+ },
963
+ "access" : "readonly",
964
+ "description" :
965
+ """The value of sysUpTime.0 when the snmpTlstmAddrTable
966
+ was last modified through any means, or 0 if it has not been
967
+ modified since the command responder was started.""",
968
+ }, # scalar
969
+ "snmpTlstmAddrTable" : {
970
+ "nodetype" : "table",
971
+ "moduleName" : "SNMP-TLS-TM-MIB",
972
+ "oid" : "1.3.6.1.2.1.198.2.2.1.9",
973
+ "status" : "current",
974
+ "description" :
975
+ """This table is used by a (D)TLS client when a (D)TLS
976
+ connection is being set up using an entry in the
977
+ SNMP-TARGET-MIB. It extends the SNMP-TARGET-MIB's
978
+ snmpTargetAddrTable so that the client can verify that the
979
+ correct server has been reached. This verification can use
980
+ either a certificate fingerprint, or an identity
981
+ authenticated via certification path validation.
982
+
983
+ If there is an active row in this table corresponding to the
984
+ entry in the SNMP-TARGET-MIB that was used to establish the
985
+ connection, and the row's snmpTlstmAddrServerFingerprint
986
+ column has non-empty value, then the server's presented
987
+ certificate is compared with the
988
+ snmpTlstmAddrServerFingerprint value (and the
989
+ snmpTlstmAddrServerIdentity column is ignored). If the
990
+ fingerprint matches, the verification has succeeded. If the
991
+ fingerprint does not match, then the connection MUST be
992
+ closed.
993
+
994
+ If the server's presented certificate has passed
995
+ certification path validation [RFC5280] to a configured
996
+ trust anchor, and an active row exists with a zero-length
997
+ snmpTlstmAddrServerFingerprint value, then the
998
+ snmpTlstmAddrServerIdentity column contains the expected
999
+ host name. This expected host name is then compared against
1000
+ the server's certificate as follows:
1001
+
1002
+ - Implementations MUST support matching the expected host
1003
+ name against a dNSName in the subjectAltName extension
1004
+ field and MAY support checking the name against the
1005
+ CommonName portion of the subject distinguished name.
1006
+
1007
+
1008
+
1009
+
1010
+
1011
+ - The '*' (ASCII 0x2a) wildcard character is allowed in the
1012
+ dNSName of the subjectAltName extension (and in common
1013
+ name, if used to store the host name), but only as the
1014
+ left-most (least significant) DNS label in that value.
1015
+ This wildcard matches any left-most DNS label in the
1016
+ server name. That is, the subject *.example.com matches
1017
+ the server names a.example.com and b.example.com, but does
1018
+ not match example.com or a.b.example.com. Implementations
1019
+ MUST support wildcards in certificates as specified above,
1020
+ but MAY provide a configuration option to disable them.
1021
+
1022
+ - If the locally configured name is an internationalized
1023
+ domain name, conforming implementations MUST convert it to
1024
+ the ASCII Compatible Encoding (ACE) format for performing
1025
+ comparisons, as specified in Section 7 of [RFC5280].
1026
+
1027
+ If the expected host name fails these conditions then the
1028
+ connection MUST be closed.
1029
+
1030
+ If there is no row in this table corresponding to the entry
1031
+ in the SNMP-TARGET-MIB and the server can be authorized by
1032
+ another, implementation-dependent means, then the connection
1033
+ MAY still proceed.""",
1034
+ }, # table
1035
+ "snmpTlstmAddrEntry" : {
1036
+ "nodetype" : "row",
1037
+ "moduleName" : "SNMP-TLS-TM-MIB",
1038
+ "oid" : "1.3.6.1.2.1.198.2.2.1.9.1",
1039
+ "create" : "true",
1040
+ "status" : "current",
1041
+ "implied" : "true",
1042
+ "linkage" : [
1043
+ "snmpTargetAddrName",
1044
+ ],
1045
+ "description" :
1046
+ """A conceptual row containing a copy of a certificate's
1047
+ fingerprint for a given snmpTargetAddrEntry. The values in
1048
+ this row should be ignored if the connection that needs to be
1049
+ established, as indicated by the SNMP-TARGET-MIB
1050
+ infrastructure, is not a (D)TLS based connection. If an
1051
+ snmpTlstmAddrEntry exists for a given snmpTargetAddrEntry, then
1052
+ the presented server certificate MUST match or the connection
1053
+ MUST NOT be established. If a row in this table does not
1054
+ exist to match an snmpTargetAddrEntry row, then the connection
1055
+ SHOULD still proceed if some other certificate validation path
1056
+ algorithm (e.g., RFC 5280) can be used.""",
1057
+ }, # row
1058
+ "snmpTlstmAddrServerFingerprint" : {
1059
+ "nodetype" : "column",
1060
+ "moduleName" : "SNMP-TLS-TM-MIB",
1061
+ "oid" : "1.3.6.1.2.1.198.2.2.1.9.1.1",
1062
+ "status" : "current",
1063
+ "syntax" : {
1064
+ "type" : { "module" :"SNMP-TLS-TM-MIB", "name" : "SnmpTLSFingerprint"},
1065
+ },
1066
+ "access" : "readwrite",
1067
+ "default" : "",
1068
+ "description" :
1069
+ """A cryptographic hash of a public X.509 certificate. This
1070
+ object should store the hash of the public X.509 certificate
1071
+ that the remote server should present during the (D)TLS
1072
+ connection setup. The fingerprint of the presented
1073
+ certificate and this hash value MUST match exactly or the
1074
+ connection MUST NOT be established.""",
1075
+ }, # column
1076
+ "snmpTlstmAddrServerIdentity" : {
1077
+ "nodetype" : "column",
1078
+ "moduleName" : "SNMP-TLS-TM-MIB",
1079
+ "oid" : "1.3.6.1.2.1.198.2.2.1.9.1.2",
1080
+ "status" : "current",
1081
+ "syntax" : {
1082
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
1083
+ },
1084
+ "access" : "readwrite",
1085
+ "default" : "",
1086
+ "description" :
1087
+ """The reference identity to check against the identity
1088
+ presented by the remote system.""",
1089
+ }, # column
1090
+ "snmpTlstmAddrStorageType" : {
1091
+ "nodetype" : "column",
1092
+ "moduleName" : "SNMP-TLS-TM-MIB",
1093
+ "oid" : "1.3.6.1.2.1.198.2.2.1.9.1.3",
1094
+ "status" : "current",
1095
+ "syntax" : {
1096
+ "type" : { "module" :"SNMPv2-TC", "name" : "StorageType"},
1097
+ },
1098
+ "access" : "readwrite",
1099
+ "default" : "nonVolatile",
1100
+ "description" :
1101
+ """The storage type for this conceptual row. Conceptual rows
1102
+ having the value 'permanent' need not allow write-access to
1103
+ any columnar objects in the row.""",
1104
+ }, # column
1105
+ "snmpTlstmAddrRowStatus" : {
1106
+ "nodetype" : "column",
1107
+ "moduleName" : "SNMP-TLS-TM-MIB",
1108
+ "oid" : "1.3.6.1.2.1.198.2.2.1.9.1.4",
1109
+ "status" : "current",
1110
+ "syntax" : {
1111
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
1112
+ },
1113
+ "access" : "readwrite",
1114
+ "description" :
1115
+ """The status of this conceptual row. This object may be used
1116
+ to create or remove rows from this table.
1117
+
1118
+ To create a row in this table, an administrator must set this
1119
+ object to either createAndGo(4) or createAndWait(5).
1120
+
1121
+ Until instances of all corresponding columns are
1122
+ appropriately configured, the value of the
1123
+ corresponding instance of the snmpTlstmAddrRowStatus
1124
+ column is notReady(3).
1125
+
1126
+ In particular, a newly created row cannot be made active until
1127
+ the corresponding snmpTlstmAddrServerFingerprint column has been
1128
+ set.
1129
+
1130
+ Rows MUST NOT be active if the snmpTlstmAddrServerFingerprint
1131
+ column is blank and the snmpTlstmAddrServerIdentity is set to
1132
+ '*' since this would insecurely accept any presented
1133
+ certificate.
1134
+
1135
+ The snmpTlstmAddrServerFingerprint object may not be modified
1136
+ while the value of this object is active(1).
1137
+
1138
+ An attempt to set these objects while the value of
1139
+ snmpTlstmAddrRowStatus is active(1) will result in
1140
+ an inconsistentValue error.""",
1141
+ }, # column
1142
+ "snmpTlstmConformance" : {
1143
+ "nodetype" : "node",
1144
+ "moduleName" : "SNMP-TLS-TM-MIB",
1145
+ "oid" : "1.3.6.1.2.1.198.3",
1146
+ }, # node
1147
+ "snmpTlstmCompliances" : {
1148
+ "nodetype" : "node",
1149
+ "moduleName" : "SNMP-TLS-TM-MIB",
1150
+ "oid" : "1.3.6.1.2.1.198.3.1",
1151
+ }, # node
1152
+ "snmpTlstmGroups" : {
1153
+ "nodetype" : "node",
1154
+ "moduleName" : "SNMP-TLS-TM-MIB",
1155
+ "oid" : "1.3.6.1.2.1.198.3.2",
1156
+ }, # node
1157
+ "snmpTLSTCPDomain" : {
1158
+ "nodetype" : "node",
1159
+ "moduleName" : "SNMP-TLS-TM-MIB",
1160
+ "oid" : "1.3.6.1.6.1.8",
1161
+ "status" : "current",
1162
+ "description" :
1163
+ """The SNMP over TLS via TCP transport domain. The
1164
+ corresponding transport address is of type SnmpTLSAddress.
1165
+
1166
+ The securityName prefix to be associated with the
1167
+ snmpTLSTCPDomain is 'tls'. This prefix may be used by
1168
+ security models or other components to identify which secure
1169
+ transport infrastructure authenticated a securityName.""",
1170
+ "reference" :
1171
+ """RFC 2579: Textual Conventions for SMIv2""",
1172
+ }, # node
1173
+ "snmpDTLSUDPDomain" : {
1174
+ "nodetype" : "node",
1175
+ "moduleName" : "SNMP-TLS-TM-MIB",
1176
+ "oid" : "1.3.6.1.6.1.9",
1177
+ "status" : "current",
1178
+ "description" :
1179
+ """The SNMP over DTLS via UDP transport domain. The
1180
+ corresponding transport address is of type SnmpTLSAddress.
1181
+
1182
+ The securityName prefix to be associated with the
1183
+ snmpDTLSUDPDomain is 'dtls'. This prefix may be used by
1184
+ security models or other components to identify which secure
1185
+ transport infrastructure authenticated a securityName.""",
1186
+ "reference" :
1187
+ """RFC 2579: Textual Conventions for SMIv2""",
1188
+ }, # node
1189
+ }, # nodes
1190
+
1191
+ "notifications" : {
1192
+ "snmpTlstmServerCertificateUnknown" : {
1193
+ "nodetype" : "notification",
1194
+ "moduleName" : "SNMP-TLS-TM-MIB",
1195
+ "oid" : "1.3.6.1.2.1.198.0.1",
1196
+ "status" : "current",
1197
+ "objects" : {
1198
+ "snmpTlstmSessionUnknownServerCertificate" : {
1199
+ "nodetype" : "object",
1200
+ "module" : "SNMP-TLS-TM-MIB"
1201
+ },
1202
+ },
1203
+ "description" :
1204
+ """Notification that the server certificate presented by an SNMP
1205
+ over (D)TLS server was invalid because no configured
1206
+ fingerprint or CA was acceptable to validate it. This may be
1207
+ because there was no entry in the snmpTlstmAddrTable or
1208
+ because no path could be found to known Certification
1209
+ Authority.
1210
+
1211
+
1212
+
1213
+
1214
+
1215
+
1216
+
1217
+ To avoid notification loops, this notification MUST NOT be
1218
+ sent to servers that themselves have triggered the
1219
+ notification.""",
1220
+ }, # notification
1221
+ "snmpTlstmServerInvalidCertificate" : {
1222
+ "nodetype" : "notification",
1223
+ "moduleName" : "SNMP-TLS-TM-MIB",
1224
+ "oid" : "1.3.6.1.2.1.198.0.2",
1225
+ "status" : "current",
1226
+ "objects" : {
1227
+ "snmpTlstmAddrServerFingerprint" : {
1228
+ "nodetype" : "object",
1229
+ "module" : "SNMP-TLS-TM-MIB"
1230
+ },
1231
+ "snmpTlstmSessionInvalidServerCertificates" : {
1232
+ "nodetype" : "object",
1233
+ "module" : "SNMP-TLS-TM-MIB"
1234
+ },
1235
+ },
1236
+ "description" :
1237
+ """Notification that the server certificate presented by an SNMP
1238
+ over (D)TLS server could not be validated even if the
1239
+ fingerprint or expected validation path was known. That is, a
1240
+ cryptographic validation error occurred during certificate
1241
+ validation processing.
1242
+
1243
+ To avoid notification loops, this notification MUST NOT be
1244
+ sent to servers that themselves have triggered the
1245
+ notification.""",
1246
+ }, # notification
1247
+ }, # notifications
1248
+
1249
+ "groups" : {
1250
+ "snmpTlstmStatsGroup" : {
1251
+ "nodetype" : "group",
1252
+ "moduleName" : "SNMP-TLS-TM-MIB",
1253
+ "oid" : "1.3.6.1.2.1.198.3.2.1",
1254
+ "status" : "current",
1255
+ "members" : {
1256
+ "snmpTlstmSessionOpens" : {
1257
+ "nodetype" : "member",
1258
+ "module" : "SNMP-TLS-TM-MIB"
1259
+ },
1260
+ "snmpTlstmSessionClientCloses" : {
1261
+ "nodetype" : "member",
1262
+ "module" : "SNMP-TLS-TM-MIB"
1263
+ },
1264
+ "snmpTlstmSessionOpenErrors" : {
1265
+ "nodetype" : "member",
1266
+ "module" : "SNMP-TLS-TM-MIB"
1267
+ },
1268
+ "snmpTlstmSessionAccepts" : {
1269
+ "nodetype" : "member",
1270
+ "module" : "SNMP-TLS-TM-MIB"
1271
+ },
1272
+ "snmpTlstmSessionServerCloses" : {
1273
+ "nodetype" : "member",
1274
+ "module" : "SNMP-TLS-TM-MIB"
1275
+ },
1276
+ "snmpTlstmSessionNoSessions" : {
1277
+ "nodetype" : "member",
1278
+ "module" : "SNMP-TLS-TM-MIB"
1279
+ },
1280
+ "snmpTlstmSessionInvalidClientCertificates" : {
1281
+ "nodetype" : "member",
1282
+ "module" : "SNMP-TLS-TM-MIB"
1283
+ },
1284
+ "snmpTlstmSessionUnknownServerCertificate" : {
1285
+ "nodetype" : "member",
1286
+ "module" : "SNMP-TLS-TM-MIB"
1287
+ },
1288
+ "snmpTlstmSessionInvalidServerCertificates" : {
1289
+ "nodetype" : "member",
1290
+ "module" : "SNMP-TLS-TM-MIB"
1291
+ },
1292
+ "snmpTlstmSessionInvalidCaches" : {
1293
+ "nodetype" : "member",
1294
+ "module" : "SNMP-TLS-TM-MIB"
1295
+ },
1296
+ }, # members
1297
+ "description" :
1298
+ """A collection of objects for maintaining
1299
+ statistical information of an SNMP engine that
1300
+ implements the SNMP TLS Transport Model.""",
1301
+ }, # group
1302
+ "snmpTlstmIncomingGroup" : {
1303
+ "nodetype" : "group",
1304
+ "moduleName" : "SNMP-TLS-TM-MIB",
1305
+ "oid" : "1.3.6.1.2.1.198.3.2.2",
1306
+ "status" : "current",
1307
+ "members" : {
1308
+ "snmpTlstmCertToTSNCount" : {
1309
+ "nodetype" : "member",
1310
+ "module" : "SNMP-TLS-TM-MIB"
1311
+ },
1312
+ "snmpTlstmCertToTSNTableLastChanged" : {
1313
+ "nodetype" : "member",
1314
+ "module" : "SNMP-TLS-TM-MIB"
1315
+ },
1316
+ "snmpTlstmCertToTSNFingerprint" : {
1317
+ "nodetype" : "member",
1318
+ "module" : "SNMP-TLS-TM-MIB"
1319
+ },
1320
+ "snmpTlstmCertToTSNMapType" : {
1321
+ "nodetype" : "member",
1322
+ "module" : "SNMP-TLS-TM-MIB"
1323
+ },
1324
+ "snmpTlstmCertToTSNData" : {
1325
+ "nodetype" : "member",
1326
+ "module" : "SNMP-TLS-TM-MIB"
1327
+ },
1328
+ "snmpTlstmCertToTSNStorageType" : {
1329
+ "nodetype" : "member",
1330
+ "module" : "SNMP-TLS-TM-MIB"
1331
+ },
1332
+ "snmpTlstmCertToTSNRowStatus" : {
1333
+ "nodetype" : "member",
1334
+ "module" : "SNMP-TLS-TM-MIB"
1335
+ },
1336
+ }, # members
1337
+ "description" :
1338
+ """A collection of objects for maintaining
1339
+ incoming connection certificate mappings to
1340
+ tmSecurityNames of an SNMP engine that implements the
1341
+ SNMP TLS Transport Model.""",
1342
+ }, # group
1343
+ "snmpTlstmOutgoingGroup" : {
1344
+ "nodetype" : "group",
1345
+ "moduleName" : "SNMP-TLS-TM-MIB",
1346
+ "oid" : "1.3.6.1.2.1.198.3.2.3",
1347
+ "status" : "current",
1348
+ "members" : {
1349
+ "snmpTlstmParamsCount" : {
1350
+ "nodetype" : "member",
1351
+ "module" : "SNMP-TLS-TM-MIB"
1352
+ },
1353
+ "snmpTlstmParamsTableLastChanged" : {
1354
+ "nodetype" : "member",
1355
+ "module" : "SNMP-TLS-TM-MIB"
1356
+ },
1357
+ "snmpTlstmParamsClientFingerprint" : {
1358
+ "nodetype" : "member",
1359
+ "module" : "SNMP-TLS-TM-MIB"
1360
+ },
1361
+ "snmpTlstmParamsStorageType" : {
1362
+ "nodetype" : "member",
1363
+ "module" : "SNMP-TLS-TM-MIB"
1364
+ },
1365
+ "snmpTlstmParamsRowStatus" : {
1366
+ "nodetype" : "member",
1367
+ "module" : "SNMP-TLS-TM-MIB"
1368
+ },
1369
+ "snmpTlstmAddrCount" : {
1370
+ "nodetype" : "member",
1371
+ "module" : "SNMP-TLS-TM-MIB"
1372
+ },
1373
+ "snmpTlstmAddrTableLastChanged" : {
1374
+ "nodetype" : "member",
1375
+ "module" : "SNMP-TLS-TM-MIB"
1376
+ },
1377
+ "snmpTlstmAddrServerFingerprint" : {
1378
+ "nodetype" : "member",
1379
+ "module" : "SNMP-TLS-TM-MIB"
1380
+ },
1381
+ "snmpTlstmAddrServerIdentity" : {
1382
+ "nodetype" : "member",
1383
+ "module" : "SNMP-TLS-TM-MIB"
1384
+ },
1385
+ "snmpTlstmAddrStorageType" : {
1386
+ "nodetype" : "member",
1387
+ "module" : "SNMP-TLS-TM-MIB"
1388
+ },
1389
+ "snmpTlstmAddrRowStatus" : {
1390
+ "nodetype" : "member",
1391
+ "module" : "SNMP-TLS-TM-MIB"
1392
+ },
1393
+ }, # members
1394
+ "description" :
1395
+ """A collection of objects for maintaining
1396
+ outgoing connection certificates to use when opening
1397
+ connections as a result of SNMP-TARGET-MIB settings.""",
1398
+ }, # group
1399
+ "snmpTlstmNotificationGroup" : {
1400
+ "nodetype" : "group",
1401
+ "moduleName" : "SNMP-TLS-TM-MIB",
1402
+ "oid" : "1.3.6.1.2.1.198.3.2.4",
1403
+ "status" : "current",
1404
+ "members" : {
1405
+ "snmpTlstmServerCertificateUnknown" : {
1406
+ "nodetype" : "member",
1407
+ "module" : "SNMP-TLS-TM-MIB"
1408
+ },
1409
+ "snmpTlstmServerInvalidCertificate" : {
1410
+ "nodetype" : "member",
1411
+ "module" : "SNMP-TLS-TM-MIB"
1412
+ },
1413
+ }, # members
1414
+ "description" :
1415
+ """Notifications""",
1416
+ }, # group
1417
+ }, # groups
1418
+
1419
+ "compliances" : {
1420
+ "snmpTlstmCompliance" : {
1421
+ "nodetype" : "compliance",
1422
+ "moduleName" : "SNMP-TLS-TM-MIB",
1423
+ "oid" : "1.3.6.1.2.1.198.3.1.1",
1424
+ "status" : "current",
1425
+ "description" :
1426
+ """The compliance statement for SNMP engines that support the
1427
+ SNMP-TLS-TM-MIB""",
1428
+ "requires" : {
1429
+ "snmpTlstmStatsGroup" : {
1430
+ "nodetype" : "mandatory",
1431
+ "module" : "SNMP-TLS-TM-MIB"
1432
+ },
1433
+ "snmpTlstmIncomingGroup" : {
1434
+ "nodetype" : "mandatory",
1435
+ "module" : "SNMP-TLS-TM-MIB"
1436
+ },
1437
+ "snmpTlstmOutgoingGroup" : {
1438
+ "nodetype" : "mandatory",
1439
+ "module" : "SNMP-TLS-TM-MIB"
1440
+ },
1441
+ "snmpTlstmNotificationGroup" : {
1442
+ "nodetype" : "mandatory",
1443
+ "module" : "SNMP-TLS-TM-MIB"
1444
+ },
1445
+ }, # requires
1446
+ }, # compliance
1447
+ }, # compliances
1448
+
1449
+ }