logstash-integration-snmp 4.0.0-java

Sign up to get free protection for your applications and to get access to all the features.
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,1135 @@
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 PTOPO-MIB
6
+
7
+ FILENAME = "./libsmi-0.5.0/mibs/ietf/PTOPO-MIB"
8
+
9
+ MIB = {
10
+ "moduleName" : "PTOPO-MIB",
11
+
12
+ "PTOPO-MIB" : {
13
+ "nodetype" : "module",
14
+ "language" : "SMIv2",
15
+ "organization" :
16
+ """IETF; PTOPOMIB Working Group""",
17
+ "contact" :
18
+ """PTOPOMIB WG Discussion:
19
+ ptopo@3com.com
20
+ Subscription:
21
+ majordomo@3com.com
22
+ msg body: [un]subscribe ptopomib
23
+
24
+ Andy Bierman
25
+ Cisco Systems Inc.
26
+ 170 West Tasman Drive
27
+ San Jose, CA 95134
28
+ 408-527-3711
29
+ abierman@cisco.com
30
+
31
+ Kendall S. Jones
32
+ Nortel Networks
33
+ 4401 Great America Parkway
34
+ Santa Clara, CA 95054
35
+ 408-495-7356
36
+ kejones@nortelnetworks.com""",
37
+ "description" :
38
+ """The MIB module for physical topology information.""",
39
+ "revisions" : (
40
+ {
41
+ "date" : "2000-09-21 00:00",
42
+ "description" :
43
+ """Initial Version of the Physical Topology MIB. This version
44
+ published as RFC 2922.""",
45
+ },
46
+ ),
47
+ "identity node" : "ptopoMIB",
48
+ },
49
+
50
+ "imports" : (
51
+ {"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
52
+ {"module" : "SNMPv2-SMI", "name" : "OBJECT-TYPE"},
53
+ {"module" : "SNMPv2-SMI", "name" : "NOTIFICATION-TYPE"},
54
+ {"module" : "SNMPv2-SMI", "name" : "Integer32"},
55
+ {"module" : "SNMPv2-SMI", "name" : "Counter32"},
56
+ {"module" : "SNMPv2-SMI", "name" : "mib-2"},
57
+ {"module" : "SNMPv2-TC", "name" : "TEXTUAL-CONVENTION"},
58
+ {"module" : "SNMPv2-TC", "name" : "AutonomousType"},
59
+ {"module" : "SNMPv2-TC", "name" : "RowStatus"},
60
+ {"module" : "SNMPv2-TC", "name" : "TimeStamp"},
61
+ {"module" : "SNMPv2-TC", "name" : "TruthValue"},
62
+ {"module" : "SNMPv2-CONF", "name" : "MODULE-COMPLIANCE"},
63
+ {"module" : "SNMPv2-CONF", "name" : "OBJECT-GROUP"},
64
+ {"module" : "SNMPv2-CONF", "name" : "NOTIFICATION-GROUP"},
65
+ {"module" : "RMON2-MIB", "name" : "TimeFilter"},
66
+ {"module" : "ENTITY-MIB", "name" : "PhysicalIndex"},
67
+ {"module" : "IANA-ADDRESS-FAMILY-NUMBERS-MIB", "name" : "AddressFamilyNumbers"},
68
+ ),
69
+
70
+ "typedefs" : {
71
+ "PtopoGenAddr" : {
72
+ "basetype" : "OctetString",
73
+ "status" : "current",
74
+ "ranges" : [
75
+ {
76
+ "min" : "0",
77
+ "max" : "20"
78
+ },
79
+ ],
80
+ "range" : {
81
+ "min" : "0",
82
+ "max" : "20"
83
+ },
84
+ "description" :
85
+ """The value of an address.""",
86
+ },
87
+ "PtopoChassisIdType" : {
88
+ "basetype" : "Enumeration",
89
+ "status" : "current",
90
+ "chasIdEntPhysicalAlias" : {
91
+ "nodetype" : "namednumber",
92
+ "number" : "1"
93
+ },
94
+ "chasIdIfAlias" : {
95
+ "nodetype" : "namednumber",
96
+ "number" : "2"
97
+ },
98
+ "chasIdPortEntPhysicalAlias" : {
99
+ "nodetype" : "namednumber",
100
+ "number" : "3"
101
+ },
102
+ "chasIdMacAddress" : {
103
+ "nodetype" : "namednumber",
104
+ "number" : "4"
105
+ },
106
+ "chasIdPtopoGenAddr" : {
107
+ "nodetype" : "namednumber",
108
+ "number" : "5"
109
+ },
110
+ "description" :
111
+ """This TC describes the source of a chassis identifier.
112
+
113
+ The enumeration 'chasIdEntPhysicalAlias(1)' represents a
114
+ chassis identifier based on the value of entPhysicalAlias
115
+ for a chassis component (i.e., an entPhysicalClass value of
116
+ 'chassis(3)').
117
+
118
+ The enumeration 'chasIdIfAlias(2)' represents a chassis
119
+ identifier based on the value of ifAlias for an interface
120
+ on the containing chassis.
121
+
122
+ The enumeration 'chasIdPortEntPhysicalAlias(3)' represents
123
+ a chassis identifier based on the value of entPhysicalAlias
124
+ for a port or backplane component (i.e., entPhysicalClass
125
+ value of 'port(10)' or 'backplane(4)'), within the
126
+ containing chassis.
127
+
128
+ The enumeration 'chasIdMacAddress(4)' represents a chassis
129
+ identifier based on the value of a unicast source MAC
130
+ address (encoded in network byte order and IEEE 802.3
131
+ canonical bit order), of a port on the containing chassis.
132
+
133
+ The enumeration 'chasIdPtopoGenAddr(5)' represents a
134
+ chassis identifier based on a network address, associated
135
+ with a particular chassis. The encoded address is actually
136
+ composed of two fields. The first field is a single octet,
137
+ representing the IANA AddressFamilyNumbers value for the
138
+ specific address type, and the second field is the
139
+ PtopoGenAddr address value.""",
140
+ },
141
+ "PtopoChassisId" : {
142
+ "basetype" : "OctetString",
143
+ "status" : "current",
144
+ "ranges" : [
145
+ {
146
+ "min" : "1",
147
+ "max" : "32"
148
+ },
149
+ ],
150
+ "range" : {
151
+ "min" : "1",
152
+ "max" : "32"
153
+ },
154
+ "description" :
155
+ """This TC describes the format of a chassis identifier
156
+ string. Objects of this type are always used with an
157
+ associated PtopoChassisIdType object, which identifies the
158
+ format of the particular PtopoChassisId object instance.
159
+
160
+ If the associated PtopoChassisIdType object has a value of
161
+ 'chasIdEntPhysicalAlias(1)', then the octet string
162
+ identifies a particular instance of the entPhysicalAlias
163
+ object for a chassis component (i.e., an entPhysicalClass
164
+ value of 'chassis(3)').
165
+
166
+ If the associated PtopoChassisIdType object has a value of
167
+ 'chasIdIfAlias(2)', then the octet string identifies a
168
+ particular instance of the ifAlias object for an interface
169
+ on the containing chassis.
170
+
171
+ If the associated PtopoChassisIdType object has a value of
172
+ 'chasIdPortEntPhysicalAlias(3)', then the octet string
173
+ identifies a particular instance of the entPhysicalAlias
174
+ object for a port or backplane component within the
175
+ containing chassis.
176
+
177
+ If the associated PtopoChassisIdType object has a value of
178
+ 'chasIdMacAddress(4)', then this string identifies a
179
+ particular unicast source MAC address (encoded in network
180
+ byte order and IEEE 802.3 canonical bit order), of a port on
181
+ the containing chassis.
182
+
183
+ If the associated PtopoChassisIdType object has a value of
184
+ 'chasIdPtopoGenAddr(5)', then this string identifies a
185
+ particular network address, encoded in network byte order,
186
+ associated with one or more ports on the containing chassis.
187
+ The first octet contains the IANA Address Family Numbers
188
+ enumeration value for the specific address type, and octets
189
+ 2 through N contain the PtopoGenAddr address value in
190
+ network byte order.""",
191
+ },
192
+ "PtopoPortIdType" : {
193
+ "basetype" : "Enumeration",
194
+ "status" : "current",
195
+ "portIdIfAlias" : {
196
+ "nodetype" : "namednumber",
197
+ "number" : "1"
198
+ },
199
+ "portIdEntPhysicalAlias" : {
200
+ "nodetype" : "namednumber",
201
+ "number" : "2"
202
+ },
203
+ "portIdMacAddr" : {
204
+ "nodetype" : "namednumber",
205
+ "number" : "3"
206
+ },
207
+ "portIdPtopoGenAddr" : {
208
+ "nodetype" : "namednumber",
209
+ "number" : "4"
210
+ },
211
+ "description" :
212
+ """This TC describes the source of a particular type of port
213
+ identifier used in the PTOPO MIB.
214
+
215
+ The enumeration 'portIdIfAlias(1)' represents a port
216
+ identifier based on the ifAlias MIB object.
217
+
218
+
219
+
220
+ The enumeration 'portIdPortEntPhysicalAlias(2)' represents a
221
+ port identifier based on the value of entPhysicalAlias for a
222
+ port or backplane component (i.e., entPhysicalClass value of
223
+ 'port(10)' or 'backplane(4)'), within the containing
224
+ chassis.
225
+
226
+ The enumeration 'portIdMacAddr(3)' represents a port
227
+ identifier based on a unicast source MAC address, which has
228
+ been detected by the agent and associated with a particular
229
+ port.
230
+
231
+ The enumeration 'portIdPtopoGenAddr(4)' represents a port
232
+ identifier based on a network address, detected by the agent
233
+ and associated with a particular port.""",
234
+ },
235
+ "PtopoPortId" : {
236
+ "basetype" : "OctetString",
237
+ "status" : "current",
238
+ "ranges" : [
239
+ {
240
+ "min" : "1",
241
+ "max" : "32"
242
+ },
243
+ ],
244
+ "range" : {
245
+ "min" : "1",
246
+ "max" : "32"
247
+ },
248
+ "description" :
249
+ """This TC describes the format of a port identifier string.
250
+ Objects of this type are always used with an associated
251
+ PtopoPortIdType object, which identifies the format of the
252
+ particular PtopoPortId object instance.
253
+
254
+ If the associated PtopoPortIdType object has a value of
255
+ 'portIdIfAlias(1)', then the octet string identifies a
256
+ particular instance of the ifAlias object.
257
+
258
+ If the associated PtopoPortIdType object has a value of
259
+ 'portIdEntPhysicalAlias(2)', then the octet string
260
+ identifies a particular instance of the entPhysicalAlias
261
+ object for a port component (i.e., entPhysicalClass value of
262
+ 'port(10)').
263
+
264
+ If the associated PtopoPortIdType object has a value of
265
+ 'portIdMacAddr(3)', then this string identifies a particular
266
+ unicast source MAC address associated with the port.
267
+
268
+ If the associated PtopoPortIdType object has a value of
269
+ 'portIdPtopoGenAddr(4)', then this string identifies a
270
+ network address associated with the port. The first octet
271
+ contains the IANA AddressFamilyNumbers enumeration value for
272
+ the specific address type, and octets 2 through N contain
273
+
274
+
275
+ the PtopoGenAddr address value in network byte order.""",
276
+ },
277
+ "PtopoAddrSeenState" : {
278
+ "basetype" : "Enumeration",
279
+ "status" : "current",
280
+ "notUsed" : {
281
+ "nodetype" : "namednumber",
282
+ "number" : "1"
283
+ },
284
+ "unknown" : {
285
+ "nodetype" : "namednumber",
286
+ "number" : "2"
287
+ },
288
+ "oneAddr" : {
289
+ "nodetype" : "namednumber",
290
+ "number" : "3"
291
+ },
292
+ "multiAddr" : {
293
+ "nodetype" : "namednumber",
294
+ "number" : "4"
295
+ },
296
+ "description" :
297
+ """This TC describes the state of address detection for a
298
+ particular type of port identifier used in the PTOPO MIB.
299
+
300
+ The enumeration 'notUsed(1)' represents an entry for which
301
+ the particular MIB object is not applicable to the remote
302
+ connection endpoint,
303
+
304
+ The enumeration 'unknown(2)' represents an entry for which
305
+ the particular address collection state is not known.
306
+
307
+ The enumeration 'oneAddr(3)' represents an entry for which
308
+ exactly one source address (of the type indicated by the
309
+ particular MIB object), has been detected.
310
+
311
+ The enumeration 'multiAddr(4)' represents an entry for
312
+ which more than one source address (of the type indicated by
313
+ the particular MIB object), has been detected.
314
+
315
+ An agent is expected to set the initial state of the
316
+ PtopoAddrSeenState to 'notUsed(1)' or 'unknown(2)'.
317
+
318
+ Note that the PTOPO MIB does not restrict or specify the
319
+ means in which the PtopoAddrSeenState is known to an agent.
320
+ In particular, an agent may detect this information through
321
+ configuration data, or some means other than directly
322
+ monitoring all port traffic.""",
323
+ },
324
+ }, # typedefs
325
+
326
+ "nodes" : {
327
+ "ptopoMIB" : {
328
+ "nodetype" : "node",
329
+ "moduleName" : "PTOPO-MIB",
330
+ "oid" : "1.3.6.1.2.1.79",
331
+ "status" : "current",
332
+ }, # node
333
+ "ptopoMIBObjects" : {
334
+ "nodetype" : "node",
335
+ "moduleName" : "PTOPO-MIB",
336
+ "oid" : "1.3.6.1.2.1.79.1",
337
+ }, # node
338
+ "ptopoData" : {
339
+ "nodetype" : "node",
340
+ "moduleName" : "PTOPO-MIB",
341
+ "oid" : "1.3.6.1.2.1.79.1.1",
342
+ }, # node
343
+ "ptopoConnTable" : {
344
+ "nodetype" : "table",
345
+ "moduleName" : "PTOPO-MIB",
346
+ "oid" : "1.3.6.1.2.1.79.1.1.1",
347
+ "status" : "current",
348
+ "description" :
349
+ """This table contains one or more rows per physical network
350
+ connection known to this agent. The agent may wish to
351
+ ensure that only one ptopoConnEntry is present for each
352
+ local port, or it may choose to maintain multiple
353
+ ptopoConnEntries for the same local port.
354
+
355
+ Entries based on lower numbered identifier types are
356
+ preferred over higher numbered identifier types, i.e., lower
357
+ values of the ptopoConnRemoteChassisType and
358
+ ptopoConnRemotePortType objects.""",
359
+ }, # table
360
+ "ptopoConnEntry" : {
361
+ "nodetype" : "row",
362
+ "moduleName" : "PTOPO-MIB",
363
+ "oid" : "1.3.6.1.2.1.79.1.1.1.1",
364
+ "create" : "true",
365
+ "status" : "current",
366
+ "linkage" : [
367
+ "ptopoConnTimeMark",
368
+ "ptopoConnLocalChassis",
369
+ "ptopoConnLocalPort",
370
+ "ptopoConnIndex",
371
+ ],
372
+ "description" :
373
+ """Information about a particular physical network connection.
374
+ Entries may be created and deleted in this table, either
375
+ manually or by the agent, if a physical topology discovery
376
+ process is active.""",
377
+ }, # row
378
+ "ptopoConnTimeMark" : {
379
+ "nodetype" : "column",
380
+ "moduleName" : "PTOPO-MIB",
381
+ "oid" : "1.3.6.1.2.1.79.1.1.1.1.1",
382
+ "status" : "current",
383
+ "syntax" : {
384
+ "type" : { "module" :"RMON2-MIB", "name" : "TimeFilter"},
385
+ },
386
+ "access" : "noaccess",
387
+ "description" :
388
+ """A TimeFilter for this entry. See the TimeFilter textual
389
+ convention in RFC 2021 to see how this works.""",
390
+ }, # column
391
+ "ptopoConnLocalChassis" : {
392
+ "nodetype" : "column",
393
+ "moduleName" : "PTOPO-MIB",
394
+ "oid" : "1.3.6.1.2.1.79.1.1.1.1.2",
395
+ "status" : "current",
396
+ "syntax" : {
397
+ "type" : { "module" :"ENTITY-MIB", "name" : "PhysicalIndex"},
398
+ },
399
+ "access" : "noaccess",
400
+ "description" :
401
+ """The entPhysicalIndex value used to identify the chassis
402
+ component associated with the local connection endpoint.""",
403
+ }, # column
404
+ "ptopoConnLocalPort" : {
405
+ "nodetype" : "column",
406
+ "moduleName" : "PTOPO-MIB",
407
+ "oid" : "1.3.6.1.2.1.79.1.1.1.1.3",
408
+ "status" : "current",
409
+ "syntax" : {
410
+ "type" : { "module" :"ENTITY-MIB", "name" : "PhysicalIndex"},
411
+ },
412
+ "access" : "noaccess",
413
+ "description" :
414
+ """The entPhysicalIndex value used to identify the port
415
+ component associated with the local connection endpoint.""",
416
+ }, # column
417
+ "ptopoConnIndex" : {
418
+ "nodetype" : "column",
419
+ "moduleName" : "PTOPO-MIB",
420
+ "oid" : "1.3.6.1.2.1.79.1.1.1.1.4",
421
+ "status" : "current",
422
+ "syntax" : {
423
+ "type" : {
424
+ "basetype" : "Integer32",
425
+ "ranges" : [
426
+ {
427
+ "min" : "1",
428
+ "max" : "2147483647"
429
+ },
430
+ ],
431
+ "range" : {
432
+ "min" : "1",
433
+ "max" : "2147483647"
434
+ },
435
+ },
436
+ },
437
+ "access" : "noaccess",
438
+ "description" :
439
+ """This object represents an arbitrary local integer value
440
+ used by this agent to identify a particular connection
441
+ instance, unique only for the indicated local connection
442
+ endpoint.
443
+
444
+ A particular ptopoConnIndex value may be reused in the event
445
+ an entry is aged out and later re-learned with the same (or
446
+ different) remote chassis and port identifiers.
447
+
448
+ An agent is encouraged to assign monotonically increasing
449
+ index values to new entries, starting with one, after each
450
+
451
+
452
+ reboot. It is considered unlikely that the ptopoConnIndex
453
+ will wrap between reboots.""",
454
+ }, # column
455
+ "ptopoConnRemoteChassisType" : {
456
+ "nodetype" : "column",
457
+ "moduleName" : "PTOPO-MIB",
458
+ "oid" : "1.3.6.1.2.1.79.1.1.1.1.5",
459
+ "status" : "current",
460
+ "syntax" : {
461
+ "type" : { "module" :"PTOPO-MIB", "name" : "PtopoChassisIdType"},
462
+ },
463
+ "access" : "readwrite",
464
+ "description" :
465
+ """The type of encoding used to identify the chassis
466
+ associated with the remote connection endpoint.
467
+
468
+ This object may not be modified if the associated
469
+ ptopoConnRowStatus object has a value of active(1).""",
470
+ }, # column
471
+ "ptopoConnRemoteChassis" : {
472
+ "nodetype" : "column",
473
+ "moduleName" : "PTOPO-MIB",
474
+ "oid" : "1.3.6.1.2.1.79.1.1.1.1.6",
475
+ "status" : "current",
476
+ "syntax" : {
477
+ "type" : { "module" :"PTOPO-MIB", "name" : "PtopoChassisId"},
478
+ },
479
+ "access" : "readwrite",
480
+ "description" :
481
+ """The string value used to identify the chassis component
482
+ associated with the remote connection endpoint.
483
+
484
+ This object may not be modified if the associated
485
+ ptopoConnRowStatus object has a value of active(1).""",
486
+ }, # column
487
+ "ptopoConnRemotePortType" : {
488
+ "nodetype" : "column",
489
+ "moduleName" : "PTOPO-MIB",
490
+ "oid" : "1.3.6.1.2.1.79.1.1.1.1.7",
491
+ "status" : "current",
492
+ "syntax" : {
493
+ "type" : { "module" :"PTOPO-MIB", "name" : "PtopoPortIdType"},
494
+ },
495
+ "access" : "readwrite",
496
+ "description" :
497
+ """The type of port identifier encoding used in the associated
498
+ 'ptopoConnRemotePort' object.
499
+
500
+ This object may not be modified if the associated
501
+ ptopoConnRowStatus object has a value of active(1).""",
502
+ }, # column
503
+ "ptopoConnRemotePort" : {
504
+ "nodetype" : "column",
505
+ "moduleName" : "PTOPO-MIB",
506
+ "oid" : "1.3.6.1.2.1.79.1.1.1.1.8",
507
+ "status" : "current",
508
+ "syntax" : {
509
+ "type" : { "module" :"PTOPO-MIB", "name" : "PtopoPortId"},
510
+ },
511
+ "access" : "readwrite",
512
+ "description" :
513
+ """The string value used to identify the port component
514
+ associated with the remote connection endpoint.
515
+
516
+
517
+
518
+ This object may not be modified if the associated
519
+ ptopoConnRowStatus object has a value of active(1).""",
520
+ }, # column
521
+ "ptopoConnDiscAlgorithm" : {
522
+ "nodetype" : "column",
523
+ "moduleName" : "PTOPO-MIB",
524
+ "oid" : "1.3.6.1.2.1.79.1.1.1.1.9",
525
+ "status" : "current",
526
+ "syntax" : {
527
+ "type" : { "module" :"SNMPv2-TC", "name" : "AutonomousType"},
528
+ },
529
+ "access" : "readonly",
530
+ "description" :
531
+ """An indication of the algorithm used to discover the
532
+ information contained in this conceptual row.
533
+
534
+ A value of ptopoDiscoveryLocal indicates this entry was
535
+ configured by the local agent, without use of a discovery
536
+ protocol.
537
+
538
+ A value of { 0 0 } indicates this entry was created manually
539
+ by an NMS via the associated RowStatus object. """,
540
+ }, # column
541
+ "ptopoConnAgentNetAddrType" : {
542
+ "nodetype" : "column",
543
+ "moduleName" : "PTOPO-MIB",
544
+ "oid" : "1.3.6.1.2.1.79.1.1.1.1.10",
545
+ "status" : "current",
546
+ "syntax" : {
547
+ "type" : { "module" :"IANA-ADDRESS-FAMILY-NUMBERS-MIB", "name" : "AddressFamilyNumbers"},
548
+ },
549
+ "access" : "readwrite",
550
+ "description" :
551
+ """This network address type of the associated
552
+ ptopoConnNetAddr object, unless that object contains a zero
553
+ length string. In such a case, an NMS application should
554
+ ignore any returned value for this object.
555
+
556
+ This object may not be modified if the associated
557
+ ptopoConnRowStatus object has a value of active(1).""",
558
+ }, # column
559
+ "ptopoConnAgentNetAddr" : {
560
+ "nodetype" : "column",
561
+ "moduleName" : "PTOPO-MIB",
562
+ "oid" : "1.3.6.1.2.1.79.1.1.1.1.11",
563
+ "status" : "current",
564
+ "syntax" : {
565
+ "type" : { "module" :"PTOPO-MIB", "name" : "PtopoGenAddr"},
566
+ },
567
+ "access" : "readwrite",
568
+ "description" :
569
+ """This object identifies a network address which may be used
570
+ to reach an SNMP agent entity containing information for the
571
+ chassis and port components represented by the associated
572
+ 'ptopoConnRemoteChassis' and 'ptopoConnRemotePort' objects.
573
+ If no such address is known, then this object shall contain
574
+ an empty string.
575
+
576
+ This object may not be modified if the associated
577
+ ptopoConnRowStatus object has a value of active(1).""",
578
+ }, # column
579
+ "ptopoConnMultiMacSASeen" : {
580
+ "nodetype" : "column",
581
+ "moduleName" : "PTOPO-MIB",
582
+ "oid" : "1.3.6.1.2.1.79.1.1.1.1.12",
583
+ "status" : "current",
584
+ "syntax" : {
585
+ "type" : { "module" :"PTOPO-MIB", "name" : "PtopoAddrSeenState"},
586
+ },
587
+ "access" : "readonly",
588
+ "description" :
589
+ """This object indicates if multiple unicast source MAC
590
+ addresses have been detected by the agent from the remote
591
+ connection endpoint, since the creation of this entry.
592
+
593
+ If this entry has an associated ptopoConnRemoteChassisType
594
+ and/or ptopoConnRemotePortType value other than
595
+ 'portIdMacAddr(3)', then the value 'notUsed(1)' is returned.
596
+
597
+ Otherwise, one of the following conditions must be true:
598
+
599
+ If the agent has not yet detected any unicast source MAC
600
+ addresses from the remote port, then the value 'unknown(2)'
601
+ is returned.
602
+
603
+ If the agent has detected exactly one unicast source MAC
604
+ address from the remote port, then the value 'oneAddr(3)' is
605
+ returned.
606
+
607
+ If the agent has detected more than one unicast source MAC
608
+ address from the remote port, then the value 'multiAddr(4)'
609
+ is returned.""",
610
+ }, # column
611
+ "ptopoConnMultiNetSASeen" : {
612
+ "nodetype" : "column",
613
+ "moduleName" : "PTOPO-MIB",
614
+ "oid" : "1.3.6.1.2.1.79.1.1.1.1.13",
615
+ "status" : "current",
616
+ "syntax" : {
617
+ "type" : { "module" :"PTOPO-MIB", "name" : "PtopoAddrSeenState"},
618
+ },
619
+ "access" : "readonly",
620
+ "description" :
621
+ """This object indicates if multiple network layer source
622
+ addresses have been detected by the agent from the remote
623
+ connection endpoint, since the creation of this entry.
624
+
625
+ If this entry has an associated ptopoConnRemoteChassisType
626
+ or ptopoConnRemotePortType value other than
627
+ 'portIdGenAddr(4)' then the value 'notUsed(1)' is returned.
628
+
629
+ Otherwise, one of the following conditions must be true:
630
+
631
+ If the agent has not yet detected any network source
632
+ addresses of the appropriate type from the remote port, then
633
+ the value 'unknown(2)' is returned.
634
+
635
+
636
+ If the agent has detected exactly one network source address
637
+ of the appropriate type from the remote port, then the value
638
+ 'oneAddr(3)' is returned.
639
+
640
+ If the agent has detected more than one network source
641
+ address (of the same appropriate type) from the remote port,
642
+ this the value 'multiAddr(4)' is returned.""",
643
+ }, # column
644
+ "ptopoConnIsStatic" : {
645
+ "nodetype" : "column",
646
+ "moduleName" : "PTOPO-MIB",
647
+ "oid" : "1.3.6.1.2.1.79.1.1.1.1.14",
648
+ "status" : "current",
649
+ "syntax" : {
650
+ "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
651
+ },
652
+ "access" : "readwrite",
653
+ "default" : "false",
654
+ "description" :
655
+ """This object identifies static ptopoConnEntries. If this
656
+ object has the value 'true(1)', then this entry is not
657
+ subject to any age-out mechanisms implemented by the agent.
658
+
659
+ If this object has the value 'false(2)', then this entry is
660
+ subject to all age-out mechanisms implemented by the agent.
661
+
662
+ This object may not be modified if the associated
663
+ ptopoConnRowStatus object has a value of active(1).""",
664
+ }, # column
665
+ "ptopoConnLastVerifyTime" : {
666
+ "nodetype" : "column",
667
+ "moduleName" : "PTOPO-MIB",
668
+ "oid" : "1.3.6.1.2.1.79.1.1.1.1.15",
669
+ "status" : "current",
670
+ "syntax" : {
671
+ "type" : { "module" :"SNMPv2-TC", "name" : "TimeStamp"},
672
+ },
673
+ "access" : "readonly",
674
+ "description" :
675
+ """If the associated value of ptopoConnIsStatic is equal to
676
+ 'false(2)', then this object contains the value of sysUpTime
677
+ at the time the conceptual row was last verified by the
678
+ agent, e.g., via reception of a topology protocol message,
679
+ pertaining to the associated remote chassis and port.
680
+
681
+ If the associated value of ptopoConnIsStatic is equal to
682
+ 'true(1)', then this object shall contain the value of
683
+ sysUpTime at the time this entry was last activated (i.e.,
684
+ ptopoConnRowStatus set to 'active(1)').""",
685
+ }, # column
686
+ "ptopoConnRowStatus" : {
687
+ "nodetype" : "column",
688
+ "moduleName" : "PTOPO-MIB",
689
+ "oid" : "1.3.6.1.2.1.79.1.1.1.1.16",
690
+ "status" : "current",
691
+ "syntax" : {
692
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
693
+ },
694
+ "access" : "readwrite",
695
+ "description" :
696
+ """The status of this conceptual row.""",
697
+ }, # column
698
+ "ptopoGeneral" : {
699
+ "nodetype" : "node",
700
+ "moduleName" : "PTOPO-MIB",
701
+ "oid" : "1.3.6.1.2.1.79.1.2",
702
+ }, # node
703
+ "ptopoLastChangeTime" : {
704
+ "nodetype" : "scalar",
705
+ "moduleName" : "PTOPO-MIB",
706
+ "oid" : "1.3.6.1.2.1.79.1.2.1",
707
+ "status" : "current",
708
+ "syntax" : {
709
+ "type" : { "module" :"SNMPv2-TC", "name" : "TimeStamp"},
710
+ },
711
+ "access" : "readonly",
712
+ "description" :
713
+ """The value of sysUpTime at the time a conceptual row is
714
+ created, modified, or deleted in the ptopoConnTable.
715
+
716
+ An NMS can use this object to reduce polling of the
717
+ ptopoData group objects.""",
718
+ }, # scalar
719
+ "ptopoConnTabInserts" : {
720
+ "nodetype" : "scalar",
721
+ "moduleName" : "PTOPO-MIB",
722
+ "oid" : "1.3.6.1.2.1.79.1.2.2",
723
+ "status" : "current",
724
+ "syntax" : {
725
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
726
+ },
727
+ "access" : "readonly",
728
+ "units" : "table entries",
729
+ "description" :
730
+ """The number of times an entry has been inserted into the
731
+ ptopoConnTable.""",
732
+ }, # scalar
733
+ "ptopoConnTabDeletes" : {
734
+ "nodetype" : "scalar",
735
+ "moduleName" : "PTOPO-MIB",
736
+ "oid" : "1.3.6.1.2.1.79.1.2.3",
737
+ "status" : "current",
738
+ "syntax" : {
739
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
740
+ },
741
+ "access" : "readonly",
742
+ "units" : "table entries",
743
+ "description" :
744
+ """The number of times an entry has been deleted from the
745
+ ptopoConnTable.""",
746
+ }, # scalar
747
+ "ptopoConnTabDrops" : {
748
+ "nodetype" : "scalar",
749
+ "moduleName" : "PTOPO-MIB",
750
+ "oid" : "1.3.6.1.2.1.79.1.2.4",
751
+ "status" : "current",
752
+ "syntax" : {
753
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
754
+ },
755
+ "access" : "readonly",
756
+ "units" : "table entries",
757
+ "description" :
758
+ """The number of times an entry would have been added to the
759
+ ptopoConnTable, (e.g., via information learned from a
760
+ topology protocol), but was not because of insufficient
761
+ resources.""",
762
+ }, # scalar
763
+ "ptopoConnTabAgeouts" : {
764
+ "nodetype" : "scalar",
765
+ "moduleName" : "PTOPO-MIB",
766
+ "oid" : "1.3.6.1.2.1.79.1.2.5",
767
+ "status" : "current",
768
+ "syntax" : {
769
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
770
+ },
771
+ "access" : "readonly",
772
+ "description" :
773
+ """The number of times an entry has been deleted from the
774
+ ptopoConnTable because the information timeliness interval
775
+ for that entry has expired.""",
776
+ }, # scalar
777
+ "ptopoConfig" : {
778
+ "nodetype" : "node",
779
+ "moduleName" : "PTOPO-MIB",
780
+ "oid" : "1.3.6.1.2.1.79.1.3",
781
+ }, # node
782
+ "ptopoConfigTrapInterval" : {
783
+ "nodetype" : "scalar",
784
+ "moduleName" : "PTOPO-MIB",
785
+ "oid" : "1.3.6.1.2.1.79.1.3.1",
786
+ "status" : "current",
787
+ "syntax" : {
788
+ "type" : {
789
+ "basetype" : "Integer32",
790
+ "ranges" : [
791
+ {
792
+ "min" : "0",
793
+ "max" : "0"
794
+ },
795
+ {
796
+ "min" : "5",
797
+ "max" : "3600"
798
+ },
799
+ ],
800
+ "range" : {
801
+ "min" : "0",
802
+ "max" : "3600"
803
+ },
804
+ },
805
+ },
806
+ "access" : "readwrite",
807
+ "default" : "0",
808
+ "units" : "seconds",
809
+ "description" :
810
+ """This object controls the transmission of PTOPO
811
+ notifications.
812
+
813
+ If this object has a value of zero, then no
814
+ ptopoConfigChange notifications will be transmitted by the
815
+ agent.
816
+
817
+ If this object has a non-zero value, then the agent must not
818
+ generate more than one ptopoConfigChange trap-event in the
819
+ indicated period, where a 'trap-event' is the transmission
820
+ of a single notification PDU type to a list of notification
821
+ destinations. If additional configuration changes occur
822
+ within the indicated throttling period, then these trap-
823
+ events must be suppressed by the agent. An NMS should
824
+ periodically check the value of ptopoLastChangeTime to
825
+ detect any missed ptopoConfigChange trap-events, e.g. due to
826
+ throttling or transmission loss.
827
+
828
+
829
+
830
+ If notification transmission is enabled, the suggested
831
+ default throttling period is 60 seconds, but transmission
832
+ should be disabled by default.
833
+
834
+ If the agent is capable of storing non-volatile
835
+ configuration, then the value of this object must be
836
+ restored after a re-initialization of the management
837
+ system.""",
838
+ }, # scalar
839
+ "ptopoConfigMaxHoldTime" : {
840
+ "nodetype" : "scalar",
841
+ "moduleName" : "PTOPO-MIB",
842
+ "oid" : "1.3.6.1.2.1.79.1.3.2",
843
+ "status" : "current",
844
+ "syntax" : {
845
+ "type" : {
846
+ "basetype" : "Integer32",
847
+ "ranges" : [
848
+ {
849
+ "min" : "1",
850
+ "max" : "2147483647"
851
+ },
852
+ ],
853
+ "range" : {
854
+ "min" : "1",
855
+ "max" : "2147483647"
856
+ },
857
+ },
858
+ },
859
+ "access" : "readwrite",
860
+ "default" : "300",
861
+ "units" : "seconds",
862
+ "description" :
863
+ """This object specifies the desired time interval for which
864
+ an agent will maintain dynamic ptopoConnEntries.
865
+
866
+ After the specified number of seconds since the last time an
867
+ entry was verified, in the absence of new verification
868
+ (e.g., receipt of a topology protocol message), the agent
869
+ shall remove the entry. Note that entries may not always be
870
+ removed immediately, but may possibly be removed at periodic
871
+ garbage collection intervals.
872
+ This object only affects dynamic ptopoConnEntries, i.e. for
873
+ which ptopoConnIsStatic equals 'false(2)'. Static entries
874
+ are not aged out.
875
+
876
+ Note that dynamic ptopoConnEntries may also be removed by
877
+ the agent due to the expired timeliness of learned topology
878
+ information (e.g., timeliness interval for a remote port
879
+ expires). The actual age-out interval for a given entry is
880
+ defined by the following formula:
881
+
882
+ age-out-time =
883
+ min(ptopoConfigMaxHoldTime, <entry-specific hold-time>)
884
+
885
+ where <entry-specific hold-time> is determined by the
886
+ discovery algorithm, and may be different for each entry.""",
887
+ }, # scalar
888
+ "ptopoMIBNotifications" : {
889
+ "nodetype" : "node",
890
+ "moduleName" : "PTOPO-MIB",
891
+ "oid" : "1.3.6.1.2.1.79.2",
892
+ }, # node
893
+ "ptopoMIBTrapPrefix" : {
894
+ "nodetype" : "node",
895
+ "moduleName" : "PTOPO-MIB",
896
+ "oid" : "1.3.6.1.2.1.79.2.0",
897
+ }, # node
898
+ "ptopoRegistrationPoints" : {
899
+ "nodetype" : "node",
900
+ "moduleName" : "PTOPO-MIB",
901
+ "oid" : "1.3.6.1.2.1.79.3",
902
+ }, # node
903
+ "ptopoDiscoveryMechanisms" : {
904
+ "nodetype" : "node",
905
+ "moduleName" : "PTOPO-MIB",
906
+ "oid" : "1.3.6.1.2.1.79.3.1",
907
+ }, # node
908
+ "ptopoDiscoveryLocal" : {
909
+ "nodetype" : "node",
910
+ "moduleName" : "PTOPO-MIB",
911
+ "oid" : "1.3.6.1.2.1.79.3.1.1",
912
+ }, # node
913
+ "ptopoConformance" : {
914
+ "nodetype" : "node",
915
+ "moduleName" : "PTOPO-MIB",
916
+ "oid" : "1.3.6.1.2.1.79.4",
917
+ }, # node
918
+ "ptopoCompliances" : {
919
+ "nodetype" : "node",
920
+ "moduleName" : "PTOPO-MIB",
921
+ "oid" : "1.3.6.1.2.1.79.4.1",
922
+ }, # node
923
+ "ptopoGroups" : {
924
+ "nodetype" : "node",
925
+ "moduleName" : "PTOPO-MIB",
926
+ "oid" : "1.3.6.1.2.1.79.4.2",
927
+ }, # node
928
+ }, # nodes
929
+
930
+ "notifications" : {
931
+ "ptopoConfigChange" : {
932
+ "nodetype" : "notification",
933
+ "moduleName" : "PTOPO-MIB",
934
+ "oid" : "1.3.6.1.2.1.79.2.0.1",
935
+ "status" : "current",
936
+ "objects" : {
937
+ "ptopoConnTabInserts" : {
938
+ "nodetype" : "object",
939
+ "module" : "PTOPO-MIB"
940
+ },
941
+ "ptopoConnTabDeletes" : {
942
+ "nodetype" : "object",
943
+ "module" : "PTOPO-MIB"
944
+ },
945
+ "ptopoConnTabDrops" : {
946
+ "nodetype" : "object",
947
+ "module" : "PTOPO-MIB"
948
+ },
949
+ "ptopoConnTabAgeouts" : {
950
+ "nodetype" : "object",
951
+ "module" : "PTOPO-MIB"
952
+ },
953
+ },
954
+ "description" :
955
+ """A ptopoConfigChange notification is sent when the value of
956
+ ptopoLastChangeTime changes. It can be utilized by an NMS to
957
+ trigger physical topology table maintenance polls.
958
+
959
+ Note that transmission of ptopoConfigChange notifications
960
+ are throttled by the agent, as specified by the
961
+ 'ptopoConfigTrapInterval' object.""",
962
+ }, # notification
963
+ }, # notifications
964
+
965
+ "groups" : {
966
+ "ptopoDataGroup" : {
967
+ "nodetype" : "group",
968
+ "moduleName" : "PTOPO-MIB",
969
+ "oid" : "1.3.6.1.2.1.79.4.2.1",
970
+ "status" : "current",
971
+ "members" : {
972
+ "ptopoConnRemoteChassisType" : {
973
+ "nodetype" : "member",
974
+ "module" : "PTOPO-MIB"
975
+ },
976
+ "ptopoConnRemoteChassis" : {
977
+ "nodetype" : "member",
978
+ "module" : "PTOPO-MIB"
979
+ },
980
+ "ptopoConnRemotePortType" : {
981
+ "nodetype" : "member",
982
+ "module" : "PTOPO-MIB"
983
+ },
984
+ "ptopoConnRemotePort" : {
985
+ "nodetype" : "member",
986
+ "module" : "PTOPO-MIB"
987
+ },
988
+ "ptopoConnDiscAlgorithm" : {
989
+ "nodetype" : "member",
990
+ "module" : "PTOPO-MIB"
991
+ },
992
+ "ptopoConnAgentNetAddrType" : {
993
+ "nodetype" : "member",
994
+ "module" : "PTOPO-MIB"
995
+ },
996
+ "ptopoConnAgentNetAddr" : {
997
+ "nodetype" : "member",
998
+ "module" : "PTOPO-MIB"
999
+ },
1000
+ "ptopoConnMultiMacSASeen" : {
1001
+ "nodetype" : "member",
1002
+ "module" : "PTOPO-MIB"
1003
+ },
1004
+ "ptopoConnMultiNetSASeen" : {
1005
+ "nodetype" : "member",
1006
+ "module" : "PTOPO-MIB"
1007
+ },
1008
+ "ptopoConnIsStatic" : {
1009
+ "nodetype" : "member",
1010
+ "module" : "PTOPO-MIB"
1011
+ },
1012
+ "ptopoConnLastVerifyTime" : {
1013
+ "nodetype" : "member",
1014
+ "module" : "PTOPO-MIB"
1015
+ },
1016
+ "ptopoConnRowStatus" : {
1017
+ "nodetype" : "member",
1018
+ "module" : "PTOPO-MIB"
1019
+ },
1020
+ }, # members
1021
+ "description" :
1022
+ """The collection of objects which are used to represent
1023
+ physical topology information for which a single agent
1024
+ provides management information.
1025
+
1026
+ This group is mandatory for all implementations of the PTOPO
1027
+ MIB.""",
1028
+ }, # group
1029
+ "ptopoGeneralGroup" : {
1030
+ "nodetype" : "group",
1031
+ "moduleName" : "PTOPO-MIB",
1032
+ "oid" : "1.3.6.1.2.1.79.4.2.2",
1033
+ "status" : "current",
1034
+ "members" : {
1035
+ "ptopoLastChangeTime" : {
1036
+ "nodetype" : "member",
1037
+ "module" : "PTOPO-MIB"
1038
+ },
1039
+ "ptopoConnTabInserts" : {
1040
+ "nodetype" : "member",
1041
+ "module" : "PTOPO-MIB"
1042
+ },
1043
+ "ptopoConnTabDeletes" : {
1044
+ "nodetype" : "member",
1045
+ "module" : "PTOPO-MIB"
1046
+ },
1047
+ "ptopoConnTabDrops" : {
1048
+ "nodetype" : "member",
1049
+ "module" : "PTOPO-MIB"
1050
+ },
1051
+ "ptopoConnTabAgeouts" : {
1052
+ "nodetype" : "member",
1053
+ "module" : "PTOPO-MIB"
1054
+ },
1055
+ }, # members
1056
+ "description" :
1057
+ """The collection of objects which are used to report the
1058
+ general status of the PTOPO MIB implementation.
1059
+
1060
+ This group is mandatory for all agents which implement the
1061
+ PTOPO MIB.""",
1062
+ }, # group
1063
+ "ptopoConfigGroup" : {
1064
+ "nodetype" : "group",
1065
+ "moduleName" : "PTOPO-MIB",
1066
+ "oid" : "1.3.6.1.2.1.79.4.2.3",
1067
+ "status" : "current",
1068
+ "members" : {
1069
+ "ptopoConfigTrapInterval" : {
1070
+ "nodetype" : "member",
1071
+ "module" : "PTOPO-MIB"
1072
+ },
1073
+ "ptopoConfigMaxHoldTime" : {
1074
+ "nodetype" : "member",
1075
+ "module" : "PTOPO-MIB"
1076
+ },
1077
+ }, # members
1078
+ "description" :
1079
+ """The collection of objects which are used to configure the
1080
+ PTOPO MIB implementation behavior.
1081
+
1082
+ This group is mandatory for agents which implement the PTOPO
1083
+ MIB.""",
1084
+ }, # group
1085
+ "ptopoNotificationsGroup" : {
1086
+ "nodetype" : "group",
1087
+ "moduleName" : "PTOPO-MIB",
1088
+ "oid" : "1.3.6.1.2.1.79.4.2.4",
1089
+ "status" : "current",
1090
+ "members" : {
1091
+ "ptopoConfigChange" : {
1092
+ "nodetype" : "member",
1093
+ "module" : "PTOPO-MIB"
1094
+ },
1095
+ }, # members
1096
+ "description" :
1097
+ """The collection of notifications used to indicate PTOPO MIB
1098
+ data consistency and general status information.
1099
+
1100
+ This group is mandatory for agents which implement the PTOPO
1101
+ MIB.""",
1102
+ }, # group
1103
+ }, # groups
1104
+
1105
+ "compliances" : {
1106
+ "ptopoCompliance" : {
1107
+ "nodetype" : "compliance",
1108
+ "moduleName" : "PTOPO-MIB",
1109
+ "oid" : "1.3.6.1.2.1.79.4.1.1",
1110
+ "status" : "current",
1111
+ "description" :
1112
+ """The compliance statement for SNMP entities which implement
1113
+ the PTOPO MIB.""",
1114
+ "requires" : {
1115
+ "ptopoDataGroup" : {
1116
+ "nodetype" : "mandatory",
1117
+ "module" : "PTOPO-MIB"
1118
+ },
1119
+ "ptopoGeneralGroup" : {
1120
+ "nodetype" : "mandatory",
1121
+ "module" : "PTOPO-MIB"
1122
+ },
1123
+ "ptopoConfigGroup" : {
1124
+ "nodetype" : "mandatory",
1125
+ "module" : "PTOPO-MIB"
1126
+ },
1127
+ "ptopoNotificationsGroup" : {
1128
+ "nodetype" : "mandatory",
1129
+ "module" : "PTOPO-MIB"
1130
+ },
1131
+ }, # requires
1132
+ }, # compliance
1133
+ }, # compliances
1134
+
1135
+ }