logstash-input-snmp 0.1.0.beta4 → 0.1.0.beta5

Sign up to get free protection for your applications and to get access to all the features.
Files changed (309) hide show
  1. checksums.yaml +4 -4
  2. data/CHANGELOG.md +5 -0
  3. data/lib/logstash/inputs/snmp.rb +75 -12
  4. data/lib/logstash/inputs/snmp/base_client.rb +162 -0
  5. data/lib/logstash/inputs/snmp/client.rb +11 -109
  6. data/lib/logstash/inputs/snmp/clientv3.rb +139 -0
  7. data/lib/logstash/inputs/snmp/mib.rb +22 -20
  8. data/lib/mibs/ietf/ACCOUNTING-CONTROL-MIB.dic +1316 -0
  9. data/lib/mibs/ietf/ADSL-LINE-EXT-MIB.dic +1724 -0
  10. data/lib/mibs/ietf/ADSL-LINE-MIB.dic +7297 -0
  11. data/lib/mibs/ietf/ADSL-TC-MIB.dic +160 -0
  12. data/lib/mibs/ietf/ADSL2-LINE-MIB.dic +8663 -0
  13. data/lib/mibs/ietf/ADSL2-LINE-TC-MIB.dic +1462 -0
  14. data/lib/mibs/ietf/AGENTX-MIB.dic +817 -0
  15. data/lib/mibs/ietf/AGGREGATE-MIB.dic +708 -0
  16. data/lib/mibs/ietf/ALARM-MIB.dic +1734 -0
  17. data/lib/mibs/ietf/APM-MIB.dic +2870 -0
  18. data/lib/mibs/ietf/APPC-MIB.dic +8687 -0
  19. data/lib/mibs/ietf/APPLETALK-MIB.dic +4399 -0
  20. data/lib/mibs/ietf/APPLICATION-MIB.dic +3750 -0
  21. data/lib/mibs/ietf/APPN-DLUR-MIB.dic +972 -0
  22. data/lib/mibs/ietf/APPN-MIB.dic +9364 -0
  23. data/lib/mibs/ietf/APPN-TRAP-MIB.dic +664 -0
  24. data/lib/mibs/ietf/APS-MIB.dic +2430 -0
  25. data/lib/mibs/ietf/ARC-MIB.dic +552 -0
  26. data/lib/mibs/ietf/ATM-ACCOUNTING-INFORMATION-MIB.dic +816 -0
  27. data/lib/mibs/ietf/ATM-MIB.dic +4104 -0
  28. data/lib/mibs/ietf/ATM-TC-MIB.dic +914 -0
  29. data/lib/mibs/ietf/ATM2-MIB.dic +4715 -0
  30. data/lib/mibs/ietf/BFD-STD-MIB.dic +2367 -0
  31. data/lib/mibs/ietf/BFD-TC-STD-MIB.dic +202 -0
  32. data/lib/mibs/ietf/BGP4-MIB.dic +1931 -0
  33. data/lib/mibs/ietf/BLDG-HVAC-MIB.dic +812 -0
  34. data/lib/mibs/ietf/BRIDGE-MIB.dic +2257 -0
  35. data/lib/mibs/ietf/CAPWAP-BASE-MIB.dic +4128 -0
  36. data/lib/mibs/ietf/CAPWAP-DOT11-MIB.dic +482 -0
  37. data/lib/mibs/ietf/CHARACTER-MIB.dic +1140 -0
  38. data/lib/mibs/ietf/CIRCUIT-IF-MIB.dic +493 -0
  39. data/lib/mibs/ietf/CLNS-MIB.dic +1702 -0
  40. data/lib/mibs/ietf/COFFEE-POT-MIB.dic +282 -0
  41. data/lib/mibs/ietf/COPS-CLIENT-MIB.dic +1270 -0
  42. data/lib/mibs/ietf/DECNET-PHIV-MIB.dic +5837 -0
  43. data/lib/mibs/ietf/DIAL-CONTROL-MIB.dic +2139 -0
  44. data/lib/mibs/ietf/DIFFSERV-CONFIG-MIB.dic +378 -0
  45. data/lib/mibs/ietf/DIFFSERV-MIB.dic +5073 -0
  46. data/lib/mibs/ietf/DIRECTORY-SERVER-MIB.dic +1041 -0
  47. data/lib/mibs/ietf/DISMAN-EVENT-MIB.dic +3151 -0
  48. data/lib/mibs/ietf/DISMAN-EXPRESSION-MIB.dic +1716 -0
  49. data/lib/mibs/ietf/DISMAN-NSLOOKUP-MIB.dic +698 -0
  50. data/lib/mibs/ietf/DISMAN-PING-MIB.dic +2635 -0
  51. data/lib/mibs/ietf/DISMAN-SCHEDULE-MIB.dic +1744 -0
  52. data/lib/mibs/ietf/DISMAN-SCRIPT-MIB.dic +2820 -0
  53. data/lib/mibs/ietf/DISMAN-TRACEROUTE-MIB.dic +3239 -0
  54. data/lib/mibs/ietf/DLSW-MIB.dic +5635 -0
  55. data/lib/mibs/ietf/DNS-RESOLVER-MIB.dic +1765 -0
  56. data/lib/mibs/ietf/DNS-SERVER-MIB.dic +1593 -0
  57. data/lib/mibs/ietf/DOCS-BPI-MIB.dic +2634 -0
  58. data/lib/mibs/ietf/DOCS-CABLE-DEVICE-MIB.dic +5042 -0
  59. data/lib/mibs/ietf/DOCS-IETF-BPI2-MIB.dic +5478 -0
  60. data/lib/mibs/ietf/DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB.dic +2447 -0
  61. data/lib/mibs/ietf/DOCS-IETF-QOS-MIB.dic +4886 -0
  62. data/lib/mibs/ietf/DOCS-IETF-SUBMGT-MIB.dic +1331 -0
  63. data/lib/mibs/ietf/DOCS-IF-MIB.dic +7980 -0
  64. data/lib/mibs/ietf/DOT12-IF-MIB.dic +1066 -0
  65. data/lib/mibs/ietf/DOT12-RPTR-MIB.dic +2669 -0
  66. data/lib/mibs/ietf/DOT3-EPON-MIB.dic +3297 -0
  67. data/lib/mibs/ietf/DOT3-OAM-MIB.dic +2830 -0
  68. data/lib/mibs/ietf/DS0-MIB.dic +466 -0
  69. data/lib/mibs/ietf/DS0BUNDLE-MIB.dic +468 -0
  70. data/lib/mibs/ietf/DS1-MIB.dic +4890 -0
  71. data/lib/mibs/ietf/DS3-MIB.dic +2719 -0
  72. data/lib/mibs/ietf/DSA-MIB.dic +888 -0
  73. data/lib/mibs/ietf/DSMON-MIB.dic +6177 -0
  74. data/lib/mibs/ietf/DVB-RCS-MIB.dic +5764 -0
  75. data/lib/mibs/ietf/EBN-MIB.dic +1026 -0
  76. data/lib/mibs/ietf/EFM-CU-MIB.dic +4335 -0
  77. data/lib/mibs/ietf/ENTITY-MIB.dic +2235 -0
  78. data/lib/mibs/ietf/ENTITY-SENSOR-MIB.dic +653 -0
  79. data/lib/mibs/ietf/ENTITY-STATE-MIB.dic +457 -0
  80. data/lib/mibs/ietf/ENTITY-STATE-TC-MIB.dic +260 -0
  81. data/lib/mibs/ietf/ETHER-CHIPSET-MIB.dic +787 -0
  82. data/lib/mibs/ietf/EtherLike-MIB.dic +2548 -0
  83. data/lib/mibs/ietf/FC-MGMT-MIB.dic +3465 -0
  84. data/lib/mibs/ietf/FCIP-MGMT-MIB.dic +1596 -0
  85. data/lib/mibs/ietf/FDDI-SMT73-MIB.dic +3378 -0
  86. data/lib/mibs/ietf/FIBRE-CHANNEL-FE-MIB.dic +2504 -0
  87. data/lib/mibs/ietf/FLOAT-TC-MIB.dic +128 -0
  88. data/lib/mibs/ietf/FLOW-METER-MIB.dic +3201 -0
  89. data/lib/mibs/ietf/FORCES-MIB.dic +598 -0
  90. data/lib/mibs/ietf/FR-ATM-PVC-SERVICE-IWF-MIB.dic +1601 -0
  91. data/lib/mibs/ietf/FR-MFR-MIB.dic +1351 -0
  92. data/lib/mibs/ietf/FRAME-RELAY-DTE-MIB.dic +1688 -0
  93. data/lib/mibs/ietf/FRNETSERV-MIB.dic +3940 -0
  94. data/lib/mibs/ietf/FRSLD-MIB.dic +2580 -0
  95. data/lib/mibs/ietf/Finisher-MIB.dic +1416 -0
  96. data/lib/mibs/ietf/GMPLS-LABEL-STD-MIB.dic +965 -0
  97. data/lib/mibs/ietf/GMPLS-LSR-STD-MIB.dic +693 -0
  98. data/lib/mibs/ietf/GMPLS-TC-STD-MIB.dic +180 -0
  99. data/lib/mibs/ietf/GMPLS-TE-STD-MIB.dic +2542 -0
  100. data/lib/mibs/ietf/GSMP-MIB.dic +2468 -0
  101. data/lib/mibs/ietf/HC-ALARM-MIB.dic +1050 -0
  102. data/lib/mibs/ietf/HC-PerfHist-TC-MIB.dic +310 -0
  103. data/lib/mibs/ietf/HC-RMON-MIB.dic +4456 -0
  104. data/lib/mibs/ietf/HDSL2-SHDSL-LINE-MIB.dic +3955 -0
  105. data/lib/mibs/ietf/HOST-RESOURCES-MIB.dic +2453 -0
  106. data/lib/mibs/ietf/HPR-IP-MIB.dic +640 -0
  107. data/lib/mibs/ietf/HPR-MIB.dic +1959 -0
  108. data/lib/mibs/ietf/IANA-ITU-ALARM-TC-MIB.dic +936 -0
  109. data/lib/mibs/ietf/IF-CAP-STACK-MIB.dic +356 -0
  110. data/lib/mibs/ietf/IF-INVERTED-STACK-MIB.dic +220 -0
  111. data/lib/mibs/ietf/IF-MIB.dic +2753 -0
  112. data/lib/mibs/ietf/IFCP-MGMT-MIB.dic +1717 -0
  113. data/lib/mibs/ietf/IGMP-STD-MIB.dic +809 -0
  114. data/lib/mibs/ietf/INET-ADDRESS-MIB.dic +570 -0
  115. data/lib/mibs/ietf/INTEGRATED-SERVICES-GUARANTEED-MIB.dic +319 -0
  116. data/lib/mibs/ietf/INTEGRATED-SERVICES-MIB.dic +1196 -0
  117. data/lib/mibs/ietf/INTERFACETOPN-MIB.dic +1705 -0
  118. data/lib/mibs/ietf/IP-FORWARD-MIB.dic +1853 -0
  119. data/lib/mibs/ietf/IP-MIB.dic +7064 -0
  120. data/lib/mibs/ietf/IPATM-IPMC-MIB.dic +4830 -0
  121. data/lib/mibs/ietf/IPFIX-MIB.dic +2334 -0
  122. data/lib/mibs/ietf/IPFIX-SELECTOR-MIB.dic +215 -0
  123. data/lib/mibs/ietf/IPMCAST-MIB.dic +3390 -0
  124. data/lib/mibs/ietf/IPMROUTE-STD-MIB.dic +1246 -0
  125. data/lib/mibs/ietf/IPOA-MIB.dic +2372 -0
  126. data/lib/mibs/ietf/IPS-AUTH-MIB.dic +1609 -0
  127. data/lib/mibs/ietf/IPSEC-SPD-MIB.dic +3989 -0
  128. data/lib/mibs/ietf/IPV6-FLOW-LABEL-MIB.dic +110 -0
  129. data/lib/mibs/ietf/IPV6-ICMP-MIB.dic +748 -0
  130. data/lib/mibs/ietf/IPV6-MIB.dic +2028 -0
  131. data/lib/mibs/ietf/IPV6-MLD-MIB.dic +659 -0
  132. data/lib/mibs/ietf/IPV6-TCP-MIB.dic +332 -0
  133. data/lib/mibs/ietf/IPV6-UDP-MIB.dic +209 -0
  134. data/lib/mibs/ietf/ISCSI-MIB.dic +4613 -0
  135. data/lib/mibs/ietf/ISDN-MIB.dic +1796 -0
  136. data/lib/mibs/ietf/ISIS-MIB.dic +6215 -0
  137. data/lib/mibs/ietf/ISNS-MIB.dic +6578 -0
  138. data/lib/mibs/ietf/ITU-ALARM-MIB.dic +665 -0
  139. data/lib/mibs/ietf/ITU-ALARM-TC-MIB.dic +137 -0
  140. data/lib/mibs/ietf/Job-Monitoring-MIB.dic +2519 -0
  141. data/lib/mibs/ietf/L2TP-MIB.dic +4050 -0
  142. data/lib/mibs/ietf/LANGTAG-TC-MIB.dic +104 -0
  143. data/lib/mibs/ietf/LISP-MIB.dic +4067 -0
  144. data/lib/mibs/ietf/LMP-MIB.dic +5166 -0
  145. data/lib/mibs/ietf/MALLOC-MIB.dic +2156 -0
  146. data/lib/mibs/ietf/MAU-MIB.dic +2619 -0
  147. data/lib/mibs/ietf/MIDCOM-MIB.dic +2856 -0
  148. data/lib/mibs/ietf/MIOX25-MIB.dic +828 -0
  149. data/lib/mibs/ietf/MIP-MIB.dic +3473 -0
  150. data/lib/mibs/ietf/MOBILEIPV6-MIB.dic +5228 -0
  151. data/lib/mibs/ietf/MPLS-FTN-STD-MIB.dic +1594 -0
  152. data/lib/mibs/ietf/MPLS-L3VPN-STD-MIB.dic +2548 -0
  153. data/lib/mibs/ietf/MPLS-LC-ATM-STD-MIB.dic +491 -0
  154. data/lib/mibs/ietf/MPLS-LC-FR-STD-MIB.dic +395 -0
  155. data/lib/mibs/ietf/MPLS-LDP-ATM-STD-MIB.dic +1019 -0
  156. data/lib/mibs/ietf/MPLS-LDP-FRAME-RELAY-STD-MIB.dic +862 -0
  157. data/lib/mibs/ietf/MPLS-LDP-GENERIC-STD-MIB.dic +445 -0
  158. data/lib/mibs/ietf/MPLS-LDP-STD-MIB.dic +3657 -0
  159. data/lib/mibs/ietf/MPLS-LSR-STD-MIB.dic +3103 -0
  160. data/lib/mibs/ietf/MPLS-TC-STD-MIB.dic +911 -0
  161. data/lib/mibs/ietf/MPLS-TE-STD-MIB.dic +3673 -0
  162. data/lib/mibs/ietf/MSDP-MIB.dic +1893 -0
  163. data/lib/mibs/ietf/MTA-MIB.dic +1898 -0
  164. data/lib/mibs/ietf/Modem-MIB.dic +2054 -0
  165. data/lib/mibs/ietf/NAT-MIB.dic +3866 -0
  166. data/lib/mibs/ietf/NETWORK-SERVICES-MIB.dic +1034 -0
  167. data/lib/mibs/ietf/NHDP-MIB.dic +3005 -0
  168. data/lib/mibs/ietf/NHRP-MIB.dic +3660 -0
  169. data/lib/mibs/ietf/NOTIFICATION-LOG-MIB.dic +1156 -0
  170. data/lib/mibs/ietf/NTPv4-MIB.dic +1535 -0
  171. data/lib/mibs/ietf/OPT-IF-MIB.dic +8972 -0
  172. data/lib/mibs/ietf/OSPF-MIB.dic +5963 -0
  173. data/lib/mibs/ietf/OSPF-TRAP-MIB.dic +1190 -0
  174. data/lib/mibs/ietf/OSPFV3-MIB.dic +5708 -0
  175. data/lib/mibs/ietf/P-BRIDGE-MIB.dic +1499 -0
  176. data/lib/mibs/ietf/PARALLEL-MIB.dic +476 -0
  177. data/lib/mibs/ietf/PIM-MIB.dic +1393 -0
  178. data/lib/mibs/ietf/PIM-STD-MIB.dic +6819 -0
  179. data/lib/mibs/ietf/PINT-MIB.dic +830 -0
  180. data/lib/mibs/ietf/PKTC-IETF-MTA-MIB.dic +3191 -0
  181. data/lib/mibs/ietf/PKTC-IETF-SIG-MIB.dic +4713 -0
  182. data/lib/mibs/ietf/PMIPV6-MIB.dic +3010 -0
  183. data/lib/mibs/ietf/PMIPV6-TC-MIB.dic +293 -0
  184. data/lib/mibs/ietf/POLICY-BASED-MANAGEMENT-MIB.dic +3316 -0
  185. data/lib/mibs/ietf/POWER-ETHERNET-MIB.dic +959 -0
  186. data/lib/mibs/ietf/PPP-BRIDGE-NCP-MIB.dic +587 -0
  187. data/lib/mibs/ietf/PPP-IP-NCP-MIB.dic +269 -0
  188. data/lib/mibs/ietf/PPP-LCP-MIB.dic +994 -0
  189. data/lib/mibs/ietf/PPP-SEC-MIB.dic +411 -0
  190. data/lib/mibs/ietf/PSAMP-MIB.dic +998 -0
  191. data/lib/mibs/ietf/PTOPO-MIB.dic +1135 -0
  192. data/lib/mibs/ietf/PW-ATM-MIB.dic +1642 -0
  193. data/lib/mibs/ietf/PW-CEP-STD-MIB.dic +3661 -0
  194. data/lib/mibs/ietf/PW-STD-MIB.dic +3592 -0
  195. data/lib/mibs/ietf/PW-TC-STD-MIB.dic +437 -0
  196. data/lib/mibs/ietf/PW-TDM-MIB.dic +1896 -0
  197. data/lib/mibs/ietf/PerfHist-TC-MIB.dic +152 -0
  198. data/lib/mibs/ietf/Printer-MIB.dic +6665 -0
  199. data/lib/mibs/ietf/Q-BRIDGE-MIB.dic +3115 -0
  200. data/lib/mibs/ietf/RADIUS-ACC-CLIENT-MIB.dic +991 -0
  201. data/lib/mibs/ietf/RADIUS-ACC-SERVER-MIB.dic +1183 -0
  202. data/lib/mibs/ietf/RADIUS-AUTH-CLIENT-MIB.dic +1073 -0
  203. data/lib/mibs/ietf/RADIUS-AUTH-SERVER-MIB.dic +1251 -0
  204. data/lib/mibs/ietf/RADIUS-DYNAUTH-CLIENT-MIB.dic +1116 -0
  205. data/lib/mibs/ietf/RADIUS-DYNAUTH-SERVER-MIB.dic +1003 -0
  206. data/lib/mibs/ietf/RAQMON-MIB.dic +2695 -0
  207. data/lib/mibs/ietf/RBRIDGE-MIB.dic +2981 -0
  208. data/lib/mibs/ietf/RDBMS-MIB.dic +1935 -0
  209. data/lib/mibs/ietf/RFC1065-SMI.dic +108 -0
  210. data/lib/mibs/ietf/RFC1155-SMI.dic +118 -0
  211. data/lib/mibs/ietf/RFC1158-MIB.dic +2440 -0
  212. data/lib/mibs/ietf/RFC1213-MIB.dic +3434 -0
  213. data/lib/mibs/ietf/RFC1269-MIB.dic +557 -0
  214. data/lib/mibs/ietf/RFC1271-MIB.dic +4135 -0
  215. data/lib/mibs/ietf/RFC1285-MIB.dic +2842 -0
  216. data/lib/mibs/ietf/RFC1316-MIB.dic +800 -0
  217. data/lib/mibs/ietf/RFC1381-MIB.dic +1347 -0
  218. data/lib/mibs/ietf/RFC1382-MIB.dic +3820 -0
  219. data/lib/mibs/ietf/RFC1414-MIB.dic +214 -0
  220. data/lib/mibs/ietf/RIPv2-MIB.dic +773 -0
  221. data/lib/mibs/ietf/RMON-MIB.dic +5551 -0
  222. data/lib/mibs/ietf/RMON2-MIB.dic +8224 -0
  223. data/lib/mibs/ietf/ROHC-MIB.dic +1613 -0
  224. data/lib/mibs/ietf/ROHC-RTP-MIB.dic +859 -0
  225. data/lib/mibs/ietf/ROHC-UNCOMPRESSED-MIB.dic +267 -0
  226. data/lib/mibs/ietf/RPKI-ROUTER-MIB.dic +1363 -0
  227. data/lib/mibs/ietf/RS-232-MIB.dic +1335 -0
  228. data/lib/mibs/ietf/RSERPOOL-MIB.dic +2501 -0
  229. data/lib/mibs/ietf/RSTP-MIB.dic +427 -0
  230. data/lib/mibs/ietf/RSVP-MIB.dic +4135 -0
  231. data/lib/mibs/ietf/RTP-MIB.dic +1376 -0
  232. data/lib/mibs/ietf/SCSI-MIB.dic +3804 -0
  233. data/lib/mibs/ietf/SCTP-MIB.dic +1924 -0
  234. data/lib/mibs/ietf/SFLOW-MIB.dic +568 -0
  235. data/lib/mibs/ietf/SIP-COMMON-MIB.dic +2769 -0
  236. data/lib/mibs/ietf/SIP-MIB.dic +1438 -0
  237. data/lib/mibs/ietf/SIP-SERVER-MIB.dic +1150 -0
  238. data/lib/mibs/ietf/SIP-TC-MIB.dic +257 -0
  239. data/lib/mibs/ietf/SIP-UA-MIB.dic +268 -0
  240. data/lib/mibs/ietf/SLAPM-MIB.dic +4527 -0
  241. data/lib/mibs/ietf/SMON-MIB.dic +1758 -0
  242. data/lib/mibs/ietf/SNA-NAU-MIB.dic +4042 -0
  243. data/lib/mibs/ietf/SNA-SDLC-MIB.dic +3858 -0
  244. data/lib/mibs/ietf/SNMP-COMMUNITY-MIB.dic +715 -0
  245. data/lib/mibs/ietf/SNMP-FRAMEWORK-MIB.dic +709 -0
  246. data/lib/mibs/ietf/SNMP-MPD-MIB.dic +230 -0
  247. data/lib/mibs/ietf/SNMP-NOTIFICATION-MIB.dic +859 -0
  248. data/lib/mibs/ietf/SNMP-PROXY-MIB.dic +414 -0
  249. data/lib/mibs/ietf/SNMP-REPEATER-MIB.dic +4335 -0
  250. data/lib/mibs/ietf/SNMP-SSH-TM-MIB.dic +447 -0
  251. data/lib/mibs/ietf/SNMP-TARGET-MIB.dic +924 -0
  252. data/lib/mibs/ietf/SNMP-TLS-TM-MIB.dic +1449 -0
  253. data/lib/mibs/ietf/SNMP-TSM-MIB.dic +315 -0
  254. data/lib/mibs/ietf/SNMP-USER-BASED-SM-MIB.dic +1164 -0
  255. data/lib/mibs/ietf/SNMP-USM-AES-MIB.dic +95 -0
  256. data/lib/mibs/ietf/SNMP-USM-DH-OBJECTS-MIB.dic +653 -0
  257. data/lib/mibs/ietf/SNMP-VIEW-BASED-ACM-MIB.dic +1202 -0
  258. data/lib/mibs/ietf/SNMPv2-MIB.dic +1382 -0
  259. data/lib/mibs/ietf/SNMPv2-SMI.dic +223 -0
  260. data/lib/mibs/ietf/SNMPv2-USEC-MIB.dic +405 -0
  261. data/lib/mibs/ietf/SONET-MIB.dic +3308 -0
  262. data/lib/mibs/ietf/SOURCE-ROUTING-MIB.dic +542 -0
  263. data/lib/mibs/ietf/SSPM-MIB.dic +1530 -0
  264. data/lib/mibs/ietf/SYSAPPL-MIB.dic +2092 -0
  265. data/lib/mibs/ietf/T11-FC-FABRIC-ADDR-MGR-MIB.dic +1779 -0
  266. data/lib/mibs/ietf/T11-FC-FABRIC-CONFIG-SERVER-MIB.dic +2822 -0
  267. data/lib/mibs/ietf/T11-FC-FABRIC-LOCK-MIB.dic +700 -0
  268. data/lib/mibs/ietf/T11-FC-FSPF-MIB.dic +1889 -0
  269. data/lib/mibs/ietf/T11-FC-NAME-SERVER-MIB.dic +1775 -0
  270. data/lib/mibs/ietf/T11-FC-ROUTE-MIB.dic +655 -0
  271. data/lib/mibs/ietf/T11-FC-RSCN-MIB.dic +1110 -0
  272. data/lib/mibs/ietf/T11-FC-VIRTUAL-FABRIC-MIB.dic +770 -0
  273. data/lib/mibs/ietf/T11-FC-ZONE-SERVER-MIB.dic +3886 -0
  274. data/lib/mibs/ietf/T11-TC-MIB.dic +110 -0
  275. data/lib/mibs/ietf/TCP-ESTATS-MIB.dic +3926 -0
  276. data/lib/mibs/ietf/TCP-MIB.dic +1319 -0
  277. data/lib/mibs/ietf/TCPIPX-MIB.dic +457 -0
  278. data/lib/mibs/ietf/TE-LINK-STD-MIB.dic +2876 -0
  279. data/lib/mibs/ietf/TE-MIB.dic +2924 -0
  280. data/lib/mibs/ietf/TED-MIB.dic +1749 -0
  281. data/lib/mibs/ietf/TIME-AGGREGATE-MIB.dic +550 -0
  282. data/lib/mibs/ietf/TN3270E-MIB.dic +2785 -0
  283. data/lib/mibs/ietf/TN3270E-RT-MIB.dic +1317 -0
  284. data/lib/mibs/ietf/TOKEN-RING-RMON-MIB.dic +2820 -0
  285. data/lib/mibs/ietf/TOKENRING-MIB.dic +1184 -0
  286. data/lib/mibs/ietf/TOKENRING-STATION-SR-MIB.dic +292 -0
  287. data/lib/mibs/ietf/TRANSPORT-ADDRESS-MIB.dic +610 -0
  288. data/lib/mibs/ietf/TRIP-MIB.dic +3159 -0
  289. data/lib/mibs/ietf/TRIP-TC-MIB.dic +241 -0
  290. data/lib/mibs/ietf/TUNNEL-MIB.dic +1095 -0
  291. data/lib/mibs/ietf/UDP-MIB.dic +751 -0
  292. data/lib/mibs/ietf/UDPLITE-MIB.dic +704 -0
  293. data/lib/mibs/ietf/UPS-MIB.dic +3088 -0
  294. data/lib/mibs/ietf/URI-TC-MIB.dic +193 -0
  295. data/lib/mibs/ietf/UUID-TC-MIB.dic +135 -0
  296. data/lib/mibs/ietf/VDSL-LINE-EXT-MCM-MIB.dic +989 -0
  297. data/lib/mibs/ietf/VDSL-LINE-EXT-SCM-MIB.dic +605 -0
  298. data/lib/mibs/ietf/VDSL-LINE-MIB.dic +4518 -0
  299. data/lib/mibs/ietf/VDSL2-LINE-MIB.dic +11029 -0
  300. data/lib/mibs/ietf/VDSL2-LINE-TC-MIB.dic +3152 -0
  301. data/lib/mibs/ietf/VPN-TC-STD-MIB.dic +121 -0
  302. data/lib/mibs/ietf/VRRP-MIB.dic +1163 -0
  303. data/lib/mibs/ietf/VRRPV3-MIB.dic +1403 -0
  304. data/lib/mibs/ietf/WWW-MIB.dic +1810 -0
  305. data/lib/mibs/logstash/iso.dic +18 -0
  306. data/logstash-input-snmp.gemspec +1 -1
  307. data/spec/inputs/snmp/mib_spec.rb +10 -17
  308. data/spec/inputs/snmp_spec.rb +27 -1
  309. metadata +302 -2
