logstash-integration-snmp 4.0.0-java

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (324) hide show
  1. checksums.yaml +7 -0
  2. data/CHANGELOG.md +23 -0
  3. data/CONTRIBUTORS +20 -0
  4. data/Gemfile +11 -0
  5. data/LICENSE +202 -0
  6. data/README.md +89 -0
  7. data/VERSION +1 -0
  8. data/docs/index.asciidoc +202 -0
  9. data/docs/input-snmp.asciidoc +524 -0
  10. data/docs/input-snmptrap.asciidoc +392 -0
  11. data/lib/logstash/inputs/snmp.rb +369 -0
  12. data/lib/logstash/inputs/snmptrap.rb +190 -0
  13. data/lib/logstash/plugin_mixins/snmp/common.rb +197 -0
  14. data/lib/logstash-integration-snmp_jars.rb +6 -0
  15. data/lib/mibs/ietf/ACCOUNTING-CONTROL-MIB.dic +1316 -0
  16. data/lib/mibs/ietf/ADSL-LINE-EXT-MIB.dic +1724 -0
  17. data/lib/mibs/ietf/ADSL-LINE-MIB.dic +7297 -0
  18. data/lib/mibs/ietf/ADSL-TC-MIB.dic +160 -0
  19. data/lib/mibs/ietf/ADSL2-LINE-MIB.dic +8663 -0
  20. data/lib/mibs/ietf/ADSL2-LINE-TC-MIB.dic +1462 -0
  21. data/lib/mibs/ietf/AGENTX-MIB.dic +817 -0
  22. data/lib/mibs/ietf/AGGREGATE-MIB.dic +708 -0
  23. data/lib/mibs/ietf/ALARM-MIB.dic +1734 -0
  24. data/lib/mibs/ietf/APM-MIB.dic +2870 -0
  25. data/lib/mibs/ietf/APPC-MIB.dic +8687 -0
  26. data/lib/mibs/ietf/APPLETALK-MIB.dic +4399 -0
  27. data/lib/mibs/ietf/APPLICATION-MIB.dic +3750 -0
  28. data/lib/mibs/ietf/APPN-DLUR-MIB.dic +972 -0
  29. data/lib/mibs/ietf/APPN-MIB.dic +9364 -0
  30. data/lib/mibs/ietf/APPN-TRAP-MIB.dic +664 -0
  31. data/lib/mibs/ietf/APS-MIB.dic +2430 -0
  32. data/lib/mibs/ietf/ARC-MIB.dic +552 -0
  33. data/lib/mibs/ietf/ATM-ACCOUNTING-INFORMATION-MIB.dic +816 -0
  34. data/lib/mibs/ietf/ATM-MIB.dic +4104 -0
  35. data/lib/mibs/ietf/ATM-TC-MIB.dic +914 -0
  36. data/lib/mibs/ietf/ATM2-MIB.dic +4715 -0
  37. data/lib/mibs/ietf/BFD-STD-MIB.dic +2367 -0
  38. data/lib/mibs/ietf/BFD-TC-STD-MIB.dic +202 -0
  39. data/lib/mibs/ietf/BGP4-MIB.dic +1931 -0
  40. data/lib/mibs/ietf/BLDG-HVAC-MIB.dic +812 -0
  41. data/lib/mibs/ietf/BRIDGE-MIB.dic +2257 -0
  42. data/lib/mibs/ietf/CAPWAP-BASE-MIB.dic +4128 -0
  43. data/lib/mibs/ietf/CAPWAP-DOT11-MIB.dic +482 -0
  44. data/lib/mibs/ietf/CHARACTER-MIB.dic +1140 -0
  45. data/lib/mibs/ietf/CIRCUIT-IF-MIB.dic +493 -0
  46. data/lib/mibs/ietf/CLNS-MIB.dic +1702 -0
  47. data/lib/mibs/ietf/COFFEE-POT-MIB.dic +282 -0
  48. data/lib/mibs/ietf/COPS-CLIENT-MIB.dic +1270 -0
  49. data/lib/mibs/ietf/DECNET-PHIV-MIB.dic +5837 -0
  50. data/lib/mibs/ietf/DIAL-CONTROL-MIB.dic +2139 -0
  51. data/lib/mibs/ietf/DIFFSERV-CONFIG-MIB.dic +378 -0
  52. data/lib/mibs/ietf/DIFFSERV-MIB.dic +5073 -0
  53. data/lib/mibs/ietf/DIRECTORY-SERVER-MIB.dic +1041 -0
  54. data/lib/mibs/ietf/DISMAN-EVENT-MIB.dic +3151 -0
  55. data/lib/mibs/ietf/DISMAN-EXPRESSION-MIB.dic +1716 -0
  56. data/lib/mibs/ietf/DISMAN-NSLOOKUP-MIB.dic +698 -0
  57. data/lib/mibs/ietf/DISMAN-PING-MIB.dic +2635 -0
  58. data/lib/mibs/ietf/DISMAN-SCHEDULE-MIB.dic +1744 -0
  59. data/lib/mibs/ietf/DISMAN-SCRIPT-MIB.dic +2820 -0
  60. data/lib/mibs/ietf/DISMAN-TRACEROUTE-MIB.dic +3239 -0
  61. data/lib/mibs/ietf/DLSW-MIB.dic +5635 -0
  62. data/lib/mibs/ietf/DNS-RESOLVER-MIB.dic +1765 -0
  63. data/lib/mibs/ietf/DNS-SERVER-MIB.dic +1593 -0
  64. data/lib/mibs/ietf/DOCS-BPI-MIB.dic +2634 -0
  65. data/lib/mibs/ietf/DOCS-CABLE-DEVICE-MIB.dic +5042 -0
  66. data/lib/mibs/ietf/DOCS-IETF-BPI2-MIB.dic +5478 -0
  67. data/lib/mibs/ietf/DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB.dic +2447 -0
  68. data/lib/mibs/ietf/DOCS-IETF-QOS-MIB.dic +4886 -0
  69. data/lib/mibs/ietf/DOCS-IETF-SUBMGT-MIB.dic +1331 -0
  70. data/lib/mibs/ietf/DOCS-IF-MIB.dic +7980 -0
  71. data/lib/mibs/ietf/DOT12-IF-MIB.dic +1066 -0
  72. data/lib/mibs/ietf/DOT12-RPTR-MIB.dic +2669 -0
  73. data/lib/mibs/ietf/DOT3-EPON-MIB.dic +3297 -0
  74. data/lib/mibs/ietf/DOT3-OAM-MIB.dic +2830 -0
  75. data/lib/mibs/ietf/DS0-MIB.dic +466 -0
  76. data/lib/mibs/ietf/DS0BUNDLE-MIB.dic +468 -0
  77. data/lib/mibs/ietf/DS1-MIB.dic +4890 -0
  78. data/lib/mibs/ietf/DS3-MIB.dic +2719 -0
  79. data/lib/mibs/ietf/DSA-MIB.dic +888 -0
  80. data/lib/mibs/ietf/DSMON-MIB.dic +6177 -0
  81. data/lib/mibs/ietf/DVB-RCS-MIB.dic +5764 -0
  82. data/lib/mibs/ietf/EBN-MIB.dic +1026 -0
  83. data/lib/mibs/ietf/EFM-CU-MIB.dic +4335 -0
  84. data/lib/mibs/ietf/ENTITY-MIB.dic +2235 -0
  85. data/lib/mibs/ietf/ENTITY-SENSOR-MIB.dic +653 -0
  86. data/lib/mibs/ietf/ENTITY-STATE-MIB.dic +457 -0
  87. data/lib/mibs/ietf/ENTITY-STATE-TC-MIB.dic +260 -0
  88. data/lib/mibs/ietf/ETHER-CHIPSET-MIB.dic +787 -0
  89. data/lib/mibs/ietf/EtherLike-MIB.dic +2548 -0
  90. data/lib/mibs/ietf/FC-MGMT-MIB.dic +3465 -0
  91. data/lib/mibs/ietf/FCIP-MGMT-MIB.dic +1596 -0
  92. data/lib/mibs/ietf/FDDI-SMT73-MIB.dic +3378 -0
  93. data/lib/mibs/ietf/FIBRE-CHANNEL-FE-MIB.dic +2504 -0
  94. data/lib/mibs/ietf/FLOAT-TC-MIB.dic +128 -0
  95. data/lib/mibs/ietf/FLOW-METER-MIB.dic +3201 -0
  96. data/lib/mibs/ietf/FORCES-MIB.dic +598 -0
  97. data/lib/mibs/ietf/FR-ATM-PVC-SERVICE-IWF-MIB.dic +1601 -0
  98. data/lib/mibs/ietf/FR-MFR-MIB.dic +1351 -0
  99. data/lib/mibs/ietf/FRAME-RELAY-DTE-MIB.dic +1688 -0
  100. data/lib/mibs/ietf/FRNETSERV-MIB.dic +3940 -0
  101. data/lib/mibs/ietf/FRSLD-MIB.dic +2580 -0
  102. data/lib/mibs/ietf/Finisher-MIB.dic +1416 -0
  103. data/lib/mibs/ietf/GMPLS-LABEL-STD-MIB.dic +965 -0
  104. data/lib/mibs/ietf/GMPLS-LSR-STD-MIB.dic +693 -0
  105. data/lib/mibs/ietf/GMPLS-TC-STD-MIB.dic +180 -0
  106. data/lib/mibs/ietf/GMPLS-TE-STD-MIB.dic +2542 -0
  107. data/lib/mibs/ietf/GSMP-MIB.dic +2468 -0
  108. data/lib/mibs/ietf/HC-ALARM-MIB.dic +1050 -0
  109. data/lib/mibs/ietf/HC-PerfHist-TC-MIB.dic +310 -0
  110. data/lib/mibs/ietf/HC-RMON-MIB.dic +4456 -0
  111. data/lib/mibs/ietf/HDSL2-SHDSL-LINE-MIB.dic +3955 -0
  112. data/lib/mibs/ietf/HOST-RESOURCES-MIB.dic +2453 -0
  113. data/lib/mibs/ietf/HPR-IP-MIB.dic +640 -0
  114. data/lib/mibs/ietf/HPR-MIB.dic +1959 -0
  115. data/lib/mibs/ietf/IANA-ITU-ALARM-TC-MIB.dic +936 -0
  116. data/lib/mibs/ietf/IF-CAP-STACK-MIB.dic +356 -0
  117. data/lib/mibs/ietf/IF-INVERTED-STACK-MIB.dic +220 -0
  118. data/lib/mibs/ietf/IF-MIB.dic +2753 -0
  119. data/lib/mibs/ietf/IFCP-MGMT-MIB.dic +1717 -0
  120. data/lib/mibs/ietf/IGMP-STD-MIB.dic +809 -0
  121. data/lib/mibs/ietf/INET-ADDRESS-MIB.dic +570 -0
  122. data/lib/mibs/ietf/INTEGRATED-SERVICES-GUARANTEED-MIB.dic +319 -0
  123. data/lib/mibs/ietf/INTEGRATED-SERVICES-MIB.dic +1196 -0
  124. data/lib/mibs/ietf/INTERFACETOPN-MIB.dic +1705 -0
  125. data/lib/mibs/ietf/IP-FORWARD-MIB.dic +1853 -0
  126. data/lib/mibs/ietf/IP-MIB.dic +7064 -0
  127. data/lib/mibs/ietf/IPATM-IPMC-MIB.dic +4830 -0
  128. data/lib/mibs/ietf/IPFIX-MIB.dic +2334 -0
  129. data/lib/mibs/ietf/IPFIX-SELECTOR-MIB.dic +215 -0
  130. data/lib/mibs/ietf/IPMCAST-MIB.dic +3390 -0
  131. data/lib/mibs/ietf/IPMROUTE-STD-MIB.dic +1246 -0
  132. data/lib/mibs/ietf/IPOA-MIB.dic +2372 -0
  133. data/lib/mibs/ietf/IPS-AUTH-MIB.dic +1609 -0
  134. data/lib/mibs/ietf/IPSEC-SPD-MIB.dic +3989 -0
  135. data/lib/mibs/ietf/IPV6-FLOW-LABEL-MIB.dic +110 -0
  136. data/lib/mibs/ietf/IPV6-ICMP-MIB.dic +748 -0
  137. data/lib/mibs/ietf/IPV6-MIB.dic +2028 -0
  138. data/lib/mibs/ietf/IPV6-MLD-MIB.dic +659 -0
  139. data/lib/mibs/ietf/IPV6-TCP-MIB.dic +332 -0
  140. data/lib/mibs/ietf/IPV6-UDP-MIB.dic +209 -0
  141. data/lib/mibs/ietf/ISCSI-MIB.dic +4613 -0
  142. data/lib/mibs/ietf/ISDN-MIB.dic +1796 -0
  143. data/lib/mibs/ietf/ISIS-MIB.dic +6215 -0
  144. data/lib/mibs/ietf/ISNS-MIB.dic +6578 -0
  145. data/lib/mibs/ietf/ITU-ALARM-MIB.dic +665 -0
  146. data/lib/mibs/ietf/ITU-ALARM-TC-MIB.dic +137 -0
  147. data/lib/mibs/ietf/Job-Monitoring-MIB.dic +2519 -0
  148. data/lib/mibs/ietf/L2TP-MIB.dic +4050 -0
  149. data/lib/mibs/ietf/LANGTAG-TC-MIB.dic +104 -0
  150. data/lib/mibs/ietf/LISP-MIB.dic +4067 -0
  151. data/lib/mibs/ietf/LMP-MIB.dic +5166 -0
  152. data/lib/mibs/ietf/MALLOC-MIB.dic +2156 -0
  153. data/lib/mibs/ietf/MAU-MIB.dic +2619 -0
  154. data/lib/mibs/ietf/MIDCOM-MIB.dic +2856 -0
  155. data/lib/mibs/ietf/MIOX25-MIB.dic +828 -0
  156. data/lib/mibs/ietf/MIP-MIB.dic +3473 -0
  157. data/lib/mibs/ietf/MOBILEIPV6-MIB.dic +5228 -0
  158. data/lib/mibs/ietf/MPLS-FTN-STD-MIB.dic +1594 -0
  159. data/lib/mibs/ietf/MPLS-L3VPN-STD-MIB.dic +2548 -0
  160. data/lib/mibs/ietf/MPLS-LC-ATM-STD-MIB.dic +491 -0
  161. data/lib/mibs/ietf/MPLS-LC-FR-STD-MIB.dic +395 -0
  162. data/lib/mibs/ietf/MPLS-LDP-ATM-STD-MIB.dic +1019 -0
  163. data/lib/mibs/ietf/MPLS-LDP-FRAME-RELAY-STD-MIB.dic +862 -0
  164. data/lib/mibs/ietf/MPLS-LDP-GENERIC-STD-MIB.dic +445 -0
  165. data/lib/mibs/ietf/MPLS-LDP-STD-MIB.dic +3657 -0
  166. data/lib/mibs/ietf/MPLS-LSR-STD-MIB.dic +3103 -0
  167. data/lib/mibs/ietf/MPLS-TC-STD-MIB.dic +911 -0
  168. data/lib/mibs/ietf/MPLS-TE-STD-MIB.dic +3673 -0
  169. data/lib/mibs/ietf/MSDP-MIB.dic +1893 -0
  170. data/lib/mibs/ietf/MTA-MIB.dic +1898 -0
  171. data/lib/mibs/ietf/Modem-MIB.dic +2054 -0
  172. data/lib/mibs/ietf/NAT-MIB.dic +3866 -0
  173. data/lib/mibs/ietf/NETWORK-SERVICES-MIB.dic +1034 -0
  174. data/lib/mibs/ietf/NHDP-MIB.dic +3005 -0
  175. data/lib/mibs/ietf/NHRP-MIB.dic +3660 -0
  176. data/lib/mibs/ietf/NOTIFICATION-LOG-MIB.dic +1156 -0
  177. data/lib/mibs/ietf/NTPv4-MIB.dic +1535 -0
  178. data/lib/mibs/ietf/OPT-IF-MIB.dic +8972 -0
  179. data/lib/mibs/ietf/OSPF-MIB.dic +5963 -0
  180. data/lib/mibs/ietf/OSPF-TRAP-MIB.dic +1190 -0
  181. data/lib/mibs/ietf/OSPFV3-MIB.dic +5708 -0
  182. data/lib/mibs/ietf/P-BRIDGE-MIB.dic +1499 -0
  183. data/lib/mibs/ietf/PARALLEL-MIB.dic +476 -0
  184. data/lib/mibs/ietf/PIM-MIB.dic +1393 -0
  185. data/lib/mibs/ietf/PIM-STD-MIB.dic +6819 -0
  186. data/lib/mibs/ietf/PINT-MIB.dic +830 -0
  187. data/lib/mibs/ietf/PKTC-IETF-MTA-MIB.dic +3191 -0
  188. data/lib/mibs/ietf/PKTC-IETF-SIG-MIB.dic +4713 -0
  189. data/lib/mibs/ietf/PMIPV6-MIB.dic +3010 -0
  190. data/lib/mibs/ietf/PMIPV6-TC-MIB.dic +293 -0
  191. data/lib/mibs/ietf/POLICY-BASED-MANAGEMENT-MIB.dic +3316 -0
  192. data/lib/mibs/ietf/POWER-ETHERNET-MIB.dic +959 -0
  193. data/lib/mibs/ietf/PPP-BRIDGE-NCP-MIB.dic +587 -0
  194. data/lib/mibs/ietf/PPP-IP-NCP-MIB.dic +269 -0
  195. data/lib/mibs/ietf/PPP-LCP-MIB.dic +994 -0
  196. data/lib/mibs/ietf/PPP-SEC-MIB.dic +411 -0
  197. data/lib/mibs/ietf/PSAMP-MIB.dic +998 -0
  198. data/lib/mibs/ietf/PTOPO-MIB.dic +1135 -0
  199. data/lib/mibs/ietf/PW-ATM-MIB.dic +1642 -0
  200. data/lib/mibs/ietf/PW-CEP-STD-MIB.dic +3661 -0
  201. data/lib/mibs/ietf/PW-STD-MIB.dic +3592 -0
  202. data/lib/mibs/ietf/PW-TC-STD-MIB.dic +437 -0
  203. data/lib/mibs/ietf/PW-TDM-MIB.dic +1896 -0
  204. data/lib/mibs/ietf/PerfHist-TC-MIB.dic +152 -0
  205. data/lib/mibs/ietf/Printer-MIB.dic +6665 -0
  206. data/lib/mibs/ietf/Q-BRIDGE-MIB.dic +3115 -0
  207. data/lib/mibs/ietf/RADIUS-ACC-CLIENT-MIB.dic +991 -0
  208. data/lib/mibs/ietf/RADIUS-ACC-SERVER-MIB.dic +1183 -0
  209. data/lib/mibs/ietf/RADIUS-AUTH-CLIENT-MIB.dic +1073 -0
  210. data/lib/mibs/ietf/RADIUS-AUTH-SERVER-MIB.dic +1251 -0
  211. data/lib/mibs/ietf/RADIUS-DYNAUTH-CLIENT-MIB.dic +1116 -0
  212. data/lib/mibs/ietf/RADIUS-DYNAUTH-SERVER-MIB.dic +1003 -0
  213. data/lib/mibs/ietf/RAQMON-MIB.dic +2695 -0
  214. data/lib/mibs/ietf/RBRIDGE-MIB.dic +2981 -0
  215. data/lib/mibs/ietf/RDBMS-MIB.dic +1935 -0
  216. data/lib/mibs/ietf/RFC1065-SMI.dic +108 -0
  217. data/lib/mibs/ietf/RFC1155-SMI.dic +118 -0
  218. data/lib/mibs/ietf/RFC1158-MIB.dic +2440 -0
  219. data/lib/mibs/ietf/RFC1213-MIB.dic +3434 -0
  220. data/lib/mibs/ietf/RFC1269-MIB.dic +557 -0
  221. data/lib/mibs/ietf/RFC1271-MIB.dic +4135 -0
  222. data/lib/mibs/ietf/RFC1285-MIB.dic +2842 -0
  223. data/lib/mibs/ietf/RFC1316-MIB.dic +800 -0
  224. data/lib/mibs/ietf/RFC1381-MIB.dic +1347 -0
  225. data/lib/mibs/ietf/RFC1382-MIB.dic +3820 -0
  226. data/lib/mibs/ietf/RFC1414-MIB.dic +214 -0
  227. data/lib/mibs/ietf/RIPv2-MIB.dic +773 -0
  228. data/lib/mibs/ietf/RMON-MIB.dic +5551 -0
  229. data/lib/mibs/ietf/RMON2-MIB.dic +8224 -0
  230. data/lib/mibs/ietf/ROHC-MIB.dic +1613 -0
  231. data/lib/mibs/ietf/ROHC-RTP-MIB.dic +859 -0
  232. data/lib/mibs/ietf/ROHC-UNCOMPRESSED-MIB.dic +267 -0
  233. data/lib/mibs/ietf/RPKI-ROUTER-MIB.dic +1363 -0
  234. data/lib/mibs/ietf/RS-232-MIB.dic +1335 -0
  235. data/lib/mibs/ietf/RSERPOOL-MIB.dic +2501 -0
  236. data/lib/mibs/ietf/RSTP-MIB.dic +427 -0
  237. data/lib/mibs/ietf/RSVP-MIB.dic +4135 -0
  238. data/lib/mibs/ietf/RTP-MIB.dic +1376 -0
  239. data/lib/mibs/ietf/SCSI-MIB.dic +3804 -0
  240. data/lib/mibs/ietf/SCTP-MIB.dic +1924 -0
  241. data/lib/mibs/ietf/SFLOW-MIB.dic +568 -0
  242. data/lib/mibs/ietf/SIP-COMMON-MIB.dic +2769 -0
  243. data/lib/mibs/ietf/SIP-MIB.dic +1438 -0
  244. data/lib/mibs/ietf/SIP-SERVER-MIB.dic +1150 -0
  245. data/lib/mibs/ietf/SIP-TC-MIB.dic +257 -0
  246. data/lib/mibs/ietf/SIP-UA-MIB.dic +268 -0
  247. data/lib/mibs/ietf/SLAPM-MIB.dic +4527 -0
  248. data/lib/mibs/ietf/SMON-MIB.dic +1758 -0
  249. data/lib/mibs/ietf/SNA-NAU-MIB.dic +4042 -0
  250. data/lib/mibs/ietf/SNA-SDLC-MIB.dic +3858 -0
  251. data/lib/mibs/ietf/SNMP-COMMUNITY-MIB.dic +715 -0
  252. data/lib/mibs/ietf/SNMP-FRAMEWORK-MIB.dic +709 -0
  253. data/lib/mibs/ietf/SNMP-MPD-MIB.dic +230 -0
  254. data/lib/mibs/ietf/SNMP-NOTIFICATION-MIB.dic +859 -0
  255. data/lib/mibs/ietf/SNMP-PROXY-MIB.dic +414 -0
  256. data/lib/mibs/ietf/SNMP-REPEATER-MIB.dic +4335 -0
  257. data/lib/mibs/ietf/SNMP-SSH-TM-MIB.dic +447 -0
  258. data/lib/mibs/ietf/SNMP-TARGET-MIB.dic +924 -0
  259. data/lib/mibs/ietf/SNMP-TLS-TM-MIB.dic +1449 -0
  260. data/lib/mibs/ietf/SNMP-TSM-MIB.dic +315 -0
  261. data/lib/mibs/ietf/SNMP-USER-BASED-SM-MIB.dic +1164 -0
  262. data/lib/mibs/ietf/SNMP-USM-AES-MIB.dic +95 -0
  263. data/lib/mibs/ietf/SNMP-USM-DH-OBJECTS-MIB.dic +653 -0
  264. data/lib/mibs/ietf/SNMP-VIEW-BASED-ACM-MIB.dic +1202 -0
  265. data/lib/mibs/ietf/SNMPv2-MIB.dic +1382 -0
  266. data/lib/mibs/ietf/SNMPv2-SMI.dic +223 -0
  267. data/lib/mibs/ietf/SNMPv2-USEC-MIB.dic +405 -0
  268. data/lib/mibs/ietf/SONET-MIB.dic +3308 -0
  269. data/lib/mibs/ietf/SOURCE-ROUTING-MIB.dic +542 -0
  270. data/lib/mibs/ietf/SSPM-MIB.dic +1530 -0
  271. data/lib/mibs/ietf/SYSAPPL-MIB.dic +2092 -0
  272. data/lib/mibs/ietf/T11-FC-FABRIC-ADDR-MGR-MIB.dic +1779 -0
  273. data/lib/mibs/ietf/T11-FC-FABRIC-CONFIG-SERVER-MIB.dic +2822 -0
  274. data/lib/mibs/ietf/T11-FC-FABRIC-LOCK-MIB.dic +700 -0
  275. data/lib/mibs/ietf/T11-FC-FSPF-MIB.dic +1889 -0
  276. data/lib/mibs/ietf/T11-FC-NAME-SERVER-MIB.dic +1775 -0
  277. data/lib/mibs/ietf/T11-FC-ROUTE-MIB.dic +655 -0
  278. data/lib/mibs/ietf/T11-FC-RSCN-MIB.dic +1110 -0
  279. data/lib/mibs/ietf/T11-FC-VIRTUAL-FABRIC-MIB.dic +770 -0
  280. data/lib/mibs/ietf/T11-FC-ZONE-SERVER-MIB.dic +3886 -0
  281. data/lib/mibs/ietf/T11-TC-MIB.dic +110 -0
  282. data/lib/mibs/ietf/TCP-ESTATS-MIB.dic +3926 -0
  283. data/lib/mibs/ietf/TCP-MIB.dic +1319 -0
  284. data/lib/mibs/ietf/TCPIPX-MIB.dic +457 -0
  285. data/lib/mibs/ietf/TE-LINK-STD-MIB.dic +2876 -0
  286. data/lib/mibs/ietf/TE-MIB.dic +2924 -0
  287. data/lib/mibs/ietf/TED-MIB.dic +1749 -0
  288. data/lib/mibs/ietf/TIME-AGGREGATE-MIB.dic +550 -0
  289. data/lib/mibs/ietf/TN3270E-MIB.dic +2785 -0
  290. data/lib/mibs/ietf/TN3270E-RT-MIB.dic +1317 -0
  291. data/lib/mibs/ietf/TOKEN-RING-RMON-MIB.dic +2820 -0
  292. data/lib/mibs/ietf/TOKENRING-MIB.dic +1184 -0
  293. data/lib/mibs/ietf/TOKENRING-STATION-SR-MIB.dic +292 -0
  294. data/lib/mibs/ietf/TRANSPORT-ADDRESS-MIB.dic +610 -0
  295. data/lib/mibs/ietf/TRIP-MIB.dic +3159 -0
  296. data/lib/mibs/ietf/TRIP-TC-MIB.dic +241 -0
  297. data/lib/mibs/ietf/TUNNEL-MIB.dic +1095 -0
  298. data/lib/mibs/ietf/UDP-MIB.dic +751 -0
  299. data/lib/mibs/ietf/UDPLITE-MIB.dic +704 -0
  300. data/lib/mibs/ietf/UPS-MIB.dic +3088 -0
  301. data/lib/mibs/ietf/URI-TC-MIB.dic +193 -0
  302. data/lib/mibs/ietf/UUID-TC-MIB.dic +135 -0
  303. data/lib/mibs/ietf/VDSL-LINE-EXT-MCM-MIB.dic +989 -0
  304. data/lib/mibs/ietf/VDSL-LINE-EXT-SCM-MIB.dic +605 -0
  305. data/lib/mibs/ietf/VDSL-LINE-MIB.dic +4518 -0
  306. data/lib/mibs/ietf/VDSL2-LINE-MIB.dic +11029 -0
  307. data/lib/mibs/ietf/VDSL2-LINE-TC-MIB.dic +3152 -0
  308. data/lib/mibs/ietf/VPN-TC-STD-MIB.dic +121 -0
  309. data/lib/mibs/ietf/VRRP-MIB.dic +1163 -0
  310. data/lib/mibs/ietf/VRRPV3-MIB.dic +1403 -0
  311. data/lib/mibs/ietf/WWW-MIB.dic +1810 -0
  312. data/lib/mibs/logstash/iso.dic +18 -0
  313. data/logstash-integration-snmp.gemspec +40 -0
  314. data/spec/fixtures/RFC1213-MIB.dic +3445 -0
  315. data/spec/fixtures/collision.dic +25 -0
  316. data/spec/integration/inputs/snmp_spec.rb +443 -0
  317. data/spec/integration/inputs/snmptrap_spec.rb +383 -0
  318. data/spec/unit/inputs/common_spec.rb +264 -0
  319. data/spec/unit/inputs/snmp_spec.rb +510 -0
  320. data/spec/unit/inputs/snmptrap_spec.rb +141 -0
  321. data/vendor/jar-dependencies/org/logstash/integrations/plugin/4.0.0/plugin-4.0.0.jar +0 -0
  322. data/vendor/jar-dependencies/org/snakeyaml/snakeyaml-engine/2.7/snakeyaml-engine-2.7.jar +0 -0
  323. data/vendor/jar-dependencies/org/snmp4j/snmp4j/3.8.0/snmp4j-3.8.0.jar +0 -0
  324. metadata +523 -0
