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

Sign up to get free protection for your applications and to get access to all the features.
Files changed (309) hide show
  1. checksums.yaml +4 -4
  2. data/CHANGELOG.md +5 -0
  3. data/lib/logstash/inputs/snmp.rb +75 -12
  4. data/lib/logstash/inputs/snmp/base_client.rb +162 -0
  5. data/lib/logstash/inputs/snmp/client.rb +11 -109
  6. data/lib/logstash/inputs/snmp/clientv3.rb +139 -0
  7. data/lib/logstash/inputs/snmp/mib.rb +22 -20
  8. data/lib/mibs/ietf/ACCOUNTING-CONTROL-MIB.dic +1316 -0
  9. data/lib/mibs/ietf/ADSL-LINE-EXT-MIB.dic +1724 -0
  10. data/lib/mibs/ietf/ADSL-LINE-MIB.dic +7297 -0
  11. data/lib/mibs/ietf/ADSL-TC-MIB.dic +160 -0
  12. data/lib/mibs/ietf/ADSL2-LINE-MIB.dic +8663 -0
  13. data/lib/mibs/ietf/ADSL2-LINE-TC-MIB.dic +1462 -0
  14. data/lib/mibs/ietf/AGENTX-MIB.dic +817 -0
  15. data/lib/mibs/ietf/AGGREGATE-MIB.dic +708 -0
  16. data/lib/mibs/ietf/ALARM-MIB.dic +1734 -0
  17. data/lib/mibs/ietf/APM-MIB.dic +2870 -0
  18. data/lib/mibs/ietf/APPC-MIB.dic +8687 -0
  19. data/lib/mibs/ietf/APPLETALK-MIB.dic +4399 -0
  20. data/lib/mibs/ietf/APPLICATION-MIB.dic +3750 -0
  21. data/lib/mibs/ietf/APPN-DLUR-MIB.dic +972 -0
  22. data/lib/mibs/ietf/APPN-MIB.dic +9364 -0
  23. data/lib/mibs/ietf/APPN-TRAP-MIB.dic +664 -0
  24. data/lib/mibs/ietf/APS-MIB.dic +2430 -0
  25. data/lib/mibs/ietf/ARC-MIB.dic +552 -0
  26. data/lib/mibs/ietf/ATM-ACCOUNTING-INFORMATION-MIB.dic +816 -0
  27. data/lib/mibs/ietf/ATM-MIB.dic +4104 -0
  28. data/lib/mibs/ietf/ATM-TC-MIB.dic +914 -0
  29. data/lib/mibs/ietf/ATM2-MIB.dic +4715 -0
  30. data/lib/mibs/ietf/BFD-STD-MIB.dic +2367 -0
  31. data/lib/mibs/ietf/BFD-TC-STD-MIB.dic +202 -0
  32. data/lib/mibs/ietf/BGP4-MIB.dic +1931 -0
  33. data/lib/mibs/ietf/BLDG-HVAC-MIB.dic +812 -0
  34. data/lib/mibs/ietf/BRIDGE-MIB.dic +2257 -0
  35. data/lib/mibs/ietf/CAPWAP-BASE-MIB.dic +4128 -0
  36. data/lib/mibs/ietf/CAPWAP-DOT11-MIB.dic +482 -0
  37. data/lib/mibs/ietf/CHARACTER-MIB.dic +1140 -0
  38. data/lib/mibs/ietf/CIRCUIT-IF-MIB.dic +493 -0
  39. data/lib/mibs/ietf/CLNS-MIB.dic +1702 -0
  40. data/lib/mibs/ietf/COFFEE-POT-MIB.dic +282 -0
  41. data/lib/mibs/ietf/COPS-CLIENT-MIB.dic +1270 -0
  42. data/lib/mibs/ietf/DECNET-PHIV-MIB.dic +5837 -0
  43. data/lib/mibs/ietf/DIAL-CONTROL-MIB.dic +2139 -0
  44. data/lib/mibs/ietf/DIFFSERV-CONFIG-MIB.dic +378 -0
  45. data/lib/mibs/ietf/DIFFSERV-MIB.dic +5073 -0
  46. data/lib/mibs/ietf/DIRECTORY-SERVER-MIB.dic +1041 -0
  47. data/lib/mibs/ietf/DISMAN-EVENT-MIB.dic +3151 -0
  48. data/lib/mibs/ietf/DISMAN-EXPRESSION-MIB.dic +1716 -0
  49. data/lib/mibs/ietf/DISMAN-NSLOOKUP-MIB.dic +698 -0
  50. data/lib/mibs/ietf/DISMAN-PING-MIB.dic +2635 -0
  51. data/lib/mibs/ietf/DISMAN-SCHEDULE-MIB.dic +1744 -0
  52. data/lib/mibs/ietf/DISMAN-SCRIPT-MIB.dic +2820 -0
  53. data/lib/mibs/ietf/DISMAN-TRACEROUTE-MIB.dic +3239 -0
  54. data/lib/mibs/ietf/DLSW-MIB.dic +5635 -0
  55. data/lib/mibs/ietf/DNS-RESOLVER-MIB.dic +1765 -0
  56. data/lib/mibs/ietf/DNS-SERVER-MIB.dic +1593 -0
  57. data/lib/mibs/ietf/DOCS-BPI-MIB.dic +2634 -0
  58. data/lib/mibs/ietf/DOCS-CABLE-DEVICE-MIB.dic +5042 -0
  59. data/lib/mibs/ietf/DOCS-IETF-BPI2-MIB.dic +5478 -0
  60. data/lib/mibs/ietf/DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB.dic +2447 -0
  61. data/lib/mibs/ietf/DOCS-IETF-QOS-MIB.dic +4886 -0
  62. data/lib/mibs/ietf/DOCS-IETF-SUBMGT-MIB.dic +1331 -0
  63. data/lib/mibs/ietf/DOCS-IF-MIB.dic +7980 -0
  64. data/lib/mibs/ietf/DOT12-IF-MIB.dic +1066 -0
  65. data/lib/mibs/ietf/DOT12-RPTR-MIB.dic +2669 -0
  66. data/lib/mibs/ietf/DOT3-EPON-MIB.dic +3297 -0
  67. data/lib/mibs/ietf/DOT3-OAM-MIB.dic +2830 -0
  68. data/lib/mibs/ietf/DS0-MIB.dic +466 -0
  69. data/lib/mibs/ietf/DS0BUNDLE-MIB.dic +468 -0
  70. data/lib/mibs/ietf/DS1-MIB.dic +4890 -0
  71. data/lib/mibs/ietf/DS3-MIB.dic +2719 -0
  72. data/lib/mibs/ietf/DSA-MIB.dic +888 -0
  73. data/lib/mibs/ietf/DSMON-MIB.dic +6177 -0
  74. data/lib/mibs/ietf/DVB-RCS-MIB.dic +5764 -0
  75. data/lib/mibs/ietf/EBN-MIB.dic +1026 -0
  76. data/lib/mibs/ietf/EFM-CU-MIB.dic +4335 -0
  77. data/lib/mibs/ietf/ENTITY-MIB.dic +2235 -0
  78. data/lib/mibs/ietf/ENTITY-SENSOR-MIB.dic +653 -0
  79. data/lib/mibs/ietf/ENTITY-STATE-MIB.dic +457 -0
  80. data/lib/mibs/ietf/ENTITY-STATE-TC-MIB.dic +260 -0
  81. data/lib/mibs/ietf/ETHER-CHIPSET-MIB.dic +787 -0
  82. data/lib/mibs/ietf/EtherLike-MIB.dic +2548 -0
  83. data/lib/mibs/ietf/FC-MGMT-MIB.dic +3465 -0
  84. data/lib/mibs/ietf/FCIP-MGMT-MIB.dic +1596 -0
  85. data/lib/mibs/ietf/FDDI-SMT73-MIB.dic +3378 -0
  86. data/lib/mibs/ietf/FIBRE-CHANNEL-FE-MIB.dic +2504 -0
  87. data/lib/mibs/ietf/FLOAT-TC-MIB.dic +128 -0
  88. data/lib/mibs/ietf/FLOW-METER-MIB.dic +3201 -0
  89. data/lib/mibs/ietf/FORCES-MIB.dic +598 -0
  90. data/lib/mibs/ietf/FR-ATM-PVC-SERVICE-IWF-MIB.dic +1601 -0
  91. data/lib/mibs/ietf/FR-MFR-MIB.dic +1351 -0
  92. data/lib/mibs/ietf/FRAME-RELAY-DTE-MIB.dic +1688 -0
  93. data/lib/mibs/ietf/FRNETSERV-MIB.dic +3940 -0
  94. data/lib/mibs/ietf/FRSLD-MIB.dic +2580 -0
  95. data/lib/mibs/ietf/Finisher-MIB.dic +1416 -0
  96. data/lib/mibs/ietf/GMPLS-LABEL-STD-MIB.dic +965 -0
  97. data/lib/mibs/ietf/GMPLS-LSR-STD-MIB.dic +693 -0
  98. data/lib/mibs/ietf/GMPLS-TC-STD-MIB.dic +180 -0
  99. data/lib/mibs/ietf/GMPLS-TE-STD-MIB.dic +2542 -0
  100. data/lib/mibs/ietf/GSMP-MIB.dic +2468 -0
  101. data/lib/mibs/ietf/HC-ALARM-MIB.dic +1050 -0
  102. data/lib/mibs/ietf/HC-PerfHist-TC-MIB.dic +310 -0
  103. data/lib/mibs/ietf/HC-RMON-MIB.dic +4456 -0
  104. data/lib/mibs/ietf/HDSL2-SHDSL-LINE-MIB.dic +3955 -0
  105. data/lib/mibs/ietf/HOST-RESOURCES-MIB.dic +2453 -0
  106. data/lib/mibs/ietf/HPR-IP-MIB.dic +640 -0
  107. data/lib/mibs/ietf/HPR-MIB.dic +1959 -0
  108. data/lib/mibs/ietf/IANA-ITU-ALARM-TC-MIB.dic +936 -0
  109. data/lib/mibs/ietf/IF-CAP-STACK-MIB.dic +356 -0
  110. data/lib/mibs/ietf/IF-INVERTED-STACK-MIB.dic +220 -0
  111. data/lib/mibs/ietf/IF-MIB.dic +2753 -0
  112. data/lib/mibs/ietf/IFCP-MGMT-MIB.dic +1717 -0
  113. data/lib/mibs/ietf/IGMP-STD-MIB.dic +809 -0
  114. data/lib/mibs/ietf/INET-ADDRESS-MIB.dic +570 -0
  115. data/lib/mibs/ietf/INTEGRATED-SERVICES-GUARANTEED-MIB.dic +319 -0
  116. data/lib/mibs/ietf/INTEGRATED-SERVICES-MIB.dic +1196 -0
  117. data/lib/mibs/ietf/INTERFACETOPN-MIB.dic +1705 -0
  118. data/lib/mibs/ietf/IP-FORWARD-MIB.dic +1853 -0
  119. data/lib/mibs/ietf/IP-MIB.dic +7064 -0
  120. data/lib/mibs/ietf/IPATM-IPMC-MIB.dic +4830 -0
  121. data/lib/mibs/ietf/IPFIX-MIB.dic +2334 -0
  122. data/lib/mibs/ietf/IPFIX-SELECTOR-MIB.dic +215 -0
  123. data/lib/mibs/ietf/IPMCAST-MIB.dic +3390 -0
  124. data/lib/mibs/ietf/IPMROUTE-STD-MIB.dic +1246 -0
  125. data/lib/mibs/ietf/IPOA-MIB.dic +2372 -0
  126. data/lib/mibs/ietf/IPS-AUTH-MIB.dic +1609 -0
  127. data/lib/mibs/ietf/IPSEC-SPD-MIB.dic +3989 -0
  128. data/lib/mibs/ietf/IPV6-FLOW-LABEL-MIB.dic +110 -0
  129. data/lib/mibs/ietf/IPV6-ICMP-MIB.dic +748 -0
  130. data/lib/mibs/ietf/IPV6-MIB.dic +2028 -0
  131. data/lib/mibs/ietf/IPV6-MLD-MIB.dic +659 -0
  132. data/lib/mibs/ietf/IPV6-TCP-MIB.dic +332 -0
  133. data/lib/mibs/ietf/IPV6-UDP-MIB.dic +209 -0
  134. data/lib/mibs/ietf/ISCSI-MIB.dic +4613 -0
  135. data/lib/mibs/ietf/ISDN-MIB.dic +1796 -0
  136. data/lib/mibs/ietf/ISIS-MIB.dic +6215 -0
  137. data/lib/mibs/ietf/ISNS-MIB.dic +6578 -0
  138. data/lib/mibs/ietf/ITU-ALARM-MIB.dic +665 -0
  139. data/lib/mibs/ietf/ITU-ALARM-TC-MIB.dic +137 -0
  140. data/lib/mibs/ietf/Job-Monitoring-MIB.dic +2519 -0
  141. data/lib/mibs/ietf/L2TP-MIB.dic +4050 -0
  142. data/lib/mibs/ietf/LANGTAG-TC-MIB.dic +104 -0
  143. data/lib/mibs/ietf/LISP-MIB.dic +4067 -0
  144. data/lib/mibs/ietf/LMP-MIB.dic +5166 -0
  145. data/lib/mibs/ietf/MALLOC-MIB.dic +2156 -0
  146. data/lib/mibs/ietf/MAU-MIB.dic +2619 -0
  147. data/lib/mibs/ietf/MIDCOM-MIB.dic +2856 -0
  148. data/lib/mibs/ietf/MIOX25-MIB.dic +828 -0
  149. data/lib/mibs/ietf/MIP-MIB.dic +3473 -0
  150. data/lib/mibs/ietf/MOBILEIPV6-MIB.dic +5228 -0
  151. data/lib/mibs/ietf/MPLS-FTN-STD-MIB.dic +1594 -0
  152. data/lib/mibs/ietf/MPLS-L3VPN-STD-MIB.dic +2548 -0
  153. data/lib/mibs/ietf/MPLS-LC-ATM-STD-MIB.dic +491 -0
  154. data/lib/mibs/ietf/MPLS-LC-FR-STD-MIB.dic +395 -0
  155. data/lib/mibs/ietf/MPLS-LDP-ATM-STD-MIB.dic +1019 -0
  156. data/lib/mibs/ietf/MPLS-LDP-FRAME-RELAY-STD-MIB.dic +862 -0
  157. data/lib/mibs/ietf/MPLS-LDP-GENERIC-STD-MIB.dic +445 -0
  158. data/lib/mibs/ietf/MPLS-LDP-STD-MIB.dic +3657 -0
  159. data/lib/mibs/ietf/MPLS-LSR-STD-MIB.dic +3103 -0
  160. data/lib/mibs/ietf/MPLS-TC-STD-MIB.dic +911 -0
  161. data/lib/mibs/ietf/MPLS-TE-STD-MIB.dic +3673 -0
  162. data/lib/mibs/ietf/MSDP-MIB.dic +1893 -0
  163. data/lib/mibs/ietf/MTA-MIB.dic +1898 -0
  164. data/lib/mibs/ietf/Modem-MIB.dic +2054 -0
  165. data/lib/mibs/ietf/NAT-MIB.dic +3866 -0
  166. data/lib/mibs/ietf/NETWORK-SERVICES-MIB.dic +1034 -0
  167. data/lib/mibs/ietf/NHDP-MIB.dic +3005 -0
  168. data/lib/mibs/ietf/NHRP-MIB.dic +3660 -0
  169. data/lib/mibs/ietf/NOTIFICATION-LOG-MIB.dic +1156 -0
  170. data/lib/mibs/ietf/NTPv4-MIB.dic +1535 -0
  171. data/lib/mibs/ietf/OPT-IF-MIB.dic +8972 -0
  172. data/lib/mibs/ietf/OSPF-MIB.dic +5963 -0
  173. data/lib/mibs/ietf/OSPF-TRAP-MIB.dic +1190 -0
  174. data/lib/mibs/ietf/OSPFV3-MIB.dic +5708 -0
  175. data/lib/mibs/ietf/P-BRIDGE-MIB.dic +1499 -0
  176. data/lib/mibs/ietf/PARALLEL-MIB.dic +476 -0
  177. data/lib/mibs/ietf/PIM-MIB.dic +1393 -0
  178. data/lib/mibs/ietf/PIM-STD-MIB.dic +6819 -0
  179. data/lib/mibs/ietf/PINT-MIB.dic +830 -0
  180. data/lib/mibs/ietf/PKTC-IETF-MTA-MIB.dic +3191 -0
  181. data/lib/mibs/ietf/PKTC-IETF-SIG-MIB.dic +4713 -0
  182. data/lib/mibs/ietf/PMIPV6-MIB.dic +3010 -0
  183. data/lib/mibs/ietf/PMIPV6-TC-MIB.dic +293 -0
  184. data/lib/mibs/ietf/POLICY-BASED-MANAGEMENT-MIB.dic +3316 -0
  185. data/lib/mibs/ietf/POWER-ETHERNET-MIB.dic +959 -0
  186. data/lib/mibs/ietf/PPP-BRIDGE-NCP-MIB.dic +587 -0
  187. data/lib/mibs/ietf/PPP-IP-NCP-MIB.dic +269 -0
  188. data/lib/mibs/ietf/PPP-LCP-MIB.dic +994 -0
  189. data/lib/mibs/ietf/PPP-SEC-MIB.dic +411 -0
  190. data/lib/mibs/ietf/PSAMP-MIB.dic +998 -0
  191. data/lib/mibs/ietf/PTOPO-MIB.dic +1135 -0
  192. data/lib/mibs/ietf/PW-ATM-MIB.dic +1642 -0
  193. data/lib/mibs/ietf/PW-CEP-STD-MIB.dic +3661 -0
  194. data/lib/mibs/ietf/PW-STD-MIB.dic +3592 -0
  195. data/lib/mibs/ietf/PW-TC-STD-MIB.dic +437 -0
  196. data/lib/mibs/ietf/PW-TDM-MIB.dic +1896 -0
  197. data/lib/mibs/ietf/PerfHist-TC-MIB.dic +152 -0
  198. data/lib/mibs/ietf/Printer-MIB.dic +6665 -0
  199. data/lib/mibs/ietf/Q-BRIDGE-MIB.dic +3115 -0
  200. data/lib/mibs/ietf/RADIUS-ACC-CLIENT-MIB.dic +991 -0
  201. data/lib/mibs/ietf/RADIUS-ACC-SERVER-MIB.dic +1183 -0
  202. data/lib/mibs/ietf/RADIUS-AUTH-CLIENT-MIB.dic +1073 -0
  203. data/lib/mibs/ietf/RADIUS-AUTH-SERVER-MIB.dic +1251 -0
  204. data/lib/mibs/ietf/RADIUS-DYNAUTH-CLIENT-MIB.dic +1116 -0
  205. data/lib/mibs/ietf/RADIUS-DYNAUTH-SERVER-MIB.dic +1003 -0
  206. data/lib/mibs/ietf/RAQMON-MIB.dic +2695 -0
  207. data/lib/mibs/ietf/RBRIDGE-MIB.dic +2981 -0
  208. data/lib/mibs/ietf/RDBMS-MIB.dic +1935 -0
  209. data/lib/mibs/ietf/RFC1065-SMI.dic +108 -0
  210. data/lib/mibs/ietf/RFC1155-SMI.dic +118 -0
  211. data/lib/mibs/ietf/RFC1158-MIB.dic +2440 -0
  212. data/lib/mibs/ietf/RFC1213-MIB.dic +3434 -0
  213. data/lib/mibs/ietf/RFC1269-MIB.dic +557 -0
  214. data/lib/mibs/ietf/RFC1271-MIB.dic +4135 -0
  215. data/lib/mibs/ietf/RFC1285-MIB.dic +2842 -0
  216. data/lib/mibs/ietf/RFC1316-MIB.dic +800 -0
  217. data/lib/mibs/ietf/RFC1381-MIB.dic +1347 -0
  218. data/lib/mibs/ietf/RFC1382-MIB.dic +3820 -0
  219. data/lib/mibs/ietf/RFC1414-MIB.dic +214 -0
  220. data/lib/mibs/ietf/RIPv2-MIB.dic +773 -0
  221. data/lib/mibs/ietf/RMON-MIB.dic +5551 -0
  222. data/lib/mibs/ietf/RMON2-MIB.dic +8224 -0
  223. data/lib/mibs/ietf/ROHC-MIB.dic +1613 -0
  224. data/lib/mibs/ietf/ROHC-RTP-MIB.dic +859 -0
  225. data/lib/mibs/ietf/ROHC-UNCOMPRESSED-MIB.dic +267 -0
  226. data/lib/mibs/ietf/RPKI-ROUTER-MIB.dic +1363 -0
  227. data/lib/mibs/ietf/RS-232-MIB.dic +1335 -0
  228. data/lib/mibs/ietf/RSERPOOL-MIB.dic +2501 -0
  229. data/lib/mibs/ietf/RSTP-MIB.dic +427 -0
  230. data/lib/mibs/ietf/RSVP-MIB.dic +4135 -0
  231. data/lib/mibs/ietf/RTP-MIB.dic +1376 -0
  232. data/lib/mibs/ietf/SCSI-MIB.dic +3804 -0
  233. data/lib/mibs/ietf/SCTP-MIB.dic +1924 -0
  234. data/lib/mibs/ietf/SFLOW-MIB.dic +568 -0
  235. data/lib/mibs/ietf/SIP-COMMON-MIB.dic +2769 -0
  236. data/lib/mibs/ietf/SIP-MIB.dic +1438 -0
  237. data/lib/mibs/ietf/SIP-SERVER-MIB.dic +1150 -0
  238. data/lib/mibs/ietf/SIP-TC-MIB.dic +257 -0
  239. data/lib/mibs/ietf/SIP-UA-MIB.dic +268 -0
  240. data/lib/mibs/ietf/SLAPM-MIB.dic +4527 -0
  241. data/lib/mibs/ietf/SMON-MIB.dic +1758 -0
  242. data/lib/mibs/ietf/SNA-NAU-MIB.dic +4042 -0
  243. data/lib/mibs/ietf/SNA-SDLC-MIB.dic +3858 -0
  244. data/lib/mibs/ietf/SNMP-COMMUNITY-MIB.dic +715 -0
  245. data/lib/mibs/ietf/SNMP-FRAMEWORK-MIB.dic +709 -0
  246. data/lib/mibs/ietf/SNMP-MPD-MIB.dic +230 -0
  247. data/lib/mibs/ietf/SNMP-NOTIFICATION-MIB.dic +859 -0
  248. data/lib/mibs/ietf/SNMP-PROXY-MIB.dic +414 -0
  249. data/lib/mibs/ietf/SNMP-REPEATER-MIB.dic +4335 -0
  250. data/lib/mibs/ietf/SNMP-SSH-TM-MIB.dic +447 -0
  251. data/lib/mibs/ietf/SNMP-TARGET-MIB.dic +924 -0
  252. data/lib/mibs/ietf/SNMP-TLS-TM-MIB.dic +1449 -0
  253. data/lib/mibs/ietf/SNMP-TSM-MIB.dic +315 -0
  254. data/lib/mibs/ietf/SNMP-USER-BASED-SM-MIB.dic +1164 -0
  255. data/lib/mibs/ietf/SNMP-USM-AES-MIB.dic +95 -0
  256. data/lib/mibs/ietf/SNMP-USM-DH-OBJECTS-MIB.dic +653 -0
  257. data/lib/mibs/ietf/SNMP-VIEW-BASED-ACM-MIB.dic +1202 -0
  258. data/lib/mibs/ietf/SNMPv2-MIB.dic +1382 -0
  259. data/lib/mibs/ietf/SNMPv2-SMI.dic +223 -0
  260. data/lib/mibs/ietf/SNMPv2-USEC-MIB.dic +405 -0
  261. data/lib/mibs/ietf/SONET-MIB.dic +3308 -0
  262. data/lib/mibs/ietf/SOURCE-ROUTING-MIB.dic +542 -0
  263. data/lib/mibs/ietf/SSPM-MIB.dic +1530 -0
  264. data/lib/mibs/ietf/SYSAPPL-MIB.dic +2092 -0
  265. data/lib/mibs/ietf/T11-FC-FABRIC-ADDR-MGR-MIB.dic +1779 -0
  266. data/lib/mibs/ietf/T11-FC-FABRIC-CONFIG-SERVER-MIB.dic +2822 -0
  267. data/lib/mibs/ietf/T11-FC-FABRIC-LOCK-MIB.dic +700 -0
  268. data/lib/mibs/ietf/T11-FC-FSPF-MIB.dic +1889 -0
  269. data/lib/mibs/ietf/T11-FC-NAME-SERVER-MIB.dic +1775 -0
  270. data/lib/mibs/ietf/T11-FC-ROUTE-MIB.dic +655 -0
  271. data/lib/mibs/ietf/T11-FC-RSCN-MIB.dic +1110 -0
  272. data/lib/mibs/ietf/T11-FC-VIRTUAL-FABRIC-MIB.dic +770 -0
  273. data/lib/mibs/ietf/T11-FC-ZONE-SERVER-MIB.dic +3886 -0
  274. data/lib/mibs/ietf/T11-TC-MIB.dic +110 -0
  275. data/lib/mibs/ietf/TCP-ESTATS-MIB.dic +3926 -0
  276. data/lib/mibs/ietf/TCP-MIB.dic +1319 -0
  277. data/lib/mibs/ietf/TCPIPX-MIB.dic +457 -0
  278. data/lib/mibs/ietf/TE-LINK-STD-MIB.dic +2876 -0
  279. data/lib/mibs/ietf/TE-MIB.dic +2924 -0
  280. data/lib/mibs/ietf/TED-MIB.dic +1749 -0
  281. data/lib/mibs/ietf/TIME-AGGREGATE-MIB.dic +550 -0
  282. data/lib/mibs/ietf/TN3270E-MIB.dic +2785 -0
  283. data/lib/mibs/ietf/TN3270E-RT-MIB.dic +1317 -0
  284. data/lib/mibs/ietf/TOKEN-RING-RMON-MIB.dic +2820 -0
  285. data/lib/mibs/ietf/TOKENRING-MIB.dic +1184 -0
  286. data/lib/mibs/ietf/TOKENRING-STATION-SR-MIB.dic +292 -0
  287. data/lib/mibs/ietf/TRANSPORT-ADDRESS-MIB.dic +610 -0
  288. data/lib/mibs/ietf/TRIP-MIB.dic +3159 -0
  289. data/lib/mibs/ietf/TRIP-TC-MIB.dic +241 -0
  290. data/lib/mibs/ietf/TUNNEL-MIB.dic +1095 -0
  291. data/lib/mibs/ietf/UDP-MIB.dic +751 -0
  292. data/lib/mibs/ietf/UDPLITE-MIB.dic +704 -0
  293. data/lib/mibs/ietf/UPS-MIB.dic +3088 -0
  294. data/lib/mibs/ietf/URI-TC-MIB.dic +193 -0
  295. data/lib/mibs/ietf/UUID-TC-MIB.dic +135 -0
  296. data/lib/mibs/ietf/VDSL-LINE-EXT-MCM-MIB.dic +989 -0
  297. data/lib/mibs/ietf/VDSL-LINE-EXT-SCM-MIB.dic +605 -0
  298. data/lib/mibs/ietf/VDSL-LINE-MIB.dic +4518 -0
  299. data/lib/mibs/ietf/VDSL2-LINE-MIB.dic +11029 -0
  300. data/lib/mibs/ietf/VDSL2-LINE-TC-MIB.dic +3152 -0
  301. data/lib/mibs/ietf/VPN-TC-STD-MIB.dic +121 -0
  302. data/lib/mibs/ietf/VRRP-MIB.dic +1163 -0
  303. data/lib/mibs/ietf/VRRPV3-MIB.dic +1403 -0
  304. data/lib/mibs/ietf/WWW-MIB.dic +1810 -0
  305. data/lib/mibs/logstash/iso.dic +18 -0
  306. data/logstash-input-snmp.gemspec +1 -1
  307. data/spec/inputs/snmp/mib_spec.rb +10 -17
  308. data/spec/inputs/snmp_spec.rb +27 -1
  309. metadata +302 -2
