logstash-integration-snmp 4.0.0-java

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (324) hide show
  1. checksums.yaml +7 -0
  2. data/CHANGELOG.md +23 -0
  3. data/CONTRIBUTORS +20 -0
  4. data/Gemfile +11 -0
  5. data/LICENSE +202 -0
  6. data/README.md +89 -0
  7. data/VERSION +1 -0
  8. data/docs/index.asciidoc +202 -0
  9. data/docs/input-snmp.asciidoc +524 -0
  10. data/docs/input-snmptrap.asciidoc +392 -0
  11. data/lib/logstash/inputs/snmp.rb +369 -0
  12. data/lib/logstash/inputs/snmptrap.rb +190 -0
  13. data/lib/logstash/plugin_mixins/snmp/common.rb +197 -0
  14. data/lib/logstash-integration-snmp_jars.rb +6 -0
  15. data/lib/mibs/ietf/ACCOUNTING-CONTROL-MIB.dic +1316 -0
  16. data/lib/mibs/ietf/ADSL-LINE-EXT-MIB.dic +1724 -0
  17. data/lib/mibs/ietf/ADSL-LINE-MIB.dic +7297 -0
  18. data/lib/mibs/ietf/ADSL-TC-MIB.dic +160 -0
  19. data/lib/mibs/ietf/ADSL2-LINE-MIB.dic +8663 -0
  20. data/lib/mibs/ietf/ADSL2-LINE-TC-MIB.dic +1462 -0
  21. data/lib/mibs/ietf/AGENTX-MIB.dic +817 -0
  22. data/lib/mibs/ietf/AGGREGATE-MIB.dic +708 -0
  23. data/lib/mibs/ietf/ALARM-MIB.dic +1734 -0
  24. data/lib/mibs/ietf/APM-MIB.dic +2870 -0
  25. data/lib/mibs/ietf/APPC-MIB.dic +8687 -0
  26. data/lib/mibs/ietf/APPLETALK-MIB.dic +4399 -0
  27. data/lib/mibs/ietf/APPLICATION-MIB.dic +3750 -0
  28. data/lib/mibs/ietf/APPN-DLUR-MIB.dic +972 -0
  29. data/lib/mibs/ietf/APPN-MIB.dic +9364 -0
  30. data/lib/mibs/ietf/APPN-TRAP-MIB.dic +664 -0
  31. data/lib/mibs/ietf/APS-MIB.dic +2430 -0
  32. data/lib/mibs/ietf/ARC-MIB.dic +552 -0
  33. data/lib/mibs/ietf/ATM-ACCOUNTING-INFORMATION-MIB.dic +816 -0
  34. data/lib/mibs/ietf/ATM-MIB.dic +4104 -0
  35. data/lib/mibs/ietf/ATM-TC-MIB.dic +914 -0
  36. data/lib/mibs/ietf/ATM2-MIB.dic +4715 -0
  37. data/lib/mibs/ietf/BFD-STD-MIB.dic +2367 -0
  38. data/lib/mibs/ietf/BFD-TC-STD-MIB.dic +202 -0
  39. data/lib/mibs/ietf/BGP4-MIB.dic +1931 -0
  40. data/lib/mibs/ietf/BLDG-HVAC-MIB.dic +812 -0
  41. data/lib/mibs/ietf/BRIDGE-MIB.dic +2257 -0
  42. data/lib/mibs/ietf/CAPWAP-BASE-MIB.dic +4128 -0
  43. data/lib/mibs/ietf/CAPWAP-DOT11-MIB.dic +482 -0
  44. data/lib/mibs/ietf/CHARACTER-MIB.dic +1140 -0
  45. data/lib/mibs/ietf/CIRCUIT-IF-MIB.dic +493 -0
  46. data/lib/mibs/ietf/CLNS-MIB.dic +1702 -0
  47. data/lib/mibs/ietf/COFFEE-POT-MIB.dic +282 -0
  48. data/lib/mibs/ietf/COPS-CLIENT-MIB.dic +1270 -0
  49. data/lib/mibs/ietf/DECNET-PHIV-MIB.dic +5837 -0
  50. data/lib/mibs/ietf/DIAL-CONTROL-MIB.dic +2139 -0
  51. data/lib/mibs/ietf/DIFFSERV-CONFIG-MIB.dic +378 -0
  52. data/lib/mibs/ietf/DIFFSERV-MIB.dic +5073 -0
  53. data/lib/mibs/ietf/DIRECTORY-SERVER-MIB.dic +1041 -0
  54. data/lib/mibs/ietf/DISMAN-EVENT-MIB.dic +3151 -0
  55. data/lib/mibs/ietf/DISMAN-EXPRESSION-MIB.dic +1716 -0
  56. data/lib/mibs/ietf/DISMAN-NSLOOKUP-MIB.dic +698 -0
  57. data/lib/mibs/ietf/DISMAN-PING-MIB.dic +2635 -0
  58. data/lib/mibs/ietf/DISMAN-SCHEDULE-MIB.dic +1744 -0
  59. data/lib/mibs/ietf/DISMAN-SCRIPT-MIB.dic +2820 -0
  60. data/lib/mibs/ietf/DISMAN-TRACEROUTE-MIB.dic +3239 -0
  61. data/lib/mibs/ietf/DLSW-MIB.dic +5635 -0
  62. data/lib/mibs/ietf/DNS-RESOLVER-MIB.dic +1765 -0
  63. data/lib/mibs/ietf/DNS-SERVER-MIB.dic +1593 -0
  64. data/lib/mibs/ietf/DOCS-BPI-MIB.dic +2634 -0
  65. data/lib/mibs/ietf/DOCS-CABLE-DEVICE-MIB.dic +5042 -0
  66. data/lib/mibs/ietf/DOCS-IETF-BPI2-MIB.dic +5478 -0
  67. data/lib/mibs/ietf/DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB.dic +2447 -0
  68. data/lib/mibs/ietf/DOCS-IETF-QOS-MIB.dic +4886 -0
  69. data/lib/mibs/ietf/DOCS-IETF-SUBMGT-MIB.dic +1331 -0
  70. data/lib/mibs/ietf/DOCS-IF-MIB.dic +7980 -0
  71. data/lib/mibs/ietf/DOT12-IF-MIB.dic +1066 -0
  72. data/lib/mibs/ietf/DOT12-RPTR-MIB.dic +2669 -0
  73. data/lib/mibs/ietf/DOT3-EPON-MIB.dic +3297 -0
  74. data/lib/mibs/ietf/DOT3-OAM-MIB.dic +2830 -0
  75. data/lib/mibs/ietf/DS0-MIB.dic +466 -0
  76. data/lib/mibs/ietf/DS0BUNDLE-MIB.dic +468 -0
  77. data/lib/mibs/ietf/DS1-MIB.dic +4890 -0
  78. data/lib/mibs/ietf/DS3-MIB.dic +2719 -0
  79. data/lib/mibs/ietf/DSA-MIB.dic +888 -0
  80. data/lib/mibs/ietf/DSMON-MIB.dic +6177 -0
  81. data/lib/mibs/ietf/DVB-RCS-MIB.dic +5764 -0
  82. data/lib/mibs/ietf/EBN-MIB.dic +1026 -0
  83. data/lib/mibs/ietf/EFM-CU-MIB.dic +4335 -0
  84. data/lib/mibs/ietf/ENTITY-MIB.dic +2235 -0
  85. data/lib/mibs/ietf/ENTITY-SENSOR-MIB.dic +653 -0
  86. data/lib/mibs/ietf/ENTITY-STATE-MIB.dic +457 -0
  87. data/lib/mibs/ietf/ENTITY-STATE-TC-MIB.dic +260 -0
  88. data/lib/mibs/ietf/ETHER-CHIPSET-MIB.dic +787 -0
  89. data/lib/mibs/ietf/EtherLike-MIB.dic +2548 -0
  90. data/lib/mibs/ietf/FC-MGMT-MIB.dic +3465 -0
  91. data/lib/mibs/ietf/FCIP-MGMT-MIB.dic +1596 -0
  92. data/lib/mibs/ietf/FDDI-SMT73-MIB.dic +3378 -0
  93. data/lib/mibs/ietf/FIBRE-CHANNEL-FE-MIB.dic +2504 -0
  94. data/lib/mibs/ietf/FLOAT-TC-MIB.dic +128 -0
  95. data/lib/mibs/ietf/FLOW-METER-MIB.dic +3201 -0
  96. data/lib/mibs/ietf/FORCES-MIB.dic +598 -0
  97. data/lib/mibs/ietf/FR-ATM-PVC-SERVICE-IWF-MIB.dic +1601 -0
  98. data/lib/mibs/ietf/FR-MFR-MIB.dic +1351 -0
  99. data/lib/mibs/ietf/FRAME-RELAY-DTE-MIB.dic +1688 -0
  100. data/lib/mibs/ietf/FRNETSERV-MIB.dic +3940 -0
  101. data/lib/mibs/ietf/FRSLD-MIB.dic +2580 -0
  102. data/lib/mibs/ietf/Finisher-MIB.dic +1416 -0
  103. data/lib/mibs/ietf/GMPLS-LABEL-STD-MIB.dic +965 -0
  104. data/lib/mibs/ietf/GMPLS-LSR-STD-MIB.dic +693 -0
  105. data/lib/mibs/ietf/GMPLS-TC-STD-MIB.dic +180 -0
  106. data/lib/mibs/ietf/GMPLS-TE-STD-MIB.dic +2542 -0
  107. data/lib/mibs/ietf/GSMP-MIB.dic +2468 -0
  108. data/lib/mibs/ietf/HC-ALARM-MIB.dic +1050 -0
  109. data/lib/mibs/ietf/HC-PerfHist-TC-MIB.dic +310 -0
  110. data/lib/mibs/ietf/HC-RMON-MIB.dic +4456 -0
  111. data/lib/mibs/ietf/HDSL2-SHDSL-LINE-MIB.dic +3955 -0
  112. data/lib/mibs/ietf/HOST-RESOURCES-MIB.dic +2453 -0
  113. data/lib/mibs/ietf/HPR-IP-MIB.dic +640 -0
  114. data/lib/mibs/ietf/HPR-MIB.dic +1959 -0
  115. data/lib/mibs/ietf/IANA-ITU-ALARM-TC-MIB.dic +936 -0
  116. data/lib/mibs/ietf/IF-CAP-STACK-MIB.dic +356 -0
  117. data/lib/mibs/ietf/IF-INVERTED-STACK-MIB.dic +220 -0
  118. data/lib/mibs/ietf/IF-MIB.dic +2753 -0
  119. data/lib/mibs/ietf/IFCP-MGMT-MIB.dic +1717 -0
  120. data/lib/mibs/ietf/IGMP-STD-MIB.dic +809 -0
  121. data/lib/mibs/ietf/INET-ADDRESS-MIB.dic +570 -0
  122. data/lib/mibs/ietf/INTEGRATED-SERVICES-GUARANTEED-MIB.dic +319 -0
  123. data/lib/mibs/ietf/INTEGRATED-SERVICES-MIB.dic +1196 -0
  124. data/lib/mibs/ietf/INTERFACETOPN-MIB.dic +1705 -0
  125. data/lib/mibs/ietf/IP-FORWARD-MIB.dic +1853 -0
  126. data/lib/mibs/ietf/IP-MIB.dic +7064 -0
  127. data/lib/mibs/ietf/IPATM-IPMC-MIB.dic +4830 -0
  128. data/lib/mibs/ietf/IPFIX-MIB.dic +2334 -0
  129. data/lib/mibs/ietf/IPFIX-SELECTOR-MIB.dic +215 -0
  130. data/lib/mibs/ietf/IPMCAST-MIB.dic +3390 -0
  131. data/lib/mibs/ietf/IPMROUTE-STD-MIB.dic +1246 -0
  132. data/lib/mibs/ietf/IPOA-MIB.dic +2372 -0
  133. data/lib/mibs/ietf/IPS-AUTH-MIB.dic +1609 -0
  134. data/lib/mibs/ietf/IPSEC-SPD-MIB.dic +3989 -0
  135. data/lib/mibs/ietf/IPV6-FLOW-LABEL-MIB.dic +110 -0
  136. data/lib/mibs/ietf/IPV6-ICMP-MIB.dic +748 -0
  137. data/lib/mibs/ietf/IPV6-MIB.dic +2028 -0
  138. data/lib/mibs/ietf/IPV6-MLD-MIB.dic +659 -0
  139. data/lib/mibs/ietf/IPV6-TCP-MIB.dic +332 -0
  140. data/lib/mibs/ietf/IPV6-UDP-MIB.dic +209 -0
  141. data/lib/mibs/ietf/ISCSI-MIB.dic +4613 -0
  142. data/lib/mibs/ietf/ISDN-MIB.dic +1796 -0
  143. data/lib/mibs/ietf/ISIS-MIB.dic +6215 -0
  144. data/lib/mibs/ietf/ISNS-MIB.dic +6578 -0
  145. data/lib/mibs/ietf/ITU-ALARM-MIB.dic +665 -0
  146. data/lib/mibs/ietf/ITU-ALARM-TC-MIB.dic +137 -0
  147. data/lib/mibs/ietf/Job-Monitoring-MIB.dic +2519 -0
  148. data/lib/mibs/ietf/L2TP-MIB.dic +4050 -0
  149. data/lib/mibs/ietf/LANGTAG-TC-MIB.dic +104 -0
  150. data/lib/mibs/ietf/LISP-MIB.dic +4067 -0
  151. data/lib/mibs/ietf/LMP-MIB.dic +5166 -0
  152. data/lib/mibs/ietf/MALLOC-MIB.dic +2156 -0
  153. data/lib/mibs/ietf/MAU-MIB.dic +2619 -0
  154. data/lib/mibs/ietf/MIDCOM-MIB.dic +2856 -0
  155. data/lib/mibs/ietf/MIOX25-MIB.dic +828 -0
  156. data/lib/mibs/ietf/MIP-MIB.dic +3473 -0
  157. data/lib/mibs/ietf/MOBILEIPV6-MIB.dic +5228 -0
  158. data/lib/mibs/ietf/MPLS-FTN-STD-MIB.dic +1594 -0
  159. data/lib/mibs/ietf/MPLS-L3VPN-STD-MIB.dic +2548 -0
  160. data/lib/mibs/ietf/MPLS-LC-ATM-STD-MIB.dic +491 -0
  161. data/lib/mibs/ietf/MPLS-LC-FR-STD-MIB.dic +395 -0
  162. data/lib/mibs/ietf/MPLS-LDP-ATM-STD-MIB.dic +1019 -0
  163. data/lib/mibs/ietf/MPLS-LDP-FRAME-RELAY-STD-MIB.dic +862 -0
  164. data/lib/mibs/ietf/MPLS-LDP-GENERIC-STD-MIB.dic +445 -0
  165. data/lib/mibs/ietf/MPLS-LDP-STD-MIB.dic +3657 -0
  166. data/lib/mibs/ietf/MPLS-LSR-STD-MIB.dic +3103 -0
  167. data/lib/mibs/ietf/MPLS-TC-STD-MIB.dic +911 -0
  168. data/lib/mibs/ietf/MPLS-TE-STD-MIB.dic +3673 -0
  169. data/lib/mibs/ietf/MSDP-MIB.dic +1893 -0
  170. data/lib/mibs/ietf/MTA-MIB.dic +1898 -0
  171. data/lib/mibs/ietf/Modem-MIB.dic +2054 -0
  172. data/lib/mibs/ietf/NAT-MIB.dic +3866 -0
  173. data/lib/mibs/ietf/NETWORK-SERVICES-MIB.dic +1034 -0
  174. data/lib/mibs/ietf/NHDP-MIB.dic +3005 -0
  175. data/lib/mibs/ietf/NHRP-MIB.dic +3660 -0
  176. data/lib/mibs/ietf/NOTIFICATION-LOG-MIB.dic +1156 -0
  177. data/lib/mibs/ietf/NTPv4-MIB.dic +1535 -0
  178. data/lib/mibs/ietf/OPT-IF-MIB.dic +8972 -0
  179. data/lib/mibs/ietf/OSPF-MIB.dic +5963 -0
  180. data/lib/mibs/ietf/OSPF-TRAP-MIB.dic +1190 -0
  181. data/lib/mibs/ietf/OSPFV3-MIB.dic +5708 -0
  182. data/lib/mibs/ietf/P-BRIDGE-MIB.dic +1499 -0
  183. data/lib/mibs/ietf/PARALLEL-MIB.dic +476 -0
  184. data/lib/mibs/ietf/PIM-MIB.dic +1393 -0
  185. data/lib/mibs/ietf/PIM-STD-MIB.dic +6819 -0
  186. data/lib/mibs/ietf/PINT-MIB.dic +830 -0
  187. data/lib/mibs/ietf/PKTC-IETF-MTA-MIB.dic +3191 -0
  188. data/lib/mibs/ietf/PKTC-IETF-SIG-MIB.dic +4713 -0
  189. data/lib/mibs/ietf/PMIPV6-MIB.dic +3010 -0
  190. data/lib/mibs/ietf/PMIPV6-TC-MIB.dic +293 -0
  191. data/lib/mibs/ietf/POLICY-BASED-MANAGEMENT-MIB.dic +3316 -0
  192. data/lib/mibs/ietf/POWER-ETHERNET-MIB.dic +959 -0
  193. data/lib/mibs/ietf/PPP-BRIDGE-NCP-MIB.dic +587 -0
  194. data/lib/mibs/ietf/PPP-IP-NCP-MIB.dic +269 -0
  195. data/lib/mibs/ietf/PPP-LCP-MIB.dic +994 -0
  196. data/lib/mibs/ietf/PPP-SEC-MIB.dic +411 -0
  197. data/lib/mibs/ietf/PSAMP-MIB.dic +998 -0
  198. data/lib/mibs/ietf/PTOPO-MIB.dic +1135 -0
  199. data/lib/mibs/ietf/PW-ATM-MIB.dic +1642 -0
  200. data/lib/mibs/ietf/PW-CEP-STD-MIB.dic +3661 -0
  201. data/lib/mibs/ietf/PW-STD-MIB.dic +3592 -0
  202. data/lib/mibs/ietf/PW-TC-STD-MIB.dic +437 -0
  203. data/lib/mibs/ietf/PW-TDM-MIB.dic +1896 -0
  204. data/lib/mibs/ietf/PerfHist-TC-MIB.dic +152 -0
  205. data/lib/mibs/ietf/Printer-MIB.dic +6665 -0
  206. data/lib/mibs/ietf/Q-BRIDGE-MIB.dic +3115 -0
  207. data/lib/mibs/ietf/RADIUS-ACC-CLIENT-MIB.dic +991 -0
  208. data/lib/mibs/ietf/RADIUS-ACC-SERVER-MIB.dic +1183 -0
  209. data/lib/mibs/ietf/RADIUS-AUTH-CLIENT-MIB.dic +1073 -0
  210. data/lib/mibs/ietf/RADIUS-AUTH-SERVER-MIB.dic +1251 -0
  211. data/lib/mibs/ietf/RADIUS-DYNAUTH-CLIENT-MIB.dic +1116 -0
  212. data/lib/mibs/ietf/RADIUS-DYNAUTH-SERVER-MIB.dic +1003 -0
  213. data/lib/mibs/ietf/RAQMON-MIB.dic +2695 -0
  214. data/lib/mibs/ietf/RBRIDGE-MIB.dic +2981 -0
  215. data/lib/mibs/ietf/RDBMS-MIB.dic +1935 -0
  216. data/lib/mibs/ietf/RFC1065-SMI.dic +108 -0
  217. data/lib/mibs/ietf/RFC1155-SMI.dic +118 -0
  218. data/lib/mibs/ietf/RFC1158-MIB.dic +2440 -0
  219. data/lib/mibs/ietf/RFC1213-MIB.dic +3434 -0
  220. data/lib/mibs/ietf/RFC1269-MIB.dic +557 -0
  221. data/lib/mibs/ietf/RFC1271-MIB.dic +4135 -0
  222. data/lib/mibs/ietf/RFC1285-MIB.dic +2842 -0
  223. data/lib/mibs/ietf/RFC1316-MIB.dic +800 -0
  224. data/lib/mibs/ietf/RFC1381-MIB.dic +1347 -0
  225. data/lib/mibs/ietf/RFC1382-MIB.dic +3820 -0
  226. data/lib/mibs/ietf/RFC1414-MIB.dic +214 -0
  227. data/lib/mibs/ietf/RIPv2-MIB.dic +773 -0
  228. data/lib/mibs/ietf/RMON-MIB.dic +5551 -0
  229. data/lib/mibs/ietf/RMON2-MIB.dic +8224 -0
  230. data/lib/mibs/ietf/ROHC-MIB.dic +1613 -0
  231. data/lib/mibs/ietf/ROHC-RTP-MIB.dic +859 -0
  232. data/lib/mibs/ietf/ROHC-UNCOMPRESSED-MIB.dic +267 -0
  233. data/lib/mibs/ietf/RPKI-ROUTER-MIB.dic +1363 -0
  234. data/lib/mibs/ietf/RS-232-MIB.dic +1335 -0
  235. data/lib/mibs/ietf/RSERPOOL-MIB.dic +2501 -0
  236. data/lib/mibs/ietf/RSTP-MIB.dic +427 -0
  237. data/lib/mibs/ietf/RSVP-MIB.dic +4135 -0
  238. data/lib/mibs/ietf/RTP-MIB.dic +1376 -0
  239. data/lib/mibs/ietf/SCSI-MIB.dic +3804 -0
  240. data/lib/mibs/ietf/SCTP-MIB.dic +1924 -0
  241. data/lib/mibs/ietf/SFLOW-MIB.dic +568 -0
  242. data/lib/mibs/ietf/SIP-COMMON-MIB.dic +2769 -0
  243. data/lib/mibs/ietf/SIP-MIB.dic +1438 -0
  244. data/lib/mibs/ietf/SIP-SERVER-MIB.dic +1150 -0
  245. data/lib/mibs/ietf/SIP-TC-MIB.dic +257 -0
  246. data/lib/mibs/ietf/SIP-UA-MIB.dic +268 -0
  247. data/lib/mibs/ietf/SLAPM-MIB.dic +4527 -0
  248. data/lib/mibs/ietf/SMON-MIB.dic +1758 -0
  249. data/lib/mibs/ietf/SNA-NAU-MIB.dic +4042 -0
  250. data/lib/mibs/ietf/SNA-SDLC-MIB.dic +3858 -0
  251. data/lib/mibs/ietf/SNMP-COMMUNITY-MIB.dic +715 -0
  252. data/lib/mibs/ietf/SNMP-FRAMEWORK-MIB.dic +709 -0
  253. data/lib/mibs/ietf/SNMP-MPD-MIB.dic +230 -0
  254. data/lib/mibs/ietf/SNMP-NOTIFICATION-MIB.dic +859 -0
  255. data/lib/mibs/ietf/SNMP-PROXY-MIB.dic +414 -0
  256. data/lib/mibs/ietf/SNMP-REPEATER-MIB.dic +4335 -0
  257. data/lib/mibs/ietf/SNMP-SSH-TM-MIB.dic +447 -0
  258. data/lib/mibs/ietf/SNMP-TARGET-MIB.dic +924 -0
  259. data/lib/mibs/ietf/SNMP-TLS-TM-MIB.dic +1449 -0
  260. data/lib/mibs/ietf/SNMP-TSM-MIB.dic +315 -0
  261. data/lib/mibs/ietf/SNMP-USER-BASED-SM-MIB.dic +1164 -0
  262. data/lib/mibs/ietf/SNMP-USM-AES-MIB.dic +95 -0
  263. data/lib/mibs/ietf/SNMP-USM-DH-OBJECTS-MIB.dic +653 -0
  264. data/lib/mibs/ietf/SNMP-VIEW-BASED-ACM-MIB.dic +1202 -0
  265. data/lib/mibs/ietf/SNMPv2-MIB.dic +1382 -0
  266. data/lib/mibs/ietf/SNMPv2-SMI.dic +223 -0
  267. data/lib/mibs/ietf/SNMPv2-USEC-MIB.dic +405 -0
  268. data/lib/mibs/ietf/SONET-MIB.dic +3308 -0
  269. data/lib/mibs/ietf/SOURCE-ROUTING-MIB.dic +542 -0
  270. data/lib/mibs/ietf/SSPM-MIB.dic +1530 -0
  271. data/lib/mibs/ietf/SYSAPPL-MIB.dic +2092 -0
  272. data/lib/mibs/ietf/T11-FC-FABRIC-ADDR-MGR-MIB.dic +1779 -0
  273. data/lib/mibs/ietf/T11-FC-FABRIC-CONFIG-SERVER-MIB.dic +2822 -0
  274. data/lib/mibs/ietf/T11-FC-FABRIC-LOCK-MIB.dic +700 -0
  275. data/lib/mibs/ietf/T11-FC-FSPF-MIB.dic +1889 -0
  276. data/lib/mibs/ietf/T11-FC-NAME-SERVER-MIB.dic +1775 -0
  277. data/lib/mibs/ietf/T11-FC-ROUTE-MIB.dic +655 -0
  278. data/lib/mibs/ietf/T11-FC-RSCN-MIB.dic +1110 -0
  279. data/lib/mibs/ietf/T11-FC-VIRTUAL-FABRIC-MIB.dic +770 -0
  280. data/lib/mibs/ietf/T11-FC-ZONE-SERVER-MIB.dic +3886 -0
  281. data/lib/mibs/ietf/T11-TC-MIB.dic +110 -0
  282. data/lib/mibs/ietf/TCP-ESTATS-MIB.dic +3926 -0
  283. data/lib/mibs/ietf/TCP-MIB.dic +1319 -0
  284. data/lib/mibs/ietf/TCPIPX-MIB.dic +457 -0
  285. data/lib/mibs/ietf/TE-LINK-STD-MIB.dic +2876 -0
  286. data/lib/mibs/ietf/TE-MIB.dic +2924 -0
  287. data/lib/mibs/ietf/TED-MIB.dic +1749 -0
  288. data/lib/mibs/ietf/TIME-AGGREGATE-MIB.dic +550 -0
  289. data/lib/mibs/ietf/TN3270E-MIB.dic +2785 -0
  290. data/lib/mibs/ietf/TN3270E-RT-MIB.dic +1317 -0
  291. data/lib/mibs/ietf/TOKEN-RING-RMON-MIB.dic +2820 -0
  292. data/lib/mibs/ietf/TOKENRING-MIB.dic +1184 -0
  293. data/lib/mibs/ietf/TOKENRING-STATION-SR-MIB.dic +292 -0
  294. data/lib/mibs/ietf/TRANSPORT-ADDRESS-MIB.dic +610 -0
  295. data/lib/mibs/ietf/TRIP-MIB.dic +3159 -0
  296. data/lib/mibs/ietf/TRIP-TC-MIB.dic +241 -0
  297. data/lib/mibs/ietf/TUNNEL-MIB.dic +1095 -0
  298. data/lib/mibs/ietf/UDP-MIB.dic +751 -0
  299. data/lib/mibs/ietf/UDPLITE-MIB.dic +704 -0
  300. data/lib/mibs/ietf/UPS-MIB.dic +3088 -0
  301. data/lib/mibs/ietf/URI-TC-MIB.dic +193 -0
  302. data/lib/mibs/ietf/UUID-TC-MIB.dic +135 -0
  303. data/lib/mibs/ietf/VDSL-LINE-EXT-MCM-MIB.dic +989 -0
  304. data/lib/mibs/ietf/VDSL-LINE-EXT-SCM-MIB.dic +605 -0
  305. data/lib/mibs/ietf/VDSL-LINE-MIB.dic +4518 -0
  306. data/lib/mibs/ietf/VDSL2-LINE-MIB.dic +11029 -0
  307. data/lib/mibs/ietf/VDSL2-LINE-TC-MIB.dic +3152 -0
  308. data/lib/mibs/ietf/VPN-TC-STD-MIB.dic +121 -0
  309. data/lib/mibs/ietf/VRRP-MIB.dic +1163 -0
  310. data/lib/mibs/ietf/VRRPV3-MIB.dic +1403 -0
  311. data/lib/mibs/ietf/WWW-MIB.dic +1810 -0
  312. data/lib/mibs/logstash/iso.dic +18 -0
  313. data/logstash-integration-snmp.gemspec +40 -0
  314. data/spec/fixtures/RFC1213-MIB.dic +3445 -0
  315. data/spec/fixtures/collision.dic +25 -0
  316. data/spec/integration/inputs/snmp_spec.rb +443 -0
  317. data/spec/integration/inputs/snmptrap_spec.rb +383 -0
  318. data/spec/unit/inputs/common_spec.rb +264 -0
  319. data/spec/unit/inputs/snmp_spec.rb +510 -0
  320. data/spec/unit/inputs/snmptrap_spec.rb +141 -0
  321. data/vendor/jar-dependencies/org/logstash/integrations/plugin/4.0.0/plugin-4.0.0.jar +0 -0
  322. data/vendor/jar-dependencies/org/snakeyaml/snakeyaml-engine/2.7/snakeyaml-engine-2.7.jar +0 -0
  323. data/vendor/jar-dependencies/org/snmp4j/snmp4j/3.8.0/snmp4j-3.8.0.jar +0 -0
  324. metadata +523 -0