@@ -0,0 +1,447 @@
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-SSH-TM-MIB
6
+
7
+ FILENAME = "./libsmi-0.5.0/mibs/ietf/SNMP-SSH-TM-MIB"
8
+
9
+ MIB = {
10
+ "moduleName" : "SNMP-SSH-TM-MIB",
11
+
12
+ "SNMP-SSH-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 Quittek
23
+ NEC Europe Ltd.
24
+ Network Laboratories
25
+ Kurfuersten-Anlage 36
26
+ 69115 Heidelberg
27
+ Germany
28
+ +49 6221 90511-15
29
+ quittek@netlab.nec.de
30
+
31
+ Juergen Schoenwaelder
32
+ Jacobs University Bremen
33
+ Campus Ring 1
34
+ 28725 Bremen
35
+ Germany
36
+ +49 421 200-3587
37
+ j.schoenwaelder@jacobs-university.de
38
+
39
+ Co-editors:
40
+ David Harrington
41
+ Huawei Technologies USA
42
+ 1700 Alma Drive
43
+ Plano Texas 75075
44
+
45
+
46
+
47
+ USA
48
+ +1 603-436-8634
49
+ ietfdbh@comcast.net
50
+
51
+ Joseph Salowey
52
+ Cisco Systems
53
+ 2901 3rd Ave
54
+ Seattle, WA 98121
55
+ USA
56
+ jsalowey@cisco.com
57
+
58
+ Wes Hardaker
59
+ Cobham Analytic Solutions
60
+ P.O. Box 382
61
+ Davis, CA 95617
62
+ USA
63
+ +1 530 792 1913
64
+ ietf@hardakers.net""",
65
+ "description" :
66
+ """The Secure Shell Transport Model MIB.
67
+
68
+ Copyright (c) 2009 IETF Trust and the persons
69
+ identified as authors of the code. All rights reserved.
70
+
71
+ Redistribution and use in source and binary forms, with or
72
+ without modification, are permitted provided that the
73
+ following conditions are met:
74
+
75
+ - Redistributions of source code must retain the above copyright
76
+ notice, this list of conditions and the following disclaimer.
77
+
78
+ - Redistributions in binary form must reproduce the above
79
+ copyright notice, this list of conditions and the following
80
+ disclaimer in the documentation and/or other materials
81
+ provided with the distribution.
82
+
83
+ - Neither the name of Internet Society, IETF or IETF Trust,
84
+ nor the names of specific contributors, may be used to endorse
85
+ or promote products derived from this software without
86
+ specific prior written permission.
87
+
88
+ THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
89
+ CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES,
90
+ INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
91
+ MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
92
+ DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
93
+ CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
94
+
95
+
96
+
97
+ SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
98
+ NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
99
+ LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
100
+ HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
101
+ CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
102
+ OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
103
+ EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
104
+
105
+ This version of this MIB module is part of RFC 5592;
106
+ see the RFC itself for full legal notices.""",
107
+ "revisions" : (
108
+ {
109
+ "date" : "2009-06-09 00:00",
110
+ "description" :
111
+ """The initial version, published in RFC 5592.""",
112
+ },
113
+ ),
114
+ "identity node" : "snmpSshtmMIB",
115
+ },
116
+
117
+ "imports" : (
118
+ {"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
119
+ {"module" : "SNMPv2-SMI", "name" : "OBJECT-TYPE"},
120
+ {"module" : "SNMPv2-SMI", "name" : "OBJECT-IDENTITY"},
121
+ {"module" : "SNMPv2-SMI", "name" : "mib-2"},
122
+ {"module" : "SNMPv2-SMI", "name" : "snmpDomains"},
123
+ {"module" : "SNMPv2-SMI", "name" : "Counter32"},
124
+ {"module" : "SNMPv2-TC", "name" : "TEXTUAL-CONVENTION"},
125
+ {"module" : "SNMPv2-CONF", "name" : "MODULE-COMPLIANCE"},
126
+ {"module" : "SNMPv2-CONF", "name" : "OBJECT-GROUP"},
127
+ ),
128
+
129
+ "typedefs" : {
130
+ "SnmpSSHAddress" : {
131
+ "basetype" : "OctetString",
132
+ "status" : "current",
133
+ "ranges" : [
134
+ {
135
+ "min" : "1",
136
+ "max" : "255"
137
+ },
138
+ ],
139
+ "range" : {
140
+ "min" : "1",
141
+ "max" : "255"
142
+ },
143
+ "format" : "1a",
144
+ "description" :
145
+ """Represents either a hostname or IP address, along with a port
146
+ number and an optional user name.
147
+
148
+ The beginning of the address specification may contain a
149
+ user name followed by an '@' (US-ASCII character 0x40). This
150
+ portion of the address will indicate the user name that should
151
+ be used when authenticating to an SSH server. The user name
152
+ must be encoded in UTF-8 (per [RFC4252]). If missing, the
153
+ SNMP securityName should be used. After the optional user
154
+ name field and '@' character comes the hostname or IP
155
+ address.
156
+
157
+ The hostname is always in US-ASCII (as per RFC1033);
158
+ internationalized hostnames are encoded in US-ASCII as
159
+ specified in RFC 3490. The hostname is followed by a colon
160
+ ':' (US-ASCII character 0x3A) and a decimal port number in
161
+ US-ASCII. The name SHOULD be fully qualified whenever
162
+ possible.
163
+
164
+ An IPv4 address must be in dotted decimal format followed
165
+ by a colon ':' (US-ASCII character 0x3A) and a decimal port
166
+ number in US-ASCII.
167
+
168
+ An IPv6 address must be in colon-separated format, surrounded
169
+ by square brackets ('[', US-ASCII character 0x5B, and ']',
170
+ US-ASCII character 0x5D), followed by a colon ':' (US-ASCII
171
+ character 0x3A) and a decimal port number in US-ASCII.
172
+
173
+ Values of this Textual Convention might not be directly usable
174
+ as transport-layer addressing information and may require
175
+ runtime resolution. As such, applications that write them
176
+ must be prepared for handling errors if such values are
177
+ not supported or cannot be resolved (if resolution occurs
178
+ at the time of the management operation).
179
+
180
+ The DESCRIPTION clause of TransportAddress objects that may
181
+ have snmpSSHAddress values must fully describe how (and
182
+ when) such names are to be resolved to IP addresses and vice
183
+ versa.
184
+
185
+ This Textual Convention SHOULD NOT be used directly in
186
+ object definitions since it restricts addresses to a
187
+ specific format. However, if it is used, it MAY be used
188
+ either on its own or in conjunction with
189
+ TransportAddressType or TransportDomain as a pair.
190
+
191
+
192
+
193
+
194
+
195
+ When this Textual Convention is used as a syntax of an
196
+ index object, there may be issues with the limit of 128
197
+ sub-identifiers, which is specified in SMIv2 (STD 58). It
198
+ is RECOMMENDED that all MIB documents using this Textual
199
+ Convention make explicit any limitations on index
200
+ component lengths that management software must observe.
201
+ This may be done either by including SIZE constraints on
202
+ the index components or by specifying applicable
203
+ constraints in the conceptual row DESCRIPTION clause or
204
+ in the surrounding documentation.""",
205
+ "reference" :
206
+ """RFC 1033: DOMAIN ADMINISTRATORS OPERATIONS GUIDE
207
+ RFC 3490: Internationalizing Domain Names in Applications
208
+ RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
209
+ RFC 4252: The Secure Shell (SSH) Authentication Protocol""",
210
+ },
211
+ }, # typedefs
212
+
213
+ "nodes" : {
214
+ "snmpSshtmMIB" : {
215
+ "nodetype" : "node",
216
+ "moduleName" : "SNMP-SSH-TM-MIB",
217
+ "oid" : "1.3.6.1.2.1.189",
218
+ "status" : "current",
219
+ }, # node
220
+ "snmpSshtmNotifications" : {
221
+ "nodetype" : "node",
222
+ "moduleName" : "SNMP-SSH-TM-MIB",
223
+ "oid" : "1.3.6.1.2.1.189.0",
224
+ }, # node
225
+ "snmpSshtmObjects" : {
226
+ "nodetype" : "node",
227
+ "moduleName" : "SNMP-SSH-TM-MIB",
228
+ "oid" : "1.3.6.1.2.1.189.1",
229
+ }, # node
230
+ "snmpSshtmSession" : {
231
+ "nodetype" : "node",
232
+ "moduleName" : "SNMP-SSH-TM-MIB",
233
+ "oid" : "1.3.6.1.2.1.189.1.1",
234
+ }, # node
235
+ "snmpSshtmSessionOpens" : {
236
+ "nodetype" : "scalar",
237
+ "moduleName" : "SNMP-SSH-TM-MIB",
238
+ "oid" : "1.3.6.1.2.1.189.1.1.1",
239
+ "status" : "current",
240
+ "syntax" : {
241
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
242
+ },
243
+ "access" : "readonly",
244
+ "description" :
245
+ """The number of times an openSession() request has been
246
+ executed as an SSH client, whether it succeeded or
247
+ failed.""",
248
+ }, # scalar
249
+ "snmpSshtmSessionCloses" : {
250
+ "nodetype" : "scalar",
251
+ "moduleName" : "SNMP-SSH-TM-MIB",
252
+ "oid" : "1.3.6.1.2.1.189.1.1.2",
253
+ "status" : "current",
254
+ "syntax" : {
255
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
256
+ },
257
+ "access" : "readonly",
258
+ "description" :
259
+ """The number of times a closeSession() request has been
260
+ executed as an SSH client, whether it succeeded or
261
+ failed.""",
262
+ }, # scalar
263
+ "snmpSshtmSessionOpenErrors" : {
264
+ "nodetype" : "scalar",
265
+ "moduleName" : "SNMP-SSH-TM-MIB",
266
+ "oid" : "1.3.6.1.2.1.189.1.1.3",
267
+ "status" : "current",
268
+ "syntax" : {
269
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
270
+ },
271
+ "access" : "readonly",
272
+ "description" :
273
+ """The number of times an openSession() request
274
+ failed to open a transport connection or failed to
275
+ authenticate the server.""",
276
+ }, # scalar
277
+ "snmpSshtmSessionUserAuthFailures" : {
278
+ "nodetype" : "scalar",
279
+ "moduleName" : "SNMP-SSH-TM-MIB",
280
+ "oid" : "1.3.6.1.2.1.189.1.1.4",
281
+ "status" : "current",
282
+ "syntax" : {
283
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
284
+ },
285
+ "access" : "readonly",
286
+ "description" :
287
+ """The number of times an openSession() request
288
+ failed to open a session as an SSH client due to
289
+ user-authentication failures.""",
290
+ }, # scalar
291
+ "snmpSshtmSessionNoChannels" : {
292
+ "nodetype" : "scalar",
293
+ "moduleName" : "SNMP-SSH-TM-MIB",
294
+ "oid" : "1.3.6.1.2.1.189.1.1.5",
295
+ "status" : "current",
296
+ "syntax" : {
297
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
298
+ },
299
+ "access" : "readonly",
300
+ "description" :
301
+ """The number of times an openSession() request
302
+ failed to open a session as an SSH client due to
303
+ channel-open failures.""",
304
+ }, # scalar
305
+ "snmpSshtmSessionNoSubsystems" : {
306
+ "nodetype" : "scalar",
307
+ "moduleName" : "SNMP-SSH-TM-MIB",
308
+ "oid" : "1.3.6.1.2.1.189.1.1.6",
309
+ "status" : "current",
310
+ "syntax" : {
311
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
312
+ },
313
+ "access" : "readonly",
314
+ "description" :
315
+ """The number of times an openSession() request
316
+ failed to open a session as an SSH client due to
317
+ inability to connect to the requested subsystem.""",
318
+ }, # scalar
319
+ "snmpSshtmSessionNoSessions" : {
320
+ "nodetype" : "scalar",
321
+ "moduleName" : "SNMP-SSH-TM-MIB",
322
+ "oid" : "1.3.6.1.2.1.189.1.1.7",
323
+ "status" : "current",
324
+ "syntax" : {
325
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
326
+ },
327
+ "access" : "readonly",
328
+ "description" :
329
+ """The number of times an outgoing message was
330
+ dropped because the same session was no longer
331
+ available.""",
332
+ }, # scalar
333
+ "snmpSshtmSessionInvalidCaches" : {
334
+ "nodetype" : "scalar",
335
+ "moduleName" : "SNMP-SSH-TM-MIB",
336
+ "oid" : "1.3.6.1.2.1.189.1.1.8",
337
+ "status" : "current",
338
+ "syntax" : {
339
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
340
+ },
341
+ "access" : "readonly",
342
+ "description" :
343
+ """The number of outgoing messages dropped because the
344
+ tmStateReference referred to an invalid cache.""",
345
+ }, # scalar
346
+ "snmpSshtmConformance" : {
347
+ "nodetype" : "node",
348
+ "moduleName" : "SNMP-SSH-TM-MIB",
349
+ "oid" : "1.3.6.1.2.1.189.2",
350
+ }, # node
351
+ "snmpSshtmCompliances" : {
352
+ "nodetype" : "node",
353
+ "moduleName" : "SNMP-SSH-TM-MIB",
354
+ "oid" : "1.3.6.1.2.1.189.2.1",
355
+ }, # node
356
+ "snmpSshtmGroups" : {
357
+ "nodetype" : "node",
358
+ "moduleName" : "SNMP-SSH-TM-MIB",
359
+ "oid" : "1.3.6.1.2.1.189.2.2",
360
+ }, # node
361
+ "snmpSSHDomain" : {
362
+ "nodetype" : "node",
363
+ "moduleName" : "SNMP-SSH-TM-MIB",
364
+ "oid" : "1.3.6.1.6.1.7",
365
+ "status" : "current",
366
+ "description" :
367
+ """The SNMP-over-SSH transport domain. The corresponding
368
+ transport address is of type SnmpSSHAddress.
369
+
370
+ When an SNMP entity uses the snmpSSHDomain Transport
371
+ Model, it must be capable of accepting messages up to
372
+ and including 8192 octets in size. Implementation of
373
+ larger values is encouraged whenever possible.
374
+
375
+ The securityName prefix to be associated with the
376
+ snmpSSHDomain is 'ssh'. This prefix may be used by Security
377
+ Models or other components to identify which secure transport
378
+ infrastructure authenticated a securityName.""",
379
+ }, # node
380
+ }, # nodes
381
+
382
+ "groups" : {
383
+ "snmpSshtmGroup" : {
384
+ "nodetype" : "group",
385
+ "moduleName" : "SNMP-SSH-TM-MIB",
386
+ "oid" : "1.3.6.1.2.1.189.2.2.2",
387
+ "status" : "current",
388
+ "members" : {
389
+ "snmpSshtmSessionOpens" : {
390
+ "nodetype" : "member",
391
+ "module" : "SNMP-SSH-TM-MIB"
392
+ },
393
+ "snmpSshtmSessionCloses" : {
394
+ "nodetype" : "member",
395
+ "module" : "SNMP-SSH-TM-MIB"
396
+ },
397
+ "snmpSshtmSessionOpenErrors" : {
398
+ "nodetype" : "member",
399
+ "module" : "SNMP-SSH-TM-MIB"
400
+ },
401
+ "snmpSshtmSessionUserAuthFailures" : {
402
+ "nodetype" : "member",
403
+ "module" : "SNMP-SSH-TM-MIB"
404
+ },
405
+ "snmpSshtmSessionNoChannels" : {
406
+ "nodetype" : "member",
407
+ "module" : "SNMP-SSH-TM-MIB"
408
+ },
409
+ "snmpSshtmSessionNoSubsystems" : {
410
+ "nodetype" : "member",
411
+ "module" : "SNMP-SSH-TM-MIB"
412
+ },
413
+ "snmpSshtmSessionNoSessions" : {
414
+ "nodetype" : "member",
415
+ "module" : "SNMP-SSH-TM-MIB"
416
+ },
417
+ "snmpSshtmSessionInvalidCaches" : {
418
+ "nodetype" : "member",
419
+ "module" : "SNMP-SSH-TM-MIB"
420
+ },
421
+ }, # members
422
+ "description" :
423
+ """A collection of objects for maintaining information
424
+ of an SNMP engine that implements the SNMP Secure
425
+ Shell Transport Model.""",
426
+ }, # group
427
+ }, # groups
428
+
429
+ "compliances" : {
430
+ "snmpSshtmCompliance" : {
431
+ "nodetype" : "compliance",
432
+ "moduleName" : "SNMP-SSH-TM-MIB",
433
+ "oid" : "1.3.6.1.2.1.189.2.1.1",
434
+ "status" : "current",
435
+ "description" :
436
+ """The compliance statement for SNMP engines that
437
+ support the SNMP-SSH-TM-MIB.""",
438
+ "requires" : {
439
+ "snmpSshtmGroup" : {
440
+ "nodetype" : "mandatory",
441
+ "module" : "SNMP-SSH-TM-MIB"
442
+ },
443
+ }, # requires
444
+ }, # compliance
445
+ }, # compliances
446
+
447
+ }
@@ -0,0 +1,924 @@
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-TARGET-MIB
6
+
7
+ FILENAME = "./libsmi-0.5.0/mibs/ietf/SNMP-TARGET-MIB"
8
+
9
+ MIB = {
10
+ "moduleName" : "SNMP-TARGET-MIB",
11
+
12
+ "SNMP-TARGET-MIB" : {
13
+ "nodetype" : "module",
14
+ "language" : "SMIv2",
15
+ "organization" :
16
+ """IETF SNMPv3 Working Group""",
17
+ "contact" :
18
+ """WG-email: snmpv3@lists.tislabs.com
19
+ Subscribe: majordomo@lists.tislabs.com
20
+ In message body: subscribe snmpv3
21
+
22
+ Co-Chair: Russ Mundy
23
+ Network Associates Laboratories
24
+ Postal: 15204 Omega Drive, Suite 300
25
+ Rockville, MD 20850-4601
26
+ USA
27
+ EMail: mundy@tislabs.com
28
+ Phone: +1 301-947-7107
29
+
30
+ Co-Chair: David Harrington
31
+ Enterasys Networks
32
+ Postal: 35 Industrial Way
33
+ P. O. Box 5004
34
+ Rochester, New Hampshire 03866-5005
35
+ USA
36
+ EMail: dbh@enterasys.com
37
+ Phone: +1 603-337-2614
38
+
39
+ Co-editor: David B. Levi
40
+ Nortel Networks
41
+ Postal: 3505 Kesterwood Drive
42
+ Knoxville, Tennessee 37918
43
+ EMail: dlevi@nortelnetworks.com
44
+ Phone: +1 865 686 0432
45
+
46
+ Co-editor: Paul Meyer
47
+ Secure Computing Corporation
48
+ Postal: 2675 Long Lake Road
49
+
50
+
51
+
52
+ Roseville, Minnesota 55113
53
+ EMail: paul_meyer@securecomputing.com
54
+ Phone: +1 651 628 1592
55
+
56
+ Co-editor: Bob Stewart
57
+ Retired""",
58
+ "description" :
59
+ """This MIB module defines MIB objects which provide
60
+ mechanisms to remotely configure the parameters used
61
+ by an SNMP entity for the generation of SNMP messages.
62
+
63
+ Copyright (C) The Internet Society (2002). This
64
+ version of this MIB module is part of RFC 3413;
65
+ see the RFC itself for full legal notices.""",
66
+ "revisions" : (
67
+ {
68
+ "date" : "2002-10-14 00:00",
69
+ "description" :
70
+ """Fixed DISPLAY-HINTS for UTF-8 strings, fixed hex
71
+ value of LF characters, clarified meaning of zero
72
+ length tag values, improved tag list examples.
73
+ Published as RFC 3413.""",
74
+ },
75
+ {
76
+ "date" : "1998-08-04 00:00",
77
+ "description" :
78
+ """Clarifications, published as
79
+ RFC 2573.""",
80
+ },
81
+ {
82
+ "date" : "1997-07-14 00:00",
83
+ "description" :
84
+ """The initial revision, published as RFC2273.""",
85
+ },
86
+ ),
87
+ "identity node" : "snmpTargetMIB",
88
+ },
89
+
90
+ "imports" : (
91
+ {"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
92
+ {"module" : "SNMPv2-SMI", "name" : "OBJECT-TYPE"},
93
+ {"module" : "SNMPv2-SMI", "name" : "snmpModules"},
94
+ {"module" : "SNMPv2-SMI", "name" : "Counter32"},
95
+ {"module" : "SNMPv2-SMI", "name" : "Integer32"},
96
+ {"module" : "SNMPv2-TC", "name" : "TEXTUAL-CONVENTION"},
97
+ {"module" : "SNMPv2-TC", "name" : "TDomain"},
98
+ {"module" : "SNMPv2-TC", "name" : "TAddress"},
99
+ {"module" : "SNMPv2-TC", "name" : "TimeInterval"},
100
+ {"module" : "SNMPv2-TC", "name" : "RowStatus"},
101
+ {"module" : "SNMPv2-TC", "name" : "StorageType"},
102
+ {"module" : "SNMPv2-TC", "name" : "TestAndIncr"},
103
+ {"module" : "SNMP-FRAMEWORK-MIB", "name" : "SnmpSecurityModel"},
104
+ {"module" : "SNMP-FRAMEWORK-MIB", "name" : "SnmpMessageProcessingModel"},
105
+ {"module" : "SNMP-FRAMEWORK-MIB", "name" : "SnmpSecurityLevel"},
106
+ {"module" : "SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
107
+ {"module" : "SNMPv2-CONF", "name" : "MODULE-COMPLIANCE"},
108
+ {"module" : "SNMPv2-CONF", "name" : "OBJECT-GROUP"},
109
+ ),
110
+
111
+ "typedefs" : {
112
+ "SnmpTagValue" : {
113
+ "basetype" : "OctetString",
114
+ "status" : "current",
115
+ "ranges" : [
116
+ {
117
+ "min" : "0",
118
+ "max" : "255"
119
+ },
120
+ ],
121
+ "range" : {
122
+ "min" : "0",
123
+ "max" : "255"
124
+ },
125
+ "format" : "255t",
126
+ "description" :
127
+ """An octet string containing a tag value.
128
+ Tag values are preferably in human-readable form.
129
+
130
+ To facilitate internationalization, this information
131
+ is represented using the ISO/IEC IS 10646-1 character
132
+ set, encoded as an octet string using the UTF-8
133
+ character encoding scheme described in RFC 2279.
134
+
135
+ Since additional code points are added by amendments
136
+ to the 10646 standard from time to time,
137
+ implementations must be prepared to encounter any code
138
+ point from 0x00000000 to 0x7fffffff.
139
+
140
+ The use of control codes should be avoided, and certain
141
+
142
+
143
+
144
+ control codes are not allowed as described below.
145
+
146
+ For code points not directly supported by user
147
+ interface hardware or software, an alternative means
148
+ of entry and display, such as hexadecimal, may be
149
+ provided.
150
+
151
+ For information encoded in 7-bit US-ASCII, the UTF-8
152
+ representation is identical to the US-ASCII encoding.
153
+
154
+ Note that when this TC is used for an object that
155
+ is used or envisioned to be used as an index, then a
156
+ SIZE restriction must be specified so that the number
157
+ of sub-identifiers for any object instance does not
158
+ exceed the limit of 128, as defined by [RFC1905].
159
+
160
+ An object of this type contains a single tag value
161
+ which is used to select a set of entries in a table.
162
+
163
+ A tag value is an arbitrary string of octets, but
164
+ may not contain a delimiter character. Delimiter
165
+ characters are defined to be one of the following:
166
+
167
+ - An ASCII space character (0x20).
168
+
169
+ - An ASCII TAB character (0x09).
170
+
171
+ - An ASCII carriage return (CR) character (0x0D).
172
+
173
+ - An ASCII line feed (LF) character (0x0A).
174
+
175
+ Delimiter characters are used to separate tag values
176
+ in a tag list. An object of this type may only
177
+ contain a single tag value, and so delimiter
178
+ characters are not allowed in a value of this type.
179
+
180
+ Note that a tag value of 0 length means that no tag is
181
+ defined. In other words, a tag value of 0 length would
182
+ never match anything in a tag list, and would never
183
+ select any table entries.
184
+
185
+ Some examples of valid tag values are:
186
+
187
+ - 'acme'
188
+
189
+ - 'router'
190
+
191
+ - 'host'
192
+
193
+
194
+
195
+ The use of a tag value to select table entries is
196
+ application and MIB specific.""",
197
+ },
198
+ "SnmpTagList" : {
199
+ "basetype" : "OctetString",
200
+ "status" : "current",
201
+ "ranges" : [
202
+ {
203
+ "min" : "0",
204
+ "max" : "255"
205
+ },
206
+ ],
207
+ "range" : {
208
+ "min" : "0",
209
+ "max" : "255"
210
+ },
211
+ "format" : "255t",
212
+ "description" :
213
+ """An octet string containing a list of tag values.
214
+ Tag values are preferably in human-readable form.
215
+
216
+ To facilitate internationalization, this information
217
+ is represented using the ISO/IEC IS 10646-1 character
218
+ set, encoded as an octet string using the UTF-8
219
+ character encoding scheme described in RFC 2279.
220
+
221
+ Since additional code points are added by amendments
222
+ to the 10646 standard from time to time,
223
+ implementations must be prepared to encounter any code
224
+ point from 0x00000000 to 0x7fffffff.
225
+
226
+ The use of control codes should be avoided, except as
227
+ described below.
228
+
229
+ For code points not directly supported by user
230
+ interface hardware or software, an alternative means
231
+ of entry and display, such as hexadecimal, may be
232
+ provided.
233
+
234
+ For information encoded in 7-bit US-ASCII, the UTF-8
235
+ representation is identical to the US-ASCII encoding.
236
+
237
+ An object of this type contains a list of tag values
238
+ which are used to select a set of entries in a table.
239
+
240
+ A tag value is an arbitrary string of octets, but
241
+ may not contain a delimiter character. Delimiter
242
+ characters are defined to be one of the following:
243
+
244
+ - An ASCII space character (0x20).
245
+
246
+ - An ASCII TAB character (0x09).
247
+
248
+ - An ASCII carriage return (CR) character (0x0D).
249
+
250
+ - An ASCII line feed (LF) character (0x0A).
251
+
252
+ Delimiter characters are used to separate tag values
253
+
254
+
255
+
256
+ in a tag list. Only a single delimiter character may
257
+ occur between two tag values. A tag value may not
258
+ have a zero length. These constraints imply certain
259
+ restrictions on the contents of this object:
260
+
261
+ - There cannot be a leading or trailing delimiter
262
+ character.
263
+
264
+ - There cannot be multiple adjacent delimiter
265
+ characters.
266
+
267
+ Some examples of valid tag lists are:
268
+
269
+ - '' -- an empty list
270
+
271
+ - 'acme' -- list of one tag
272
+
273
+ - 'host router bridge' -- list of several tags
274
+
275
+ Note that although a tag value may not have a length of
276
+ zero, an empty string is still valid. This indicates
277
+ an empty list (i.e. there are no tag values in the list).
278
+
279
+ The use of the tag list to select table entries is
280
+ application and MIB specific. Typically, an application
281
+ will provide one or more tag values, and any entry
282
+ which contains some combination of these tag values
283
+ will be selected.""",
284
+ },
285
+ }, # typedefs
286
+
287
+ "nodes" : {
288
+ "snmpTargetMIB" : {
289
+ "nodetype" : "node",
290
+ "moduleName" : "SNMP-TARGET-MIB",
291
+ "oid" : "1.3.6.1.6.3.12",
292
+ "status" : "current",
293
+ }, # node
294
+ "snmpTargetObjects" : {
295
+ "nodetype" : "node",
296
+ "moduleName" : "SNMP-TARGET-MIB",
297
+ "oid" : "1.3.6.1.6.3.12.1",
298
+ }, # node
299
+ "snmpTargetSpinLock" : {
300
+ "nodetype" : "scalar",
301
+ "moduleName" : "SNMP-TARGET-MIB",
302
+ "oid" : "1.3.6.1.6.3.12.1.1",
303
+ "status" : "current",
304
+ "syntax" : {
305
+ "type" : { "module" :"SNMPv2-TC", "name" : "TestAndIncr"},
306
+ },
307
+ "access" : "readwrite",
308
+ "description" :
309
+ """This object is used to facilitate modification of table
310
+ entries in the SNMP-TARGET-MIB module by multiple
311
+ managers. In particular, it is useful when modifying
312
+ the value of the snmpTargetAddrTagList object.
313
+
314
+ The procedure for modifying the snmpTargetAddrTagList
315
+ object is as follows:
316
+
317
+
318
+
319
+ 1. Retrieve the value of snmpTargetSpinLock and
320
+ of snmpTargetAddrTagList.
321
+
322
+ 2. Generate a new value for snmpTargetAddrTagList.
323
+
324
+ 3. Set the value of snmpTargetSpinLock to the
325
+ retrieved value, and the value of
326
+ snmpTargetAddrTagList to the new value. If
327
+ the set fails for the snmpTargetSpinLock
328
+ object, go back to step 1.""",
329
+ }, # scalar
330
+ "snmpTargetAddrTable" : {
331
+ "nodetype" : "table",
332
+ "moduleName" : "SNMP-TARGET-MIB",
333
+ "oid" : "1.3.6.1.6.3.12.1.2",
334
+ "status" : "current",
335
+ "description" :
336
+ """A table of transport addresses to be used in the generation
337
+ of SNMP messages.""",
338
+ }, # table
339
+ "snmpTargetAddrEntry" : {
340
+ "nodetype" : "row",
341
+ "moduleName" : "SNMP-TARGET-MIB",
342
+ "oid" : "1.3.6.1.6.3.12.1.2.1",
343
+ "create" : "true",
344
+ "status" : "current",
345
+ "implied" : "true",
346
+ "linkage" : [
347
+ "snmpTargetAddrName",
348
+ ],
349
+ "description" :
350
+ """A transport address to be used in the generation
351
+ of SNMP operations.
352
+
353
+ Entries in the snmpTargetAddrTable are created and
354
+ deleted using the snmpTargetAddrRowStatus object.""",
355
+ }, # row
356
+ "snmpTargetAddrName" : {
357
+ "nodetype" : "column",
358
+ "moduleName" : "SNMP-TARGET-MIB",
359
+ "oid" : "1.3.6.1.6.3.12.1.2.1.1",
360
+ "status" : "current",
361
+ "syntax" : {
362
+ "type" : {
363
+ "basetype" : "OctetString",
364
+ "parent module" : {
365
+ "name" : "SNMP-FRAMEWORK-MIB",
366
+ "type" : "SnmpAdminString",
367
+ },
368
+ "ranges" : [
369
+ {
370
+ "min" : "1",
371
+ "max" : "32"
372
+ },
373
+ ],
374
+ "range" : {
375
+ "min" : "1",
376
+ "max" : "32"
377
+ },
378
+ },
379
+ },
380
+ "access" : "noaccess",
381
+ "description" :
382
+ """The locally arbitrary, but unique identifier associated
383
+ with this snmpTargetAddrEntry.""",
384
+ }, # column
385
+ "snmpTargetAddrTDomain" : {
386
+ "nodetype" : "column",
387
+ "moduleName" : "SNMP-TARGET-MIB",
388
+ "oid" : "1.3.6.1.6.3.12.1.2.1.2",
389
+ "status" : "current",
390
+ "syntax" : {
391
+ "type" : { "module" :"SNMPv2-TC", "name" : "TDomain"},
392
+ },
393
+ "access" : "readwrite",
394
+ "description" :
395
+ """This object indicates the transport type of the address
396
+ contained in the snmpTargetAddrTAddress object.""",
397
+ }, # column
398
+ "snmpTargetAddrTAddress" : {
399
+ "nodetype" : "column",
400
+ "moduleName" : "SNMP-TARGET-MIB",
401
+ "oid" : "1.3.6.1.6.3.12.1.2.1.3",
402
+ "status" : "current",
403
+ "syntax" : {
404
+ "type" : { "module" :"SNMPv2-TC", "name" : "TAddress"},
405
+ },
406
+ "access" : "readwrite",
407
+ "description" :
408
+ """This object contains a transport address. The format of
409
+ this address depends on the value of the
410
+ snmpTargetAddrTDomain object.""",
411
+ }, # column
412
+ "snmpTargetAddrTimeout" : {
413
+ "nodetype" : "column",
414
+ "moduleName" : "SNMP-TARGET-MIB",
415
+ "oid" : "1.3.6.1.6.3.12.1.2.1.4",
416
+ "status" : "current",
417
+ "syntax" : {
418
+ "type" : { "module" :"SNMPv2-TC", "name" : "TimeInterval"},
419
+ },
420
+ "access" : "readwrite",
421
+ "default" : "1500",
422
+ "description" :
423
+ """This object should reflect the expected maximum round
424
+ trip time for communicating with the transport address
425
+ defined by this row. When a message is sent to this
426
+ address, and a response (if one is expected) is not
427
+ received within this time period, an implementation
428
+ may assume that the response will not be delivered.
429
+
430
+ Note that the time interval that an application waits
431
+ for a response may actually be derived from the value
432
+ of this object. The method for deriving the actual time
433
+ interval is implementation dependent. One such method
434
+ is to derive the expected round trip time based on a
435
+ particular retransmission algorithm and on the number
436
+ of timeouts which have occurred. The type of message may
437
+ also be considered when deriving expected round trip
438
+ times for retransmissions. For example, if a message is
439
+ being sent with a securityLevel that indicates both
440
+
441
+
442
+
443
+ authentication and privacy, the derived value may be
444
+ increased to compensate for extra processing time spent
445
+ during authentication and encryption processing.""",
446
+ }, # column
447
+ "snmpTargetAddrRetryCount" : {
448
+ "nodetype" : "column",
449
+ "moduleName" : "SNMP-TARGET-MIB",
450
+ "oid" : "1.3.6.1.6.3.12.1.2.1.5",
451
+ "status" : "current",
452
+ "syntax" : {
453
+ "type" : {
454
+ "basetype" : "Integer32",
455
+ "ranges" : [
456
+ {
457
+ "min" : "0",
458
+ "max" : "255"
459
+ },
460
+ ],
461
+ "range" : {
462
+ "min" : "0",
463
+ "max" : "255"
464
+ },
465
+ },
466
+ },
467
+ "access" : "readwrite",
468
+ "default" : "3",
469
+ "description" :
470
+ """This object specifies a default number of retries to be
471
+ attempted when a response is not received for a generated
472
+ message. An application may provide its own retry count,
473
+ in which case the value of this object is ignored.""",
474
+ }, # column
475
+ "snmpTargetAddrTagList" : {
476
+ "nodetype" : "column",
477
+ "moduleName" : "SNMP-TARGET-MIB",
478
+ "oid" : "1.3.6.1.6.3.12.1.2.1.6",
479
+ "status" : "current",
480
+ "syntax" : {
481
+ "type" : { "module" :"SNMP-TARGET-MIB", "name" : "SnmpTagList"},
482
+ },
483
+ "access" : "readwrite",
484
+ "default" : "",
485
+ "description" :
486
+ """This object contains a list of tag values which are
487
+ used to select target addresses for a particular
488
+ operation.""",
489
+ }, # column
490
+ "snmpTargetAddrParams" : {
491
+ "nodetype" : "column",
492
+ "moduleName" : "SNMP-TARGET-MIB",
493
+ "oid" : "1.3.6.1.6.3.12.1.2.1.7",
494
+ "status" : "current",
495
+ "syntax" : {
496
+ "type" : {
497
+ "basetype" : "OctetString",
498
+ "parent module" : {
499
+ "name" : "SNMP-FRAMEWORK-MIB",
500
+ "type" : "SnmpAdminString",
501
+ },
502
+ "ranges" : [
503
+ {
504
+ "min" : "1",
505
+ "max" : "32"
506
+ },
507
+ ],
508
+ "range" : {
509
+ "min" : "1",
510
+ "max" : "32"
511
+ },
512
+ },
513
+ },
514
+ "access" : "readwrite",
515
+ "description" :
516
+ """The value of this object identifies an entry in the
517
+ snmpTargetParamsTable. The identified entry
518
+ contains SNMP parameters to be used when generating
519
+ messages to be sent to this transport address.""",
520
+ }, # column
521
+ "snmpTargetAddrStorageType" : {
522
+ "nodetype" : "column",
523
+ "moduleName" : "SNMP-TARGET-MIB",
524
+ "oid" : "1.3.6.1.6.3.12.1.2.1.8",
525
+ "status" : "current",
526
+ "syntax" : {
527
+ "type" : { "module" :"SNMPv2-TC", "name" : "StorageType"},
528
+ },
529
+ "access" : "readwrite",
530
+ "default" : "nonVolatile",
531
+ "description" :
532
+ """The storage type for this conceptual row.
533
+ Conceptual rows having the value 'permanent' need not
534
+ allow write-access to any columnar objects in the row.""",
535
+ }, # column
536
+ "snmpTargetAddrRowStatus" : {
537
+ "nodetype" : "column",
538
+ "moduleName" : "SNMP-TARGET-MIB",
539
+ "oid" : "1.3.6.1.6.3.12.1.2.1.9",
540
+ "status" : "current",
541
+ "syntax" : {
542
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
543
+ },
544
+ "access" : "readwrite",
545
+ "description" :
546
+ """The status of this conceptual row.
547
+
548
+ To create a row in this table, a manager must
549
+ set this object to either createAndGo(4) or
550
+ createAndWait(5).
551
+
552
+ Until instances of all corresponding columns are
553
+ appropriately configured, the value of the
554
+ corresponding instance of the snmpTargetAddrRowStatus
555
+ column is 'notReady'.
556
+
557
+ In particular, a newly created row cannot be made
558
+ active until the corresponding instances of
559
+ snmpTargetAddrTDomain, snmpTargetAddrTAddress, and
560
+ snmpTargetAddrParams have all been set.
561
+
562
+ The following objects may not be modified while the
563
+ value of this object is active(1):
564
+ - snmpTargetAddrTDomain
565
+ - snmpTargetAddrTAddress
566
+ An attempt to set these objects while the value of
567
+ snmpTargetAddrRowStatus is active(1) will result in
568
+ an inconsistentValue error.""",
569
+ }, # column
570
+ "snmpTargetParamsTable" : {
571
+ "nodetype" : "table",
572
+ "moduleName" : "SNMP-TARGET-MIB",
573
+ "oid" : "1.3.6.1.6.3.12.1.3",
574
+ "status" : "current",
575
+ "description" :
576
+ """A table of SNMP target information to be used
577
+ in the generation of SNMP messages.""",
578
+ }, # table
579
+ "snmpTargetParamsEntry" : {
580
+ "nodetype" : "row",
581
+ "moduleName" : "SNMP-TARGET-MIB",
582
+ "oid" : "1.3.6.1.6.3.12.1.3.1",
583
+ "create" : "true",
584
+ "status" : "current",
585
+ "implied" : "true",
586
+ "linkage" : [
587
+ "snmpTargetParamsName",
588
+ ],
589
+ "description" :
590
+ """A set of SNMP target information.
591
+
592
+
593
+
594
+ Entries in the snmpTargetParamsTable are created and
595
+ deleted using the snmpTargetParamsRowStatus object.""",
596
+ }, # row
597
+ "snmpTargetParamsName" : {
598
+ "nodetype" : "column",
599
+ "moduleName" : "SNMP-TARGET-MIB",
600
+ "oid" : "1.3.6.1.6.3.12.1.3.1.1",
601
+ "status" : "current",
602
+ "syntax" : {
603
+ "type" : {
604
+ "basetype" : "OctetString",
605
+ "parent module" : {
606
+ "name" : "SNMP-FRAMEWORK-MIB",
607
+ "type" : "SnmpAdminString",
608
+ },
609
+ "ranges" : [
610
+ {
611
+ "min" : "1",
612
+ "max" : "32"
613
+ },
614
+ ],
615
+ "range" : {
616
+ "min" : "1",
617
+ "max" : "32"
618
+ },
619
+ },
620
+ },
621
+ "access" : "noaccess",
622
+ "description" :
623
+ """The locally arbitrary, but unique identifier associated
624
+ with this snmpTargetParamsEntry.""",
625
+ }, # column
626
+ "snmpTargetParamsMPModel" : {
627
+ "nodetype" : "column",
628
+ "moduleName" : "SNMP-TARGET-MIB",
629
+ "oid" : "1.3.6.1.6.3.12.1.3.1.2",
630
+ "status" : "current",
631
+ "syntax" : {
632
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpMessageProcessingModel"},
633
+ },
634
+ "access" : "readwrite",
635
+ "description" :
636
+ """The Message Processing Model to be used when generating
637
+ SNMP messages using this entry.""",
638
+ }, # column
639
+ "snmpTargetParamsSecurityModel" : {
640
+ "nodetype" : "column",
641
+ "moduleName" : "SNMP-TARGET-MIB",
642
+ "oid" : "1.3.6.1.6.3.12.1.3.1.3",
643
+ "status" : "current",
644
+ "syntax" : {
645
+ "type" : {
646
+ "basetype" : "Integer32",
647
+ "parent module" : {
648
+ "name" : "SNMP-FRAMEWORK-MIB",
649
+ "type" : "SnmpSecurityModel",
650
+ },
651
+ "ranges" : [
652
+ {
653
+ "min" : "1",
654
+ "max" : "2147483647"
655
+ },
656
+ ],
657
+ "range" : {
658
+ "min" : "1",
659
+ "max" : "2147483647"
660
+ },
661
+ },
662
+ },
663
+ "access" : "readwrite",
664
+ "description" :
665
+ """The Security Model to be used when generating SNMP
666
+ messages using this entry. An implementation may
667
+ choose to return an inconsistentValue error if an
668
+ attempt is made to set this variable to a value
669
+ for a security model which the implementation does
670
+ not support.""",
671
+ }, # column
672
+ "snmpTargetParamsSecurityName" : {
673
+ "nodetype" : "column",
674
+ "moduleName" : "SNMP-TARGET-MIB",
675
+ "oid" : "1.3.6.1.6.3.12.1.3.1.4",
676
+ "status" : "current",
677
+ "syntax" : {
678
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
679
+ },
680
+ "access" : "readwrite",
681
+ "description" :
682
+ """The securityName which identifies the Principal on
683
+ whose behalf SNMP messages will be generated using
684
+ this entry.""",
685
+ }, # column
686
+ "snmpTargetParamsSecurityLevel" : {
687
+ "nodetype" : "column",
688
+ "moduleName" : "SNMP-TARGET-MIB",
689
+ "oid" : "1.3.6.1.6.3.12.1.3.1.5",
690
+ "status" : "current",
691
+ "syntax" : {
692
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpSecurityLevel"},
693
+ },
694
+ "access" : "readwrite",
695
+ "description" :
696
+ """The Level of Security to be used when generating
697
+ SNMP messages using this entry.""",
698
+ }, # column
699
+ "snmpTargetParamsStorageType" : {
700
+ "nodetype" : "column",
701
+ "moduleName" : "SNMP-TARGET-MIB",
702
+ "oid" : "1.3.6.1.6.3.12.1.3.1.6",
703
+ "status" : "current",
704
+ "syntax" : {
705
+ "type" : { "module" :"SNMPv2-TC", "name" : "StorageType"},
706
+ },
707
+ "access" : "readwrite",
708
+ "default" : "nonVolatile",
709
+ "description" :
710
+ """The storage type for this conceptual row.
711
+ Conceptual rows having the value 'permanent' need not
712
+ allow write-access to any columnar objects in the row.""",
713
+ }, # column
714
+ "snmpTargetParamsRowStatus" : {
715
+ "nodetype" : "column",
716
+ "moduleName" : "SNMP-TARGET-MIB",
717
+ "oid" : "1.3.6.1.6.3.12.1.3.1.7",
718
+ "status" : "current",
719
+ "syntax" : {
720
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
721
+ },
722
+ "access" : "readwrite",
723
+ "description" :
724
+ """The status of this conceptual row.
725
+
726
+ To create a row in this table, a manager must
727
+ set this object to either createAndGo(4) or
728
+ createAndWait(5).
729
+
730
+ Until instances of all corresponding columns are
731
+ appropriately configured, the value of the
732
+ corresponding instance of the snmpTargetParamsRowStatus
733
+ column is 'notReady'.
734
+
735
+ In particular, a newly created row cannot be made
736
+ active until the corresponding
737
+ snmpTargetParamsMPModel,
738
+ snmpTargetParamsSecurityModel,
739
+
740
+
741
+
742
+ snmpTargetParamsSecurityName,
743
+ and snmpTargetParamsSecurityLevel have all been set.
744
+
745
+ The following objects may not be modified while the
746
+ value of this object is active(1):
747
+ - snmpTargetParamsMPModel
748
+ - snmpTargetParamsSecurityModel
749
+ - snmpTargetParamsSecurityName
750
+ - snmpTargetParamsSecurityLevel
751
+ An attempt to set these objects while the value of
752
+ snmpTargetParamsRowStatus is active(1) will result in
753
+ an inconsistentValue error.""",
754
+ }, # column
755
+ "snmpUnavailableContexts" : {
756
+ "nodetype" : "scalar",
757
+ "moduleName" : "SNMP-TARGET-MIB",
758
+ "oid" : "1.3.6.1.6.3.12.1.4",
759
+ "status" : "current",
760
+ "syntax" : {
761
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
762
+ },
763
+ "access" : "readonly",
764
+ "description" :
765
+ """The total number of packets received by the SNMP
766
+ engine which were dropped because the context
767
+ contained in the message was unavailable.""",
768
+ }, # scalar
769
+ "snmpUnknownContexts" : {
770
+ "nodetype" : "scalar",
771
+ "moduleName" : "SNMP-TARGET-MIB",
772
+ "oid" : "1.3.6.1.6.3.12.1.5",
773
+ "status" : "current",
774
+ "syntax" : {
775
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
776
+ },
777
+ "access" : "readonly",
778
+ "description" :
779
+ """The total number of packets received by the SNMP
780
+ engine which were dropped because the context
781
+ contained in the message was unknown.""",
782
+ }, # scalar
783
+ "snmpTargetConformance" : {
784
+ "nodetype" : "node",
785
+ "moduleName" : "SNMP-TARGET-MIB",
786
+ "oid" : "1.3.6.1.6.3.12.3",
787
+ }, # node
788
+ "snmpTargetCompliances" : {
789
+ "nodetype" : "node",
790
+ "moduleName" : "SNMP-TARGET-MIB",
791
+ "oid" : "1.3.6.1.6.3.12.3.1",
792
+ }, # node
793
+ "snmpTargetGroups" : {
794
+ "nodetype" : "node",
795
+ "moduleName" : "SNMP-TARGET-MIB",
796
+ "oid" : "1.3.6.1.6.3.12.3.2",
797
+ }, # node
798
+ }, # nodes
799
+
800
+ "groups" : {
801
+ "snmpTargetBasicGroup" : {
802
+ "nodetype" : "group",
803
+ "moduleName" : "SNMP-TARGET-MIB",
804
+ "oid" : "1.3.6.1.6.3.12.3.2.1",
805
+ "status" : "current",
806
+ "members" : {
807
+ "snmpTargetSpinLock" : {
808
+ "nodetype" : "member",
809
+ "module" : "SNMP-TARGET-MIB"
810
+ },
811
+ "snmpTargetAddrTDomain" : {
812
+ "nodetype" : "member",
813
+ "module" : "SNMP-TARGET-MIB"
814
+ },
815
+ "snmpTargetAddrTAddress" : {
816
+ "nodetype" : "member",
817
+ "module" : "SNMP-TARGET-MIB"
818
+ },
819
+ "snmpTargetAddrTagList" : {
820
+ "nodetype" : "member",
821
+ "module" : "SNMP-TARGET-MIB"
822
+ },
823
+ "snmpTargetAddrParams" : {
824
+ "nodetype" : "member",
825
+ "module" : "SNMP-TARGET-MIB"
826
+ },
827
+ "snmpTargetAddrStorageType" : {
828
+ "nodetype" : "member",
829
+ "module" : "SNMP-TARGET-MIB"
830
+ },
831
+ "snmpTargetAddrRowStatus" : {
832
+ "nodetype" : "member",
833
+ "module" : "SNMP-TARGET-MIB"
834
+ },
835
+ "snmpTargetParamsMPModel" : {
836
+ "nodetype" : "member",
837
+ "module" : "SNMP-TARGET-MIB"
838
+ },
839
+ "snmpTargetParamsSecurityModel" : {
840
+ "nodetype" : "member",
841
+ "module" : "SNMP-TARGET-MIB"
842
+ },
843
+ "snmpTargetParamsSecurityName" : {
844
+ "nodetype" : "member",
845
+ "module" : "SNMP-TARGET-MIB"
846
+ },
847
+ "snmpTargetParamsSecurityLevel" : {
848
+ "nodetype" : "member",
849
+ "module" : "SNMP-TARGET-MIB"
850
+ },
851
+ "snmpTargetParamsStorageType" : {
852
+ "nodetype" : "member",
853
+ "module" : "SNMP-TARGET-MIB"
854
+ },
855
+ "snmpTargetParamsRowStatus" : {
856
+ "nodetype" : "member",
857
+ "module" : "SNMP-TARGET-MIB"
858
+ },
859
+ }, # members
860
+ "description" :
861
+ """A collection of objects providing basic remote
862
+ configuration of management targets.""",
863
+ }, # group
864
+ "snmpTargetResponseGroup" : {
865
+ "nodetype" : "group",
866
+ "moduleName" : "SNMP-TARGET-MIB",
867
+ "oid" : "1.3.6.1.6.3.12.3.2.2",
868
+ "status" : "current",
869
+ "members" : {
870
+ "snmpTargetAddrTimeout" : {
871
+ "nodetype" : "member",
872
+ "module" : "SNMP-TARGET-MIB"
873
+ },
874
+ "snmpTargetAddrRetryCount" : {
875
+ "nodetype" : "member",
876
+ "module" : "SNMP-TARGET-MIB"
877
+ },
878
+ }, # members
879
+ "description" :
880
+ """A collection of objects providing remote configuration
881
+ of management targets for applications which generate
882
+ SNMP messages for which a response message would be
883
+ expected.""",
884
+ }, # group
885
+ "snmpTargetCommandResponderGroup" : {
886
+ "nodetype" : "group",
887
+ "moduleName" : "SNMP-TARGET-MIB",
888
+ "oid" : "1.3.6.1.6.3.12.3.2.3",
889
+ "status" : "current",
890
+ "members" : {
891
+ "snmpUnavailableContexts" : {
892
+ "nodetype" : "member",
893
+ "module" : "SNMP-TARGET-MIB"
894
+ },
895
+ "snmpUnknownContexts" : {
896
+ "nodetype" : "member",
897
+ "module" : "SNMP-TARGET-MIB"
898
+ },
899
+ }, # members
900
+ "description" :
901
+ """A collection of objects required for command responder
902
+ applications, used for counting error conditions.""",
903
+ }, # group
904
+ }, # groups
905
+
906
+ "compliances" : {
907
+ "snmpTargetCommandResponderCompliance" : {
908
+ "nodetype" : "compliance",
909
+ "moduleName" : "SNMP-TARGET-MIB",
910
+ "oid" : "1.3.6.1.6.3.12.3.1.1",
911
+ "status" : "current",
912
+ "description" :
913
+ """The compliance statement for SNMP entities which include
914
+ a command responder application.""",
915
+ "requires" : {
916
+ "snmpTargetCommandResponderGroup" : {
917
+ "nodetype" : "mandatory",
918
+ "module" : "SNMP-TARGET-MIB"
919
+ },
920
+ }, # requires
921
+ }, # compliance
922
+ }, # compliances
923
+
924
+ }