@@ -0,0 +1,2870 @@
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 APM-MIB
6
+
7
+ FILENAME = "./libsmi-0.5.0/mibs/ietf/APM-MIB"
8
+
9
+ MIB = {
10
+ "moduleName" : "APM-MIB",
11
+
12
+ "APM-MIB" : {
13
+ "nodetype" : "module",
14
+ "language" : "SMIv2",
15
+ "organization" :
16
+ """IETF RMON MIB Working Group""",
17
+ "contact" :
18
+ """Author:
19
+ Steve Waldbusser
20
+
21
+
22
+
23
+ Phone: +1-650-948-6500
24
+ Fax : +1-650-745-0671
25
+ Email: waldbusser@nextbeacon.com
26
+
27
+ Working Group Chair:
28
+ Andy Bierman
29
+ Cisco Systems, Inc.
30
+ Postal: 170 West Tasman Drive
31
+ San Jose, CA USA 95134
32
+ Tel: +1 408 527-3711
33
+ E-mail: abierman@cisco.com
34
+
35
+ Working Group Mailing List: <rmonmib@ietf.org>
36
+ To subscribe send email to: <rmonmib-request@ietf.org>""",
37
+ "description" :
38
+ """The MIB module for measuring application performance
39
+ as experienced by end-users.
40
+
41
+ Copyright (C) The Internet Society (2004). This version of
42
+ this MIB module is part of RFC 3729; see the RFC itself for
43
+ full legal notices.""",
44
+ "revisions" : (
45
+ {
46
+ "date" : "2004-02-19 00:00",
47
+ "description" :
48
+ """The original version of this MIB Module, published as
49
+ RFC3729.""",
50
+ },
51
+ ),
52
+ "identity node" : "apm",
53
+ },
54
+
55
+ "imports" : (
56
+ {"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
57
+ {"module" : "SNMPv2-SMI", "name" : "OBJECT-TYPE"},
58
+ {"module" : "SNMPv2-SMI", "name" : "NOTIFICATION-TYPE"},
59
+ {"module" : "SNMPv2-SMI", "name" : "Counter32"},
60
+ {"module" : "SNMPv2-SMI", "name" : "Unsigned32"},
61
+ {"module" : "SNMPv2-TC", "name" : "TEXTUAL-CONVENTION"},
62
+ {"module" : "SNMPv2-TC", "name" : "RowStatus"},
63
+ {"module" : "SNMPv2-TC", "name" : "TimeStamp"},
64
+ {"module" : "SNMPv2-TC", "name" : "TimeInterval"},
65
+ {"module" : "SNMPv2-TC", "name" : "TruthValue"},
66
+ {"module" : "SNMPv2-TC", "name" : "DateAndTime"},
67
+ {"module" : "SNMPv2-TC", "name" : "StorageType"},
68
+ {"module" : "SNMPv2-CONF", "name" : "MODULE-COMPLIANCE"},
69
+ {"module" : "SNMPv2-CONF", "name" : "OBJECT-GROUP"},
70
+ {"module" : "SNMPv2-CONF", "name" : "NOTIFICATION-GROUP"},
71
+ {"module" : "SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
72
+ {"module" : "RMON-MIB", "name" : "rmon"},
73
+ {"module" : "RMON-MIB", "name" : "OwnerString"},
74
+ {"module" : "RMON2-MIB", "name" : "protocolDirLocalIndex"},
75
+ ),
76
+
77
+ "typedefs" : {
78
+ "AppLocalIndex" : {
79
+ "basetype" : "Unsigned32",
80
+ "status" : "current",
81
+ "ranges" : [
82
+ {
83
+ "min" : "1",
84
+ "max" : "2147483647"
85
+ },
86
+ ],
87
+ "range" : {
88
+ "min" : "1",
89
+ "max" : "2147483647"
90
+ },
91
+ "description" :
92
+ """A locally arbitrary unique identifier associated with an
93
+ application or application verb.
94
+
95
+ All objects of type AppLocalIndex are assigned by the agent
96
+ out of a common number space. In other words, AppLocalIndex
97
+ values assigned to entries in one table must not overlap with
98
+ AppLocalIndex values assigned to entries in another
99
+ table. Further, every protocolDirLocalIndex value registered
100
+ by the agent automatically assigns the same value out of the
101
+
102
+
103
+
104
+ AppLocalIndex number space.
105
+
106
+ For example, if the protocolDirLocalIndex values { 1, 3, 5, 7 }
107
+ have been assigned, and the apmHttpFilterAppLocalIndex values
108
+ { 6, 8, 9 } have been assigned:
109
+
110
+ - Assignment of new AppLocalIndex values must not use the
111
+ values { 1, 3, 5, 6, 7, 8, 9 }.
112
+ - AppLocalIndex values { 1, 3, 5, 7 } are automatically
113
+ assigned and are associated with the identical value of
114
+ protocolDirLocalIndex. In particular, an entry in the
115
+ apmAppDirTable indexed by a value provides further
116
+ information about a protocol indexed by the same value
117
+ in the protocolDirTable of RMON2.
118
+
119
+ The value for each supported application must remain constant
120
+ at least from one re-initialization of the entity's network
121
+ management system to the next re-initialization, except that
122
+ if an application is deleted and re-created, it must be
123
+ re-created with a new value that has not been used since the
124
+ last re-initialization.
125
+
126
+ The specific value is meaningful only within a given SNMP
127
+ entity. An AppLocalIndex value must not be re-used until the
128
+ next agent restart.""",
129
+ },
130
+ "ProtocolDirNetworkAddress" : {
131
+ "basetype" : "OctetString",
132
+ "status" : "current",
133
+ "ranges" : [
134
+ {
135
+ "min" : "0",
136
+ "max" : "255"
137
+ },
138
+ ],
139
+ "range" : {
140
+ "min" : "0",
141
+ "max" : "255"
142
+ },
143
+ "description" :
144
+ """A network level address whose semantics and encoding are
145
+ specified by an associated protocolDirLocalIndex
146
+ value. Objects of this type must specify which
147
+ protocolDirLocalIndex value is used. This value is encoded
148
+ according to the encoding rules for the identified
149
+ protocolDirectory entry.
150
+
151
+ For example, if the associated protocolDirLocalIndex indicates
152
+ an encapsulation of ip, this object is encoded as a length
153
+ octet of 4, followed by the 4 octets of the ip address,
154
+ in network byte order.
155
+
156
+ Objects of this type may allow this value to be the zero
157
+ length string. If so, they must identify they meaning of this
158
+ value.""",
159
+ },
160
+ "DataSourceOrZero" : {
161
+ "basetype" : "ObjectIdentifier",
162
+ "status" : "current",
163
+ "description" :
164
+ """Identifies the source of the data that the associated
165
+ function is configured to analyze. This source can be any
166
+ interface on this device.
167
+
168
+ In order to identify a particular interface, this
169
+ object shall identify the instance of the ifIndex
170
+ object, defined in [4], for the desired interface.
171
+
172
+ For example, if an entry were to receive data from
173
+ interface #1, this object would be set to ifIndex.1.
174
+
175
+ If the source of the data isn't an interface or cannot be
176
+ localized to an interface, this object would be set to 0.0""",
177
+ "reference" :
178
+ """The DataSource textual convention is defined in
179
+ RFC 2021 [5].""",
180
+ },
181
+ "RmonClientID" : {
182
+ "basetype" : "Unsigned32",
183
+ "status" : "current",
184
+ "ranges" : [
185
+ {
186
+ "min" : "0",
187
+ "max" : "4294967295"
188
+ },
189
+ ],
190
+ "range" : {
191
+ "min" : "0",
192
+ "max" : "4294967295"
193
+ },
194
+ "description" :
195
+ """A long-lived unique ID assigned to an end-system. This ID is
196
+ assigned by the agent using an implementation-specific
197
+ algorithm.
198
+
199
+ Because a client machine may be assigned multiple addresses
200
+ over any time period it can be difficult to attribute
201
+ behavior to a particular client based solely on its
202
+ address. A ClientID may be assigned to provide a more
203
+ stable handle for referencing that client. The entity that
204
+ assigns the ClientID may use various implementation
205
+ techniques to keep track of a client but if the assigning
206
+ entity is unable to track client address mappings, it may map
207
+ client identifiers to client addresses rather than to
208
+ distinct client machines.
209
+
210
+ This is named ClientID because it helps to solve a problem
211
+ seen in network clients (servers usually have well-known,
212
+ long-lived addresses). However, ClientID's may be assigned to
213
+ any end-system regardless of its role on the network.""",
214
+ },
215
+ "TransactionAggregationType" : {
216
+ "basetype" : "Enumeration",
217
+ "status" : "current",
218
+ "flows" : {
219
+ "nodetype" : "namednumber",
220
+ "number" : "1"
221
+ },
222
+ "clients" : {
223
+ "nodetype" : "namednumber",
224
+ "number" : "2"
225
+ },
226
+ "servers" : {
227
+ "nodetype" : "namednumber",
228
+ "number" : "3"
229
+ },
230
+ "applications" : {
231
+ "nodetype" : "namednumber",
232
+ "number" : "4"
233
+ },
234
+ "description" :
235
+ """Specifies one of 4 different techniques for aggregating
236
+ transactions.
237
+
238
+ The metrics for a single transaction are the responsiveness of
239
+ the transaction and whether the transaction succeeded (a
240
+ boolean). When such metrics are aggregated in this MIB Module,
241
+ these metrics are replaced by averages and distributions of
242
+ responsiveness and availability. The metrics describing
243
+ aggregates are constant no matter which type of aggregation is
244
+ being performed. These metrics may be found in the
245
+ apmReportTable.
246
+
247
+ The flows(1) aggregation is the simplest. All transactions
248
+ that share common application/server/client 3-tuples are
249
+ aggregated together, resulting in a set of metrics for all
250
+ such unique 3-tuples.
251
+
252
+ The clients(2) aggregation results in somewhat more
253
+ aggregation (i.e., fewer resulting records). All transactions
254
+ that share common application/client tuples are aggregated
255
+ together, resulting in a set of metrics for all such unique
256
+ tuples.
257
+
258
+ The servers(3) aggregation usually results in still more
259
+ aggregation (i.e., fewer resulting records). All transactions
260
+ that share common application/server tuples are aggregated
261
+ together, resulting in a set of metrics for all such unique
262
+ tuples.
263
+
264
+ The applications(4) aggregation results in the most
265
+ aggregation (i.e., the fewest resulting records). All
266
+ transactions that share a common application are aggregated
267
+ together, resulting in a set of metrics for all such unique
268
+ applications.
269
+
270
+ Note that it is not meaningful to aggregate applications, as
271
+ different applications have widely varying characteristics. As a
272
+ result, this set of aggregations is complete.""",
273
+ },
274
+ }, # typedefs
275
+
276
+ "nodes" : {
277
+ "apm" : {
278
+ "nodetype" : "node",
279
+ "moduleName" : "APM-MIB",
280
+ "oid" : "1.3.6.1.2.1.16.23",
281
+ "status" : "current",
282
+ }, # node
283
+ "apmNotifications" : {
284
+ "nodetype" : "node",
285
+ "moduleName" : "APM-MIB",
286
+ "oid" : "1.3.6.1.2.1.16.23.0",
287
+ }, # node
288
+ "apmMibObjects" : {
289
+ "nodetype" : "node",
290
+ "moduleName" : "APM-MIB",
291
+ "oid" : "1.3.6.1.2.1.16.23.1",
292
+ }, # node
293
+ "apmAppDirTable" : {
294
+ "nodetype" : "table",
295
+ "moduleName" : "APM-MIB",
296
+ "oid" : "1.3.6.1.2.1.16.23.1.1",
297
+ "status" : "current",
298
+ "description" :
299
+ """The APM MIB directory of applications and application
300
+ verbs. The agent will populate this table with all
301
+ applications/verbs of any responsivenessType it has the
302
+ capability to monitor. Since the agent populates this table
303
+ with every entry it has the capability to monitor, the
304
+ entries in this table are read-write, allowing the management
305
+ station to modify parameters in this table but not to add new
306
+ entries or delete entries (however, entries may be
307
+ disabled). If new entries are added to the apmHttpFilterTable
308
+ or the apmUserDefinedAppTable, the agent will add the
309
+ corresponding entries to this table.
310
+
311
+ It is an implementation-dependent matter as to how the agent
312
+ sets these default parameters. For example, it may leave
313
+ certain entries in this table 'off(0)' if the agent developer
314
+
315
+
316
+
317
+ believes that combination will be infrequently used, allowing
318
+ a manager that needs that capability to set it to 'on(1)'.
319
+
320
+ Some applications are registered in the RMON2 protocol
321
+ directory and some are registered in other tables in this
322
+ MIB Module. Regardless of where an application is originally
323
+ registered, it is assigned an AppLocalIndex value that is the
324
+ primary index for this table.
325
+
326
+ The contents of this table affect all reports and exceptions
327
+ generated by this agent. Accordingly, modification of this
328
+ table should be performed by a manager acting in the role of
329
+ administrator. In particular, management software should not
330
+ require or enforce particular configuration of this table - it
331
+ should reflect the preferences of the site administrator, not
332
+ the software author. As a practical matter, this requires
333
+ management software to allow the administrator to configure
334
+ the values it will use so that it can be adapted to the site
335
+ policy.""",
336
+ }, # table
337
+ "apmAppDirEntry" : {
338
+ "nodetype" : "row",
339
+ "moduleName" : "APM-MIB",
340
+ "oid" : "1.3.6.1.2.1.16.23.1.1.1",
341
+ "status" : "current",
342
+ "linkage" : [
343
+ "apmAppDirAppLocalIndex",
344
+ "apmAppDirResponsivenessType",
345
+ ],
346
+ "description" :
347
+ """The APM MIB directory of applications and application
348
+ verbs. An entry will exist in this table for all applications
349
+ for which application performance measurement is supported.""",
350
+ }, # row
351
+ "apmAppDirAppLocalIndex" : {
352
+ "nodetype" : "column",
353
+ "moduleName" : "APM-MIB",
354
+ "oid" : "1.3.6.1.2.1.16.23.1.1.1.1",
355
+ "status" : "current",
356
+ "syntax" : {
357
+ "type" : { "module" :"APM-MIB", "name" : "AppLocalIndex"},
358
+ },
359
+ "access" : "noaccess",
360
+ "description" :
361
+ """The AppLocalIndex assigned for this application Directory
362
+ entry.""",
363
+ }, # column
364
+ "apmAppDirResponsivenessType" : {
365
+ "nodetype" : "column",
366
+ "moduleName" : "APM-MIB",
367
+ "oid" : "1.3.6.1.2.1.16.23.1.1.1.2",
368
+ "status" : "current",
369
+ "syntax" : {
370
+ "type" : {
371
+ "basetype" : "Enumeration",
372
+ "transactionOriented" : {
373
+ "nodetype" : "namednumber",
374
+ "number" : "1"
375
+ },
376
+ "throughputOriented" : {
377
+ "nodetype" : "namednumber",
378
+ "number" : "2"
379
+ },
380
+ "streamingOriented" : {
381
+ "nodetype" : "namednumber",
382
+ "number" : "3"
383
+ },
384
+ },
385
+ },
386
+ "access" : "noaccess",
387
+ "description" :
388
+ """This object describes and configures the agent's support for
389
+ application performance measurement for this application.
390
+ There are 3 types of measurements for different types of
391
+ applications:
392
+
393
+ Transaction-Oriented applications have a fairly constant
394
+ workload to perform for all transactions. The responsiveness
395
+ metric for transaction-oriented applications is application
396
+ response time (from first request to final delivery of
397
+ service) and is measured in milliseconds. This is
398
+ commonly referred to as end-user response time.
399
+
400
+ Throughput-Oriented applications have widely varying workloads
401
+ based on the nature of the client request. In particular,
402
+ throughput-oriented applications vary widely in the amount of
403
+ data that must be transported to satisfy the request. The
404
+ responsiveness metric for throughput-oriented applications is
405
+ kilobits per second.
406
+
407
+ Streaming-Oriented applications deliver data at a constant
408
+ metered rate of speed regardless of the responsiveness of the
409
+ networking and computing infrastructure. This constant rate of
410
+ speed is generally specified to be below (sometimes well
411
+ below) the nominal capability of the infrastructure. However,
412
+ when the infrastructures cannot deliver data at this speed,
413
+ interruption of service or degradation of service can
414
+ result. The responsiveness metric for streaming-oriented
415
+ applications is the ratio of time that the service is degraded
416
+ or interrupted to the total service time. This metric is
417
+ measured in parts per million.
418
+
419
+ Note that for some applications, measuring more than one
420
+ responsiveness type may be interesting. For agents that wish
421
+
422
+
423
+
424
+ to support more than one measurement for a application, they
425
+ will populate this table with multiple entries for that
426
+ application, one for each type.""",
427
+ }, # column
428
+ "apmAppDirConfig" : {
429
+ "nodetype" : "column",
430
+ "moduleName" : "APM-MIB",
431
+ "oid" : "1.3.6.1.2.1.16.23.1.1.1.3",
432
+ "status" : "current",
433
+ "syntax" : {
434
+ "type" : {
435
+ "basetype" : "Enumeration",
436
+ "off" : {
437
+ "nodetype" : "namednumber",
438
+ "number" : "1"
439
+ },
440
+ "on" : {
441
+ "nodetype" : "namednumber",
442
+ "number" : "2"
443
+ },
444
+ },
445
+ },
446
+ "access" : "readwrite",
447
+ "description" :
448
+ """This object describes and configures support for application
449
+ performance measurement for this application.
450
+
451
+ If the value of this object is on(2), the agent supports
452
+ measurement of application performance metrics for this
453
+ application and is configured to measure such metrics for all
454
+ APM MIB functions and all interfaces. If the value of this
455
+ object is off(1), the agent supports measurement of
456
+ application performance for this application but is configured
457
+ to not measure these metrics for any APM MIB functions or
458
+ interfaces. Whenever this value changes from on(2) to off(1),
459
+ the agent shall delete all related entries in all tables in
460
+ this MIB Module.
461
+
462
+ The value of this object must persist across reboots.""",
463
+ }, # column
464
+ "apmAppDirResponsivenessBoundary1" : {
465
+ "nodetype" : "column",
466
+ "moduleName" : "APM-MIB",
467
+ "oid" : "1.3.6.1.2.1.16.23.1.1.1.4",
468
+ "status" : "current",
469
+ "syntax" : {
470
+ "type" : { "module" :"", "name" : "Unsigned32"},
471
+ },
472
+ "access" : "readwrite",
473
+ "description" :
474
+ """The boundary value between bucket1 and bucket 2. If this
475
+ value is modified, all entries in the apmReportTable must be
476
+ deleted by the agent.
477
+
478
+ The value of this object must persist across reboots.""",
479
+ }, # column
480
+ "apmAppDirResponsivenessBoundary2" : {
481
+ "nodetype" : "column",
482
+ "moduleName" : "APM-MIB",
483
+ "oid" : "1.3.6.1.2.1.16.23.1.1.1.5",
484
+ "status" : "current",
485
+ "syntax" : {
486
+ "type" : { "module" :"", "name" : "Unsigned32"},
487
+ },
488
+ "access" : "readwrite",
489
+ "description" :
490
+ """The boundary value between bucket2 and bucket 3. If this
491
+
492
+
493
+
494
+ value is modified, all entries in the apmReportTable must be
495
+ deleted by the agent.
496
+
497
+ The value of this object must persist across reboots.""",
498
+ }, # column
499
+ "apmAppDirResponsivenessBoundary3" : {
500
+ "nodetype" : "column",
501
+ "moduleName" : "APM-MIB",
502
+ "oid" : "1.3.6.1.2.1.16.23.1.1.1.6",
503
+ "status" : "current",
504
+ "syntax" : {
505
+ "type" : { "module" :"", "name" : "Unsigned32"},
506
+ },
507
+ "access" : "readwrite",
508
+ "description" :
509
+ """The boundary value between bucket3 and bucket 4. If this
510
+ value is modified, all entries in the apmReportTable must be
511
+ deleted by the agent.
512
+
513
+ The value of this object must persist across reboots.""",
514
+ }, # column
515
+ "apmAppDirResponsivenessBoundary4" : {
516
+ "nodetype" : "column",
517
+ "moduleName" : "APM-MIB",
518
+ "oid" : "1.3.6.1.2.1.16.23.1.1.1.7",
519
+ "status" : "current",
520
+ "syntax" : {
521
+ "type" : { "module" :"", "name" : "Unsigned32"},
522
+ },
523
+ "access" : "readwrite",
524
+ "description" :
525
+ """The boundary value between bucket4 and bucket 5. If this
526
+ value is modified, all entries in the apmReportTable must be
527
+ deleted by the agent.
528
+
529
+ The value of this object must persist across reboots.""",
530
+ }, # column
531
+ "apmAppDirResponsivenessBoundary5" : {
532
+ "nodetype" : "column",
533
+ "moduleName" : "APM-MIB",
534
+ "oid" : "1.3.6.1.2.1.16.23.1.1.1.8",
535
+ "status" : "current",
536
+ "syntax" : {
537
+ "type" : { "module" :"", "name" : "Unsigned32"},
538
+ },
539
+ "access" : "readwrite",
540
+ "description" :
541
+ """The boundary value between bucket5 and bucket 6. If this
542
+ value is modified, all entries in the apmReportTable must be
543
+ deleted by the agent.
544
+
545
+ The value of this object must persist across reboots.""",
546
+ }, # column
547
+ "apmAppDirResponsivenessBoundary6" : {
548
+ "nodetype" : "column",
549
+ "moduleName" : "APM-MIB",
550
+ "oid" : "1.3.6.1.2.1.16.23.1.1.1.9",
551
+ "status" : "current",
552
+ "syntax" : {
553
+ "type" : { "module" :"", "name" : "Unsigned32"},
554
+ },
555
+ "access" : "readwrite",
556
+ "description" :
557
+ """The boundary value between bucket6 and bucket 7. If this
558
+
559
+
560
+
561
+ value is modified, all entries in the apmReportTable must be
562
+ deleted by the agent.
563
+
564
+ The value of this object must persist across reboots.""",
565
+ }, # column
566
+ "apmBucketBoundaryLastChange" : {
567
+ "nodetype" : "scalar",
568
+ "moduleName" : "APM-MIB",
569
+ "oid" : "1.3.6.1.2.1.16.23.1.2",
570
+ "status" : "current",
571
+ "syntax" : {
572
+ "type" : { "module" :"SNMPv2-TC", "name" : "TimeStamp"},
573
+ },
574
+ "access" : "readonly",
575
+ "description" :
576
+ """The value of sysUpTime the last time that any bucket boundary
577
+ in any appDirEntry was changed. This object can help to
578
+ determine if two managers are both trying to enforce different
579
+ configurations of this table.""",
580
+ }, # scalar
581
+ "apmAppDirID" : {
582
+ "nodetype" : "scalar",
583
+ "moduleName" : "APM-MIB",
584
+ "oid" : "1.3.6.1.2.1.16.23.1.3",
585
+ "status" : "current",
586
+ "syntax" : {
587
+ "type" : { "module" :"", "name" : "ObjectIdentifier"},
588
+ },
589
+ "access" : "readwrite",
590
+ "description" :
591
+ """This object allows managers to avoid downloading application
592
+ directory information when the directory is set to a known
593
+ (usually fixed) configuration.
594
+
595
+ If the value of this object isn't 0.0, it signifies
596
+ that the entire contents of the apmAppDirTable,
597
+ apmHttpFilterTable, apmUserDefinedAppTable and
598
+ protocolDirTable are equal to a known state identified
599
+ by the value of this object. If a manager recognizes this
600
+ value as identifying a directory configuration it has a local
601
+ copy of, it may use this local copy rather than downloading
602
+ these tables. Note that it may have downloaded this local copy
603
+ (and the ID) from another agent and used this copy for all
604
+ other agents that advertised the same ID.
605
+
606
+ If an agent recognizes that the entire contents of the
607
+ apmAppDirTable, apmHttpFilterTable,
608
+ apmUserDefinedAppTable and protocolDirTable are equal to
609
+ a known state to which an ID has been assigned, it should set
610
+ this object to that ID.
611
+
612
+ In many cases when this feature is used, the application
613
+ directory information will be in read-only memory and thus the
614
+ tables may not be modified via SNMP requests. In the event
615
+
616
+
617
+
618
+ that the tables are writable and a modification is made, the
619
+ agent is responsible for setting this object to 0.0 if it
620
+ cannot determine that the state is equal to a known state.
621
+
622
+ An agent is not obligated to recognize and advertise all such
623
+ registered states as it may not have knowledge of all states.
624
+ Thus, a manager may encounter agents whose DirectoryID value
625
+ is 0.0 even though the contents of the directory were equal to
626
+ a registered state.
627
+
628
+ Note that the contents of those tables includes the
629
+ protocolDirLocalIndex and appLocalIndex values. In other
630
+ words, these values can't be assigned randomly on each agent,
631
+ but must be equal to values that are part of the known
632
+ state. While it is possible for a manager to download
633
+ application directory details using SNMP and to set the
634
+ appropriate directoryID, the manager would need to have some
635
+ scheme to ensure consistent values of LocalIndex variables
636
+ from agent to agent. Such schemes are outside the scope of
637
+ this specification.
638
+
639
+ Application directory registrations are unique within an
640
+ administrative domain.
641
+
642
+ Typically these registrations will be made by an agent
643
+ software developer who will set the application directory
644
+ tables to a read-only state and assign a DirectoryID to that
645
+ state. Thus, all agents running this software would share the
646
+ same DirectoryID. As the application directory might change
647
+ from one software release to the next, the developer may
648
+ register different DirectoryID's for each software release.
649
+
650
+ A customer could also create a site-wide application directory
651
+ configuration and assign a DirectoryID to that configuration
652
+ as long as consistent values of LocalIndex variables can be
653
+ ensured.
654
+
655
+ The value of this object must persist across reboots.""",
656
+ }, # scalar
657
+ "apmHttpFilterTable" : {
658
+ "nodetype" : "table",
659
+ "moduleName" : "APM-MIB",
660
+ "oid" : "1.3.6.1.2.1.16.23.1.4",
661
+ "status" : "current",
662
+ "description" :
663
+ """A table that creates virtual applications which measure the
664
+ performance of certain web pages or sets of web pages.
665
+
666
+ When an entry is added to this table, the agent will
667
+ automatically create one or more entries in the
668
+ apmAppDirTable (one for each responsivenessType it is
669
+ capable of measuring).
670
+
671
+ Note that when entries exist in this table some HTTP
672
+ transactions will be summarized twice: in applications
673
+ represented here as well as the HTTP application. If entries
674
+ in this table overlap, these transactions may be summarized
675
+ additional times.
676
+
677
+ The contents of this table affect all reports and exceptions
678
+ generated by this agent. Accordingly, modification of this
679
+ table should be performed by a manager acting in the role of
680
+ administrator. In particular, management software should not
681
+ require or enforce particular configuration of this table - it
682
+ should reflect the preferences of the site administrator, not
683
+ the software author.""",
684
+ }, # table
685
+ "apmHttpFilterEntry" : {
686
+ "nodetype" : "row",
687
+ "moduleName" : "APM-MIB",
688
+ "oid" : "1.3.6.1.2.1.16.23.1.4.1",
689
+ "create" : "true",
690
+ "status" : "current",
691
+ "linkage" : [
692
+ "apmHttpFilterIndex",
693
+ ],
694
+ "description" :
695
+ """A virtual application which measure the performance of certain
696
+ web pages or sets of web pages.""",
697
+ }, # row
698
+ "apmHttpFilterIndex" : {
699
+ "nodetype" : "column",
700
+ "moduleName" : "APM-MIB",
701
+ "oid" : "1.3.6.1.2.1.16.23.1.4.1.1",
702
+ "status" : "current",
703
+ "syntax" : {
704
+ "type" : {
705
+ "basetype" : "Unsigned32",
706
+ "ranges" : [
707
+ {
708
+ "min" : "0",
709
+ "max" : "65535"
710
+ },
711
+ ],
712
+ "range" : {
713
+ "min" : "0",
714
+ "max" : "65535"
715
+ },
716
+ },
717
+ },
718
+ "access" : "noaccess",
719
+ "description" :
720
+ """An index that uniquely identifies an entry in the
721
+ apmHttpFilterTable.""",
722
+ }, # column
723
+ "apmHttpFilterAppLocalIndex" : {
724
+ "nodetype" : "column",
725
+ "moduleName" : "APM-MIB",
726
+ "oid" : "1.3.6.1.2.1.16.23.1.4.1.2",
727
+ "status" : "current",
728
+ "syntax" : {
729
+ "type" : { "module" :"APM-MIB", "name" : "AppLocalIndex"},
730
+ },
731
+ "access" : "readonly",
732
+ "description" :
733
+ """The AppLocalIndex that represents HTTP transactions
734
+ that match this entry.
735
+
736
+ This object is read-only. A value is created by the agent from
737
+ an unused AppLocalIndex value when this apmHttpFilterEntry is
738
+ created.""",
739
+ }, # column
740
+ "apmHttpFilterServerProtocol" : {
741
+ "nodetype" : "column",
742
+ "moduleName" : "APM-MIB",
743
+ "oid" : "1.3.6.1.2.1.16.23.1.4.1.3",
744
+ "status" : "current",
745
+ "syntax" : {
746
+ "type" : {
747
+ "basetype" : "Unsigned32",
748
+ "ranges" : [
749
+ {
750
+ "min" : "1",
751
+ "max" : "2147483647"
752
+ },
753
+ ],
754
+ "range" : {
755
+ "min" : "1",
756
+ "max" : "2147483647"
757
+ },
758
+ },
759
+ },
760
+ "access" : "readwrite",
761
+ "description" :
762
+ """The protocolDirLocalIndex value of the network level protocol
763
+ of the apmHttpFilterServerAddress.""",
764
+ }, # column
765
+ "apmHttpFilterServerAddress" : {
766
+ "nodetype" : "column",
767
+ "moduleName" : "APM-MIB",
768
+ "oid" : "1.3.6.1.2.1.16.23.1.4.1.4",
769
+ "status" : "current",
770
+ "syntax" : {
771
+ "type" : { "module" :"APM-MIB", "name" : "ProtocolDirNetworkAddress"},
772
+ },
773
+ "access" : "readwrite",
774
+ "description" :
775
+ """This entry will only represent transactions coming from the
776
+ network address specified in this object.
777
+
778
+
779
+
780
+
781
+ This is represented as an octet string with
782
+ specific semantics and length as identified
783
+ by the associated apmHttpFilterServerProtocol object.
784
+
785
+ If this object is the zero-length string, then this entry will
786
+ match one of the addresses represented by the 'host' component
787
+ of the associated apmHttpFilterURLPath object, where the
788
+ format if a URL [9] is
789
+ http://<host>:<port>/<path>?<searchpart>.""",
790
+ }, # column
791
+ "apmHttpFilterURLPath" : {
792
+ "nodetype" : "column",
793
+ "moduleName" : "APM-MIB",
794
+ "oid" : "1.3.6.1.2.1.16.23.1.4.1.5",
795
+ "status" : "current",
796
+ "syntax" : {
797
+ "type" : {
798
+ "basetype" : "OctetString",
799
+ "ranges" : [
800
+ {
801
+ "min" : "0",
802
+ "max" : "65535"
803
+ },
804
+ ],
805
+ "range" : {
806
+ "min" : "0",
807
+ "max" : "65535"
808
+ },
809
+ },
810
+ },
811
+ "access" : "readwrite",
812
+ "description" :
813
+ """This entry will only represent HTTP transactions
814
+ where the URL path component in the request matches this
815
+ value. This value represents the requested path regardless of
816
+ any substitution that the server might perform.
817
+
818
+ Prior to the matching, the URL is stripped of any server
819
+ address or DNS name and consists solely of the path name on
820
+ that server.
821
+
822
+ If the length of this object is zero, then this entry will
823
+ match if the associated apmHttpFilterServerAddress match. If
824
+ the length of that object is also zero, then this entry will
825
+ match nothing.
826
+
827
+ The value of the associated apmHttpFilterMatchType dictates
828
+ the type of matching that will be attempted.""",
829
+ }, # column
830
+ "apmHttpFilterMatchType" : {
831
+ "nodetype" : "column",
832
+ "moduleName" : "APM-MIB",
833
+ "oid" : "1.3.6.1.2.1.16.23.1.4.1.6",
834
+ "status" : "current",
835
+ "syntax" : {
836
+ "type" : {
837
+ "basetype" : "Enumeration",
838
+ "exact" : {
839
+ "nodetype" : "namednumber",
840
+ "number" : "1"
841
+ },
842
+ "stripTrailingSlash" : {
843
+ "nodetype" : "namednumber",
844
+ "number" : "2"
845
+ },
846
+ "prefix" : {
847
+ "nodetype" : "namednumber",
848
+ "number" : "3"
849
+ },
850
+ },
851
+ },
852
+ "access" : "readwrite",
853
+ "description" :
854
+ """The matching algorithm used to compare the URL pathname.
855
+
856
+ If the value is exact(1), then the pathname component will be
857
+ compared with the associated apmHttpFilterURLPath and
858
+ will only be associated with this entry if it matches exactly.
859
+
860
+
861
+
862
+ If the value is stripTrailingSlash(2), then the pathname
863
+ component will be compared with the associated
864
+ apmHttpFilterURLPath and will only be associated with this
865
+ entry if it matches exactly or if the pathname ends with a '/'
866
+ symbol and matches apmHttpFilterURLPath if the '/' symbol is
867
+ removed from the pathname. This option exists for those paths
868
+ where an optional trailing slash is possible but for which a
869
+ prefix match would be too broad.
870
+
871
+ If the value is prefix(3), then the pathname component will be
872
+ compared with the associated apmHttpFilterURLPath and will
873
+ only be associated with this entry if the beginning of the
874
+ pathname matches every octet of this value. Octets that extend
875
+ beyond the length of this value are ignored.""",
876
+ }, # column
877
+ "apmHttpFilterOwner" : {
878
+ "nodetype" : "column",
879
+ "moduleName" : "APM-MIB",
880
+ "oid" : "1.3.6.1.2.1.16.23.1.4.1.7",
881
+ "status" : "current",
882
+ "syntax" : {
883
+ "type" : { "module" :"RMON-MIB", "name" : "OwnerString"},
884
+ },
885
+ "access" : "readwrite",
886
+ "description" :
887
+ """The entity that configured this entry and is
888
+ therefore using the resources assigned to it.""",
889
+ }, # column
890
+ "apmHttpFilterStorageType" : {
891
+ "nodetype" : "column",
892
+ "moduleName" : "APM-MIB",
893
+ "oid" : "1.3.6.1.2.1.16.23.1.4.1.8",
894
+ "status" : "current",
895
+ "syntax" : {
896
+ "type" : { "module" :"SNMPv2-TC", "name" : "StorageType"},
897
+ },
898
+ "access" : "readwrite",
899
+ "description" :
900
+ """The storage type of this apmHttpFilterEntry. If the value of
901
+ this object is 'permanent', no objects in this row need to be
902
+ writable.""",
903
+ }, # column
904
+ "apmHttpFilterRowStatus" : {
905
+ "nodetype" : "column",
906
+ "moduleName" : "APM-MIB",
907
+ "oid" : "1.3.6.1.2.1.16.23.1.4.1.9",
908
+ "status" : "current",
909
+ "syntax" : {
910
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
911
+ },
912
+ "access" : "readwrite",
913
+ "description" :
914
+ """The status of this apmHttpFilterEntry. No objects in this row
915
+ may be modified while the row's status is 'active'.""",
916
+ }, # column
917
+ "apmHttpIgnoreUnregisteredURLs" : {
918
+ "nodetype" : "scalar",
919
+ "moduleName" : "APM-MIB",
920
+ "oid" : "1.3.6.1.2.1.16.23.1.5",
921
+ "status" : "current",
922
+ "syntax" : {
923
+ "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
924
+ },
925
+ "access" : "readwrite",
926
+ "description" :
927
+ """When true, APM measurements of HTTP transactions will only
928
+ measure transactions relating to URLs that match a filter in
929
+ the apmHttpFilterTable. Thus, measurements for the HTTP
930
+ application will present aggregated statistics for
931
+ URL-matching HTTP transactions and measurements for the HTTP
932
+ GET application verb will present aggregated statistics for
933
+ URL-matching HTTP GET transactions.
934
+
935
+ This will be used in environments that wish to monitor only
936
+ targeted URLs and to ignore large volumes of internet web
937
+ browsing traffic.
938
+
939
+ This object affects all APM reports and exceptions generated
940
+ by this agent. Accordingly, modification of this object should
941
+ be performed by a manager acting in the role of
942
+ administrator. In particular, management software should not
943
+ require or enforce particular configuration of this object -
944
+ it should reflect the preferences of the site administrator,
945
+ not the software author.
946
+
947
+ The value of this object must persist across reboots.""",
948
+ }, # scalar
949
+ "apmHttp4xxIsFailure" : {
950
+ "nodetype" : "scalar",
951
+ "moduleName" : "APM-MIB",
952
+ "oid" : "1.3.6.1.2.1.16.23.1.6",
953
+ "status" : "current",
954
+ "syntax" : {
955
+ "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
956
+ },
957
+ "access" : "readwrite",
958
+ "description" :
959
+ """When true, this agent will recognize HTTP errors in the range
960
+ of 400 through 499 and will treat them as unavailable
961
+ transactions. When false or when this object isn't supported,
962
+ they will be treated as successful transactions.
963
+
964
+ This object allows such error pages to be tracked at the
965
+ possible expense of having user typos treated as poor service
966
+ on the part of the web server.
967
+
968
+ This object affects all reports and exceptions generated by
969
+ this agent. Accordingly, modification of this object should be
970
+ performed by a manager acting in the role of administrator. In
971
+ particular, management software should not require or enforce
972
+ particular configuration of this object - it should reflect
973
+ the preferences of the site administrator, not the software
974
+ author.
975
+
976
+ The value of this object must persist across reboots.""",
977
+ }, # scalar
978
+ "apmUserDefinedAppTable" : {
979
+ "nodetype" : "table",
980
+ "moduleName" : "APM-MIB",
981
+ "oid" : "1.3.6.1.2.1.16.23.1.7",
982
+ "status" : "current",
983
+ "description" :
984
+ """A table that advertises user-defined applications that the
985
+ agent is measuring.
986
+
987
+ The agent will automatically create one or more entries in the
988
+ apmAppDirTable (one for each responsivenessType it is
989
+ capable of measuring) for each entry in this table.
990
+
991
+ Note that when entries exist in this table some
992
+ transactions can be summarized more than once if there is
993
+ overlap between applications defined here and applications
994
+ defined in the protocol directory or in the httpFilter table.""",
995
+ }, # table
996
+ "apmUserDefinedAppEntry" : {
997
+ "nodetype" : "row",
998
+ "moduleName" : "APM-MIB",
999
+ "oid" : "1.3.6.1.2.1.16.23.1.7.1",
1000
+ "status" : "current",
1001
+ "linkage" : [
1002
+ "apmAppDirAppLocalIndex",
1003
+ ],
1004
+ "description" :
1005
+ """A user-defined application that the agent is measuring, along
1006
+ with its AppLocalIndex assignment.
1007
+
1008
+ The apmAppDirAppLocalIndex value in the index identifies
1009
+ the agent-assigned AppLocalIndex value for this user-defined
1010
+ application.""",
1011
+ }, # row
1012
+ "apmUserDefinedAppParentIndex" : {
1013
+ "nodetype" : "column",
1014
+ "moduleName" : "APM-MIB",
1015
+ "oid" : "1.3.6.1.2.1.16.23.1.7.1.1",
1016
+ "status" : "current",
1017
+ "syntax" : {
1018
+ "type" : {
1019
+ "basetype" : "Unsigned32",
1020
+ "ranges" : [
1021
+ {
1022
+ "min" : "1",
1023
+ "max" : "2147483647"
1024
+ },
1025
+ ],
1026
+ "range" : {
1027
+ "min" : "1",
1028
+ "max" : "2147483647"
1029
+ },
1030
+ },
1031
+ },
1032
+ "access" : "readonly",
1033
+ "description" :
1034
+ """The protocolDirLocalIndex value of the highest-layer
1035
+ protocol defined in the protocolDirTable that this
1036
+ application is a child of.""",
1037
+ }, # column
1038
+ "apmUserDefinedAppApplication" : {
1039
+ "nodetype" : "column",
1040
+ "moduleName" : "APM-MIB",
1041
+ "oid" : "1.3.6.1.2.1.16.23.1.7.1.2",
1042
+ "status" : "current",
1043
+ "syntax" : {
1044
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
1045
+ },
1046
+ "access" : "readonly",
1047
+ "description" :
1048
+ """A human readable descriptive tag for this application.""",
1049
+ }, # column
1050
+ "apmNameTable" : {
1051
+ "nodetype" : "table",
1052
+ "moduleName" : "APM-MIB",
1053
+ "oid" : "1.3.6.1.2.1.16.23.1.8",
1054
+ "status" : "current",
1055
+ "description" :
1056
+ """A client machine may have multiple addresses during a period
1057
+ of monitoring. The apmNameTable assigns a long-lived
1058
+ identifier to a client and records what addresses were
1059
+ assigned to that client for periods of time. Various
1060
+ implementation techniques exist for tracking this mapping but
1061
+ if an agent is unable to track client address mappings, it may
1062
+ map client identifiers to client addresses rather than to
1063
+ distinct client machines.
1064
+
1065
+ A particular apmNameClientID should be a constant attribute of
1066
+ a particular client. When available, the agent may also record
1067
+ the machine name and/or user name which may be valuable for
1068
+ displaying to humans. The apmNameMachineName and
1069
+ apmNameUserName are relatively constant, changing only if
1070
+ these attributes actually change on the client.
1071
+
1072
+ The agent will store a historical log of these entries, aging
1073
+ out old entries as the log becomes too large. Since this table
1074
+ contains information vital to the interpretation of other
1075
+ tables (e.g., the apmReportTable), the agent should ensure that
1076
+
1077
+
1078
+
1079
+ the log doesn't age out entries that would be referenced by
1080
+ data in those tables.
1081
+
1082
+ Note that an entry for a clientID is active from its
1083
+ StartTime until the StartTime of another entry (for the same
1084
+ clientID) that supersedes it, or 'now' if none supersede
1085
+ it. Therefore, if a clientID only has a single entry, it is by
1086
+ definition very new and should never be aged out. No entry for
1087
+ a clientID should be aged out unless it has been updated by a
1088
+ new entry for the client (i.e., with an updated address) and
1089
+ only if the new entry is 'old' enough.
1090
+
1091
+ To determine how old is old enough, compute the maximum value
1092
+ of Interval * (NumReports + 1) of all entries in the
1093
+ apmReportControlTable (the '+ 1' is to allow a reasonable
1094
+ period of time for the report to be downloaded). Then take the
1095
+ larger of this value and the age in seconds of the oldest
1096
+ entry in the current transaction table. If an entry for a
1097
+ clientID is superseded by another entry whose StartTime is
1098
+ more than this many seconds ago, then the older entry may be
1099
+ deleted.""",
1100
+ }, # table
1101
+ "apmNameEntry" : {
1102
+ "nodetype" : "row",
1103
+ "moduleName" : "APM-MIB",
1104
+ "oid" : "1.3.6.1.2.1.16.23.1.8.1",
1105
+ "status" : "current",
1106
+ "linkage" : [
1107
+ "apmNameClientID",
1108
+ "protocolDirLocalIndex",
1109
+ "apmNameClientAddress",
1110
+ "apmNameMappingStartTime",
1111
+ ],
1112
+ "description" :
1113
+ """An entry in the APM name table. An entry exists for each
1114
+ period of time that a client has been associated with a
1115
+ particular address.
1116
+
1117
+ The protocolDirLocalIndex value in the index identifies
1118
+ the network layer protocol for the ClientAddress for this
1119
+ entry.
1120
+
1121
+ Note that some combinations of index values may result in an
1122
+ index that exceeds 128 sub-identifiers in length which exceeds
1123
+ the maximum for the SNMP protocol. Implementations should take
1124
+ care to avoid such combinations.""",
1125
+ }, # row
1126
+ "apmNameClientID" : {
1127
+ "nodetype" : "column",
1128
+ "moduleName" : "APM-MIB",
1129
+ "oid" : "1.3.6.1.2.1.16.23.1.8.1.1",
1130
+ "status" : "current",
1131
+ "syntax" : {
1132
+ "type" : { "module" :"APM-MIB", "name" : "RmonClientID"},
1133
+ },
1134
+ "access" : "noaccess",
1135
+ "description" :
1136
+ """A unique ID assigned to the machine represented by this
1137
+ mapping. This ID is assigned by the agent using an
1138
+ implementation-specific algorithm.""",
1139
+ }, # column
1140
+ "apmNameClientAddress" : {
1141
+ "nodetype" : "column",
1142
+ "moduleName" : "APM-MIB",
1143
+ "oid" : "1.3.6.1.2.1.16.23.1.8.1.2",
1144
+ "status" : "current",
1145
+ "syntax" : {
1146
+ "type" : {
1147
+ "basetype" : "OctetString",
1148
+ "parent module" : {
1149
+ "name" : "APM-MIB",
1150
+ "type" : "ProtocolDirNetworkAddress",
1151
+ },
1152
+ "ranges" : [
1153
+ {
1154
+ "min" : "1",
1155
+ "max" : "255"
1156
+ },
1157
+ ],
1158
+ "range" : {
1159
+ "min" : "1",
1160
+ "max" : "255"
1161
+ },
1162
+ },
1163
+ },
1164
+ "access" : "noaccess",
1165
+ "description" :
1166
+ """The network client address for this client when this mapping
1167
+ was active.
1168
+
1169
+ This is represented as an octet string with specific semantics
1170
+ and length as identified by the protocolDirLocalIndex
1171
+ component of the index. This object may not be the zero length
1172
+ string.
1173
+
1174
+ Since this object is an index variable, it is encoded in the
1175
+ index according to the index encoding rules. For example, if
1176
+ the protocolDirLocalIndex component of the index indicates an
1177
+ encapsulation of ip, this object is encoded as a length octet
1178
+ of 4, followed by the 4 octets of the ip address, in network
1179
+ byte order. Care should be taken to avoid values of this
1180
+ object that, in conjunction with the other index variables,
1181
+ would result in an index longer than SNMP's maximum of 128
1182
+ subidentifiers.""",
1183
+ }, # column
1184
+ "apmNameMappingStartTime" : {
1185
+ "nodetype" : "column",
1186
+ "moduleName" : "APM-MIB",
1187
+ "oid" : "1.3.6.1.2.1.16.23.1.8.1.3",
1188
+ "status" : "current",
1189
+ "syntax" : {
1190
+ "type" : { "module" :"SNMPv2-TC", "name" : "DateAndTime"},
1191
+ },
1192
+ "access" : "noaccess",
1193
+ "description" :
1194
+ """The time that the agent first discovered this mapping
1195
+ as active.""",
1196
+ }, # column
1197
+ "apmNameMachineName" : {
1198
+ "nodetype" : "column",
1199
+ "moduleName" : "APM-MIB",
1200
+ "oid" : "1.3.6.1.2.1.16.23.1.8.1.4",
1201
+ "status" : "current",
1202
+ "syntax" : {
1203
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
1204
+ },
1205
+ "access" : "readonly",
1206
+ "description" :
1207
+ """The human readable name of the client machine.
1208
+
1209
+ If the client has no machine name or the agent is
1210
+ unable to learn the machine name, this object will be
1211
+ a zero-length string.""",
1212
+ }, # column
1213
+ "apmNameUserName" : {
1214
+ "nodetype" : "column",
1215
+ "moduleName" : "APM-MIB",
1216
+ "oid" : "1.3.6.1.2.1.16.23.1.8.1.5",
1217
+ "status" : "current",
1218
+ "syntax" : {
1219
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
1220
+ },
1221
+ "access" : "readonly",
1222
+ "description" :
1223
+ """The human readable name of a human user using the client
1224
+ machine. If more than one user name are available
1225
+ simultaneously, it is an implementation-dependent matter as to
1226
+ which is used here. However, if the user name changes, this
1227
+ object should change to reflect that change.
1228
+
1229
+ Non-human user names like 'root' or 'administrator' aren't
1230
+ intended as values for this object. If the client has no
1231
+ recorded user name or the agent is unable to learn a user
1232
+ name, this object will be a zero-length string.""",
1233
+ }, # column
1234
+ "apmReportControlTable" : {
1235
+ "nodetype" : "table",
1236
+ "moduleName" : "APM-MIB",
1237
+ "oid" : "1.3.6.1.2.1.16.23.1.9",
1238
+ "status" : "current",
1239
+ "description" :
1240
+ """Parameters that control the creation of a set of reports that
1241
+ aggregate application performance.""",
1242
+ }, # table
1243
+ "apmReportControlEntry" : {
1244
+ "nodetype" : "row",
1245
+ "moduleName" : "APM-MIB",
1246
+ "oid" : "1.3.6.1.2.1.16.23.1.9.1",
1247
+ "create" : "true",
1248
+ "status" : "current",
1249
+ "linkage" : [
1250
+ "apmReportControlIndex",
1251
+ ],
1252
+ "description" :
1253
+ """A conceptual row in the apmReportControlTable.
1254
+
1255
+ An example of the indexing of this table is
1256
+
1257
+
1258
+
1259
+ apmReportControlInterval.3""",
1260
+ }, # row
1261
+ "apmReportControlIndex" : {
1262
+ "nodetype" : "column",
1263
+ "moduleName" : "APM-MIB",
1264
+ "oid" : "1.3.6.1.2.1.16.23.1.9.1.1",
1265
+ "status" : "current",
1266
+ "syntax" : {
1267
+ "type" : {
1268
+ "basetype" : "Unsigned32",
1269
+ "ranges" : [
1270
+ {
1271
+ "min" : "1",
1272
+ "max" : "65535"
1273
+ },
1274
+ ],
1275
+ "range" : {
1276
+ "min" : "1",
1277
+ "max" : "65535"
1278
+ },
1279
+ },
1280
+ },
1281
+ "access" : "noaccess",
1282
+ "description" :
1283
+ """An index that uniquely identifies an entry in the
1284
+ apmReportControlTable. Each such entry defines a unique
1285
+ report whose results are placed in the apmReportTable on
1286
+ behalf of this apmReportControlEntry.""",
1287
+ }, # column
1288
+ "apmReportControlDataSource" : {
1289
+ "nodetype" : "column",
1290
+ "moduleName" : "APM-MIB",
1291
+ "oid" : "1.3.6.1.2.1.16.23.1.9.1.2",
1292
+ "status" : "current",
1293
+ "syntax" : {
1294
+ "type" : { "module" :"APM-MIB", "name" : "DataSourceOrZero"},
1295
+ },
1296
+ "access" : "readwrite",
1297
+ "description" :
1298
+ """The source of the data for APM Reports generated on
1299
+ behalf of this apmReportControlEntry.
1300
+
1301
+ If the measurement is being performed by a probe, this should
1302
+ be set to interface or port where data was received for
1303
+ analysis. If the measurement isn't being performed by a probe,
1304
+ this should be set to the primary interface over which the
1305
+ measurement is being performed. If the measurement isn't being
1306
+ performed by a probe and there is no primary interface or this
1307
+
1308
+
1309
+
1310
+ information isn't known, this object should be set to 0.0.
1311
+
1312
+ This object may not be modified if the associated
1313
+ apmReportControlStatus object is equal to active(1).""",
1314
+ }, # column
1315
+ "apmReportControlAggregationType" : {
1316
+ "nodetype" : "column",
1317
+ "moduleName" : "APM-MIB",
1318
+ "oid" : "1.3.6.1.2.1.16.23.1.9.1.3",
1319
+ "status" : "current",
1320
+ "syntax" : {
1321
+ "type" : { "module" :"APM-MIB", "name" : "TransactionAggregationType"},
1322
+ },
1323
+ "access" : "readwrite",
1324
+ "description" :
1325
+ """The type of aggregation being performed for this set of
1326
+ reports.
1327
+
1328
+ The metrics for a single transaction are the responsiveness of
1329
+ the transaction and whether the transaction succeeded (a
1330
+ boolean). When such metrics are aggregated in this MIB Module,
1331
+ these metrics are replaced by averages and distributions of
1332
+ responsiveness and availability. The metrics describing
1333
+ aggregates are constant no matter which type of aggregation is
1334
+ being performed. These metrics may be found in the
1335
+ apmReportTable.
1336
+
1337
+ The flows(1) aggregation is the simplest. All transactions
1338
+ that share common application/server/client 3-tuples are
1339
+ aggregated together, resulting in a set of metrics for all
1340
+ such unique 3-tuples.
1341
+
1342
+ The clients(2) aggregation results in somewhat more
1343
+ aggregation (i.e., fewer resulting records). All transactions
1344
+ that share common application/client tuples are aggregated
1345
+ together, resulting in a set of metrics for all such unique
1346
+ tuples.
1347
+
1348
+ The servers(3) aggregation usually results in still more
1349
+ aggregation (i.e., fewer resulting records). All transactions
1350
+ that share common application/server tuples are aggregated
1351
+ together, resulting in a set of metrics for all such unique
1352
+ tuples.
1353
+
1354
+ The applications(4) aggregation results in the most
1355
+ aggregation (i.e., the fewest resulting records). All
1356
+
1357
+
1358
+
1359
+ transactions that share a common application are aggregated
1360
+ together, resulting in a set of metrics for all such unique
1361
+ applications.
1362
+
1363
+ Note that it is not meaningful to aggregate applications, as
1364
+ different applications have widely varying characteristics.
1365
+ As a result, this set of aggregations is complete.
1366
+
1367
+ This object may not be modified if the associated
1368
+ apmReportControlStatus object is equal to active(1).""",
1369
+ }, # column
1370
+ "apmReportControlInterval" : {
1371
+ "nodetype" : "column",
1372
+ "moduleName" : "APM-MIB",
1373
+ "oid" : "1.3.6.1.2.1.16.23.1.9.1.4",
1374
+ "status" : "current",
1375
+ "syntax" : {
1376
+ "type" : { "module" :"", "name" : "Unsigned32"},
1377
+ },
1378
+ "access" : "readwrite",
1379
+ "default" : "3600",
1380
+ "units" : "Seconds",
1381
+ "description" :
1382
+ """The interval in seconds over which data is accumulated before
1383
+ being aggregated into a report in the apmReportTable. All
1384
+ reports with the same apmReportControlIndex will be based on
1385
+ the same interval. This object must be greater than zero.
1386
+
1387
+ Many users desire that these reports be synchronized to within
1388
+ seconds of the beginning of the hour because the results may
1389
+ be correlated more meaningfully to business behavior and so
1390
+ that data from multiple agents is aggregated over the same
1391
+ time periods. Thus management software may take extra effort
1392
+ to synchronize reports to the beginning of the hour and to one
1393
+ another. However, the agent must not allow reports to 'drift'
1394
+ over time as they will quickly become unsynchronized. In
1395
+ particular, if there is any fixed processing delay between
1396
+ reports, the reports should deduct this time from the interval
1397
+ so that reports don't drift.
1398
+
1399
+ This object may not be modified if the associated
1400
+ apmReportControlStatus object is equal to active(1).""",
1401
+ }, # column
1402
+ "apmReportControlRequestedSize" : {
1403
+ "nodetype" : "column",
1404
+ "moduleName" : "APM-MIB",
1405
+ "oid" : "1.3.6.1.2.1.16.23.1.9.1.5",
1406
+ "status" : "current",
1407
+ "syntax" : {
1408
+ "type" : { "module" :"", "name" : "Unsigned32"},
1409
+ },
1410
+ "access" : "readwrite",
1411
+ "description" :
1412
+ """The number of entries requested to be allocated for each
1413
+ report generated on behalf of this entry.""",
1414
+ }, # column
1415
+ "apmReportControlGrantedSize" : {
1416
+ "nodetype" : "column",
1417
+ "moduleName" : "APM-MIB",
1418
+ "oid" : "1.3.6.1.2.1.16.23.1.9.1.6",
1419
+ "status" : "current",
1420
+ "syntax" : {
1421
+ "type" : { "module" :"", "name" : "Unsigned32"},
1422
+ },
1423
+ "access" : "readonly",
1424
+ "description" :
1425
+ """The number of entries per report the agent has allocated
1426
+ based on the requested amount in apmReportControlRequestedSize.
1427
+ Since multiple reports are saved, the total number of entries
1428
+ allocated will be this number multiplied by the value of
1429
+ apmReportControlGrantedReports, or 1 if that object doesn't
1430
+ exist.
1431
+
1432
+ When the associated apmReportControlRequestedSize object is
1433
+ created or modified, the agent should set this object as
1434
+ closely to the requested value as is possible for the
1435
+ particular implementation and available resources. When
1436
+ considering resources available, the agent must consider its
1437
+ ability to allocate this many entries for all reports.
1438
+
1439
+ Note that while the actual number of entries stored in the
1440
+ reports may fluctuate due to changing conditions, the agent
1441
+ must continue to have storage available to satisfy the full
1442
+ report size for all reports when necessary. Further, the agent
1443
+ must not lower this value except as a result of a set to the
1444
+ associated apmReportControlRequestedSize object.""",
1445
+ }, # column
1446
+ "apmReportControlRequestedReports" : {
1447
+ "nodetype" : "column",
1448
+ "moduleName" : "APM-MIB",
1449
+ "oid" : "1.3.6.1.2.1.16.23.1.9.1.7",
1450
+ "status" : "current",
1451
+ "syntax" : {
1452
+ "type" : {
1453
+ "basetype" : "Unsigned32",
1454
+ "ranges" : [
1455
+ {
1456
+ "min" : "0",
1457
+ "max" : "65535"
1458
+ },
1459
+ ],
1460
+ "range" : {
1461
+ "min" : "0",
1462
+ "max" : "65535"
1463
+ },
1464
+ },
1465
+ },
1466
+ "access" : "readwrite",
1467
+ "description" :
1468
+ """The number of saved reports requested to be allocated on
1469
+ behalf of this entry.""",
1470
+ }, # column
1471
+ "apmReportControlGrantedReports" : {
1472
+ "nodetype" : "column",
1473
+ "moduleName" : "APM-MIB",
1474
+ "oid" : "1.3.6.1.2.1.16.23.1.9.1.8",
1475
+ "status" : "current",
1476
+ "syntax" : {
1477
+ "type" : {
1478
+ "basetype" : "Unsigned32",
1479
+ "ranges" : [
1480
+ {
1481
+ "min" : "0",
1482
+ "max" : "65535"
1483
+ },
1484
+ ],
1485
+ "range" : {
1486
+ "min" : "0",
1487
+ "max" : "65535"
1488
+ },
1489
+ },
1490
+ },
1491
+ "access" : "readonly",
1492
+ "description" :
1493
+ """The number of saved reports the agent has allocated
1494
+ based on the requested amount in
1495
+ apmReportControlRequestedReports. Since each report can have
1496
+ many entries, the total number of entries allocated will be
1497
+ this number multiplied by the value of
1498
+ apmReportControlGrantedSize, or 1 if that object doesn't
1499
+ exist.
1500
+
1501
+
1502
+
1503
+ When the associated apmReportControlRequestedReports object is
1504
+ created or modified, the agent should set this object as
1505
+ closely to the requested value as is possible for the
1506
+ particular implementation and available resources. When
1507
+ considering resources available, the agent must consider its
1508
+ ability to allocate this many reports each with the number of
1509
+ entries represented by apmReportControlGrantedSize, or 1 if
1510
+ that object doesn't exist.
1511
+
1512
+ Note that while the storage required for each report may
1513
+ fluctuate due to changing conditions, the agent must continue
1514
+ to have storage available to satisfy the full report size for
1515
+ all reports when necessary. Further, the agent must not lower
1516
+ this value except as a result of a set to the associated
1517
+ apmReportControlRequestedSize object.""",
1518
+ }, # column
1519
+ "apmReportControlStartTime" : {
1520
+ "nodetype" : "column",
1521
+ "moduleName" : "APM-MIB",
1522
+ "oid" : "1.3.6.1.2.1.16.23.1.9.1.9",
1523
+ "status" : "current",
1524
+ "syntax" : {
1525
+ "type" : { "module" :"SNMPv2-TC", "name" : "TimeStamp"},
1526
+ },
1527
+ "access" : "readonly",
1528
+ "description" :
1529
+ """The value of sysUpTime when the system began processing the
1530
+ report in progress. Note that the report in progress is not
1531
+ available.
1532
+
1533
+ This object may be used by the management station to figure
1534
+ out the start time for all previous reports saved for this
1535
+ apmReportControlEntry, as reports are started at fixed
1536
+ intervals.""",
1537
+ }, # column
1538
+ "apmReportControlReportNumber" : {
1539
+ "nodetype" : "column",
1540
+ "moduleName" : "APM-MIB",
1541
+ "oid" : "1.3.6.1.2.1.16.23.1.9.1.10",
1542
+ "status" : "current",
1543
+ "syntax" : {
1544
+ "type" : {
1545
+ "basetype" : "Unsigned32",
1546
+ "ranges" : [
1547
+ {
1548
+ "min" : "1",
1549
+ "max" : "4294967295"
1550
+ },
1551
+ ],
1552
+ "range" : {
1553
+ "min" : "1",
1554
+ "max" : "4294967295"
1555
+ },
1556
+ },
1557
+ },
1558
+ "access" : "readonly",
1559
+ "description" :
1560
+ """The number of the report in progress. When an
1561
+ apmReportControlEntry is activated, the first report will be
1562
+ numbered one.""",
1563
+ }, # column
1564
+ "apmReportControlDeniedInserts" : {
1565
+ "nodetype" : "column",
1566
+ "moduleName" : "APM-MIB",
1567
+ "oid" : "1.3.6.1.2.1.16.23.1.9.1.11",
1568
+ "status" : "current",
1569
+ "syntax" : {
1570
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
1571
+ },
1572
+ "access" : "readonly",
1573
+ "description" :
1574
+ """The number of failed attempts to add an entry to reports for
1575
+
1576
+
1577
+
1578
+ this apmReportControlEntry because the number of entries
1579
+ would have exceeded apmReportControlGrantedSize.
1580
+
1581
+ This number is valuable in determining if enough entries have
1582
+ been allocated for reports in light of fluctuating network
1583
+ usage. Note that since an entry that is denied will often be
1584
+ attempted again, this number will not predict the exact number
1585
+ of additional entries needed, but can be used to understand
1586
+ the relative magnitude of the problem.
1587
+
1588
+ Also note that there is no ordering specified for the entries
1589
+ in the report, thus there are no rules for which entries will
1590
+ be omitted when not enough entries are available. As a
1591
+ consequence, the agent is not required to delete 'least
1592
+ valuable' entries first.""",
1593
+ }, # column
1594
+ "apmReportControlDroppedFrames" : {
1595
+ "nodetype" : "column",
1596
+ "moduleName" : "APM-MIB",
1597
+ "oid" : "1.3.6.1.2.1.16.23.1.9.1.12",
1598
+ "status" : "current",
1599
+ "syntax" : {
1600
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
1601
+ },
1602
+ "access" : "readonly",
1603
+ "description" :
1604
+ """The total number of frames which were received by the agent
1605
+ and therefore not accounted for in the *StatsDropEvents, but
1606
+ for which the agent chose not to count for this entry for
1607
+ whatever reason. Most often, this event occurs when the agent
1608
+ is out of some resources and decides to shed load from this
1609
+ collection.
1610
+
1611
+ This count does not include packets that were not counted
1612
+ because they had MAC-layer errors.
1613
+
1614
+ This counter is only relevant if this apm report is based on
1615
+ a data source whose collection methodology is based on
1616
+ analyzing network traffic.
1617
+
1618
+ Note that if the apmReportTables are inactive because no
1619
+ applications are enabled in the application directory, this
1620
+ value should be 0.
1621
+
1622
+ Note that, unlike the dropEvents counter, this number is the
1623
+ exact number of frames dropped.""",
1624
+ }, # column
1625
+ "apmReportControlOwner" : {
1626
+ "nodetype" : "column",
1627
+ "moduleName" : "APM-MIB",
1628
+ "oid" : "1.3.6.1.2.1.16.23.1.9.1.13",
1629
+ "status" : "current",
1630
+ "syntax" : {
1631
+ "type" : { "module" :"RMON-MIB", "name" : "OwnerString"},
1632
+ },
1633
+ "access" : "readwrite",
1634
+ "description" :
1635
+ """The entity that configured this entry and is
1636
+ therefore using the resources assigned to it.""",
1637
+ }, # column
1638
+ "apmReportControlStorageType" : {
1639
+ "nodetype" : "column",
1640
+ "moduleName" : "APM-MIB",
1641
+ "oid" : "1.3.6.1.2.1.16.23.1.9.1.14",
1642
+ "status" : "current",
1643
+ "syntax" : {
1644
+ "type" : { "module" :"SNMPv2-TC", "name" : "StorageType"},
1645
+ },
1646
+ "access" : "readwrite",
1647
+ "description" :
1648
+ """The storage type of this apmReportControlEntry. If the value
1649
+ of this object is 'permanent', no objects in this row need to
1650
+ be writable.""",
1651
+ }, # column
1652
+ "apmReportControlStatus" : {
1653
+ "nodetype" : "column",
1654
+ "moduleName" : "APM-MIB",
1655
+ "oid" : "1.3.6.1.2.1.16.23.1.9.1.15",
1656
+ "status" : "current",
1657
+ "syntax" : {
1658
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
1659
+ },
1660
+ "access" : "readwrite",
1661
+ "description" :
1662
+ """The status of this apmReportControlEntry.
1663
+
1664
+ An entry may not exist in the active state unless all
1665
+ objects in the entry have an appropriate value. The only
1666
+ objects in the entry that may be modified while the entry is
1667
+ in the active state are apmReportControlRequestedSize and
1668
+ apmReportControlRequestedReports.
1669
+
1670
+ If this object is not equal to active(1), all
1671
+ associated entries in the apmReportTable shall be deleted
1672
+ by the agent.""",
1673
+ }, # column
1674
+ "apmReportTable" : {
1675
+ "nodetype" : "table",
1676
+ "moduleName" : "APM-MIB",
1677
+ "oid" : "1.3.6.1.2.1.16.23.1.10",
1678
+ "status" : "current",
1679
+ "description" :
1680
+ """The data resulting from aggregated APM reports. Consult the
1681
+ definition of apmReportControlAggregationType for the
1682
+ definition of the various types of aggregations.""",
1683
+ }, # table
1684
+ "apmReportEntry" : {
1685
+ "nodetype" : "row",
1686
+ "moduleName" : "APM-MIB",
1687
+ "oid" : "1.3.6.1.2.1.16.23.1.10.1",
1688
+ "status" : "current",
1689
+ "linkage" : [
1690
+ "apmReportControlIndex",
1691
+ "apmReportIndex",
1692
+ "apmAppDirAppLocalIndex",
1693
+ "apmAppDirResponsivenessType",
1694
+ "protocolDirLocalIndex",
1695
+ "apmReportServerAddress",
1696
+ "apmNameClientID",
1697
+ ],
1698
+ "description" :
1699
+ """A conceptual row in the apmReportTable.
1700
+ The apmReportControlIndex value in the index identifies the
1701
+ apmReportControlEntry on whose behalf this entry was created.
1702
+ The apmReportIndex value in the index identifies which report
1703
+ (in the series of reports) this entry is a part of.
1704
+ The apmAppDirAppLocalIndex value in the index identifies
1705
+ the common application of the transactions aggregated in this
1706
+ entry.
1707
+ The apmAppDirResponsivenessType value in the index
1708
+ identifies the type of responsiveness metric reported by
1709
+ this entry and uniquely identifies this entry when more
1710
+ than one responsiveness metric is measured for a flow.
1711
+ Entries will only exist in this table for those
1712
+ combinations of AppLocalIndex and ResponsivenessType
1713
+ that are configured 'on(1)'.
1714
+ The protocolDirLocalIndex value in the index identifies
1715
+ the network layer protocol of the apmReportServerAddress.
1716
+ When the associated apmReportControlAggregationType value is
1717
+ equal to applications(4) or clients(2), this
1718
+ protocolDirLocalIndex value will equal 0.
1719
+ The apmReportServerAddress value in the index identifies the
1720
+ network layer address of the server in transactions aggregated
1721
+ in this entry.
1722
+ The apmNameClientID value in the index identifies the
1723
+ client in transactions aggregated in this entry. If the
1724
+ associated apmReportControlAggregationType is equal to
1725
+ applications(4) or servers(3), then this protocolDirLocalIndex
1726
+ value will equal 0.
1727
+
1728
+ An example of the indexing of this entry is
1729
+ apmReportTransactionCount.3.15.3.1.8.4.192.168.1.2.3232235788
1730
+
1731
+ Note that some combinations of index values may result in an
1732
+ index that exceeds 128 sub-identifiers in length which exceeds
1733
+ the maximum for the SNMP protocol. Implementations should take
1734
+ care to avoid such combinations.""",
1735
+ }, # row
1736
+ "apmReportIndex" : {
1737
+ "nodetype" : "column",
1738
+ "moduleName" : "APM-MIB",
1739
+ "oid" : "1.3.6.1.2.1.16.23.1.10.1.1",
1740
+ "status" : "current",
1741
+ "syntax" : {
1742
+ "type" : {
1743
+ "basetype" : "Unsigned32",
1744
+ "ranges" : [
1745
+ {
1746
+ "min" : "1",
1747
+ "max" : "4294967295"
1748
+ },
1749
+ ],
1750
+ "range" : {
1751
+ "min" : "1",
1752
+ "max" : "4294967295"
1753
+ },
1754
+ },
1755
+ },
1756
+ "access" : "noaccess",
1757
+ "description" :
1758
+ """The value of apmReportControlReportNumber for the report to
1759
+ which this entry belongs.""",
1760
+ }, # column
1761
+ "apmReportServerAddress" : {
1762
+ "nodetype" : "column",
1763
+ "moduleName" : "APM-MIB",
1764
+ "oid" : "1.3.6.1.2.1.16.23.1.10.1.2",
1765
+ "status" : "current",
1766
+ "syntax" : {
1767
+ "type" : { "module" :"APM-MIB", "name" : "ProtocolDirNetworkAddress"},
1768
+ },
1769
+ "access" : "noaccess",
1770
+ "description" :
1771
+ """The network server address for this apmReportEntry.
1772
+
1773
+ This is represented as an octet string with
1774
+ specific semantics and length as identified
1775
+ by the protocolDirLocalIndex component of the index.
1776
+
1777
+ Since this object is an index variable, it is encoded in the
1778
+ index according to the index encoding rules. For example, if
1779
+ the protocolDirLocalIndex indicates an encapsulation of ip,
1780
+ this object is encoded as a length octet of 4, followed by the
1781
+ 4 octets of the ip address, in network byte order. Care
1782
+ should be taken to avoid values of this object that, in
1783
+ conjunction with the other index variables, would result in an
1784
+ index longer than SNMP's maximum of 128 subidentifiers.
1785
+
1786
+ If the associated apmReportControlAggregationType is equal to
1787
+ applications(4) or clients(2), then this object will be a null
1788
+ string and will be encoded simply as a length octet of 0.""",
1789
+ }, # column
1790
+ "apmReportTransactionCount" : {
1791
+ "nodetype" : "column",
1792
+ "moduleName" : "APM-MIB",
1793
+ "oid" : "1.3.6.1.2.1.16.23.1.10.1.3",
1794
+ "status" : "current",
1795
+ "syntax" : {
1796
+ "type" : { "module" :"", "name" : "Unsigned32"},
1797
+ },
1798
+ "access" : "readonly",
1799
+ "description" :
1800
+ """The total number of transactions aggregated into this record.""",
1801
+ }, # column
1802
+ "apmReportSuccessfulTransactions" : {
1803
+ "nodetype" : "column",
1804
+ "moduleName" : "APM-MIB",
1805
+ "oid" : "1.3.6.1.2.1.16.23.1.10.1.4",
1806
+ "status" : "current",
1807
+ "syntax" : {
1808
+ "type" : { "module" :"", "name" : "Unsigned32"},
1809
+ },
1810
+ "access" : "readonly",
1811
+ "description" :
1812
+ """The total number of successful transactions aggregated into
1813
+ this record.""",
1814
+ }, # column
1815
+ "apmReportResponsivenessMean" : {
1816
+ "nodetype" : "column",
1817
+ "moduleName" : "APM-MIB",
1818
+ "oid" : "1.3.6.1.2.1.16.23.1.10.1.5",
1819
+ "status" : "current",
1820
+ "syntax" : {
1821
+ "type" : { "module" :"", "name" : "Unsigned32"},
1822
+ },
1823
+ "access" : "readonly",
1824
+ "description" :
1825
+ """The arithmetic mean of the responsiveness metrics for all
1826
+ successful transactions aggregated into this record.""",
1827
+ }, # column
1828
+ "apmReportResponsivenessMin" : {
1829
+ "nodetype" : "column",
1830
+ "moduleName" : "APM-MIB",
1831
+ "oid" : "1.3.6.1.2.1.16.23.1.10.1.6",
1832
+ "status" : "current",
1833
+ "syntax" : {
1834
+ "type" : { "module" :"", "name" : "Unsigned32"},
1835
+ },
1836
+ "access" : "readonly",
1837
+ "description" :
1838
+ """The minimum of the responsiveness metrics for all
1839
+ successful transactions aggregated into this record.""",
1840
+ }, # column
1841
+ "apmReportResponsivenessMax" : {
1842
+ "nodetype" : "column",
1843
+ "moduleName" : "APM-MIB",
1844
+ "oid" : "1.3.6.1.2.1.16.23.1.10.1.7",
1845
+ "status" : "current",
1846
+ "syntax" : {
1847
+ "type" : { "module" :"", "name" : "Unsigned32"},
1848
+ },
1849
+ "access" : "readonly",
1850
+ "description" :
1851
+ """The maximum of the responsiveness metrics for all
1852
+ successful transactions aggregated into this record.""",
1853
+ }, # column
1854
+ "apmReportResponsivenessB1" : {
1855
+ "nodetype" : "column",
1856
+ "moduleName" : "APM-MIB",
1857
+ "oid" : "1.3.6.1.2.1.16.23.1.10.1.8",
1858
+ "status" : "current",
1859
+ "syntax" : {
1860
+ "type" : { "module" :"", "name" : "Unsigned32"},
1861
+ },
1862
+ "access" : "readonly",
1863
+ "description" :
1864
+ """The number of successful transactions aggregated into this
1865
+ record whose responsiveness was less than boundary1 value for
1866
+ this application.""",
1867
+ }, # column
1868
+ "apmReportResponsivenessB2" : {
1869
+ "nodetype" : "column",
1870
+ "moduleName" : "APM-MIB",
1871
+ "oid" : "1.3.6.1.2.1.16.23.1.10.1.9",
1872
+ "status" : "current",
1873
+ "syntax" : {
1874
+ "type" : { "module" :"", "name" : "Unsigned32"},
1875
+ },
1876
+ "access" : "readonly",
1877
+ "description" :
1878
+ """The number of successful transactions aggregated into this
1879
+ record whose responsiveness did not fall into Bucket 1 and was
1880
+ greater than or equal to the boundary1 value for this
1881
+ application and less than the boundary2 value for this
1882
+ application.""",
1883
+ }, # column
1884
+ "apmReportResponsivenessB3" : {
1885
+ "nodetype" : "column",
1886
+ "moduleName" : "APM-MIB",
1887
+ "oid" : "1.3.6.1.2.1.16.23.1.10.1.10",
1888
+ "status" : "current",
1889
+ "syntax" : {
1890
+ "type" : { "module" :"", "name" : "Unsigned32"},
1891
+ },
1892
+ "access" : "readonly",
1893
+ "description" :
1894
+ """The number of successful transactions aggregated into this
1895
+ record whose responsiveness did not fall into Bucket 1 or 2
1896
+ and as greater than or equal to the boundary2 value for this
1897
+ application and less than the boundary3 value for this
1898
+ application.""",
1899
+ }, # column
1900
+ "apmReportResponsivenessB4" : {
1901
+ "nodetype" : "column",
1902
+ "moduleName" : "APM-MIB",
1903
+ "oid" : "1.3.6.1.2.1.16.23.1.10.1.11",
1904
+ "status" : "current",
1905
+ "syntax" : {
1906
+ "type" : { "module" :"", "name" : "Unsigned32"},
1907
+ },
1908
+ "access" : "readonly",
1909
+ "description" :
1910
+ """The number of successful transactions aggregated into this
1911
+ record whose responsiveness did not fall into Buckets 1
1912
+ through 3 and was greater than or equal to the boundary3 value
1913
+ for this application and less than the boundary4 value for
1914
+ this application.""",
1915
+ }, # column
1916
+ "apmReportResponsivenessB5" : {
1917
+ "nodetype" : "column",
1918
+ "moduleName" : "APM-MIB",
1919
+ "oid" : "1.3.6.1.2.1.16.23.1.10.1.12",
1920
+ "status" : "current",
1921
+ "syntax" : {
1922
+ "type" : { "module" :"", "name" : "Unsigned32"},
1923
+ },
1924
+ "access" : "readonly",
1925
+ "description" :
1926
+ """The number of successful transactions aggregated into this
1927
+ record whose responsiveness did not fall into Buckets 1
1928
+ through 4 and was greater than or equal to the boundary4 value
1929
+ for this application and less than the boundary5 value for
1930
+ this application.""",
1931
+ }, # column
1932
+ "apmReportResponsivenessB6" : {
1933
+ "nodetype" : "column",
1934
+ "moduleName" : "APM-MIB",
1935
+ "oid" : "1.3.6.1.2.1.16.23.1.10.1.13",
1936
+ "status" : "current",
1937
+ "syntax" : {
1938
+ "type" : { "module" :"", "name" : "Unsigned32"},
1939
+ },
1940
+ "access" : "readonly",
1941
+ "description" :
1942
+ """The number of successful transactions aggregated into this
1943
+ record whose responsiveness did not fall into Buckets 1
1944
+ through 5 and was greater than or equal to the
1945
+ boundary5 value for this application and less than the
1946
+ boundary6 value for this application.""",
1947
+ }, # column
1948
+ "apmReportResponsivenessB7" : {
1949
+ "nodetype" : "column",
1950
+ "moduleName" : "APM-MIB",
1951
+ "oid" : "1.3.6.1.2.1.16.23.1.10.1.14",
1952
+ "status" : "current",
1953
+ "syntax" : {
1954
+ "type" : { "module" :"", "name" : "Unsigned32"},
1955
+ },
1956
+ "access" : "readonly",
1957
+ "description" :
1958
+ """The number of successful transactions aggregated into this
1959
+ record whose responsiveness did not fall into Buckets 1
1960
+ through 6 and was greater than or equal to the boundary6 value
1961
+ for this application.""",
1962
+ }, # column
1963
+ "apmTransactionTable" : {
1964
+ "nodetype" : "table",
1965
+ "moduleName" : "APM-MIB",
1966
+ "oid" : "1.3.6.1.2.1.16.23.1.11",
1967
+ "status" : "current",
1968
+ "description" :
1969
+ """This table contains transactions that are currently running
1970
+ or have recently finished.""",
1971
+ }, # table
1972
+ "apmTransactionEntry" : {
1973
+ "nodetype" : "row",
1974
+ "moduleName" : "APM-MIB",
1975
+ "oid" : "1.3.6.1.2.1.16.23.1.11.1",
1976
+ "status" : "current",
1977
+ "linkage" : [
1978
+ "apmAppDirAppLocalIndex",
1979
+ "apmAppDirResponsivenessType",
1980
+ "protocolDirLocalIndex",
1981
+ "apmTransactionServerAddress",
1982
+ "apmNameClientID",
1983
+ "apmTransactionID",
1984
+ ],
1985
+ "description" :
1986
+ """A conceptual row in the apmTransactionTable.
1987
+
1988
+ The apmAppDirAppLocalIndex value in the index identifies
1989
+ the application of the transaction represented by this entry.
1990
+ The apmAppDirResponsivenessType value in the index
1991
+ identifies the type of responsiveness metric reported by
1992
+ this entry and uniquely identifies this entry when more
1993
+ than one responsiveness metric is measured for a flow.
1994
+ Entries will only exist in this table for those
1995
+ combinations of AppLocalIndex and ResponsivenessType
1996
+ that are configured 'on(1)'.
1997
+ The protocolDirLocalIndex value in the index identifies
1998
+ the network layer protocol of the apmTransactionServerAddress.
1999
+ The apmTransactionServerAddress value in the index identifies
2000
+ the network layer address of the server in the transaction
2001
+ represented by this entry.
2002
+ The apmNameClientID value in the index identifies the
2003
+ client in the transaction represented by this entry.
2004
+
2005
+ An example of the indexing of this entry is
2006
+ apmTransactionCount.3.1.8.4.192.168.1.2.3232235788.2987
2007
+
2008
+ Note that some combinations of index values may result in an
2009
+ index that exceeds 128 sub-identifiers in length which exceeds
2010
+ the maximum for the SNMP protocol. Implementations should take
2011
+ care to avoid such combinations.""",
2012
+ }, # row
2013
+ "apmTransactionServerAddress" : {
2014
+ "nodetype" : "column",
2015
+ "moduleName" : "APM-MIB",
2016
+ "oid" : "1.3.6.1.2.1.16.23.1.11.1.1",
2017
+ "status" : "current",
2018
+ "syntax" : {
2019
+ "type" : {
2020
+ "basetype" : "OctetString",
2021
+ "parent module" : {
2022
+ "name" : "APM-MIB",
2023
+ "type" : "ProtocolDirNetworkAddress",
2024
+ },
2025
+ "ranges" : [
2026
+ {
2027
+ "min" : "1",
2028
+ "max" : "255"
2029
+ },
2030
+ ],
2031
+ "range" : {
2032
+ "min" : "1",
2033
+ "max" : "255"
2034
+ },
2035
+ },
2036
+ },
2037
+ "access" : "noaccess",
2038
+ "description" :
2039
+ """The network server address for this apmTransactionEntry.
2040
+
2041
+ This is represented as an octet string with specific semantics
2042
+ and length as identified by the protocolDirLocalIndex
2043
+ component of the index. This object may not be the zero length
2044
+ string.
2045
+
2046
+ For example, if the protocolDirLocalIndex indicates an
2047
+ encapsulation of ip, this object is encoded as a length octet
2048
+ of 4, followed by the 4 octets of the ip address, in network
2049
+ byte order. Care should be taken to avoid values of this
2050
+ object that, in conjunction with the other index variables,
2051
+ would result in an index longer than SNMP's maximum of 128
2052
+ subidentifiers.""",
2053
+ }, # column
2054
+ "apmTransactionID" : {
2055
+ "nodetype" : "column",
2056
+ "moduleName" : "APM-MIB",
2057
+ "oid" : "1.3.6.1.2.1.16.23.1.11.1.2",
2058
+ "status" : "current",
2059
+ "syntax" : {
2060
+ "type" : {
2061
+ "basetype" : "Unsigned32",
2062
+ "ranges" : [
2063
+ {
2064
+ "min" : "0",
2065
+ "max" : "4294967295"
2066
+ },
2067
+ ],
2068
+ "range" : {
2069
+ "min" : "0",
2070
+ "max" : "4294967295"
2071
+ },
2072
+ },
2073
+ },
2074
+ "access" : "noaccess",
2075
+ "description" :
2076
+ """A unique value for this transaction amongst other
2077
+ transactions sharing the same application layer protocol and
2078
+ server and client addresses. Implementations may choose to use
2079
+ the value of the client's source port, when possible.""",
2080
+ }, # column
2081
+ "apmTransactionResponsiveness" : {
2082
+ "nodetype" : "column",
2083
+ "moduleName" : "APM-MIB",
2084
+ "oid" : "1.3.6.1.2.1.16.23.1.11.1.3",
2085
+ "status" : "current",
2086
+ "syntax" : {
2087
+ "type" : { "module" :"", "name" : "Unsigned32"},
2088
+ },
2089
+ "access" : "readonly",
2090
+ "description" :
2091
+ """The current value of the responsiveness metric for this
2092
+ transaction. If this transaction has completed, the final
2093
+ value of the metric will be available.
2094
+
2095
+ Note that this value may change over the lifetime of the
2096
+ transaction and it is the final value of this metric that is
2097
+ recorded as the responsiveness of the transaction for use in
2098
+ other APM MIB functions.""",
2099
+ }, # column
2100
+ "apmTransactionAge" : {
2101
+ "nodetype" : "column",
2102
+ "moduleName" : "APM-MIB",
2103
+ "oid" : "1.3.6.1.2.1.16.23.1.11.1.4",
2104
+ "status" : "current",
2105
+ "syntax" : {
2106
+ "type" : { "module" :"SNMPv2-TC", "name" : "TimeInterval"},
2107
+ },
2108
+ "access" : "readonly",
2109
+ "description" :
2110
+ """If this transaction is still executing, this value shall be
2111
+
2112
+
2113
+
2114
+ the length of time since it was started. If it has completed,
2115
+ this value shall be the length of time it was executing.""",
2116
+ }, # column
2117
+ "apmTransactionSuccess" : {
2118
+ "nodetype" : "column",
2119
+ "moduleName" : "APM-MIB",
2120
+ "oid" : "1.3.6.1.2.1.16.23.1.11.1.5",
2121
+ "status" : "current",
2122
+ "syntax" : {
2123
+ "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
2124
+ },
2125
+ "access" : "readonly",
2126
+ "description" :
2127
+ """The success of this transaction up to this time. Once a
2128
+ transaction has been marked as failed, it cannot move back
2129
+ into the successful state.""",
2130
+ }, # column
2131
+ "apmTransactionsRequestedHistorySize" : {
2132
+ "nodetype" : "scalar",
2133
+ "moduleName" : "APM-MIB",
2134
+ "oid" : "1.3.6.1.2.1.16.23.1.12",
2135
+ "status" : "current",
2136
+ "syntax" : {
2137
+ "type" : { "module" :"", "name" : "Unsigned32"},
2138
+ },
2139
+ "access" : "readwrite",
2140
+ "description" :
2141
+ """The maximum number of completed transactions desired to be
2142
+ retained in the apmTransactionTable. If the agent doesn't have
2143
+ enough resources to retain this many, it will retain as many as
2144
+ possible. Regardless of this value, the agent must attempt to
2145
+ keep records for all current transactions it is monitoring.
2146
+
2147
+ The value of this object must persist across reboots.""",
2148
+ }, # scalar
2149
+ "apmExceptionTable" : {
2150
+ "nodetype" : "table",
2151
+ "moduleName" : "APM-MIB",
2152
+ "oid" : "1.3.6.1.2.1.16.23.1.13",
2153
+ "status" : "current",
2154
+ "description" :
2155
+ """This table creates filters so that a management station can
2156
+ get immediate notification of a transaction that has had poor
2157
+
2158
+
2159
+
2160
+ availability or responsiveness.
2161
+
2162
+ Each apmExceptionEntry is associated with a particular type of
2163
+ transaction and is applied to all transactions of that
2164
+ type. Multiple apmExceptionEntries may be associated with a
2165
+ particular type of transaction. A transaction type is
2166
+ identified by the value of the apmAppDirAppLocalIndex
2167
+ component of the index.
2168
+
2169
+ Because the quality of a transaction is not known until it is
2170
+ completed, these thresholds are only applied after the
2171
+ transaction has completed.""",
2172
+ }, # table
2173
+ "apmExceptionEntry" : {
2174
+ "nodetype" : "row",
2175
+ "moduleName" : "APM-MIB",
2176
+ "oid" : "1.3.6.1.2.1.16.23.1.13.1",
2177
+ "create" : "true",
2178
+ "status" : "current",
2179
+ "linkage" : [
2180
+ "apmAppDirAppLocalIndex",
2181
+ "apmAppDirResponsivenessType",
2182
+ "apmExceptionIndex",
2183
+ ],
2184
+ "description" :
2185
+ """A conceptual row in the apmExceptionTable.
2186
+
2187
+ The apmAppDirAppLocalIndex value in the index identifies
2188
+ the application this entry will monitor.
2189
+ The apmAppDirResponsivenessType value in the index
2190
+ identifies the type of responsiveness metric this entry will
2191
+ monitor.""",
2192
+ }, # row
2193
+ "apmExceptionIndex" : {
2194
+ "nodetype" : "column",
2195
+ "moduleName" : "APM-MIB",
2196
+ "oid" : "1.3.6.1.2.1.16.23.1.13.1.1",
2197
+ "status" : "current",
2198
+ "syntax" : {
2199
+ "type" : {
2200
+ "basetype" : "Unsigned32",
2201
+ "ranges" : [
2202
+ {
2203
+ "min" : "1",
2204
+ "max" : "65535"
2205
+ },
2206
+ ],
2207
+ "range" : {
2208
+ "min" : "1",
2209
+ "max" : "65535"
2210
+ },
2211
+ },
2212
+ },
2213
+ "access" : "noaccess",
2214
+ "description" :
2215
+ """An index that uniquely identifies an entry in the
2216
+ apmExceptionTable amongst other entries with equivalent index
2217
+ values for apmAppDirAppLocalIndex and
2218
+ apmAppDirResponsivenessType. Each such entry sets up
2219
+ thresholds for a particular measurement of a particular
2220
+ application.""",
2221
+ }, # column
2222
+ "apmExceptionResponsivenessComparison" : {
2223
+ "nodetype" : "column",
2224
+ "moduleName" : "APM-MIB",
2225
+ "oid" : "1.3.6.1.2.1.16.23.1.13.1.2",
2226
+ "status" : "current",
2227
+ "syntax" : {
2228
+ "type" : {
2229
+ "basetype" : "Enumeration",
2230
+ "none" : {
2231
+ "nodetype" : "namednumber",
2232
+ "number" : "1"
2233
+ },
2234
+ "greater" : {
2235
+ "nodetype" : "namednumber",
2236
+ "number" : "2"
2237
+ },
2238
+ "less" : {
2239
+ "nodetype" : "namednumber",
2240
+ "number" : "3"
2241
+ },
2242
+ },
2243
+ },
2244
+ "access" : "readwrite",
2245
+ "description" :
2246
+ """If this value is greater(2) or less(3), the associated
2247
+ apmExceptionResponsivenessThreshold will be compared to this
2248
+ value and an exception will be created if the responsiveness
2249
+ is greater than the threshold (greater(2)) or less than the
2250
+ threshold (less(3)).""",
2251
+ }, # column
2252
+ "apmExceptionResponsivenessThreshold" : {
2253
+ "nodetype" : "column",
2254
+ "moduleName" : "APM-MIB",
2255
+ "oid" : "1.3.6.1.2.1.16.23.1.13.1.3",
2256
+ "status" : "current",
2257
+ "syntax" : {
2258
+ "type" : { "module" :"", "name" : "Unsigned32"},
2259
+ },
2260
+ "access" : "readwrite",
2261
+ "description" :
2262
+ """The threshold that responsiveness metrics are compared to.""",
2263
+ }, # column
2264
+ "apmExceptionUnsuccessfulException" : {
2265
+ "nodetype" : "column",
2266
+ "moduleName" : "APM-MIB",
2267
+ "oid" : "1.3.6.1.2.1.16.23.1.13.1.4",
2268
+ "status" : "current",
2269
+ "syntax" : {
2270
+ "type" : {
2271
+ "basetype" : "Enumeration",
2272
+ "off" : {
2273
+ "nodetype" : "namednumber",
2274
+ "number" : "1"
2275
+ },
2276
+ "on" : {
2277
+ "nodetype" : "namednumber",
2278
+ "number" : "2"
2279
+ },
2280
+ },
2281
+ },
2282
+ "access" : "readwrite",
2283
+ "description" :
2284
+ """If this value is on(2), an exception will be created if a
2285
+ transaction of the associated type is unsuccessful.""",
2286
+ }, # column
2287
+ "apmExceptionResponsivenessEvents" : {
2288
+ "nodetype" : "column",
2289
+ "moduleName" : "APM-MIB",
2290
+ "oid" : "1.3.6.1.2.1.16.23.1.13.1.5",
2291
+ "status" : "current",
2292
+ "syntax" : {
2293
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
2294
+ },
2295
+ "access" : "readonly",
2296
+ "description" :
2297
+ """The total number of responsiveness exceptions generated. This
2298
+ counter will be incremented even if no notification was sent
2299
+ due to notifications not being configured or due to exceeding
2300
+ the apmNotificationMaxRate value.""",
2301
+ }, # column
2302
+ "apmExceptionUnsuccessfulEvents" : {
2303
+ "nodetype" : "column",
2304
+ "moduleName" : "APM-MIB",
2305
+ "oid" : "1.3.6.1.2.1.16.23.1.13.1.6",
2306
+ "status" : "current",
2307
+ "syntax" : {
2308
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
2309
+ },
2310
+ "access" : "readonly",
2311
+ "description" :
2312
+ """The total number of unsuccessful exceptions generated. This
2313
+ counter will be incremented even if no notification was sent
2314
+ due to notifications not being configured or due to exceeding
2315
+ the apmNotificationMaxRate value.""",
2316
+ }, # column
2317
+ "apmExceptionOwner" : {
2318
+ "nodetype" : "column",
2319
+ "moduleName" : "APM-MIB",
2320
+ "oid" : "1.3.6.1.2.1.16.23.1.13.1.7",
2321
+ "status" : "current",
2322
+ "syntax" : {
2323
+ "type" : { "module" :"RMON-MIB", "name" : "OwnerString"},
2324
+ },
2325
+ "access" : "readwrite",
2326
+ "description" :
2327
+ """The entity that configured this entry and is
2328
+ therefore using the resources assigned to it.""",
2329
+ }, # column
2330
+ "apmExceptionStorageType" : {
2331
+ "nodetype" : "column",
2332
+ "moduleName" : "APM-MIB",
2333
+ "oid" : "1.3.6.1.2.1.16.23.1.13.1.8",
2334
+ "status" : "current",
2335
+ "syntax" : {
2336
+ "type" : { "module" :"SNMPv2-TC", "name" : "StorageType"},
2337
+ },
2338
+ "access" : "readwrite",
2339
+ "description" :
2340
+ """The storage type of this apmReportControlEntry. If the value
2341
+ of this object is 'permanent', no objects in this row need to
2342
+ be writable.""",
2343
+ }, # column
2344
+ "apmExceptionStatus" : {
2345
+ "nodetype" : "column",
2346
+ "moduleName" : "APM-MIB",
2347
+ "oid" : "1.3.6.1.2.1.16.23.1.13.1.9",
2348
+ "status" : "current",
2349
+ "syntax" : {
2350
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
2351
+ },
2352
+ "access" : "readwrite",
2353
+ "description" :
2354
+ """The status of this apmExceptionEntry. The only objects in the
2355
+ entry that may be modified while the entry is in the active
2356
+ state are apmExceptionResponsivenessComparison,
2357
+ apmExceptionResponsivenessThreshold and
2358
+ apmExceptionUnsuccessfulException.""",
2359
+ }, # column
2360
+ "apmThroughputExceptionMinTime" : {
2361
+ "nodetype" : "scalar",
2362
+ "moduleName" : "APM-MIB",
2363
+ "oid" : "1.3.6.1.2.1.16.23.1.14",
2364
+ "status" : "current",
2365
+ "syntax" : {
2366
+ "type" : { "module" :"", "name" : "Unsigned32"},
2367
+ },
2368
+ "access" : "readwrite",
2369
+ "default" : "10",
2370
+ "units" : "seconds",
2371
+ "description" :
2372
+ """Because the responsiveness for throughput-oriented
2373
+ transactions is divided by the elapsed time, it can be very
2374
+ sensitive to short-term performance variations for
2375
+ transactions that take a short period of time. For example,
2376
+ when downloading a very short file, a single dropped packet
2377
+ could double or triple the total response time.
2378
+
2379
+ Further, throughput is usually examined for applications that
2380
+ transfer a lot of data, and when doing so it is helpful to
2381
+ conceptualize transaction costs that are proportional to the
2382
+ amount of data separately from those costs that are relatively
2383
+ fixed (i.e., independent of the amount of data). For very
2384
+ short transactions, these fixed transaction costs (handshake,
2385
+ setup time, authentication, round-trip time) may dominate the
2386
+ total response time for the transaction, resulting in
2387
+ throughput measurements that aren't really proportional to the
2388
+ network's, server's and client's combined data throughput
2389
+ capability.
2390
+
2391
+ This object controls the minimum number of seconds that an
2392
+ throughput-based transaction must exceed before an exception
2393
+ can be generated for it. If this object is set to zero, then
2394
+ all throughput-based transactions are candidates for
2395
+ exceptions.
2396
+
2397
+ The value of this object must persist across reboots.""",
2398
+ }, # scalar
2399
+ "apmNotificationMaxRate" : {
2400
+ "nodetype" : "scalar",
2401
+ "moduleName" : "APM-MIB",
2402
+ "oid" : "1.3.6.1.2.1.16.23.1.15",
2403
+ "status" : "current",
2404
+ "syntax" : {
2405
+ "type" : { "module" :"", "name" : "Unsigned32"},
2406
+ },
2407
+ "access" : "readwrite",
2408
+ "default" : "1",
2409
+ "description" :
2410
+ """The maximum number of notifications that can be generated
2411
+ from this agent by the apmExceptionTable in any 60 second
2412
+ period.
2413
+
2414
+ The value of this object must persist across reboots.""",
2415
+ }, # scalar
2416
+ "apmConformance" : {
2417
+ "nodetype" : "node",
2418
+ "moduleName" : "APM-MIB",
2419
+ "oid" : "1.3.6.1.2.1.16.23.2",
2420
+ }, # node
2421
+ "apmCompliances" : {
2422
+ "nodetype" : "node",
2423
+ "moduleName" : "APM-MIB",
2424
+ "oid" : "1.3.6.1.2.1.16.23.2.1",
2425
+ }, # node
2426
+ "apmGroups" : {
2427
+ "nodetype" : "node",
2428
+ "moduleName" : "APM-MIB",
2429
+ "oid" : "1.3.6.1.2.1.16.23.2.2",
2430
+ }, # node
2431
+ }, # nodes
2432
+
2433
+ "notifications" : {
2434
+ "apmTransactionResponsivenessAlarm" : {
2435
+ "nodetype" : "notification",
2436
+ "moduleName" : "APM-MIB",
2437
+ "oid" : "1.3.6.1.2.1.16.23.0.1",
2438
+ "status" : "current",
2439
+ "objects" : {
2440
+ "apmExceptionResponsivenessThreshold" : {
2441
+ "nodetype" : "object",
2442
+ "module" : "APM-MIB"
2443
+ },
2444
+ "apmTransactionResponsiveness" : {
2445
+ "nodetype" : "object",
2446
+ "module" : "APM-MIB"
2447
+ },
2448
+ },
2449
+ "description" :
2450
+ """Notification sent when a transaction exceeds a threshold
2451
+ defined in the apmException table. The index of the
2452
+ included apmExceptionResponsivenessThreshold object identifies
2453
+ the apmExceptionEntry that specified the threshold. The
2454
+ apmTransactionResponsiveness variable identifies the actual
2455
+ transaction and its responsiveness.
2456
+
2457
+ Agent implementors are urged to include additional data
2458
+ objects in the alarm that may explain the reason for the
2459
+ alarm. It is helpful to include such data in the alarm because
2460
+ it describes the situation at the time the alarm was
2461
+ generated, where polls after the fact may not provide
2462
+ meaningful information. Examples of such information are CPU
2463
+ load, memory utilization, network utilization, and transaction
2464
+ statistics.""",
2465
+ }, # notification
2466
+ "apmTransactionUnsuccessfulAlarm" : {
2467
+ "nodetype" : "notification",
2468
+ "moduleName" : "APM-MIB",
2469
+ "oid" : "1.3.6.1.2.1.16.23.0.2",
2470
+ "status" : "current",
2471
+ "objects" : {
2472
+ "apmExceptionResponsivenessThreshold" : {
2473
+ "nodetype" : "object",
2474
+ "module" : "APM-MIB"
2475
+ },
2476
+ },
2477
+ "description" :
2478
+ """Notification sent when a transaction is unsuccessful.
2479
+ The index of the included apmExceptionResponsivenessThreshold
2480
+ object identifies both the type of the transaction that caused
2481
+ this notification as well as the apmExceptionEntry that
2482
+ specified the threshold.
2483
+
2484
+ Agent implementors are urged to include additional data
2485
+ objects in the alarm that may explain the reason for the
2486
+ alarm. It is helpful to include such data in the alarm because
2487
+ it describes the situation at the time the alarm was
2488
+ generated, where polls after the fact may not provide
2489
+ meaningful information. Examples of such information are CPU
2490
+ load, memory utilization, network utilization, and transaction
2491
+ statistics.""",
2492
+ }, # notification
2493
+ }, # notifications
2494
+
2495
+ "groups" : {
2496
+ "apmAppDirGroup" : {
2497
+ "nodetype" : "group",
2498
+ "moduleName" : "APM-MIB",
2499
+ "oid" : "1.3.6.1.2.1.16.23.2.2.1",
2500
+ "status" : "current",
2501
+ "members" : {
2502
+ "apmAppDirConfig" : {
2503
+ "nodetype" : "member",
2504
+ "module" : "APM-MIB"
2505
+ },
2506
+ "apmAppDirResponsivenessBoundary1" : {
2507
+ "nodetype" : "member",
2508
+ "module" : "APM-MIB"
2509
+ },
2510
+ "apmAppDirResponsivenessBoundary2" : {
2511
+ "nodetype" : "member",
2512
+ "module" : "APM-MIB"
2513
+ },
2514
+ "apmAppDirResponsivenessBoundary3" : {
2515
+ "nodetype" : "member",
2516
+ "module" : "APM-MIB"
2517
+ },
2518
+ "apmAppDirResponsivenessBoundary4" : {
2519
+ "nodetype" : "member",
2520
+ "module" : "APM-MIB"
2521
+ },
2522
+ "apmAppDirResponsivenessBoundary5" : {
2523
+ "nodetype" : "member",
2524
+ "module" : "APM-MIB"
2525
+ },
2526
+ "apmAppDirResponsivenessBoundary6" : {
2527
+ "nodetype" : "member",
2528
+ "module" : "APM-MIB"
2529
+ },
2530
+ "apmBucketBoundaryLastChange" : {
2531
+ "nodetype" : "member",
2532
+ "module" : "APM-MIB"
2533
+ },
2534
+ "apmAppDirID" : {
2535
+ "nodetype" : "member",
2536
+ "module" : "APM-MIB"
2537
+ },
2538
+ "apmNameMachineName" : {
2539
+ "nodetype" : "member",
2540
+ "module" : "APM-MIB"
2541
+ },
2542
+ "apmNameUserName" : {
2543
+ "nodetype" : "member",
2544
+ "module" : "APM-MIB"
2545
+ },
2546
+ }, # members
2547
+ "description" :
2548
+ """The APM MIB directory of applications and application verbs.""",
2549
+ }, # group
2550
+ "apmUserDefinedApplicationsGroup" : {
2551
+ "nodetype" : "group",
2552
+ "moduleName" : "APM-MIB",
2553
+ "oid" : "1.3.6.1.2.1.16.23.2.2.2",
2554
+ "status" : "current",
2555
+ "members" : {
2556
+ "apmHttpFilterAppLocalIndex" : {
2557
+ "nodetype" : "member",
2558
+ "module" : "APM-MIB"
2559
+ },
2560
+ "apmHttpFilterServerProtocol" : {
2561
+ "nodetype" : "member",
2562
+ "module" : "APM-MIB"
2563
+ },
2564
+ "apmHttpFilterServerAddress" : {
2565
+ "nodetype" : "member",
2566
+ "module" : "APM-MIB"
2567
+ },
2568
+ "apmHttpFilterURLPath" : {
2569
+ "nodetype" : "member",
2570
+ "module" : "APM-MIB"
2571
+ },
2572
+ "apmHttpFilterMatchType" : {
2573
+ "nodetype" : "member",
2574
+ "module" : "APM-MIB"
2575
+ },
2576
+ "apmHttpFilterOwner" : {
2577
+ "nodetype" : "member",
2578
+ "module" : "APM-MIB"
2579
+ },
2580
+ "apmHttpFilterStorageType" : {
2581
+ "nodetype" : "member",
2582
+ "module" : "APM-MIB"
2583
+ },
2584
+ "apmHttpFilterRowStatus" : {
2585
+ "nodetype" : "member",
2586
+ "module" : "APM-MIB"
2587
+ },
2588
+ "apmHttpIgnoreUnregisteredURLs" : {
2589
+ "nodetype" : "member",
2590
+ "module" : "APM-MIB"
2591
+ },
2592
+ "apmHttp4xxIsFailure" : {
2593
+ "nodetype" : "member",
2594
+ "module" : "APM-MIB"
2595
+ },
2596
+ "apmUserDefinedAppParentIndex" : {
2597
+ "nodetype" : "member",
2598
+ "module" : "APM-MIB"
2599
+ },
2600
+ "apmUserDefinedAppApplication" : {
2601
+ "nodetype" : "member",
2602
+ "module" : "APM-MIB"
2603
+ },
2604
+ }, # members
2605
+ "description" :
2606
+ """Objects used for creating and managing user-defined
2607
+ applications.""",
2608
+ }, # group
2609
+ "apmReportGroup" : {
2610
+ "nodetype" : "group",
2611
+ "moduleName" : "APM-MIB",
2612
+ "oid" : "1.3.6.1.2.1.16.23.2.2.3",
2613
+ "status" : "current",
2614
+ "members" : {
2615
+ "apmReportControlDataSource" : {
2616
+ "nodetype" : "member",
2617
+ "module" : "APM-MIB"
2618
+ },
2619
+ "apmReportControlAggregationType" : {
2620
+ "nodetype" : "member",
2621
+ "module" : "APM-MIB"
2622
+ },
2623
+ "apmReportControlInterval" : {
2624
+ "nodetype" : "member",
2625
+ "module" : "APM-MIB"
2626
+ },
2627
+ "apmReportControlRequestedSize" : {
2628
+ "nodetype" : "member",
2629
+ "module" : "APM-MIB"
2630
+ },
2631
+ "apmReportControlGrantedSize" : {
2632
+ "nodetype" : "member",
2633
+ "module" : "APM-MIB"
2634
+ },
2635
+ "apmReportControlRequestedReports" : {
2636
+ "nodetype" : "member",
2637
+ "module" : "APM-MIB"
2638
+ },
2639
+ "apmReportControlGrantedReports" : {
2640
+ "nodetype" : "member",
2641
+ "module" : "APM-MIB"
2642
+ },
2643
+ "apmReportControlStartTime" : {
2644
+ "nodetype" : "member",
2645
+ "module" : "APM-MIB"
2646
+ },
2647
+ "apmReportControlReportNumber" : {
2648
+ "nodetype" : "member",
2649
+ "module" : "APM-MIB"
2650
+ },
2651
+ "apmReportControlDeniedInserts" : {
2652
+ "nodetype" : "member",
2653
+ "module" : "APM-MIB"
2654
+ },
2655
+ "apmReportControlDroppedFrames" : {
2656
+ "nodetype" : "member",
2657
+ "module" : "APM-MIB"
2658
+ },
2659
+ "apmReportControlOwner" : {
2660
+ "nodetype" : "member",
2661
+ "module" : "APM-MIB"
2662
+ },
2663
+ "apmReportControlStorageType" : {
2664
+ "nodetype" : "member",
2665
+ "module" : "APM-MIB"
2666
+ },
2667
+ "apmReportControlStatus" : {
2668
+ "nodetype" : "member",
2669
+ "module" : "APM-MIB"
2670
+ },
2671
+ "apmReportTransactionCount" : {
2672
+ "nodetype" : "member",
2673
+ "module" : "APM-MIB"
2674
+ },
2675
+ "apmReportSuccessfulTransactions" : {
2676
+ "nodetype" : "member",
2677
+ "module" : "APM-MIB"
2678
+ },
2679
+ "apmReportResponsivenessMean" : {
2680
+ "nodetype" : "member",
2681
+ "module" : "APM-MIB"
2682
+ },
2683
+ "apmReportResponsivenessMin" : {
2684
+ "nodetype" : "member",
2685
+ "module" : "APM-MIB"
2686
+ },
2687
+ "apmReportResponsivenessMax" : {
2688
+ "nodetype" : "member",
2689
+ "module" : "APM-MIB"
2690
+ },
2691
+ "apmReportResponsivenessB1" : {
2692
+ "nodetype" : "member",
2693
+ "module" : "APM-MIB"
2694
+ },
2695
+ "apmReportResponsivenessB2" : {
2696
+ "nodetype" : "member",
2697
+ "module" : "APM-MIB"
2698
+ },
2699
+ "apmReportResponsivenessB3" : {
2700
+ "nodetype" : "member",
2701
+ "module" : "APM-MIB"
2702
+ },
2703
+ "apmReportResponsivenessB4" : {
2704
+ "nodetype" : "member",
2705
+ "module" : "APM-MIB"
2706
+ },
2707
+ "apmReportResponsivenessB5" : {
2708
+ "nodetype" : "member",
2709
+ "module" : "APM-MIB"
2710
+ },
2711
+ "apmReportResponsivenessB6" : {
2712
+ "nodetype" : "member",
2713
+ "module" : "APM-MIB"
2714
+ },
2715
+ "apmReportResponsivenessB7" : {
2716
+ "nodetype" : "member",
2717
+ "module" : "APM-MIB"
2718
+ },
2719
+ }, # members
2720
+ "description" :
2721
+ """The apm report group controls the creation and retrieval of
2722
+ reports that aggregate application performance.""",
2723
+ }, # group
2724
+ "apmTransactionGroup" : {
2725
+ "nodetype" : "group",
2726
+ "moduleName" : "APM-MIB",
2727
+ "oid" : "1.3.6.1.2.1.16.23.2.2.4",
2728
+ "status" : "current",
2729
+ "members" : {
2730
+ "apmTransactionResponsiveness" : {
2731
+ "nodetype" : "member",
2732
+ "module" : "APM-MIB"
2733
+ },
2734
+ "apmTransactionAge" : {
2735
+ "nodetype" : "member",
2736
+ "module" : "APM-MIB"
2737
+ },
2738
+ "apmTransactionSuccess" : {
2739
+ "nodetype" : "member",
2740
+ "module" : "APM-MIB"
2741
+ },
2742
+ "apmTransactionsRequestedHistorySize" : {
2743
+ "nodetype" : "member",
2744
+ "module" : "APM-MIB"
2745
+ },
2746
+ }, # members
2747
+ "description" :
2748
+ """The apm transaction group contains statistics for
2749
+ individual transactions.""",
2750
+ }, # group
2751
+ "apmExceptionGroup" : {
2752
+ "nodetype" : "group",
2753
+ "moduleName" : "APM-MIB",
2754
+ "oid" : "1.3.6.1.2.1.16.23.2.2.5",
2755
+ "status" : "current",
2756
+ "members" : {
2757
+ "apmExceptionResponsivenessComparison" : {
2758
+ "nodetype" : "member",
2759
+ "module" : "APM-MIB"
2760
+ },
2761
+ "apmExceptionResponsivenessThreshold" : {
2762
+ "nodetype" : "member",
2763
+ "module" : "APM-MIB"
2764
+ },
2765
+ "apmExceptionUnsuccessfulException" : {
2766
+ "nodetype" : "member",
2767
+ "module" : "APM-MIB"
2768
+ },
2769
+ "apmExceptionResponsivenessEvents" : {
2770
+ "nodetype" : "member",
2771
+ "module" : "APM-MIB"
2772
+ },
2773
+ "apmExceptionUnsuccessfulEvents" : {
2774
+ "nodetype" : "member",
2775
+ "module" : "APM-MIB"
2776
+ },
2777
+ "apmExceptionOwner" : {
2778
+ "nodetype" : "member",
2779
+ "module" : "APM-MIB"
2780
+ },
2781
+ "apmExceptionStorageType" : {
2782
+ "nodetype" : "member",
2783
+ "module" : "APM-MIB"
2784
+ },
2785
+ "apmExceptionStatus" : {
2786
+ "nodetype" : "member",
2787
+ "module" : "APM-MIB"
2788
+ },
2789
+ "apmThroughputExceptionMinTime" : {
2790
+ "nodetype" : "member",
2791
+ "module" : "APM-MIB"
2792
+ },
2793
+ "apmNotificationMaxRate" : {
2794
+ "nodetype" : "member",
2795
+ "module" : "APM-MIB"
2796
+ },
2797
+ }, # members
2798
+ "description" :
2799
+ """The apm exception group causes notifications to be sent
2800
+ whenever transactions are detected that had poor availability
2801
+ or responsiveness.""",
2802
+ }, # group
2803
+ "apmNotificationGroup" : {
2804
+ "nodetype" : "group",
2805
+ "moduleName" : "APM-MIB",
2806
+ "oid" : "1.3.6.1.2.1.16.23.2.2.6",
2807
+ "status" : "current",
2808
+ "members" : {
2809
+ "apmTransactionResponsivenessAlarm" : {
2810
+ "nodetype" : "member",
2811
+ "module" : "APM-MIB"
2812
+ },
2813
+ "apmTransactionUnsuccessfulAlarm" : {
2814
+ "nodetype" : "member",
2815
+ "module" : "APM-MIB"
2816
+ },
2817
+ }, # members
2818
+ "description" :
2819
+ """Notifications sent by an APM MIB agent.""",
2820
+ }, # group
2821
+ }, # groups
2822
+
2823
+ "compliances" : {
2824
+ "apmCompliance" : {
2825
+ "nodetype" : "compliance",
2826
+ "moduleName" : "APM-MIB",
2827
+ "oid" : "1.3.6.1.2.1.16.23.2.1.1",
2828
+ "status" : "current",
2829
+ "description" :
2830
+ """Describes the requirements for conformance to
2831
+ the APM MIB""",
2832
+ "requires" : {
2833
+ "apmAppDirGroup" : {
2834
+ "nodetype" : "mandatory",
2835
+ "module" : "APM-MIB"
2836
+ },
2837
+ "apmReportGroup" : {
2838
+ "nodetype" : "mandatory",
2839
+ "module" : "APM-MIB"
2840
+ },
2841
+ "apmUserDefinedApplicationsGroup" : {
2842
+ "nodetype" : "optional",
2843
+ "module" : "APM-MIB",
2844
+ "description" :
2845
+ """Implementation of the apmUserDefinedApplicationsGroup
2846
+ is optional.""",
2847
+ },
2848
+ "apmTransactionGroup" : {
2849
+ "nodetype" : "optional",
2850
+ "module" : "APM-MIB",
2851
+ "description" :
2852
+ """Implementation of the apmTransactionGroup is optional.""",
2853
+ },
2854
+ "apmExceptionGroup" : {
2855
+ "nodetype" : "optional",
2856
+ "module" : "APM-MIB",
2857
+ "description" :
2858
+ """Implementation of the apmExceptionGroup is optional.""",
2859
+ },
2860
+ "apmNotificationGroup" : {
2861
+ "nodetype" : "optional",
2862
+ "module" : "APM-MIB",
2863
+ "description" :
2864
+ """Implementation of the apmNotificationGroup is optional.""",
2865
+ },
2866
+ }, # requires
2867
+ }, # compliance
2868
+ }, # compliances
2869
+
2870
+ }