@@ -0,0 +1,2856 @@
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 MIDCOM-MIB
6
+
7
+ FILENAME = "./libsmi-0.5.0/mibs/ietf/MIDCOM-MIB"
8
+
9
+ MIB = {
10
+ "moduleName" : "MIDCOM-MIB",
11
+
12
+ "MIDCOM-MIB" : {
13
+ "nodetype" : "module",
14
+ "language" : "SMIv2",
15
+ "organization" :
16
+ """IETF Middlebox Communication Working Group""",
17
+ "contact" :
18
+ """WG charter:
19
+ http://www.ietf.org/html.charters/midcom-charter.html
20
+
21
+ Mailing Lists:
22
+ General Discussion: midcom@ietf.org
23
+ To Subscribe: midcom-request@ietf.org
24
+ In Body: subscribe your_email_address
25
+
26
+ Co-editor:
27
+ Juergen Quittek
28
+ NEC Europe Ltd.
29
+ Kurfuersten-Anlage 36
30
+ 69115 Heidelberg
31
+ Germany
32
+ Tel: +49 6221 4342-115
33
+ Email: quittek@nw.neclab.eu
34
+
35
+ Co-editor:
36
+ Martin Stiemerling
37
+ NEC Europe Ltd.
38
+ Kurfuersten-Anlage 36
39
+ 69115 Heidelberg
40
+ Germany
41
+ Tel: +49 6221 4342-113
42
+ Email: stiemerling@nw.neclab.eu
43
+
44
+ Co-editor:
45
+ Pyda Srisuresh
46
+ Kazeon Systems, Inc.
47
+ 1161 San Antonio Rd.
48
+ Mountain View, CA 94043
49
+ U.S.A.
50
+ Tel: +1 408 836-4773
51
+ Email: srisuresh@yahoo.com""",
52
+ "description" :
53
+ """This MIB module defines a set of basic objects for
54
+ configuring middleboxes, such as firewalls and network
55
+
56
+
57
+
58
+ address translators, in order to enable communication
59
+ across these devices.
60
+
61
+ Managed objects defined in this MIB module are structured
62
+ in three kinds of objects:
63
+ - transaction objects required according to the MIDCOM
64
+ protocol requirements defined in RFC 3304 and according
65
+ to the MIDCOM protocol semantics defined in RFC 3989,
66
+ - configuration objects that can be used for retrieving or
67
+ setting parameters of the implementation of transaction
68
+ objects,
69
+ - optional monitoring objects that provide information
70
+ about used resource and statistics
71
+
72
+ The transaction objects are organized in two subtrees:
73
+ - objects modeling MIDCOM policy rules in the
74
+ midcomRuleTable
75
+ - objects modeling MIDCOM policy rule groups in the
76
+ midcomGroupTable
77
+
78
+ Note that typically, configuration objects are not intended
79
+ to be written by MIDCOM clients. In general, write access
80
+ to these objects needs to be restricted more strictly than
81
+ write access to objects in the transaction subtrees.
82
+
83
+ Copyright (C) The Internet Society (2008). This version
84
+ of this MIB module is part of RFC 5190; see the RFC
85
+ itself for full legal notices.""",
86
+ "revisions" : (
87
+ {
88
+ "date" : "2007-08-09 10:11",
89
+ "description" :
90
+ """Initial version, published as RFC 5190.""",
91
+ },
92
+ ),
93
+ "identity node" : "midcomMIB",
94
+ },
95
+
96
+ "imports" : (
97
+ {"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
98
+ {"module" : "SNMPv2-SMI", "name" : "OBJECT-TYPE"},
99
+ {"module" : "SNMPv2-SMI", "name" : "NOTIFICATION-TYPE"},
100
+ {"module" : "SNMPv2-SMI", "name" : "Unsigned32"},
101
+ {"module" : "SNMPv2-SMI", "name" : "Counter32"},
102
+ {"module" : "SNMPv2-SMI", "name" : "Gauge32"},
103
+ {"module" : "SNMPv2-SMI", "name" : "mib-2"},
104
+ {"module" : "SNMPv2-TC", "name" : "TEXTUAL-CONVENTION"},
105
+ {"module" : "SNMPv2-TC", "name" : "TruthValue"},
106
+ {"module" : "SNMPv2-TC", "name" : "StorageType"},
107
+ {"module" : "SNMPv2-TC", "name" : "RowStatus"},
108
+ {"module" : "SNMPv2-CONF", "name" : "MODULE-COMPLIANCE"},
109
+ {"module" : "SNMPv2-CONF", "name" : "OBJECT-GROUP"},
110
+ {"module" : "SNMPv2-CONF", "name" : "NOTIFICATION-GROUP"},
111
+ {"module" : "SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
112
+ {"module" : "INET-ADDRESS-MIB", "name" : "InetAddressType"},
113
+ {"module" : "INET-ADDRESS-MIB", "name" : "InetAddress"},
114
+ {"module" : "INET-ADDRESS-MIB", "name" : "InetPortNumber"},
115
+ {"module" : "INET-ADDRESS-MIB", "name" : "InetAddressPrefixLength"},
116
+ {"module" : "IF-MIB", "name" : "InterfaceIndexOrZero"},
117
+ {"module" : "NAT-MIB", "name" : "NatBindIdOrZero"},
118
+ ),
119
+
120
+ "typedefs" : {
121
+ "MidcomNatBindMode" : {
122
+ "basetype" : "Enumeration",
123
+ "status" : "current",
124
+ "addressBind" : {
125
+ "nodetype" : "namednumber",
126
+ "number" : "1"
127
+ },
128
+ "addressPortBind" : {
129
+ "nodetype" : "namednumber",
130
+ "number" : "2"
131
+ },
132
+ "none" : {
133
+ "nodetype" : "namednumber",
134
+ "number" : "3"
135
+ },
136
+ "description" :
137
+ """An indicator of the kind of NAT resources used by a policy
138
+ rule. This definition corresponds to the definition of
139
+ NatBindMode in the NAT-MIB (RFC 4008). Value none(3) can
140
+ be used to indicate that the policy rule does not use
141
+ any NAT binding.""",
142
+ },
143
+ "MidcomNatSessionIdOrZero" : {
144
+ "basetype" : "Unsigned32",
145
+ "status" : "current",
146
+ "format" : "d",
147
+ "description" :
148
+ """A unique ID that is assigned to each NAT session by
149
+ a NAT implementation. This definition corresponds to
150
+ the definition of NatSessionId in the NAT-MIB (RFC 4008).
151
+ Value 0 can be used to indicate that the policy rule does
152
+ not use any NAT binding.""",
153
+ },
154
+ }, # typedefs
155
+
156
+ "nodes" : {
157
+ "midcomMIB" : {
158
+ "nodetype" : "node",
159
+ "moduleName" : "MIDCOM-MIB",
160
+ "oid" : "1.3.6.1.2.1.171",
161
+ "status" : "current",
162
+ }, # node
163
+ "midcomNotifications" : {
164
+ "nodetype" : "node",
165
+ "moduleName" : "MIDCOM-MIB",
166
+ "oid" : "1.3.6.1.2.1.171.0",
167
+ }, # node
168
+ "midcomObjects" : {
169
+ "nodetype" : "node",
170
+ "moduleName" : "MIDCOM-MIB",
171
+ "oid" : "1.3.6.1.2.1.171.1",
172
+ }, # node
173
+ "midcomTransaction" : {
174
+ "nodetype" : "node",
175
+ "moduleName" : "MIDCOM-MIB",
176
+ "oid" : "1.3.6.1.2.1.171.1.1",
177
+ }, # node
178
+ "midcomRuleTable" : {
179
+ "nodetype" : "table",
180
+ "moduleName" : "MIDCOM-MIB",
181
+ "oid" : "1.3.6.1.2.1.171.1.1.3",
182
+ "status" : "current",
183
+ "description" :
184
+ """This table lists policy rules.
185
+
186
+ It is indexed by the midcomRuleOwner, the
187
+ midcomGroupIndex, and the midcomRuleIndex.
188
+ This implies that a rule is a member of exactly
189
+ one group and that group membership cannot
190
+ be changed.
191
+
192
+ Entries can be deleted by writing to
193
+ midcomGroupLifetime or midcomRuleLifetime
194
+ and potentially also to midcomRuleStorageTime.""",
195
+ }, # table
196
+ "midcomRuleEntry" : {
197
+ "nodetype" : "row",
198
+ "moduleName" : "MIDCOM-MIB",
199
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1",
200
+ "create" : "true",
201
+ "status" : "current",
202
+ "linkage" : [
203
+ "midcomRuleOwner",
204
+ "midcomGroupIndex",
205
+ "midcomRuleIndex",
206
+ ],
207
+ "description" :
208
+ """An entry describing a particular MIDCOM policy rule.""",
209
+ }, # row
210
+ "midcomRuleOwner" : {
211
+ "nodetype" : "column",
212
+ "moduleName" : "MIDCOM-MIB",
213
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.1",
214
+ "status" : "current",
215
+ "syntax" : {
216
+ "type" : {
217
+ "basetype" : "OctetString",
218
+ "parent module" : {
219
+ "name" : "SNMP-FRAMEWORK-MIB",
220
+ "type" : "SnmpAdminString",
221
+ },
222
+ "ranges" : [
223
+ {
224
+ "min" : "0",
225
+ "max" : "32"
226
+ },
227
+ ],
228
+ "range" : {
229
+ "min" : "0",
230
+ "max" : "32"
231
+ },
232
+ },
233
+ },
234
+ "access" : "noaccess",
235
+ "description" :
236
+ """The manager who owns this row in the midcomRuleTable.
237
+
238
+ This object SHOULD uniquely identify an authenticated
239
+ MIDCOM client. This object is part of the table index to
240
+ allow for the use of the SNMPv3 View-based Access Control
241
+ Model (VACM, RFC 3415).""",
242
+ }, # column
243
+ "midcomRuleIndex" : {
244
+ "nodetype" : "column",
245
+ "moduleName" : "MIDCOM-MIB",
246
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.3",
247
+ "status" : "current",
248
+ "syntax" : {
249
+ "type" : {
250
+ "basetype" : "Unsigned32",
251
+ "ranges" : [
252
+ {
253
+ "min" : "1",
254
+ "max" : "4294967295"
255
+ },
256
+ ],
257
+ "range" : {
258
+ "min" : "1",
259
+ "max" : "4294967295"
260
+ },
261
+ },
262
+ },
263
+ "access" : "noaccess",
264
+ "description" :
265
+ """The value of this object must be unique in
266
+ combination with the values of the objects
267
+ midcomRuleOwner and midcomGroupIndex in this row.""",
268
+ }, # column
269
+ "midcomRuleAdminStatus" : {
270
+ "nodetype" : "column",
271
+ "moduleName" : "MIDCOM-MIB",
272
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.4",
273
+ "status" : "current",
274
+ "syntax" : {
275
+ "type" : {
276
+ "basetype" : "Enumeration",
277
+ "reserve" : {
278
+ "nodetype" : "namednumber",
279
+ "number" : "1"
280
+ },
281
+ "enable" : {
282
+ "nodetype" : "namednumber",
283
+ "number" : "2"
284
+ },
285
+ "notSet" : {
286
+ "nodetype" : "namednumber",
287
+ "number" : "3"
288
+ },
289
+ },
290
+ },
291
+ "access" : "readwrite",
292
+ "default" : "notSet",
293
+ "description" :
294
+ """The value of this object indicates the desired status of
295
+ the policy rule. See the definition of midcomRuleOperStatus
296
+ for a description of the values.
297
+
298
+ When a midcomRuleEntry is created without explicitly setting
299
+ this object, its value will be notSet(3).
300
+
301
+ However, a SET request can only set this object to either
302
+ reserve(1) or enable(2). Attempts to set this object to
303
+ notSet(3) will always fail with an 'inconsistentValue'
304
+ error. Note that this error code is SNMP specific. If the
305
+ MIB module is used with other protocols than SNMP, errors
306
+ with similar semantics specific to those protocols should
307
+ be returned.
308
+
309
+ When the midcomRuleAdminStatus object is set, then the
310
+ MIDCOM-MIB implementation will try to read the respective
311
+ relevant objects of the entry and try to achieve the
312
+ corresponding midcomRuleOperStatus.
313
+
314
+ Setting midcomRuleAdminStatus to value reserve(1) when
315
+ object midcomRuleOperStatus has a value of reserved(7)
316
+ does not have any effect on the policy rule.
317
+ Setting midcomRuleAdminStatus to value enable(2) when
318
+ object midcomRuleOperStatus has a value of enabled(8)
319
+ does not have any effect on the policy rule.
320
+
321
+ Depending on whether the midcomRuleAdminStatus is set to
322
+ reserve(1) or enable(2), several objects must be set in
323
+ advance. They serve as parameters of the policy rule to be
324
+ established.
325
+
326
+
327
+
328
+
329
+ When object midcomRuleAdminStatus is set to reserve(1),
330
+ then the following objects in the same entry are of
331
+ relevance:
332
+ - midcomRuleInterface
333
+ - midcomRuleTransportProtocol
334
+ - midcomRulePortRange
335
+ - midcomRuleInternalIpVersion
336
+ - midcomRuleExternalIpVersion
337
+ - midcomRuleInternalIpAddr
338
+ - midcomRuleInternalIpPrefixLength
339
+ - midcomRuleInternalPort
340
+ - midcomRuleLifetime
341
+
342
+ MIDCOM-MIB implementation may also consider the value
343
+ of object midcomRuleMaxIdleTime when establishing
344
+ a reserve rule.
345
+
346
+ When object midcomRuleAdminStatus is set to enable(2),
347
+ then the following objects in the same entry are of
348
+ relevance:
349
+ - midcomRuleInterface
350
+ - midcomRuleFlowDirection
351
+ - midcomRuleMaxIdleTime
352
+ - midcomRuleTransportProtocol
353
+ - midcomRulePortRange
354
+ - midcomRuleInternalIpVersion
355
+ - midcomRuleExternalIpVersion
356
+ - midcomRuleInternalIpAddr
357
+ - midcomRuleInternalIpPrefixLength
358
+ - midcomRuleInternalPort
359
+ - midcomRuleExternalIpAddr
360
+ - midcomRuleExternalIpPrefixLength
361
+ - midcomRuleExternalPort
362
+ - midcomRuleLifetime
363
+
364
+ When retrieved, the object returns the last set value.
365
+ If no value has been set, it returns the default value
366
+ notSet(3).""",
367
+ }, # column
368
+ "midcomRuleOperStatus" : {
369
+ "nodetype" : "column",
370
+ "moduleName" : "MIDCOM-MIB",
371
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.5",
372
+ "status" : "current",
373
+ "syntax" : {
374
+ "type" : {
375
+ "basetype" : "Enumeration",
376
+ "newEntry" : {
377
+ "nodetype" : "namednumber",
378
+ "number" : "1"
379
+ },
380
+ "setting" : {
381
+ "nodetype" : "namednumber",
382
+ "number" : "2"
383
+ },
384
+ "checkingRequest" : {
385
+ "nodetype" : "namednumber",
386
+ "number" : "3"
387
+ },
388
+ "incorrectRequest" : {
389
+ "nodetype" : "namednumber",
390
+ "number" : "4"
391
+ },
392
+ "processingRequest" : {
393
+ "nodetype" : "namednumber",
394
+ "number" : "5"
395
+ },
396
+ "requestRejected" : {
397
+ "nodetype" : "namednumber",
398
+ "number" : "6"
399
+ },
400
+ "reserved" : {
401
+ "nodetype" : "namednumber",
402
+ "number" : "7"
403
+ },
404
+ "enabled" : {
405
+ "nodetype" : "namednumber",
406
+ "number" : "8"
407
+ },
408
+ "timedOut" : {
409
+ "nodetype" : "namednumber",
410
+ "number" : "9"
411
+ },
412
+ "terminatedOnRequest" : {
413
+ "nodetype" : "namednumber",
414
+ "number" : "10"
415
+ },
416
+ "terminated" : {
417
+ "nodetype" : "namednumber",
418
+ "number" : "11"
419
+ },
420
+ "genericError" : {
421
+ "nodetype" : "namednumber",
422
+ "number" : "12"
423
+ },
424
+ },
425
+ },
426
+ "access" : "readonly",
427
+ "default" : "newEntry",
428
+ "description" :
429
+ """The actual status of the policy rule. The
430
+ midcomRuleOperStatus object may have the following values:
431
+
432
+ - newEntry(1) indicates that the entry in the
433
+ midcomRuleTable was created, but not modified yet.
434
+ Such an entry needs to be filled with values specifying
435
+ a request first.
436
+
437
+ - setting(2) indicates that the entry has been already
438
+ modified after generating it, but no request was made
439
+ yet.
440
+
441
+ - checkingRequest(3) indicates that midcomRuleAdminStatus
442
+ has recently been set and that the MIDCOM-MIB
443
+ implementation is currently checking the parameters of
444
+ the request. This is a transient state. The value of
445
+ this object will change to either incorrectRequest(4)
446
+ or processingRequest(5) without any external
447
+ interaction. A MIDCOM-MIB implementation MAY return
448
+ this value while checking request parameters.
449
+
450
+ - incorrectRequest(4) indicates that checking a request
451
+ resulted in detecting an incorrect value in one of the
452
+ objects containing request parameters. The failure
453
+ reason is indicated by the value of midcomRuleError.
454
+
455
+ - processingRequest(5) indicates that
456
+ midcomRuleAdminStatus has recently been set and that
457
+ the MIDCOM-MIB implementation is currently processing
458
+ the request and trying to configure the middlebox
459
+ accordingly. This is a transient state. The value of
460
+ this object will change to either requestRejected(6),
461
+ reserved(7), or enabled(8) without any external
462
+ interaction. A MIDCOM-MIB implementation MAY return
463
+ this value while processing a request.
464
+
465
+ - requestRejected(6) indicates that a request to establish
466
+
467
+
468
+
469
+ a policy rule specified by the entry was rejected. The
470
+ reason for rejection is indicated by the value of
471
+ midcomRuleError.
472
+
473
+ - reserved(7) indicates that the entry describes an
474
+ established policy reserve rule.
475
+ These values of MidcomRuleEntry are meaningful
476
+ for a reserved policy rule:
477
+ - midcomRuleMaxIdleTime
478
+ - midcomRuleInterface
479
+ - midcomRuleTransportProtocol
480
+ - midcomRulePortRange
481
+ - midcomRuleInternalIpVersion
482
+ - midcomRuleExternalIpVersion
483
+ - midcomRuleInternalIpAddr
484
+ - midcomRuleInternalIpPrefixLength
485
+ - midcomRuleInternalPort
486
+ - midcomRuleOutsideIpAddr
487
+ - midcomRuleOutsidePort
488
+ - midcomRuleLifetime
489
+
490
+ - enabled(8) indicates that the entry describes an
491
+ established policy enable rule.
492
+ These values of MidcomRuleEntry are meaningful
493
+ for an enabled policy rule:
494
+
495
+ - midcomRuleFlowDirection
496
+ - midcomRuleInterface
497
+ - midcomRuleMaxIdleTime
498
+ - midcomRuleTransportProtocol
499
+ - midcomRulePortRange
500
+ - midcomRuleInternalIpVersion
501
+ - midcomRuleExternalIpVersion
502
+ - midcomRuleInternalIpAddr
503
+ - midcomRuleInternalIpPrefixLength
504
+ - midcomRuleInternalPort
505
+ - midcomRuleExternalIpAddr
506
+ - midcomRuleExternalIpPrefixLength
507
+ - midcomRuleExternalPort
508
+ - midcomRuleInsideIpAddr
509
+ - midcomRuleInsidePort
510
+ - midcomRuleOutsideIpAddr
511
+ - midcomRuleOutsidePort
512
+ - midcomRuleLifetime
513
+
514
+ - timedOut(9) indicates that the lifetime of a previously
515
+ established policy rule has expired and that the policy
516
+ rule is terminated for this reason.
517
+
518
+
519
+
520
+ - terminatedOnRequest(10) indicates that a previously
521
+ established policy rule was terminated by an SNMP
522
+ manager setting the midcomRuleLifetime to 0 or
523
+ setting midcomGroupLifetime to 0.
524
+
525
+ - terminated(11) indicates that a previously established
526
+ policy rule was terminated by the MIDCOM-MIB
527
+ implementation for a reason other than lifetime
528
+ expiration or an explicit request from a MIDCOM client.
529
+
530
+ - genericError(12) indicates that the policy rule
531
+ specified by the entry is not established due to
532
+ an error condition not listed above.
533
+
534
+ The states timedOut(9), terminatedOnRequest(10), and
535
+ terminated(11) are referred to as termination states.
536
+
537
+ The states incorrectRequest(4), requestRejected(6),
538
+ and genericError(12) are referred to as error states.
539
+
540
+ The checkingRequest(3) and processingRequest(5)
541
+ states are transient states, which will lead to either
542
+ one of the error states or the reserved(7) state or the
543
+ enabled(8) state. MIDCOM-MIB implementations MAY return
544
+ these values when checking or processing requests.""",
545
+ }, # column
546
+ "midcomRuleStorageType" : {
547
+ "nodetype" : "column",
548
+ "moduleName" : "MIDCOM-MIB",
549
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.6",
550
+ "status" : "current",
551
+ "syntax" : {
552
+ "type" : { "module" :"SNMPv2-TC", "name" : "StorageType"},
553
+ },
554
+ "access" : "readwrite",
555
+ "default" : "volatile",
556
+ "description" :
557
+ """When retrieved, this object returns the storage
558
+ type of the policy rule. Writing to this object can
559
+ change the storage type of the particular row from
560
+ volatile(2) to nonVolatile(3) or vice versa.
561
+
562
+ Attempts to set this object to permanent will always
563
+ fail with an 'inconsistentValue' error. Note that this
564
+ error code is SNMP specific. If the MIB module is used
565
+ with other protocols than SNMP, errors with similar
566
+ semantics specific to those protocols should be
567
+ returned.
568
+
569
+ If midcomRuleStorageType has the value permanent(4),
570
+ then all objects in this row whose MAX-ACCESS value
571
+ is read-create must be read-only.""",
572
+ }, # column
573
+ "midcomRuleStorageTime" : {
574
+ "nodetype" : "column",
575
+ "moduleName" : "MIDCOM-MIB",
576
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.7",
577
+ "status" : "current",
578
+ "syntax" : {
579
+ "type" : { "module" :"", "name" : "Unsigned32"},
580
+ },
581
+ "access" : "readwrite",
582
+ "default" : "0",
583
+ "units" : "seconds",
584
+ "description" :
585
+ """The value of this object specifies how long this row
586
+ can exist in the midcomRuleTable after the
587
+ midcomRuleOperStatus switched to a termination state or
588
+ to an error state. This object returns the remaining
589
+ time that the row may exist before it is aged out.
590
+
591
+ After expiration or termination of the context, the value
592
+ of this object ticks backwards. The entry in the
593
+ midcomRuleTable is destroyed when the value reaches 0.
594
+
595
+ The value of this object may be set in order to increase
596
+ or reduce the remaining time that the row may exist.
597
+ Setting the value to 0 will destroy this entry as soon as
598
+ the midcomRuleOperStatus switched to a termination state
599
+ or to an error state.
600
+
601
+ Note that there is no guarantee that the row is stored as
602
+ long as this object indicates. At any time, the MIDCOM-
603
+ MIB implementation may decide to remove a row describing
604
+ a terminated policy rule before the storage time of the
605
+ corresponding row in the midcomRuleTable reaches the
606
+ value of 0. In this case, the information stored in this
607
+ row is not available anymore.
608
+
609
+ If object midcomRuleStorageType indicates that the policy
610
+ rule has the storage type permanent(4), then this object has
611
+ a constant value of 4294967295.""",
612
+ }, # column
613
+ "midcomRuleError" : {
614
+ "nodetype" : "column",
615
+ "moduleName" : "MIDCOM-MIB",
616
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.8",
617
+ "status" : "current",
618
+ "syntax" : {
619
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
620
+ },
621
+ "access" : "readonly",
622
+ "default" : "",
623
+ "description" :
624
+ """This object contains a descriptive error message if
625
+ the transition into the operational status reserved(7)
626
+ or enabled(8) failed. Implementations must reset the
627
+ error message to a zero-length string when a new
628
+
629
+
630
+
631
+ attempt to change the policy rule status to reserved(7)
632
+ or enabled(8) is started.
633
+
634
+ RECOMMENDED values to be returned in particular cases
635
+ include
636
+ - 'lack of IP addresses'
637
+ - 'lack of port numbers'
638
+ - 'lack of resources'
639
+ - 'specified NAT interface does not exist'
640
+ - 'specified NAT interface does not support NAT'
641
+ - 'conflict with already existing policy rule'
642
+ - 'no internal IP wildcarding allowed'
643
+ - 'no external IP wildcarding allowed'
644
+
645
+ The semantics of these error messages and the corresponding
646
+ behavior of the MIDCOM-MIB implementation are specified
647
+ in sections 2.3.9 and 2.3.10 of RFC 3989.""",
648
+ "reference" :
649
+ """RFC 3989, sections 2.3.9 and 2.3.10""",
650
+ }, # column
651
+ "midcomRuleInterface" : {
652
+ "nodetype" : "column",
653
+ "moduleName" : "MIDCOM-MIB",
654
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.9",
655
+ "status" : "current",
656
+ "syntax" : {
657
+ "type" : { "module" :"IF-MIB", "name" : "InterfaceIndexOrZero"},
658
+ },
659
+ "access" : "readwrite",
660
+ "default" : "0",
661
+ "description" :
662
+ """This object indicates the IP interface for which
663
+ enforcement of a policy rule is requested or performed,
664
+ respectively.
665
+
666
+ The interface is identified by its index in the ifTable
667
+ (see IF-MIB in RFC 2863). If the object has a value of 0,
668
+ then no particular interface is indicated.
669
+
670
+ This object is used as input to a request for establishing
671
+ a policy rule as well as for indicating the properties of
672
+ an established policy rule.
673
+
674
+ If object midcomRuleOperStatus of the same entry has the
675
+ value newEntry(1) or setting(2), then this object can be
676
+ written by a manager in order to request its preference
677
+ concerning the interface at which it requests NAT service.
678
+ The default value of 0 indicates that the manager does not
679
+ have a preferred interface or does not have sufficient
680
+ topology information for specifying one. Writing to this
681
+ object in any state other than newEntry(1) or setting(2)
682
+ will always fail with an 'inconsistentValue' error.
683
+
684
+
685
+
686
+ Note that this error code is SNMP specific. If the MIB
687
+ module is used with other protocols than SNMP, errors with
688
+ similar semantics specific to those protocols should be
689
+ returned.
690
+
691
+ If object midcomRuleOperStatus of the same entry has the
692
+ value reserved(7) or enabled(8), then this object indicates
693
+ the interface at which NAT service for this rule is
694
+ performed. If NAT service is not required for enforcing
695
+ the policy rule, then the value of this object is 0. Also,
696
+ if the MIDCOM-MIB implementation cannot indicate an
697
+ interface, because it does not have this information or
698
+ because NAT service is not offered at a particular single
699
+ interface, then the value of the object is 0.
700
+
701
+ Note that the index of a particular interface in the
702
+ ifTable may change after a re-initialization of the
703
+ middlebox, for example, after adding another interface to
704
+ it. In such a case, the value of this object may change,
705
+ but the interface referred to by the MIDCOM-MIB MUST still
706
+ be the same. If, after a re-initialization of the
707
+ middlebox, the interface referred to before
708
+ re-initialization cannot be uniquely mapped anymore to a
709
+ particular entry in the ifTable, then the value of object
710
+ midcomRuleOperStatus of the same entry MUST be changed to
711
+ terminated(11).
712
+
713
+ If object midcomRuleOperStatus of the same entry has a
714
+ value other than newEntry(1), setting(2), reserved(7), or
715
+ enabled(8), then the value of this object is irrelevant.""",
716
+ }, # column
717
+ "midcomRuleFlowDirection" : {
718
+ "nodetype" : "column",
719
+ "moduleName" : "MIDCOM-MIB",
720
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.10",
721
+ "status" : "current",
722
+ "syntax" : {
723
+ "type" : {
724
+ "basetype" : "Enumeration",
725
+ "inbound" : {
726
+ "nodetype" : "namednumber",
727
+ "number" : "1"
728
+ },
729
+ "outbound" : {
730
+ "nodetype" : "namednumber",
731
+ "number" : "2"
732
+ },
733
+ "biDirectional" : {
734
+ "nodetype" : "namednumber",
735
+ "number" : "3"
736
+ },
737
+ },
738
+ },
739
+ "access" : "readwrite",
740
+ "default" : "outbound",
741
+ "description" :
742
+ """This parameter specifies the direction of enabled
743
+ communication, either inbound(1), outbound(2), or
744
+ biDirectional(3).
745
+
746
+ The semantics of this object depends on the protocol
747
+ the rule relates to. If the rule is independent of
748
+
749
+
750
+
751
+ the transport protocol (midcomRuleTransportProtocol
752
+ has a value of 0) or if the transport protocol is UDP,
753
+ then the value of midcomRuleFlowDirection indicates
754
+ the direction of packets traversing the middlebox.
755
+
756
+ In this case, value inbound(1) indicates that packets
757
+ are traversing from outside to inside, value outbound(2)
758
+ indicates that packets are traversing from inside to
759
+ outside. For both values, inbound(1) and outbound(2)
760
+ packets can traverse the middlebox only unidirectional.
761
+ A bidirectional flow is indicated by value
762
+ biDirectional(3).
763
+
764
+ If the transport protocol is TCP, the packet flow is
765
+ always bidirectional, but the value of
766
+ midcomRuleFlowDirection indicates that:
767
+
768
+ - inbound(1): bidirectional TCP packet flow.
769
+ First packet, with TCP SYN flag set, must arrive
770
+ at an outside interface of the middlebox.
771
+
772
+ - outbound(2): bidirectional TCP packet flow.
773
+ First packet, with TCP SYN flag set, must arrive
774
+ at an inside interface of the middlebox.
775
+
776
+ - biDirectional(3): bidirectional TCP packet flow.
777
+ First packet, with TCP SYN flag set, may arrive
778
+ at an inside or an outside interface of the middlebox.
779
+
780
+ This object is used as input to a request for
781
+ establishing a policy enable rule as well as for
782
+ indicating the properties of an established policy rule.
783
+
784
+ If object midcomRuleOperStatus of the same entry has a
785
+ value of either newEntry(1), setting(2), or reserved(7),
786
+ then this object can be written by a manager in order to
787
+ specify a requested direction to be enabled by a policy
788
+ rule. Writing to this object in any state other than
789
+ newEntry(1), setting(2), or reserved(7) will always fail
790
+ with an 'inconsistentValue' error.
791
+
792
+ Note that this error code is SNMP specific. If the MIB
793
+ module is used with other protocols than SNMP, errors with
794
+ similar semantics specific to those protocols should be
795
+ returned.
796
+
797
+ If object midcomRuleOperStatus of the same entry has the
798
+ value enabled(8), then this object indicates the enabled
799
+
800
+
801
+
802
+ flow direction.
803
+
804
+ If object midcomRuleOperStatus of the same entry has a
805
+ value other than newEntry(1), setting(2), reserved(7), or
806
+ enabled(8), then the value of this object is irrelevant.""",
807
+ }, # column
808
+ "midcomRuleMaxIdleTime" : {
809
+ "nodetype" : "column",
810
+ "moduleName" : "MIDCOM-MIB",
811
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.11",
812
+ "status" : "current",
813
+ "syntax" : {
814
+ "type" : { "module" :"", "name" : "Unsigned32"},
815
+ },
816
+ "access" : "readwrite",
817
+ "default" : "0",
818
+ "units" : "seconds",
819
+ "description" :
820
+ """Maximum idle time of the policy rule in seconds.
821
+
822
+ If no packet to which the policy rule applies passes the
823
+ middlebox for the specified midcomRuleMaxIdleTime, then
824
+ the policy rule enters the termination state timedOut(9).
825
+
826
+ A value of 0 indicates that the policy does not require
827
+ an individual idle time and that instead, a default idle
828
+ time chosen by the middlebox is used.
829
+
830
+ A value of 4294967295 ( = 2^32 - 1 ) indicates that the
831
+ policy does not time out if it is idle.
832
+
833
+ This object is used as input to a request for
834
+ establishing a policy enable rule as well as for
835
+ indicating the properties of an established policy rule.
836
+
837
+ If object midcomRuleOperStatus of the same entry has a
838
+ value of either newEntry(1), setting(2), or reserved(7),
839
+ then this object can be written by a manager in order to
840
+ specify a maximum idle time for the policy rule to be
841
+ requested. Writing to this object in any state others
842
+ than newEntry(1), setting(2), or reserved(7) will always
843
+ fail with an 'inconsistentValue' error.
844
+
845
+ Note that this error code is SNMP specific. If the MIB
846
+ module is used with other protocols than SNMP, errors with
847
+ similar semantics specific to those protocols should be
848
+ returned.
849
+
850
+ If object midcomRuleOperStatus of the same entry has the
851
+ value enabled(8), then this object indicates the maximum
852
+ idle time of the policy rule. Note that even if a maximum
853
+ idle time greater than zero was requested, the middlebox
854
+
855
+
856
+
857
+ may not be able to support maximum idle times and set the
858
+ value of this object to zero when entering state
859
+ enabled(8).
860
+
861
+ If object midcomRuleOperStatus of the same entry has a
862
+ value other than newEntry(1), setting(2), reserved(7), or
863
+ enabled(8), then the value of this object is irrelevant.""",
864
+ }, # column
865
+ "midcomRuleTransportProtocol" : {
866
+ "nodetype" : "column",
867
+ "moduleName" : "MIDCOM-MIB",
868
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.12",
869
+ "status" : "current",
870
+ "syntax" : {
871
+ "type" : {
872
+ "basetype" : "Unsigned32",
873
+ "ranges" : [
874
+ {
875
+ "min" : "0",
876
+ "max" : "255"
877
+ },
878
+ ],
879
+ "range" : {
880
+ "min" : "0",
881
+ "max" : "255"
882
+ },
883
+ },
884
+ },
885
+ "access" : "readwrite",
886
+ "default" : "0",
887
+ "description" :
888
+ """The transport protocol.
889
+
890
+ Valid values for midcomRuleTransportProtocol
891
+ other than zero are defined at:
892
+ http://www.iana.org/assignments/protocol-numbers
893
+
894
+ This object is used as input to a request for establishing
895
+ a policy rule as well as for indicating the properties of
896
+ an established policy rule.
897
+
898
+ If object midcomRuleOperStatus of the same entry has a
899
+ value of either newEntry(1) or setting(2), then this
900
+ object can be written by a manager in order to specify a
901
+ requested transport protocol. If translation of an IP
902
+ address only is requested, then this object must have the
903
+ default value 0. Writing to this object in any state
904
+ other than newEntry(1) or setting(2) will always fail
905
+ with an 'inconsistentValue' error.
906
+
907
+ Note that this error code is SNMP specific. If the MIB
908
+ module is used with other protocols than SNMP, errors with
909
+ similar semantics specific to those protocols should be
910
+ returned.
911
+
912
+ If object midcomRuleOperStatus of the same entry has the
913
+ value reserved(7) or enabled(8), then this object
914
+ indicates which transport protocol is enforced by this
915
+ policy rule. A value of 0 indicates a rule acting on IP
916
+ addresses only.
917
+
918
+ If object midcomRuleOperStatus of the same entry has a
919
+ value other than newEntry(1), setting(2), reserved(7), or
920
+ enabled(8), then the value of this object is irrelevant.""",
921
+ }, # column
922
+ "midcomRulePortRange" : {
923
+ "nodetype" : "column",
924
+ "moduleName" : "MIDCOM-MIB",
925
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.13",
926
+ "status" : "current",
927
+ "syntax" : {
928
+ "type" : {
929
+ "basetype" : "Enumeration",
930
+ "single" : {
931
+ "nodetype" : "namednumber",
932
+ "number" : "1"
933
+ },
934
+ "pair" : {
935
+ "nodetype" : "namednumber",
936
+ "number" : "2"
937
+ },
938
+ },
939
+ },
940
+ "access" : "readwrite",
941
+ "default" : "single",
942
+ "description" :
943
+ """The range of port numbers.
944
+
945
+ This object is used as input to a request for establishing
946
+ a policy rule as well as for indicating the properties of
947
+ an established policy rule. It is relevant to the
948
+ operation of the MIDCOM-MIB implementation only if the
949
+ value of object midcomTransportProtocol in the same entry
950
+ has a value other than 0.
951
+
952
+ If object midcomRuleOperStatus of the same entry has the
953
+ value newEntry(1) or setting(2), then this object can be
954
+ written by a manager in order to specify the requested
955
+ size of the port range. With single(1) just a single
956
+ port number is requested, with pair(2) a consecutive pair
957
+ of port numbers is requested with the lower number being
958
+ even. Requesting a consecutive pair of port numbers may
959
+ be used by RTP [RFC3550] and may even be required to
960
+ support older RTP applications.
961
+
962
+ Writing to this object in any state other than
963
+ newEntry(1), setting(2) or reserved(7) will always fail
964
+ with an 'inconsistentValue' error.
965
+
966
+ Note that this error code is SNMP specific. If the MIB
967
+ module is used with other protocols than SNMP, errors with
968
+ similar semantics specific to those protocols should be
969
+ returned.
970
+
971
+ If object midcomRuleOperStatus of the same entry has a
972
+ value of either reserved(7) or enabled(8), then this
973
+ object will have the value that it had before the
974
+ transition to this state.
975
+
976
+ If object midcomRuleOperStatus of the same entry has a
977
+ value other than newEntry(1), setting(2), reserved(7), or
978
+ enabled(8), then the value of this object is irrelevant.""",
979
+ }, # column
980
+ "midcomRuleInternalIpVersion" : {
981
+ "nodetype" : "column",
982
+ "moduleName" : "MIDCOM-MIB",
983
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.14",
984
+ "status" : "current",
985
+ "syntax" : {
986
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetAddressType"},
987
+ },
988
+ "access" : "readwrite",
989
+ "default" : "ipv4",
990
+ "description" :
991
+ """IP version of the internal address (A0) and the inside
992
+ address (A1). Allowed values are ipv4(1), ipv6(2),
993
+ ipv4z(3), and ipv6z(4).
994
+
995
+ This object is used as input to a request for establishing
996
+ a policy rule as well as for indicating the properties of
997
+ an established policy rule.
998
+
999
+ If object midcomRuleOperStatus of the same entry has the
1000
+ value newEntry(1) or setting(2), then this object can be
1001
+ written by a manager in order to specify the IP version
1002
+ required at the inside of the middlebox. Writing to this
1003
+ object in any state other than newEntry(1) or setting(2)
1004
+ will always fail with an 'inconsistentValue' error.
1005
+
1006
+ Note that this error code is SNMP specific. If the MIB
1007
+ module is used with other protocols than SNMP, errors with
1008
+ similar semantics specific to those protocols should be
1009
+ returned.
1010
+
1011
+ If object midcomRuleOperStatus of the same entry has the
1012
+ value reserved(7) or enabled(8), then this object
1013
+ indicates the internal/inside IP version.
1014
+
1015
+ If object midcomRuleOperStatus of the same entry has a
1016
+ value other than newEntry(1), setting(2), reserved(7), or
1017
+ enabled(8), then the value of this object is irrelevant.""",
1018
+ }, # column
1019
+ "midcomRuleExternalIpVersion" : {
1020
+ "nodetype" : "column",
1021
+ "moduleName" : "MIDCOM-MIB",
1022
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.15",
1023
+ "status" : "current",
1024
+ "syntax" : {
1025
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetAddressType"},
1026
+ },
1027
+ "access" : "readwrite",
1028
+ "default" : "ipv4",
1029
+ "description" :
1030
+ """IP version of the external address (A3) and the outside
1031
+ address (A2). Allowed values are ipv4(1) and ipv6(2).
1032
+
1033
+ This object is used as input to a request for establishing
1034
+ a policy rule as well as for indicating the properties of
1035
+ an established policy rule.
1036
+
1037
+
1038
+
1039
+ If object midcomRuleOperStatus of the same entry has the
1040
+ value newEntry(1) or setting(2), then this object can be
1041
+ written by a manager in order to specify the IP version
1042
+ required at the outside of the middlebox. Writing to
1043
+ this object in any state other than newEntry(1) or
1044
+ setting(2) will always fail with an 'inconsistentValue'
1045
+ error.
1046
+ Note that this error code is SNMP specific. If the MIB
1047
+ module is used with other protocols than SNMP, errors with
1048
+ similar semantics specific to those protocols should be
1049
+ returned.
1050
+
1051
+ If object midcomRuleOperStatus of the same entry has the
1052
+ value reserved(7) or enabled(8), then this object
1053
+ indicates the external/outside IP version.
1054
+
1055
+ If object midcomRuleOperStatus of the same entry has a
1056
+ value other than newEntry(1), setting(2), reserved(7) or
1057
+ enabled(8), then the value of this object is irrelevant.""",
1058
+ }, # column
1059
+ "midcomRuleInternalIpAddr" : {
1060
+ "nodetype" : "column",
1061
+ "moduleName" : "MIDCOM-MIB",
1062
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.16",
1063
+ "status" : "current",
1064
+ "syntax" : {
1065
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetAddress"},
1066
+ },
1067
+ "access" : "readwrite",
1068
+ "description" :
1069
+ """The internal IP address (A0).
1070
+
1071
+ This object is used as input to a request for establishing
1072
+ a policy rule as well as for indicating the properties of
1073
+ an established policy rule.
1074
+
1075
+ If object midcomRuleOperStatus of the same entry has the
1076
+ value newEntry(1) or setting(2), then this object can be
1077
+ written by a manager in order to specify the internal IP
1078
+ address for which a reserve policy rule or a enable policy
1079
+ rule is requested to be established. Writing to this
1080
+ object in any state other than newEntry(1) or setting(2)
1081
+ will always fail with an 'inconsistentValue' error.
1082
+ Note that this error code is SNMP specific. If the MIB
1083
+ module is used with other protocols than SNMP, errors with
1084
+ similar semantics specific to those protocols should be
1085
+ returned.
1086
+
1087
+ If object midcomRuleOperStatus of the same entry has the
1088
+ value reserved(7) or enabled(8), then this object will
1089
+ have the value which it had before the transition to this
1090
+
1091
+
1092
+
1093
+ state.
1094
+
1095
+ If object midcomRuleOperStatus of the same entry has a
1096
+ value other than newEntry(1), setting(2), reserved(7) or
1097
+ enabled(8), then the value of this object is irrelevant.""",
1098
+ }, # column
1099
+ "midcomRuleInternalIpPrefixLength" : {
1100
+ "nodetype" : "column",
1101
+ "moduleName" : "MIDCOM-MIB",
1102
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.17",
1103
+ "status" : "current",
1104
+ "syntax" : {
1105
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetAddressPrefixLength"},
1106
+ },
1107
+ "access" : "readwrite",
1108
+ "default" : "128",
1109
+ "description" :
1110
+ """The prefix length of the internal IP address used for
1111
+ wildcarding. A value of 0 indicates a full wildcard;
1112
+ in this case, the value of midcomRuleInternalIpAddr is
1113
+ irrelevant. If midcomRuleInternalIpVersion has a value
1114
+ of ipv4(1), then a value > 31 indicates no wildcarding
1115
+ at all. If midcomRuleInternalIpVersion has a value
1116
+ of ipv4(2), then a value > 127 indicates no wildcarding
1117
+ at all. A MIDCOM-MIB implementation that does not
1118
+ support IP address wildcarding MUST implement this object
1119
+ as read-only with a value of 128. A MIDCOM that does
1120
+ not support wildcarding based on prefix length MAY
1121
+ restrict allowed values for this object to 0 and 128.
1122
+
1123
+ This object is used as input to a request for establishing
1124
+ a policy rule as well as for indicating the properties of
1125
+ an established policy rule.
1126
+
1127
+ If object midcomRuleOperStatus of the same entry has the
1128
+ value newEntry(1) or setting(2), then this object can be
1129
+ written by a manager in order to specify the prefix length
1130
+ of the internal IP address for which a reserve policy rule
1131
+ or an enable policy rule is requested to be established.
1132
+ Writing to this object in any state other than newEntry(1)
1133
+ or setting(2) will always fail with an 'inconsistentValue'
1134
+ error.
1135
+
1136
+ Note that this error code is SNMP specific. If the MIB
1137
+ module is used with other protocols than SNMP, errors with
1138
+ similar semantics specific to those protocols should be
1139
+ returned.
1140
+
1141
+ If object midcomRuleOperStatus of the same entry has the
1142
+ value reserved(7) or enabled(8), then this object will
1143
+ have the value which it had before the transition to this
1144
+ state.
1145
+
1146
+
1147
+
1148
+
1149
+ If object midcomRuleOperStatus of the same entry has a
1150
+ value other than newEntry(1), setting(2), reserved(7), or
1151
+ enabled(8), then the value of this object is irrelevant.""",
1152
+ }, # column
1153
+ "midcomRuleInternalPort" : {
1154
+ "nodetype" : "column",
1155
+ "moduleName" : "MIDCOM-MIB",
1156
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.18",
1157
+ "status" : "current",
1158
+ "syntax" : {
1159
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetPortNumber"},
1160
+ },
1161
+ "access" : "readwrite",
1162
+ "default" : "0",
1163
+ "description" :
1164
+ """The internal port number. A value of 0 is a wildcard.
1165
+
1166
+ This object is used as input to a request for establishing
1167
+ a policy rule as well as for indicating the properties of
1168
+ an established policy rule. It is relevant to the
1169
+ operation of the MIDCOM-MIB implementation only if the
1170
+ value of object midcomTransportProtocol in the same entry
1171
+ has a value other than 0.
1172
+
1173
+ If object midcomRuleOperStatus of the same entry has the
1174
+ value newEntry(1) or setting(2), then this object can be
1175
+ written by a manager in order to specify the internal port
1176
+ number for which a reserve policy rule or an enable policy
1177
+ rule is requested to be established. Writing to this
1178
+ object in any state other than newEntry(1) or setting(2)
1179
+ will always fail with an 'inconsistentValue' error.
1180
+
1181
+ Note that this error code is SNMP specific. If the MIB
1182
+ module is used with other protocols than SNMP, errors with
1183
+ similar semantics specific to those protocols should be
1184
+ returned.
1185
+
1186
+ If object midcomRuleOperStatus of the same entry has the
1187
+ value reserved(7) or enabled(8), then this object will
1188
+ have the value that it had before the transition to this
1189
+ state.
1190
+
1191
+ If object midcomRuleOperStatus of the same entry has a
1192
+ value other than newEntry(1), setting(2), reserved(7), or
1193
+ enabled(8), then the value of this object is irrelevant.""",
1194
+ }, # column
1195
+ "midcomRuleExternalIpAddr" : {
1196
+ "nodetype" : "column",
1197
+ "moduleName" : "MIDCOM-MIB",
1198
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.19",
1199
+ "status" : "current",
1200
+ "syntax" : {
1201
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetAddress"},
1202
+ },
1203
+ "access" : "readwrite",
1204
+ "description" :
1205
+ """The external IP address (A3).
1206
+
1207
+ This object is used as input to a request for establishing
1208
+ a policy rule as well as for indicating the properties of
1209
+ an established policy rule.
1210
+
1211
+ If object midcomRuleOperStatus of the same entry has the
1212
+ value newEntry(1), setting(2), or reserved(7), then this
1213
+ object can be written by a manager in order to specify the
1214
+ external IP address for which an enable policy rule is
1215
+ requested to be established. Writing to this object in
1216
+ any state other than newEntry(1), setting(2), or reserved(7)
1217
+ will always fail with an 'inconsistentValue' error.
1218
+
1219
+ Note that this error code is SNMP specific. If the MIB
1220
+ module is used with other protocols than SNMP, errors with
1221
+ similar semantics specific to those protocols should be
1222
+ returned.
1223
+
1224
+ If object midcomRuleOperStatus of the same entry has the
1225
+ value enabled(8), then this object will have the value
1226
+ that it had before the transition to this state.
1227
+
1228
+ If object midcomRuleOperStatus of the same entry has a
1229
+ value other than newEntry(1), setting(2), reserved(7), or
1230
+ enabled(8), then the value of this object is irrelevant.""",
1231
+ }, # column
1232
+ "midcomRuleExternalIpPrefixLength" : {
1233
+ "nodetype" : "column",
1234
+ "moduleName" : "MIDCOM-MIB",
1235
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.20",
1236
+ "status" : "current",
1237
+ "syntax" : {
1238
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetAddressPrefixLength"},
1239
+ },
1240
+ "access" : "readwrite",
1241
+ "default" : "128",
1242
+ "description" :
1243
+ """The prefix length of the external IP address used for
1244
+ wildcarding. A value of 0 indicates a full wildcard;
1245
+ in this case, the value of midcomRuleExternalIpAddr is
1246
+ irrelevant. If midcomRuleExternalIpVersion has a value
1247
+ of ipv4(1), then a value > 31 indicates no wildcarding
1248
+ at all. If midcomRuleExternalIpVersion has a value
1249
+ of ipv4(2), then a value > 127 indicates no wildcarding
1250
+ at all. A MIDCOM-MIB implementation that does not
1251
+ support IP address wildcarding MUST implement this object
1252
+ as read-only with a value of 128. A MIDCOM that does
1253
+ not support wildcarding based on prefix length MAY
1254
+ restrict allowed values for this object to 0 and 128.
1255
+
1256
+ This object is used as input to a request for establishing
1257
+
1258
+
1259
+
1260
+ a policy rule as well as for indicating the properties of
1261
+ an established policy rule.
1262
+
1263
+ If object midcomRuleOperStatus of the same entry has the
1264
+ value newEntry(1), setting(2), or reserved(7), then this
1265
+ object can be written by a manager in order to specify the
1266
+ prefix length of the external IP address for which an
1267
+ enable policy rule is requested to be established.
1268
+ Writing to this object in any state other than
1269
+ newEntry(1), setting(2), or reserved(7) will always fail
1270
+ with an 'inconsistentValue' error.
1271
+
1272
+ Note that this error code is SNMP specific. If the MIB
1273
+ module is used with other protocols than SNMP, errors with
1274
+ similar semantics specific to those protocols should be
1275
+ returned.
1276
+
1277
+ If object midcomRuleOperStatus of the same entry has the
1278
+ value enabled(8), then this object will have the value
1279
+ that it had before the transition to this state.
1280
+
1281
+ If object midcomRuleOperStatus of the same entry has a
1282
+ value other than newEntry(1), setting(2), reserved(7), or
1283
+ enabled(8), then the value of this object is irrelevant.""",
1284
+ }, # column
1285
+ "midcomRuleExternalPort" : {
1286
+ "nodetype" : "column",
1287
+ "moduleName" : "MIDCOM-MIB",
1288
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.21",
1289
+ "status" : "current",
1290
+ "syntax" : {
1291
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetPortNumber"},
1292
+ },
1293
+ "access" : "readwrite",
1294
+ "default" : "0",
1295
+ "description" :
1296
+ """The external port number. A value of 0 is a wildcard.
1297
+
1298
+ This object is used as input to a request for establishing
1299
+ a policy rule as well as for indicating the properties of
1300
+ an established policy rule. It is relevant to the
1301
+ operation of the MIDCOM-MIB implementation only if the
1302
+ value of object midcomTransportProtocol in the same entry
1303
+ has a value other than 0.
1304
+
1305
+ If object midcomRuleOperStatus of the same entry has the
1306
+ value newEntry(1), setting(2) or reserved(7), then this
1307
+ object can be written by a manager in order to specify the
1308
+ external port number for which an enable policy rule is
1309
+ requested to be established. Writing to this object in
1310
+ any state other than newEntry(1), setting(2) or reserved(7)
1311
+ will always fail with an 'inconsistentValue' error.
1312
+
1313
+
1314
+
1315
+ Note that this error code is SNMP specific. If the MIB
1316
+ module is used with other protocols than SNMP, errors with
1317
+ similar semantics specific to those protocols should be
1318
+ returned.
1319
+
1320
+ If object midcomRuleOperStatus of the same entry has the
1321
+ value enabled(8), then this object will have the value
1322
+ which it had before the transition to this state.
1323
+
1324
+ If object midcomRuleOperStatus of the same entry has a
1325
+ value other than newEntry(1), setting(2), reserved(7) or
1326
+ enabled(8), then the value of this object is irrelevant.""",
1327
+ }, # column
1328
+ "midcomRuleInsideIpAddr" : {
1329
+ "nodetype" : "column",
1330
+ "moduleName" : "MIDCOM-MIB",
1331
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.22",
1332
+ "status" : "current",
1333
+ "syntax" : {
1334
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetAddress"},
1335
+ },
1336
+ "access" : "readonly",
1337
+ "description" :
1338
+ """The inside IP address at the middlebox (A1).
1339
+
1340
+ The value of this object is relevant only if
1341
+ object midcomRuleOperStatus of the same entry has
1342
+ a value of either reserved(7) or enabled(8).""",
1343
+ }, # column
1344
+ "midcomRuleInsidePort" : {
1345
+ "nodetype" : "column",
1346
+ "moduleName" : "MIDCOM-MIB",
1347
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.23",
1348
+ "status" : "current",
1349
+ "syntax" : {
1350
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetPortNumber"},
1351
+ },
1352
+ "access" : "readonly",
1353
+ "description" :
1354
+ """The inside port number at the middlebox.
1355
+ A value of 0 is a wildcard.
1356
+
1357
+ The value of this object is relevant only if
1358
+ object midcomRuleOperStatus of the same entry has
1359
+ a value of either reserved(7) or enabled(8).""",
1360
+ }, # column
1361
+ "midcomRuleOutsideIpAddr" : {
1362
+ "nodetype" : "column",
1363
+ "moduleName" : "MIDCOM-MIB",
1364
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.24",
1365
+ "status" : "current",
1366
+ "syntax" : {
1367
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetAddress"},
1368
+ },
1369
+ "access" : "readonly",
1370
+ "description" :
1371
+ """The outside IP address at the middlebox (A2).
1372
+
1373
+ The value of this object is relevant only if
1374
+
1375
+
1376
+
1377
+ object midcomRuleOperStatus of the same entry has
1378
+ a value of either reserved(7) or enabled(8).""",
1379
+ }, # column
1380
+ "midcomRuleOutsidePort" : {
1381
+ "nodetype" : "column",
1382
+ "moduleName" : "MIDCOM-MIB",
1383
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.25",
1384
+ "status" : "current",
1385
+ "syntax" : {
1386
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetPortNumber"},
1387
+ },
1388
+ "access" : "readonly",
1389
+ "description" :
1390
+ """The outside port number at the middlebox.
1391
+ A value of 0 is a wildcard.
1392
+
1393
+ The value of this object is relevant only if
1394
+ object midcomRuleOperStatus of the same entry has
1395
+ a value of either reserved(7) or enabled(8).""",
1396
+ }, # column
1397
+ "midcomRuleLifetime" : {
1398
+ "nodetype" : "column",
1399
+ "moduleName" : "MIDCOM-MIB",
1400
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.26",
1401
+ "status" : "current",
1402
+ "syntax" : {
1403
+ "type" : { "module" :"", "name" : "Unsigned32"},
1404
+ },
1405
+ "access" : "readwrite",
1406
+ "default" : "180",
1407
+ "units" : "seconds",
1408
+ "description" :
1409
+ """The remaining lifetime in seconds of this policy rule.
1410
+
1411
+ Lifetime of a policy rule starts when object
1412
+ midcomRuleOperStatus in the same entry enters either
1413
+ state reserved(7) or state enabled(8).
1414
+
1415
+ This object is used as input to a request for establishing
1416
+ a policy rule as well as for indicating the properties of
1417
+ an established policy rule.
1418
+
1419
+ If object midcomRuleOperStatus of the same entry has a
1420
+ value of either newEntry(1) or setting(2), then this
1421
+ object can be written by a manager in order to specify
1422
+ the requested lifetime of a policy rule to be established.
1423
+
1424
+ If object midcomRuleOperStatus of the same entry has a
1425
+ value of either reserved(7) or enabled(8), then this
1426
+ object indicates the (continuously decreasing) remaining
1427
+ lifetime of the established policy rule. Note that when
1428
+ entering state reserved(7) or enabled(8), the MIDCOM-MIB
1429
+ implementation can choose a lifetime shorter than the one
1430
+ requested.
1431
+
1432
+ Unlike other parameters of the policy rule, this parameter
1433
+ can still be written in state reserved(7) and enabled(8).
1434
+
1435
+
1436
+
1437
+ Writing to this object is processed by the MIDCOM-MIB
1438
+ implementation by choosing a lifetime value that is
1439
+ greater than 0 and less than or equal to the minimum of
1440
+ the requested value and the value specified by object
1441
+ midcomConfigMaxLifetime:
1442
+
1443
+ 0 <= lt_granted <= MINIMUM(lt_requested, lt_maximum)
1444
+
1445
+ where:
1446
+ - lt_granted is the actually granted lifetime by the
1447
+ MIDCOM-MIB implementation
1448
+ - lt_requested is the requested lifetime of the MIDCOM
1449
+ client
1450
+ - lt_maximum is the value of object
1451
+ midcomConfigMaxLifetime
1452
+
1453
+ SNMP SET requests to this object may be rejected or the
1454
+ value of the object after an accepted SET operation may be
1455
+ less than the value that was contained in the SNMP SET
1456
+ request.
1457
+
1458
+ Successfully writing a value of 0 terminates the policy
1459
+ rule. Note that after a policy rule is terminated, still
1460
+ the entry will exist as long as indicated by the value of
1461
+ midcomRuleStorageTime.
1462
+
1463
+ Writing to this object in any state other than
1464
+ newEntry(1), setting(2), reserved(7), or enabled(7)
1465
+ will always fail with an 'inconsistentValue' error.
1466
+
1467
+ Note that this error code is SNMP specific. If the MIB
1468
+ module is used with other protocols than SNMP, errors with
1469
+ similar semantics specific to those protocols should be
1470
+ returned.
1471
+
1472
+ If object midcomRuleOperStatus of the same entry has a
1473
+ value other than newEntry(1), setting(2), reserved(7), or
1474
+ enabled(8), then the value of this object is irrelevant.""",
1475
+ }, # column
1476
+ "midcomRuleRowStatus" : {
1477
+ "nodetype" : "column",
1478
+ "moduleName" : "MIDCOM-MIB",
1479
+ "oid" : "1.3.6.1.2.1.171.1.1.3.1.27",
1480
+ "status" : "current",
1481
+ "syntax" : {
1482
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
1483
+ },
1484
+ "access" : "readwrite",
1485
+ "description" :
1486
+ """A control that allows entries to be added and removed from
1487
+ this table.
1488
+
1489
+
1490
+
1491
+ Entries can also be removed from this table by setting
1492
+ objects midcomRuleLifetime and midcomRuleStorageTime of
1493
+ an entry to 0.
1494
+
1495
+ Attempts to set a row notInService(2) where the value
1496
+ of the midcomRuleStorageType object is permanent(4) or
1497
+ readOnly(5) will result in an 'notWritable' error.
1498
+
1499
+ Note that this error code is SNMP specific. If the MIB
1500
+ module is used with other protocols than SNMP, errors with
1501
+ similar semantics specific to those protocols should be
1502
+ returned.
1503
+
1504
+ The value of this object has no effect on whether other
1505
+ objects in this conceptual row can be modified.""",
1506
+ }, # column
1507
+ "midcomGroupTable" : {
1508
+ "nodetype" : "table",
1509
+ "moduleName" : "MIDCOM-MIB",
1510
+ "oid" : "1.3.6.1.2.1.171.1.1.4",
1511
+ "status" : "current",
1512
+ "description" :
1513
+ """This table lists all current policy rule groups.
1514
+
1515
+ Entries in this table are created or removed
1516
+ implicitly when entries in the midcomRuleTable are
1517
+ created or removed, respectively. A group entry
1518
+ in this table only exists as long as there are
1519
+ member rules of this group in the midcomRuleTable.
1520
+
1521
+ The table serves for listing the existing groups and
1522
+ their remaining lifetimes and for changing lifetimes
1523
+ of groups and implicitly of all group members.
1524
+ Groups and all their member policy rules can only be
1525
+ deleted by deleting all member policies in the
1526
+ midcomRuleTable.
1527
+
1528
+ Setting midcomGroupLifetime will result in setting
1529
+ the lifetime of all policy members to the same value.""",
1530
+ }, # table
1531
+ "midcomGroupEntry" : {
1532
+ "nodetype" : "row",
1533
+ "moduleName" : "MIDCOM-MIB",
1534
+ "oid" : "1.3.6.1.2.1.171.1.1.4.1",
1535
+ "status" : "current",
1536
+ "linkage" : [
1537
+ "midcomRuleOwner",
1538
+ "midcomGroupIndex",
1539
+ ],
1540
+ "description" :
1541
+ """An entry describing properties of a particular
1542
+ MIDCOM policy rule group.""",
1543
+ }, # row
1544
+ "midcomGroupIndex" : {
1545
+ "nodetype" : "column",
1546
+ "moduleName" : "MIDCOM-MIB",
1547
+ "oid" : "1.3.6.1.2.1.171.1.1.4.1.2",
1548
+ "status" : "current",
1549
+ "syntax" : {
1550
+ "type" : {
1551
+ "basetype" : "Unsigned32",
1552
+ "ranges" : [
1553
+ {
1554
+ "min" : "1",
1555
+ "max" : "4294967295"
1556
+ },
1557
+ ],
1558
+ "range" : {
1559
+ "min" : "1",
1560
+ "max" : "4294967295"
1561
+ },
1562
+ },
1563
+ },
1564
+ "access" : "noaccess",
1565
+ "description" :
1566
+ """The index of this group for the midcomRuleOwner.
1567
+ A group is identified by the combination of
1568
+ midcomRuleOwner and midcomGroupIndex.
1569
+
1570
+ The value of this index must be unique per
1571
+ midcomRuleOwner.""",
1572
+ }, # column
1573
+ "midcomGroupLifetime" : {
1574
+ "nodetype" : "column",
1575
+ "moduleName" : "MIDCOM-MIB",
1576
+ "oid" : "1.3.6.1.2.1.171.1.1.4.1.3",
1577
+ "status" : "current",
1578
+ "syntax" : {
1579
+ "type" : { "module" :"", "name" : "Unsigned32"},
1580
+ },
1581
+ "access" : "readwrite",
1582
+ "units" : "seconds",
1583
+ "description" :
1584
+ """When retrieved, this object delivers the maximum
1585
+ lifetime in seconds of all member rules of this group,
1586
+ i.e., of all rows in the midcomRuleTable that have the
1587
+ same values for midcomRuleOwner and midcomGroupIndex.
1588
+
1589
+ Successfully writing to this object modifies the
1590
+ lifetime of all member policies. Successfully
1591
+ writing a value of 0 terminates all member policies
1592
+ and implicitly deletes the group as soon as all member
1593
+ entries are removed from the midcomRuleTable.
1594
+
1595
+ Note that after a group's lifetime is expired or is
1596
+ set to 0, still the corresponding entry in the
1597
+ midcomGroupTable will exist as long as terminated
1598
+ member policy rules are stored as entries in the
1599
+
1600
+
1601
+
1602
+ midcomRuleTable.
1603
+
1604
+ Writing to this object is processed by the MIDCOM-MIB
1605
+ implementation by choosing a lifetime value that is
1606
+ greater than 0 and less than or equal to the minimum of
1607
+ the requested value and the value specified by object
1608
+ midcomConfigMaxLifetime:
1609
+
1610
+ 0 <= lt_granted <= MINIMUM(lt_requested, lt_maximum)
1611
+
1612
+ where:
1613
+ - lt_granted is the actually granted lifetime by the
1614
+ MIDCOM-MIB implementation
1615
+ - lt_requested is the requested lifetime of the MIDCOM
1616
+ client
1617
+ - lt_maximum is the value of object
1618
+ midcomConfigMaxLifetime
1619
+
1620
+ SNMP SET requests to this object may be rejected or the
1621
+ value of the object after an accepted SET operation may be
1622
+ less than the value that was contained in the SNMP SET
1623
+ request.""",
1624
+ }, # column
1625
+ "midcomConfig" : {
1626
+ "nodetype" : "node",
1627
+ "moduleName" : "MIDCOM-MIB",
1628
+ "oid" : "1.3.6.1.2.1.171.1.2",
1629
+ }, # node
1630
+ "midcomConfigMaxLifetime" : {
1631
+ "nodetype" : "scalar",
1632
+ "moduleName" : "MIDCOM-MIB",
1633
+ "oid" : "1.3.6.1.2.1.171.1.2.1",
1634
+ "status" : "current",
1635
+ "syntax" : {
1636
+ "type" : { "module" :"", "name" : "Unsigned32"},
1637
+ },
1638
+ "access" : "readwrite",
1639
+ "units" : "seconds",
1640
+ "description" :
1641
+ """When retrieved, this object returns the maximum lifetime,
1642
+ in seconds, that this middlebox allows policy rules to
1643
+ have.""",
1644
+ }, # scalar
1645
+ "midcomConfigPersistentRules" : {
1646
+ "nodetype" : "scalar",
1647
+ "moduleName" : "MIDCOM-MIB",
1648
+ "oid" : "1.3.6.1.2.1.171.1.2.2",
1649
+ "status" : "current",
1650
+ "syntax" : {
1651
+ "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
1652
+ },
1653
+ "access" : "readwrite",
1654
+ "description" :
1655
+ """When retrieved, this object returns true(1) if the
1656
+ MIDCOM-MIB implementation can store policy rules
1657
+ persistently. Otherwise, it returns false(2).
1658
+
1659
+ A value of true(1) indicates that there may be
1660
+ entries in the midcomRuleTable with object
1661
+ midcomRuleStorageType set to value nonVolatile(3).""",
1662
+ }, # scalar
1663
+ "midcomConfigIfTable" : {
1664
+ "nodetype" : "table",
1665
+ "moduleName" : "MIDCOM-MIB",
1666
+ "oid" : "1.3.6.1.2.1.171.1.2.3",
1667
+ "status" : "current",
1668
+ "description" :
1669
+ """This table indicates capabilities of the MIDCOM-MIB
1670
+ implementation per IP interface.
1671
+
1672
+ The table is indexed by the object midcomConfigIfIndex.
1673
+
1674
+ For indexing a single interface, this object contains
1675
+ the value of the ifIndex object that is associated
1676
+ with the interface. If an entry with
1677
+ midcomConfigIfIndex = 0 occurs, then bits set in
1678
+ objects of this entry apply to all interfaces for which
1679
+ there is no entry in this table with the interface's
1680
+ index.""",
1681
+ }, # table
1682
+ "midcomConfigIfEntry" : {
1683
+ "nodetype" : "row",
1684
+ "moduleName" : "MIDCOM-MIB",
1685
+ "oid" : "1.3.6.1.2.1.171.1.2.3.1",
1686
+ "status" : "current",
1687
+ "linkage" : [
1688
+ "midcomConfigIfIndex",
1689
+ ],
1690
+ "description" :
1691
+ """An entry describing the capabilities of a middlebox
1692
+ with respect to the indexed IP interface.""",
1693
+ }, # row
1694
+ "midcomConfigIfIndex" : {
1695
+ "nodetype" : "column",
1696
+ "moduleName" : "MIDCOM-MIB",
1697
+ "oid" : "1.3.6.1.2.1.171.1.2.3.1.1",
1698
+ "status" : "current",
1699
+ "syntax" : {
1700
+ "type" : { "module" :"IF-MIB", "name" : "InterfaceIndexOrZero"},
1701
+ },
1702
+ "access" : "noaccess",
1703
+ "description" :
1704
+ """The index of an entry in the midcomConfigIfTable.
1705
+
1706
+ For values different from zero, this object
1707
+ identifies an IP interface by containing the same
1708
+ value as the ifIndex object associated with the
1709
+ interface.
1710
+
1711
+ Note that the index of a particular interface in the
1712
+ ifTable may change after a re-initialization of the
1713
+ middlebox, for example, after adding another interface to
1714
+ it. In such a case, the value of this object may change,
1715
+ but the interface referred to by the MIDCOM-MIB MUST still
1716
+ be the same. If, after a re-initialization of the
1717
+ middlebox, the interface referred to before
1718
+ re-initialization cannot be uniquely mapped anymore to a
1719
+ particular entry in the ifTable, then the value of object
1720
+ midcomConfigIfEnabled of the same entry MUST be changed to
1721
+ false(2).
1722
+
1723
+ If the object has a value of 0, then values
1724
+ specified by further objects of the same entry
1725
+ apply to all interfaces for which there is no
1726
+ explicit entry in the midcomConfigIfTable.""",
1727
+ }, # column
1728
+ "midcomConfigIfBits" : {
1729
+ "nodetype" : "column",
1730
+ "moduleName" : "MIDCOM-MIB",
1731
+ "oid" : "1.3.6.1.2.1.171.1.2.3.1.2",
1732
+ "status" : "current",
1733
+ "syntax" : {
1734
+ "type" : {
1735
+ "basetype" : "Bits",
1736
+ "ipv4" : {
1737
+ "nodetype" : "namednumber",
1738
+ "number" : "0"
1739
+ },
1740
+ "ipv6" : {
1741
+ "nodetype" : "namednumber",
1742
+ "number" : "1"
1743
+ },
1744
+ "addressWildcards" : {
1745
+ "nodetype" : "namednumber",
1746
+ "number" : "2"
1747
+ },
1748
+ "portWildcards" : {
1749
+ "nodetype" : "namednumber",
1750
+ "number" : "3"
1751
+ },
1752
+ "firewall" : {
1753
+ "nodetype" : "namednumber",
1754
+ "number" : "4"
1755
+ },
1756
+ "nat" : {
1757
+ "nodetype" : "namednumber",
1758
+ "number" : "5"
1759
+ },
1760
+ "portTranslation" : {
1761
+ "nodetype" : "namednumber",
1762
+ "number" : "6"
1763
+ },
1764
+ "protocolTranslation" : {
1765
+ "nodetype" : "namednumber",
1766
+ "number" : "7"
1767
+ },
1768
+ "twiceNat" : {
1769
+ "nodetype" : "namednumber",
1770
+ "number" : "8"
1771
+ },
1772
+ "inside" : {
1773
+ "nodetype" : "namednumber",
1774
+ "number" : "9"
1775
+ },
1776
+ },
1777
+ },
1778
+ "access" : "readonly",
1779
+ "description" :
1780
+ """When retrieved, this object returns a set of bits
1781
+ indicating the capabilities (or configuration) of
1782
+ the middlebox with respect to the referenced IP interface.
1783
+ If the index equals 0, then all set bits apply to all
1784
+ interfaces.
1785
+
1786
+ If the ipv4(0) bit is set, then the middlebox supports
1787
+ IPv4 at the indexed IP interface.
1788
+
1789
+ If the ipv6(1) bit is set, then the middlebox supports
1790
+ IPv6 at the indexed IP interface.
1791
+
1792
+ If the addressWildcards(2) bit is set, then the
1793
+ middlebox supports IP address wildcarding at the indexed
1794
+ IP interface.
1795
+
1796
+ If the portWildcards(3) bit is set, then the
1797
+ middlebox supports port wildcarding at the indexed
1798
+ IP interface.
1799
+
1800
+ If the firewall(4) bit is set, then the middlebox offers
1801
+ firewall functionality at the indexed interface.
1802
+
1803
+ If the nat(5) bit is set, then the middlebox offers
1804
+ network address translation service at the indexed
1805
+ interface.
1806
+
1807
+ If the portTranslation(6) bit is set, then the middlebox
1808
+ offers port translation service at the indexed interface.
1809
+ This bit is only relevant if nat(5) is set.
1810
+
1811
+ If the protocolTranslation(7) bit is set, then the
1812
+ middlebox offers protocol translation service between
1813
+ IPv4 and IPv6 at the indexed interface. This bit is only
1814
+ relevant if nat(5) is set.
1815
+
1816
+ If the twiceNat(8) bit is set, then the middlebox offers
1817
+ twice network address translation service at the indexed
1818
+ interface. This bit is only relevant if nat(5) is set.
1819
+
1820
+ If the inside(9) bit is set, then the indexed interface is
1821
+
1822
+
1823
+
1824
+ an inside interface with respect to NAT functionality.
1825
+ Otherwise, it is an outside interface. This bit is only
1826
+ relevant if nat(5) is set. An SNMP agent supporting both
1827
+ the MIDCOM-MIB module and the NAT-MIB module SHOULD ensure
1828
+ that the value of this object is consistent with the values
1829
+ of corresponding objects in the NAT-MIB module.""",
1830
+ }, # column
1831
+ "midcomConfigIfEnabled" : {
1832
+ "nodetype" : "column",
1833
+ "moduleName" : "MIDCOM-MIB",
1834
+ "oid" : "1.3.6.1.2.1.171.1.2.3.1.3",
1835
+ "status" : "current",
1836
+ "syntax" : {
1837
+ "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
1838
+ },
1839
+ "access" : "readwrite",
1840
+ "default" : "true",
1841
+ "description" :
1842
+ """The value of this object indicates the availability of
1843
+ the middlebox service described by midcomConfigIfBits
1844
+ at the indexed IP interface.
1845
+
1846
+ By writing to this object, the MIDCOM support for the
1847
+ entire IP interface can be switched on or off. Setting
1848
+ this object to false(2) immediately stops middlebox
1849
+ support at the indexed IP interface. This implies that
1850
+ all policy rules that use NAT or firewall resources at
1851
+ the indexed IP interface are terminated immediately.
1852
+ In this case, the MIDCOM agent MUST send
1853
+ midcomUnsolicitedRuleEvent to all MIDCOM clients that
1854
+ have access to one of the terminated rules.""",
1855
+ }, # column
1856
+ "midcomConfigFirewallTable" : {
1857
+ "nodetype" : "table",
1858
+ "moduleName" : "MIDCOM-MIB",
1859
+ "oid" : "1.3.6.1.2.1.171.1.2.4",
1860
+ "status" : "current",
1861
+ "description" :
1862
+ """This table lists the firewall configuration per IP interface.
1863
+
1864
+ It can be used for configuring how policy rules created by
1865
+ MIDCOM clients are realized as firewall rules of a firewall
1866
+ implementation. Particularly, the priority used for MIDCOM
1867
+ policy rules can be configured. For a single firewall
1868
+ implementation at a particular IP interface, all MIDCOM
1869
+ policy rules are realized as firewall rules with the same
1870
+
1871
+
1872
+
1873
+ priority. Also, a firewall rule group name can be
1874
+ configured.
1875
+
1876
+ The table is indexed by the object midcomConfigFirewallIndex.
1877
+ For indexing a single interface, this object contains the
1878
+ value of the ifIndex object that is associated with the
1879
+ interface. If an entry with midcomConfigFirewallIndex = 0
1880
+ occurs, then bits set in objects of this entry apply to all
1881
+ interfaces for which there is no entry in this table for the
1882
+ interface's index.""",
1883
+ }, # table
1884
+ "midcomConfigFirewallEntry" : {
1885
+ "nodetype" : "row",
1886
+ "moduleName" : "MIDCOM-MIB",
1887
+ "oid" : "1.3.6.1.2.1.171.1.2.4.1",
1888
+ "status" : "current",
1889
+ "linkage" : [
1890
+ "midcomConfigFirewallIndex",
1891
+ ],
1892
+ "description" :
1893
+ """An entry describing a particular set of
1894
+ firewall resources.""",
1895
+ }, # row
1896
+ "midcomConfigFirewallIndex" : {
1897
+ "nodetype" : "column",
1898
+ "moduleName" : "MIDCOM-MIB",
1899
+ "oid" : "1.3.6.1.2.1.171.1.2.4.1.1",
1900
+ "status" : "current",
1901
+ "syntax" : {
1902
+ "type" : { "module" :"IF-MIB", "name" : "InterfaceIndexOrZero"},
1903
+ },
1904
+ "access" : "noaccess",
1905
+ "description" :
1906
+ """The index of an entry in the midcomConfigFirewallTable.
1907
+
1908
+ For values different from 0, this object identifies an
1909
+ IP interface by containing the same value as the ifIndex
1910
+ object associated with the interface.
1911
+
1912
+ Note that the index of a particular interface in the
1913
+ ifTable may change after a re-initialization of the
1914
+ middlebox, for example, after adding another interface to
1915
+ it. In such a case, the value of this object may change,
1916
+ but the interface referred to by the MIDCOM-MIB MUST still
1917
+ be the same. If, after a re-initialization of the
1918
+ middlebox, the interface referred to before
1919
+ re-initialization cannot be uniquely mapped anymore to a
1920
+ particular entry in the ifTable, then the entry in the
1921
+
1922
+
1923
+
1924
+ midcomConfigFirewallTable MUST be deleted.
1925
+
1926
+ If the object has a value of 0, then values specified by
1927
+ further objects of the same entry apply to all interfaces
1928
+ for which there is no explicit entry in the
1929
+ midcomConfigFirewallTable.""",
1930
+ }, # column
1931
+ "midcomConfigFirewallGroupId" : {
1932
+ "nodetype" : "column",
1933
+ "moduleName" : "MIDCOM-MIB",
1934
+ "oid" : "1.3.6.1.2.1.171.1.2.4.1.2",
1935
+ "status" : "current",
1936
+ "syntax" : {
1937
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
1938
+ },
1939
+ "access" : "readwrite",
1940
+ "description" :
1941
+ """The firewall rule group to which all firewall rules are
1942
+ assigned that the MIDCOM server creates for the interface
1943
+ indicated by object midcomConfigFirewallIndex. If the
1944
+ value of object midcomConfigFirewallIndex is 0, then all
1945
+ firewall rules of the MIDCOM server that are created for
1946
+ interfaces with no specific entry in the
1947
+ midcomConfigFirewallTable are assigned to the firewall
1948
+ rule group indicated by the value of this object.""",
1949
+ }, # column
1950
+ "midcomConfigFirewallPriority" : {
1951
+ "nodetype" : "column",
1952
+ "moduleName" : "MIDCOM-MIB",
1953
+ "oid" : "1.3.6.1.2.1.171.1.2.4.1.3",
1954
+ "status" : "current",
1955
+ "syntax" : {
1956
+ "type" : { "module" :"", "name" : "Unsigned32"},
1957
+ },
1958
+ "access" : "readwrite",
1959
+ "description" :
1960
+ """The priority assigned to all firewall rules that the
1961
+ MIDCOM server creates for the interface indicated by
1962
+ object midcomConfigFirewallIndex. If the value of object
1963
+ midcomConfigFirewallIndex is 0, then this priority is
1964
+ assigned to all firewall rules of the MIDCOM server that
1965
+ are created for interfaces for which there is no specific
1966
+ entry in the midcomConfigFirewallTable.""",
1967
+ }, # column
1968
+ "midcomMonitoring" : {
1969
+ "nodetype" : "node",
1970
+ "moduleName" : "MIDCOM-MIB",
1971
+ "oid" : "1.3.6.1.2.1.171.1.3",
1972
+ }, # node
1973
+ "midcomResourceTable" : {
1974
+ "nodetype" : "table",
1975
+ "moduleName" : "MIDCOM-MIB",
1976
+ "oid" : "1.3.6.1.2.1.171.1.3.1",
1977
+ "status" : "current",
1978
+ "description" :
1979
+ """This table lists all used middlebox resources per
1980
+ MIDCOM policy rule.
1981
+
1982
+ The midcomResourceTable augments the
1983
+
1984
+
1985
+
1986
+ midcomRuleTable.""",
1987
+ }, # table
1988
+ "midcomResourceEntry" : {
1989
+ "nodetype" : "row",
1990
+ "moduleName" : "MIDCOM-MIB",
1991
+ "oid" : "1.3.6.1.2.1.171.1.3.1.1",
1992
+ "status" : "current",
1993
+ "linkage" : [
1994
+ { "MIDCOM-MIB" : {
1995
+ "indexkind" : "augments",
1996
+ "relatedNode" : "midcomRuleEntry",
1997
+ }},
1998
+ ],
1999
+ "description" :
2000
+ """An entry describing a particular set of middlebox
2001
+ resources.""",
2002
+ }, # row
2003
+ "midcomRscNatInternalAddrBindMode" : {
2004
+ "nodetype" : "column",
2005
+ "moduleName" : "MIDCOM-MIB",
2006
+ "oid" : "1.3.6.1.2.1.171.1.3.1.1.4",
2007
+ "status" : "current",
2008
+ "syntax" : {
2009
+ "type" : { "module" :"MIDCOM-MIB", "name" : "MidcomNatBindMode"},
2010
+ },
2011
+ "access" : "readonly",
2012
+ "description" :
2013
+ """An indication of whether this policy rule uses an address
2014
+ NAT bind or an address-port NAT bind for binding the
2015
+ internal address.
2016
+
2017
+ If the MIDCOM-MIB module is operated together with
2018
+ the NAT-MIB module (RFC 4008) then object
2019
+ midcomRscNatInternalAddrBindMode contains the same
2020
+ value as the corresponding object
2021
+ natSessionPrivateSrcEPBindMode of the NAT-MIB module.""",
2022
+ }, # column
2023
+ "midcomRscNatInternalAddrBindId" : {
2024
+ "nodetype" : "column",
2025
+ "moduleName" : "MIDCOM-MIB",
2026
+ "oid" : "1.3.6.1.2.1.171.1.3.1.1.5",
2027
+ "status" : "current",
2028
+ "syntax" : {
2029
+ "type" : { "module" :"NAT-MIB", "name" : "NatBindIdOrZero"},
2030
+ },
2031
+ "access" : "readonly",
2032
+ "description" :
2033
+ """This object references to the allocated internal NAT
2034
+ bind that is used by this policy rule. A NAT bind
2035
+ describes the mapping of internal addresses to
2036
+ outside addresses. MIDCOM-MIB implementations can
2037
+
2038
+
2039
+
2040
+ read this object to learn the corresponding NAT bind
2041
+ resource for this particular policy rule.
2042
+
2043
+ If the MIDCOM-MIB module is operated together with
2044
+ the NAT-MIB module (RFC 4008) then object
2045
+ midcomRscNatInternalAddrBindId contains the same
2046
+ value as the corresponding object
2047
+ natSessionPrivateSrcEPBindId of the NAT-MIB module.""",
2048
+ }, # column
2049
+ "midcomRscNatInsideAddrBindMode" : {
2050
+ "nodetype" : "column",
2051
+ "moduleName" : "MIDCOM-MIB",
2052
+ "oid" : "1.3.6.1.2.1.171.1.3.1.1.6",
2053
+ "status" : "current",
2054
+ "syntax" : {
2055
+ "type" : { "module" :"MIDCOM-MIB", "name" : "MidcomNatBindMode"},
2056
+ },
2057
+ "access" : "readonly",
2058
+ "description" :
2059
+ """An indication of whether this policy rule uses an address
2060
+ NAT bind or an address-port NAT bind for binding the
2061
+ external address.
2062
+
2063
+ If the MIDCOM-MIB module is operated together with
2064
+ the NAT-MIB module (RFC 4008), then object
2065
+ midcomRscNatInsideAddrBindMode contains the same
2066
+ value as the corresponding object
2067
+ natSessionPrivateDstEPBindMode of the NAT-MIB module.""",
2068
+ }, # column
2069
+ "midcomRscNatInsideAddrBindId" : {
2070
+ "nodetype" : "column",
2071
+ "moduleName" : "MIDCOM-MIB",
2072
+ "oid" : "1.3.6.1.2.1.171.1.3.1.1.7",
2073
+ "status" : "current",
2074
+ "syntax" : {
2075
+ "type" : { "module" :"NAT-MIB", "name" : "NatBindIdOrZero"},
2076
+ },
2077
+ "access" : "readonly",
2078
+ "description" :
2079
+ """This object refers to the allocated external NAT
2080
+ bind that is used by this policy rule. A NAT bind
2081
+ describes the mapping of external addresses to
2082
+ inside addresses. MIDCOM-MIB implementations can
2083
+ read this object to learn the corresponding NAT bind
2084
+ resource for this particular policy rule.
2085
+
2086
+ If the MIDCOM-MIB module is operated together with the
2087
+ NAT-MIB module (RFC 4008), then object
2088
+ midcomRscNatInsideAddrBindId contains the same
2089
+ value as the corresponding object
2090
+ natSessionPrivateDstEPBindId of the NAT-MIB module.""",
2091
+ }, # column
2092
+ "midcomRscNatSessionId1" : {
2093
+ "nodetype" : "column",
2094
+ "moduleName" : "MIDCOM-MIB",
2095
+ "oid" : "1.3.6.1.2.1.171.1.3.1.1.8",
2096
+ "status" : "current",
2097
+ "syntax" : {
2098
+ "type" : { "module" :"MIDCOM-MIB", "name" : "MidcomNatSessionIdOrZero"},
2099
+ },
2100
+ "access" : "readonly",
2101
+ "description" :
2102
+ """This object refers to the first allocated NAT session for
2103
+ this policy rule. MIDCOM-MIB implementations can read this
2104
+ object to learn whether or not a NAT session for a
2105
+ particular policy rule is used. A value of 0 means that no
2106
+ NAT session is allocated for this policy rule. A value
2107
+ other than 0 refers to the NAT session.""",
2108
+ }, # column
2109
+ "midcomRscNatSessionId2" : {
2110
+ "nodetype" : "column",
2111
+ "moduleName" : "MIDCOM-MIB",
2112
+ "oid" : "1.3.6.1.2.1.171.1.3.1.1.9",
2113
+ "status" : "current",
2114
+ "syntax" : {
2115
+ "type" : { "module" :"MIDCOM-MIB", "name" : "MidcomNatSessionIdOrZero"},
2116
+ },
2117
+ "access" : "readonly",
2118
+ "description" :
2119
+ """This object refers to the second allocated NAT session for
2120
+ this policy rule. MIDCOM-MIB implementations can read this
2121
+ object to learn whether or not a NAT session for a
2122
+ particular policy rule is used. A value of 0 means that no
2123
+ NAT session is allocated for this policy rule. A value
2124
+ other than 0 refers to the NAT session.""",
2125
+ }, # column
2126
+ "midcomRscFirewallRuleId" : {
2127
+ "nodetype" : "column",
2128
+ "moduleName" : "MIDCOM-MIB",
2129
+ "oid" : "1.3.6.1.2.1.171.1.3.1.1.10",
2130
+ "status" : "current",
2131
+ "syntax" : {
2132
+ "type" : { "module" :"", "name" : "Unsigned32"},
2133
+ },
2134
+ "access" : "readonly",
2135
+ "description" :
2136
+ """This object refers to the allocated firewall
2137
+ rule in the firewall engine for this policy rule.
2138
+ MIDCOM-MIB implementations can read this value to
2139
+ learn whether a firewall rule for this particular
2140
+ policy rule is used or not. A value of 0 means that
2141
+ no firewall rule is allocated for this policy rule.
2142
+ A value other than 0 refers to the firewall rule
2143
+ number within the firewall engine.""",
2144
+ }, # column
2145
+ "midcomStatistics" : {
2146
+ "nodetype" : "node",
2147
+ "moduleName" : "MIDCOM-MIB",
2148
+ "oid" : "1.3.6.1.2.1.171.1.3.2",
2149
+ }, # node
2150
+ "midcomCurrentOwners" : {
2151
+ "nodetype" : "scalar",
2152
+ "moduleName" : "MIDCOM-MIB",
2153
+ "oid" : "1.3.6.1.2.1.171.1.3.2.1",
2154
+ "status" : "current",
2155
+ "syntax" : {
2156
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Gauge32"},
2157
+ },
2158
+ "access" : "readonly",
2159
+ "description" :
2160
+ """The number of different values for midcomRuleOwner
2161
+ for all current entries in the midcomRuleTable.""",
2162
+ }, # scalar
2163
+ "midcomTotalRejectedRuleEntries" : {
2164
+ "nodetype" : "scalar",
2165
+ "moduleName" : "MIDCOM-MIB",
2166
+ "oid" : "1.3.6.1.2.1.171.1.3.2.2",
2167
+ "status" : "current",
2168
+ "syntax" : {
2169
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
2170
+ },
2171
+ "access" : "readonly",
2172
+ "description" :
2173
+ """The total number of failed attempts to create an entry
2174
+ in the midcomRuleTable.""",
2175
+ }, # scalar
2176
+ "midcomCurrentRulesIncomplete" : {
2177
+ "nodetype" : "scalar",
2178
+ "moduleName" : "MIDCOM-MIB",
2179
+ "oid" : "1.3.6.1.2.1.171.1.3.2.3",
2180
+ "status" : "current",
2181
+ "syntax" : {
2182
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Gauge32"},
2183
+ },
2184
+ "access" : "readonly",
2185
+ "description" :
2186
+ """The current number of policy rules that are incomplete.
2187
+
2188
+ Policy rules are loaded via row entries in the
2189
+ midcomRuleTable. This object counts policy rules that are
2190
+ loaded but not fully specified, i.e., they are in state
2191
+ newEntry(1) or setting(2).""",
2192
+ }, # scalar
2193
+ "midcomTotalIncorrectReserveRules" : {
2194
+ "nodetype" : "scalar",
2195
+ "moduleName" : "MIDCOM-MIB",
2196
+ "oid" : "1.3.6.1.2.1.171.1.3.2.4",
2197
+ "status" : "current",
2198
+ "syntax" : {
2199
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
2200
+ },
2201
+ "access" : "readonly",
2202
+ "description" :
2203
+ """The total number of policy reserve rules that failed
2204
+ parameter check and entered state incorrectRequest(4).""",
2205
+ }, # scalar
2206
+ "midcomTotalRejectedReserveRules" : {
2207
+ "nodetype" : "scalar",
2208
+ "moduleName" : "MIDCOM-MIB",
2209
+ "oid" : "1.3.6.1.2.1.171.1.3.2.5",
2210
+ "status" : "current",
2211
+ "syntax" : {
2212
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
2213
+ },
2214
+ "access" : "readonly",
2215
+ "description" :
2216
+ """The total number of policy reserve rules that failed
2217
+ while being processed and entered state requestRejected(6).""",
2218
+ }, # scalar
2219
+ "midcomCurrentActiveReserveRules" : {
2220
+ "nodetype" : "scalar",
2221
+ "moduleName" : "MIDCOM-MIB",
2222
+ "oid" : "1.3.6.1.2.1.171.1.3.2.6",
2223
+ "status" : "current",
2224
+ "syntax" : {
2225
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Gauge32"},
2226
+ },
2227
+ "access" : "readonly",
2228
+ "description" :
2229
+ """The number of currently active policy reserve rules.""",
2230
+ }, # scalar
2231
+ "midcomTotalExpiredReserveRules" : {
2232
+ "nodetype" : "scalar",
2233
+ "moduleName" : "MIDCOM-MIB",
2234
+ "oid" : "1.3.6.1.2.1.171.1.3.2.7",
2235
+ "status" : "current",
2236
+ "syntax" : {
2237
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
2238
+ },
2239
+ "access" : "readonly",
2240
+ "description" :
2241
+ """The total number of expired policy reserve rules
2242
+ (entered termination state timedOut(9)).""",
2243
+ }, # scalar
2244
+ "midcomTotalTerminatedOnRqReserveRules" : {
2245
+ "nodetype" : "scalar",
2246
+ "moduleName" : "MIDCOM-MIB",
2247
+ "oid" : "1.3.6.1.2.1.171.1.3.2.8",
2248
+ "status" : "current",
2249
+ "syntax" : {
2250
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
2251
+ },
2252
+ "access" : "readonly",
2253
+ "description" :
2254
+ """The total number of policy reserve rules that were
2255
+ terminated on request (entered termination state
2256
+ terminatedOnRequest(10)).""",
2257
+ }, # scalar
2258
+ "midcomTotalTerminatedReserveRules" : {
2259
+ "nodetype" : "scalar",
2260
+ "moduleName" : "MIDCOM-MIB",
2261
+ "oid" : "1.3.6.1.2.1.171.1.3.2.9",
2262
+ "status" : "current",
2263
+ "syntax" : {
2264
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
2265
+ },
2266
+ "access" : "readonly",
2267
+ "description" :
2268
+ """The total number of policy reserve rules that were
2269
+ terminated, but not on request (entered termination state
2270
+ terminated(11)).""",
2271
+ }, # scalar
2272
+ "midcomTotalIncorrectEnableRules" : {
2273
+ "nodetype" : "scalar",
2274
+ "moduleName" : "MIDCOM-MIB",
2275
+ "oid" : "1.3.6.1.2.1.171.1.3.2.10",
2276
+ "status" : "current",
2277
+ "syntax" : {
2278
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
2279
+ },
2280
+ "access" : "readonly",
2281
+ "description" :
2282
+ """The total number of policy enable rules that failed
2283
+ parameter check and entered state incorrectRequest(4).""",
2284
+ }, # scalar
2285
+ "midcomTotalRejectedEnableRules" : {
2286
+ "nodetype" : "scalar",
2287
+ "moduleName" : "MIDCOM-MIB",
2288
+ "oid" : "1.3.6.1.2.1.171.1.3.2.11",
2289
+ "status" : "current",
2290
+ "syntax" : {
2291
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
2292
+ },
2293
+ "access" : "readonly",
2294
+ "description" :
2295
+ """The total number of policy enable rules that failed
2296
+ while being processed and entered state requestRejected(6).""",
2297
+ }, # scalar
2298
+ "midcomCurrentActiveEnableRules" : {
2299
+ "nodetype" : "scalar",
2300
+ "moduleName" : "MIDCOM-MIB",
2301
+ "oid" : "1.3.6.1.2.1.171.1.3.2.12",
2302
+ "status" : "current",
2303
+ "syntax" : {
2304
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Gauge32"},
2305
+ },
2306
+ "access" : "readonly",
2307
+ "description" :
2308
+ """The number of currently active policy enable rules.""",
2309
+ }, # scalar
2310
+ "midcomTotalExpiredEnableRules" : {
2311
+ "nodetype" : "scalar",
2312
+ "moduleName" : "MIDCOM-MIB",
2313
+ "oid" : "1.3.6.1.2.1.171.1.3.2.13",
2314
+ "status" : "current",
2315
+ "syntax" : {
2316
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
2317
+ },
2318
+ "access" : "readonly",
2319
+ "description" :
2320
+ """The total number of expired policy enable rules
2321
+ (entered termination state timedOut(9)).""",
2322
+ }, # scalar
2323
+ "midcomTotalTerminatedOnRqEnableRules" : {
2324
+ "nodetype" : "scalar",
2325
+ "moduleName" : "MIDCOM-MIB",
2326
+ "oid" : "1.3.6.1.2.1.171.1.3.2.14",
2327
+ "status" : "current",
2328
+ "syntax" : {
2329
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
2330
+ },
2331
+ "access" : "readonly",
2332
+ "description" :
2333
+ """The total number of policy enable rules that were
2334
+ terminated on request (entered termination state
2335
+ terminatedOnRequest(10)).""",
2336
+ }, # scalar
2337
+ "midcomTotalTerminatedEnableRules" : {
2338
+ "nodetype" : "scalar",
2339
+ "moduleName" : "MIDCOM-MIB",
2340
+ "oid" : "1.3.6.1.2.1.171.1.3.2.15",
2341
+ "status" : "current",
2342
+ "syntax" : {
2343
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
2344
+ },
2345
+ "access" : "readonly",
2346
+ "description" :
2347
+ """The total number of policy enable rules that were
2348
+ terminated, but not on request (entered termination state
2349
+ terminated(11)).""",
2350
+ }, # scalar
2351
+ "midcomConformance" : {
2352
+ "nodetype" : "node",
2353
+ "moduleName" : "MIDCOM-MIB",
2354
+ "oid" : "1.3.6.1.2.1.171.2",
2355
+ }, # node
2356
+ "midcomCompliances" : {
2357
+ "nodetype" : "node",
2358
+ "moduleName" : "MIDCOM-MIB",
2359
+ "oid" : "1.3.6.1.2.1.171.2.1",
2360
+ }, # node
2361
+ "midcomGroups" : {
2362
+ "nodetype" : "node",
2363
+ "moduleName" : "MIDCOM-MIB",
2364
+ "oid" : "1.3.6.1.2.1.171.2.2",
2365
+ }, # node
2366
+ }, # nodes
2367
+
2368
+ "notifications" : {
2369
+ "midcomUnsolicitedRuleEvent" : {
2370
+ "nodetype" : "notification",
2371
+ "moduleName" : "MIDCOM-MIB",
2372
+ "oid" : "1.3.6.1.2.1.171.0.1",
2373
+ "status" : "current",
2374
+ "objects" : {
2375
+ "midcomRuleOperStatus" : {
2376
+ "nodetype" : "object",
2377
+ "module" : "MIDCOM-MIB"
2378
+ },
2379
+ "midcomRuleLifetime" : {
2380
+ "nodetype" : "object",
2381
+ "module" : "MIDCOM-MIB"
2382
+ },
2383
+ },
2384
+ "description" :
2385
+ """This notification is generated whenever the value of
2386
+ midcomRuleOperStatus enters any error state or any
2387
+ termination state without an explicit trigger by a
2388
+ MIDCOM client.""",
2389
+ }, # notification
2390
+ "midcomSolicitedRuleEvent" : {
2391
+ "nodetype" : "notification",
2392
+ "moduleName" : "MIDCOM-MIB",
2393
+ "oid" : "1.3.6.1.2.1.171.0.2",
2394
+ "status" : "current",
2395
+ "objects" : {
2396
+ "midcomRuleOperStatus" : {
2397
+ "nodetype" : "object",
2398
+ "module" : "MIDCOM-MIB"
2399
+ },
2400
+ "midcomRuleLifetime" : {
2401
+ "nodetype" : "object",
2402
+ "module" : "MIDCOM-MIB"
2403
+ },
2404
+ },
2405
+ "description" :
2406
+ """This notification is generated whenever the value
2407
+ of midcomRuleOperStatus enters one of the states
2408
+ {reserved, enabled, any error state, any termination state}
2409
+ as a result of a MIDCOM agent writing successfully to
2410
+ object midcomRuleAdminStatus.
2411
+
2412
+ In addition, it is generated when the lifetime of
2413
+ a rule was changed by successfully writing to object
2414
+ midcomRuleLifetime.""",
2415
+ }, # notification
2416
+ "midcomSolicitedGroupEvent" : {
2417
+ "nodetype" : "notification",
2418
+ "moduleName" : "MIDCOM-MIB",
2419
+ "oid" : "1.3.6.1.2.1.171.0.3",
2420
+ "status" : "current",
2421
+ "objects" : {
2422
+ "midcomGroupLifetime" : {
2423
+ "nodetype" : "object",
2424
+ "module" : "MIDCOM-MIB"
2425
+ },
2426
+ },
2427
+ "description" :
2428
+ """This notification is generated for indicating that the
2429
+ lifetime of all member rules of the group was changed by
2430
+ successfully writing to object midcomGroupLifetime.
2431
+
2432
+ Note that this notification is only sent if the lifetime
2433
+ of a group was changed by successfully writing to object
2434
+ midcomGroupLifetime. No notification is sent
2435
+ - if a group's lifetime is changed by writing to object
2436
+ midcomRuleLifetime of any of its member policies,
2437
+ - if a group's lifetime expires (in this case,
2438
+ notifications are sent for all member policies), or
2439
+ - if the group is terminated by terminating the last
2440
+ of its member policies without writing to object
2441
+ midcomGroupLifetime.""",
2442
+ }, # notification
2443
+ }, # notifications
2444
+
2445
+ "groups" : {
2446
+ "midcomRuleGroup" : {
2447
+ "nodetype" : "group",
2448
+ "moduleName" : "MIDCOM-MIB",
2449
+ "oid" : "1.3.6.1.2.1.171.2.2.1",
2450
+ "status" : "current",
2451
+ "members" : {
2452
+ "midcomRuleAdminStatus" : {
2453
+ "nodetype" : "member",
2454
+ "module" : "MIDCOM-MIB"
2455
+ },
2456
+ "midcomRuleOperStatus" : {
2457
+ "nodetype" : "member",
2458
+ "module" : "MIDCOM-MIB"
2459
+ },
2460
+ "midcomRuleStorageType" : {
2461
+ "nodetype" : "member",
2462
+ "module" : "MIDCOM-MIB"
2463
+ },
2464
+ "midcomRuleStorageTime" : {
2465
+ "nodetype" : "member",
2466
+ "module" : "MIDCOM-MIB"
2467
+ },
2468
+ "midcomRuleError" : {
2469
+ "nodetype" : "member",
2470
+ "module" : "MIDCOM-MIB"
2471
+ },
2472
+ "midcomRuleInterface" : {
2473
+ "nodetype" : "member",
2474
+ "module" : "MIDCOM-MIB"
2475
+ },
2476
+ "midcomRuleFlowDirection" : {
2477
+ "nodetype" : "member",
2478
+ "module" : "MIDCOM-MIB"
2479
+ },
2480
+ "midcomRuleMaxIdleTime" : {
2481
+ "nodetype" : "member",
2482
+ "module" : "MIDCOM-MIB"
2483
+ },
2484
+ "midcomRuleTransportProtocol" : {
2485
+ "nodetype" : "member",
2486
+ "module" : "MIDCOM-MIB"
2487
+ },
2488
+ "midcomRulePortRange" : {
2489
+ "nodetype" : "member",
2490
+ "module" : "MIDCOM-MIB"
2491
+ },
2492
+ "midcomRuleInternalIpVersion" : {
2493
+ "nodetype" : "member",
2494
+ "module" : "MIDCOM-MIB"
2495
+ },
2496
+ "midcomRuleExternalIpVersion" : {
2497
+ "nodetype" : "member",
2498
+ "module" : "MIDCOM-MIB"
2499
+ },
2500
+ "midcomRuleInternalIpAddr" : {
2501
+ "nodetype" : "member",
2502
+ "module" : "MIDCOM-MIB"
2503
+ },
2504
+ "midcomRuleInternalIpPrefixLength" : {
2505
+ "nodetype" : "member",
2506
+ "module" : "MIDCOM-MIB"
2507
+ },
2508
+ "midcomRuleInternalPort" : {
2509
+ "nodetype" : "member",
2510
+ "module" : "MIDCOM-MIB"
2511
+ },
2512
+ "midcomRuleExternalIpAddr" : {
2513
+ "nodetype" : "member",
2514
+ "module" : "MIDCOM-MIB"
2515
+ },
2516
+ "midcomRuleExternalIpPrefixLength" : {
2517
+ "nodetype" : "member",
2518
+ "module" : "MIDCOM-MIB"
2519
+ },
2520
+ "midcomRuleExternalPort" : {
2521
+ "nodetype" : "member",
2522
+ "module" : "MIDCOM-MIB"
2523
+ },
2524
+ "midcomRuleInsideIpAddr" : {
2525
+ "nodetype" : "member",
2526
+ "module" : "MIDCOM-MIB"
2527
+ },
2528
+ "midcomRuleInsidePort" : {
2529
+ "nodetype" : "member",
2530
+ "module" : "MIDCOM-MIB"
2531
+ },
2532
+ "midcomRuleOutsideIpAddr" : {
2533
+ "nodetype" : "member",
2534
+ "module" : "MIDCOM-MIB"
2535
+ },
2536
+ "midcomRuleOutsidePort" : {
2537
+ "nodetype" : "member",
2538
+ "module" : "MIDCOM-MIB"
2539
+ },
2540
+ "midcomRuleLifetime" : {
2541
+ "nodetype" : "member",
2542
+ "module" : "MIDCOM-MIB"
2543
+ },
2544
+ "midcomRuleRowStatus" : {
2545
+ "nodetype" : "member",
2546
+ "module" : "MIDCOM-MIB"
2547
+ },
2548
+ "midcomGroupLifetime" : {
2549
+ "nodetype" : "member",
2550
+ "module" : "MIDCOM-MIB"
2551
+ },
2552
+ }, # members
2553
+ "description" :
2554
+ """A collection of objects providing information about
2555
+ policy rules and policy rule groups.""",
2556
+ }, # group
2557
+ "midcomCapabilitiesGroup" : {
2558
+ "nodetype" : "group",
2559
+ "moduleName" : "MIDCOM-MIB",
2560
+ "oid" : "1.3.6.1.2.1.171.2.2.2",
2561
+ "status" : "current",
2562
+ "members" : {
2563
+ "midcomConfigMaxLifetime" : {
2564
+ "nodetype" : "member",
2565
+ "module" : "MIDCOM-MIB"
2566
+ },
2567
+ "midcomConfigPersistentRules" : {
2568
+ "nodetype" : "member",
2569
+ "module" : "MIDCOM-MIB"
2570
+ },
2571
+ "midcomConfigIfBits" : {
2572
+ "nodetype" : "member",
2573
+ "module" : "MIDCOM-MIB"
2574
+ },
2575
+ "midcomConfigIfEnabled" : {
2576
+ "nodetype" : "member",
2577
+ "module" : "MIDCOM-MIB"
2578
+ },
2579
+ }, # members
2580
+ "description" :
2581
+ """A collection of objects providing information about
2582
+ the capabilities of a middlebox.""",
2583
+ }, # group
2584
+ "midcomConfigFirewallGroup" : {
2585
+ "nodetype" : "group",
2586
+ "moduleName" : "MIDCOM-MIB",
2587
+ "oid" : "1.3.6.1.2.1.171.2.2.3",
2588
+ "status" : "current",
2589
+ "members" : {
2590
+ "midcomConfigFirewallGroupId" : {
2591
+ "nodetype" : "member",
2592
+ "module" : "MIDCOM-MIB"
2593
+ },
2594
+ "midcomConfigFirewallPriority" : {
2595
+ "nodetype" : "member",
2596
+ "module" : "MIDCOM-MIB"
2597
+ },
2598
+ }, # members
2599
+ "description" :
2600
+ """A collection of objects providing information about
2601
+ the firewall rule group and firewall rule priority to
2602
+ be used by firewalls loaded through MIDCOM.""",
2603
+ }, # group
2604
+ "midcomResourceGroup" : {
2605
+ "nodetype" : "group",
2606
+ "moduleName" : "MIDCOM-MIB",
2607
+ "oid" : "1.3.6.1.2.1.171.2.2.4",
2608
+ "status" : "current",
2609
+ "members" : {
2610
+ "midcomRscNatInternalAddrBindMode" : {
2611
+ "nodetype" : "member",
2612
+ "module" : "MIDCOM-MIB"
2613
+ },
2614
+ "midcomRscNatInternalAddrBindId" : {
2615
+ "nodetype" : "member",
2616
+ "module" : "MIDCOM-MIB"
2617
+ },
2618
+ "midcomRscNatInsideAddrBindMode" : {
2619
+ "nodetype" : "member",
2620
+ "module" : "MIDCOM-MIB"
2621
+ },
2622
+ "midcomRscNatInsideAddrBindId" : {
2623
+ "nodetype" : "member",
2624
+ "module" : "MIDCOM-MIB"
2625
+ },
2626
+ "midcomRscNatSessionId1" : {
2627
+ "nodetype" : "member",
2628
+ "module" : "MIDCOM-MIB"
2629
+ },
2630
+ "midcomRscNatSessionId2" : {
2631
+ "nodetype" : "member",
2632
+ "module" : "MIDCOM-MIB"
2633
+ },
2634
+ "midcomRscFirewallRuleId" : {
2635
+ "nodetype" : "member",
2636
+ "module" : "MIDCOM-MIB"
2637
+ },
2638
+ }, # members
2639
+ "description" :
2640
+ """A collection of objects providing information about
2641
+ the used NAT and firewall resources.""",
2642
+ }, # group
2643
+ "midcomStatisticsGroup" : {
2644
+ "nodetype" : "group",
2645
+ "moduleName" : "MIDCOM-MIB",
2646
+ "oid" : "1.3.6.1.2.1.171.2.2.5",
2647
+ "status" : "current",
2648
+ "members" : {
2649
+ "midcomCurrentOwners" : {
2650
+ "nodetype" : "member",
2651
+ "module" : "MIDCOM-MIB"
2652
+ },
2653
+ "midcomTotalRejectedRuleEntries" : {
2654
+ "nodetype" : "member",
2655
+ "module" : "MIDCOM-MIB"
2656
+ },
2657
+ "midcomCurrentRulesIncomplete" : {
2658
+ "nodetype" : "member",
2659
+ "module" : "MIDCOM-MIB"
2660
+ },
2661
+ "midcomTotalIncorrectReserveRules" : {
2662
+ "nodetype" : "member",
2663
+ "module" : "MIDCOM-MIB"
2664
+ },
2665
+ "midcomTotalRejectedReserveRules" : {
2666
+ "nodetype" : "member",
2667
+ "module" : "MIDCOM-MIB"
2668
+ },
2669
+ "midcomCurrentActiveReserveRules" : {
2670
+ "nodetype" : "member",
2671
+ "module" : "MIDCOM-MIB"
2672
+ },
2673
+ "midcomTotalExpiredReserveRules" : {
2674
+ "nodetype" : "member",
2675
+ "module" : "MIDCOM-MIB"
2676
+ },
2677
+ "midcomTotalTerminatedOnRqReserveRules" : {
2678
+ "nodetype" : "member",
2679
+ "module" : "MIDCOM-MIB"
2680
+ },
2681
+ "midcomTotalTerminatedReserveRules" : {
2682
+ "nodetype" : "member",
2683
+ "module" : "MIDCOM-MIB"
2684
+ },
2685
+ "midcomTotalIncorrectEnableRules" : {
2686
+ "nodetype" : "member",
2687
+ "module" : "MIDCOM-MIB"
2688
+ },
2689
+ "midcomTotalRejectedEnableRules" : {
2690
+ "nodetype" : "member",
2691
+ "module" : "MIDCOM-MIB"
2692
+ },
2693
+ "midcomCurrentActiveEnableRules" : {
2694
+ "nodetype" : "member",
2695
+ "module" : "MIDCOM-MIB"
2696
+ },
2697
+ "midcomTotalExpiredEnableRules" : {
2698
+ "nodetype" : "member",
2699
+ "module" : "MIDCOM-MIB"
2700
+ },
2701
+ "midcomTotalTerminatedOnRqEnableRules" : {
2702
+ "nodetype" : "member",
2703
+ "module" : "MIDCOM-MIB"
2704
+ },
2705
+ "midcomTotalTerminatedEnableRules" : {
2706
+ "nodetype" : "member",
2707
+ "module" : "MIDCOM-MIB"
2708
+ },
2709
+ }, # members
2710
+ "description" :
2711
+ """A collection of objects providing statistical
2712
+ information about the MIDCOM server.""",
2713
+ }, # group
2714
+ "midcomNotificationsGroup" : {
2715
+ "nodetype" : "group",
2716
+ "moduleName" : "MIDCOM-MIB",
2717
+ "oid" : "1.3.6.1.2.1.171.2.2.6",
2718
+ "status" : "current",
2719
+ "members" : {
2720
+ "midcomUnsolicitedRuleEvent" : {
2721
+ "nodetype" : "member",
2722
+ "module" : "MIDCOM-MIB"
2723
+ },
2724
+ "midcomSolicitedRuleEvent" : {
2725
+ "nodetype" : "member",
2726
+ "module" : "MIDCOM-MIB"
2727
+ },
2728
+ "midcomSolicitedGroupEvent" : {
2729
+ "nodetype" : "member",
2730
+ "module" : "MIDCOM-MIB"
2731
+ },
2732
+ }, # members
2733
+ "description" :
2734
+ """The notifications emitted by the midcomMIB.""",
2735
+ }, # group
2736
+ }, # groups
2737
+
2738
+ "compliances" : {
2739
+ "midcomCompliance" : {
2740
+ "nodetype" : "compliance",
2741
+ "moduleName" : "MIDCOM-MIB",
2742
+ "oid" : "1.3.6.1.2.1.171.2.1.1",
2743
+ "status" : "current",
2744
+ "description" :
2745
+ """The compliance statement for implementations of the
2746
+ MIDCOM-MIB module.
2747
+
2748
+ Note that compliance with this compliance
2749
+ statement requires compliance with the
2750
+ ifCompliance3 MODULE-COMPLIANCE statement of the
2751
+ IF-MIB [RFC2863].""",
2752
+ "requires" : {
2753
+ "midcomRuleGroup" : {
2754
+ "nodetype" : "mandatory",
2755
+ "module" : "MIDCOM-MIB"
2756
+ },
2757
+ "midcomNotificationsGroup" : {
2758
+ "nodetype" : "mandatory",
2759
+ "module" : "MIDCOM-MIB"
2760
+ },
2761
+ "midcomCapabilitiesGroup" : {
2762
+ "nodetype" : "mandatory",
2763
+ "module" : "MIDCOM-MIB"
2764
+ },
2765
+ "midcomStatisticsGroup" : {
2766
+ "nodetype" : "mandatory",
2767
+ "module" : "MIDCOM-MIB"
2768
+ },
2769
+ "midcomConfigFirewallGroup" : {
2770
+ "nodetype" : "optional",
2771
+ "module" : "MIDCOM-MIB",
2772
+ "description" :
2773
+ """A compliant implementation does not have to implement
2774
+ the midcomConfigFirewallGroup.""",
2775
+ },
2776
+ "midcomResourceGroup" : {
2777
+ "nodetype" : "optional",
2778
+ "module" : "MIDCOM-MIB",
2779
+ "description" :
2780
+ """A compliant implementation does not have to implement
2781
+ the midcomResourceGroup.""",
2782
+ },
2783
+ }, # requires
2784
+ "refinements" : {
2785
+ "midcomRuleInternalIpPrefixLength" : {
2786
+ "module" : "MIDCOM-MIB",
2787
+ "access" : "readonly",
2788
+ "description" :
2789
+ """Write access is not required. When write access is
2790
+ not supported, return 128 as the value of this object.
2791
+ A value of 128 means that the function represented by
2792
+ this option is not supported.""",
2793
+ },
2794
+ "midcomRuleExternalIpPrefixLength" : {
2795
+ "module" : "MIDCOM-MIB",
2796
+ "access" : "readonly",
2797
+ "description" :
2798
+ """Write access is not required. When write access is
2799
+ not supported, return 128 as the value of this object.
2800
+
2801
+
2802
+
2803
+ A value of 128 means that the function represented by
2804
+ this option is not supported.""",
2805
+ },
2806
+ "midcomRuleMaxIdleTime" : {
2807
+ "module" : "MIDCOM-MIB",
2808
+ "access" : "readonly",
2809
+ "description" :
2810
+ """Write access is not required. When write access is
2811
+ not supported, return 0 as the value of this object.
2812
+ A value of 0 means that the function represented by
2813
+ this option is not supported.""",
2814
+ },
2815
+ "midcomRuleInterface" : {
2816
+ "module" : "MIDCOM-MIB",
2817
+ "access" : "readonly",
2818
+ "description" :
2819
+ """Write access is not required.""",
2820
+ },
2821
+ "midcomConfigMaxLifetime" : {
2822
+ "module" : "MIDCOM-MIB",
2823
+ "access" : "readonly",
2824
+ "description" :
2825
+ """Write access is not required.""",
2826
+ },
2827
+ "midcomConfigPersistentRules" : {
2828
+ "module" : "MIDCOM-MIB",
2829
+ "access" : "readonly",
2830
+ "description" :
2831
+ """Write access is not required.""",
2832
+ },
2833
+ "midcomConfigIfEnabled" : {
2834
+ "module" : "MIDCOM-MIB",
2835
+ "access" : "readonly",
2836
+ "description" :
2837
+ """Write access is not required.""",
2838
+ },
2839
+ "midcomConfigFirewallGroupId" : {
2840
+ "module" : "MIDCOM-MIB",
2841
+ "access" : "readonly",
2842
+ "description" :
2843
+ """Write access is not required.""",
2844
+ },
2845
+ "midcomConfigFirewallPriority" : {
2846
+ "module" : "MIDCOM-MIB",
2847
+ "access" : "readonly",
2848
+ "description" :
2849
+ """Write access is not required.""",
2850
+ },
2851
+ }, # refinements
2852
+
2853
+ }, # compliance
2854
+ }, # compliances
2855
+
2856
+ }