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,3316 @@
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 POLICY-BASED-MANAGEMENT-MIB
6
+
7
+ FILENAME = "./libsmi-0.5.0/mibs/ietf/POLICY-BASED-MANAGEMENT-MIB"
8
+
9
+ MIB = {
10
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
11
+
12
+ "POLICY-BASED-MANAGEMENT-MIB" : {
13
+ "nodetype" : "module",
14
+ "language" : "SMIv2",
15
+ "organization" :
16
+ """IETF SNMP Configuration Working Group""",
17
+ "contact" :
18
+ """
19
+
20
+
21
+
22
+
23
+ Steve Waldbusser
24
+ Phone: +1-650-948-6500
25
+ Fax: +1-650-745-0671
26
+ Email: waldbusser@nextbeacon.com
27
+
28
+ Jon Saperia (WG Co-chair)
29
+ JDS Consulting, Inc.
30
+ 84 Kettell Plain Road.
31
+ Stow MA 01775
32
+ USA
33
+ Phone: +1-978-461-0249
34
+ Fax: +1-617-249-0874
35
+ Email: saperia@jdscons.com
36
+
37
+ Thippanna Hongal
38
+ Riverstone Networks, Inc.
39
+ 5200 Great America Parkway
40
+ Santa Clara, CA, 95054
41
+ USA
42
+
43
+ Phone: +1-408-878-6562
44
+ Fax: +1-408-878-6501
45
+ Email: hongal@riverstonenet.com
46
+
47
+ David Partain (WG Co-chair)
48
+ Postal: Ericsson AB
49
+ P.O. Box 1248
50
+ SE-581 12 Linkoping
51
+ Sweden
52
+ Tel: +46 13 28 41 44
53
+ E-mail: David.Partain@ericsson.com
54
+
55
+ Any questions or comments about this document can also be
56
+ directed to the working group at snmpconf@snmp.com.""",
57
+ "description" :
58
+ """The MIB module for policy-based configuration of SNMP
59
+ infrastructures.
60
+
61
+ Copyright (C) The Internet Society (2005). This version of
62
+ this MIB module is part of RFC 4011; see the RFC itself for
63
+ full legal notices.""",
64
+ "revisions" : (
65
+ {
66
+ "date" : "2005-02-07 00:00",
67
+ "description" :
68
+ """The original version of this MIB, published as RFC4011.""",
69
+ },
70
+ ),
71
+ "identity node" : "pmMib",
72
+ },
73
+
74
+ "imports" : (
75
+ {"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
76
+ {"module" : "SNMPv2-SMI", "name" : "OBJECT-TYPE"},
77
+ {"module" : "SNMPv2-SMI", "name" : "NOTIFICATION-TYPE"},
78
+ {"module" : "SNMPv2-SMI", "name" : "Counter32"},
79
+ {"module" : "SNMPv2-SMI", "name" : "Gauge32"},
80
+ {"module" : "SNMPv2-SMI", "name" : "Unsigned32"},
81
+ {"module" : "SNMPv2-SMI", "name" : "mib-2"},
82
+ {"module" : "SNMPv2-TC", "name" : "RowStatus"},
83
+ {"module" : "SNMPv2-TC", "name" : "RowPointer"},
84
+ {"module" : "SNMPv2-TC", "name" : "TEXTUAL-CONVENTION"},
85
+ {"module" : "SNMPv2-TC", "name" : "DateAndTime"},
86
+ {"module" : "SNMPv2-TC", "name" : "StorageType"},
87
+ {"module" : "SNMPv2-CONF", "name" : "MODULE-COMPLIANCE"},
88
+ {"module" : "SNMPv2-CONF", "name" : "OBJECT-GROUP"},
89
+ {"module" : "SNMPv2-CONF", "name" : "NOTIFICATION-GROUP"},
90
+ {"module" : "SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
91
+ ),
92
+
93
+ "typedefs" : {
94
+ "PmUTF8String" : {
95
+ "basetype" : "OctetString",
96
+ "status" : "current",
97
+ "ranges" : [
98
+ {
99
+ "min" : "0",
100
+ "max" : "65535"
101
+ },
102
+ ],
103
+ "range" : {
104
+ "min" : "0",
105
+ "max" : "65535"
106
+ },
107
+ "description" :
108
+ """An octet string containing information typically in
109
+ human-readable form.
110
+
111
+ To facilitate internationalization, this
112
+ information is represented by using the ISO/IEC
113
+ IS 10646-1 character set, encoded as an octet
114
+ string using the UTF-8 transformation format
115
+ described in RFC 3629.
116
+
117
+ As additional code points are added by
118
+ amendments to the 10646 standard from time
119
+ to time, implementations must be prepared to
120
+ encounter any code point from 0x00000000 to
121
+ 0x10FFFF. Byte sequences that do not
122
+ correspond to the valid UTF-8 encoding of a
123
+ code point or that are outside this range are
124
+ prohibited.
125
+
126
+ The use of control codes should be avoided.
127
+
128
+ When it is necessary to represent a newline,
129
+ the control code sequence CR LF should be used.
130
+
131
+ For code points not directly supported by user
132
+ interface hardware or software, an alternative
133
+ means of entry and display, such as hexadecimal,
134
+ may be provided.
135
+
136
+ For information encoded in 7-bit US-ASCII,
137
+ the UTF-8 encoding is identical to the
138
+ US-ASCII encoding.
139
+
140
+ UTF-8 may require multiple bytes to represent a
141
+ single character/code point; thus, the length
142
+ of this object in octets may be different from
143
+ the number of characters encoded. Similarly,
144
+ size constraints refer to the number of encoded
145
+ octets, not the number of characters represented
146
+ by an encoding.
147
+
148
+ Note that when this TC is used for an object
149
+ used or envisioned to be used as an index, then
150
+ a SIZE restriction MUST be specified so that the
151
+ number of sub-identifiers for any object instance
152
+ does not exceed the limit of 128, as defined by
153
+
154
+
155
+
156
+ RFC 3416.
157
+
158
+ Note that the size of PmUTF8String object is
159
+ measured in octets, not characters.""",
160
+ },
161
+ }, # typedefs
162
+
163
+ "nodes" : {
164
+ "pmMib" : {
165
+ "nodetype" : "node",
166
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
167
+ "oid" : "1.3.6.1.2.1.124",
168
+ "status" : "current",
169
+ }, # node
170
+ "pmNotifications" : {
171
+ "nodetype" : "node",
172
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
173
+ "oid" : "1.3.6.1.2.1.124.0",
174
+ }, # node
175
+ "pmPolicyTable" : {
176
+ "nodetype" : "table",
177
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
178
+ "oid" : "1.3.6.1.2.1.124.1",
179
+ "status" : "current",
180
+ "description" :
181
+ """The policy table. A policy is a pairing of a
182
+ policyCondition and a policyAction that is used to apply the
183
+ action to a selected set of elements.""",
184
+ }, # table
185
+ "pmPolicyEntry" : {
186
+ "nodetype" : "row",
187
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
188
+ "oid" : "1.3.6.1.2.1.124.1.1",
189
+ "create" : "true",
190
+ "status" : "current",
191
+ "linkage" : [
192
+ "pmPolicyAdminGroup",
193
+ "pmPolicyIndex",
194
+ ],
195
+ "description" :
196
+ """An entry in the policy table representing one policy.""",
197
+ }, # row
198
+ "pmPolicyAdminGroup" : {
199
+ "nodetype" : "column",
200
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
201
+ "oid" : "1.3.6.1.2.1.124.1.1.1",
202
+ "status" : "current",
203
+ "syntax" : {
204
+ "type" : {
205
+ "basetype" : "OctetString",
206
+ "parent module" : {
207
+ "name" : "POLICY-BASED-MANAGEMENT-MIB",
208
+ "type" : "PmUTF8String",
209
+ },
210
+ "ranges" : [
211
+ {
212
+ "min" : "0",
213
+ "max" : "32"
214
+ },
215
+ ],
216
+ "range" : {
217
+ "min" : "0",
218
+ "max" : "32"
219
+ },
220
+ },
221
+ },
222
+ "access" : "noaccess",
223
+ "description" :
224
+ """An administratively assigned string that can be used to group
225
+ policies for convenience, for readability, or to simplify
226
+ configuration of access control.
227
+
228
+ The value of this string does not affect policy processing in
229
+ any way. If grouping is not desired or necessary, this object
230
+ may be set to a zero-length string.""",
231
+ }, # column
232
+ "pmPolicyIndex" : {
233
+ "nodetype" : "column",
234
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
235
+ "oid" : "1.3.6.1.2.1.124.1.1.2",
236
+ "status" : "current",
237
+ "syntax" : {
238
+ "type" : {
239
+ "basetype" : "Unsigned32",
240
+ "ranges" : [
241
+ {
242
+ "min" : "1",
243
+ "max" : "4294967295"
244
+ },
245
+ ],
246
+ "range" : {
247
+ "min" : "1",
248
+ "max" : "4294967295"
249
+ },
250
+ },
251
+ },
252
+ "access" : "noaccess",
253
+ "description" :
254
+ """A unique index for this policy entry, unique among all
255
+ policies regardless of administrative group.""",
256
+ }, # column
257
+ "pmPolicyPrecedenceGroup" : {
258
+ "nodetype" : "column",
259
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
260
+ "oid" : "1.3.6.1.2.1.124.1.1.3",
261
+ "status" : "current",
262
+ "syntax" : {
263
+ "type" : {
264
+ "basetype" : "OctetString",
265
+ "parent module" : {
266
+ "name" : "POLICY-BASED-MANAGEMENT-MIB",
267
+ "type" : "PmUTF8String",
268
+ },
269
+ "ranges" : [
270
+ {
271
+ "min" : "0",
272
+ "max" : "32"
273
+ },
274
+ ],
275
+ "range" : {
276
+ "min" : "0",
277
+ "max" : "32"
278
+ },
279
+ },
280
+ },
281
+ "access" : "readwrite",
282
+ "description" :
283
+ """An administratively assigned string that is used to group
284
+ policies. For each element, only one policy in the same
285
+ precedence group may be active on that element. If multiple
286
+ policies would be active on an element (because their
287
+ conditions return non-zero), the execution environment will
288
+ only allow the policy with the highest value of
289
+ pmPolicyPrecedence to be active.
290
+
291
+ All values of this object must have been successfully
292
+ transformed by Stringprep RFC 3454. Management stations
293
+ must perform this translation and must only set this object to
294
+ string values that have been transformed.""",
295
+ }, # column
296
+ "pmPolicyPrecedence" : {
297
+ "nodetype" : "column",
298
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
299
+ "oid" : "1.3.6.1.2.1.124.1.1.4",
300
+ "status" : "current",
301
+ "syntax" : {
302
+ "type" : {
303
+ "basetype" : "Unsigned32",
304
+ "ranges" : [
305
+ {
306
+ "min" : "0",
307
+ "max" : "65535"
308
+ },
309
+ ],
310
+ "range" : {
311
+ "min" : "0",
312
+ "max" : "65535"
313
+ },
314
+ },
315
+ },
316
+ "access" : "readwrite",
317
+ "description" :
318
+ """If, while checking to see which policy conditions match an
319
+ element, 2 or more ready policies in the same precedence group
320
+ match the same element, the pmPolicyPrecedence object provides
321
+ the rule to arbitrate which single policy will be active on
322
+ 'this element'. Of policies in the same precedence group, only
323
+ the ready and matching policy with the highest precedence
324
+ value (e.g., 2 is higher than 1) will have its policy action
325
+ periodically executed on 'this element'.
326
+
327
+ When a policy is active on an element but the condition ceases
328
+ to match the element, its action (if currently running) will
329
+ be allowed to finish and then the condition-matching ready
330
+ policy with the next-highest precedence will immediately
331
+ become active (and have its action run immediately). If the
332
+ condition of a higher-precedence ready policy suddenly begins
333
+ matching an element, the previously-active policy's action (if
334
+ currently running) will be allowed to finish and then the
335
+ higher precedence policy will immediately become active. Its
336
+ action will run immediately, and any lower-precedence matching
337
+ policy will not be active anymore.
338
+
339
+ In the case where multiple ready policies share the highest
340
+ value, it is an implementation-dependent matter as to which
341
+ single policy action will be chosen.
342
+
343
+ Note that if it is necessary to take certain actions after a
344
+ policy is no longer active on an element, these actions should
345
+ be included in a lower-precedence policy that is in the same
346
+ precedence group.""",
347
+ }, # column
348
+ "pmPolicySchedule" : {
349
+ "nodetype" : "column",
350
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
351
+ "oid" : "1.3.6.1.2.1.124.1.1.5",
352
+ "status" : "current",
353
+ "syntax" : {
354
+ "type" : {
355
+ "basetype" : "Unsigned32",
356
+ "ranges" : [
357
+ {
358
+ "min" : "1",
359
+ "max" : "4294967295"
360
+ },
361
+ ],
362
+ "range" : {
363
+ "min" : "1",
364
+ "max" : "4294967295"
365
+ },
366
+ },
367
+ },
368
+ "access" : "readwrite",
369
+ "description" :
370
+ """This policy will be ready if any of the associated schedule
371
+ entries are active.
372
+
373
+ If the value of this object is 0, this policy is always
374
+ ready.
375
+
376
+ If the value of this object is non-zero but doesn't
377
+ refer to a schedule group that includes an active schedule,
378
+ then the policy will not be ready, even if this is due to a
379
+ misconfiguration of this object or the pmSchedTable.""",
380
+ }, # column
381
+ "pmPolicyElementTypeFilter" : {
382
+ "nodetype" : "column",
383
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
384
+ "oid" : "1.3.6.1.2.1.124.1.1.6",
385
+ "status" : "current",
386
+ "syntax" : {
387
+ "type" : {
388
+ "basetype" : "OctetString",
389
+ "parent module" : {
390
+ "name" : "POLICY-BASED-MANAGEMENT-MIB",
391
+ "type" : "PmUTF8String",
392
+ },
393
+ "ranges" : [
394
+ {
395
+ "min" : "0",
396
+ "max" : "128"
397
+ },
398
+ ],
399
+ "range" : {
400
+ "min" : "0",
401
+ "max" : "128"
402
+ },
403
+ },
404
+ },
405
+ "access" : "readwrite",
406
+ "description" :
407
+ """This object specifies the element types for which this policy
408
+ can be executed.
409
+
410
+ The format of this object will be a sequence of
411
+ pmElementTypeRegOIDPrefix values, encoded in the following
412
+ BNF form:
413
+
414
+ elementTypeFilter: oid [ ';' oid ]*
415
+ oid: subid [ '.' subid ]*
416
+ subid: '0' | decimal_constant
417
+
418
+ For example, to register for the policy to be run on all
419
+ interface elements, the 'ifEntry' element type will be
420
+ registered as '1.3.6.1.2.1.2.2.1'.
421
+
422
+ If a value is included that does not represent a registered
423
+ pmElementTypeRegOIDPrefix, then that value will be ignored.""",
424
+ }, # column
425
+ "pmPolicyConditionScriptIndex" : {
426
+ "nodetype" : "column",
427
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
428
+ "oid" : "1.3.6.1.2.1.124.1.1.7",
429
+ "status" : "current",
430
+ "syntax" : {
431
+ "type" : {
432
+ "basetype" : "Unsigned32",
433
+ "ranges" : [
434
+ {
435
+ "min" : "1",
436
+ "max" : "4294967295"
437
+ },
438
+ ],
439
+ "range" : {
440
+ "min" : "1",
441
+ "max" : "4294967295"
442
+ },
443
+ },
444
+ },
445
+ "access" : "readonly",
446
+ "description" :
447
+ """A pointer to the row or rows in the pmPolicyCodeTable that
448
+ contain the condition code for this policy. When a policy
449
+ entry is created, a pmPolicyCodeIndex value unused by this
450
+ policy's adminGroup will be assigned to this object.
451
+
452
+ A policy condition is one or more PolicyScript statements
453
+ that result(s) in a boolean value that represents whether
454
+ an element is a member of a set of elements upon which an
455
+ action is to be performed. If a policy is ready and the
456
+ condition returns true for an element of a proper element
457
+ type, and if no higher-precedence policy should be active,
458
+ then the policy is active on that element.
459
+
460
+ Condition evaluation stops immediately when any run-time
461
+ exception is detected, and the policyAction is not executed.
462
+
463
+ The policyCondition is evaluated for various elements. Any
464
+ element for which the policyCondition returns any nonzero value
465
+ will match the condition and will have the associated
466
+
467
+
468
+
469
+ policyAction executed on that element unless a
470
+ higher-precedence policy in the same precedence group also
471
+ matches 'this element'.
472
+
473
+ If the condition object is empty (contains no code) or
474
+ otherwise does not return a value, the element will not be
475
+ matched.
476
+
477
+ When this condition is executed, if SNMP requests are made to
478
+ the local system and secModel/secName/secLevel aren't
479
+ specified, access to objects is under the security
480
+ credentials of the requester who most recently modified the
481
+ associated pmPolicyAdminStatus object. If SNMP requests are
482
+ made in which secModel/secName/secLevel are specified, then
483
+ the specified credentials are retrieved from the local
484
+ configuration datastore only if VACM is configured to
485
+ allow access to the requester who most recently modified the
486
+ associated pmPolicyAdminStatus object. See the Security
487
+ Considerations section for more information.""",
488
+ }, # column
489
+ "pmPolicyActionScriptIndex" : {
490
+ "nodetype" : "column",
491
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
492
+ "oid" : "1.3.6.1.2.1.124.1.1.8",
493
+ "status" : "current",
494
+ "syntax" : {
495
+ "type" : {
496
+ "basetype" : "Unsigned32",
497
+ "ranges" : [
498
+ {
499
+ "min" : "1",
500
+ "max" : "4294967295"
501
+ },
502
+ ],
503
+ "range" : {
504
+ "min" : "1",
505
+ "max" : "4294967295"
506
+ },
507
+ },
508
+ },
509
+ "access" : "readonly",
510
+ "description" :
511
+ """A pointer to the row or rows in the pmPolicyCodeTable that
512
+ contain the action code for this policy. When a policy entry
513
+ is created, a pmPolicyCodeIndex value unused by this policy's
514
+ adminGroup will be assigned to this object.
515
+
516
+ A PolicyAction is an operation performed on a
517
+ set of elements for which the policy is active.
518
+
519
+ Action evaluation stops immediately when any run-time
520
+ exception is detected.
521
+
522
+ When this condition is executed, if SNMP requests are made to
523
+ the local system and secModel/secName/secLevel aren't
524
+ specified, access to objects is under the security
525
+ credentials of the requester who most recently modified the
526
+ associated pmPolicyAdminStatus object. If SNMP requests are
527
+ made in which secModel/secName/secLevel are specified, then
528
+ the specified credentials are retrieved from the local
529
+ configuration datastore only if VACM is configured to
530
+ allow access to the requester who most recently modified the
531
+ associated pmPolicyAdminStatus object. See the Security
532
+ Considerations section for more information.""",
533
+ }, # column
534
+ "pmPolicyParameters" : {
535
+ "nodetype" : "column",
536
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
537
+ "oid" : "1.3.6.1.2.1.124.1.1.9",
538
+ "status" : "current",
539
+ "syntax" : {
540
+ "type" : {
541
+ "basetype" : "OctetString",
542
+ "ranges" : [
543
+ {
544
+ "min" : "0",
545
+ "max" : "65535"
546
+ },
547
+ ],
548
+ "range" : {
549
+ "min" : "0",
550
+ "max" : "65535"
551
+ },
552
+ },
553
+ },
554
+ "access" : "readwrite",
555
+ "description" :
556
+ """From time to time, policy scripts may seek one or more
557
+ parameters (e.g., site-specific constants). These parameters
558
+ may be installed with the script in this object and are
559
+ accessible to the script via the getParameters() function. If
560
+ it is necessary for multiple parameters to be passed to the
561
+ script, the script can choose whatever encoding/delimiting
562
+ mechanism is most appropriate.""",
563
+ }, # column
564
+ "pmPolicyConditionMaxLatency" : {
565
+ "nodetype" : "column",
566
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
567
+ "oid" : "1.3.6.1.2.1.124.1.1.10",
568
+ "status" : "current",
569
+ "syntax" : {
570
+ "type" : {
571
+ "basetype" : "Unsigned32",
572
+ "ranges" : [
573
+ {
574
+ "min" : "0",
575
+ "max" : "2147483647"
576
+ },
577
+ ],
578
+ "range" : {
579
+ "min" : "0",
580
+ "max" : "2147483647"
581
+ },
582
+ },
583
+ },
584
+ "access" : "readwrite",
585
+ "units" : "milliseconds",
586
+ "description" :
587
+ """Every element under the control of this agent is
588
+ re-checked periodically to see whether it is under control
589
+ of this policy by re-running the condition for this policy.
590
+ This object lets the manager control the maximum amount of
591
+ time that may pass before an element is re-checked.
592
+
593
+ In other words, in any given interval of this duration, all
594
+ elements must be re-checked. Note that how the policy agent
595
+ schedules the checking of various elements within this
596
+ interval is an implementation-dependent matter.
597
+ Implementations may wish to re-run a condition more
598
+ quickly if they note a change to the role strings for an
599
+ element.""",
600
+ }, # column
601
+ "pmPolicyActionMaxLatency" : {
602
+ "nodetype" : "column",
603
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
604
+ "oid" : "1.3.6.1.2.1.124.1.1.11",
605
+ "status" : "current",
606
+ "syntax" : {
607
+ "type" : {
608
+ "basetype" : "Unsigned32",
609
+ "ranges" : [
610
+ {
611
+ "min" : "0",
612
+ "max" : "2147483647"
613
+ },
614
+ ],
615
+ "range" : {
616
+ "min" : "0",
617
+ "max" : "2147483647"
618
+ },
619
+ },
620
+ },
621
+ "access" : "readwrite",
622
+ "units" : "milliseconds",
623
+ "description" :
624
+ """Every element that matches this policy's condition and is
625
+ therefore under control of this policy will have this policy's
626
+ action executed periodically to ensure that the element
627
+ remains in the state dictated by the policy.
628
+ This object lets the manager control the maximum amount of
629
+
630
+
631
+
632
+ time that may pass before an element has the action run on
633
+ it.
634
+
635
+ In other words, in any given interval of this duration, all
636
+ elements under control of this policy must have the action run
637
+ on them. Note that how the policy agent schedules the policy
638
+ action on various elements within this interval is an
639
+ implementation-dependent matter.""",
640
+ }, # column
641
+ "pmPolicyMaxIterations" : {
642
+ "nodetype" : "column",
643
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
644
+ "oid" : "1.3.6.1.2.1.124.1.1.12",
645
+ "status" : "current",
646
+ "syntax" : {
647
+ "type" : { "module" :"", "name" : "Unsigned32"},
648
+ },
649
+ "access" : "readwrite",
650
+ "description" :
651
+ """If a condition or action script iterates in loops too many
652
+ times in one invocation, the execution environment may
653
+ consider it in an infinite loop or otherwise not acting
654
+ as intended and may be terminated by the execution
655
+ environment. The execution environment will count the
656
+ cumulative number of times all 'for' or 'while' loops iterated
657
+ and will apply a threshold to determine when to terminate the
658
+ script. What threshold the execution environment uses is an
659
+ implementation-dependent manner, but the value of
660
+ this object SHOULD be the basis for choosing the threshold for
661
+ each script. The value of this object represents a
662
+ policy-specific threshold and can be tuned for policies of
663
+ varying workloads. If this value is zero, no
664
+ threshold will be enforced except for any
665
+ implementation-dependent maximum. Regardless of this value,
666
+ the agent is allowed to terminate any script invocation that
667
+ exceeds a local CPU or memory limitation.
668
+
669
+ Note that the condition and action invocations are tracked
670
+ separately.""",
671
+ }, # column
672
+ "pmPolicyDescription" : {
673
+ "nodetype" : "column",
674
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
675
+ "oid" : "1.3.6.1.2.1.124.1.1.13",
676
+ "status" : "current",
677
+ "syntax" : {
678
+ "type" : { "module" :"POLICY-BASED-MANAGEMENT-MIB", "name" : "PmUTF8String"},
679
+ },
680
+ "access" : "readwrite",
681
+ "description" :
682
+ """A description of this rule and its significance, typically
683
+ provided by a human.""",
684
+ }, # column
685
+ "pmPolicyMatches" : {
686
+ "nodetype" : "column",
687
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
688
+ "oid" : "1.3.6.1.2.1.124.1.1.14",
689
+ "status" : "current",
690
+ "syntax" : {
691
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Gauge32"},
692
+ },
693
+ "access" : "readonly",
694
+ "units" : "elements",
695
+ "description" :
696
+ """The number of elements that, in their most recent execution
697
+ of the associated condition, were matched by the condition.""",
698
+ }, # column
699
+ "pmPolicyAbnormalTerminations" : {
700
+ "nodetype" : "column",
701
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
702
+ "oid" : "1.3.6.1.2.1.124.1.1.15",
703
+ "status" : "current",
704
+ "syntax" : {
705
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Gauge32"},
706
+ },
707
+ "access" : "readonly",
708
+ "units" : "elements",
709
+ "description" :
710
+ """The number of elements that, in their most recent execution
711
+ of the associated condition or action, have experienced a
712
+ run-time exception and terminated abnormally. Note that if a
713
+ policy was experiencing a run-time exception while processing
714
+ a particular element but runs normally on a subsequent
715
+ invocation, this number can decline.""",
716
+ }, # column
717
+ "pmPolicyExecutionErrors" : {
718
+ "nodetype" : "column",
719
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
720
+ "oid" : "1.3.6.1.2.1.124.1.1.16",
721
+ "status" : "current",
722
+ "syntax" : {
723
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
724
+ },
725
+ "access" : "readonly",
726
+ "units" : "errors",
727
+ "description" :
728
+ """The total number of times that execution of this policy's
729
+ condition or action has been terminated due to run-time
730
+ exceptions.""",
731
+ }, # column
732
+ "pmPolicyDebugging" : {
733
+ "nodetype" : "column",
734
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
735
+ "oid" : "1.3.6.1.2.1.124.1.1.17",
736
+ "status" : "current",
737
+ "syntax" : {
738
+ "type" : {
739
+ "basetype" : "Enumeration",
740
+ "off" : {
741
+ "nodetype" : "namednumber",
742
+ "number" : "1"
743
+ },
744
+ "on" : {
745
+ "nodetype" : "namednumber",
746
+ "number" : "2"
747
+ },
748
+ },
749
+ },
750
+ "access" : "readwrite",
751
+ "default" : "off",
752
+ "description" :
753
+ """The status of debugging for this policy. If this is turned
754
+ on(2), log entries will be created in the pmDebuggingTable
755
+ for each run-time exception that is experienced by this
756
+ policy.""",
757
+ }, # column
758
+ "pmPolicyAdminStatus" : {
759
+ "nodetype" : "column",
760
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
761
+ "oid" : "1.3.6.1.2.1.124.1.1.18",
762
+ "status" : "current",
763
+ "syntax" : {
764
+ "type" : {
765
+ "basetype" : "Enumeration",
766
+ "disabled" : {
767
+ "nodetype" : "namednumber",
768
+ "number" : "1"
769
+ },
770
+ "enabled" : {
771
+ "nodetype" : "namednumber",
772
+ "number" : "2"
773
+ },
774
+ "enabledAutoRemove" : {
775
+ "nodetype" : "namednumber",
776
+ "number" : "3"
777
+ },
778
+ },
779
+ },
780
+ "access" : "readwrite",
781
+ "description" :
782
+ """The administrative status of this policy.
783
+
784
+ The policy will be valid only if the associated
785
+ pmPolicyRowStatus is set to active(1) and this object is set
786
+ to enabled(2) or enabledAutoRemove(3).
787
+
788
+ If this object is set to enabledAutoRemove(3), the next time
789
+ the associated schedule moves from the active state to the
790
+ inactive state, this policy will immediately be deleted,
791
+ including any associated entries in the pmPolicyCodeTable.
792
+
793
+ The following related objects may not be changed unless this
794
+ object is set to disabled(1):
795
+ pmPolicyPrecedenceGroup, pmPolicyPrecedence,
796
+ pmPolicySchedule, pmPolicyElementTypeFilter,
797
+ pmPolicyConditionScriptIndex, pmPolicyActionScriptIndex,
798
+ pmPolicyParameters, and any pmPolicyCodeTable row
799
+ referenced by this policy.
800
+ In order to change any of these parameters, the policy must
801
+ be moved to the disabled(1) state, changed, and then
802
+ re-enabled.
803
+
804
+ When this policy moves to either enabled state from the
805
+ disabled state, any cached values of policy condition must be
806
+ erased, and any Policy or PolicyElement scratchpad values for
807
+ this policy should be removed. Policy execution will begin by
808
+ testing the policy condition on all appropriate elements.""",
809
+ }, # column
810
+ "pmPolicyStorageType" : {
811
+ "nodetype" : "column",
812
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
813
+ "oid" : "1.3.6.1.2.1.124.1.1.19",
814
+ "status" : "current",
815
+ "syntax" : {
816
+ "type" : { "module" :"SNMPv2-TC", "name" : "StorageType"},
817
+ },
818
+ "access" : "readwrite",
819
+ "description" :
820
+ """This object defines whether this policy and any associated
821
+ entries in the pmPolicyCodeTable are kept in volatile storage
822
+ and lost upon reboot or if this row is backed up by
823
+ non-volatile or permanent storage.
824
+
825
+
826
+
827
+
828
+ If the value of this object is 'permanent', the values for
829
+ the associated pmPolicyAdminStatus object must remain
830
+ writable.""",
831
+ }, # column
832
+ "pmPolicyRowStatus" : {
833
+ "nodetype" : "column",
834
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
835
+ "oid" : "1.3.6.1.2.1.124.1.1.20",
836
+ "status" : "current",
837
+ "syntax" : {
838
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
839
+ },
840
+ "access" : "readwrite",
841
+ "description" :
842
+ """The row status of this pmPolicyEntry.
843
+
844
+ The status may not be set to active if any of the related
845
+ entries in the pmPolicyCode table do not have a status of
846
+ active or if any of the objects in this row are not set to
847
+ valid values. Only the following objects may be modified
848
+ while in the active state:
849
+ pmPolicyParameters
850
+ pmPolicyConditionMaxLatency
851
+ pmPolicyActionMaxLatency
852
+ pmPolicyDebugging
853
+ pmPolicyAdminStatus
854
+
855
+ If this row is deleted, any associated entries in the
856
+ pmPolicyCodeTable will be deleted as well.""",
857
+ }, # column
858
+ "pmPolicyCodeTable" : {
859
+ "nodetype" : "table",
860
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
861
+ "oid" : "1.3.6.1.2.1.124.2",
862
+ "status" : "current",
863
+ "description" :
864
+ """The pmPolicyCodeTable stores the code for policy conditions and
865
+ actions.
866
+
867
+ An example of the relationships between the code table and the
868
+ policy table follows:
869
+
870
+ pmPolicyTable
871
+ AdminGroup Index ConditionScriptIndex ActionScriptIndex
872
+ A '' 1 1 2
873
+ B 'oper' 1 1 2
874
+ C 'oper' 2 3 4
875
+
876
+ pmPolicyCodeTable
877
+ AdminGroup ScriptIndex Segment Note
878
+
879
+
880
+
881
+ '' 1 1 Filter for policy A
882
+ '' 2 1 Action for policy A
883
+ 'oper' 1 1 Filter for policy B
884
+ 'oper' 2 1 Action 1/2 for policy B
885
+ 'oper' 2 2 Action 2/2 for policy B
886
+ 'oper' 3 1 Filter for policy C
887
+ 'oper' 4 1 Action for policy C
888
+
889
+ In this example, there are 3 policies: 1 in the '' adminGroup,
890
+ and 2 in the 'oper' adminGroup. Policy A has been assigned
891
+ script indexes 1 and 2 (these script indexes are assigned out of
892
+ a separate pool per adminGroup), with 1 code segment each for
893
+ the filter and the action. Policy B has been assigned script
894
+ indexes 1 and 2 (out of the pool for the 'oper' adminGroup).
895
+ While the filter has 1 segment, the action is longer and is
896
+ loaded into 2 segments. Finally, Policy C has been assigned
897
+ script indexes 3 and 4, with 1 code segment each for the filter
898
+ and the action.""",
899
+ }, # table
900
+ "pmPolicyCodeEntry" : {
901
+ "nodetype" : "row",
902
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
903
+ "oid" : "1.3.6.1.2.1.124.2.1",
904
+ "create" : "true",
905
+ "status" : "current",
906
+ "linkage" : [
907
+ "pmPolicyAdminGroup",
908
+ "pmPolicyCodeScriptIndex",
909
+ "pmPolicyCodeSegment",
910
+ ],
911
+ "description" :
912
+ """An entry in the policy code table representing one code
913
+ segment. Entries that share a common AdminGroup/ScriptIndex
914
+ pair make up a single script. Valid values of ScriptIndex are
915
+ retrieved from pmPolicyConditionScriptIndex and
916
+ pmPolicyActionScriptIndex after a pmPolicyEntry is
917
+ created. Segments of code can then be written to this table
918
+ with the learned ScriptIndex values.
919
+
920
+ The StorageType of this entry is determined by the value of
921
+ the associated pmPolicyStorageType.
922
+
923
+ The pmPolicyAdminGroup element of the index represents the
924
+ administrative group of the policy of which this code entry is
925
+ a part.""",
926
+ }, # row
927
+ "pmPolicyCodeScriptIndex" : {
928
+ "nodetype" : "column",
929
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
930
+ "oid" : "1.3.6.1.2.1.124.2.1.1",
931
+ "status" : "current",
932
+ "syntax" : {
933
+ "type" : {
934
+ "basetype" : "Unsigned32",
935
+ "ranges" : [
936
+ {
937
+ "min" : "1",
938
+ "max" : "4294967295"
939
+ },
940
+ ],
941
+ "range" : {
942
+ "min" : "1",
943
+ "max" : "4294967295"
944
+ },
945
+ },
946
+ },
947
+ "access" : "noaccess",
948
+ "description" :
949
+ """A unique index for each policy condition or action. The code
950
+ for each such condition or action may be composed of multiple
951
+ entries in this table if the code cannot fit in one entry.
952
+ Values of pmPolicyCodeScriptIndex may not be used unless
953
+ they have previously been assigned in the
954
+ pmPolicyConditionScriptIndex or pmPolicyActionScriptIndex
955
+ objects.""",
956
+ }, # column
957
+ "pmPolicyCodeSegment" : {
958
+ "nodetype" : "column",
959
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
960
+ "oid" : "1.3.6.1.2.1.124.2.1.2",
961
+ "status" : "current",
962
+ "syntax" : {
963
+ "type" : {
964
+ "basetype" : "Unsigned32",
965
+ "ranges" : [
966
+ {
967
+ "min" : "1",
968
+ "max" : "4294967295"
969
+ },
970
+ ],
971
+ "range" : {
972
+ "min" : "1",
973
+ "max" : "4294967295"
974
+ },
975
+ },
976
+ },
977
+ "access" : "noaccess",
978
+ "description" :
979
+ """A unique index for each segment of a policy condition or
980
+ action.
981
+
982
+ When a policy condition or action spans multiple entries in
983
+ this table, the code of that policy starts from the
984
+ lowest-numbered segment and continues with increasing segment
985
+ values until it ends with the highest-numbered segment.""",
986
+ }, # column
987
+ "pmPolicyCodeText" : {
988
+ "nodetype" : "column",
989
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
990
+ "oid" : "1.3.6.1.2.1.124.2.1.3",
991
+ "status" : "current",
992
+ "syntax" : {
993
+ "type" : {
994
+ "basetype" : "OctetString",
995
+ "parent module" : {
996
+ "name" : "POLICY-BASED-MANAGEMENT-MIB",
997
+ "type" : "PmUTF8String",
998
+ },
999
+ "ranges" : [
1000
+ {
1001
+ "min" : "1",
1002
+ "max" : "1024"
1003
+ },
1004
+ ],
1005
+ "range" : {
1006
+ "min" : "1",
1007
+ "max" : "1024"
1008
+ },
1009
+ },
1010
+ },
1011
+ "access" : "readwrite",
1012
+ "description" :
1013
+ """A segment of policy code (condition or action). Lengthy
1014
+ Policy conditions or actions may be stored in multiple
1015
+ segments in this table that share the same value of
1016
+ pmPolicyCodeScriptIndex. When multiple segments are used, it
1017
+ is recommended that each segment be as large as is practical.
1018
+
1019
+ Entries in this table are associated with policies by values
1020
+ of the pmPolicyConditionScriptIndex and
1021
+ pmPolicyActionScriptIndex objects. If the status of the
1022
+ related policy is active, then this object may not be
1023
+ modified.""",
1024
+ }, # column
1025
+ "pmPolicyCodeStatus" : {
1026
+ "nodetype" : "column",
1027
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1028
+ "oid" : "1.3.6.1.2.1.124.2.1.4",
1029
+ "status" : "current",
1030
+ "syntax" : {
1031
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
1032
+ },
1033
+ "access" : "readwrite",
1034
+ "description" :
1035
+ """The status of this code entry.
1036
+
1037
+ Entries in this table are associated with policies by values
1038
+ of the pmPolicyConditionScriptIndex and
1039
+ pmPolicyActionScriptIndex objects. If the status of the
1040
+ related policy is active, then this object can not be
1041
+ modified (i.e., deleted or set to notInService), nor may new
1042
+ entries be created.
1043
+
1044
+ If the status of this object is active, no objects in this
1045
+ row may be modified.""",
1046
+ }, # column
1047
+ "pmElementTypeRegTable" : {
1048
+ "nodetype" : "table",
1049
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1050
+ "oid" : "1.3.6.1.2.1.124.3",
1051
+ "status" : "current",
1052
+ "description" :
1053
+ """A registration table for element types managed by this
1054
+ system.
1055
+
1056
+ The Element Type Registration table allows the manager to
1057
+ learn what element types are being managed by the system and
1058
+ to register new types, if necessary. An element type is
1059
+ registered by providing the OID of an SNMP object (i.e.,
1060
+ without the instance). Each SNMP instance that exists under
1061
+ that object is a distinct element. The index of the element is
1062
+ the index part of the discovered OID. This index will be
1063
+ supplied to policy conditions and actions so that this code
1064
+ can inspect and configure the element.
1065
+
1066
+ For example, this table might contain the following entries.
1067
+ The first three are agent-installed, and the 4th was
1068
+ downloaded by a management station:
1069
+
1070
+ OIDPrefix MaxLatency Description StorageType
1071
+ ifEntry 100 mS interfaces - builtin readOnly
1072
+ 0.0 100 mS system element - builtin readOnly
1073
+ frCircuitEntry 100 mS FR Circuits - builtin readOnly
1074
+ hrSWRunEntry 60 sec Running Processes volatile
1075
+
1076
+
1077
+
1078
+
1079
+ Note that agents may automatically configure elements in this
1080
+ table for frequently used element types (interfaces, circuits,
1081
+ etc.). In particular, it may configure elements for whom
1082
+ discovery is optimized in one or both of the following ways:
1083
+
1084
+ 1. The agent may discover elements by scanning internal data
1085
+ structures as opposed to issuing local SNMP requests. It is
1086
+ possible to recreate the exact semantics described in this
1087
+ table even if local SNMP requests are not issued.
1088
+
1089
+ 2. The agent may receive asynchronous notification of new
1090
+ elements (for example, 'card inserted') and use that
1091
+ information to instantly create elements rather than
1092
+ through polling. A similar feature might be available for
1093
+ the deletion of elements.
1094
+
1095
+ Note that the disposition of agent-installed entries is
1096
+ described by the pmPolicyStorageType object.""",
1097
+ }, # table
1098
+ "pmElementTypeRegEntry" : {
1099
+ "nodetype" : "row",
1100
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1101
+ "oid" : "1.3.6.1.2.1.124.3.1",
1102
+ "create" : "true",
1103
+ "status" : "current",
1104
+ "linkage" : [
1105
+ "pmElementTypeRegOIDPrefix",
1106
+ ],
1107
+ "description" :
1108
+ """A registration of an element type.
1109
+
1110
+ Note that some values of this table's index may result in an
1111
+ instance name that exceeds a length of 128 sub-identifiers,
1112
+ which exceeds the maximum for the SNMP protocol.
1113
+ Implementations should take care to avoid such values.""",
1114
+ }, # row
1115
+ "pmElementTypeRegOIDPrefix" : {
1116
+ "nodetype" : "column",
1117
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1118
+ "oid" : "1.3.6.1.2.1.124.3.1.2",
1119
+ "status" : "current",
1120
+ "syntax" : {
1121
+ "type" : { "module" :"", "name" : "ObjectIdentifier"},
1122
+ },
1123
+ "access" : "noaccess",
1124
+ "description" :
1125
+ """This OBJECT IDENTIFIER value identifies a table in which all
1126
+
1127
+
1128
+
1129
+ elements of this type will be found. Every row in the
1130
+ referenced table will be treated as an element for the
1131
+ period of time that it remains in the table. The agent will
1132
+ then execute policy conditions and actions as appropriate on
1133
+ each of these elements.
1134
+
1135
+ This object identifier value is specified down to the 'entry'
1136
+ component (e.g., ifEntry) of the identifier.
1137
+
1138
+ The index of each discovered row will be passed to each
1139
+ invocation of the policy condition and policy action.
1140
+
1141
+ The actual mechanism by which instances are discovered is
1142
+ implementation dependent. Periodic walks of the table to
1143
+ discover the rows in the table is one such mechanism. This
1144
+ mechanism has the advantage that it can be performed by an
1145
+ agent with no knowledge of the names, syntax, or semantics
1146
+ of the MIB objects in the table. This mechanism also serves as
1147
+ the reference design. Other implementation-dependent
1148
+ mechanisms may be implemented that are more efficient (perhaps
1149
+ because they are hard coded) or that don't require polling.
1150
+ These mechanisms must discover the same elements as would the
1151
+ table-walking reference design.
1152
+
1153
+ This object can contain a OBJECT IDENTIFIER, '0.0'.
1154
+ '0.0' represents the single instance of the system
1155
+ itself and provides an execution context for policies to
1156
+ operate on the 'system element' and on MIB objects
1157
+ modeled as scalars. For example, '0.0' gives an execution
1158
+ context for policy-based selection of the operating system
1159
+ code version (likely modeled as a scalar MIB object). The
1160
+ element type '0.0' always exists; as a consequence, no actual
1161
+ discovery will take place, and the pmElementTypeRegMaxLatency
1162
+ object will have no effect for the '0.0' element
1163
+ type. However, if the '0.0' element type is not registered in
1164
+ the table, policies will not be executed on the '0.0' element.
1165
+
1166
+ When a policy is invoked on behalf of a '0.0' entry in this
1167
+ table, the element name will be '0.0', and there is no index
1168
+ of 'this element' (in other words, it has zero length).
1169
+
1170
+ As this object is used in the index for the
1171
+ pmElementTypeRegTable, users of this table should be careful
1172
+ not to create entries that would result in instance names with
1173
+ more than 128 sub-identifiers.""",
1174
+ }, # column
1175
+ "pmElementTypeRegMaxLatency" : {
1176
+ "nodetype" : "column",
1177
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1178
+ "oid" : "1.3.6.1.2.1.124.3.1.3",
1179
+ "status" : "current",
1180
+ "syntax" : {
1181
+ "type" : { "module" :"", "name" : "Unsigned32"},
1182
+ },
1183
+ "access" : "readwrite",
1184
+ "units" : "milliseconds",
1185
+ "description" :
1186
+ """The PM agent is responsible for discovering new elements of
1187
+ types that are registered. This object lets the manager
1188
+ control the maximum amount of time that may pass between the
1189
+ time an element is created and when it is discovered.
1190
+
1191
+ In other words, in any given interval of this duration, all
1192
+ new elements must be discovered. Note that how the policy
1193
+ agent schedules the checking of various elements within this
1194
+ interval is an implementation-dependent matter.""",
1195
+ }, # column
1196
+ "pmElementTypeRegDescription" : {
1197
+ "nodetype" : "column",
1198
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1199
+ "oid" : "1.3.6.1.2.1.124.3.1.4",
1200
+ "status" : "current",
1201
+ "syntax" : {
1202
+ "type" : {
1203
+ "basetype" : "OctetString",
1204
+ "parent module" : {
1205
+ "name" : "POLICY-BASED-MANAGEMENT-MIB",
1206
+ "type" : "PmUTF8String",
1207
+ },
1208
+ "ranges" : [
1209
+ {
1210
+ "min" : "0",
1211
+ "max" : "64"
1212
+ },
1213
+ ],
1214
+ "range" : {
1215
+ "min" : "0",
1216
+ "max" : "64"
1217
+ },
1218
+ },
1219
+ },
1220
+ "access" : "readwrite",
1221
+ "description" :
1222
+ """A descriptive label for this registered type.""",
1223
+ }, # column
1224
+ "pmElementTypeRegStorageType" : {
1225
+ "nodetype" : "column",
1226
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1227
+ "oid" : "1.3.6.1.2.1.124.3.1.5",
1228
+ "status" : "current",
1229
+ "syntax" : {
1230
+ "type" : { "module" :"SNMPv2-TC", "name" : "StorageType"},
1231
+ },
1232
+ "access" : "readwrite",
1233
+ "description" :
1234
+ """This object defines whether this row is kept
1235
+ in volatile storage and lost upon reboot or
1236
+ backed up by non-volatile or permanent storage.
1237
+
1238
+ If the value of this object is 'permanent', no values in the
1239
+ associated row have to be writable.""",
1240
+ }, # column
1241
+ "pmElementTypeRegRowStatus" : {
1242
+ "nodetype" : "column",
1243
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1244
+ "oid" : "1.3.6.1.2.1.124.3.1.6",
1245
+ "status" : "current",
1246
+ "syntax" : {
1247
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
1248
+ },
1249
+ "access" : "readwrite",
1250
+ "description" :
1251
+ """The status of this registration entry.
1252
+
1253
+ If the value of this object is active, no objects in this row
1254
+ may be modified.""",
1255
+ }, # column
1256
+ "pmRoleTable" : {
1257
+ "nodetype" : "table",
1258
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1259
+ "oid" : "1.3.6.1.2.1.124.4",
1260
+ "status" : "current",
1261
+ "description" :
1262
+ """The pmRoleTable is a read-create table that organizes role
1263
+ strings sorted by element. This table is used to create and
1264
+ modify role strings and their associations, as well as to allow
1265
+ a management station to learn about the existence of roles and
1266
+ their associations.
1267
+
1268
+ It is the responsibility of the agent to keep track of any
1269
+ re-indexing of the underlying SNMP elements and to continue to
1270
+ associate role strings with the element with which they were
1271
+ initially configured.
1272
+
1273
+ Policy MIB agents that have elements in multiple local SNMP
1274
+ contexts have to allow some roles to be assigned to elements
1275
+ in particular contexts. This is particularly true when some
1276
+ elements have the same names in different contexts and the
1277
+ context is required to disambiguate them. In those situations,
1278
+ a value for the pmRoleContextName may be provided. When a
1279
+ pmRoleContextName value is not provided, the assignment is to
1280
+ the element in the default context.
1281
+
1282
+ Policy MIB agents that discover elements on other systems and
1283
+ execute policies on their behalf need to have access to role
1284
+ information for these remote elements. In such situations,
1285
+ role assignments for other systems can be stored in this table
1286
+ by providing values for the pmRoleContextEngineID parameters.
1287
+
1288
+ For example:
1289
+ Example:
1290
+ element role context ctxEngineID #comment
1291
+ ifindex.1 gold local, default context
1292
+ ifindex.2 gold local, default context
1293
+ repeaterid.1 foo rptr1 local, rptr1 context
1294
+ repeaterid.1 bar rptr2 local, rptr2 context
1295
+ ifindex.1 gold '' A different system
1296
+ ifindex.1 gold '' B different system
1297
+
1298
+ The agent must store role string associations in non-volatile
1299
+ storage.""",
1300
+ }, # table
1301
+ "pmRoleEntry" : {
1302
+ "nodetype" : "row",
1303
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1304
+ "oid" : "1.3.6.1.2.1.124.4.1",
1305
+ "create" : "true",
1306
+ "status" : "current",
1307
+ "linkage" : [
1308
+ "pmRoleElement",
1309
+ "pmRoleContextName",
1310
+ "pmRoleContextEngineID",
1311
+ "pmRoleString",
1312
+ ],
1313
+ "description" :
1314
+ """A role string entry associates a role string with an
1315
+ individual element.
1316
+
1317
+ Note that some combinations of index values may result in an
1318
+ instance name that exceeds a length of 128 sub-identifiers,
1319
+ which exceeds the maximum for the SNMP
1320
+ protocol. Implementations should take care to avoid such
1321
+ combinations.""",
1322
+ }, # row
1323
+ "pmRoleElement" : {
1324
+ "nodetype" : "column",
1325
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1326
+ "oid" : "1.3.6.1.2.1.124.4.1.1",
1327
+ "status" : "current",
1328
+ "syntax" : {
1329
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowPointer"},
1330
+ },
1331
+ "access" : "noaccess",
1332
+ "description" :
1333
+ """The element with which this role string is associated.
1334
+
1335
+ For example, if the element is interface 3, then this object
1336
+ will contain the OID for 'ifIndex.3'.
1337
+
1338
+ If the agent assigns new indexes in the MIB table to
1339
+ represent the same underlying element (re-indexing), the
1340
+ agent will modify this value to contain the new index for the
1341
+ underlying element.
1342
+
1343
+ As this object is used in the index for the pmRoleTable,
1344
+ users of this table should be careful not to create entries
1345
+ that would result in instance names with more than 128
1346
+ sub-identifiers.""",
1347
+ }, # column
1348
+ "pmRoleContextName" : {
1349
+ "nodetype" : "column",
1350
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1351
+ "oid" : "1.3.6.1.2.1.124.4.1.2",
1352
+ "status" : "current",
1353
+ "syntax" : {
1354
+ "type" : {
1355
+ "basetype" : "OctetString",
1356
+ "parent module" : {
1357
+ "name" : "SNMP-FRAMEWORK-MIB",
1358
+ "type" : "SnmpAdminString",
1359
+ },
1360
+ "ranges" : [
1361
+ {
1362
+ "min" : "0",
1363
+ "max" : "32"
1364
+ },
1365
+ ],
1366
+ "range" : {
1367
+ "min" : "0",
1368
+ "max" : "32"
1369
+ },
1370
+ },
1371
+ },
1372
+ "access" : "noaccess",
1373
+ "description" :
1374
+ """If the associated element is not in the default SNMP context
1375
+ for the target system, this object is used to identify the
1376
+ context. If the element is in the default context, this object
1377
+ is equal to the empty string.""",
1378
+ }, # column
1379
+ "pmRoleContextEngineID" : {
1380
+ "nodetype" : "column",
1381
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1382
+ "oid" : "1.3.6.1.2.1.124.4.1.3",
1383
+ "status" : "current",
1384
+ "syntax" : {
1385
+ "type" : {
1386
+ "basetype" : "OctetString",
1387
+ "ranges" : [
1388
+ {
1389
+ "min" : "0",
1390
+ "max" : "0"
1391
+ },
1392
+ {
1393
+ "min" : "5",
1394
+ "max" : "32"
1395
+ },
1396
+ ],
1397
+ "range" : {
1398
+ "min" : "0",
1399
+ "max" : "32"
1400
+ },
1401
+ },
1402
+ },
1403
+ "access" : "noaccess",
1404
+ "description" :
1405
+ """If the associated element is on a remote system, this object
1406
+ is used to identify the remote system. This object contains
1407
+ the contextEngineID of the system for which this role string
1408
+ assignment is valid. If the element is on the local system
1409
+ this object will be the empty string.""",
1410
+ }, # column
1411
+ "pmRoleString" : {
1412
+ "nodetype" : "column",
1413
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1414
+ "oid" : "1.3.6.1.2.1.124.4.1.4",
1415
+ "status" : "current",
1416
+ "syntax" : {
1417
+ "type" : {
1418
+ "basetype" : "OctetString",
1419
+ "parent module" : {
1420
+ "name" : "POLICY-BASED-MANAGEMENT-MIB",
1421
+ "type" : "PmUTF8String",
1422
+ },
1423
+ "ranges" : [
1424
+ {
1425
+ "min" : "0",
1426
+ "max" : "64"
1427
+ },
1428
+ ],
1429
+ "range" : {
1430
+ "min" : "0",
1431
+ "max" : "64"
1432
+ },
1433
+ },
1434
+ },
1435
+ "access" : "noaccess",
1436
+ "description" :
1437
+ """The role string that is associated with an element through
1438
+ this table. All role strings must have been successfully
1439
+ transformed by Stringprep RFC 3454. Management stations
1440
+ must perform this translation and must only set this object
1441
+ to string values that have been transformed.
1442
+
1443
+ A role string is an administratively specified characteristic
1444
+ of a managed element (for example, an interface). It is a
1445
+ selector for policy rules, that determines the applicability of
1446
+ the rule to a particular managed element.""",
1447
+ }, # column
1448
+ "pmRoleStatus" : {
1449
+ "nodetype" : "column",
1450
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1451
+ "oid" : "1.3.6.1.2.1.124.4.1.5",
1452
+ "status" : "current",
1453
+ "syntax" : {
1454
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
1455
+ },
1456
+ "access" : "readwrite",
1457
+ "description" :
1458
+ """The status of this role string.
1459
+
1460
+
1461
+
1462
+
1463
+
1464
+ If the value of this object is active, no object in this row
1465
+ may be modified.""",
1466
+ }, # column
1467
+ "pmCapabilitiesTable" : {
1468
+ "nodetype" : "table",
1469
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1470
+ "oid" : "1.3.6.1.2.1.124.5",
1471
+ "status" : "current",
1472
+ "description" :
1473
+ """The pmCapabilitiesTable contains a description of
1474
+ the inherent capabilities of the system so that
1475
+ management stations can learn of an agent's capabilities and
1476
+ differentially install policies based on the capabilities.
1477
+
1478
+ Capabilities are expressed at the system level. There can be
1479
+ variation in how capabilities are realized from one vendor or
1480
+ model to the next. Management systems should consider these
1481
+ differences before selecting which policy to install in a
1482
+ system.""",
1483
+ }, # table
1484
+ "pmCapabilitiesEntry" : {
1485
+ "nodetype" : "row",
1486
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1487
+ "oid" : "1.3.6.1.2.1.124.5.1",
1488
+ "status" : "current",
1489
+ "linkage" : [
1490
+ "pmCapabilitiesType",
1491
+ ],
1492
+ "description" :
1493
+ """A capabilities entry holds an OID indicating support for a
1494
+ particular capability. Capabilities may include hardware and
1495
+ software functions and the implementation of MIB
1496
+ Modules. The semantics of the OID are defined in the
1497
+ description of pmCapabilitiesType.
1498
+
1499
+ Entries appear in this table if any element in the system has
1500
+ a specific capability. A capability should appear in this
1501
+ table only once, regardless of the number of elements in the
1502
+ system with that capability. An entry is removed from this
1503
+ table when the last element in the system that has the
1504
+ capability is removed. In some cases, capabilities are
1505
+ dynamic and exist only in software. This table should have an
1506
+ entry for the capability even if there are no current
1507
+ instances. Examples include systems with database or WEB
1508
+ services. While the system has the ability to create new
1509
+ databases or WEB services, the entry should exist. In these
1510
+ cases, the ability to create these services could come from
1511
+ other processes that are running in the system, even though
1512
+ there are no currently open databases or WEB servers running.
1513
+
1514
+
1515
+
1516
+ Capabilities may include the implementation of MIB Modules
1517
+ but need not be limited to those that represent MIB Modules
1518
+ with one or more configurable objects. It may also be
1519
+ valuable to include entries for capabilities that do not
1520
+ include configuration objects, as that information, in
1521
+ combination with other entries in this table, might be used
1522
+ by the management software to determine whether to
1523
+ install a policy.
1524
+
1525
+ Vendor software may also add entries in this table to express
1526
+ capabilities from their private branch.
1527
+
1528
+ Note that some values of this table's index may result in an
1529
+ instance name that exceeds a length of 128 sub-identifiers,
1530
+ which exceeds the maximum for the SNMP
1531
+ protocol. Implementations should take care to avoid such
1532
+ values.""",
1533
+ }, # row
1534
+ "pmCapabilitiesType" : {
1535
+ "nodetype" : "column",
1536
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1537
+ "oid" : "1.3.6.1.2.1.124.5.1.1",
1538
+ "status" : "current",
1539
+ "syntax" : {
1540
+ "type" : { "module" :"", "name" : "ObjectIdentifier"},
1541
+ },
1542
+ "access" : "readonly",
1543
+ "description" :
1544
+ """There are three types of OIDs that may be present in the
1545
+ pmCapabilitiesType object:
1546
+
1547
+ 1) The OID of a MODULE-COMPLIANCE macro that represents the
1548
+ highest level of compliance realized by the agent for that
1549
+ MIB Module. For example, an agent that implements the OSPF
1550
+ MIB Module at the highest level of compliance would have the
1551
+ value of '1.3.6.1.2.1.14.15.2' in the pmCapabilitiesType
1552
+ object. For software that realizes standard MIB
1553
+ Modules that do not have compliance statements, the base OID
1554
+ of the MIB Module should be used instead. If the OSPF MIB
1555
+ Module had not been created with a compliance statement, then
1556
+ the correct value of the pmCapabilitiesType would be
1557
+ '1.3.6.1.2.1.14'. In the cases where multiple compliance
1558
+ statements in a MIB Module are supported by the agent, and
1559
+ where one compliance statement does not by definition include
1560
+ the other, each of the compliance OIDs would have entries in
1561
+ this table.
1562
+
1563
+
1564
+
1565
+
1566
+ MIB Documents can contain more than one MIB Module. In the
1567
+ case of OSPF, there is a second MIB Module
1568
+ that describes notifications for the OSPF Version 2 Protocol.
1569
+ If the agent also realizes these functions, an entry will
1570
+ also exist for those capabilities in this table.
1571
+
1572
+ 2) Vendors should install OIDs in this table that represent
1573
+ vendor-specific capabilities. These capabilities can be
1574
+ expressed just as those described above for MIB Modules on
1575
+ the standards track. In addition, vendors may install any
1576
+ OID they desire from their registered branch. The OIDs may be
1577
+ at any level of granularity, from the root of their entire
1578
+ branch to an instance of a single OID. There is no
1579
+ restriction on the number of registrations they may make,
1580
+ though care should be taken to avoid unnecessary entries.
1581
+
1582
+ 3) OIDs that represent one capability or a collection of
1583
+ capabilities that could be any collection of MIB Objects or
1584
+ hardware or software functions may be created in working
1585
+ groups and registered in a MIB Module. Other entities (e.g.,
1586
+ vendors) may also make registrations. Software will register
1587
+ these standard capability OIDs, as well as vendor specific
1588
+ OIDs.
1589
+
1590
+ If the OID for a known capability is not present in the
1591
+ table, then it should be assumed that the capability is not
1592
+ implemented.
1593
+
1594
+ As this object is used in the index for the
1595
+ pmCapabilitiesTable, users of this table should be careful
1596
+ not to create entries that would result in instance names
1597
+ with more than 128 sub-identifiers.""",
1598
+ }, # column
1599
+ "pmCapabilitiesOverrideTable" : {
1600
+ "nodetype" : "table",
1601
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1602
+ "oid" : "1.3.6.1.2.1.124.6",
1603
+ "status" : "current",
1604
+ "description" :
1605
+ """The pmCapabilitiesOverrideTable allows management stations
1606
+ to override pmCapabilitiesTable entries that have been
1607
+ registered by the agent. This facility can be used to avoid
1608
+ situations in which managers in the network send policies to
1609
+ a system that has advertised a capability in the
1610
+ pmCapabilitiesTable but that should not be installed on this
1611
+ particular system. One example could be newly deployed
1612
+
1613
+
1614
+
1615
+ equipment that is still in a trial state in a trial state or
1616
+ resources reserved for some other administrative reason.
1617
+ This table can also be used to override entries in the
1618
+ pmCapabilitiesTable through the use of the
1619
+ pmCapabilitiesOverrideState object. Capabilities can also be
1620
+ declared available in this table that were not registered in
1621
+ the pmCapabilitiesTable. A management application can make
1622
+ an entry in this table for any valid OID and declare the
1623
+ capability available by setting the
1624
+ pmCapabilitiesOverrideState for that row to valid(1).""",
1625
+ }, # table
1626
+ "pmCapabilitiesOverrideEntry" : {
1627
+ "nodetype" : "row",
1628
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1629
+ "oid" : "1.3.6.1.2.1.124.6.1",
1630
+ "create" : "true",
1631
+ "status" : "current",
1632
+ "linkage" : [
1633
+ "pmCapabilitiesOverrideType",
1634
+ ],
1635
+ "description" :
1636
+ """An entry in this table indicates whether a particular
1637
+ capability is valid or invalid.
1638
+
1639
+ Note that some values of this table's index may result in an
1640
+ instance name that exceeds a length of 128 sub-identifiers,
1641
+ which exceeds the maximum for the SNMP
1642
+ protocol. Implementations should take care to avoid such
1643
+ values.""",
1644
+ }, # row
1645
+ "pmCapabilitiesOverrideType" : {
1646
+ "nodetype" : "column",
1647
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1648
+ "oid" : "1.3.6.1.2.1.124.6.1.1",
1649
+ "status" : "current",
1650
+ "syntax" : {
1651
+ "type" : { "module" :"", "name" : "ObjectIdentifier"},
1652
+ },
1653
+ "access" : "noaccess",
1654
+ "description" :
1655
+ """This is the OID of the capability that is declared valid or
1656
+ invalid by the pmCapabilitiesOverrideState value for this
1657
+ row. Any valid OID, as described in the pmCapabilitiesTable,
1658
+ is permitted in the pmCapabilitiesOverrideType object. This
1659
+ means that capabilities can be expressed at any level, from a
1660
+ specific instance of an object to a table or entire module.
1661
+ There are no restrictions on whether these objects are from
1662
+ standards track MIB documents or in the private branch of the
1663
+ MIB.
1664
+
1665
+
1666
+
1667
+ If an entry exists in this table for which there is a
1668
+ corresponding entry in the pmCapabilitiesTable, then this entry
1669
+ shall have precedence over the entry in the
1670
+ pmCapabilitiesTable. All entries in this table must be
1671
+ preserved across reboots.
1672
+
1673
+ As this object is used in the index for the
1674
+ pmCapabilitiesOverrideTable, users of this table should be
1675
+ careful not to create entries that would result in instance
1676
+ names with more than 128 sub-identifiers.""",
1677
+ }, # column
1678
+ "pmCapabilitiesOverrideState" : {
1679
+ "nodetype" : "column",
1680
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1681
+ "oid" : "1.3.6.1.2.1.124.6.1.2",
1682
+ "status" : "current",
1683
+ "syntax" : {
1684
+ "type" : {
1685
+ "basetype" : "Enumeration",
1686
+ "invalid" : {
1687
+ "nodetype" : "namednumber",
1688
+ "number" : "1"
1689
+ },
1690
+ "valid" : {
1691
+ "nodetype" : "namednumber",
1692
+ "number" : "2"
1693
+ },
1694
+ },
1695
+ },
1696
+ "access" : "readwrite",
1697
+ "description" :
1698
+ """A pmCapabilitiesOverrideState of invalid indicates that
1699
+ management software should not send policies to this system
1700
+ for the capability identified in the
1701
+ pmCapabilitiesOverrideType for this row of the table. This
1702
+ behavior is the same whether the capability represented by
1703
+ the pmCapabilitiesOverrideType exists only in this table
1704
+ (that is, it was installed by an external management
1705
+ application) or exists in this table as well as the
1706
+ pmCapabilitiesTable. This would be the case when a manager
1707
+ wanted to disable a capability that the native management
1708
+ system found and registered in the pmCapabilitiesTable.
1709
+
1710
+ An entry in this table that has a pmCapabilitiesOverrideState
1711
+ of valid should be treated as though it appeared in the
1712
+ pmCapabilitiesTable. If the entry also exists in the
1713
+ pmCapabilitiesTable in the pmCapabilitiesType object, and if
1714
+ the value of this object is valid, then the system shall
1715
+ operate as though this entry did not exist and policy
1716
+ installations and executions will continue in a normal
1717
+ fashion.""",
1718
+ }, # column
1719
+ "pmCapabilitiesOverrideRowStatus" : {
1720
+ "nodetype" : "column",
1721
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1722
+ "oid" : "1.3.6.1.2.1.124.6.1.3",
1723
+ "status" : "current",
1724
+ "syntax" : {
1725
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
1726
+ },
1727
+ "access" : "readwrite",
1728
+ "description" :
1729
+ """The row status of this pmCapabilitiesOverrideEntry.
1730
+
1731
+
1732
+
1733
+ If the value of this object is active, no object in this row
1734
+ may be modified.""",
1735
+ }, # column
1736
+ "pmSchedLocalTime" : {
1737
+ "nodetype" : "scalar",
1738
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1739
+ "oid" : "1.3.6.1.2.1.124.7",
1740
+ "status" : "current",
1741
+ "syntax" : {
1742
+ "type" : {
1743
+ "basetype" : "OctetString",
1744
+ "parent module" : {
1745
+ "name" : "SNMPv2-TC",
1746
+ "type" : "DateAndTime",
1747
+ },
1748
+ "ranges" : [
1749
+ {
1750
+ "min" : "11",
1751
+ "max" : "11"
1752
+ },
1753
+ ],
1754
+ "range" : {
1755
+ "min" : "11",
1756
+ "max" : "11"
1757
+ },
1758
+ },
1759
+ },
1760
+ "access" : "readonly",
1761
+ "description" :
1762
+ """The local time used by the scheduler. Schedules that
1763
+ refer to calendar time will use the local time indicated
1764
+ by this object. An implementation MUST return all 11 bytes
1765
+ of the DateAndTime textual-convention so that a manager
1766
+ may retrieve the offset from GMT time.""",
1767
+ }, # scalar
1768
+ "pmSchedTable" : {
1769
+ "nodetype" : "table",
1770
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1771
+ "oid" : "1.3.6.1.2.1.124.8",
1772
+ "status" : "current",
1773
+ "description" :
1774
+ """This table defines schedules for policies.""",
1775
+ }, # table
1776
+ "pmSchedEntry" : {
1777
+ "nodetype" : "row",
1778
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1779
+ "oid" : "1.3.6.1.2.1.124.8.1",
1780
+ "create" : "true",
1781
+ "status" : "current",
1782
+ "linkage" : [
1783
+ "pmSchedIndex",
1784
+ ],
1785
+ "description" :
1786
+ """An entry describing a particular schedule.
1787
+
1788
+ Unless noted otherwise, writable objects of this row can be
1789
+ modified independently of the current value of pmSchedRowStatus,
1790
+ pmSchedAdminStatus and pmSchedOperStatus. In particular, it
1791
+ is legal to modify pmSchedWeekDay, pmSchedMonth, and
1792
+ pmSchedDay when pmSchedRowStatus is active.""",
1793
+ }, # row
1794
+ "pmSchedIndex" : {
1795
+ "nodetype" : "column",
1796
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1797
+ "oid" : "1.3.6.1.2.1.124.8.1.1",
1798
+ "status" : "current",
1799
+ "syntax" : {
1800
+ "type" : {
1801
+ "basetype" : "Unsigned32",
1802
+ "ranges" : [
1803
+ {
1804
+ "min" : "1",
1805
+ "max" : "4294967295"
1806
+ },
1807
+ ],
1808
+ "range" : {
1809
+ "min" : "1",
1810
+ "max" : "4294967295"
1811
+ },
1812
+ },
1813
+ },
1814
+ "access" : "noaccess",
1815
+ "description" :
1816
+ """The locally unique, administratively assigned index for this
1817
+ scheduling entry.""",
1818
+ }, # column
1819
+ "pmSchedGroupIndex" : {
1820
+ "nodetype" : "column",
1821
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1822
+ "oid" : "1.3.6.1.2.1.124.8.1.2",
1823
+ "status" : "current",
1824
+ "syntax" : {
1825
+ "type" : {
1826
+ "basetype" : "Unsigned32",
1827
+ "ranges" : [
1828
+ {
1829
+ "min" : "1",
1830
+ "max" : "4294967295"
1831
+ },
1832
+ ],
1833
+ "range" : {
1834
+ "min" : "1",
1835
+ "max" : "4294967295"
1836
+ },
1837
+ },
1838
+ },
1839
+ "access" : "readwrite",
1840
+ "description" :
1841
+ """The locally unique, administratively assigned index for the
1842
+ schedule group this scheduling entry belongs to.
1843
+
1844
+ To assign multiple schedule entries to the same group, the
1845
+ pmSchedGroupIndex of each entry in the group will be set to
1846
+ the same value. This pmSchedGroupIndex value must be equal to
1847
+ the pmSchedIndex of one of the entries in the group. If the
1848
+ entry whose pmSchedIndex equals the pmSchedGroupIndex
1849
+ for the group is deleted, the agent will assign a new
1850
+ pmSchedGroupIndex to all remaining members of the group.
1851
+
1852
+ If an entry is not a member of a group, its pmSchedGroupIndex
1853
+ must be assigned to the value of its pmSchedIndex.
1854
+
1855
+ Policies that are controlled by a group of schedule entries
1856
+ are active when any schedule in the group is active.""",
1857
+ }, # column
1858
+ "pmSchedDescr" : {
1859
+ "nodetype" : "column",
1860
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1861
+ "oid" : "1.3.6.1.2.1.124.8.1.3",
1862
+ "status" : "current",
1863
+ "syntax" : {
1864
+ "type" : { "module" :"POLICY-BASED-MANAGEMENT-MIB", "name" : "PmUTF8String"},
1865
+ },
1866
+ "access" : "readwrite",
1867
+ "default" : "",
1868
+ "description" :
1869
+ """The human-readable description of the purpose of this
1870
+ scheduling entry.""",
1871
+ }, # column
1872
+ "pmSchedTimePeriod" : {
1873
+ "nodetype" : "column",
1874
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1875
+ "oid" : "1.3.6.1.2.1.124.8.1.4",
1876
+ "status" : "current",
1877
+ "syntax" : {
1878
+ "type" : {
1879
+ "basetype" : "OctetString",
1880
+ "parent module" : {
1881
+ "name" : "POLICY-BASED-MANAGEMENT-MIB",
1882
+ "type" : "PmUTF8String",
1883
+ },
1884
+ "ranges" : [
1885
+ {
1886
+ "min" : "0",
1887
+ "max" : "31"
1888
+ },
1889
+ ],
1890
+ "range" : {
1891
+ "min" : "0",
1892
+ "max" : "31"
1893
+ },
1894
+ },
1895
+ },
1896
+ "access" : "readwrite",
1897
+ "description" :
1898
+ """The overall range of calendar dates and times over which this
1899
+ schedule is active. It is stored in a slightly extended version
1900
+ of the format for a 'period-explicit' defined in RFC 2445.
1901
+ This format is expressed as a string representing the
1902
+ starting date and time, in which the character 'T' indicates
1903
+ the beginning of the time portion, followed by the solidus
1904
+ character, '/', followed by a similar string representing an
1905
+ end date and time. The start of the period MUST be before the
1906
+ end of the period. Date-Time values are expressed as
1907
+ substrings of the form 'yyyymmddThhmmss'. For example:
1908
+
1909
+ 20000101T080000/20000131T130000
1910
+
1911
+ January 1, 2000, 0800 through January 31, 2000, 1PM
1912
+
1913
+ The 'Date with UTC time' format defined in RFC 2445 in which
1914
+ the Date-Time string ends with the character 'Z' is not
1915
+ allowed.
1916
+
1917
+ This 'period-explicit' format is also extended to allow two
1918
+ special cases in which one of the Date-Time strings is
1919
+ replaced with a special string defined in RFC 2445:
1920
+
1921
+ 1. If the first Date-Time value is replaced with the string
1922
+ 'THISANDPRIOR', then the value indicates that the schedule
1923
+ is active at any time prior to the Date-Time that appears
1924
+ after the '/'.
1925
+
1926
+ 2. If the second Date-Time is replaced with the string
1927
+ 'THISANDFUTURE', then the value indicates that the schedule
1928
+ is active at any time after the Date-Time that appears
1929
+ before the '/'.
1930
+
1931
+
1932
+
1933
+
1934
+ Note that although RFC 2445 defines these two strings, they are
1935
+ not specified for use in the 'period-explicit' format. The use
1936
+ of these strings represents an extension to the
1937
+ 'period-explicit' format.""",
1938
+ }, # column
1939
+ "pmSchedMonth" : {
1940
+ "nodetype" : "column",
1941
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
1942
+ "oid" : "1.3.6.1.2.1.124.8.1.5",
1943
+ "status" : "current",
1944
+ "syntax" : {
1945
+ "type" : {
1946
+ "basetype" : "Bits",
1947
+ "january" : {
1948
+ "nodetype" : "namednumber",
1949
+ "number" : "0"
1950
+ },
1951
+ "february" : {
1952
+ "nodetype" : "namednumber",
1953
+ "number" : "1"
1954
+ },
1955
+ "march" : {
1956
+ "nodetype" : "namednumber",
1957
+ "number" : "2"
1958
+ },
1959
+ "april" : {
1960
+ "nodetype" : "namednumber",
1961
+ "number" : "3"
1962
+ },
1963
+ "may" : {
1964
+ "nodetype" : "namednumber",
1965
+ "number" : "4"
1966
+ },
1967
+ "june" : {
1968
+ "nodetype" : "namednumber",
1969
+ "number" : "5"
1970
+ },
1971
+ "july" : {
1972
+ "nodetype" : "namednumber",
1973
+ "number" : "6"
1974
+ },
1975
+ "august" : {
1976
+ "nodetype" : "namednumber",
1977
+ "number" : "7"
1978
+ },
1979
+ "september" : {
1980
+ "nodetype" : "namednumber",
1981
+ "number" : "8"
1982
+ },
1983
+ "october" : {
1984
+ "nodetype" : "namednumber",
1985
+ "number" : "9"
1986
+ },
1987
+ "november" : {
1988
+ "nodetype" : "namednumber",
1989
+ "number" : "10"
1990
+ },
1991
+ "december" : {
1992
+ "nodetype" : "namednumber",
1993
+ "number" : "11"
1994
+ },
1995
+ },
1996
+ },
1997
+ "access" : "readwrite",
1998
+ "default" : "(january, february, march, april, may, june, july, august, september, october, november, december)",
1999
+ "description" :
2000
+ """Within the overall time period specified in the
2001
+ pmSchedTimePeriod object, the value of this object specifies
2002
+ the specific months within that time period when the schedule
2003
+ is active. Setting all bits will cause the schedule to act
2004
+ independently of the month.""",
2005
+ }, # column
2006
+ "pmSchedDay" : {
2007
+ "nodetype" : "column",
2008
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2009
+ "oid" : "1.3.6.1.2.1.124.8.1.6",
2010
+ "status" : "current",
2011
+ "syntax" : {
2012
+ "type" : {
2013
+ "basetype" : "Bits",
2014
+ "d1" : {
2015
+ "nodetype" : "namednumber",
2016
+ "number" : "0"
2017
+ },
2018
+ "d2" : {
2019
+ "nodetype" : "namednumber",
2020
+ "number" : "1"
2021
+ },
2022
+ "d3" : {
2023
+ "nodetype" : "namednumber",
2024
+ "number" : "2"
2025
+ },
2026
+ "d4" : {
2027
+ "nodetype" : "namednumber",
2028
+ "number" : "3"
2029
+ },
2030
+ "d5" : {
2031
+ "nodetype" : "namednumber",
2032
+ "number" : "4"
2033
+ },
2034
+ "d6" : {
2035
+ "nodetype" : "namednumber",
2036
+ "number" : "5"
2037
+ },
2038
+ "d7" : {
2039
+ "nodetype" : "namednumber",
2040
+ "number" : "6"
2041
+ },
2042
+ "d8" : {
2043
+ "nodetype" : "namednumber",
2044
+ "number" : "7"
2045
+ },
2046
+ "d9" : {
2047
+ "nodetype" : "namednumber",
2048
+ "number" : "8"
2049
+ },
2050
+ "d10" : {
2051
+ "nodetype" : "namednumber",
2052
+ "number" : "9"
2053
+ },
2054
+ "d11" : {
2055
+ "nodetype" : "namednumber",
2056
+ "number" : "10"
2057
+ },
2058
+ "d12" : {
2059
+ "nodetype" : "namednumber",
2060
+ "number" : "11"
2061
+ },
2062
+ "d13" : {
2063
+ "nodetype" : "namednumber",
2064
+ "number" : "12"
2065
+ },
2066
+ "d14" : {
2067
+ "nodetype" : "namednumber",
2068
+ "number" : "13"
2069
+ },
2070
+ "d15" : {
2071
+ "nodetype" : "namednumber",
2072
+ "number" : "14"
2073
+ },
2074
+ "d16" : {
2075
+ "nodetype" : "namednumber",
2076
+ "number" : "15"
2077
+ },
2078
+ "d17" : {
2079
+ "nodetype" : "namednumber",
2080
+ "number" : "16"
2081
+ },
2082
+ "d18" : {
2083
+ "nodetype" : "namednumber",
2084
+ "number" : "17"
2085
+ },
2086
+ "d19" : {
2087
+ "nodetype" : "namednumber",
2088
+ "number" : "18"
2089
+ },
2090
+ "d20" : {
2091
+ "nodetype" : "namednumber",
2092
+ "number" : "19"
2093
+ },
2094
+ "d21" : {
2095
+ "nodetype" : "namednumber",
2096
+ "number" : "20"
2097
+ },
2098
+ "d22" : {
2099
+ "nodetype" : "namednumber",
2100
+ "number" : "21"
2101
+ },
2102
+ "d23" : {
2103
+ "nodetype" : "namednumber",
2104
+ "number" : "22"
2105
+ },
2106
+ "d24" : {
2107
+ "nodetype" : "namednumber",
2108
+ "number" : "23"
2109
+ },
2110
+ "d25" : {
2111
+ "nodetype" : "namednumber",
2112
+ "number" : "24"
2113
+ },
2114
+ "d26" : {
2115
+ "nodetype" : "namednumber",
2116
+ "number" : "25"
2117
+ },
2118
+ "d27" : {
2119
+ "nodetype" : "namednumber",
2120
+ "number" : "26"
2121
+ },
2122
+ "d28" : {
2123
+ "nodetype" : "namednumber",
2124
+ "number" : "27"
2125
+ },
2126
+ "d29" : {
2127
+ "nodetype" : "namednumber",
2128
+ "number" : "28"
2129
+ },
2130
+ "d30" : {
2131
+ "nodetype" : "namednumber",
2132
+ "number" : "29"
2133
+ },
2134
+ "d31" : {
2135
+ "nodetype" : "namednumber",
2136
+ "number" : "30"
2137
+ },
2138
+ "r1" : {
2139
+ "nodetype" : "namednumber",
2140
+ "number" : "31"
2141
+ },
2142
+ "r2" : {
2143
+ "nodetype" : "namednumber",
2144
+ "number" : "32"
2145
+ },
2146
+ "r3" : {
2147
+ "nodetype" : "namednumber",
2148
+ "number" : "33"
2149
+ },
2150
+ "r4" : {
2151
+ "nodetype" : "namednumber",
2152
+ "number" : "34"
2153
+ },
2154
+ "r5" : {
2155
+ "nodetype" : "namednumber",
2156
+ "number" : "35"
2157
+ },
2158
+ "r6" : {
2159
+ "nodetype" : "namednumber",
2160
+ "number" : "36"
2161
+ },
2162
+ "r7" : {
2163
+ "nodetype" : "namednumber",
2164
+ "number" : "37"
2165
+ },
2166
+ "r8" : {
2167
+ "nodetype" : "namednumber",
2168
+ "number" : "38"
2169
+ },
2170
+ "r9" : {
2171
+ "nodetype" : "namednumber",
2172
+ "number" : "39"
2173
+ },
2174
+ "r10" : {
2175
+ "nodetype" : "namednumber",
2176
+ "number" : "40"
2177
+ },
2178
+ "r11" : {
2179
+ "nodetype" : "namednumber",
2180
+ "number" : "41"
2181
+ },
2182
+ "r12" : {
2183
+ "nodetype" : "namednumber",
2184
+ "number" : "42"
2185
+ },
2186
+ "r13" : {
2187
+ "nodetype" : "namednumber",
2188
+ "number" : "43"
2189
+ },
2190
+ "r14" : {
2191
+ "nodetype" : "namednumber",
2192
+ "number" : "44"
2193
+ },
2194
+ "r15" : {
2195
+ "nodetype" : "namednumber",
2196
+ "number" : "45"
2197
+ },
2198
+ "r16" : {
2199
+ "nodetype" : "namednumber",
2200
+ "number" : "46"
2201
+ },
2202
+ "r17" : {
2203
+ "nodetype" : "namednumber",
2204
+ "number" : "47"
2205
+ },
2206
+ "r18" : {
2207
+ "nodetype" : "namednumber",
2208
+ "number" : "48"
2209
+ },
2210
+ "r19" : {
2211
+ "nodetype" : "namednumber",
2212
+ "number" : "49"
2213
+ },
2214
+ "r20" : {
2215
+ "nodetype" : "namednumber",
2216
+ "number" : "50"
2217
+ },
2218
+ "r21" : {
2219
+ "nodetype" : "namednumber",
2220
+ "number" : "51"
2221
+ },
2222
+ "r22" : {
2223
+ "nodetype" : "namednumber",
2224
+ "number" : "52"
2225
+ },
2226
+ "r23" : {
2227
+ "nodetype" : "namednumber",
2228
+ "number" : "53"
2229
+ },
2230
+ "r24" : {
2231
+ "nodetype" : "namednumber",
2232
+ "number" : "54"
2233
+ },
2234
+ "r25" : {
2235
+ "nodetype" : "namednumber",
2236
+ "number" : "55"
2237
+ },
2238
+ "r26" : {
2239
+ "nodetype" : "namednumber",
2240
+ "number" : "56"
2241
+ },
2242
+ "r27" : {
2243
+ "nodetype" : "namednumber",
2244
+ "number" : "57"
2245
+ },
2246
+ "r28" : {
2247
+ "nodetype" : "namednumber",
2248
+ "number" : "58"
2249
+ },
2250
+ "r29" : {
2251
+ "nodetype" : "namednumber",
2252
+ "number" : "59"
2253
+ },
2254
+ "r30" : {
2255
+ "nodetype" : "namednumber",
2256
+ "number" : "60"
2257
+ },
2258
+ "r31" : {
2259
+ "nodetype" : "namednumber",
2260
+ "number" : "61"
2261
+ },
2262
+ },
2263
+ },
2264
+ "access" : "readwrite",
2265
+ "default" : "(d1, d2, d3, d4, d5, d6, d7, d8, d9, d10, d11, d12, d13, d14, d15, d16, d17, d18, d19, d20, d21, d22, d23, d24, d25, d26, d27, d28, d29, d30, d31, r1, r2, r3, r4, r5, r6, r7, r8, r9, r10, r11, r12, r13, r14, r15, r16, r17, r18, r19, r20, r21, r22, r23, r24, r25, r26, r27, r28, r29, r30, r31)",
2266
+ "description" :
2267
+ """Within the overall time period specified in the
2268
+ pmSchedTimePeriod object, the value of this object specifies
2269
+ the specific days of the month within that time period when
2270
+ the schedule is active.
2271
+
2272
+ There are two sets of bits one can use to define the day
2273
+ within a month:
2274
+
2275
+ Enumerations starting with the letter 'd' indicate a
2276
+ day in a month relative to the first day of a month.
2277
+ The first day of the month can therefore be specified
2278
+ by setting the bit d1(0), and d31(30) means the last
2279
+ day of a month with 31 days.
2280
+
2281
+ Enumerations starting with the letter 'r' indicate a
2282
+ day in a month in reverse order, relative to the last
2283
+ day of a month. The last day in the month can therefore
2284
+ be specified by setting the bit r1(31), and r31(61) means
2285
+ the first day of a month with 31 days.
2286
+
2287
+ Setting multiple bits will include several days in the set
2288
+ of possible days for this schedule. Setting all bits starting
2289
+ with the letter 'd' or all bits starting with the letter 'r'
2290
+ will cause the schedule to act independently of the day of the
2291
+ month.""",
2292
+ }, # column
2293
+ "pmSchedWeekDay" : {
2294
+ "nodetype" : "column",
2295
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2296
+ "oid" : "1.3.6.1.2.1.124.8.1.7",
2297
+ "status" : "current",
2298
+ "syntax" : {
2299
+ "type" : {
2300
+ "basetype" : "Bits",
2301
+ "sunday" : {
2302
+ "nodetype" : "namednumber",
2303
+ "number" : "0"
2304
+ },
2305
+ "monday" : {
2306
+ "nodetype" : "namednumber",
2307
+ "number" : "1"
2308
+ },
2309
+ "tuesday" : {
2310
+ "nodetype" : "namednumber",
2311
+ "number" : "2"
2312
+ },
2313
+ "wednesday" : {
2314
+ "nodetype" : "namednumber",
2315
+ "number" : "3"
2316
+ },
2317
+ "thursday" : {
2318
+ "nodetype" : "namednumber",
2319
+ "number" : "4"
2320
+ },
2321
+ "friday" : {
2322
+ "nodetype" : "namednumber",
2323
+ "number" : "5"
2324
+ },
2325
+ "saturday" : {
2326
+ "nodetype" : "namednumber",
2327
+ "number" : "6"
2328
+ },
2329
+ },
2330
+ },
2331
+ "access" : "readwrite",
2332
+ "default" : "(sunday, monday, tuesday, wednesday, thursday, friday, saturday)",
2333
+ "description" :
2334
+ """Within the overall time period specified in the
2335
+ pmSchedTimePeriod object, the value of this object specifies
2336
+ the specific days of the week within that time period when
2337
+ the schedule is active. Setting all bits will cause the
2338
+ schedule to act independently of the day of the week.""",
2339
+ }, # column
2340
+ "pmSchedTimeOfDay" : {
2341
+ "nodetype" : "column",
2342
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2343
+ "oid" : "1.3.6.1.2.1.124.8.1.8",
2344
+ "status" : "current",
2345
+ "syntax" : {
2346
+ "type" : {
2347
+ "basetype" : "OctetString",
2348
+ "parent module" : {
2349
+ "name" : "POLICY-BASED-MANAGEMENT-MIB",
2350
+ "type" : "PmUTF8String",
2351
+ },
2352
+ "ranges" : [
2353
+ {
2354
+ "min" : "0",
2355
+ "max" : "15"
2356
+ },
2357
+ ],
2358
+ "range" : {
2359
+ "min" : "0",
2360
+ "max" : "15"
2361
+ },
2362
+ },
2363
+ },
2364
+ "access" : "readwrite",
2365
+ "default" : "T000000/T235959",
2366
+ "description" :
2367
+ """Within the overall time period specified in the
2368
+ pmSchedTimePeriod object, the value of this object specifies
2369
+ the range of times in a day when the schedule is active.
2370
+
2371
+ This value is stored in a format based on the RFC 2445 format
2372
+ for 'time': The character 'T' followed by a 'time' string,
2373
+ followed by the solidus character, '/', followed by the
2374
+ character 'T', followed by a second time string. The first time
2375
+ indicates the beginning of the range, and the second time
2376
+ indicates the end. Thus, this value takes the following
2377
+ form:
2378
+
2379
+ 'Thhmmss/Thhmmss'.
2380
+
2381
+ The second substring always identifies a later time than the
2382
+ first substring. To allow for ranges that span midnight,
2383
+ however, the value of the second string may be smaller than
2384
+ the value of the first substring. Thus, 'T080000/T210000'
2385
+ identifies the range from 0800 until 2100, whereas
2386
+ 'T210000/T080000' identifies the range from 2100 until 0800 of
2387
+ the following day.
2388
+
2389
+ When a range spans midnight, by definition it includes parts
2390
+ of two successive days. When one of these days is also
2391
+ selected by either the MonthOfYearMask, DayOfMonthMask, and/or
2392
+ DayOfWeekMask, but the other day is not, then the policy is
2393
+ active only during the portion of the range that falls on the
2394
+ selected day. For example, if the range extends from 2100
2395
+
2396
+
2397
+
2398
+ until 0800, and the day of week mask selects Monday and
2399
+ Tuesday, then the policy is active during the following three
2400
+ intervals:
2401
+
2402
+ From midnight Sunday until 0800 Monday
2403
+ From 2100 Monday until 0800 Tuesday
2404
+ From 2100 Tuesday until 23:59:59 Tuesday
2405
+
2406
+ Setting this value to 'T000000/T235959' will cause the
2407
+ schedule to act independently of the time of day.""",
2408
+ }, # column
2409
+ "pmSchedLocalOrUtc" : {
2410
+ "nodetype" : "column",
2411
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2412
+ "oid" : "1.3.6.1.2.1.124.8.1.9",
2413
+ "status" : "current",
2414
+ "syntax" : {
2415
+ "type" : {
2416
+ "basetype" : "Enumeration",
2417
+ "localTime" : {
2418
+ "nodetype" : "namednumber",
2419
+ "number" : "1"
2420
+ },
2421
+ "utcTime" : {
2422
+ "nodetype" : "namednumber",
2423
+ "number" : "2"
2424
+ },
2425
+ },
2426
+ },
2427
+ "access" : "readwrite",
2428
+ "default" : "utcTime",
2429
+ "description" :
2430
+ """This object indicates whether the times represented in the
2431
+ TimePeriod object and in the various Mask objects represent
2432
+ local times or UTC times.""",
2433
+ }, # column
2434
+ "pmSchedStorageType" : {
2435
+ "nodetype" : "column",
2436
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2437
+ "oid" : "1.3.6.1.2.1.124.8.1.10",
2438
+ "status" : "current",
2439
+ "syntax" : {
2440
+ "type" : { "module" :"SNMPv2-TC", "name" : "StorageType"},
2441
+ },
2442
+ "access" : "readwrite",
2443
+ "default" : "volatile",
2444
+ "description" :
2445
+ """This object defines whether this schedule entry is kept
2446
+ in volatile storage and lost upon reboot or
2447
+ backed up by non-volatile or permanent storage.
2448
+
2449
+ Conceptual rows having the value 'permanent' must allow write
2450
+ access to the columnar objects pmSchedDescr, pmSchedWeekDay,
2451
+ pmSchedMonth, and pmSchedDay.
2452
+
2453
+ If the value of this object is 'permanent', no values in the
2454
+ associated row have to be writable.""",
2455
+ }, # column
2456
+ "pmSchedRowStatus" : {
2457
+ "nodetype" : "column",
2458
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2459
+ "oid" : "1.3.6.1.2.1.124.8.1.11",
2460
+ "status" : "current",
2461
+ "syntax" : {
2462
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
2463
+ },
2464
+ "access" : "readwrite",
2465
+ "description" :
2466
+ """The status of this schedule entry.
2467
+
2468
+ If the value of this object is active, no object in this row
2469
+ may be modified.""",
2470
+ }, # column
2471
+ "pmTrackingPETable" : {
2472
+ "nodetype" : "table",
2473
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2474
+ "oid" : "1.3.6.1.2.1.124.9",
2475
+ "status" : "current",
2476
+ "description" :
2477
+ """The pmTrackingPETable describes what elements
2478
+ are active (under control of) a policy. This table is indexed
2479
+ in order to optimize retrieval of the entire status for a
2480
+ given policy.""",
2481
+ }, # table
2482
+ "pmTrackingPEEntry" : {
2483
+ "nodetype" : "row",
2484
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2485
+ "oid" : "1.3.6.1.2.1.124.9.1",
2486
+ "status" : "current",
2487
+ "linkage" : [
2488
+ "pmPolicyIndex",
2489
+ "pmTrackingPEElement",
2490
+ "pmTrackingPEContextName",
2491
+ "pmTrackingPEContextEngineID",
2492
+ ],
2493
+ "description" :
2494
+ """An entry in the pmTrackingPETable. The pmPolicyIndex in
2495
+ the index specifies the policy tracked by this entry.
2496
+
2497
+ Note that some combinations of index values may result in an
2498
+ instance name that exceeds a length of 128 sub-identifiers,
2499
+ which exceeds the maximum for the SNMP
2500
+ protocol. Implementations should take care to avoid such
2501
+ combinations.""",
2502
+ }, # row
2503
+ "pmTrackingPEElement" : {
2504
+ "nodetype" : "column",
2505
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2506
+ "oid" : "1.3.6.1.2.1.124.9.1.1",
2507
+ "status" : "current",
2508
+ "syntax" : {
2509
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowPointer"},
2510
+ },
2511
+ "access" : "noaccess",
2512
+ "description" :
2513
+ """The element that is acted upon by the associated policy.
2514
+
2515
+ As this object is used in the index for the
2516
+ pmTrackingPETable, users of this table should be careful not
2517
+ to create entries that would result in instance names with
2518
+ more than 128 sub-identifiers.""",
2519
+ }, # column
2520
+ "pmTrackingPEContextName" : {
2521
+ "nodetype" : "column",
2522
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2523
+ "oid" : "1.3.6.1.2.1.124.9.1.2",
2524
+ "status" : "current",
2525
+ "syntax" : {
2526
+ "type" : {
2527
+ "basetype" : "OctetString",
2528
+ "parent module" : {
2529
+ "name" : "SNMP-FRAMEWORK-MIB",
2530
+ "type" : "SnmpAdminString",
2531
+ },
2532
+ "ranges" : [
2533
+ {
2534
+ "min" : "0",
2535
+ "max" : "32"
2536
+ },
2537
+ ],
2538
+ "range" : {
2539
+ "min" : "0",
2540
+ "max" : "32"
2541
+ },
2542
+ },
2543
+ },
2544
+ "access" : "noaccess",
2545
+ "description" :
2546
+ """If the associated element is not in the default SNMP context
2547
+ for the target system, this object is used to identify the
2548
+ context. If the element is in the default context, this object
2549
+ is equal to the empty string.""",
2550
+ }, # column
2551
+ "pmTrackingPEContextEngineID" : {
2552
+ "nodetype" : "column",
2553
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2554
+ "oid" : "1.3.6.1.2.1.124.9.1.3",
2555
+ "status" : "current",
2556
+ "syntax" : {
2557
+ "type" : {
2558
+ "basetype" : "OctetString",
2559
+ "ranges" : [
2560
+ {
2561
+ "min" : "0",
2562
+ "max" : "0"
2563
+ },
2564
+ {
2565
+ "min" : "5",
2566
+ "max" : "32"
2567
+ },
2568
+ ],
2569
+ "range" : {
2570
+ "min" : "0",
2571
+ "max" : "32"
2572
+ },
2573
+ },
2574
+ },
2575
+ "access" : "noaccess",
2576
+ "description" :
2577
+ """If the associated element is on a remote system, this object
2578
+ is used to identify the remote system. This object contains
2579
+ the contextEngineID of the system on which the associated
2580
+ element resides. If the element is on the local system,
2581
+ this object will be the empty string.""",
2582
+ }, # column
2583
+ "pmTrackingPEInfo" : {
2584
+ "nodetype" : "column",
2585
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2586
+ "oid" : "1.3.6.1.2.1.124.9.1.4",
2587
+ "status" : "current",
2588
+ "syntax" : {
2589
+ "type" : {
2590
+ "basetype" : "Bits",
2591
+ "actionSkippedDueToPrecedence" : {
2592
+ "nodetype" : "namednumber",
2593
+ "number" : "0"
2594
+ },
2595
+ "conditionRunTimeException" : {
2596
+ "nodetype" : "namednumber",
2597
+ "number" : "1"
2598
+ },
2599
+ "conditionUserSignal" : {
2600
+ "nodetype" : "namednumber",
2601
+ "number" : "2"
2602
+ },
2603
+ "actionRunTimeException" : {
2604
+ "nodetype" : "namednumber",
2605
+ "number" : "3"
2606
+ },
2607
+ "actionUserSignal" : {
2608
+ "nodetype" : "namednumber",
2609
+ "number" : "4"
2610
+ },
2611
+ },
2612
+ },
2613
+ "access" : "readonly",
2614
+ "description" :
2615
+ """This object returns information about the previous policy
2616
+ script executions.
2617
+
2618
+ If the actionSkippedDueToPrecedence(1) bit is set, the last
2619
+ execution of the associated policy condition returned non-zero,
2620
+ but the action is not active, because it was trumped by a
2621
+ matching policy condition in the same precedence group with a
2622
+ higher precedence value.
2623
+
2624
+ If the conditionRunTimeException(2) bit is set, the last
2625
+ execution of the associated policy condition encountered a
2626
+ run-time exception and aborted.
2627
+
2628
+ If the conditionUserSignal(3) bit is set, the last
2629
+ execution of the associated policy condition called the
2630
+ signalError() function.
2631
+
2632
+ If the actionRunTimeException(4) bit is set, the last
2633
+ execution of the associated policy action encountered a
2634
+ run-time exception and aborted.
2635
+
2636
+ If the actionUserSignal(5) bit is set, the last
2637
+ execution of the associated policy action called the
2638
+ signalError() function.
2639
+
2640
+ Entries will only exist in this table of one or more bits are
2641
+ set. In particular, if an entry does not exist for a
2642
+ particular policy/element combination, it can be assumed that
2643
+ the policy's condition did not match 'this element'.""",
2644
+ }, # column
2645
+ "pmTrackingEPTable" : {
2646
+ "nodetype" : "table",
2647
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2648
+ "oid" : "1.3.6.1.2.1.124.10",
2649
+ "status" : "current",
2650
+ "description" :
2651
+ """The pmTrackingEPTable describes what policies
2652
+ are controlling an element. This table is indexed in
2653
+ order to optimize retrieval of the status of all policies
2654
+ active for a given element.""",
2655
+ }, # table
2656
+ "pmTrackingEPEntry" : {
2657
+ "nodetype" : "row",
2658
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2659
+ "oid" : "1.3.6.1.2.1.124.10.1",
2660
+ "status" : "current",
2661
+ "linkage" : [
2662
+ "pmTrackingEPElement",
2663
+ "pmTrackingEPContextName",
2664
+ "pmTrackingEPContextEngineID",
2665
+ "pmPolicyIndex",
2666
+ ],
2667
+ "description" :
2668
+ """An entry in the pmTrackingEPTable. Entries exist for all
2669
+ element/policy combinations for which the policy's condition
2670
+ matches and only if the schedule for the policy is active.
2671
+
2672
+ The pmPolicyIndex in the index specifies the policy
2673
+ tracked by this entry.
2674
+
2675
+ Note that some combinations of index values may result in an
2676
+ instance name that exceeds a length of 128 sub-identifiers,
2677
+ which exceeds the maximum for the SNMP protocol.
2678
+ Implementations should take care to avoid such combinations.""",
2679
+ }, # row
2680
+ "pmTrackingEPElement" : {
2681
+ "nodetype" : "column",
2682
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2683
+ "oid" : "1.3.6.1.2.1.124.10.1.1",
2684
+ "status" : "current",
2685
+ "syntax" : {
2686
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowPointer"},
2687
+ },
2688
+ "access" : "noaccess",
2689
+ "description" :
2690
+ """The element acted upon by the associated policy.
2691
+
2692
+ As this object is used in the index for the
2693
+ pmTrackingEPTable, users of this table should be careful
2694
+ not to create entries that would result in instance names
2695
+ with more than 128 sub-identifiers.""",
2696
+ }, # column
2697
+ "pmTrackingEPContextName" : {
2698
+ "nodetype" : "column",
2699
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2700
+ "oid" : "1.3.6.1.2.1.124.10.1.2",
2701
+ "status" : "current",
2702
+ "syntax" : {
2703
+ "type" : {
2704
+ "basetype" : "OctetString",
2705
+ "parent module" : {
2706
+ "name" : "SNMP-FRAMEWORK-MIB",
2707
+ "type" : "SnmpAdminString",
2708
+ },
2709
+ "ranges" : [
2710
+ {
2711
+ "min" : "0",
2712
+ "max" : "32"
2713
+ },
2714
+ ],
2715
+ "range" : {
2716
+ "min" : "0",
2717
+ "max" : "32"
2718
+ },
2719
+ },
2720
+ },
2721
+ "access" : "noaccess",
2722
+ "description" :
2723
+ """If the associated element is not in the default SNMP context
2724
+
2725
+
2726
+
2727
+ for the target system, this object is used to identify the
2728
+ context. If the element is in the default context, this object
2729
+ is equal to the empty string.""",
2730
+ }, # column
2731
+ "pmTrackingEPContextEngineID" : {
2732
+ "nodetype" : "column",
2733
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2734
+ "oid" : "1.3.6.1.2.1.124.10.1.3",
2735
+ "status" : "current",
2736
+ "syntax" : {
2737
+ "type" : {
2738
+ "basetype" : "OctetString",
2739
+ "ranges" : [
2740
+ {
2741
+ "min" : "0",
2742
+ "max" : "0"
2743
+ },
2744
+ {
2745
+ "min" : "5",
2746
+ "max" : "32"
2747
+ },
2748
+ ],
2749
+ "range" : {
2750
+ "min" : "0",
2751
+ "max" : "32"
2752
+ },
2753
+ },
2754
+ },
2755
+ "access" : "noaccess",
2756
+ "description" :
2757
+ """If the associated element is on a remote system, this object
2758
+ is used to identify the remote system. This object contains
2759
+ the contextEngineID of the system on which the associated
2760
+ element resides. If the element is on the local system,
2761
+ this object will be the empty string.""",
2762
+ }, # column
2763
+ "pmTrackingEPStatus" : {
2764
+ "nodetype" : "column",
2765
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2766
+ "oid" : "1.3.6.1.2.1.124.10.1.4",
2767
+ "status" : "current",
2768
+ "syntax" : {
2769
+ "type" : {
2770
+ "basetype" : "Enumeration",
2771
+ "on" : {
2772
+ "nodetype" : "namednumber",
2773
+ "number" : "1"
2774
+ },
2775
+ "forceOff" : {
2776
+ "nodetype" : "namednumber",
2777
+ "number" : "2"
2778
+ },
2779
+ },
2780
+ },
2781
+ "access" : "readwrite",
2782
+ "description" :
2783
+ """This entry will only exist if the calendar for the policy is
2784
+ active and if the associated policyCondition returned 1 for
2785
+ 'this element'.
2786
+
2787
+ A policy can be forcibly disabled on a particular element
2788
+ by setting this value to forceOff(2). The agent should then
2789
+ act as though the policyCondition failed for 'this element'.
2790
+ The forceOff(2) state will persist (even across reboots) until
2791
+ this value is set to on(1) by a management request. The
2792
+ forceOff(2) state may be set even if the entry does not
2793
+ previously exist so that future policy invocations can be
2794
+ avoided.
2795
+
2796
+ Unless forcibly disabled, if this entry exists, its value
2797
+ will be on(1).""",
2798
+ }, # column
2799
+ "pmDebuggingTable" : {
2800
+ "nodetype" : "table",
2801
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2802
+ "oid" : "1.3.6.1.2.1.124.11",
2803
+ "status" : "current",
2804
+ "description" :
2805
+ """Policies that have debugging turned on will generate a log
2806
+ entry in the policy debugging table for every runtime
2807
+ exception that occurs in either the condition or action
2808
+ code.
2809
+
2810
+ The pmDebuggingTable logs debugging messages when
2811
+ policies experience run-time exceptions in either the condition
2812
+ or action code and the associated pmPolicyDebugging object
2813
+ has been turned on.
2814
+
2815
+ The maximum number of debugging entries that will be stored
2816
+ and the maximum length of time an entry will be kept are an
2817
+ implementation-dependent manner. If entries must
2818
+ be discarded to make room for new entries, the oldest entries
2819
+ must be discarded first.
2820
+
2821
+ If the system restarts, all debugging entries may be deleted.""",
2822
+ }, # table
2823
+ "pmDebuggingEntry" : {
2824
+ "nodetype" : "row",
2825
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2826
+ "oid" : "1.3.6.1.2.1.124.11.1",
2827
+ "status" : "current",
2828
+ "linkage" : [
2829
+ "pmPolicyIndex",
2830
+ "pmDebuggingElement",
2831
+ "pmDebuggingContextName",
2832
+ "pmDebuggingContextEngineID",
2833
+ "pmDebuggingLogIndex",
2834
+ ],
2835
+ "description" :
2836
+ """An entry in the pmDebuggingTable. The pmPolicyIndex in the
2837
+ index specifies the policy that encountered the exception
2838
+ that led to this log entry.
2839
+
2840
+ Note that some combinations of index values may result in an
2841
+ instance name that exceeds a length of 128 sub-identifiers,
2842
+ which exceeds the maximum for the SNMP protocol.
2843
+ Implementations should take care to avoid such combinations.""",
2844
+ }, # row
2845
+ "pmDebuggingElement" : {
2846
+ "nodetype" : "column",
2847
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2848
+ "oid" : "1.3.6.1.2.1.124.11.1.1",
2849
+ "status" : "current",
2850
+ "syntax" : {
2851
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowPointer"},
2852
+ },
2853
+ "access" : "noaccess",
2854
+ "description" :
2855
+ """The element the policy was executing on when it encountered
2856
+ the error that led to this log entry.
2857
+
2858
+ For example, if the element is interface 3, then this object
2859
+ will contain the OID for 'ifIndex.3'.
2860
+
2861
+ As this object is used in the index for the
2862
+ pmDebuggingTable, users of this table should be careful
2863
+ not to create entries that would result in instance names
2864
+ with more than 128 sub-identifiers.""",
2865
+ }, # column
2866
+ "pmDebuggingContextName" : {
2867
+ "nodetype" : "column",
2868
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2869
+ "oid" : "1.3.6.1.2.1.124.11.1.2",
2870
+ "status" : "current",
2871
+ "syntax" : {
2872
+ "type" : {
2873
+ "basetype" : "OctetString",
2874
+ "parent module" : {
2875
+ "name" : "SNMP-FRAMEWORK-MIB",
2876
+ "type" : "SnmpAdminString",
2877
+ },
2878
+ "ranges" : [
2879
+ {
2880
+ "min" : "0",
2881
+ "max" : "32"
2882
+ },
2883
+ ],
2884
+ "range" : {
2885
+ "min" : "0",
2886
+ "max" : "32"
2887
+ },
2888
+ },
2889
+ },
2890
+ "access" : "noaccess",
2891
+ "description" :
2892
+ """If the associated element is not in the default SNMP context
2893
+ for the target system, this object is used to identify the
2894
+ context. If the element is in the default context, this object
2895
+ is equal to the empty string.""",
2896
+ }, # column
2897
+ "pmDebuggingContextEngineID" : {
2898
+ "nodetype" : "column",
2899
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2900
+ "oid" : "1.3.6.1.2.1.124.11.1.3",
2901
+ "status" : "current",
2902
+ "syntax" : {
2903
+ "type" : {
2904
+ "basetype" : "OctetString",
2905
+ "ranges" : [
2906
+ {
2907
+ "min" : "0",
2908
+ "max" : "0"
2909
+ },
2910
+ {
2911
+ "min" : "5",
2912
+ "max" : "32"
2913
+ },
2914
+ ],
2915
+ "range" : {
2916
+ "min" : "0",
2917
+ "max" : "32"
2918
+ },
2919
+ },
2920
+ },
2921
+ "access" : "noaccess",
2922
+ "description" :
2923
+ """If the associated element is on a remote system, this object
2924
+ is used to identify the remote system. This object contains
2925
+ the contextEngineID of the system on which the associated
2926
+ element resides. If the element is on the local system,
2927
+ this object will be the empty string.""",
2928
+ }, # column
2929
+ "pmDebuggingLogIndex" : {
2930
+ "nodetype" : "column",
2931
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2932
+ "oid" : "1.3.6.1.2.1.124.11.1.4",
2933
+ "status" : "current",
2934
+ "syntax" : {
2935
+ "type" : {
2936
+ "basetype" : "Unsigned32",
2937
+ "ranges" : [
2938
+ {
2939
+ "min" : "1",
2940
+ "max" : "4294967295"
2941
+ },
2942
+ ],
2943
+ "range" : {
2944
+ "min" : "1",
2945
+ "max" : "4294967295"
2946
+ },
2947
+ },
2948
+ },
2949
+ "access" : "noaccess",
2950
+ "description" :
2951
+ """A unique index for this log entry among other log entries
2952
+ for this policy/element combination.""",
2953
+ }, # column
2954
+ "pmDebuggingMessage" : {
2955
+ "nodetype" : "column",
2956
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2957
+ "oid" : "1.3.6.1.2.1.124.11.1.5",
2958
+ "status" : "current",
2959
+ "syntax" : {
2960
+ "type" : {
2961
+ "basetype" : "OctetString",
2962
+ "parent module" : {
2963
+ "name" : "POLICY-BASED-MANAGEMENT-MIB",
2964
+ "type" : "PmUTF8String",
2965
+ },
2966
+ "ranges" : [
2967
+ {
2968
+ "min" : "0",
2969
+ "max" : "128"
2970
+ },
2971
+ ],
2972
+ "range" : {
2973
+ "min" : "0",
2974
+ "max" : "128"
2975
+ },
2976
+ },
2977
+ },
2978
+ "access" : "readonly",
2979
+ "description" :
2980
+ """An error message generated by the policy execution
2981
+ environment. It is recommended that this message include the
2982
+ time of day when the message was generated, if known.""",
2983
+ }, # column
2984
+ "pmConformance" : {
2985
+ "nodetype" : "node",
2986
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2987
+ "oid" : "1.3.6.1.2.1.124.12",
2988
+ }, # node
2989
+ "pmCompliances" : {
2990
+ "nodetype" : "node",
2991
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2992
+ "oid" : "1.3.6.1.2.1.124.12.1",
2993
+ }, # node
2994
+ "pmGroups" : {
2995
+ "nodetype" : "node",
2996
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
2997
+ "oid" : "1.3.6.1.2.1.124.12.2",
2998
+ }, # node
2999
+ "pmBaseFunctionLibrary" : {
3000
+ "nodetype" : "node",
3001
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
3002
+ "oid" : "1.3.6.1.2.1.124.12.2.4",
3003
+ }, # node
3004
+ }, # nodes
3005
+
3006
+ "notifications" : {
3007
+ "pmNewRoleNotification" : {
3008
+ "nodetype" : "notification",
3009
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
3010
+ "oid" : "1.3.6.1.2.1.124.0.1",
3011
+ "status" : "current",
3012
+ "objects" : {
3013
+ "pmRoleStatus" : {
3014
+ "nodetype" : "object",
3015
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3016
+ },
3017
+ },
3018
+ "description" :
3019
+ """The pmNewRoleNotification is sent when an agent is configured
3020
+ with its first instance of a previously unused role string
3021
+ (not every time a new element is given a particular role).
3022
+
3023
+ An instance of the pmRoleStatus object is sent containing
3024
+ the new roleString in its index. In the event that two or
3025
+ more elements are given the same role simultaneously, it is an
3026
+ implementation-dependent matter as to which pmRoleTable
3027
+ instance will be included in the notification.""",
3028
+ }, # notification
3029
+ "pmNewCapabilityNotification" : {
3030
+ "nodetype" : "notification",
3031
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
3032
+ "oid" : "1.3.6.1.2.1.124.0.2",
3033
+ "status" : "current",
3034
+ "objects" : {
3035
+ "pmCapabilitiesType" : {
3036
+ "nodetype" : "object",
3037
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3038
+ },
3039
+ },
3040
+ "description" :
3041
+ """The pmNewCapabilityNotification is sent when an agent
3042
+ gains a new capability that did not previously exist in any
3043
+ element on the system (not every time an element gains a
3044
+ particular capability).
3045
+
3046
+ An instance of the pmCapabilitiesType object is sent containing
3047
+ the identity of the new capability. In the event that two or
3048
+ more elements gain the same capability simultaneously, it is an
3049
+ implementation-dependent matter as to which pmCapabilitiesType
3050
+ instance will be included in the notification.""",
3051
+ }, # notification
3052
+ "pmAbnormalTermNotification" : {
3053
+ "nodetype" : "notification",
3054
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
3055
+ "oid" : "1.3.6.1.2.1.124.0.3",
3056
+ "status" : "current",
3057
+ "objects" : {
3058
+ "pmTrackingPEInfo" : {
3059
+ "nodetype" : "object",
3060
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3061
+ },
3062
+ },
3063
+ "description" :
3064
+ """The pmAbnormalTermNotification is sent when a policy's
3065
+ pmPolicyAbnormalTerminations gauge value changes from zero to
3066
+ any value greater than zero and no such notification has been
3067
+ sent for that policy in the last 5 minutes.
3068
+
3069
+ The notification contains an instance of the pmTrackingPEInfo
3070
+ object where the pmPolicyIndex component of the index
3071
+ identifies the associated policy and the rest of the index
3072
+ identifies an element on which the policy failed.""",
3073
+ }, # notification
3074
+ }, # notifications
3075
+
3076
+ "groups" : {
3077
+ "pmPolicyManagementGroup" : {
3078
+ "nodetype" : "group",
3079
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
3080
+ "oid" : "1.3.6.1.2.1.124.12.2.1",
3081
+ "status" : "current",
3082
+ "members" : {
3083
+ "pmPolicyPrecedenceGroup" : {
3084
+ "nodetype" : "member",
3085
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3086
+ },
3087
+ "pmPolicyPrecedence" : {
3088
+ "nodetype" : "member",
3089
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3090
+ },
3091
+ "pmPolicySchedule" : {
3092
+ "nodetype" : "member",
3093
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3094
+ },
3095
+ "pmPolicyElementTypeFilter" : {
3096
+ "nodetype" : "member",
3097
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3098
+ },
3099
+ "pmPolicyConditionScriptIndex" : {
3100
+ "nodetype" : "member",
3101
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3102
+ },
3103
+ "pmPolicyActionScriptIndex" : {
3104
+ "nodetype" : "member",
3105
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3106
+ },
3107
+ "pmPolicyParameters" : {
3108
+ "nodetype" : "member",
3109
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3110
+ },
3111
+ "pmPolicyConditionMaxLatency" : {
3112
+ "nodetype" : "member",
3113
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3114
+ },
3115
+ "pmPolicyActionMaxLatency" : {
3116
+ "nodetype" : "member",
3117
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3118
+ },
3119
+ "pmPolicyMaxIterations" : {
3120
+ "nodetype" : "member",
3121
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3122
+ },
3123
+ "pmPolicyDescription" : {
3124
+ "nodetype" : "member",
3125
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3126
+ },
3127
+ "pmPolicyMatches" : {
3128
+ "nodetype" : "member",
3129
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3130
+ },
3131
+ "pmPolicyAbnormalTerminations" : {
3132
+ "nodetype" : "member",
3133
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3134
+ },
3135
+ "pmPolicyExecutionErrors" : {
3136
+ "nodetype" : "member",
3137
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3138
+ },
3139
+ "pmPolicyDebugging" : {
3140
+ "nodetype" : "member",
3141
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3142
+ },
3143
+ "pmPolicyStorageType" : {
3144
+ "nodetype" : "member",
3145
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3146
+ },
3147
+ "pmPolicyAdminStatus" : {
3148
+ "nodetype" : "member",
3149
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3150
+ },
3151
+ "pmPolicyRowStatus" : {
3152
+ "nodetype" : "member",
3153
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3154
+ },
3155
+ "pmPolicyCodeText" : {
3156
+ "nodetype" : "member",
3157
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3158
+ },
3159
+ "pmPolicyCodeStatus" : {
3160
+ "nodetype" : "member",
3161
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3162
+ },
3163
+ "pmElementTypeRegMaxLatency" : {
3164
+ "nodetype" : "member",
3165
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3166
+ },
3167
+ "pmElementTypeRegDescription" : {
3168
+ "nodetype" : "member",
3169
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3170
+ },
3171
+ "pmElementTypeRegStorageType" : {
3172
+ "nodetype" : "member",
3173
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3174
+ },
3175
+ "pmElementTypeRegRowStatus" : {
3176
+ "nodetype" : "member",
3177
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3178
+ },
3179
+ "pmRoleStatus" : {
3180
+ "nodetype" : "member",
3181
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3182
+ },
3183
+ "pmCapabilitiesType" : {
3184
+ "nodetype" : "member",
3185
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3186
+ },
3187
+ "pmCapabilitiesOverrideState" : {
3188
+ "nodetype" : "member",
3189
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3190
+ },
3191
+ "pmCapabilitiesOverrideRowStatus" : {
3192
+ "nodetype" : "member",
3193
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3194
+ },
3195
+ "pmTrackingPEInfo" : {
3196
+ "nodetype" : "member",
3197
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3198
+ },
3199
+ "pmTrackingEPStatus" : {
3200
+ "nodetype" : "member",
3201
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3202
+ },
3203
+ "pmDebuggingMessage" : {
3204
+ "nodetype" : "member",
3205
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3206
+ },
3207
+ }, # members
3208
+ "description" :
3209
+ """Objects that allow for the creation and management of
3210
+ configuration policies.""",
3211
+ }, # group
3212
+ "pmSchedGroup" : {
3213
+ "nodetype" : "group",
3214
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
3215
+ "oid" : "1.3.6.1.2.1.124.12.2.2",
3216
+ "status" : "current",
3217
+ "members" : {
3218
+ "pmSchedLocalTime" : {
3219
+ "nodetype" : "member",
3220
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3221
+ },
3222
+ "pmSchedGroupIndex" : {
3223
+ "nodetype" : "member",
3224
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3225
+ },
3226
+ "pmSchedDescr" : {
3227
+ "nodetype" : "member",
3228
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3229
+ },
3230
+ "pmSchedTimePeriod" : {
3231
+ "nodetype" : "member",
3232
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3233
+ },
3234
+ "pmSchedMonth" : {
3235
+ "nodetype" : "member",
3236
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3237
+ },
3238
+ "pmSchedDay" : {
3239
+ "nodetype" : "member",
3240
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3241
+ },
3242
+ "pmSchedWeekDay" : {
3243
+ "nodetype" : "member",
3244
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3245
+ },
3246
+ "pmSchedTimeOfDay" : {
3247
+ "nodetype" : "member",
3248
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3249
+ },
3250
+ "pmSchedLocalOrUtc" : {
3251
+ "nodetype" : "member",
3252
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3253
+ },
3254
+ "pmSchedStorageType" : {
3255
+ "nodetype" : "member",
3256
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3257
+ },
3258
+ "pmSchedRowStatus" : {
3259
+ "nodetype" : "member",
3260
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3261
+ },
3262
+ }, # members
3263
+ "description" :
3264
+ """Objects that allow for the scheduling of policies.""",
3265
+ }, # group
3266
+ "pmNotificationGroup" : {
3267
+ "nodetype" : "group",
3268
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
3269
+ "oid" : "1.3.6.1.2.1.124.12.2.3",
3270
+ "status" : "current",
3271
+ "members" : {
3272
+ "pmNewRoleNotification" : {
3273
+ "nodetype" : "member",
3274
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3275
+ },
3276
+ "pmNewCapabilityNotification" : {
3277
+ "nodetype" : "member",
3278
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3279
+ },
3280
+ "pmAbnormalTermNotification" : {
3281
+ "nodetype" : "member",
3282
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3283
+ },
3284
+ }, # members
3285
+ "description" :
3286
+ """Notifications sent by an Policy MIB agent.""",
3287
+ }, # group
3288
+ }, # groups
3289
+
3290
+ "compliances" : {
3291
+ "pmCompliance" : {
3292
+ "nodetype" : "compliance",
3293
+ "moduleName" : "POLICY-BASED-MANAGEMENT-MIB",
3294
+ "oid" : "1.3.6.1.2.1.124.12.1.1",
3295
+ "status" : "current",
3296
+ "description" :
3297
+ """Describes the requirements for conformance to
3298
+ the Policy-Based Management MIB""",
3299
+ "requires" : {
3300
+ "pmPolicyManagementGroup" : {
3301
+ "nodetype" : "mandatory",
3302
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3303
+ },
3304
+ "pmSchedGroup" : {
3305
+ "nodetype" : "mandatory",
3306
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3307
+ },
3308
+ "pmNotificationGroup" : {
3309
+ "nodetype" : "mandatory",
3310
+ "module" : "POLICY-BASED-MANAGEMENT-MIB"
3311
+ },
3312
+ }, # requires
3313
+ }, # compliance
3314
+ }, # compliances
3315
+
3316
+ }