@@ -0,0 +1,3191 @@
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 PKTC-IETF-MTA-MIB
6
+
7
+ FILENAME = "./libsmi-0.5.0/mibs/ietf/PKTC-IETF-MTA-MIB"
8
+
9
+ MIB = {
10
+ "moduleName" : "PKTC-IETF-MTA-MIB",
11
+
12
+ "PKTC-IETF-MTA-MIB" : {
13
+ "nodetype" : "module",
14
+ "language" : "SMIv2",
15
+ "organization" :
16
+ """IETF IP over Cable Data Network Working Group""",
17
+ "contact" :
18
+ """Eugene Nechamkin
19
+ Broadcom Corporation,
20
+ 200-13711 International Place,
21
+
22
+
23
+
24
+ Richmond, BC, V6V 2Z8
25
+ CANADA
26
+ Phone: +1 604 233 8500
27
+ Email: enechamkin@broadcom.com
28
+
29
+ Jean-Francois Mule
30
+ Cable Television Laboratories, Inc.
31
+ 858 Coal Creek Circle
32
+ Louisville, CO 80027-9750
33
+ U.S.A.
34
+ Phone: +1 303 661 9100
35
+ Email: jf.mule@cablelabs.com
36
+
37
+ IETF IPCDN Working Group
38
+ General Discussion: ipcdn@ietf.org
39
+ Subscribe: http://www.ietf.org/mailman/listinfo/ipcdn
40
+ Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
41
+ Co-Chair: Jean-Francois Mule, jf.mule@cablelabs.com
42
+ Co-Chair: Richard Woundy, Richard_Woundy@cable.comcast.com""",
43
+ "description" :
44
+ """This MIB module defines the basic management object
45
+ for the Multimedia Terminal Adapter devices compliant
46
+ with PacketCable and IPCablecom requirements.
47
+
48
+ Copyright (C) The IETF Trust (2006). This version of
49
+ this MIB module is part of RFC 4682; see the RFC itself for
50
+ full legal notices.""",
51
+ "revisions" : (
52
+ {
53
+ "date" : "2006-09-18 00:00",
54
+ "description" :
55
+ """Initial version, published as RFC 4682.""",
56
+ },
57
+ ),
58
+ "identity node" : "pktcIetfMtaMib",
59
+ },
60
+
61
+ "imports" : (
62
+ {"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
63
+ {"module" : "SNMPv2-SMI", "name" : "OBJECT-TYPE"},
64
+ {"module" : "SNMPv2-SMI", "name" : "OBJECT-IDENTITY"},
65
+ {"module" : "SNMPv2-SMI", "name" : "Unsigned32"},
66
+ {"module" : "SNMPv2-SMI", "name" : "Counter32"},
67
+ {"module" : "SNMPv2-SMI", "name" : "NOTIFICATION-TYPE"},
68
+ {"module" : "SNMPv2-SMI", "name" : "mib-2"},
69
+ {"module" : "SNMPv2-TC", "name" : "TEXTUAL-CONVENTION"},
70
+ {"module" : "SNMPv2-TC", "name" : "RowStatus"},
71
+ {"module" : "SNMPv2-TC", "name" : "TruthValue"},
72
+ {"module" : "SNMPv2-CONF", "name" : "OBJECT-GROUP"},
73
+ {"module" : "SNMPv2-CONF", "name" : "MODULE-COMPLIANCE"},
74
+ {"module" : "SNMPv2-CONF", "name" : "NOTIFICATION-GROUP"},
75
+ {"module" : "INET-ADDRESS-MIB", "name" : "InetAddressType"},
76
+ {"module" : "INET-ADDRESS-MIB", "name" : "InetAddress"},
77
+ {"module" : "SNMPv2-MIB", "name" : "sysDescr"},
78
+ {"module" : "SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
79
+ {"module" : "DOCS-CABLE-DEVICE-MIB", "name" : "docsDevSoftwareGroupV2"},
80
+ {"module" : "DOCS-IETF-BPI2-MIB", "name" : "DocsX509ASN1DEREncodedCertificate"},
81
+ {"module" : "DOCS-IETF-BPI2-MIB", "name" : "docsBpi2CodeDownloadGroup"},
82
+ {"module" : "SYSAPPL-MIB", "name" : "LongUtf8String"},
83
+ {"module" : "IF-MIB", "name" : "ifPhysAddress"},
84
+ ),
85
+
86
+ "typedefs" : {
87
+ "PktcMtaDevProvEncryptAlg" : {
88
+ "basetype" : "Enumeration",
89
+ "status" : "current",
90
+ "none" : {
91
+ "nodetype" : "namednumber",
92
+ "number" : "0"
93
+ },
94
+ "des64CbcMode" : {
95
+ "nodetype" : "namednumber",
96
+ "number" : "1"
97
+ },
98
+ "t3Des192CbcMode" : {
99
+ "nodetype" : "namednumber",
100
+ "number" : "2"
101
+ },
102
+ "aes128CbcMode" : {
103
+ "nodetype" : "namednumber",
104
+ "number" : "3"
105
+ },
106
+ "aes256CbcMode" : {
107
+ "nodetype" : "namednumber",
108
+ "number" : "4"
109
+ },
110
+ "description" :
111
+ """ This textual convention defines various types of the
112
+ encryption algorithms used for the encryption of the MTA
113
+ configuration file. The description of the encryption
114
+ algorithm for each enumerated value is as follows:
115
+
116
+ 'none(0)' no encryption is used,
117
+ 'des64CbcMode(1)' DES 64-bit key in CBC mode,
118
+
119
+
120
+
121
+ 't3Des192CbcMode(2)' 3DES 192-bit key in CBC mode,
122
+ 'aes128CbcMode(3)' AES 128-bit key in CBC mode,
123
+ 'aes256CbcMode(4)' AES 256-bit key in CBC mode.""",
124
+ },
125
+ }, # typedefs
126
+
127
+ "nodes" : {
128
+ "pktcIetfMtaMib" : {
129
+ "nodetype" : "node",
130
+ "moduleName" : "PKTC-IETF-MTA-MIB",
131
+ "oid" : "1.3.6.1.2.1.140",
132
+ "status" : "current",
133
+ }, # node
134
+ "pktcMtaNotification" : {
135
+ "nodetype" : "node",
136
+ "moduleName" : "PKTC-IETF-MTA-MIB",
137
+ "oid" : "1.3.6.1.2.1.140.0",
138
+ }, # node
139
+ "pktcMtaMibObjects" : {
140
+ "nodetype" : "node",
141
+ "moduleName" : "PKTC-IETF-MTA-MIB",
142
+ "oid" : "1.3.6.1.2.1.140.1",
143
+ }, # node
144
+ "pktcMtaDevBase" : {
145
+ "nodetype" : "node",
146
+ "moduleName" : "PKTC-IETF-MTA-MIB",
147
+ "oid" : "1.3.6.1.2.1.140.1.1",
148
+ }, # node
149
+ "pktcMtaDevResetNow" : {
150
+ "nodetype" : "scalar",
151
+ "moduleName" : "PKTC-IETF-MTA-MIB",
152
+ "oid" : "1.3.6.1.2.1.140.1.1.1",
153
+ "status" : "current",
154
+ "syntax" : {
155
+ "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
156
+ },
157
+ "access" : "readwrite",
158
+ "description" :
159
+ """ This object controls the MTA software reset.
160
+ Reading this object always returns 'false'. Setting this
161
+ object to 'true' causes the device to reset immediately
162
+ and the following actions to occur:
163
+ 1. All connections (if present) are flushed locally.
164
+ 2. All current actions such as ringing immediately
165
+ terminate.
166
+ 3. Requests for signaling notifications, such as
167
+ notification based on digit map recognition, are
168
+ flushed.
169
+ 4. All endpoints are disabled.
170
+ 5. The provisioning flow is started at step MTA-1.
171
+ If a value is written into an instance of
172
+ pktcMtaDevResetNow, the agent MUST NOT retain the supplied
173
+ value across MTA re-initializations or reboots.""",
174
+ "reference" :
175
+ """ PacketCable MTA Device Provisioning Specification.""",
176
+ }, # scalar
177
+ "pktcMtaDevSerialNumber" : {
178
+ "nodetype" : "scalar",
179
+ "moduleName" : "PKTC-IETF-MTA-MIB",
180
+ "oid" : "1.3.6.1.2.1.140.1.1.2",
181
+ "status" : "current",
182
+ "syntax" : {
183
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
184
+ },
185
+ "access" : "readonly",
186
+ "description" :
187
+ """ This object specifies the manufacturer's serial
188
+ number of this MTA. The value of this object MUST be
189
+ identical to the value specified in DHCP option 43,
190
+ sub-option 4. The list of sub-options for DHCP option
191
+ 43 are defined in the PacketCable MTA Device
192
+ Provisioning Specification.""",
193
+ "reference" :
194
+ """ PacketCable MTA Device Provisioning Specification.""",
195
+ }, # scalar
196
+ "pktcMtaDevSwCurrentVers" : {
197
+ "nodetype" : "scalar",
198
+ "moduleName" : "PKTC-IETF-MTA-MIB",
199
+ "oid" : "1.3.6.1.2.1.140.1.1.3",
200
+ "status" : "current",
201
+ "syntax" : {
202
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
203
+ },
204
+ "access" : "readonly",
205
+ "description" :
206
+ """ This object identifies the software version currently
207
+ operating in the MTA.
208
+ The MTA MUST return a string descriptive of the current
209
+ software load. This object should use the syntax
210
+ defined by the individual vendor to identify the software
211
+ version. The data presented in this object MUST be
212
+ identical to the software version information contained
213
+ in the 'sysDescr' MIB object of the MTA. The value of
214
+ this object MUST be identical to the value specified in
215
+ DHCP option 43, sub-option 6. The list of sub-options for
216
+ DHCP option 43 are defined in the PacketCable MTA Device
217
+ Provisioning Specification.""",
218
+ "reference" :
219
+ """ PacketCable MTA Device Provisioning Specification.""",
220
+ }, # scalar
221
+ "pktcMtaDevFQDN" : {
222
+ "nodetype" : "scalar",
223
+ "moduleName" : "PKTC-IETF-MTA-MIB",
224
+ "oid" : "1.3.6.1.2.1.140.1.1.4",
225
+ "status" : "current",
226
+ "syntax" : {
227
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
228
+ },
229
+ "access" : "readonly",
230
+ "description" :
231
+ """ This object contains the Fully Qualified Domain Name for
232
+ this MTA. The MTA FQDN is used to uniquely identify the
233
+ device to the PacketCable back office elements.""",
234
+ }, # scalar
235
+ "pktcMtaDevEndPntCount" : {
236
+ "nodetype" : "scalar",
237
+ "moduleName" : "PKTC-IETF-MTA-MIB",
238
+ "oid" : "1.3.6.1.2.1.140.1.1.5",
239
+ "status" : "current",
240
+ "syntax" : {
241
+ "type" : {
242
+ "basetype" : "Unsigned32",
243
+ "ranges" : [
244
+ {
245
+ "min" : "1",
246
+ "max" : "255"
247
+ },
248
+ ],
249
+ "range" : {
250
+ "min" : "1",
251
+ "max" : "255"
252
+ },
253
+ },
254
+ },
255
+ "access" : "readonly",
256
+ "description" :
257
+ """ This object contains the number of physical endpoints for
258
+ this MTA.""",
259
+ }, # scalar
260
+ "pktcMtaDevEnabled" : {
261
+ "nodetype" : "scalar",
262
+ "moduleName" : "PKTC-IETF-MTA-MIB",
263
+ "oid" : "1.3.6.1.2.1.140.1.1.6",
264
+ "status" : "current",
265
+ "syntax" : {
266
+ "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
267
+ },
268
+ "access" : "readwrite",
269
+ "description" :
270
+ """ This object contains the MTA Admin Status of this device.
271
+ If this object is set to 'true', the MTA is
272
+ administratively enabled, and the MTA MUST be able to
273
+ interact with the PacketCable entities, such as CMS,
274
+ Provisioning Server, KDC, and other MTAs and MGs on all
275
+ PacketCable interfaces.
276
+ If this object is set to 'false', the MTA is
277
+ administratively disabled, and the MTA MUST perform the
278
+ following actions for all endpoints:
279
+ - Shut down all media sessions, if present.
280
+ - Shut down Network Control Signaling (NCS)
281
+ signaling by following the Restart in
282
+ Progress procedures in the PacketCable NCS
283
+ specification.
284
+ The MTA must execute all actions required to
285
+ enable or disable the telephony services for all
286
+ endpoints immediately upon receipt of an SNMP SET
287
+ operation.
288
+
289
+ Additionally, the MTA MUST maintain the SNMP Interface
290
+ for management and also the SNMP Key management interface.
291
+ Also, the MTA MUST NOT continue Kerberized key management
292
+ with CMSes until this object is set to 'true'.
293
+ Note: MTAs MUST renew the CMS Kerberos tickets according
294
+ to the PacketCable Security or IPCablecom Specification.
295
+ If a value is written into an instance of
296
+ pktcMtaDevEnabled, the agent MUST NOT retain the supplied
297
+ value across MTA re-initializations or reboots.""",
298
+ "reference" :
299
+ """ PacketCable MTA Device Provisioning Specification;
300
+ PacketCable Security Specification;
301
+ PacketCable Network-Based Call Signaling Protocol
302
+
303
+
304
+
305
+ Specification.""",
306
+ }, # scalar
307
+ "pktcMtaDevTypeIdentifier" : {
308
+ "nodetype" : "scalar",
309
+ "moduleName" : "PKTC-IETF-MTA-MIB",
310
+ "oid" : "1.3.6.1.2.1.140.1.1.7",
311
+ "status" : "current",
312
+ "syntax" : {
313
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
314
+ },
315
+ "access" : "readonly",
316
+ "description" :
317
+ """ This object provides the MTA device type identifier. The
318
+ value of this object must be a copy of the DHCP option 60
319
+ value exchanged between the MTA and the DHCP server. The
320
+ DHCP option 60 value contains an ASCII-encoded string
321
+ identifying capabilities of the MTA as defined in the
322
+ PacketCable MTA Device Provisioning Specification.""",
323
+ "reference" :
324
+ """ RFC 2132, DHCP Options and BOOTP Vendor Extensions;
325
+ PacketCable MTA Device Provisioning Specification.""",
326
+ }, # scalar
327
+ "pktcMtaDevProvisioningState" : {
328
+ "nodetype" : "scalar",
329
+ "moduleName" : "PKTC-IETF-MTA-MIB",
330
+ "oid" : "1.3.6.1.2.1.140.1.1.8",
331
+ "status" : "current",
332
+ "syntax" : {
333
+ "type" : {
334
+ "basetype" : "Enumeration",
335
+ "pass" : {
336
+ "nodetype" : "namednumber",
337
+ "number" : "1"
338
+ },
339
+ "inProgress" : {
340
+ "nodetype" : "namednumber",
341
+ "number" : "2"
342
+ },
343
+ "failConfigFileError" : {
344
+ "nodetype" : "namednumber",
345
+ "number" : "3"
346
+ },
347
+ "passWithWarnings" : {
348
+ "nodetype" : "namednumber",
349
+ "number" : "4"
350
+ },
351
+ "passWithIncompleteParsing" : {
352
+ "nodetype" : "namednumber",
353
+ "number" : "5"
354
+ },
355
+ "failureInternalError" : {
356
+ "nodetype" : "namednumber",
357
+ "number" : "6"
358
+ },
359
+ "failureOtherReason" : {
360
+ "nodetype" : "namednumber",
361
+ "number" : "7"
362
+ },
363
+ },
364
+ },
365
+ "access" : "readonly",
366
+ "description" :
367
+ """ This object indicates the completion state of the MTA
368
+ device provisioning process.
369
+
370
+ pass:
371
+ If the configuration file could be parsed successfully
372
+ and the MTA is able to reflect the same in its
373
+ MIB, the MTA MUST return the value 'pass'.
374
+
375
+ inProgress:
376
+ If the MTA is in the process of being provisioned,
377
+ the MTA MUST return the value 'inProgress'.
378
+
379
+ failConfigFileError:
380
+ If the configuration file was in error due to incorrect
381
+ values in the mandatory parameters, the MTA MUST reject
382
+ the configuration file, and the MTA MUST return the value
383
+
384
+
385
+
386
+ 'failConfigFileError'.
387
+
388
+ passWithWarnings:
389
+ If the configuration file had proper values for all the
390
+ mandatory parameters but has errors in any of the optional
391
+ parameters (this includes any vendor-specific Object
392
+ Identifiers (OIDs) that are incorrect or not known
393
+ to the MTA), the MTA MUST return the value
394
+ 'passWithWarnings'.
395
+
396
+ passWithIncompleteParsing:
397
+ If the configuration file is valid but the MTA cannot
398
+ reflect the same in its configuration (for example, too
399
+ many entries caused memory exhaustion), it must accept
400
+ the CMS configuration entries related, and the MTA MUST
401
+ return the value 'passWithIncompleteParsing'.
402
+
403
+ failureInternalError:
404
+ If the configuration file cannot be parsed due to an
405
+ Internal error, the MTA MUST return the value
406
+ 'failureInternalError'.
407
+
408
+ failureOtherReason:
409
+ If the MTA cannot accept the configuration file for any
410
+ other reason than the ones stated above, the MTA MUST
411
+ return the value 'failureOtherReason'.
412
+
413
+ When a final SNMP INFORM is sent as part of Step 25 of the
414
+ MTA Provisioning process, this parameter is also included
415
+ in the final INFORM message.""",
416
+ "reference" :
417
+ """ PacketCable MTA Device Provisioning Specification.""",
418
+ }, # scalar
419
+ "pktcMtaDevHttpAccess" : {
420
+ "nodetype" : "scalar",
421
+ "moduleName" : "PKTC-IETF-MTA-MIB",
422
+ "oid" : "1.3.6.1.2.1.140.1.1.9",
423
+ "status" : "current",
424
+ "syntax" : {
425
+ "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
426
+ },
427
+ "access" : "readonly",
428
+ "description" :
429
+ """ This object indicates whether the HTTP protocol is
430
+ supported for the MTA configuration file transfer.""",
431
+ }, # scalar
432
+ "pktcMtaDevProvisioningTimer" : {
433
+ "nodetype" : "scalar",
434
+ "moduleName" : "PKTC-IETF-MTA-MIB",
435
+ "oid" : "1.3.6.1.2.1.140.1.1.10",
436
+ "status" : "current",
437
+ "syntax" : {
438
+ "type" : {
439
+ "basetype" : "Unsigned32",
440
+ "ranges" : [
441
+ {
442
+ "min" : "0",
443
+ "max" : "30"
444
+ },
445
+ ],
446
+ "range" : {
447
+ "min" : "0",
448
+ "max" : "30"
449
+ },
450
+ },
451
+ },
452
+ "access" : "readwrite",
453
+ "default" : "10",
454
+ "units" : "minutes",
455
+ "description" :
456
+ """ This object defines the time interval for the provisioning
457
+ flow to complete. The MTA MUST finish all provisioning
458
+ operations starting from the moment when an MTA receives
459
+ its DHCP ACK and ending at the moment when the MTA
460
+ downloads its configuration file (e.g., MTA5 to MTA23)
461
+ within the period of time set by this object.
462
+ Failure to comply with this condition constitutes
463
+ a provisioning flow failure. If the object is set to 0,
464
+ the MTA MUST ignore the provisioning timer condition.
465
+ If a value is written into an instance of
466
+ pktcMtaDevProvisioningTimer, the agent MUST NOT retain the
467
+ supplied value across MTA re-initializations or reboots.""",
468
+ "reference" :
469
+ """ PacketCable MTA Device Provisioning Specification.""",
470
+ }, # scalar
471
+ "pktcMtaDevProvisioningCounter" : {
472
+ "nodetype" : "scalar",
473
+ "moduleName" : "PKTC-IETF-MTA-MIB",
474
+ "oid" : "1.3.6.1.2.1.140.1.1.11",
475
+ "status" : "current",
476
+ "syntax" : {
477
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
478
+ },
479
+ "access" : "readonly",
480
+ "description" :
481
+ """This object counts the number of times the
482
+ provisioning cycle has looped through step MTA-1.""",
483
+ }, # scalar
484
+ "pktcMtaDevErrorOidsTable" : {
485
+ "nodetype" : "table",
486
+ "moduleName" : "PKTC-IETF-MTA-MIB",
487
+ "oid" : "1.3.6.1.2.1.140.1.1.12",
488
+ "status" : "current",
489
+ "description" :
490
+ """ This table contains the list of configuration errors or
491
+ warnings the MTA encountered when parsing the
492
+ configuration file it received from the Provisioning
493
+ Server.
494
+ For each error, an entry is created in this table,
495
+ containing the configuration parameters the MTA rejected
496
+ and the associated reason (e.g., wrong or unknown OID,
497
+ inappropriate object values). If the MTA
498
+ did not report a provisioning state of 'pass(1)' in
499
+ the pktcMtaDevProvisioningState object, this table MUST be
500
+ populated for each error or warning instance. Even if
501
+ different parameters share the same error type (e.g., all
502
+ realm name configuration parameters are invalid), all
503
+ observed errors or warnings must be reported as
504
+ different instances. Errors are placed into the table in
505
+ no particular order. The table MUST be cleared each time
506
+
507
+
508
+
509
+ the MTA reboots.""",
510
+ "reference" :
511
+ """ PacketCable MTA Device Provisioning Specification.""",
512
+ }, # table
513
+ "pktcMtaDevErrorOidsEntry" : {
514
+ "nodetype" : "row",
515
+ "moduleName" : "PKTC-IETF-MTA-MIB",
516
+ "oid" : "1.3.6.1.2.1.140.1.1.12.1",
517
+ "status" : "current",
518
+ "linkage" : [
519
+ "pktcMtaDevErrorOidIndex",
520
+ ],
521
+ "description" :
522
+ """ This entry contains the necessary information the MTA MUST
523
+ attempt to provide in case of configuration file errors or
524
+ warnings.""",
525
+ }, # row
526
+ "pktcMtaDevErrorOidIndex" : {
527
+ "nodetype" : "column",
528
+ "moduleName" : "PKTC-IETF-MTA-MIB",
529
+ "oid" : "1.3.6.1.2.1.140.1.1.12.1.1",
530
+ "status" : "current",
531
+ "syntax" : {
532
+ "type" : {
533
+ "basetype" : "Unsigned32",
534
+ "ranges" : [
535
+ {
536
+ "min" : "1",
537
+ "max" : "1024"
538
+ },
539
+ ],
540
+ "range" : {
541
+ "min" : "1",
542
+ "max" : "1024"
543
+ },
544
+ },
545
+ },
546
+ "access" : "noaccess",
547
+ "description" :
548
+ """ This object is the index of the MTA configuration error
549
+ table. It is an integer value that starts at value '1'
550
+ and is incremented for each encountered configuration
551
+ file error or warning.
552
+
553
+ The maximum number of errors or warnings that can be
554
+ recorded in the pktcMtaDevErrorOidsTable is set to 1024 as
555
+ a configuration file is usually validated by operators
556
+ before deployment. Given the possible number of
557
+ configuration parameter assignments in the MTA
558
+ configuration file, 1024 is perceived as a sufficient
559
+ limit even with future extensions.
560
+
561
+ If the number of the errors in the configuration file
562
+ exceeds 1024, all errors beyond the 1024th one MUST
563
+ be ignored and not be reflected in the
564
+ pktcMtaDevErrorOidsTable.""",
565
+ }, # column
566
+ "pktcMtaDevErrorOid" : {
567
+ "nodetype" : "column",
568
+ "moduleName" : "PKTC-IETF-MTA-MIB",
569
+ "oid" : "1.3.6.1.2.1.140.1.1.12.1.2",
570
+ "status" : "current",
571
+ "syntax" : {
572
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
573
+ },
574
+ "access" : "readonly",
575
+ "description" :
576
+ """ This object contains a human readable representation
577
+ (character string) of the OID corresponding to the
578
+ configuration file parameter that caused the particular
579
+ error.
580
+ For example, if the value of the pktcMtaDevEnabled object
581
+ in the configuration file caused an error, then this
582
+ object instance will contain the human-readable string of
583
+ '1.3.6.1.2.1.140.1.1.6.0'.
584
+ If the MTA generated an error because it was not able
585
+ to recognize a particular OID, then this object
586
+ instance would contain an empty value (zero-length
587
+ string).
588
+ For example, if the value of an OID in the configuration
589
+ file was interpreted by the MTA as being 1.2.3.4.5, and if
590
+ the MTA was not able to recognize this OID as a valid one,
591
+ this object instance will contain a zero-length string.
592
+
593
+ If the number of errors in the configuration file exceeds
594
+ 1024, then for all subsequent errors, the
595
+ pktcMtaDevErrorOid of the table's 1024th entry MUST
596
+ contain a human-readable representation of the
597
+ pktcMtaDevErrorsTooManyErrors object; i.e., the string
598
+ '1.3.6.1.2.1.140.1.1.4.1.0'.
599
+ Note that the syntax of this object is SnmpAdminString
600
+ instead of OBJECT IDENTIFIER because the object value may
601
+ not be a valid OID due to human or configuration tool
602
+ encoding errors.""",
603
+ }, # column
604
+ "pktcMtaDevErrorValue" : {
605
+ "nodetype" : "column",
606
+ "moduleName" : "PKTC-IETF-MTA-MIB",
607
+ "oid" : "1.3.6.1.2.1.140.1.1.12.1.3",
608
+ "status" : "current",
609
+ "syntax" : {
610
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
611
+ },
612
+ "access" : "readonly",
613
+ "description" :
614
+ """ This object contains the value of the OID corresponding to
615
+ the configuration file parameter that caused the error.
616
+ If the MTA cannot recognize the OID of the
617
+ configuration parameter causing the error, then this
618
+ object instance contains the OID itself as interpreted
619
+ by the MTA in human-readable representation.
620
+ If the MTA can recognize the OID but generate an error due
621
+ to a wrong value of the parameter, then the object
622
+
623
+
624
+
625
+ instance contains the erroneous value of the parameter as
626
+ read from the configuration file.
627
+ In both cases, the value of this object must be
628
+ represented in human-readable form as a character string.
629
+ For example, if the value of the pktcMtaDevEnabled object
630
+ in the configuration file was 3 (invalid value), then the
631
+ pktcMtaDevErrorValue object instance will contain the
632
+ human-readable (string) representation of value '3'.
633
+ Similarly, if the OID in the configuration file has been
634
+ interpreted by the MTA as being 1.2.3.4.5 and the MTA
635
+ cannot recognize this OID as a valid one, then this
636
+ pktcMtaDevErrorValue object instance will contain human
637
+ readable (string) representation of value '1.2.3.4.5'.
638
+
639
+ If the number of errors in the configuration file exceeds
640
+ 1024, then for all subsequent errors, the
641
+ pktcMtaDevErrorValue of the table's 1024th entry MUST
642
+ contain a human-readable representation of the
643
+ pktcMtaDevErrorsTooManyErrors object; i.e., the string
644
+ '1.3.6.1.2.1.140.1.1.4.1.0'.""",
645
+ }, # column
646
+ "pktcMtaDevErrorReason" : {
647
+ "nodetype" : "column",
648
+ "moduleName" : "PKTC-IETF-MTA-MIB",
649
+ "oid" : "1.3.6.1.2.1.140.1.1.12.1.4",
650
+ "status" : "current",
651
+ "syntax" : {
652
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
653
+ },
654
+ "access" : "readonly",
655
+ "description" :
656
+ """ This object indicates the reason for the error or warning,
657
+ as per the MTA's interpretation, in human-readable form.
658
+ For example:
659
+ 'VALUE NOT IN RANGE', 'VALUE DOES NOT MATCH TYPE',
660
+ 'UNSUPPORTED VALUE', 'LAST 4 BITS MUST BE SET TO ZERO',
661
+ 'OUT OF MEMORY - CANNOT STORE'.
662
+ This object may also contain vendor specific errors for
663
+ private vendor OIDs and any proprietary error codes or
664
+ messages that can help diagnose configuration errors.
665
+
666
+ If the number of errors in the configuration file exceeds
667
+ 1024, then for all subsequent errors, the
668
+ pktcMtaDevErrorReason of the table's 1024th entry MUST
669
+ contain a human-readable string indicating the reason
670
+ for an error; for example,
671
+ 'Too many errors in the configuration file'.""",
672
+ }, # column
673
+ "pktcMtaDevServer" : {
674
+ "nodetype" : "node",
675
+ "moduleName" : "PKTC-IETF-MTA-MIB",
676
+ "oid" : "1.3.6.1.2.1.140.1.2",
677
+ }, # node
678
+ "pktcMtaDevDhcpServerAddressType" : {
679
+ "nodetype" : "scalar",
680
+ "moduleName" : "PKTC-IETF-MTA-MIB",
681
+ "oid" : "1.3.6.1.2.1.140.1.2.1",
682
+ "status" : "current",
683
+ "syntax" : {
684
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetAddressType"},
685
+ },
686
+ "access" : "readonly",
687
+ "default" : "ipv4",
688
+ "description" :
689
+ """ This object contains the Internet address type for the
690
+ PacketCable DHCP servers specified in MTA MIB.""",
691
+ }, # scalar
692
+ "pktcMtaDevServerDhcp1" : {
693
+ "nodetype" : "scalar",
694
+ "moduleName" : "PKTC-IETF-MTA-MIB",
695
+ "oid" : "1.3.6.1.2.1.140.1.2.2",
696
+ "status" : "current",
697
+ "syntax" : {
698
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetAddress"},
699
+ },
700
+ "access" : "readonly",
701
+ "description" :
702
+ """ This object contains the Internet Address of the primary
703
+ DHCP server the MTA uses during provisioning.
704
+ The type of this address is determined by the value of
705
+ the pktcMtaDevDhcpServerAddressType object.
706
+ When the latter has the value 'ipv4(1)', this object
707
+ contains the IP address of the primary DHCP
708
+ server. It is provided by the CM to the MTA via the DHCP
709
+ option code 122, sub-option 1, as defined in RFC 3495.
710
+
711
+ The behavior of this object when the value of
712
+ pktcMtaDevDhcpServerAddressType is other than 'ipv4(1)'
713
+ is not presently specified, but it may be specified
714
+ in future versions of this MIB module.
715
+ If this object is of value
716
+ 0.0.0.0, the MTA MUST stop all provisioning
717
+ attempts, as well as all other activities.
718
+ If this object is of value 255.255.255.255, it means
719
+ that there was no preference given for the primary
720
+ DHCP server, and, the MTA must follow the logic of
721
+ RFC2131, and the value of DHCP option 122,
722
+ sub-option 2, must be ignored.""",
723
+ "reference" :
724
+ """ PacketCable MTA Device Provisioning Specification;
725
+ RFC 2131, Dynamic Host Configuration Protocol;
726
+ RFC 3495, DHCP Option for CableLabs Client Configuration.""",
727
+ }, # scalar
728
+ "pktcMtaDevServerDhcp2" : {
729
+ "nodetype" : "scalar",
730
+ "moduleName" : "PKTC-IETF-MTA-MIB",
731
+ "oid" : "1.3.6.1.2.1.140.1.2.3",
732
+ "status" : "current",
733
+ "syntax" : {
734
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetAddress"},
735
+ },
736
+ "access" : "readonly",
737
+ "description" :
738
+ """ This object contains the Internet Address of the secondary
739
+ DHCP server the MTA uses during provisioning.
740
+ The type of this address is determined by the value of
741
+ the pktcMtaDevDhcpServerAddressType object.
742
+ When the latter has the value 'ipv4(1)', this object
743
+ contains the IP address of the secondary DHCP
744
+ server. It is provided by the CM to the MTA via the DHCP
745
+ option code 122, sub-option 2, as defined in RFC 3495.
746
+
747
+ The behavior of this object when the value of
748
+ pktcMtaDevDhcpServerAddressType is other than 'ipv4(1)'
749
+ is not presently specified, but it may be specified
750
+ in future versions of this MIB module.
751
+ If there was no secondary DHCP server provided in DHCP
752
+ Option 122, sub-option 2, this object must return the value
753
+ 0.0.0.0.""",
754
+ "reference" :
755
+ """ PacketCable MTA Device Provisioning Specification;
756
+ RFC 3495, DHCP Option for CableLabs Client Configuration.""",
757
+ }, # scalar
758
+ "pktcMtaDevDnsServerAddressType" : {
759
+ "nodetype" : "scalar",
760
+ "moduleName" : "PKTC-IETF-MTA-MIB",
761
+ "oid" : "1.3.6.1.2.1.140.1.2.4",
762
+ "status" : "current",
763
+ "syntax" : {
764
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetAddressType"},
765
+ },
766
+ "access" : "readonly",
767
+ "default" : "ipv4",
768
+ "description" :
769
+ """ This object contains the Internet address type for the
770
+ PacketCable DNS servers specified in MTA MIB.""",
771
+ }, # scalar
772
+ "pktcMtaDevServerDns1" : {
773
+ "nodetype" : "scalar",
774
+ "moduleName" : "PKTC-IETF-MTA-MIB",
775
+ "oid" : "1.3.6.1.2.1.140.1.2.5",
776
+ "status" : "current",
777
+ "syntax" : {
778
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetAddress"},
779
+ },
780
+ "access" : "readwrite",
781
+ "description" :
782
+ """ This object contains the IP Address of the primary
783
+ DNS server to be used by the MTA. The type of this address
784
+ is determined by the value of the
785
+ pktcMtaDevDnsServerAddressType object.
786
+ When the latter has the value 'ipv4(1)', this object
787
+ contains the IP address of the primary DNS server.
788
+ As defined in RFC 2132, PacketCable-compliant MTAs receive
789
+ the IP addresses of the DNS Servers in DHCP option 6.
790
+ The behavior of this object when the value of
791
+ pktcMtaDevDnsServerAddressType is other than 'ipv4(1)'
792
+
793
+
794
+
795
+ is not presently specified, but it may be specified
796
+ in future versions of this MIB module.
797
+ If a value is written into an instance of
798
+ pktcMtaDevServerDns1, the agent MUST NOT retain the
799
+ supplied value across MTA re-initializations or reboots.""",
800
+ "reference" :
801
+ """ PacketCable MTA Device Provisioning Specification;
802
+ RFC 2132, DHCP Options and BOOTP Vendor Extensions.""",
803
+ }, # scalar
804
+ "pktcMtaDevServerDns2" : {
805
+ "nodetype" : "scalar",
806
+ "moduleName" : "PKTC-IETF-MTA-MIB",
807
+ "oid" : "1.3.6.1.2.1.140.1.2.6",
808
+ "status" : "current",
809
+ "syntax" : {
810
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetAddress"},
811
+ },
812
+ "access" : "readwrite",
813
+ "description" :
814
+ """ This object contains the IP Address of the secondary
815
+ DNS server to be used by the MTA. The type of this address
816
+ is determined by the value of the
817
+ pktcMtaDevDnsServerAddressType object.
818
+ When the latter has the value 'ipv4(1)', this object
819
+ contains the IP address of the secondary DNS
820
+ server. As defined in RFC 2132, PacketCable-compliant MTAs
821
+ receive the IP addresses of the DNS Servers in DHCP
822
+ option 6.
823
+ The behavior of this object when the value of
824
+ pktcMtaDevDnsServerAddressType is other than 'ipv4(1)'
825
+ is not presently specified, but it may be specified
826
+ in future versions of this MIB module.
827
+ If a value is written into an instance of
828
+ pktcMtaDevServerDns2, the agent MUST NOT retain the
829
+ supplied value across MTA re-initializations or reboots.""",
830
+ "reference" :
831
+ """ PacketCable MTA Device Provisioning Specification;
832
+ RFC 2132, DHCP Options and BOOTP Vendor Extensions.""",
833
+ }, # scalar
834
+ "pktcMtaDevTimeServerAddressType" : {
835
+ "nodetype" : "scalar",
836
+ "moduleName" : "PKTC-IETF-MTA-MIB",
837
+ "oid" : "1.3.6.1.2.1.140.1.2.7",
838
+ "status" : "current",
839
+ "syntax" : {
840
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetAddressType"},
841
+ },
842
+ "access" : "readonly",
843
+ "default" : "ipv4",
844
+ "description" :
845
+ """ This object contains the Internet address type for the
846
+ PacketCable Time servers specified in MTA MIB.""",
847
+ }, # scalar
848
+ "pktcMtaDevTimeServer" : {
849
+ "nodetype" : "scalar",
850
+ "moduleName" : "PKTC-IETF-MTA-MIB",
851
+ "oid" : "1.3.6.1.2.1.140.1.2.8",
852
+ "status" : "current",
853
+ "syntax" : {
854
+ "type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetAddress"},
855
+ },
856
+ "access" : "readwrite",
857
+ "description" :
858
+ """ This object contains the Internet Address of the Time
859
+ Server used by an S-MTA for Time Synchronization. The type
860
+ of this address is determined by the value of the
861
+ pktcMtaDevTimeServerAddressType object.
862
+ When the latter has the value 'ipv4(1)', this object
863
+ contains the IP address of the Time Server used for Time
864
+ Synchronization.
865
+ In the case of an S-MTA, this object must be
866
+ populated with a value other than 0.0.0.0 as obtained
867
+ from DHCP option 4. The protocol by which the time of day
868
+ MUST be retrieved is defined in RFC 868.
869
+ In the case of an E-MTA, this object must contain a
870
+ value of 0.0.0.0 if the address type is 'ipv4(1)' since
871
+ an E-MTA does not use the Time Protocol for time
872
+ synchronization (an E-MTA uses the time retrieved by the
873
+ DOCSIS cable modem).
874
+ The behavior of this object when the value of
875
+ pktcMtaDevTimeServerAddressType is other than 'ipv4(1)'
876
+ is not presently specified, but it may be specified in
877
+ future versions of this MIB module.
878
+ If a value is written into an instance of
879
+ pktcMtaDevTimeServer, the agent MUST NOT retain the
880
+ supplied value across MTA re-initializations or reboots.""",
881
+ "reference" :
882
+ """ RFC 868, Time Protocol;
883
+ RFC 2131, Dynamic Host Configuration Protocol;
884
+ RFC 2132, DHCP Options and BOOTP Vendor Extensions.""",
885
+ }, # scalar
886
+ "pktcMtaDevConfigFile" : {
887
+ "nodetype" : "scalar",
888
+ "moduleName" : "PKTC-IETF-MTA-MIB",
889
+ "oid" : "1.3.6.1.2.1.140.1.2.9",
890
+ "status" : "current",
891
+ "syntax" : {
892
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
893
+ },
894
+ "access" : "readwrite",
895
+ "description" :
896
+ """ This object specifies the MTA device configuration file
897
+ information, including the access method, the server name,
898
+ and the configuration file name. The value of this object
899
+ is the Uniform Resource Locator (URL) of the configuration
900
+ file for TFTP or HTTP download.
901
+ If this object value is a TFTP URL, it must be formatted
902
+ as defined in RFC 3617.
903
+ If this object value is an HTTP URL, it must be formatted
904
+ as defined in RFC 2616.
905
+ If the MTA SNMP Enrollment mechanism is used, then the MTA
906
+ must download the file provided by the Provisioning Server
907
+
908
+
909
+
910
+ during provisioning via an SNMP SET on this object.
911
+ If the MTA SNMP Enrollment mechanism is not used, this
912
+ object MUST contain the URL value corresponding to the
913
+ 'siaddr' and 'file' fields received in the DHCP ACK to
914
+ locate the configuration file: the 'siaddr' and 'file'
915
+ fields represent the host and file of the TFTP URL,
916
+ respectively. In this case, the MTA MUST return an
917
+ 'inconsistentValue' error in response to SNMP SET
918
+ operations.
919
+ The MTA MUST return a zero-length string if the server
920
+ address (host part of the URL) is unknown.
921
+ If a value is written into an instance of
922
+ pktcMtaDevConfigFile, the agent MUST NOT retain the
923
+ supplied value across MTA re-initializations or reboots.""",
924
+ "reference" :
925
+ """ PacketCable MTA Device Provisioning Specification;
926
+ RFC 3617, URI Scheme for TFTP; RFC 2616, HTTP 1.1""",
927
+ }, # scalar
928
+ "pktcMtaDevSnmpEntity" : {
929
+ "nodetype" : "scalar",
930
+ "moduleName" : "PKTC-IETF-MTA-MIB",
931
+ "oid" : "1.3.6.1.2.1.140.1.2.10",
932
+ "status" : "current",
933
+ "syntax" : {
934
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
935
+ },
936
+ "access" : "readonly",
937
+ "description" :
938
+ """ This object contains the FQDN of the SNMP entity of the
939
+ Provisioning Server. When the MTA SNMP Enrollment
940
+ Mechanism is used, this object represents the server that
941
+ the MTA communicates with, that it receives the
942
+ configuration file URL from, and that it sends the
943
+ enrollment notification to. The SNMP entity is also the
944
+ destination entity for all the provisioning
945
+ notifications. It may be used for post-provisioning
946
+ SNMP operations. During the provisioning phase, this
947
+ SNMP entity FQDN is supplied to the MTA via DHCP option
948
+ 122, sub-option 3, as defined in RFC 3495. The MTA must
949
+ resolve the FQDN value before its very first network
950
+ interaction with the SNMP entity during the provisioning
951
+ phase.""",
952
+ "reference" :
953
+ """ PacketCable MTA Device Provisioning Specification;
954
+ RFC 3495, DHCP Option for CableLabs Client Configuration.""",
955
+ }, # scalar
956
+ "pktcMtaDevProvConfigHash" : {
957
+ "nodetype" : "scalar",
958
+ "moduleName" : "PKTC-IETF-MTA-MIB",
959
+ "oid" : "1.3.6.1.2.1.140.1.2.11",
960
+ "status" : "current",
961
+ "syntax" : {
962
+ "type" : {
963
+ "basetype" : "OctetString",
964
+ "ranges" : [
965
+ {
966
+ "min" : "20",
967
+ "max" : "20"
968
+ },
969
+ ],
970
+ "range" : {
971
+ "min" : "20",
972
+ "max" : "20"
973
+ },
974
+ },
975
+ },
976
+ "access" : "readwrite",
977
+ "description" :
978
+ """ This object contains the hash value of the contents of the
979
+ configuration file.
980
+ The authentication algorithm is Secure Hashing Algorithm
981
+ 1 (SHA-1), and the length is 160 bits. The hash
982
+ calculation MUST follow the requirements defined in the
983
+ PacketCable Security Specification. When the MTA SNMP
984
+ Enrollment mechanism is used, this hash value is
985
+ calculated and sent to the MTA prior to sending the
986
+ config file. This object value is then provided by the
987
+ Provisioning server via an SNMP SET operation.
988
+ When the MTA SNMP Enrollment mechanism is not in use, the
989
+ hash value is provided in the configuration file itself,
990
+ and it is also calculated by the MTA. This object value
991
+ MUST represent the hash value calculated by the MTA.
992
+ When the MTA SNMP Enrollment mechanism is not in use, the
993
+ MTA must reject all SNMP SET operations on this object and
994
+ return an 'inconsistentValue' error.
995
+ If a value is written into an instance of
996
+ pktcMtaDevProvConfigHash, the agent MUST NOT retain the
997
+ supplied value across MTA re-initializations or reboots.""",
998
+ "reference" :
999
+ """ PacketCable MTA Device Provisioning Specification;
1000
+ PacketCable Security Specification.""",
1001
+ }, # scalar
1002
+ "pktcMtaDevProvConfigKey" : {
1003
+ "nodetype" : "scalar",
1004
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1005
+ "oid" : "1.3.6.1.2.1.140.1.2.12",
1006
+ "status" : "current",
1007
+ "syntax" : {
1008
+ "type" : {
1009
+ "basetype" : "OctetString",
1010
+ "ranges" : [
1011
+ {
1012
+ "min" : "32",
1013
+ "max" : "32"
1014
+ },
1015
+ ],
1016
+ "range" : {
1017
+ "min" : "32",
1018
+ "max" : "32"
1019
+ },
1020
+ },
1021
+ },
1022
+ "access" : "readwrite",
1023
+ "description" :
1024
+ """ This object contains the key used to encrypt/decrypt
1025
+ the configuration file when secure SNMPv3 provisioning
1026
+ is used.
1027
+ The value of this object is provided along with the
1028
+ configuration file information (pktcMtaDevConfigFile)
1029
+ and hash (pktcMtaDevProvConfigHash) by the Provisioning
1030
+ Server via SNMP SET once the configuration file has been
1031
+ created, as defined by the PacketCable Security
1032
+ specification.
1033
+
1034
+ The privacy algorithm is defined by the
1035
+ pktcMtaDevProvConfigEncryptAlg MIB object. The
1036
+ MTA requirements related to the privacy algorithm are
1037
+ defined in the PacketCable Security Specification.
1038
+
1039
+ If this object is set at any other provisioning step than
1040
+ that allowed by the PacketCable MTA Device
1041
+
1042
+
1043
+
1044
+ Provisioning Specification, the MTA SHOULD return
1045
+ an 'inconsistentValue' error.
1046
+ This object must not be used in non secure provisioning
1047
+ mode. In non-secure provisioning modes, the MTA SHOULD
1048
+ return an 'inconsistentValue' in response to SNMP SET
1049
+ operations, and the MTA SHOULD return a zero-length
1050
+ string in response to SNMP GET operations.
1051
+ If a value is written into an instance of
1052
+ pktcMtaDevProvConfigKey, the agent MUST NOT retain the
1053
+ supplied value across MTA re-initializations or reboots.""",
1054
+ "reference" :
1055
+ """ PacketCable MTA Device Provisioning Specification;
1056
+ PacketCable Security Specification.""",
1057
+ }, # scalar
1058
+ "pktcMtaDevProvConfigEncryptAlg" : {
1059
+ "nodetype" : "scalar",
1060
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1061
+ "oid" : "1.3.6.1.2.1.140.1.2.13",
1062
+ "status" : "current",
1063
+ "syntax" : {
1064
+ "type" : { "module" :"PKTC-IETF-MTA-MIB", "name" : "PktcMtaDevProvEncryptAlg"},
1065
+ },
1066
+ "access" : "readwrite",
1067
+ "default" : "des64CbcMode",
1068
+ "description" :
1069
+ """ This object defines the encryption algorithm used for
1070
+ privacy protection of the MTA Configuration File content.""",
1071
+ }, # scalar
1072
+ "pktcMtaDevProvSolicitedKeyTimeout" : {
1073
+ "nodetype" : "scalar",
1074
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1075
+ "oid" : "1.3.6.1.2.1.140.1.2.14",
1076
+ "status" : "current",
1077
+ "syntax" : {
1078
+ "type" : {
1079
+ "basetype" : "Unsigned32",
1080
+ "ranges" : [
1081
+ {
1082
+ "min" : "0",
1083
+ "max" : "180"
1084
+ },
1085
+ ],
1086
+ "range" : {
1087
+ "min" : "0",
1088
+ "max" : "180"
1089
+ },
1090
+ },
1091
+ },
1092
+ "access" : "readwrite",
1093
+ "default" : "3",
1094
+ "units" : "seconds",
1095
+ "description" :
1096
+ """ This object defines a Kerberos Key Management timer on the
1097
+ MTA. It is the time period during which the MTA saves the
1098
+ nonce and Server Kerberos Principal Identifier to match an
1099
+ AP Request and its associated AP Reply response from the
1100
+ Provisioning Server.
1101
+ After the timeout has been exceeded, the client discards
1102
+ this (nonce, Server Kerberos Principal Identifier) pair,
1103
+ after which it will no longer accept a matching AP Reply.
1104
+ This timer only applies when the Provisioning Server
1105
+ initiated key management for SNMPv3 (with a
1106
+ Wake Up message).
1107
+ If this object is set to a zero value, the MTA MUST return
1108
+ an 'inconsistentValue' in response to SNMP SET operations.
1109
+ This object should not be used in non-secure provisioning
1110
+ modes. In non-secure provisioning modes, the MTA MUST
1111
+ return an 'inconsistentValue' in response to SNMP SET
1112
+ operations, and the MTA MUST return a zero value in
1113
+
1114
+
1115
+
1116
+ response to SNMP GET operations.
1117
+ If a value is written into an instance of
1118
+ pktcMtaDevProvSolicitedKeyTimeout, the agent MUST NOT
1119
+ retain the supplied value across MTA re-initializations
1120
+ or reboots.""",
1121
+ }, # scalar
1122
+ "pktcMtaDevProvUnsolicitedKeyMaxTimeout" : {
1123
+ "nodetype" : "scalar",
1124
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1125
+ "oid" : "1.3.6.1.2.1.140.1.2.15",
1126
+ "status" : "current",
1127
+ "syntax" : {
1128
+ "type" : {
1129
+ "basetype" : "Unsigned32",
1130
+ "ranges" : [
1131
+ {
1132
+ "min" : "0",
1133
+ "max" : "600"
1134
+ },
1135
+ ],
1136
+ "range" : {
1137
+ "min" : "0",
1138
+ "max" : "600"
1139
+ },
1140
+ },
1141
+ },
1142
+ "access" : "readonly",
1143
+ "default" : "600",
1144
+ "units" : "seconds",
1145
+ "description" :
1146
+ """ This object defines the timeout value that applies to
1147
+ an MTA-initiated AP-REQ/REP key management exchange with
1148
+ the Provisioning Server in SNMPv3 provisioning.
1149
+ It is the maximum timeout value, and it may not be exceeded
1150
+ in the exponential back-off algorithm. If the DHCP option
1151
+
1152
+
1153
+
1154
+ code 122, sub-option 5, is provided to the MTA, it
1155
+ overwrites this value.
1156
+ In non-secure provisioning modes, the MTA MUST
1157
+ return a zero value in response to SNMP GET
1158
+ operations.""",
1159
+ "reference" :
1160
+ """ PacketCable Security Specification.""",
1161
+ }, # scalar
1162
+ "pktcMtaDevProvUnsolicitedKeyNomTimeout" : {
1163
+ "nodetype" : "scalar",
1164
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1165
+ "oid" : "1.3.6.1.2.1.140.1.2.16",
1166
+ "status" : "current",
1167
+ "syntax" : {
1168
+ "type" : {
1169
+ "basetype" : "Unsigned32",
1170
+ "ranges" : [
1171
+ {
1172
+ "min" : "0",
1173
+ "max" : "600"
1174
+ },
1175
+ ],
1176
+ "range" : {
1177
+ "min" : "0",
1178
+ "max" : "600"
1179
+ },
1180
+ },
1181
+ },
1182
+ "access" : "readonly",
1183
+ "default" : "3",
1184
+ "units" : "seconds",
1185
+ "description" :
1186
+ """ This object defines the starting value of the timeout
1187
+ for the AP-REQ/REP Backoff and Retry mechanism
1188
+ with exponential timeout in SNMPv3 provisioning.
1189
+ If the DHCP option code 122, sub-option 5, is provided
1190
+ the MTA, it overwrites this value.
1191
+ In non-secure provisioning modes, the MTA MUST
1192
+ return a zero value in response to SNMP GET
1193
+ operations.""",
1194
+ "reference" :
1195
+ """ PacketCable Security Specification.""",
1196
+ }, # scalar
1197
+ "pktcMtaDevProvUnsolicitedKeyMaxRetries" : {
1198
+ "nodetype" : "scalar",
1199
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1200
+ "oid" : "1.3.6.1.2.1.140.1.2.17",
1201
+ "status" : "current",
1202
+ "syntax" : {
1203
+ "type" : {
1204
+ "basetype" : "Unsigned32",
1205
+ "ranges" : [
1206
+ {
1207
+ "min" : "0",
1208
+ "max" : "32"
1209
+ },
1210
+ ],
1211
+ "range" : {
1212
+ "min" : "0",
1213
+ "max" : "32"
1214
+ },
1215
+ },
1216
+ },
1217
+ "access" : "readonly",
1218
+ "default" : "8",
1219
+ "description" :
1220
+ """ This object contains a retry counter that applies to
1221
+ an MTA-initiated AP-REQ/REP key management exchange with
1222
+ the Provisioning Server in secure SNMPv3 provisioning.
1223
+ It is the maximum number of retries before the MTA stops
1224
+ attempting to establish a Security Association with
1225
+ Provisioning Server.
1226
+ If the DHCP option code 122, sub-option 5, is provided to
1227
+ the MTA, it overwrites this value.
1228
+ If this object is set to a zero value, the MTA MUST return
1229
+ an 'inconsistentValue' in response to SNMP SET operations.
1230
+ In non-secure provisioning modes, the MTA MUST
1231
+ return a zero value in response to SNMP GET
1232
+ operations.""",
1233
+ "reference" :
1234
+ """ PacketCable Security Specification.""",
1235
+ }, # scalar
1236
+ "pktcMtaDevProvKerbRealmName" : {
1237
+ "nodetype" : "scalar",
1238
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1239
+ "oid" : "1.3.6.1.2.1.140.1.2.18",
1240
+ "status" : "current",
1241
+ "syntax" : {
1242
+ "type" : {
1243
+ "basetype" : "OctetString",
1244
+ "parent module" : {
1245
+ "name" : "SNMP-FRAMEWORK-MIB",
1246
+ "type" : "SnmpAdminString",
1247
+ },
1248
+ "ranges" : [
1249
+ {
1250
+ "min" : "1",
1251
+ "max" : "255"
1252
+ },
1253
+ ],
1254
+ "range" : {
1255
+ "min" : "1",
1256
+ "max" : "255"
1257
+ },
1258
+ },
1259
+ },
1260
+ "access" : "readonly",
1261
+ "description" :
1262
+ """ This object contains the name of the associated
1263
+ provisioning Kerberos realm acquired during the MTA4
1264
+ provisioning step (DHCP Ack) for SNMPv3 provisioning.
1265
+ The uppercase ASCII representation of the associated
1266
+ Kerberos realm name MUST be used by both the Manager (SNMP
1267
+ entity) and the MTA.
1268
+ The Kerberos realm name for the Provisioning Server is
1269
+ supplied to the MTA via DHCP option code 122, sub-option 6,
1270
+ as defined in RFC 3495. In secure SNMP provisioning mode,
1271
+ the value of the Kerberos realm name for the Provisioning
1272
+ Server supplied in the MTA configuration file must match
1273
+ the value supplied in the DHCP option code 122,
1274
+ sub-option 6. Otherwise, the value of this object must
1275
+ contain the value supplied in DHCP Option 122,
1276
+ sub-option 6.""",
1277
+ "reference" :
1278
+ """ PacketCable MTA Device Provisioning Specification;
1279
+ RFC 3495, DHCP Option for CableLabs Client Configuration.""",
1280
+ }, # scalar
1281
+ "pktcMtaDevProvState" : {
1282
+ "nodetype" : "scalar",
1283
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1284
+ "oid" : "1.3.6.1.2.1.140.1.2.19",
1285
+ "status" : "current",
1286
+ "syntax" : {
1287
+ "type" : {
1288
+ "basetype" : "Enumeration",
1289
+ "operational" : {
1290
+ "nodetype" : "namednumber",
1291
+ "number" : "1"
1292
+ },
1293
+ "waitingForSnmpSetInfo" : {
1294
+ "nodetype" : "namednumber",
1295
+ "number" : "2"
1296
+ },
1297
+ "waitingForTftpAddrResponse" : {
1298
+ "nodetype" : "namednumber",
1299
+ "number" : "3"
1300
+ },
1301
+ "waitingForConfigFile" : {
1302
+ "nodetype" : "namednumber",
1303
+ "number" : "4"
1304
+ },
1305
+ },
1306
+ },
1307
+ "access" : "readonly",
1308
+ "description" :
1309
+ """ This object defines the MTA provisioning state.
1310
+ If the state is:
1311
+
1312
+ 'operational(1)', the device has completed the loading
1313
+ and processing of the initialization parameters.
1314
+
1315
+ 'waitingForSnmpSetInfo(2)', the device is waiting on
1316
+ its configuration file download access information.
1317
+ Note that this state is only reported when the MTA
1318
+
1319
+
1320
+
1321
+ SNMP enrollment mechanism is used.
1322
+
1323
+ 'waitingForTftpAddrResponse(3)', the device has sent a
1324
+ DNS request to resolve the server providing the
1325
+ configuration file, and it is awaiting for a response.
1326
+ Note that this state is only reported when the MTA
1327
+ SNMP enrollment mechanism is used.
1328
+
1329
+ 'waitingForConfigFile(4)', the device has sent a
1330
+ request via TFTP or HTTP for the download of its
1331
+ configuration file, and it is awaiting for a response or
1332
+ the file download is in progress.""",
1333
+ "reference" :
1334
+ """ PacketCable MTA Device Provisioning Specification,
1335
+ PacketCable Security Specification.""",
1336
+ }, # scalar
1337
+ "pktcMtaDevSecurity" : {
1338
+ "nodetype" : "node",
1339
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1340
+ "oid" : "1.3.6.1.2.1.140.1.3",
1341
+ }, # node
1342
+ "pktcMtaDevManufacturerCertificate" : {
1343
+ "nodetype" : "scalar",
1344
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1345
+ "oid" : "1.3.6.1.2.1.140.1.3.1",
1346
+ "status" : "current",
1347
+ "syntax" : {
1348
+ "type" : { "module" :"DOCS-IETF-BPI2-MIB", "name" : "DocsX509ASN1DEREncodedCertificate"},
1349
+ },
1350
+ "access" : "readonly",
1351
+ "description" :
1352
+ """ This object contains the MTA Manufacturer Certificate.
1353
+ The object value must be the ASN.1 DER encoding of the MTA
1354
+ manufacturer's X.509 public key certificate. The MTA
1355
+ Manufacturer Certificate is issued to each MTA
1356
+ manufacturer and is installed into each MTA at the time of
1357
+ manufacture or with a secure code download. The specific
1358
+ requirements related to this certificate are defined in
1359
+ the PacketCable or IPCablecom Security specifications.""",
1360
+ "reference" :
1361
+ """ PacketCable Security Specification.""",
1362
+ }, # scalar
1363
+ "pktcMtaDevCertificate" : {
1364
+ "nodetype" : "scalar",
1365
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1366
+ "oid" : "1.3.6.1.2.1.140.1.3.2",
1367
+ "status" : "current",
1368
+ "syntax" : {
1369
+ "type" : { "module" :"DOCS-IETF-BPI2-MIB", "name" : "DocsX509ASN1DEREncodedCertificate"},
1370
+ },
1371
+ "access" : "readonly",
1372
+ "description" :
1373
+ """ This object contains the MTA Device Certificate.
1374
+ The object value must be the ASN.1 DER encoding of the
1375
+ MTA's X.509 public-key certificate issued by the
1376
+ manufacturer and installed into the MTA at the time of
1377
+
1378
+
1379
+
1380
+ manufacture or with a secure code download.
1381
+ This certificate contains the MTA MAC address. The
1382
+ specific requirements related to this certificate are
1383
+ defined in the PacketCable or IPCablecom Security
1384
+ specifications.""",
1385
+ "reference" :
1386
+ """ PacketCable Security Specification.""",
1387
+ }, # scalar
1388
+ "pktcMtaDevCorrelationId" : {
1389
+ "nodetype" : "scalar",
1390
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1391
+ "oid" : "1.3.6.1.2.1.140.1.3.3",
1392
+ "status" : "current",
1393
+ "syntax" : {
1394
+ "type" : { "module" :"", "name" : "Unsigned32"},
1395
+ },
1396
+ "access" : "readonly",
1397
+ "description" :
1398
+ """ This object contains a correlation ID, an arbitrary value
1399
+ generated by the MTA that will be exchanged as part of the
1400
+ device capability data to the Provisioning Application.
1401
+ This random value is used as an identifier to correlate
1402
+ related events in the MTA provisioning sequence.
1403
+ This value is intended for use only during the MTA
1404
+ initialization and configuration file download.""",
1405
+ "reference" :
1406
+ """ PacketCable MTA Device Provisioning Specification.""",
1407
+ }, # scalar
1408
+ "pktcMtaDevTelephonyRootCertificate" : {
1409
+ "nodetype" : "scalar",
1410
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1411
+ "oid" : "1.3.6.1.2.1.140.1.3.4",
1412
+ "status" : "current",
1413
+ "syntax" : {
1414
+ "type" : { "module" :"DOCS-IETF-BPI2-MIB", "name" : "DocsX509ASN1DEREncodedCertificate"},
1415
+ },
1416
+ "access" : "readonly",
1417
+ "description" :
1418
+ """ This object contains the telephony Service Provider Root
1419
+ certificate. The object value is the ASN.1 DER encoding of
1420
+ the IP Telephony Service Provider Root X.509 public key
1421
+ certificate. This certification is stored in the MTA
1422
+ non-volatile memory and can be updated with a secure code
1423
+ download. This certificate is used to validate the initial
1424
+ AS Reply received by the MTA from the Key Distribution
1425
+ Center (KDC) during the MTA initialization. The specific
1426
+ requirements related to this certificate are defined in
1427
+ the PacketCable or IPCablecom Security specifications.""",
1428
+ "reference" :
1429
+ """ PacketCable Security Specification.""",
1430
+ }, # scalar
1431
+ "pktcMtaDevRealmAvailSlot" : {
1432
+ "nodetype" : "scalar",
1433
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1434
+ "oid" : "1.3.6.1.2.1.140.1.3.5",
1435
+ "status" : "current",
1436
+ "syntax" : {
1437
+ "type" : {
1438
+ "basetype" : "Unsigned32",
1439
+ "ranges" : [
1440
+ {
1441
+ "min" : "0",
1442
+ "max" : "64"
1443
+ },
1444
+ ],
1445
+ "range" : {
1446
+ "min" : "0",
1447
+ "max" : "64"
1448
+ },
1449
+ },
1450
+ },
1451
+ "access" : "readonly",
1452
+ "description" :
1453
+ """ This object contains the index number of the first
1454
+ available entry in the realm table (pktcMtaDevRealmTable).
1455
+ If all the entries in the realm table have been assigned,
1456
+ this object contains the value of zero.
1457
+ A management station should create new entries in the
1458
+ realm table, using the following procedure:
1459
+
1460
+ First, issue a management protocol retrieval operation
1461
+ to determine the value of the first available index in the
1462
+ realm table (pktcMtaDevRealmAvailSlot).
1463
+
1464
+ Second, issue a management protocol SET operation
1465
+ to create an instance of the pktcMtaDevRealmStatus
1466
+ object by setting its value to 'createAndWait(5)'.
1467
+
1468
+ Third, if the SET operation succeeded, continue
1469
+ modifying the object instances corresponding to the newly
1470
+ created conceptual row, without fear of collision with
1471
+ other management stations. When all necessary conceptual
1472
+ columns of the row are properly populated (via SET
1473
+ operations or default values), the management station may
1474
+ SET the pktcMtaDevRealmStatus object to 'active(1)'.""",
1475
+ }, # scalar
1476
+ "pktcMtaDevRealmTable" : {
1477
+ "nodetype" : "table",
1478
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1479
+ "oid" : "1.3.6.1.2.1.140.1.3.6",
1480
+ "status" : "current",
1481
+ "description" :
1482
+ """ This object contains the realm table.
1483
+ The CMS table (pktcMtaDevCmsTable) and the realm table
1484
+ (pktcMtaDevRealmTable) are used for managing the MTA-CMS
1485
+ Security Associations. The realm table defines the
1486
+ Kerberos realms for the Application Servers (CMSes and the
1487
+ Provisioning Server).""",
1488
+ }, # table
1489
+ "pktcMtaDevRealmEntry" : {
1490
+ "nodetype" : "row",
1491
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1492
+ "oid" : "1.3.6.1.2.1.140.1.3.6.1",
1493
+ "create" : "true",
1494
+ "status" : "current",
1495
+ "linkage" : [
1496
+ "pktcMtaDevRealmIndex",
1497
+ ],
1498
+ "description" :
1499
+ """ This table entry object lists the MTA security parameters
1500
+ for a single Kerberos realm. The conceptual rows MUST NOT
1501
+ persist across MTA reboots.""",
1502
+ }, # row
1503
+ "pktcMtaDevRealmIndex" : {
1504
+ "nodetype" : "column",
1505
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1506
+ "oid" : "1.3.6.1.2.1.140.1.3.6.1.1",
1507
+ "status" : "current",
1508
+ "syntax" : {
1509
+ "type" : {
1510
+ "basetype" : "Unsigned32",
1511
+ "ranges" : [
1512
+ {
1513
+ "min" : "1",
1514
+ "max" : "64"
1515
+ },
1516
+ ],
1517
+ "range" : {
1518
+ "min" : "1",
1519
+ "max" : "64"
1520
+ },
1521
+ },
1522
+ },
1523
+ "access" : "noaccess",
1524
+ "description" :
1525
+ """ This object defines the realm table index.""",
1526
+ }, # column
1527
+ "pktcMtaDevRealmName" : {
1528
+ "nodetype" : "column",
1529
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1530
+ "oid" : "1.3.6.1.2.1.140.1.3.6.1.2",
1531
+ "status" : "current",
1532
+ "syntax" : {
1533
+ "type" : {
1534
+ "basetype" : "OctetString",
1535
+ "parent module" : {
1536
+ "name" : "SNMP-FRAMEWORK-MIB",
1537
+ "type" : "SnmpAdminString",
1538
+ },
1539
+ "ranges" : [
1540
+ {
1541
+ "min" : "1",
1542
+ "max" : "255"
1543
+ },
1544
+ ],
1545
+ "range" : {
1546
+ "min" : "1",
1547
+ "max" : "255"
1548
+ },
1549
+ },
1550
+ },
1551
+ "access" : "readwrite",
1552
+ "description" :
1553
+ """ This object identifies the Kerberos realm name in all
1554
+ capitals. The MTA MUST prohibit the instantiation of any
1555
+ two rows with identical Kerberos realm names. The MTA MUST
1556
+ also verify that any search operation involving Kerberos
1557
+ realm names is done using the uppercase ASCII
1558
+ representation of the characters.""",
1559
+ }, # column
1560
+ "pktcMtaDevRealmPkinitGracePeriod" : {
1561
+ "nodetype" : "column",
1562
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1563
+ "oid" : "1.3.6.1.2.1.140.1.3.6.1.3",
1564
+ "status" : "current",
1565
+ "syntax" : {
1566
+ "type" : {
1567
+ "basetype" : "Unsigned32",
1568
+ "ranges" : [
1569
+ {
1570
+ "min" : "15",
1571
+ "max" : "600"
1572
+ },
1573
+ ],
1574
+ "range" : {
1575
+ "min" : "15",
1576
+ "max" : "600"
1577
+ },
1578
+ },
1579
+ },
1580
+ "access" : "readwrite",
1581
+ "default" : "15",
1582
+ "units" : "minutes",
1583
+ "description" :
1584
+ """ This object contains the PKINIT Grace Period. For the
1585
+ purpose of key management with Application Servers (CMSes
1586
+
1587
+
1588
+
1589
+ or the Provisioning Server), the MTA must utilize the
1590
+ PKINIT exchange to obtain Application Server tickets. The
1591
+ MTA may utilize the PKINIT exchange to obtain Ticket
1592
+ Granting Tickets (TGTs), which are then used to obtain
1593
+ Application Server tickets in a TGS exchange.
1594
+ The PKINIT exchange occurs according to the current Ticket
1595
+ Expiration Time (TicketEXP) and on the PKINIT Grace Period
1596
+ (PKINITGP). The MTA MUST initiate the PKINIT exchange at
1597
+ the time: TicketEXP - PKINITGP.""",
1598
+ "reference" :
1599
+ """ PacketCable Security Specification.""",
1600
+ }, # column
1601
+ "pktcMtaDevRealmTgsGracePeriod" : {
1602
+ "nodetype" : "column",
1603
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1604
+ "oid" : "1.3.6.1.2.1.140.1.3.6.1.4",
1605
+ "status" : "current",
1606
+ "syntax" : {
1607
+ "type" : {
1608
+ "basetype" : "Unsigned32",
1609
+ "ranges" : [
1610
+ {
1611
+ "min" : "1",
1612
+ "max" : "600"
1613
+ },
1614
+ ],
1615
+ "range" : {
1616
+ "min" : "1",
1617
+ "max" : "600"
1618
+ },
1619
+ },
1620
+ },
1621
+ "access" : "readwrite",
1622
+ "default" : "10",
1623
+ "units" : "minutes",
1624
+ "description" :
1625
+ """ This object contains the Ticket Granting Server Grace
1626
+ Period (TGSGP). The Ticket Granting Server (TGS)
1627
+ Request/Reply exchange may be performed by the MTA
1628
+ on demand whenever an Application Server ticket is
1629
+ needed to establish security parameters. If the MTA
1630
+ possesses a ticket that corresponds to the Provisioning
1631
+ Server or a CMS that currently exists in the CMS table,
1632
+ the MTA MUST initiate the TGS Request/Reply exchange
1633
+ at the time: TicketEXP - TGSGP.""",
1634
+ "reference" :
1635
+ """ PacketCable Security Specification.""",
1636
+ }, # column
1637
+ "pktcMtaDevRealmOrgName" : {
1638
+ "nodetype" : "column",
1639
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1640
+ "oid" : "1.3.6.1.2.1.140.1.3.6.1.5",
1641
+ "status" : "current",
1642
+ "syntax" : {
1643
+ "type" : { "module" :"SYSAPPL-MIB", "name" : "LongUtf8String"},
1644
+ },
1645
+ "access" : "readwrite",
1646
+ "description" :
1647
+ """ This object contains the X.500 organization name attribute
1648
+ as defined in the subject name of the service provider
1649
+ certificate.""",
1650
+ "reference" :
1651
+ """ PacketCable Security Specification;
1652
+ RFCs 3280 and 4630, Internet X.509 Public Key
1653
+ Infrastructure Certificate and Certificate Revocation List
1654
+ (CRL) Profile""",
1655
+ }, # column
1656
+ "pktcMtaDevRealmUnsolicitedKeyMaxTimeout" : {
1657
+ "nodetype" : "column",
1658
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1659
+ "oid" : "1.3.6.1.2.1.140.1.3.6.1.6",
1660
+ "status" : "current",
1661
+ "syntax" : {
1662
+ "type" : {
1663
+ "basetype" : "Unsigned32",
1664
+ "ranges" : [
1665
+ {
1666
+ "min" : "1",
1667
+ "max" : "600"
1668
+ },
1669
+ ],
1670
+ "range" : {
1671
+ "min" : "1",
1672
+ "max" : "600"
1673
+ },
1674
+ },
1675
+ },
1676
+ "access" : "readwrite",
1677
+ "default" : "100",
1678
+ "units" : "seconds",
1679
+ "description" :
1680
+ """ This object specifies the maximum time the MTA will
1681
+ attempt to perform the exponential back-off algorithm.
1682
+ This timer only applies when the MTA initiated key
1683
+ management. If the DHCP option code 122, sub-option 4, is
1684
+ provided to the MTA, it overwrites this value.
1685
+
1686
+ Unsolicited key updates are retransmitted according to an
1687
+ exponential back-off mechanism using two timers and a
1688
+ maximum retry counter for AS replies.
1689
+ The initial retransmission timer value is the nominal
1690
+ timer value (pktcMtaDevRealmUnsolicitedKeyNomTimeout). The
1691
+ retransmissions occur with an exponentially increasing
1692
+ interval that caps at the maximum timeout value
1693
+ (pktcMtaDevRealmUnsolicitedKeyMaxTimeout).
1694
+ Retransmissions stop when the maximum retry counter is
1695
+ reached (pktcMatDevRealmUnsolicitedMaxRetries).
1696
+
1697
+ For example, with values of 3 seconds for the nominal
1698
+ timer, 20 seconds for the maximum timeout, and 5 retries
1699
+ max, retransmission intervals will be 3 s, 6 s,
1700
+ 12 s, 20 s, and 20 s, and retransmissions then stop because
1701
+ the maximum number of retries has been reached.""",
1702
+ "reference" :
1703
+ """ PacketCable Security Specification.""",
1704
+ }, # column
1705
+ "pktcMtaDevRealmUnsolicitedKeyNomTimeout" : {
1706
+ "nodetype" : "column",
1707
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1708
+ "oid" : "1.3.6.1.2.1.140.1.3.6.1.7",
1709
+ "status" : "current",
1710
+ "syntax" : {
1711
+ "type" : {
1712
+ "basetype" : "Unsigned32",
1713
+ "ranges" : [
1714
+ {
1715
+ "min" : "100",
1716
+ "max" : "600000"
1717
+ },
1718
+ ],
1719
+ "range" : {
1720
+ "min" : "100",
1721
+ "max" : "600000"
1722
+ },
1723
+ },
1724
+ },
1725
+ "access" : "readwrite",
1726
+ "default" : "3000",
1727
+ "units" : "milliseconds",
1728
+ "description" :
1729
+ """ This object specifies the initial timeout value
1730
+ for the AS-REQ/AS-REP exponential back-off and retry
1731
+ mechanism. If the DHCP option code 122, sub-option 4, is
1732
+ provided to the MTA, it overwrites this value.
1733
+ This value should account for the average roundtrip
1734
+ time between the MTA and the KDC, as well as the
1735
+ processing delay on the KDC.
1736
+
1737
+
1738
+
1739
+
1740
+ Unsolicited key updates are retransmitted according to an
1741
+ exponential back-off mechanism using two timers and a
1742
+ maximum retry counter for AS replies.
1743
+ The initial retransmission timer value is the nominal
1744
+ timer value (pktcMtaDevRealmUnsolicitedKeyNomTimeout). The
1745
+ retransmissions occur with an exponentially increasing
1746
+ interval that caps at the maximum timeout value
1747
+ (pktcMtaDevRealmUnsolicitedKeyMaxTimeout).
1748
+ Retransmissions stop when the maximum retry counter is
1749
+ reached (pktcMatDevRealmUnsolicitedMaxRetries).
1750
+
1751
+ For example, with values of 3 seconds for the nominal
1752
+ timer, 20 seconds for the maximum timeout, and 5 retries
1753
+ max, in retransmission intervals will be 3 s, 6 s,
1754
+ 12 s, 20 s, and 20 s; retransmissions then stop because
1755
+ the maximum number of retries has been reached.""",
1756
+ "reference" :
1757
+ """ PacketCable Security Specification.""",
1758
+ }, # column
1759
+ "pktcMtaDevRealmUnsolicitedKeyMaxRetries" : {
1760
+ "nodetype" : "column",
1761
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1762
+ "oid" : "1.3.6.1.2.1.140.1.3.6.1.8",
1763
+ "status" : "current",
1764
+ "syntax" : {
1765
+ "type" : {
1766
+ "basetype" : "Unsigned32",
1767
+ "ranges" : [
1768
+ {
1769
+ "min" : "0",
1770
+ "max" : "1024"
1771
+ },
1772
+ ],
1773
+ "range" : {
1774
+ "min" : "0",
1775
+ "max" : "1024"
1776
+ },
1777
+ },
1778
+ },
1779
+ "access" : "readwrite",
1780
+ "default" : "5",
1781
+ "description" :
1782
+ """ This object specifies the maximum number of retries the
1783
+ MTA attempts to obtain a ticket from the KDC.
1784
+
1785
+ Unsolicited key updates are retransmitted according to an
1786
+ exponential back-off mechanism using two timers and a
1787
+ maximum retry counter for AS replies.
1788
+ The initial retransmission timer value is the nominal
1789
+ timer value (pktcMtaDevRealmUnsolicitedKeyNomTimeout). The
1790
+ retransmissions occur with an exponentially increasing
1791
+ interval that caps at the maximum timeout value
1792
+ (pktcMtaDevRealmUnsolicitedKeyMaxTimeout).
1793
+ Retransmissions stop when the maximum retry counter is
1794
+ reached (pktcMatDevRealmUnsolicitedMaxRetries).
1795
+
1796
+ For example, with values of 3 seconds for the nominal
1797
+ timer, 20 seconds for the maximum timeout, and 5 retries
1798
+ max, retransmission intervals will be 3 s, 6 s,
1799
+ 12 s, 20 s, and 20 s; retransmissions then stop because
1800
+ the maximum number of retries has been reached.""",
1801
+ "reference" :
1802
+ """ PacketCable Security Specification.""",
1803
+ }, # column
1804
+ "pktcMtaDevRealmStatus" : {
1805
+ "nodetype" : "column",
1806
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1807
+ "oid" : "1.3.6.1.2.1.140.1.3.6.1.9",
1808
+ "status" : "current",
1809
+ "syntax" : {
1810
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
1811
+ },
1812
+ "access" : "readwrite",
1813
+ "description" :
1814
+ """ This object defines the row status of this realm in the
1815
+ realm table (pktcMtaDevRealmTable).
1816
+
1817
+ An entry in this table is not qualified for activation
1818
+ until the object instances of all corresponding columns
1819
+ have been initialized, either by default values, or via
1820
+ explicit SET operations. Until all object instances in
1821
+ this row are initialized, the status value for this realm
1822
+ must be 'notReady(3)'.
1823
+ In particular, two columnar objects must be explicitly
1824
+ SET: the realm name (pktcMtaDevRealmName) and the
1825
+ organization name (pktcMtaDevRealmOrgName). Once these 2
1826
+ objects have been set and the row status is SET to
1827
+ 'active(1)', the MTA MUST NOT allow any modification of
1828
+ these 2 object values.
1829
+ The value of this object has no effect on whether other
1830
+ columnar objects in this row can be modified.""",
1831
+ }, # column
1832
+ "pktcMtaDevCmsAvailSlot" : {
1833
+ "nodetype" : "scalar",
1834
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1835
+ "oid" : "1.3.6.1.2.1.140.1.3.7",
1836
+ "status" : "current",
1837
+ "syntax" : {
1838
+ "type" : {
1839
+ "basetype" : "Unsigned32",
1840
+ "ranges" : [
1841
+ {
1842
+ "min" : "0",
1843
+ "max" : "128"
1844
+ },
1845
+ ],
1846
+ "range" : {
1847
+ "min" : "0",
1848
+ "max" : "128"
1849
+ },
1850
+ },
1851
+ },
1852
+ "access" : "readonly",
1853
+ "description" :
1854
+ """ This object contains the index number of the first
1855
+ available entry in the CMS table (pktcMtaDevCmsTable).
1856
+ If all the entries in the CMS table have been assigned,
1857
+ this object contains the value of zero.
1858
+ A management station should create new entries in the
1859
+ CMS table, using the following procedure:
1860
+
1861
+ First, issue a management protocol retrieval operation
1862
+ to determine the value of the first available index in the
1863
+ CMS table (pktcMtaDevCmsAvailSlot).
1864
+
1865
+ Second, issue a management protocol SET operation
1866
+ to create an instance of the pktcMtaDevCmsStatus
1867
+ object by setting its value to 'createAndWait(5)'.
1868
+
1869
+ Third, if the SET operation succeeded, continue
1870
+ modifying the object instances corresponding to the newly
1871
+ created conceptual row, without fear of collision with
1872
+ other management stations. When all necessary conceptual
1873
+ columns of the row are properly populated (via SET
1874
+ operations or default values), the management station may
1875
+ SET the pktcMtaDevCmsStatus object to 'active(1)'.""",
1876
+ }, # scalar
1877
+ "pktcMtaDevCmsTable" : {
1878
+ "nodetype" : "table",
1879
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1880
+ "oid" : "1.3.6.1.2.1.140.1.3.8",
1881
+ "status" : "current",
1882
+ "description" :
1883
+ """ This object defines the CMS table.
1884
+ The CMS table (pktcMtaDevCmsTable) and the realm table
1885
+ (pktcMtaDevRealmTable) are used for managing security
1886
+ between the MTA and CMSes. Each CMS table entry defines
1887
+ a CMS the managed MTA is allowed to communicate with
1888
+ and contains security parameters for key management with
1889
+ that CMS.""",
1890
+ }, # table
1891
+ "pktcMtaDevCmsEntry" : {
1892
+ "nodetype" : "row",
1893
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1894
+ "oid" : "1.3.6.1.2.1.140.1.3.8.1",
1895
+ "create" : "true",
1896
+ "status" : "current",
1897
+ "linkage" : [
1898
+ "pktcMtaDevCmsIndex",
1899
+ ],
1900
+ "description" :
1901
+ """ This table entry object lists the MTA key management
1902
+ parameters used when establishing Security Associations
1903
+ with a CMS. The conceptual rows MUST NOT persist across
1904
+ MTA reboots.""",
1905
+ }, # row
1906
+ "pktcMtaDevCmsIndex" : {
1907
+ "nodetype" : "column",
1908
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1909
+ "oid" : "1.3.6.1.2.1.140.1.3.8.1.1",
1910
+ "status" : "current",
1911
+ "syntax" : {
1912
+ "type" : {
1913
+ "basetype" : "Unsigned32",
1914
+ "ranges" : [
1915
+ {
1916
+ "min" : "1",
1917
+ "max" : "128"
1918
+ },
1919
+ ],
1920
+ "range" : {
1921
+ "min" : "1",
1922
+ "max" : "128"
1923
+ },
1924
+ },
1925
+ },
1926
+ "access" : "noaccess",
1927
+ "description" :
1928
+ """ This object defines the CMS table index.""",
1929
+ }, # column
1930
+ "pktcMtaDevCmsFqdn" : {
1931
+ "nodetype" : "column",
1932
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1933
+ "oid" : "1.3.6.1.2.1.140.1.3.8.1.2",
1934
+ "status" : "current",
1935
+ "syntax" : {
1936
+ "type" : {
1937
+ "basetype" : "OctetString",
1938
+ "parent module" : {
1939
+ "name" : "SNMP-FRAMEWORK-MIB",
1940
+ "type" : "SnmpAdminString",
1941
+ },
1942
+ "ranges" : [
1943
+ {
1944
+ "min" : "1",
1945
+ "max" : "255"
1946
+ },
1947
+ ],
1948
+ "range" : {
1949
+ "min" : "1",
1950
+ "max" : "255"
1951
+ },
1952
+ },
1953
+ },
1954
+ "access" : "readwrite",
1955
+ "description" :
1956
+ """ This object specifies the CMS FQDN. The MTA must
1957
+ prohibit the instantiation of any two rows with identical
1958
+ FQDNs. The MTA must also verify that any search and/or
1959
+ comparison operation involving a CMS FQDN is case
1960
+ insensitive. The MTA must resolve the CMS FQDN as required
1961
+ by the corresponding PacketCable Specifications.""",
1962
+ "reference" :
1963
+ """ PacketCable MTA Device Provisioning Specification;
1964
+ PacketCable Security Specification;
1965
+ PacketCable Network-Based Call Signaling Protocol
1966
+ Specification.""",
1967
+ }, # column
1968
+ "pktcMtaDevCmsKerbRealmName" : {
1969
+ "nodetype" : "column",
1970
+ "moduleName" : "PKTC-IETF-MTA-MIB",
1971
+ "oid" : "1.3.6.1.2.1.140.1.3.8.1.3",
1972
+ "status" : "current",
1973
+ "syntax" : {
1974
+ "type" : {
1975
+ "basetype" : "OctetString",
1976
+ "parent module" : {
1977
+ "name" : "SNMP-FRAMEWORK-MIB",
1978
+ "type" : "SnmpAdminString",
1979
+ },
1980
+ "ranges" : [
1981
+ {
1982
+ "min" : "1",
1983
+ "max" : "255"
1984
+ },
1985
+ ],
1986
+ "range" : {
1987
+ "min" : "1",
1988
+ "max" : "255"
1989
+ },
1990
+ },
1991
+ },
1992
+ "access" : "readwrite",
1993
+ "description" :
1994
+ """ This object identifies the Kerberos realm name in uppercase
1995
+ characters associated with the CMS defined in this
1996
+
1997
+
1998
+
1999
+ conceptual row. The object value is a reference
2000
+ point to the corresponding Kerberos realm name in the
2001
+ realm table (pktcMtaDevRealmTable).""",
2002
+ }, # column
2003
+ "pktcMtaDevCmsMaxClockSkew" : {
2004
+ "nodetype" : "column",
2005
+ "moduleName" : "PKTC-IETF-MTA-MIB",
2006
+ "oid" : "1.3.6.1.2.1.140.1.3.8.1.4",
2007
+ "status" : "current",
2008
+ "syntax" : {
2009
+ "type" : {
2010
+ "basetype" : "Unsigned32",
2011
+ "ranges" : [
2012
+ {
2013
+ "min" : "1",
2014
+ "max" : "1800"
2015
+ },
2016
+ ],
2017
+ "range" : {
2018
+ "min" : "1",
2019
+ "max" : "1800"
2020
+ },
2021
+ },
2022
+ },
2023
+ "access" : "readwrite",
2024
+ "default" : "300",
2025
+ "units" : "seconds",
2026
+ "description" :
2027
+ """ This object specifies the maximum allowable clock skew
2028
+ between the MTA and the CMS defined in this row.""",
2029
+ }, # column
2030
+ "pktcMtaDevCmsSolicitedKeyTimeout" : {
2031
+ "nodetype" : "column",
2032
+ "moduleName" : "PKTC-IETF-MTA-MIB",
2033
+ "oid" : "1.3.6.1.2.1.140.1.3.8.1.5",
2034
+ "status" : "current",
2035
+ "syntax" : {
2036
+ "type" : {
2037
+ "basetype" : "Unsigned32",
2038
+ "ranges" : [
2039
+ {
2040
+ "min" : "100",
2041
+ "max" : "30000"
2042
+ },
2043
+ ],
2044
+ "range" : {
2045
+ "min" : "100",
2046
+ "max" : "30000"
2047
+ },
2048
+ },
2049
+ },
2050
+ "access" : "readwrite",
2051
+ "default" : "1000",
2052
+ "units" : "milliseconds",
2053
+ "description" :
2054
+ """ This object defines a Kerberos Key Management timer on the
2055
+ MTA. It is the time period during which the MTA saves the
2056
+ nonce and Server Kerberos Principal Identifier to match an
2057
+ AP Request and its associated AP Reply response from the
2058
+ CMS. This timer only applies when the CMS initiated key
2059
+ management (with a Wake Up message or a Rekey message).""",
2060
+ "reference" :
2061
+ """ PacketCable Security Specification.""",
2062
+ }, # column
2063
+ "pktcMtaDevCmsUnsolicitedKeyMaxTimeout" : {
2064
+ "nodetype" : "column",
2065
+ "moduleName" : "PKTC-IETF-MTA-MIB",
2066
+ "oid" : "1.3.6.1.2.1.140.1.3.8.1.6",
2067
+ "status" : "current",
2068
+ "syntax" : {
2069
+ "type" : {
2070
+ "basetype" : "Unsigned32",
2071
+ "ranges" : [
2072
+ {
2073
+ "min" : "1",
2074
+ "max" : "600"
2075
+ },
2076
+ ],
2077
+ "range" : {
2078
+ "min" : "1",
2079
+ "max" : "600"
2080
+ },
2081
+ },
2082
+ },
2083
+ "access" : "readwrite",
2084
+ "default" : "600",
2085
+ "units" : "seconds",
2086
+ "description" :
2087
+ """ This object defines the timeout value that only applies
2088
+ to an MTA-initiated key management exchange. It is the
2089
+ maximum timeout, and it may not be exceeded in the
2090
+ exponential back-off algorithm.""",
2091
+ "reference" :
2092
+ """ PacketCable Security Specification.""",
2093
+ }, # column
2094
+ "pktcMtaDevCmsUnsolicitedKeyNomTimeout" : {
2095
+ "nodetype" : "column",
2096
+ "moduleName" : "PKTC-IETF-MTA-MIB",
2097
+ "oid" : "1.3.6.1.2.1.140.1.3.8.1.7",
2098
+ "status" : "current",
2099
+ "syntax" : {
2100
+ "type" : {
2101
+ "basetype" : "Unsigned32",
2102
+ "ranges" : [
2103
+ {
2104
+ "min" : "100",
2105
+ "max" : "30000"
2106
+ },
2107
+ ],
2108
+ "range" : {
2109
+ "min" : "100",
2110
+ "max" : "30000"
2111
+ },
2112
+ },
2113
+ },
2114
+ "access" : "readwrite",
2115
+ "default" : "500",
2116
+ "units" : "milliseconds",
2117
+ "description" :
2118
+ """ This object defines the starting value of the timeout
2119
+ for an MTA-initiated key management. It should account for
2120
+ the average roundtrip time between the MTA and the CMS and
2121
+ the processing time on the CMS.""",
2122
+ "reference" :
2123
+ """ PacketCable Security Specification.""",
2124
+ }, # column
2125
+ "pktcMtaDevCmsUnsolicitedKeyMaxRetries" : {
2126
+ "nodetype" : "column",
2127
+ "moduleName" : "PKTC-IETF-MTA-MIB",
2128
+ "oid" : "1.3.6.1.2.1.140.1.3.8.1.8",
2129
+ "status" : "current",
2130
+ "syntax" : {
2131
+ "type" : {
2132
+ "basetype" : "Unsigned32",
2133
+ "ranges" : [
2134
+ {
2135
+ "min" : "0",
2136
+ "max" : "1024"
2137
+ },
2138
+ ],
2139
+ "range" : {
2140
+ "min" : "0",
2141
+ "max" : "1024"
2142
+ },
2143
+ },
2144
+ },
2145
+ "access" : "readwrite",
2146
+ "default" : "5",
2147
+ "description" :
2148
+ """ This object contains the maximum number of retries before
2149
+ the MTA stops attempting to establish a Security
2150
+ Association with the CMS.""",
2151
+ "reference" :
2152
+ """ PacketCable Security Specification.""",
2153
+ }, # column
2154
+ "pktcMtaDevCmsIpsecCtrl" : {
2155
+ "nodetype" : "column",
2156
+ "moduleName" : "PKTC-IETF-MTA-MIB",
2157
+ "oid" : "1.3.6.1.2.1.140.1.3.8.1.9",
2158
+ "status" : "current",
2159
+ "syntax" : {
2160
+ "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
2161
+ },
2162
+ "access" : "readonly",
2163
+ "default" : "true",
2164
+ "description" :
2165
+ """ This object specifies the MTA IPSec control flag.
2166
+ If the object value is 'true', the MTA must use Kerberos
2167
+ Key Management and IPsec to communicate with this CMS. If
2168
+ it is 'false', IPSec Signaling Security and Kerberos key
2169
+ management are disabled for this specific CMS.""",
2170
+ }, # column
2171
+ "pktcMtaDevCmsStatus" : {
2172
+ "nodetype" : "column",
2173
+ "moduleName" : "PKTC-IETF-MTA-MIB",
2174
+ "oid" : "1.3.6.1.2.1.140.1.3.8.1.10",
2175
+ "status" : "current",
2176
+ "syntax" : {
2177
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
2178
+ },
2179
+ "access" : "readwrite",
2180
+ "description" :
2181
+ """ This object defines the row status associated with this
2182
+ particular CMS in the CMS table (pktcMtaDevCmsTable).
2183
+
2184
+ An entry in this table is not qualified for activation
2185
+ until the object instances of all corresponding columns
2186
+ have been initialized, either by default values or via
2187
+ explicit SET operations. Until all object instances in
2188
+ this row are initialized, the status value for this realm
2189
+ must be 'notReady(3)'.
2190
+ In particular, two columnar objects must be SET: the
2191
+ CMS FQDN (pktcMtaDevCmsFqdn) and the Kerberos realm name
2192
+ (pktcMtaDevCmsKerbRealmName). Once these 2 objects have
2193
+ been set and the row status is SET to 'active(1)', the MTA
2194
+ MUST NOT allow any modification of these 2 object values.
2195
+
2196
+ The value of this object has no effect on
2197
+ whether other columnar objects in this row can be
2198
+ modified.""",
2199
+ }, # column
2200
+ "pktcMtaDevResetKrbTickets" : {
2201
+ "nodetype" : "scalar",
2202
+ "moduleName" : "PKTC-IETF-MTA-MIB",
2203
+ "oid" : "1.3.6.1.2.1.140.1.3.9",
2204
+ "status" : "current",
2205
+ "syntax" : {
2206
+ "type" : {
2207
+ "basetype" : "Bits",
2208
+ "invalidateProvOnReboot" : {
2209
+ "nodetype" : "namednumber",
2210
+ "number" : "0"
2211
+ },
2212
+ "invalidateAllCmsOnReboot" : {
2213
+ "nodetype" : "namednumber",
2214
+ "number" : "1"
2215
+ },
2216
+ },
2217
+ },
2218
+ "access" : "readwrite",
2219
+ "default" : "()",
2220
+ "description" :
2221
+ """ This object defines a Kerberos Ticket Control Mask that
2222
+ instructs the MTA to invalidate the specific Application
2223
+
2224
+
2225
+
2226
+ Server Kerberos ticket(s) that are stored locally in the
2227
+ MTA NVRAM (non-volatile or persistent memory).
2228
+ If the MTA does not store Kerberos tickets in NVRAM, it
2229
+ MUST ignore setting of this object and MUST report a BITS
2230
+ value of zero when the object is read.
2231
+ If the MTA supports Kerberos tickets storage in NVRAM, the
2232
+ object value is encoded as follows:
2233
+ - Setting the invalidateProvOnReboot bit (bit 0) to 1
2234
+ means that the MTA MUST invalidate the Kerberos
2235
+ Application Ticket(s) for the Provisioning Application
2236
+ at the next MTA reboot if secure SNMP provisioning mode
2237
+ is used. In non-secure provisioning modes, the MTA MUST
2238
+ return an 'inconsistentValue' in response to SNMP SET
2239
+ operations with a bit 0 set to 1.
2240
+ - Setting the invalidateAllCmsOnReboot bit (bit 1) to 1
2241
+ means that the MTA MUST invalidate the Kerberos
2242
+ Application Ticket(s) for all CMSes currently assigned
2243
+ to the MTA endpoints.
2244
+ If a value is written into an instance of
2245
+ pktcMtaDevResetKrbTickets, the agent MUST retain the
2246
+ supplied value across an MTA re-initialization or
2247
+ reboot.""",
2248
+ "reference" :
2249
+ """PacketCable Security Specification.""",
2250
+ }, # scalar
2251
+ "pktcMtaDevErrors" : {
2252
+ "nodetype" : "node",
2253
+ "moduleName" : "PKTC-IETF-MTA-MIB",
2254
+ "oid" : "1.3.6.1.2.1.140.1.4",
2255
+ }, # node
2256
+ "pktcMtaDevErrorsTooManyErrors" : {
2257
+ "nodetype" : "node",
2258
+ "moduleName" : "PKTC-IETF-MTA-MIB",
2259
+ "oid" : "1.3.6.1.2.1.140.1.4.1",
2260
+ "status" : "current",
2261
+ "description" :
2262
+ """This object defines the OID corresponding to the error
2263
+ condition when too many errors are encountered in the
2264
+ MTA configuration file during provisioning.""",
2265
+ }, # node
2266
+ "pktcMtaConformance" : {
2267
+ "nodetype" : "node",
2268
+ "moduleName" : "PKTC-IETF-MTA-MIB",
2269
+ "oid" : "1.3.6.1.2.1.140.2",
2270
+ }, # node
2271
+ "pktcMtaCompliances" : {
2272
+ "nodetype" : "node",
2273
+ "moduleName" : "PKTC-IETF-MTA-MIB",
2274
+ "oid" : "1.3.6.1.2.1.140.2.1",
2275
+ }, # node
2276
+ "pktcMtaGroups" : {
2277
+ "nodetype" : "node",
2278
+ "moduleName" : "PKTC-IETF-MTA-MIB",
2279
+ "oid" : "1.3.6.1.2.1.140.2.2",
2280
+ }, # node
2281
+ }, # nodes
2282
+
2283
+ "notifications" : {
2284
+ "pktcMtaDevProvisioningEnrollment" : {
2285
+ "nodetype" : "notification",
2286
+ "moduleName" : "PKTC-IETF-MTA-MIB",
2287
+ "oid" : "1.3.6.1.2.1.140.0.1",
2288
+ "status" : "current",
2289
+ "objects" : {
2290
+ "sysDescr" : {
2291
+ "nodetype" : "object",
2292
+ "module" : "SNMPv2-MIB"
2293
+ },
2294
+ "pktcMtaDevSwCurrentVers" : {
2295
+ "nodetype" : "object",
2296
+ "module" : "PKTC-IETF-MTA-MIB"
2297
+ },
2298
+ "pktcMtaDevTypeIdentifier" : {
2299
+ "nodetype" : "object",
2300
+ "module" : "PKTC-IETF-MTA-MIB"
2301
+ },
2302
+ "ifPhysAddress" : {
2303
+ "nodetype" : "object",
2304
+ "module" : "IF-MIB"
2305
+ },
2306
+ "pktcMtaDevCorrelationId" : {
2307
+ "nodetype" : "object",
2308
+ "module" : "PKTC-IETF-MTA-MIB"
2309
+ },
2310
+ },
2311
+ "description" :
2312
+ """ This INFORM notification is issued by the MTA to initiate
2313
+ the PacketCable provisioning process when the MTA SNMP
2314
+ enrollment mechanism is used.
2315
+ It contains the system description, the current software
2316
+ version, the MTA device type identifier, the MTA MAC
2317
+ address (obtained in the MTA ifTable in the ifPhysAddress
2318
+ object that corresponds to the ifIndex 1), and a
2319
+ correlation ID.""",
2320
+ }, # notification
2321
+ "pktcMtaDevProvisioningStatus" : {
2322
+ "nodetype" : "notification",
2323
+ "moduleName" : "PKTC-IETF-MTA-MIB",
2324
+ "oid" : "1.3.6.1.2.1.140.0.2",
2325
+ "status" : "current",
2326
+ "objects" : {
2327
+ "ifPhysAddress" : {
2328
+ "nodetype" : "object",
2329
+ "module" : "IF-MIB"
2330
+ },
2331
+ "pktcMtaDevCorrelationId" : {
2332
+ "nodetype" : "object",
2333
+ "module" : "PKTC-IETF-MTA-MIB"
2334
+ },
2335
+ "pktcMtaDevProvisioningState" : {
2336
+ "nodetype" : "object",
2337
+ "module" : "PKTC-IETF-MTA-MIB"
2338
+ },
2339
+ },
2340
+ "description" :
2341
+ """ This INFORM notification may be issued by the MTA to
2342
+ confirm the completion of the PacketCable provisioning
2343
+ process, and to report its provisioning completion
2344
+ status.
2345
+ It contains the MTA MAC address (obtained in the MTA
2346
+ ifTable in the ifPhysAddress object that corresponds
2347
+ to the ifIndex 1), a correlation ID and the MTA
2348
+ provisioning state as defined in
2349
+ pktcMtaDevProvisioningState.""",
2350
+ }, # notification
2351
+ }, # notifications
2352
+
2353
+ "groups" : {
2354
+ "pktcMtaGroup" : {
2355
+ "nodetype" : "group",
2356
+ "moduleName" : "PKTC-IETF-MTA-MIB",
2357
+ "oid" : "1.3.6.1.2.1.140.2.2.1",
2358
+ "status" : "current",
2359
+ "members" : {
2360
+ "pktcMtaDevResetNow" : {
2361
+ "nodetype" : "member",
2362
+ "module" : "PKTC-IETF-MTA-MIB"
2363
+ },
2364
+ "pktcMtaDevSerialNumber" : {
2365
+ "nodetype" : "member",
2366
+ "module" : "PKTC-IETF-MTA-MIB"
2367
+ },
2368
+ "pktcMtaDevSwCurrentVers" : {
2369
+ "nodetype" : "member",
2370
+ "module" : "PKTC-IETF-MTA-MIB"
2371
+ },
2372
+ "pktcMtaDevFQDN" : {
2373
+ "nodetype" : "member",
2374
+ "module" : "PKTC-IETF-MTA-MIB"
2375
+ },
2376
+ "pktcMtaDevEndPntCount" : {
2377
+ "nodetype" : "member",
2378
+ "module" : "PKTC-IETF-MTA-MIB"
2379
+ },
2380
+ "pktcMtaDevEnabled" : {
2381
+ "nodetype" : "member",
2382
+ "module" : "PKTC-IETF-MTA-MIB"
2383
+ },
2384
+ "pktcMtaDevProvisioningCounter" : {
2385
+ "nodetype" : "member",
2386
+ "module" : "PKTC-IETF-MTA-MIB"
2387
+ },
2388
+ "pktcMtaDevErrorOid" : {
2389
+ "nodetype" : "member",
2390
+ "module" : "PKTC-IETF-MTA-MIB"
2391
+ },
2392
+ "pktcMtaDevErrorValue" : {
2393
+ "nodetype" : "member",
2394
+ "module" : "PKTC-IETF-MTA-MIB"
2395
+ },
2396
+ "pktcMtaDevErrorReason" : {
2397
+ "nodetype" : "member",
2398
+ "module" : "PKTC-IETF-MTA-MIB"
2399
+ },
2400
+ "pktcMtaDevTypeIdentifier" : {
2401
+ "nodetype" : "member",
2402
+ "module" : "PKTC-IETF-MTA-MIB"
2403
+ },
2404
+ "pktcMtaDevProvisioningState" : {
2405
+ "nodetype" : "member",
2406
+ "module" : "PKTC-IETF-MTA-MIB"
2407
+ },
2408
+ "pktcMtaDevHttpAccess" : {
2409
+ "nodetype" : "member",
2410
+ "module" : "PKTC-IETF-MTA-MIB"
2411
+ },
2412
+ "pktcMtaDevCertificate" : {
2413
+ "nodetype" : "member",
2414
+ "module" : "PKTC-IETF-MTA-MIB"
2415
+ },
2416
+ "pktcMtaDevCorrelationId" : {
2417
+ "nodetype" : "member",
2418
+ "module" : "PKTC-IETF-MTA-MIB"
2419
+ },
2420
+ "pktcMtaDevManufacturerCertificate" : {
2421
+ "nodetype" : "member",
2422
+ "module" : "PKTC-IETF-MTA-MIB"
2423
+ },
2424
+ "pktcMtaDevDhcpServerAddressType" : {
2425
+ "nodetype" : "member",
2426
+ "module" : "PKTC-IETF-MTA-MIB"
2427
+ },
2428
+ "pktcMtaDevDnsServerAddressType" : {
2429
+ "nodetype" : "member",
2430
+ "module" : "PKTC-IETF-MTA-MIB"
2431
+ },
2432
+ "pktcMtaDevTimeServerAddressType" : {
2433
+ "nodetype" : "member",
2434
+ "module" : "PKTC-IETF-MTA-MIB"
2435
+ },
2436
+ "pktcMtaDevProvConfigEncryptAlg" : {
2437
+ "nodetype" : "member",
2438
+ "module" : "PKTC-IETF-MTA-MIB"
2439
+ },
2440
+ "pktcMtaDevServerDhcp1" : {
2441
+ "nodetype" : "member",
2442
+ "module" : "PKTC-IETF-MTA-MIB"
2443
+ },
2444
+ "pktcMtaDevServerDhcp2" : {
2445
+ "nodetype" : "member",
2446
+ "module" : "PKTC-IETF-MTA-MIB"
2447
+ },
2448
+ "pktcMtaDevServerDns1" : {
2449
+ "nodetype" : "member",
2450
+ "module" : "PKTC-IETF-MTA-MIB"
2451
+ },
2452
+ "pktcMtaDevServerDns2" : {
2453
+ "nodetype" : "member",
2454
+ "module" : "PKTC-IETF-MTA-MIB"
2455
+ },
2456
+ "pktcMtaDevTimeServer" : {
2457
+ "nodetype" : "member",
2458
+ "module" : "PKTC-IETF-MTA-MIB"
2459
+ },
2460
+ "pktcMtaDevConfigFile" : {
2461
+ "nodetype" : "member",
2462
+ "module" : "PKTC-IETF-MTA-MIB"
2463
+ },
2464
+ "pktcMtaDevSnmpEntity" : {
2465
+ "nodetype" : "member",
2466
+ "module" : "PKTC-IETF-MTA-MIB"
2467
+ },
2468
+ "pktcMtaDevRealmPkinitGracePeriod" : {
2469
+ "nodetype" : "member",
2470
+ "module" : "PKTC-IETF-MTA-MIB"
2471
+ },
2472
+ "pktcMtaDevRealmTgsGracePeriod" : {
2473
+ "nodetype" : "member",
2474
+ "module" : "PKTC-IETF-MTA-MIB"
2475
+ },
2476
+ "pktcMtaDevRealmAvailSlot" : {
2477
+ "nodetype" : "member",
2478
+ "module" : "PKTC-IETF-MTA-MIB"
2479
+ },
2480
+ "pktcMtaDevRealmName" : {
2481
+ "nodetype" : "member",
2482
+ "module" : "PKTC-IETF-MTA-MIB"
2483
+ },
2484
+ "pktcMtaDevRealmOrgName" : {
2485
+ "nodetype" : "member",
2486
+ "module" : "PKTC-IETF-MTA-MIB"
2487
+ },
2488
+ "pktcMtaDevRealmUnsolicitedKeyMaxTimeout" : {
2489
+ "nodetype" : "member",
2490
+ "module" : "PKTC-IETF-MTA-MIB"
2491
+ },
2492
+ "pktcMtaDevRealmUnsolicitedKeyNomTimeout" : {
2493
+ "nodetype" : "member",
2494
+ "module" : "PKTC-IETF-MTA-MIB"
2495
+ },
2496
+ "pktcMtaDevRealmUnsolicitedKeyMaxRetries" : {
2497
+ "nodetype" : "member",
2498
+ "module" : "PKTC-IETF-MTA-MIB"
2499
+ },
2500
+ "pktcMtaDevRealmStatus" : {
2501
+ "nodetype" : "member",
2502
+ "module" : "PKTC-IETF-MTA-MIB"
2503
+ },
2504
+ "pktcMtaDevCmsAvailSlot" : {
2505
+ "nodetype" : "member",
2506
+ "module" : "PKTC-IETF-MTA-MIB"
2507
+ },
2508
+ "pktcMtaDevCmsFqdn" : {
2509
+ "nodetype" : "member",
2510
+ "module" : "PKTC-IETF-MTA-MIB"
2511
+ },
2512
+ "pktcMtaDevCmsKerbRealmName" : {
2513
+ "nodetype" : "member",
2514
+ "module" : "PKTC-IETF-MTA-MIB"
2515
+ },
2516
+ "pktcMtaDevCmsUnsolicitedKeyMaxTimeout" : {
2517
+ "nodetype" : "member",
2518
+ "module" : "PKTC-IETF-MTA-MIB"
2519
+ },
2520
+ "pktcMtaDevCmsUnsolicitedKeyNomTimeout" : {
2521
+ "nodetype" : "member",
2522
+ "module" : "PKTC-IETF-MTA-MIB"
2523
+ },
2524
+ "pktcMtaDevCmsUnsolicitedKeyMaxRetries" : {
2525
+ "nodetype" : "member",
2526
+ "module" : "PKTC-IETF-MTA-MIB"
2527
+ },
2528
+ "pktcMtaDevCmsSolicitedKeyTimeout" : {
2529
+ "nodetype" : "member",
2530
+ "module" : "PKTC-IETF-MTA-MIB"
2531
+ },
2532
+ "pktcMtaDevCmsMaxClockSkew" : {
2533
+ "nodetype" : "member",
2534
+ "module" : "PKTC-IETF-MTA-MIB"
2535
+ },
2536
+ "pktcMtaDevCmsIpsecCtrl" : {
2537
+ "nodetype" : "member",
2538
+ "module" : "PKTC-IETF-MTA-MIB"
2539
+ },
2540
+ "pktcMtaDevCmsStatus" : {
2541
+ "nodetype" : "member",
2542
+ "module" : "PKTC-IETF-MTA-MIB"
2543
+ },
2544
+ "pktcMtaDevResetKrbTickets" : {
2545
+ "nodetype" : "member",
2546
+ "module" : "PKTC-IETF-MTA-MIB"
2547
+ },
2548
+ "pktcMtaDevProvUnsolicitedKeyMaxTimeout" : {
2549
+ "nodetype" : "member",
2550
+ "module" : "PKTC-IETF-MTA-MIB"
2551
+ },
2552
+ "pktcMtaDevProvUnsolicitedKeyNomTimeout" : {
2553
+ "nodetype" : "member",
2554
+ "module" : "PKTC-IETF-MTA-MIB"
2555
+ },
2556
+ "pktcMtaDevProvUnsolicitedKeyMaxRetries" : {
2557
+ "nodetype" : "member",
2558
+ "module" : "PKTC-IETF-MTA-MIB"
2559
+ },
2560
+ "pktcMtaDevProvKerbRealmName" : {
2561
+ "nodetype" : "member",
2562
+ "module" : "PKTC-IETF-MTA-MIB"
2563
+ },
2564
+ "pktcMtaDevProvSolicitedKeyTimeout" : {
2565
+ "nodetype" : "member",
2566
+ "module" : "PKTC-IETF-MTA-MIB"
2567
+ },
2568
+ "pktcMtaDevProvConfigHash" : {
2569
+ "nodetype" : "member",
2570
+ "module" : "PKTC-IETF-MTA-MIB"
2571
+ },
2572
+ "pktcMtaDevProvConfigKey" : {
2573
+ "nodetype" : "member",
2574
+ "module" : "PKTC-IETF-MTA-MIB"
2575
+ },
2576
+ "pktcMtaDevProvState" : {
2577
+ "nodetype" : "member",
2578
+ "module" : "PKTC-IETF-MTA-MIB"
2579
+ },
2580
+ "pktcMtaDevProvisioningTimer" : {
2581
+ "nodetype" : "member",
2582
+ "module" : "PKTC-IETF-MTA-MIB"
2583
+ },
2584
+ "pktcMtaDevTelephonyRootCertificate" : {
2585
+ "nodetype" : "member",
2586
+ "module" : "PKTC-IETF-MTA-MIB"
2587
+ },
2588
+ }, # members
2589
+ "description" :
2590
+ """ A collection of objects for managing PacketCable or
2591
+ IPCablecom MTA implementations.""",
2592
+ }, # group
2593
+ "pktcMtaNotificationGroup" : {
2594
+ "nodetype" : "group",
2595
+ "moduleName" : "PKTC-IETF-MTA-MIB",
2596
+ "oid" : "1.3.6.1.2.1.140.2.2.2",
2597
+ "status" : "current",
2598
+ "members" : {
2599
+ "pktcMtaDevProvisioningStatus" : {
2600
+ "nodetype" : "member",
2601
+ "module" : "PKTC-IETF-MTA-MIB"
2602
+ },
2603
+ "pktcMtaDevProvisioningEnrollment" : {
2604
+ "nodetype" : "member",
2605
+ "module" : "PKTC-IETF-MTA-MIB"
2606
+ },
2607
+ }, # members
2608
+ "description" :
2609
+ """ A collection of notifications dealing with the change of
2610
+ MTA provisioning status.""",
2611
+ }, # group
2612
+ }, # groups
2613
+
2614
+ "compliances" : {
2615
+ "pktcMtaBasicCompliance" : {
2616
+ "nodetype" : "compliance",
2617
+ "moduleName" : "PKTC-IETF-MTA-MIB",
2618
+ "oid" : "1.3.6.1.2.1.140.2.1.1",
2619
+ "status" : "current",
2620
+ "description" :
2621
+ """ The compliance statement for MTA devices that implement
2622
+ PacketCable or IPCablecom requirements.
2623
+
2624
+ This compliance statement applies to MTA implementations
2625
+ that support PacketCable 1.0 or IPCablecom requirements,
2626
+ which are not IPv6-capable at the time of this
2627
+
2628
+
2629
+
2630
+ RFC publication.""",
2631
+ "requires" : {
2632
+ "pktcMtaGroup" : {
2633
+ "nodetype" : "mandatory",
2634
+ "module" : "PKTC-IETF-MTA-MIB"
2635
+ },
2636
+ "pktcMtaNotificationGroup" : {
2637
+ "nodetype" : "mandatory",
2638
+ "module" : "PKTC-IETF-MTA-MIB"
2639
+ },
2640
+ }, # requires
2641
+ "refinements" : {
2642
+ "pktcMtaDevDhcpServerAddressType" : {
2643
+ "module" : "PKTC-IETF-MTA-MIB",
2644
+ "syntax" : {
2645
+ "type" : {
2646
+ "basetype" : "Enumeration",
2647
+ "parent module" : {
2648
+ "name" : "INET-ADDRESS-MIB",
2649
+ "type" : "InetAddressType",
2650
+ },
2651
+ "ipv4" : {
2652
+ "nodetype" : "namednumber",
2653
+ "number" : "1"
2654
+ },
2655
+ },
2656
+ }, # syntax
2657
+ "description" :
2658
+ """ Support for address types other than 'ipv4(1)'
2659
+ is not presently specified and therefore is not
2660
+ required. It may be defined in future versions of
2661
+ this MIB module.""",
2662
+ },
2663
+ "pktcMtaDevDnsServerAddressType" : {
2664
+ "module" : "PKTC-IETF-MTA-MIB",
2665
+ "syntax" : {
2666
+ "type" : {
2667
+ "basetype" : "Enumeration",
2668
+ "parent module" : {
2669
+ "name" : "INET-ADDRESS-MIB",
2670
+ "type" : "InetAddressType",
2671
+ },
2672
+ "ipv4" : {
2673
+ "nodetype" : "namednumber",
2674
+ "number" : "1"
2675
+ },
2676
+ },
2677
+ }, # syntax
2678
+ "description" :
2679
+ """ Support for address types other than 'ipv4(1)'
2680
+ is not presently specified and therefore is not
2681
+ required. It may be defined in future versions of
2682
+ this MIB module.""",
2683
+ },
2684
+ "pktcMtaDevTimeServerAddressType" : {
2685
+ "module" : "PKTC-IETF-MTA-MIB",
2686
+ "syntax" : {
2687
+ "type" : {
2688
+ "basetype" : "Enumeration",
2689
+ "parent module" : {
2690
+ "name" : "INET-ADDRESS-MIB",
2691
+ "type" : "InetAddressType",
2692
+ },
2693
+ "ipv4" : {
2694
+ "nodetype" : "namednumber",
2695
+ "number" : "1"
2696
+ },
2697
+ },
2698
+ }, # syntax
2699
+ "description" :
2700
+ """ Support for address types other than 'ipv4(1)'
2701
+ is not presently specified and therefore is not
2702
+ required. It may be defined in future versions of
2703
+ this MIB module.""",
2704
+ },
2705
+ "pktcMtaDevServerDhcp1" : {
2706
+ "module" : "PKTC-IETF-MTA-MIB",
2707
+ "syntax" : {
2708
+ "type" : {
2709
+ "basetype" : "OctetString",
2710
+ "parent module" : {
2711
+ "name" : "INET-ADDRESS-MIB",
2712
+ "type" : "InetAddress",
2713
+ },
2714
+ "ranges" : [
2715
+ {
2716
+ "min" : "4",
2717
+ "max" : "4"
2718
+ },
2719
+ ],
2720
+ "range" : {
2721
+ "min" : "4",
2722
+ "max" : "4"
2723
+ },
2724
+ },
2725
+ }, # syntax
2726
+ "description" :
2727
+ """An implementation is only required to support IPv4
2728
+ addresses. Other address types support may be defined in
2729
+ future versions of this MIB module.""",
2730
+ },
2731
+ "pktcMtaDevServerDhcp2" : {
2732
+ "module" : "PKTC-IETF-MTA-MIB",
2733
+ "syntax" : {
2734
+ "type" : {
2735
+ "basetype" : "OctetString",
2736
+ "parent module" : {
2737
+ "name" : "INET-ADDRESS-MIB",
2738
+ "type" : "InetAddress",
2739
+ },
2740
+ "ranges" : [
2741
+ {
2742
+ "min" : "4",
2743
+ "max" : "4"
2744
+ },
2745
+ ],
2746
+ "range" : {
2747
+ "min" : "4",
2748
+ "max" : "4"
2749
+ },
2750
+ },
2751
+ }, # syntax
2752
+ "description" :
2753
+ """An implementation is only required to support IPv4
2754
+ addresses. Other address types support may be defined in
2755
+ future versions of this MIB module.""",
2756
+ },
2757
+ "pktcMtaDevServerDns1" : {
2758
+ "module" : "PKTC-IETF-MTA-MIB",
2759
+ "syntax" : {
2760
+ "type" : {
2761
+ "basetype" : "OctetString",
2762
+ "parent module" : {
2763
+ "name" : "INET-ADDRESS-MIB",
2764
+ "type" : "InetAddress",
2765
+ },
2766
+ "ranges" : [
2767
+ {
2768
+ "min" : "4",
2769
+ "max" : "4"
2770
+ },
2771
+ ],
2772
+ "range" : {
2773
+ "min" : "4",
2774
+ "max" : "4"
2775
+ },
2776
+ },
2777
+ }, # syntax
2778
+ "description" :
2779
+ """An implementation is only required to support IPv4
2780
+ addresses. Other address types support may be defined in
2781
+ future versions of this MIB module.""",
2782
+ },
2783
+ "pktcMtaDevServerDns2" : {
2784
+ "module" : "PKTC-IETF-MTA-MIB",
2785
+ "syntax" : {
2786
+ "type" : {
2787
+ "basetype" : "OctetString",
2788
+ "parent module" : {
2789
+ "name" : "INET-ADDRESS-MIB",
2790
+ "type" : "InetAddress",
2791
+ },
2792
+ "ranges" : [
2793
+ {
2794
+ "min" : "4",
2795
+ "max" : "4"
2796
+ },
2797
+ ],
2798
+ "range" : {
2799
+ "min" : "4",
2800
+ "max" : "4"
2801
+ },
2802
+ },
2803
+ }, # syntax
2804
+ "description" :
2805
+ """An implementation is only required to support IPv4
2806
+ addresses. Other address types support may be defined in
2807
+ future versions of this MIB module.""",
2808
+ },
2809
+ "pktcMtaDevTimeServer" : {
2810
+ "module" : "PKTC-IETF-MTA-MIB",
2811
+ "syntax" : {
2812
+ "type" : {
2813
+ "basetype" : "OctetString",
2814
+ "parent module" : {
2815
+ "name" : "INET-ADDRESS-MIB",
2816
+ "type" : "InetAddress",
2817
+ },
2818
+ "ranges" : [
2819
+ {
2820
+ "min" : "4",
2821
+ "max" : "4"
2822
+ },
2823
+ ],
2824
+ "range" : {
2825
+ "min" : "4",
2826
+ "max" : "4"
2827
+ },
2828
+ },
2829
+ }, # syntax
2830
+ "description" :
2831
+ """An implementation is only required to support IPv4
2832
+ addresses. Other address types support may be defined in
2833
+ future versions of this MIB module.""",
2834
+ },
2835
+ "pktcMtaDevProvConfigEncryptAlg" : {
2836
+ "module" : "PKTC-IETF-MTA-MIB",
2837
+ "syntax" : {
2838
+ "type" : {
2839
+ "basetype" : "Enumeration",
2840
+ "parent module" : {
2841
+ "name" : "PKTC-IETF-MTA-MIB",
2842
+ "type" : "PktcMtaDevProvEncryptAlg",
2843
+ },
2844
+ },
2845
+ }, # syntax
2846
+ "description" :
2847
+ """An implementation is only required to support
2848
+ values of none(0) and des64Cbcmode(1).
2849
+ An IV of zero is used to encrypt in des64Cbcmode, and
2850
+ the length of pktcMtaDevProvConfigKey is 64 bits, as
2851
+ defined in the PacketCable Security specification.
2852
+ Other encryption types may be defined in future
2853
+ versions of this MIB module.""",
2854
+ },
2855
+ "pktcMtaDevRealmOrgName" : {
2856
+ "module" : "PKTC-IETF-MTA-MIB",
2857
+ "syntax" : {
2858
+ "type" : {
2859
+ "basetype" : "OctetString",
2860
+ "parent module" : {
2861
+ "name" : "SYSAPPL-MIB",
2862
+ "type" : "LongUtf8String",
2863
+ },
2864
+ "ranges" : [
2865
+ {
2866
+ "min" : "1",
2867
+ "max" : "384"
2868
+ },
2869
+ ],
2870
+ "range" : {
2871
+ "min" : "1",
2872
+ "max" : "384"
2873
+ },
2874
+ },
2875
+ }, # syntax
2876
+ "description" :
2877
+ """The Organization Name field in X.509 certificates
2878
+ can contain up to 64 UTF-8 encoded characters,
2879
+ as defined in RFCs 3280 and 4630. Therefore, compliant
2880
+ devices are only required to support Organization
2881
+ Name values of up to 64 UTF-8 encoded characters.
2882
+ Given that RFCs 3280 and 4630 define the UTF-8 encoding,
2883
+ compliant devices must support a maximum size of 384
2884
+ octets for pktcMtaDevRealmOrgName. The calculation of
2885
+ 384 octets comes from the RFC 3629 UTF-8 encoding
2886
+ definition whereby the UTF-8 encoded characters
2887
+ are encoded as sequences of 1 to 6 octets,
2888
+ assuming that code points as high as 0x7ffffffff
2889
+ might be used. Subsequent versions of Unicode and ISO
2890
+ 10646 have limited the upper bound to 0x10ffff.
2891
+
2892
+
2893
+
2894
+ Consequently, the current version of UTF-8, defined in
2895
+ RFC 3629, does not require more than four octets to
2896
+ encode a valid code point.""",
2897
+ },
2898
+ }, # refinements
2899
+
2900
+ }, # compliance
2901
+ "pktcMtaBasicSmtaCompliance" : {
2902
+ "nodetype" : "compliance",
2903
+ "moduleName" : "PKTC-IETF-MTA-MIB",
2904
+ "oid" : "1.3.6.1.2.1.140.2.1.2",
2905
+ "status" : "current",
2906
+ "description" :
2907
+ """ The compliance statement for S-MTA devices
2908
+ that implement PacketCable or IPCablecom requirements.
2909
+
2910
+ This compliance statement applies to S-MTA implementations
2911
+ that support PacketCable or IPCablecom requirements,
2912
+ which are not IPv6-capable at the time of this
2913
+ RFC publication.""",
2914
+ "requires" : {
2915
+ "pktcMtaGroup" : {
2916
+ "nodetype" : "mandatory",
2917
+ "module" : "PKTC-IETF-MTA-MIB"
2918
+ },
2919
+ "pktcMtaNotificationGroup" : {
2920
+ "nodetype" : "mandatory",
2921
+ "module" : "PKTC-IETF-MTA-MIB"
2922
+ },
2923
+ "docsDevSoftwareGroupV2" : {
2924
+ "nodetype" : "mandatory",
2925
+ "module" : "DOCS-CABLE-DEVICE-MIB"
2926
+ },
2927
+ "docsBpi2CodeDownloadGroup" : {
2928
+ "nodetype" : "mandatory",
2929
+ "module" : "DOCS-IETF-BPI2-MIB"
2930
+ },
2931
+ }, # requires
2932
+ "refinements" : {
2933
+ "pktcMtaDevDhcpServerAddressType" : {
2934
+ "module" : "PKTC-IETF-MTA-MIB",
2935
+ "syntax" : {
2936
+ "type" : {
2937
+ "basetype" : "Enumeration",
2938
+ "parent module" : {
2939
+ "name" : "INET-ADDRESS-MIB",
2940
+ "type" : "InetAddressType",
2941
+ },
2942
+ "ipv4" : {
2943
+ "nodetype" : "namednumber",
2944
+ "number" : "1"
2945
+ },
2946
+ },
2947
+ }, # syntax
2948
+ "description" :
2949
+ """ Support for address types other than 'ipv4(1)'
2950
+ is not presently specified and therefore is not
2951
+ required. It may be defined in future versions of
2952
+ this MIB module.""",
2953
+ },
2954
+ "pktcMtaDevDnsServerAddressType" : {
2955
+ "module" : "PKTC-IETF-MTA-MIB",
2956
+ "syntax" : {
2957
+ "type" : {
2958
+ "basetype" : "Enumeration",
2959
+ "parent module" : {
2960
+ "name" : "INET-ADDRESS-MIB",
2961
+ "type" : "InetAddressType",
2962
+ },
2963
+ "ipv4" : {
2964
+ "nodetype" : "namednumber",
2965
+ "number" : "1"
2966
+ },
2967
+ },
2968
+ }, # syntax
2969
+ "description" :
2970
+ """ Support for address types other than 'ipv4(1)'
2971
+ is not presently specified and therefore is not
2972
+ required. It may be defined in future versions of
2973
+ this MIB module.""",
2974
+ },
2975
+ "pktcMtaDevTimeServerAddressType" : {
2976
+ "module" : "PKTC-IETF-MTA-MIB",
2977
+ "syntax" : {
2978
+ "type" : {
2979
+ "basetype" : "Enumeration",
2980
+ "parent module" : {
2981
+ "name" : "INET-ADDRESS-MIB",
2982
+ "type" : "InetAddressType",
2983
+ },
2984
+ "ipv4" : {
2985
+ "nodetype" : "namednumber",
2986
+ "number" : "1"
2987
+ },
2988
+ },
2989
+ }, # syntax
2990
+ "description" :
2991
+ """ Support for address types other than 'ipv4(1)'
2992
+ is not presently specified and therefore is not
2993
+ required. It may be defined in future versions of
2994
+ this MIB module.""",
2995
+ },
2996
+ "pktcMtaDevServerDhcp1" : {
2997
+ "module" : "PKTC-IETF-MTA-MIB",
2998
+ "syntax" : {
2999
+ "type" : {
3000
+ "basetype" : "OctetString",
3001
+ "parent module" : {
3002
+ "name" : "INET-ADDRESS-MIB",
3003
+ "type" : "InetAddress",
3004
+ },
3005
+ "ranges" : [
3006
+ {
3007
+ "min" : "4",
3008
+ "max" : "4"
3009
+ },
3010
+ ],
3011
+ "range" : {
3012
+ "min" : "4",
3013
+ "max" : "4"
3014
+ },
3015
+ },
3016
+ }, # syntax
3017
+ "description" :
3018
+ """An implementation is only required to support IPv4
3019
+ addresses. Other address types support may be defined in
3020
+ future versions of this MIB module.""",
3021
+ },
3022
+ "pktcMtaDevServerDhcp2" : {
3023
+ "module" : "PKTC-IETF-MTA-MIB",
3024
+ "syntax" : {
3025
+ "type" : {
3026
+ "basetype" : "OctetString",
3027
+ "parent module" : {
3028
+ "name" : "INET-ADDRESS-MIB",
3029
+ "type" : "InetAddress",
3030
+ },
3031
+ "ranges" : [
3032
+ {
3033
+ "min" : "4",
3034
+ "max" : "4"
3035
+ },
3036
+ ],
3037
+ "range" : {
3038
+ "min" : "4",
3039
+ "max" : "4"
3040
+ },
3041
+ },
3042
+ }, # syntax
3043
+ "description" :
3044
+ """An implementation is only required to support IPv4
3045
+ addresses. Other address types support may be defined in
3046
+ future versions of this MIB module.""",
3047
+ },
3048
+ "pktcMtaDevServerDns1" : {
3049
+ "module" : "PKTC-IETF-MTA-MIB",
3050
+ "syntax" : {
3051
+ "type" : {
3052
+ "basetype" : "OctetString",
3053
+ "parent module" : {
3054
+ "name" : "INET-ADDRESS-MIB",
3055
+ "type" : "InetAddress",
3056
+ },
3057
+ "ranges" : [
3058
+ {
3059
+ "min" : "4",
3060
+ "max" : "4"
3061
+ },
3062
+ ],
3063
+ "range" : {
3064
+ "min" : "4",
3065
+ "max" : "4"
3066
+ },
3067
+ },
3068
+ }, # syntax
3069
+ "description" :
3070
+ """An implementation is only required to support IPv4
3071
+ addresses. Other address types support may be defined in
3072
+ future versions of this MIB module.""",
3073
+ },
3074
+ "pktcMtaDevServerDns2" : {
3075
+ "module" : "PKTC-IETF-MTA-MIB",
3076
+ "syntax" : {
3077
+ "type" : {
3078
+ "basetype" : "OctetString",
3079
+ "parent module" : {
3080
+ "name" : "INET-ADDRESS-MIB",
3081
+ "type" : "InetAddress",
3082
+ },
3083
+ "ranges" : [
3084
+ {
3085
+ "min" : "4",
3086
+ "max" : "4"
3087
+ },
3088
+ ],
3089
+ "range" : {
3090
+ "min" : "4",
3091
+ "max" : "4"
3092
+ },
3093
+ },
3094
+ }, # syntax
3095
+ "description" :
3096
+ """An implementation is only required to support IPv4
3097
+ addresses. Other address types support may be defined in
3098
+ future versions of this MIB module.""",
3099
+ },
3100
+ "pktcMtaDevTimeServer" : {
3101
+ "module" : "PKTC-IETF-MTA-MIB",
3102
+ "syntax" : {
3103
+ "type" : {
3104
+ "basetype" : "OctetString",
3105
+ "parent module" : {
3106
+ "name" : "INET-ADDRESS-MIB",
3107
+ "type" : "InetAddress",
3108
+ },
3109
+ "ranges" : [
3110
+ {
3111
+ "min" : "4",
3112
+ "max" : "4"
3113
+ },
3114
+ ],
3115
+ "range" : {
3116
+ "min" : "4",
3117
+ "max" : "4"
3118
+ },
3119
+ },
3120
+ }, # syntax
3121
+ "description" :
3122
+ """An implementation is only required to support IPv4
3123
+ addresses. Other address types support may be defined in
3124
+ future versions of this MIB module.""",
3125
+ },
3126
+ "pktcMtaDevProvConfigEncryptAlg" : {
3127
+ "module" : "PKTC-IETF-MTA-MIB",
3128
+ "syntax" : {
3129
+ "type" : {
3130
+ "basetype" : "Enumeration",
3131
+ "parent module" : {
3132
+ "name" : "PKTC-IETF-MTA-MIB",
3133
+ "type" : "PktcMtaDevProvEncryptAlg",
3134
+ },
3135
+ },
3136
+ }, # syntax
3137
+ "description" :
3138
+ """An implementation is only required to support
3139
+ values of none(0) and des64Cbcmode(1).
3140
+ An IV of zero is used to encrypt in des64Cbcmode, and
3141
+ the length of pktcMtaDevProvConfigKey is 64 bits, as
3142
+ defined in the PacketCable Security specification.
3143
+ Other encryption types may be defined in future
3144
+ versions of this MIB module.""",
3145
+ },
3146
+ "pktcMtaDevRealmOrgName" : {
3147
+ "module" : "PKTC-IETF-MTA-MIB",
3148
+ "syntax" : {
3149
+ "type" : {
3150
+ "basetype" : "OctetString",
3151
+ "parent module" : {
3152
+ "name" : "SYSAPPL-MIB",
3153
+ "type" : "LongUtf8String",
3154
+ },
3155
+ "ranges" : [
3156
+ {
3157
+ "min" : "1",
3158
+ "max" : "384"
3159
+ },
3160
+ ],
3161
+ "range" : {
3162
+ "min" : "1",
3163
+ "max" : "384"
3164
+ },
3165
+ },
3166
+ }, # syntax
3167
+ "description" :
3168
+ """The Organization Name field in X.509 certificates
3169
+ can contain up to 64 UTF-8 encoded characters, as
3170
+ defined in RFCs 3280 and 4630. Therefore, compliant
3171
+ devices are only required to support Organization
3172
+ Name values of up to 64 UTF-8 encoded characters.
3173
+ Given that RFCs 3280 and 4630 define the UTF-8 encoding,
3174
+ compliant devices must support a maximum size of 384
3175
+ octets for pktcMtaDevRealmOrgName. The calculation of
3176
+ 384 octets comes from the RFC 3629 UTF-8 encoding
3177
+ definition whereby the UTF-8 encoded characters
3178
+ are encoded as sequences of 1 to 6 octets,
3179
+ assuming that code points as high as 0x7ffffffff
3180
+ might be used. Subsequent versions of Unicode and ISO
3181
+ 10646 have limited the upper bound to 0x10ffff.
3182
+ Consequently, the current version of UTF-8, defined in
3183
+ RFC 3629 does not require more than four octets to
3184
+ encode a valid code point.""",
3185
+ },
3186
+ }, # refinements
3187
+
3188
+ }, # compliance
3189
+ }, # compliances
3190
+
3191
+ }