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,4335 @@
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 EFM-CU-MIB
6
+
7
+ FILENAME = "./libsmi-0.5.0/mibs/ietf/EFM-CU-MIB"
8
+
9
+ MIB = {
10
+ "moduleName" : "EFM-CU-MIB",
11
+
12
+ "EFM-CU-MIB" : {
13
+ "nodetype" : "module",
14
+ "language" : "SMIv2",
15
+ "organization" :
16
+ """IETF Ethernet Interfaces and Hub MIB Working Group""",
17
+ "contact" :
18
+ """WG charter:
19
+ http://www.ietf.org/html.charters/OLD/hubmib-charter.html
20
+
21
+
22
+
23
+ Mailing Lists:
24
+ General Discussion: hubmib@ietf.org
25
+ To Subscribe: hubmib-request@ietf.org
26
+ In Body: subscribe your_email_address
27
+
28
+ Chair: Bert Wijnen
29
+ Postal: Alcatel-Lucent
30
+ Schagen 33
31
+ 3461 GL Linschoten
32
+ Netherlands
33
+ Phone: +31-348-407-775
34
+ EMail: bwijnen@alcatel-lucent.com
35
+
36
+ Editor: Edward Beili
37
+ Postal: Actelis Networks Inc.
38
+ 25 Bazel St., P.O.B. 10173
39
+ Petach-Tikva 10173
40
+ Israel
41
+ Phone: +972-3-924-3491
42
+ Email: edward.beili@actelis.com""",
43
+ "description" :
44
+ """The objects in this MIB module are used to manage
45
+ the Ethernet in the First Mile (EFM) Copper (EFMCu) Interfaces
46
+ 2BASE-TL and 10PASS-TS, defined in IEEE Std. 802.3ah-2004,
47
+ which is now a part of IEEE Std. 802.3-2005.
48
+
49
+ The following references are used throughout this MIB module:
50
+
51
+ [802.3ah] refers to:
52
+ IEEE Std 802.3ah-2004: 'IEEE Standard for Information
53
+ technology - Telecommunications and information exchange
54
+ between systems - Local and metropolitan area networks -
55
+ Specific requirements -
56
+ Part 3: Carrier Sense Multiple Access with Collision
57
+ Detection (CSMA/CD) Access Method and Physical Layer
58
+ Specifications -
59
+ Amendment: Media Access Control Parameters, Physical
60
+ Layers and Management Parameters for Subscriber Access
61
+ Networks', 07 September 2004.
62
+
63
+ Of particular interest are Clause 61, 'Physical Coding
64
+ Sublayer (PCS) and common specifications, type 10PASS-TS and
65
+ type 2BASE-TL', Clause 30, 'Management', Clause 45,
66
+ 'Management Data Input/Output (MDIO) Interface', Annex 62A,
67
+ 'PMD profiles for 10PASS-TS' and Annex 63A, 'PMD profiles for
68
+ 2BASE-TL'.
69
+
70
+
71
+
72
+
73
+ [G.991.2] refers to:
74
+ ITU-T Recommendation G.991.2: 'Single-pair High-speed Digital
75
+ Subscriber Line (SHDSL) transceivers', December 2003.
76
+
77
+ [ANFP] refers to:
78
+ NICC Document ND1602:2005/08: 'Specification of the Access
79
+ Network Frequency Plan (ANFP) applicable to transmission
80
+ systems used on the BT Access Network,' August 2005.
81
+
82
+ The following normative documents are quoted by the DESCRIPTION
83
+ clauses in this MIB module:
84
+
85
+ [G.993.1] refers to:
86
+ ITU-T Recommendation G.993.1: 'Very High speed Digital
87
+ Subscriber Line transceivers', June 2004.
88
+
89
+ [T1.424] refers to:
90
+ ANSI T1.424-2004: 'Interface Between Networks and Customer
91
+ Installation Very-high-bit-rate Digital Subscriber Lines
92
+ (VDSL) Metallic Interface (DMT Based)', June 2004.
93
+
94
+ [TS 101 270-1] refers to:
95
+ ETSI TS 101 270-1: 'Transmission and Multiplexing (TM);
96
+ Access transmission systems on metallic access cables;
97
+ Very high speed Digital Subscriber Line (VDSL); Part 1:
98
+ Functional requirements', October 2005.
99
+
100
+ Naming Conventions:
101
+ Atn - Attenuation
102
+ CO - Central Office
103
+ CPE - Customer Premises Equipment
104
+ EFM - Ethernet in the First Mile
105
+ EFMCu - EFM Copper
106
+ MDIO - Management Data Input/Output
107
+ Mgn - Margin
108
+ PAF - PME Aggregation Function
109
+ PBO - Power Back-Off
110
+ PCS - Physical Coding Sublayer
111
+ PMD - Physical Medium Dependent
112
+ PME - Physical Medium Entity
113
+ PSD - Power Spectral Density
114
+ SNR - Signal to Noise Ratio
115
+ TCPAM - Trellis Coded Pulse Amplitude Modulation
116
+
117
+ Copyright (C) The IETF Trust (2007). This version
118
+ of this MIB module is part of RFC 5066; see the RFC
119
+ itself for full legal notices.""",
120
+ "revisions" : (
121
+ {
122
+ "date" : "2007-11-14 00:00",
123
+ "description" :
124
+ """Initial version, published as RFC 5066.""",
125
+ },
126
+ ),
127
+ "identity node" : "efmCuMIB",
128
+ },
129
+
130
+ "imports" : (
131
+ {"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
132
+ {"module" : "SNMPv2-SMI", "name" : "OBJECT-TYPE"},
133
+ {"module" : "SNMPv2-SMI", "name" : "NOTIFICATION-TYPE"},
134
+ {"module" : "SNMPv2-SMI", "name" : "Integer32"},
135
+ {"module" : "SNMPv2-SMI", "name" : "Unsigned32"},
136
+ {"module" : "SNMPv2-SMI", "name" : "Counter32"},
137
+ {"module" : "SNMPv2-SMI", "name" : "mib-2"},
138
+ {"module" : "SNMPv2-TC", "name" : "TEXTUAL-CONVENTION"},
139
+ {"module" : "SNMPv2-TC", "name" : "TruthValue"},
140
+ {"module" : "SNMPv2-TC", "name" : "RowStatus"},
141
+ {"module" : "SNMPv2-TC", "name" : "PhysAddress"},
142
+ {"module" : "SNMPv2-CONF", "name" : "MODULE-COMPLIANCE"},
143
+ {"module" : "SNMPv2-CONF", "name" : "OBJECT-GROUP"},
144
+ {"module" : "SNMPv2-CONF", "name" : "NOTIFICATION-GROUP"},
145
+ {"module" : "SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
146
+ {"module" : "IF-MIB", "name" : "ifIndex"},
147
+ {"module" : "IF-MIB", "name" : "ifSpeed"},
148
+ ),
149
+
150
+ "typedefs" : {
151
+ "EfmProfileIndex" : {
152
+ "basetype" : "Unsigned32",
153
+ "status" : "current",
154
+ "ranges" : [
155
+ {
156
+ "min" : "1",
157
+ "max" : "255"
158
+ },
159
+ ],
160
+ "range" : {
161
+ "min" : "1",
162
+ "max" : "255"
163
+ },
164
+ "format" : "d",
165
+ "description" :
166
+ """A unique value, greater than zero, for each PME configuration
167
+ profile in the managed EFMCu port. It is RECOMMENDED that
168
+ values are assigned contiguously starting from 1. The value
169
+ for each profile MUST remain constant at least from one
170
+ re-initialization of the entity's network management system
171
+ to the next re-initialization.""",
172
+ },
173
+ "EfmProfileIndexOrZero" : {
174
+ "basetype" : "Unsigned32",
175
+ "status" : "current",
176
+ "ranges" : [
177
+ {
178
+ "min" : "0",
179
+ "max" : "255"
180
+ },
181
+ ],
182
+ "range" : {
183
+ "min" : "0",
184
+ "max" : "255"
185
+ },
186
+ "format" : "d",
187
+ "description" :
188
+ """This textual convention is an extension of the
189
+ EfmProfileIndex convention. The latter defines a greater than
190
+ zero value used to identify a PME profile in the managed EFMCu
191
+ port. This extension permits the additional value of zero.
192
+ The value of zero is object-specific and MUST therefore be
193
+ defined as part of the description of any object that uses
194
+ this syntax.
195
+ Examples of the usage of zero value might include situations
196
+ where the current operational profile is unknown.""",
197
+ },
198
+ "EfmProfileIndexList" : {
199
+ "basetype" : "OctetString",
200
+ "status" : "current",
201
+ "ranges" : [
202
+ {
203
+ "min" : "0",
204
+ "max" : "6"
205
+ },
206
+ ],
207
+ "range" : {
208
+ "min" : "0",
209
+ "max" : "6"
210
+ },
211
+ "format" : "1d:",
212
+ "description" :
213
+ """This textual convention represents a list of up to 6
214
+ EfmProfileIndex values, any of which can be chosen for
215
+ configuration of a PME in a managed EFMCu port.
216
+ The EfmProfileIndex textual convention defines a greater than
217
+ zero value used to identify a PME profile.
218
+ The value of this object is a concatenation of zero or
219
+ more (up to 6) octets, where each octet contains an 8-bit
220
+ EfmProfileIndex value.
221
+ A zero-length octet string is object-specific and MUST
222
+ therefore be defined as part of the description of any object
223
+ that uses this syntax. Examples of the usage of a zero-length
224
+ value might include situations where an object using this
225
+ textual convention is irrelevant for a specific EFMCu port
226
+ type.""",
227
+ },
228
+ "EfmTruthValueOrUnknown" : {
229
+ "basetype" : "Enumeration",
230
+ "status" : "current",
231
+ "unknown" : {
232
+ "nodetype" : "namednumber",
233
+ "number" : "0"
234
+ },
235
+ "true" : {
236
+ "nodetype" : "namednumber",
237
+ "number" : "1"
238
+ },
239
+ "false" : {
240
+ "nodetype" : "namednumber",
241
+ "number" : "2"
242
+ },
243
+ "description" :
244
+ """This textual convention is an extension of the TruthValue
245
+ convention. The latter defines a boolean value with possible
246
+ values of true(1) and false(2). This extension permits the
247
+ additional value of unknown(0), which can be returned as the
248
+ result of a GET operation when an exact true or false value
249
+ of the object cannot be determined.""",
250
+ },
251
+ }, # typedefs
252
+
253
+ "nodes" : {
254
+ "efmCuMIB" : {
255
+ "nodetype" : "node",
256
+ "moduleName" : "EFM-CU-MIB",
257
+ "oid" : "1.3.6.1.2.1.167",
258
+ "status" : "current",
259
+ }, # node
260
+ "efmCuObjects" : {
261
+ "nodetype" : "node",
262
+ "moduleName" : "EFM-CU-MIB",
263
+ "oid" : "1.3.6.1.2.1.167.1",
264
+ }, # node
265
+ "efmCuPort" : {
266
+ "nodetype" : "node",
267
+ "moduleName" : "EFM-CU-MIB",
268
+ "oid" : "1.3.6.1.2.1.167.1.1",
269
+ }, # node
270
+ "efmCuPortNotifications" : {
271
+ "nodetype" : "node",
272
+ "moduleName" : "EFM-CU-MIB",
273
+ "oid" : "1.3.6.1.2.1.167.1.1.0",
274
+ }, # node
275
+ "efmCuPortConfTable" : {
276
+ "nodetype" : "table",
277
+ "moduleName" : "EFM-CU-MIB",
278
+ "oid" : "1.3.6.1.2.1.167.1.1.1",
279
+ "status" : "current",
280
+ "description" :
281
+ """Table for Configuration of EFMCu 2BASE-TL/10PASS-TS (PCS)
282
+ Ports. Entries in this table MUST be maintained in a
283
+ persistent manner.""",
284
+ }, # table
285
+ "efmCuPortConfEntry" : {
286
+ "nodetype" : "row",
287
+ "moduleName" : "EFM-CU-MIB",
288
+ "oid" : "1.3.6.1.2.1.167.1.1.1.1",
289
+ "status" : "current",
290
+ "linkage" : [
291
+ "ifIndex",
292
+ ],
293
+ "description" :
294
+ """An entry in the EFMCu Port Configuration table.
295
+ Each entry represents an EFMCu port indexed by the ifIndex.
296
+ Note that an EFMCu PCS port runs on top of a single
297
+ or multiple PME port(s), which are also indexed by ifIndex.""",
298
+ }, # row
299
+ "efmCuPAFAdminState" : {
300
+ "nodetype" : "column",
301
+ "moduleName" : "EFM-CU-MIB",
302
+ "oid" : "1.3.6.1.2.1.167.1.1.1.1.1",
303
+ "status" : "current",
304
+ "syntax" : {
305
+ "type" : {
306
+ "basetype" : "Enumeration",
307
+ "enabled" : {
308
+ "nodetype" : "namednumber",
309
+ "number" : "1"
310
+ },
311
+ "disabled" : {
312
+ "nodetype" : "namednumber",
313
+ "number" : "2"
314
+ },
315
+ },
316
+ },
317
+ "access" : "readwrite",
318
+ "description" :
319
+ """Administrative (desired) state of the PAF of the EFMCu port
320
+ (PCS).
321
+ When 'disabled', PME aggregation will not be performed by the
322
+ PCS. No more than a single PME can be assigned to this PCS in
323
+ this case.
324
+ When 'enabled', PAF will be performed by the PCS when the link
325
+ is Up, even on a single attached PME, if PAF is supported.
326
+
327
+ PCS ports incapable of supporting PAF SHALL return a value of
328
+ 'disabled'. Attempts to 'enable' such ports SHALL be
329
+ rejected.
330
+
331
+ A PAF 'enabled' port with multiple PMEs assigned cannot be
332
+ 'disabled'. Attempts to 'disable' such port SHALL be
333
+ rejected, until at most one PME is left assigned.
334
+
335
+ Changing PAFAdminState is a traffic-disruptive operation and
336
+ as such SHALL be done when the link is Down. Attempts to
337
+ change this object SHALL be rejected if the link is Up or
338
+ Initializing.
339
+
340
+ This object maps to the Clause 30 attribute aPAFAdminState.
341
+
342
+ If a Clause 45 MDIO Interface to the PCS is present, then this
343
+ object maps to the PAF enable bit in the 10P/2B PCS control
344
+ register.
345
+
346
+ This object MUST be maintained in a persistent manner.""",
347
+ "reference" :
348
+ """[802.3ah] 61.2.2, 45.2.3.18.3""",
349
+ }, # column
350
+ "efmCuPAFDiscoveryCode" : {
351
+ "nodetype" : "column",
352
+ "moduleName" : "EFM-CU-MIB",
353
+ "oid" : "1.3.6.1.2.1.167.1.1.1.1.2",
354
+ "status" : "current",
355
+ "syntax" : {
356
+ "type" : {
357
+ "basetype" : "OctetString",
358
+ "parent module" : {
359
+ "name" : "SNMPv2-TC",
360
+ "type" : "PhysAddress",
361
+ },
362
+ "ranges" : [
363
+ {
364
+ "min" : "0",
365
+ "max" : "0"
366
+ },
367
+ {
368
+ "min" : "6",
369
+ "max" : "6"
370
+ },
371
+ ],
372
+ "range" : {
373
+ "min" : "0",
374
+ "max" : "6"
375
+ },
376
+ },
377
+ },
378
+ "access" : "readwrite",
379
+ "description" :
380
+ """PAF Discovery Code of the EFMCu port (PCS).
381
+ A unique 6-octet code used by the Discovery function,
382
+ when PAF is supported.
383
+ PCS ports incapable of supporting PAF SHALL return a
384
+ zero-length octet string on an attempt to read this object.
385
+ An attempt to write to this object SHALL be rejected for such
386
+ ports.
387
+ This object MUST be instantiated for the -O subtype PCS before
388
+ writing operations on the efmCuPAFRemoteDiscoveryCode
389
+ (Set_if_Clear and Clear_if_Same) are performed by PMEs
390
+ associated with the PCS.
391
+ The initial value of this object for -R subtype ports after
392
+ reset is all zeroes. For -R subtype ports, the value of this
393
+ object cannot be changed directly. This value may be changed
394
+ as a result of writing operation on the
395
+ efmCuPAFRemoteDiscoveryCode object of remote PME of -O
396
+ subtype, connected to one of the local PMEs associated with
397
+ the PCS.
398
+
399
+ Discovery MUST be performed when the link is Down.
400
+ Attempts to change this object MUST be rejected (in case of
401
+ SNMP with the error inconsistentValue), if the link is Up or
402
+ Initializing.
403
+
404
+ The PAF Discovery Code maps to the local Discovery code
405
+ variable in PAF (note that it does not have a corresponding
406
+ Clause 45 register).""",
407
+ "reference" :
408
+ """[802.3ah] 61.2.2.8.3, 61.2.2.8.4, 45.2.6.6.1, 45.2.6.8,
409
+ 61A.2""",
410
+ }, # column
411
+ "efmCuAdminProfile" : {
412
+ "nodetype" : "column",
413
+ "moduleName" : "EFM-CU-MIB",
414
+ "oid" : "1.3.6.1.2.1.167.1.1.1.1.3",
415
+ "status" : "current",
416
+ "syntax" : {
417
+ "type" : { "module" :"EFM-CU-MIB", "name" : "EfmProfileIndexList"},
418
+ },
419
+ "access" : "readwrite",
420
+ "default" : "0x01",
421
+ "description" :
422
+ """Desired configuration profile(s), common for all PMEs in the
423
+ EFMCu port. This object is a list of pointers to entries in
424
+ either efmCuPme2BProfileTable or
425
+ efmCuPme10PProfileTable, depending on the current
426
+ operating SubType of the EFMCu port as indicated by
427
+ efmCuPortSide.
428
+
429
+
430
+
431
+ The value of this object is a list of up to 6 indices of
432
+ profiles. If this list consists of a single profile index,
433
+ then all PMEs assigned to this EFMCu port SHALL be configured
434
+ according to the profile referenced by that index, unless it
435
+ is overwritten by a corresponding non-zero
436
+ efmCuPmeAdminProfile instance, which takes precedence over
437
+ efmCuAdminProfile.
438
+ A list consisting of more than one index allows each PME
439
+ in the port to be configured according to any profile
440
+ specified in the list.
441
+ By default, this object has a value of 0x01, referencing the
442
+ 1st entry in efmCuPme2BProfileTable or
443
+ efmCuPme10PProfileTable.
444
+
445
+ This object is writable and readable for the -O subtype
446
+ (2BaseTL-O or 10PassTS-O) EFMCu ports. It is irrelevant for
447
+ the -R subtype (2BaseTL-R or 10PassTS-R) ports -- a
448
+ zero-length octet string SHALL be returned on an attempt to
449
+ read this object and an attempt to change this object MUST be
450
+ rejected in this case.
451
+
452
+ Note that the current operational profile value is available
453
+ via the efmCuPmeOperProfile object.
454
+
455
+ Any modification of this object MUST be performed when the
456
+ link is Down. Attempts to change this object MUST be
457
+ rejected, if the link is Up or Initializing.
458
+ Attempts to set this object to a list with a member value that
459
+ is not the value of the index for an active entry in the
460
+ corresponding profile table MUST be rejected.
461
+
462
+ This object maps to the Clause 30 attribute aProfileSelect.
463
+
464
+ This object MUST be maintained in a persistent manner.""",
465
+ "reference" :
466
+ """[802.3ah] 30.11.2.1.6""",
467
+ }, # column
468
+ "efmCuTargetDataRate" : {
469
+ "nodetype" : "column",
470
+ "moduleName" : "EFM-CU-MIB",
471
+ "oid" : "1.3.6.1.2.1.167.1.1.1.1.4",
472
+ "status" : "current",
473
+ "syntax" : {
474
+ "type" : {
475
+ "basetype" : "Unsigned32",
476
+ "ranges" : [
477
+ {
478
+ "min" : "1",
479
+ "max" : "100000"
480
+ },
481
+ {
482
+ "min" : "999999",
483
+ "max" : "999999"
484
+ },
485
+ ],
486
+ "range" : {
487
+ "min" : "1",
488
+ "max" : "999999"
489
+ },
490
+ },
491
+ },
492
+ "access" : "readwrite",
493
+ "units" : "Kbps",
494
+ "description" :
495
+ """Desired EFMCu port 'net' (as seen across MII) Data Rate in
496
+ Kbps, to be achieved during initialization, under spectral
497
+ restrictions placed on each PME via efmCuAdminProfile or
498
+
499
+
500
+
501
+ efmCuPmeAdminProfile, with the desired SNR margin specified by
502
+ efmCuTargetSnrMgn.
503
+ In case of PAF, this object represents a sum of individual PME
504
+ data rates, modified to compensate for fragmentation and
505
+ 64/65-octet encapsulation overhead (e.g., target data rate of
506
+ 10 Mbps SHALL allow lossless transmission of a full-duplex
507
+ 10 Mbps Ethernet frame stream with minimal inter-frame gap).
508
+
509
+ The value is limited above by 100 Mbps as this is the max
510
+ burst rate across MII for EFMCu ports.
511
+
512
+ The value between 1 and 100000 indicates that the total data
513
+ rate (ifSpeed) of the EFMCu port after initialization SHALL be
514
+ equal to the target data rate or less, if the target data rate
515
+ cannot be achieved under spectral restrictions specified by
516
+ efmCuAdminProfile/efmCuPmeAdminProfile and with the desired
517
+ SNR margin. In case the copper environment allows a higher
518
+ total data rate to be achieved than that specified by the
519
+ target, the excess capability SHALL be either converted to
520
+ additional SNR margin or reclaimed by minimizing transmit
521
+ power as controlled by efmCuAdaptiveSpectra.
522
+
523
+ The value of 999999 means that the target data rate is not
524
+ fixed and SHALL be set to the maximum attainable rate during
525
+ initialization (Best Effort), under specified spectral
526
+ restrictions and with the desired SNR margin.
527
+
528
+ This object is read-write for the -O subtype EFMCu ports
529
+ (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
530
+
531
+ Changing of the Target Data Rate MUST be performed when the
532
+ link is Down. Attempts to change this object MUST be rejected
533
+ (in case of SNMP with the error inconsistentValue), if the
534
+ link is Up or Initializing.
535
+
536
+ Note that the current Data Rate of the EFMCu port is
537
+ represented by the ifSpeed object of IF-MIB.
538
+
539
+ This object MUST be maintained in a persistent manner.""",
540
+ }, # column
541
+ "efmCuTargetSnrMgn" : {
542
+ "nodetype" : "column",
543
+ "moduleName" : "EFM-CU-MIB",
544
+ "oid" : "1.3.6.1.2.1.167.1.1.1.1.5",
545
+ "status" : "current",
546
+ "syntax" : {
547
+ "type" : {
548
+ "basetype" : "Unsigned32",
549
+ "ranges" : [
550
+ {
551
+ "min" : "0",
552
+ "max" : "21"
553
+ },
554
+ ],
555
+ "range" : {
556
+ "min" : "0",
557
+ "max" : "21"
558
+ },
559
+ },
560
+ },
561
+ "access" : "readwrite",
562
+ "units" : "dB",
563
+ "description" :
564
+ """Desired EFMCu port SNR margin to be achieved on all PMEs
565
+
566
+
567
+
568
+ assigned to the port, during initialization. (The SNR margin
569
+ is the difference between the desired SNR and the actual SNR).
570
+
571
+ Note that 802.3ah recommends using a default target SNR margin
572
+ of 5 dB for 2BASE-TL ports and 6 dB for 10PASS-TS ports in
573
+ order to achieve a mean Bit Error Rate (BER) of 10^-7 at the
574
+ PMA service interface.
575
+
576
+ This object is read-write for the -O subtype EFMCu ports
577
+ (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
578
+
579
+ Changing of the target SNR margin MUST be performed when the
580
+ link is Down. Attempts to change this object MUST be rejected
581
+ (in case of SNMP with the error inconsistentValue), if the
582
+ link is Up or Initializing.
583
+
584
+ Note that the current SNR margin of the PMEs comprising the
585
+ EFMCu port is represented by efmCuPmeSnrMgn.
586
+
587
+ This object MUST be maintained in a persistent manner.""",
588
+ "reference" :
589
+ """[802.3ah] 61.1.2""",
590
+ }, # column
591
+ "efmCuAdaptiveSpectra" : {
592
+ "nodetype" : "column",
593
+ "moduleName" : "EFM-CU-MIB",
594
+ "oid" : "1.3.6.1.2.1.167.1.1.1.1.6",
595
+ "status" : "current",
596
+ "syntax" : {
597
+ "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
598
+ },
599
+ "access" : "readwrite",
600
+ "description" :
601
+ """Indicates how to utilize excess capacity when the copper
602
+ environment allows a higher total data rate to be achieved
603
+ than that specified by the efmCuTargetDataRate.
604
+
605
+ A value of true(1) indicates that the excess capability SHALL
606
+ be reclaimed by minimizing transmit power, e.g., using higher
607
+ constellations and Power Back-Off, in order to reduce
608
+ interference to other copper pairs in the binder and the
609
+ adverse impact to link/system performance.
610
+
611
+ A value of false(2) indicates that the excess capability SHALL
612
+ be converted to additional SNR margin and spread evenly across
613
+ all active PMEs assigned to the (PCS) port, to increase link
614
+ robustness.
615
+
616
+ This object is read-write for the -O subtype EFMCu ports
617
+ (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
618
+
619
+ Changing of this object MUST be performed when the link is
620
+
621
+
622
+
623
+ Down. Attempts to change this object MUST be rejected (in
624
+ case of SNMP with the error inconsistentValue), if the link
625
+ is Up or Initializing.
626
+
627
+ This object MUST be maintained in a persistent manner.""",
628
+ }, # column
629
+ "efmCuThreshLowRate" : {
630
+ "nodetype" : "column",
631
+ "moduleName" : "EFM-CU-MIB",
632
+ "oid" : "1.3.6.1.2.1.167.1.1.1.1.7",
633
+ "status" : "current",
634
+ "syntax" : {
635
+ "type" : {
636
+ "basetype" : "Unsigned32",
637
+ "ranges" : [
638
+ {
639
+ "min" : "1",
640
+ "max" : "100000"
641
+ },
642
+ ],
643
+ "range" : {
644
+ "min" : "1",
645
+ "max" : "100000"
646
+ },
647
+ },
648
+ },
649
+ "access" : "readwrite",
650
+ "units" : "Kbps",
651
+ "description" :
652
+ """This object configures the EFMCu port low-rate crossing alarm
653
+ threshold. When the current value of ifSpeed for this port
654
+ reaches/drops below or exceeds this threshold, an
655
+ efmCuLowRateCrossing notification MAY be generated if enabled
656
+ by efmCuLowRateCrossingEnable.
657
+
658
+ This object is read-write for the -O subtype EFMCu ports
659
+ (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
660
+
661
+ This object MUST be maintained in a persistent manner.""",
662
+ }, # column
663
+ "efmCuLowRateCrossingEnable" : {
664
+ "nodetype" : "column",
665
+ "moduleName" : "EFM-CU-MIB",
666
+ "oid" : "1.3.6.1.2.1.167.1.1.1.1.8",
667
+ "status" : "current",
668
+ "syntax" : {
669
+ "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
670
+ },
671
+ "access" : "readwrite",
672
+ "description" :
673
+ """Indicates whether efmCuLowRateCrossing notifications should
674
+ be generated for this interface.
675
+
676
+ A value of true(1) indicates that efmCuLowRateCrossing
677
+ notification is enabled. A value of false(2) indicates that
678
+ the notification is disabled.
679
+
680
+ This object is read-write for the -O subtype EFMCu ports
681
+ (2BaseTL-O/10PassTS-O) and not available for the -R subtypes.
682
+
683
+ This object MUST be maintained in a persistent manner.""",
684
+ }, # column
685
+ "efmCuPortCapabilityTable" : {
686
+ "nodetype" : "table",
687
+ "moduleName" : "EFM-CU-MIB",
688
+ "oid" : "1.3.6.1.2.1.167.1.1.2",
689
+ "status" : "current",
690
+ "description" :
691
+ """Table for Capabilities of EFMCu 2BASE-TL/10PASS-TS (PCS)
692
+ Ports. Entries in this table MUST be maintained in a
693
+ persistent manner""",
694
+ }, # table
695
+ "efmCuPortCapabilityEntry" : {
696
+ "nodetype" : "row",
697
+ "moduleName" : "EFM-CU-MIB",
698
+ "oid" : "1.3.6.1.2.1.167.1.1.2.1",
699
+ "status" : "current",
700
+ "linkage" : [
701
+ "ifIndex",
702
+ ],
703
+ "description" :
704
+ """An entry in the EFMCu Port Capability table.
705
+ Each entry represents an EFMCu port indexed by the ifIndex.
706
+ Note that an EFMCu PCS port runs on top of a single
707
+ or multiple PME port(s), which are also indexed by ifIndex.""",
708
+ }, # row
709
+ "efmCuPAFSupported" : {
710
+ "nodetype" : "column",
711
+ "moduleName" : "EFM-CU-MIB",
712
+ "oid" : "1.3.6.1.2.1.167.1.1.2.1.1",
713
+ "status" : "current",
714
+ "syntax" : {
715
+ "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
716
+ },
717
+ "access" : "readonly",
718
+ "description" :
719
+ """PME Aggregation Function (PAF) capability of the EFMCu port
720
+ (PCS).
721
+ This object has a value of true(1) when the PCS can perform
722
+ PME aggregation on the available PMEs.
723
+ Ports incapable of PAF SHALL return a value of false(2).
724
+
725
+ This object maps to the Clause 30 attribute aPAFSupported.
726
+
727
+ If a Clause 45 MDIO Interface to the PCS is present,
728
+ then this object maps to the PAF available bit in the
729
+ 10P/2B capability register.""",
730
+ "reference" :
731
+ """[802.3ah] 61.2.2, 30.11.1.1.4, 45.2.3.17.1""",
732
+ }, # column
733
+ "efmCuPeerPAFSupported" : {
734
+ "nodetype" : "column",
735
+ "moduleName" : "EFM-CU-MIB",
736
+ "oid" : "1.3.6.1.2.1.167.1.1.2.1.2",
737
+ "status" : "current",
738
+ "syntax" : {
739
+ "type" : { "module" :"EFM-CU-MIB", "name" : "EfmTruthValueOrUnknown"},
740
+ },
741
+ "access" : "readonly",
742
+ "description" :
743
+ """PME Aggregation Function (PAF) capability of the EFMCu port
744
+ (PCS) link partner.
745
+ This object has a value of true(1) when the remote PCS can
746
+ perform PME aggregation on its available PMEs.
747
+ Ports whose peers are incapable of PAF SHALL return a value
748
+ of false(2).
749
+ Ports whose peers cannot be reached because of the link
750
+ state SHALL return a value of unknown(0).
751
+
752
+ This object maps to the Clause 30 attribute
753
+ aRemotePAFSupported.
754
+
755
+ If a Clause 45 MDIO Interface to the PCS is present, then
756
+ this object maps to the Remote PAF supported bit in the
757
+ 10P/2B capability register.""",
758
+ "reference" :
759
+ """[802.3ah] 61.2.2, 30.11.1.1.9, 45.2.3.17.2""",
760
+ }, # column
761
+ "efmCuPAFCapacity" : {
762
+ "nodetype" : "column",
763
+ "moduleName" : "EFM-CU-MIB",
764
+ "oid" : "1.3.6.1.2.1.167.1.1.2.1.3",
765
+ "status" : "current",
766
+ "syntax" : {
767
+ "type" : {
768
+ "basetype" : "Unsigned32",
769
+ "ranges" : [
770
+ {
771
+ "min" : "1",
772
+ "max" : "32"
773
+ },
774
+ ],
775
+ "range" : {
776
+ "min" : "1",
777
+ "max" : "32"
778
+ },
779
+ },
780
+ },
781
+ "access" : "readonly",
782
+ "description" :
783
+ """Number of PMEs that can be aggregated by the local PAF.
784
+ The number of PMEs currently assigned to a particular
785
+ EFMCu port (efmCuNumPMEs) is never greater than
786
+ efmCuPAFCapacity.
787
+
788
+ This object maps to the Clause 30 attribute
789
+ aLocalPAFCapacity.""",
790
+ "reference" :
791
+ """[802.3ah] 61.2.2, 30.11.1.1.6""",
792
+ }, # column
793
+ "efmCuPeerPAFCapacity" : {
794
+ "nodetype" : "column",
795
+ "moduleName" : "EFM-CU-MIB",
796
+ "oid" : "1.3.6.1.2.1.167.1.1.2.1.4",
797
+ "status" : "current",
798
+ "syntax" : {
799
+ "type" : {
800
+ "basetype" : "Unsigned32",
801
+ "ranges" : [
802
+ {
803
+ "min" : "0",
804
+ "max" : "32"
805
+ },
806
+ ],
807
+ "range" : {
808
+ "min" : "0",
809
+ "max" : "32"
810
+ },
811
+ },
812
+ },
813
+ "access" : "readonly",
814
+ "description" :
815
+ """Number of PMEs that can be aggregated by the PAF of the peer
816
+ PHY (PCS port).
817
+ A value of 0 is returned when peer PAF capacity is unknown
818
+ (peer cannot be reached).
819
+
820
+
821
+
822
+
823
+ This object maps to the Clause 30 attribute
824
+ aRemotePAFCapacity.""",
825
+ "reference" :
826
+ """[802.3ah] 61.2.2, 30.11.1.1.10""",
827
+ }, # column
828
+ "efmCuPortStatusTable" : {
829
+ "nodetype" : "table",
830
+ "moduleName" : "EFM-CU-MIB",
831
+ "oid" : "1.3.6.1.2.1.167.1.1.3",
832
+ "status" : "current",
833
+ "description" :
834
+ """This table provides overall status information of EFMCu
835
+ 2BASE-TL/10PASS-TS ports, complementing the generic status
836
+ information from the ifTable of IF-MIB and ifMauTable of
837
+ MAU-MIB. Additional status information about connected PMEs
838
+ is available from the efmCuPmeStatusTable.
839
+
840
+ This table contains live data from the equipment. As such,
841
+ it is NOT persistent.""",
842
+ }, # table
843
+ "efmCuPortStatusEntry" : {
844
+ "nodetype" : "row",
845
+ "moduleName" : "EFM-CU-MIB",
846
+ "oid" : "1.3.6.1.2.1.167.1.1.3.1",
847
+ "status" : "current",
848
+ "linkage" : [
849
+ "ifIndex",
850
+ ],
851
+ "description" :
852
+ """An entry in the EFMCu Port Status table.
853
+ Each entry represents an EFMCu port indexed by the ifIndex.
854
+ Note that an EFMCu PCS port runs on top of a single
855
+ or multiple PME port(s), which are also indexed by ifIndex.""",
856
+ }, # row
857
+ "efmCuFltStatus" : {
858
+ "nodetype" : "column",
859
+ "moduleName" : "EFM-CU-MIB",
860
+ "oid" : "1.3.6.1.2.1.167.1.1.3.1.1",
861
+ "status" : "current",
862
+ "syntax" : {
863
+ "type" : {
864
+ "basetype" : "Bits",
865
+ "noPeer" : {
866
+ "nodetype" : "namednumber",
867
+ "number" : "0"
868
+ },
869
+ "peerPowerLoss" : {
870
+ "nodetype" : "namednumber",
871
+ "number" : "1"
872
+ },
873
+ "pmeSubTypeMismatch" : {
874
+ "nodetype" : "namednumber",
875
+ "number" : "2"
876
+ },
877
+ "lowRate" : {
878
+ "nodetype" : "namednumber",
879
+ "number" : "3"
880
+ },
881
+ },
882
+ },
883
+ "access" : "readonly",
884
+ "description" :
885
+ """EFMCu (PCS) port Fault Status. This is a bitmap of possible
886
+ conditions. The various bit positions are:
887
+ noPeer - the peer PHY cannot be reached (e.g.,
888
+ no PMEs attached, all PMEs are Down,
889
+ etc.). More info is available in
890
+ efmCuPmeFltStatus.
891
+ peerPowerLoss - the peer PHY has indicated impending
892
+ unit failure due to loss of local
893
+ power ('Dying Gasp').
894
+ pmeSubTypeMismatch - local PMEs in the aggregation group
895
+ are not of the same subtype, e.g.,
896
+ some PMEs in the local device are -O
897
+ while others are -R subtype.
898
+ lowRate - ifSpeed of the port reached or dropped
899
+ below efmCuThreshLowRate.
900
+
901
+ This object is intended to supplement the ifOperStatus object
902
+ in IF-MIB and ifMauMediaAvailable in MAU-MIB.
903
+
904
+ Additional information is available via the efmCuPmeFltStatus
905
+ object for each PME in the aggregation group (single PME if
906
+ PAF is disabled).""",
907
+ "reference" :
908
+ """IF-MIB, ifOperStatus; MAU-MIB, ifMauMediaAvailable;
909
+ efmCuPmeFltStatus""",
910
+ }, # column
911
+ "efmCuPortSide" : {
912
+ "nodetype" : "column",
913
+ "moduleName" : "EFM-CU-MIB",
914
+ "oid" : "1.3.6.1.2.1.167.1.1.3.1.2",
915
+ "status" : "current",
916
+ "syntax" : {
917
+ "type" : {
918
+ "basetype" : "Enumeration",
919
+ "subscriber" : {
920
+ "nodetype" : "namednumber",
921
+ "number" : "1"
922
+ },
923
+ "office" : {
924
+ "nodetype" : "namednumber",
925
+ "number" : "2"
926
+ },
927
+ "unknown" : {
928
+ "nodetype" : "namednumber",
929
+ "number" : "3"
930
+ },
931
+ },
932
+ },
933
+ "access" : "readonly",
934
+ "description" :
935
+ """EFM port mode of operation (subtype).
936
+ The value of 'subscriber' indicates that the port is
937
+
938
+
939
+
940
+ designated as '-R' subtype (all PMEs assigned to this port are
941
+ of subtype '-R').
942
+ The value of the 'office' indicates that the port is
943
+ designated as '-O' subtype (all PMEs assigned to this port are
944
+ of subtype '-O').
945
+ The value of 'unknown' indicates that the port has no assigned
946
+ PMEs yet or that the assigned PMEs are not of the same side
947
+ (subTypePMEMismatch).
948
+
949
+ This object partially maps to the Clause 30 attribute
950
+ aPhyEnd.""",
951
+ "reference" :
952
+ """[802.3ah] 61.1, 30.11.1.1.2""",
953
+ }, # column
954
+ "efmCuNumPMEs" : {
955
+ "nodetype" : "column",
956
+ "moduleName" : "EFM-CU-MIB",
957
+ "oid" : "1.3.6.1.2.1.167.1.1.3.1.3",
958
+ "status" : "current",
959
+ "syntax" : {
960
+ "type" : {
961
+ "basetype" : "Unsigned32",
962
+ "ranges" : [
963
+ {
964
+ "min" : "0",
965
+ "max" : "32"
966
+ },
967
+ ],
968
+ "range" : {
969
+ "min" : "0",
970
+ "max" : "32"
971
+ },
972
+ },
973
+ },
974
+ "access" : "readonly",
975
+ "description" :
976
+ """The number of PMEs that is currently aggregated by the local
977
+ PAF (assigned to the EFMCu port using the ifStackTable).
978
+ This number is never greater than efmCuPAFCapacity.
979
+
980
+ This object SHALL be automatically incremented or decremented
981
+ when a PME is added or deleted to/from the EFMCu port using
982
+ the ifStackTable.""",
983
+ "reference" :
984
+ """[802.3ah] 61.2.2, 30.11.1.1.6""",
985
+ }, # column
986
+ "efmCuPAFInErrors" : {
987
+ "nodetype" : "column",
988
+ "moduleName" : "EFM-CU-MIB",
989
+ "oid" : "1.3.6.1.2.1.167.1.1.3.1.4",
990
+ "status" : "current",
991
+ "syntax" : {
992
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
993
+ },
994
+ "access" : "readonly",
995
+ "description" :
996
+ """The number of fragments that have been received across the
997
+ gamma interface with RxErr asserted and discarded.
998
+ This read-only counter is inactive (not incremented) when the
999
+ PAF is unsupported or disabled. Upon disabling the PAF, the
1000
+ counter retains its previous value.
1001
+
1002
+ If a Clause 45 MDIO Interface to the PCS is present, then
1003
+ this object maps to the 10P/2B PAF RX error register.
1004
+
1005
+ Discontinuities in the value of this counter can occur at
1006
+ re-initialization of the management system, and at other times
1007
+ as indicated by the value of ifCounterDiscontinuityTime,
1008
+
1009
+
1010
+
1011
+ defined in IF-MIB.""",
1012
+ "reference" :
1013
+ """[802.3ah] 45.2.3.21""",
1014
+ }, # column
1015
+ "efmCuPAFInSmallFragments" : {
1016
+ "nodetype" : "column",
1017
+ "moduleName" : "EFM-CU-MIB",
1018
+ "oid" : "1.3.6.1.2.1.167.1.1.3.1.5",
1019
+ "status" : "current",
1020
+ "syntax" : {
1021
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
1022
+ },
1023
+ "access" : "readonly",
1024
+ "description" :
1025
+ """The number of fragments smaller than minFragmentSize
1026
+ (64 bytes) that have been received across the gamma interface
1027
+ and discarded.
1028
+ This read-only counter is inactive when the PAF is
1029
+ unsupported or disabled. Upon disabling the PAF, the counter
1030
+ retains its previous value.
1031
+
1032
+ If a Clause 45 MDIO Interface to the PCS is present, then
1033
+ this object maps to the 10P/2B PAF small fragments register.
1034
+
1035
+ Discontinuities in the value of this counter can occur at
1036
+ re-initialization of the management system, and at other times
1037
+ as indicated by the value of ifCounterDiscontinuityTime,
1038
+ defined in IF-MIB.""",
1039
+ "reference" :
1040
+ """[802.3ah] 45.2.3.22""",
1041
+ }, # column
1042
+ "efmCuPAFInLargeFragments" : {
1043
+ "nodetype" : "column",
1044
+ "moduleName" : "EFM-CU-MIB",
1045
+ "oid" : "1.3.6.1.2.1.167.1.1.3.1.6",
1046
+ "status" : "current",
1047
+ "syntax" : {
1048
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
1049
+ },
1050
+ "access" : "readonly",
1051
+ "description" :
1052
+ """The number of fragments larger than maxFragmentSize
1053
+ (512 bytes) that have been received across the gamma interface
1054
+ and discarded.
1055
+ This read-only counter is inactive when the PAF is
1056
+ unsupported or disabled. Upon disabling the PAF, the counter
1057
+ retains its previous value.
1058
+
1059
+ If a Clause 45 MDIO Interface to the PCS is present, then
1060
+ this object maps to the 10P/2B PAF large fragments register.
1061
+
1062
+ Discontinuities in the value of this counter can occur at
1063
+ re-initialization of the management system, and at other times
1064
+ as indicated by the value of ifCounterDiscontinuityTime,
1065
+ defined in IF-MIB.""",
1066
+ "reference" :
1067
+ """[802.3ah] 45.2.3.23""",
1068
+ }, # column
1069
+ "efmCuPAFInBadFragments" : {
1070
+ "nodetype" : "column",
1071
+ "moduleName" : "EFM-CU-MIB",
1072
+ "oid" : "1.3.6.1.2.1.167.1.1.3.1.7",
1073
+ "status" : "current",
1074
+ "syntax" : {
1075
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
1076
+ },
1077
+ "access" : "readonly",
1078
+ "description" :
1079
+ """The number of fragments that do not fit into the sequence
1080
+ expected by the frame assembly function and that have been
1081
+ received across the gamma interface and discarded (the
1082
+ frame buffer is flushed to the next valid frame start).
1083
+ This read-only counter is inactive when the PAF is
1084
+ unsupported or disabled. Upon disabling the PAF, the counter
1085
+ retains its previous value.
1086
+
1087
+ If a Clause 45 MDIO Interface to the PCS is present, then
1088
+ this object maps to the 10P/2B PAF bad fragments register.
1089
+
1090
+ Discontinuities in the value of this counter can occur at
1091
+ re-initialization of the management system, and at other times
1092
+ as indicated by the value of ifCounterDiscontinuityTime,
1093
+ defined in IF-MIB.""",
1094
+ "reference" :
1095
+ """[802.3ah] 45.2.3.25""",
1096
+ }, # column
1097
+ "efmCuPAFInLostFragments" : {
1098
+ "nodetype" : "column",
1099
+ "moduleName" : "EFM-CU-MIB",
1100
+ "oid" : "1.3.6.1.2.1.167.1.1.3.1.8",
1101
+ "status" : "current",
1102
+ "syntax" : {
1103
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
1104
+ },
1105
+ "access" : "readonly",
1106
+ "description" :
1107
+ """The number of gaps in the sequence of fragments that have
1108
+ been received across the gamma interface (the frame buffer is
1109
+ flushed to the next valid frame start, when fragment/fragments
1110
+ expected by the frame assembly function is/are not received).
1111
+ This read-only counter is inactive when the PAF is
1112
+ unsupported or disabled. Upon disabling the PAF, the counter
1113
+ retains its previous value.
1114
+
1115
+ If a Clause 45 MDIO Interface to the PCS is present, then
1116
+ this object maps to the 10P/2B PAF lost fragment register.
1117
+
1118
+ Discontinuities in the value of this counter can occur at
1119
+ re-initialization of the management system, and at other times
1120
+ as indicated by the value of ifCounterDiscontinuityTime,
1121
+ defined in IF-MIB.""",
1122
+ "reference" :
1123
+ """[802.3ah] 45.2.3.26""",
1124
+ }, # column
1125
+ "efmCuPAFInLostStarts" : {
1126
+ "nodetype" : "column",
1127
+ "moduleName" : "EFM-CU-MIB",
1128
+ "oid" : "1.3.6.1.2.1.167.1.1.3.1.9",
1129
+ "status" : "current",
1130
+ "syntax" : {
1131
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
1132
+ },
1133
+ "access" : "readonly",
1134
+ "description" :
1135
+ """The number of missing StartOfPacket indicators expected by
1136
+ the frame assembly function.
1137
+ This read-only counter is inactive when the PAF is
1138
+ unsupported or disabled. Upon disabling the PAF, the counter
1139
+ retains its previous value.
1140
+
1141
+ If a Clause 45 MDIO Interface to the PCS is present, then
1142
+ this object maps to the 10P/2B PAF lost start of fragment
1143
+ register.
1144
+
1145
+ Discontinuities in the value of this counter can occur at
1146
+ re-initialization of the management system, and at other times
1147
+ as indicated by the value of ifCounterDiscontinuityTime,
1148
+ defined in IF-MIB.""",
1149
+ "reference" :
1150
+ """[802.3ah] 45.2.3.27""",
1151
+ }, # column
1152
+ "efmCuPAFInLostEnds" : {
1153
+ "nodetype" : "column",
1154
+ "moduleName" : "EFM-CU-MIB",
1155
+ "oid" : "1.3.6.1.2.1.167.1.1.3.1.10",
1156
+ "status" : "current",
1157
+ "syntax" : {
1158
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
1159
+ },
1160
+ "access" : "readonly",
1161
+ "description" :
1162
+ """The number of missing EndOfPacket indicators expected by the
1163
+ frame assembly function.
1164
+ This read-only counter is inactive when the PAF is
1165
+ unsupported or disabled. Upon disabling the PAF, the counter
1166
+ retains its previous value.
1167
+
1168
+ If a Clause 45 MDIO Interface to the PCS is present, then
1169
+ this object maps to the 10P/2B PAF lost start of fragment
1170
+ register.
1171
+
1172
+ Discontinuities in the value of this counter can occur at
1173
+ re-initialization of the management system, and at other times
1174
+ as indicated by the value of ifCounterDiscontinuityTime,
1175
+ defined in IF-MIB.""",
1176
+ "reference" :
1177
+ """[802.3ah] 45.2.3.28""",
1178
+ }, # column
1179
+ "efmCuPAFInOverflows" : {
1180
+ "nodetype" : "column",
1181
+ "moduleName" : "EFM-CU-MIB",
1182
+ "oid" : "1.3.6.1.2.1.167.1.1.3.1.11",
1183
+ "status" : "current",
1184
+ "syntax" : {
1185
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
1186
+ },
1187
+ "access" : "readonly",
1188
+ "description" :
1189
+ """The number of fragments, received across the gamma interface
1190
+ and discarded, which would have caused the frame assembly
1191
+ buffer to overflow.
1192
+ This read-only counter is inactive when the PAF is
1193
+ unsupported or disabled. Upon disabling the PAF, the counter
1194
+ retains its previous value.
1195
+
1196
+ If a Clause 45 MDIO Interface to the PCS is present, then
1197
+ this object maps to the 10P/2B PAF overflow register.
1198
+
1199
+ Discontinuities in the value of this counter can occur at
1200
+ re-initialization of the management system, and at other times
1201
+ as indicated by the value of ifCounterDiscontinuityTime,
1202
+ defined in IF-MIB.""",
1203
+ "reference" :
1204
+ """[802.3ah] 45.2.3.24""",
1205
+ }, # column
1206
+ "efmCuPme" : {
1207
+ "nodetype" : "node",
1208
+ "moduleName" : "EFM-CU-MIB",
1209
+ "oid" : "1.3.6.1.2.1.167.1.2",
1210
+ }, # node
1211
+ "efmCuPmeNotifications" : {
1212
+ "nodetype" : "node",
1213
+ "moduleName" : "EFM-CU-MIB",
1214
+ "oid" : "1.3.6.1.2.1.167.1.2.0",
1215
+ }, # node
1216
+ "efmCuPmeConfTable" : {
1217
+ "nodetype" : "table",
1218
+ "moduleName" : "EFM-CU-MIB",
1219
+ "oid" : "1.3.6.1.2.1.167.1.2.1",
1220
+ "status" : "current",
1221
+ "description" :
1222
+ """Table for Configuration of common aspects for EFMCu
1223
+ 2BASE-TL/10PASS-TS PME ports (modems). Configuration of
1224
+ aspects specific to 2BASE-TL or 10PASS-TS PME types is
1225
+ represented in efmCuPme2BConfTable and efmCuPme10PConfTable,
1226
+ respectively.
1227
+
1228
+ Entries in this table MUST be maintained in a persistent
1229
+ manner.""",
1230
+ }, # table
1231
+ "efmCuPmeConfEntry" : {
1232
+ "nodetype" : "row",
1233
+ "moduleName" : "EFM-CU-MIB",
1234
+ "oid" : "1.3.6.1.2.1.167.1.2.1.1",
1235
+ "status" : "current",
1236
+ "linkage" : [
1237
+ "ifIndex",
1238
+ ],
1239
+ "description" :
1240
+ """An entry in the EFMCu PME Configuration table.
1241
+ Each entry represents common aspects of an EFMCu PME port
1242
+ indexed by the ifIndex. Note that an EFMCu PME port can be
1243
+ stacked below a single PCS port, also indexed by ifIndex,
1244
+ possibly together with other PME ports if PAF is enabled.""",
1245
+ }, # row
1246
+ "efmCuPmeAdminSubType" : {
1247
+ "nodetype" : "column",
1248
+ "moduleName" : "EFM-CU-MIB",
1249
+ "oid" : "1.3.6.1.2.1.167.1.2.1.1.1",
1250
+ "status" : "current",
1251
+ "syntax" : {
1252
+ "type" : {
1253
+ "basetype" : "Enumeration",
1254
+ "ieee2BaseTLO" : {
1255
+ "nodetype" : "namednumber",
1256
+ "number" : "1"
1257
+ },
1258
+ "ieee2BaseTLR" : {
1259
+ "nodetype" : "namednumber",
1260
+ "number" : "2"
1261
+ },
1262
+ "ieee10PassTSO" : {
1263
+ "nodetype" : "namednumber",
1264
+ "number" : "3"
1265
+ },
1266
+ "ieee10PassTSR" : {
1267
+ "nodetype" : "namednumber",
1268
+ "number" : "4"
1269
+ },
1270
+ "ieee2BaseTLor10PassTSR" : {
1271
+ "nodetype" : "namednumber",
1272
+ "number" : "5"
1273
+ },
1274
+ "ieee2BaseTLor10PassTSO" : {
1275
+ "nodetype" : "namednumber",
1276
+ "number" : "6"
1277
+ },
1278
+ "ieee10PassTSor2BaseTLO" : {
1279
+ "nodetype" : "namednumber",
1280
+ "number" : "7"
1281
+ },
1282
+ },
1283
+ },
1284
+ "access" : "readwrite",
1285
+ "description" :
1286
+ """Administrative (desired) subtype of the PME.
1287
+ Possible values are:
1288
+ ieee2BaseTLO - PME SHALL operate as 2BaseTL-O
1289
+ ieee2BaseTLR - PME SHALL operate as 2BaseTL-R
1290
+ ieee10PassTSO - PME SHALL operate as 10PassTS-O
1291
+ ieee10PassTSR - PME SHALL operate as 10PassTS-R
1292
+ ieee2BaseTLor10PassTSR - PME SHALL operate as 2BaseTL-R or
1293
+ 10PassTS-R. The actual value will
1294
+ be set by the -O link partner
1295
+ during initialization (handshake).
1296
+ ieee2BaseTLor10PassTSO - PME SHALL operate as 2BaseTL-O
1297
+ (preferred) or 10PassTS-O. The
1298
+ actual value will be set during
1299
+ initialization depending on the -R
1300
+ link partner capability (i.e., if
1301
+ -R is incapable of the preferred
1302
+ 2BaseTL mode, 10PassTS will be
1303
+ used).
1304
+ ieee10PassTSor2BaseTLO - PME SHALL operate as 10PassTS-O
1305
+
1306
+
1307
+
1308
+ (preferred) or 2BaseTL-O. The
1309
+ actual value will be set during
1310
+ initialization depending on the -R
1311
+ link partner capability (i.e., if
1312
+ -R is incapable of the preferred
1313
+ 10PassTS mode, 2BaseTL will be
1314
+ used).
1315
+
1316
+ Changing efmCuPmeAdminSubType is a traffic-disruptive
1317
+ operation and as such SHALL be done when the link is Down.
1318
+ Attempts to change this object SHALL be rejected if the link
1319
+ is Up or Initializing.
1320
+ Attempts to change this object to an unsupported subtype
1321
+ (see efmCuPmeSubTypesSupported) SHALL be rejected.
1322
+
1323
+ The current operational subtype is indicated by the
1324
+ efmCuPmeOperSubType variable.
1325
+
1326
+ If a Clause 45 MDIO Interface to the PMA/PMD is present, then
1327
+ this object combines values of the Port subtype select bits
1328
+ and the PMA/PMD type selection bits in the 10P/2B PMA/PMD
1329
+ control register.""",
1330
+ "reference" :
1331
+ """[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7""",
1332
+ }, # column
1333
+ "efmCuPmeAdminProfile" : {
1334
+ "nodetype" : "column",
1335
+ "moduleName" : "EFM-CU-MIB",
1336
+ "oid" : "1.3.6.1.2.1.167.1.2.1.1.2",
1337
+ "status" : "current",
1338
+ "syntax" : {
1339
+ "type" : { "module" :"EFM-CU-MIB", "name" : "EfmProfileIndexOrZero"},
1340
+ },
1341
+ "access" : "readwrite",
1342
+ "default" : "0",
1343
+ "description" :
1344
+ """Desired PME configuration profile. This object is a pointer
1345
+ to an entry in either the efmCuPme2BProfileTable or the
1346
+ efmCuPme10PProfileTable, depending on the current operating
1347
+ SubType of the PME. The value of this object is the index of
1348
+ the referenced profile.
1349
+ The value of zero (default) indicates that the PME is
1350
+ configured via the efmCuAdminProfile object for the PCS port
1351
+ to which this PME is assigned. That is, the profile
1352
+ referenced by efmCuPmeAdminProfile takes precedence
1353
+ over the profile(s) referenced by efmCuAdminProfile.
1354
+
1355
+ This object is writable and readable for the CO subtype PMEs
1356
+ (2BaseTL-O or 10PassTS-O). It is irrelevant for the CPE
1357
+ subtype (2BaseTL-R or 10PassTS-R) -- a zero value SHALL be
1358
+ returned on an attempt to read this object and any attempt
1359
+ to change this object MUST be rejected in this case.
1360
+
1361
+
1362
+
1363
+
1364
+ Note that the current operational profile value is available
1365
+ via efmCuPmeOperProfile object.
1366
+
1367
+ Any modification of this object MUST be performed when the
1368
+ link is Down. Attempts to change this object MUST be
1369
+ rejected, if the link is Up or Initializing.
1370
+
1371
+ Attempts to set this object to a value that is not the value
1372
+ of the index for an active entry in the corresponding profile
1373
+ table MUST be rejected.
1374
+
1375
+ This object maps to the Clause 30 attribute aProfileSelect.
1376
+
1377
+ This object MUST be maintained in a persistent manner.""",
1378
+ "reference" :
1379
+ """[802.3ah] 30.11.2.1.6""",
1380
+ }, # column
1381
+ "efmCuPAFRemoteDiscoveryCode" : {
1382
+ "nodetype" : "column",
1383
+ "moduleName" : "EFM-CU-MIB",
1384
+ "oid" : "1.3.6.1.2.1.167.1.2.1.1.3",
1385
+ "status" : "current",
1386
+ "syntax" : {
1387
+ "type" : {
1388
+ "basetype" : "OctetString",
1389
+ "parent module" : {
1390
+ "name" : "SNMPv2-TC",
1391
+ "type" : "PhysAddress",
1392
+ },
1393
+ "ranges" : [
1394
+ {
1395
+ "min" : "0",
1396
+ "max" : "0"
1397
+ },
1398
+ {
1399
+ "min" : "6",
1400
+ "max" : "6"
1401
+ },
1402
+ ],
1403
+ "range" : {
1404
+ "min" : "0",
1405
+ "max" : "6"
1406
+ },
1407
+ },
1408
+ },
1409
+ "access" : "readwrite",
1410
+ "description" :
1411
+ """PAF Remote Discovery Code of the PME port at the CO.
1412
+ The 6-octet Discovery Code of the peer PCS connected via
1413
+ the PME.
1414
+ Reading this object results in a Discovery Get operation.
1415
+ Setting this object to all zeroes results in a Discovery
1416
+ Clear_if_Same operation (the value of efmCuPAFDiscoveryCode
1417
+ at the peer PCS SHALL be the same as efmCuPAFDiscoveryCode of
1418
+ the local PCS associated with the PME for the operation to
1419
+ succeed).
1420
+ Writing a non-zero value to this object results in a
1421
+ Discovery Set_if_Clear operation.
1422
+ A zero-length octet string SHALL be returned on an attempt to
1423
+ read this object when PAF aggregation is not enabled.
1424
+
1425
+ This object is irrelevant in CPE port (-R) subtypes: in this
1426
+ case, a zero-length octet string SHALL be returned on an
1427
+ attempt to read this object; writing to this object SHALL
1428
+ be rejected.
1429
+
1430
+ Discovery MUST be performed when the link is Down.
1431
+ Attempts to change this object MUST be rejected (in case of
1432
+ SNMP with the error inconsistentValue), if the link is Up or
1433
+ Initializing.
1434
+
1435
+
1436
+
1437
+
1438
+ If a Clause 45 MDIO Interface to the PMA/PMD is present, then
1439
+ this object is a function of 10P/2B aggregation discovery
1440
+ control register, Discovery operation result bits in 10P/2B
1441
+ aggregation and discovery status register and
1442
+ 10P/2B aggregation discovery code register.""",
1443
+ "reference" :
1444
+ """[802.3ah] 61.2.2.8.4, 45.2.6.6-45.2.6.8""",
1445
+ }, # column
1446
+ "efmCuPmeThreshLineAtn" : {
1447
+ "nodetype" : "column",
1448
+ "moduleName" : "EFM-CU-MIB",
1449
+ "oid" : "1.3.6.1.2.1.167.1.2.1.1.4",
1450
+ "status" : "current",
1451
+ "syntax" : {
1452
+ "type" : {
1453
+ "basetype" : "Integer32",
1454
+ "ranges" : [
1455
+ {
1456
+ "min" : "-127",
1457
+ "max" : "128"
1458
+ },
1459
+ ],
1460
+ "range" : {
1461
+ "min" : "-127",
1462
+ "max" : "128"
1463
+ },
1464
+ },
1465
+ },
1466
+ "access" : "readwrite",
1467
+ "units" : "dB",
1468
+ "description" :
1469
+ """Desired Line Attenuation threshold for the 2B/10P PME.
1470
+ This object configures the line attenuation alarm threshold.
1471
+ When the current value of Line Attenuation reaches or
1472
+ exceeds this threshold, an efmCuPmeLineAtnCrossing
1473
+ notification MAY be generated, if enabled by
1474
+ efmCuPmeLineAtnCrossingEnable.
1475
+
1476
+ This object is writable for the CO subtype PMEs (-O).
1477
+ It is read-only for the CPE subtype (-R).
1478
+
1479
+ Changing of the Line Attenuation threshold MUST be performed
1480
+ when the link is Down. Attempts to change this object MUST be
1481
+ rejected (in case of SNMP with the error inconsistentValue),
1482
+ if the link is Up or Initializing.
1483
+
1484
+ If a Clause 45 MDIO Interface to the PME is present, then this
1485
+ object maps to the loop attenuation threshold bits in
1486
+ the 2B PMD line quality thresholds register.""",
1487
+ "reference" :
1488
+ """[802.3ah] 45.2.1.36""",
1489
+ }, # column
1490
+ "efmCuPmeThreshSnrMgn" : {
1491
+ "nodetype" : "column",
1492
+ "moduleName" : "EFM-CU-MIB",
1493
+ "oid" : "1.3.6.1.2.1.167.1.2.1.1.5",
1494
+ "status" : "current",
1495
+ "syntax" : {
1496
+ "type" : {
1497
+ "basetype" : "Integer32",
1498
+ "ranges" : [
1499
+ {
1500
+ "min" : "-127",
1501
+ "max" : "128"
1502
+ },
1503
+ ],
1504
+ "range" : {
1505
+ "min" : "-127",
1506
+ "max" : "128"
1507
+ },
1508
+ },
1509
+ },
1510
+ "access" : "readwrite",
1511
+ "units" : "dB",
1512
+ "description" :
1513
+ """Desired SNR margin threshold for the 2B/10P PME.
1514
+ This object configures the SNR margin alarm threshold.
1515
+ When the current value of SNR margin reaches or exceeds this
1516
+ threshold, an efmCuPmeSnrMgnCrossing notification MAY be
1517
+ generated, if enabled by efmCuPmeSnrMgnCrossingEnable.
1518
+
1519
+
1520
+
1521
+ This object is writable for the CO subtype PMEs
1522
+ (2BaseTL-O/10PassTS-O). It is read-only for the CPE subtype
1523
+ (2BaseTL-R/10PassTS-R).
1524
+
1525
+ Changing of the SNR margin threshold MUST be performed when
1526
+ the link is Down. Attempts to change this object MUST be
1527
+ rejected (in case of SNMP with the error inconsistentValue),
1528
+ if the link is Up or Initializing.
1529
+
1530
+ If a Clause 45 MDIO Interface to the PME is present, then this
1531
+ object maps to the SNR margin threshold bits in the 2B PMD
1532
+ line quality thresholds register.""",
1533
+ "reference" :
1534
+ """[802.3ah] 45.2.1.36""",
1535
+ }, # column
1536
+ "efmCuPmeLineAtnCrossingEnable" : {
1537
+ "nodetype" : "column",
1538
+ "moduleName" : "EFM-CU-MIB",
1539
+ "oid" : "1.3.6.1.2.1.167.1.2.1.1.6",
1540
+ "status" : "current",
1541
+ "syntax" : {
1542
+ "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
1543
+ },
1544
+ "access" : "readwrite",
1545
+ "description" :
1546
+ """Indicates whether efmCuPmeLineAtnCrossing notifications
1547
+ should be generated for this interface.
1548
+
1549
+ A value of true(1) indicates that efmCuPmeLineAtnCrossing
1550
+ notification is enabled. A value of false(2) indicates that
1551
+ the notification is disabled.""",
1552
+ }, # column
1553
+ "efmCuPmeSnrMgnCrossingEnable" : {
1554
+ "nodetype" : "column",
1555
+ "moduleName" : "EFM-CU-MIB",
1556
+ "oid" : "1.3.6.1.2.1.167.1.2.1.1.7",
1557
+ "status" : "current",
1558
+ "syntax" : {
1559
+ "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
1560
+ },
1561
+ "access" : "readwrite",
1562
+ "description" :
1563
+ """Indicates whether efmCuPmeSnrMgnCrossing notifications
1564
+ should be generated for this interface.
1565
+
1566
+ A value of true(1) indicates that efmCuPmeSnrMgnCrossing
1567
+ notification is enabled. A value of false(2) indicates that
1568
+ the notification is disabled.""",
1569
+ }, # column
1570
+ "efmCuPmeDeviceFaultEnable" : {
1571
+ "nodetype" : "column",
1572
+ "moduleName" : "EFM-CU-MIB",
1573
+ "oid" : "1.3.6.1.2.1.167.1.2.1.1.8",
1574
+ "status" : "current",
1575
+ "syntax" : {
1576
+ "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
1577
+ },
1578
+ "access" : "readwrite",
1579
+ "description" :
1580
+ """Indicates whether efmCuPmeDeviceFault notifications
1581
+
1582
+
1583
+
1584
+ should be generated for this interface.
1585
+
1586
+ A value of true(1) indicates that efmCuPmeDeviceFault
1587
+ notification is enabled. A value of false(2) indicates that
1588
+ the notification is disabled.""",
1589
+ }, # column
1590
+ "efmCuPmeConfigInitFailEnable" : {
1591
+ "nodetype" : "column",
1592
+ "moduleName" : "EFM-CU-MIB",
1593
+ "oid" : "1.3.6.1.2.1.167.1.2.1.1.9",
1594
+ "status" : "current",
1595
+ "syntax" : {
1596
+ "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
1597
+ },
1598
+ "access" : "readwrite",
1599
+ "description" :
1600
+ """Indicates whether efmCuPmeConfigInitFailure notifications
1601
+ should be generated for this interface.
1602
+
1603
+ A value of true(1) indicates that efmCuPmeConfigInitFailure
1604
+ notification is enabled. A value of false(2) indicates that
1605
+ the notification is disabled.""",
1606
+ }, # column
1607
+ "efmCuPmeProtocolInitFailEnable" : {
1608
+ "nodetype" : "column",
1609
+ "moduleName" : "EFM-CU-MIB",
1610
+ "oid" : "1.3.6.1.2.1.167.1.2.1.1.10",
1611
+ "status" : "current",
1612
+ "syntax" : {
1613
+ "type" : { "module" :"SNMPv2-TC", "name" : "TruthValue"},
1614
+ },
1615
+ "access" : "readwrite",
1616
+ "description" :
1617
+ """Indicates whether efmCuPmeProtocolInitFailure notifications
1618
+ should be generated for this interface.
1619
+
1620
+ A value of true(1) indicates that efmCuPmeProtocolInitFailure
1621
+ notification is enabled. A value of false(2) indicates that
1622
+ the notification is disabled.""",
1623
+ }, # column
1624
+ "efmCuPmeCapabilityTable" : {
1625
+ "nodetype" : "table",
1626
+ "moduleName" : "EFM-CU-MIB",
1627
+ "oid" : "1.3.6.1.2.1.167.1.2.2",
1628
+ "status" : "current",
1629
+ "description" :
1630
+ """Table for the configuration of common aspects for EFMCu
1631
+ 2BASE-TL/10PASS-TS PME ports (modems). The configuration of
1632
+ aspects specific to 2BASE-TL or 10PASS-TS PME types is
1633
+ represented in the efmCuPme2BConfTable and the
1634
+ efmCuPme10PConfTable, respectively.
1635
+
1636
+ Entries in this table MUST be maintained in a persistent
1637
+ manner.""",
1638
+ }, # table
1639
+ "efmCuPmeCapabilityEntry" : {
1640
+ "nodetype" : "row",
1641
+ "moduleName" : "EFM-CU-MIB",
1642
+ "oid" : "1.3.6.1.2.1.167.1.2.2.1",
1643
+ "status" : "current",
1644
+ "linkage" : [
1645
+ "ifIndex",
1646
+ ],
1647
+ "description" :
1648
+ """An entry in the EFMCu PME Capability table.
1649
+ Each entry represents common aspects of an EFMCu PME port
1650
+ indexed by the ifIndex. Note that an EFMCu PME port can be
1651
+ stacked below a single PCS port, also indexed by ifIndex,
1652
+ possibly together with other PME ports if PAF is enabled.""",
1653
+ }, # row
1654
+ "efmCuPmeSubTypesSupported" : {
1655
+ "nodetype" : "column",
1656
+ "moduleName" : "EFM-CU-MIB",
1657
+ "oid" : "1.3.6.1.2.1.167.1.2.2.1.1",
1658
+ "status" : "current",
1659
+ "syntax" : {
1660
+ "type" : {
1661
+ "basetype" : "Bits",
1662
+ "ieee2BaseTLO" : {
1663
+ "nodetype" : "namednumber",
1664
+ "number" : "0"
1665
+ },
1666
+ "ieee2BaseTLR" : {
1667
+ "nodetype" : "namednumber",
1668
+ "number" : "1"
1669
+ },
1670
+ "ieee10PassTSO" : {
1671
+ "nodetype" : "namednumber",
1672
+ "number" : "2"
1673
+ },
1674
+ "ieee10PassTSR" : {
1675
+ "nodetype" : "namednumber",
1676
+ "number" : "3"
1677
+ },
1678
+ },
1679
+ },
1680
+ "access" : "readonly",
1681
+ "description" :
1682
+ """PME supported subtypes. This is a bitmap of possible
1683
+ subtypes. The various bit positions are:
1684
+ ieee2BaseTLO - PME is capable of operating as 2BaseTL-O
1685
+ ieee2BaseTLR - PME is capable of operating as 2BaseTL-R
1686
+ ieee10PassTSO - PME is capable of operating as 10PassTS-O
1687
+ ieee10PassTSR - PME is capable of operating as 10PassTS-R
1688
+
1689
+ The desired mode of operation is determined by
1690
+ efmCuPmeAdminSubType, while efmCuPmeOperSubType reflects the
1691
+ current operating mode.
1692
+
1693
+ If a Clause 45 MDIO Interface to the PCS is present, then this
1694
+ object combines the 10PASS-TS capable and 2BASE-TL capable
1695
+ bits in the 10P/2B PMA/PMD speed ability register and the
1696
+ CO supported and CPE supported bits in the 10P/2B PMA/PMD
1697
+ status register.""",
1698
+ "reference" :
1699
+ """[802.3ah] 61.1, 45.2.1.4.1, 45.2.1.4.2, 45.2.1.12.2,
1700
+ 45.2.1.12.3""",
1701
+ }, # column
1702
+ "efmCuPmeStatusTable" : {
1703
+ "nodetype" : "table",
1704
+ "moduleName" : "EFM-CU-MIB",
1705
+ "oid" : "1.3.6.1.2.1.167.1.2.3",
1706
+ "status" : "current",
1707
+ "description" :
1708
+ """This table provides common status information of EFMCu
1709
+ 2BASE-TL/10PASS-TS PME ports. Status information specific
1710
+ to 10PASS-TS PME is represented in efmCuPme10PStatusTable.
1711
+
1712
+ This table contains live data from the equipment. As such,
1713
+ it is NOT persistent.""",
1714
+ }, # table
1715
+ "efmCuPmeStatusEntry" : {
1716
+ "nodetype" : "row",
1717
+ "moduleName" : "EFM-CU-MIB",
1718
+ "oid" : "1.3.6.1.2.1.167.1.2.3.1",
1719
+ "status" : "current",
1720
+ "linkage" : [
1721
+ "ifIndex",
1722
+ ],
1723
+ "description" :
1724
+ """An entry in the EFMCu PME Status table.
1725
+ Each entry represents common aspects of an EFMCu PME port
1726
+ indexed by the ifIndex. Note that an EFMCu PME port can be
1727
+ stacked below a single PCS port, also indexed by ifIndex,
1728
+ possibly together with other PME ports if PAF is enabled.""",
1729
+ }, # row
1730
+ "efmCuPmeOperStatus" : {
1731
+ "nodetype" : "column",
1732
+ "moduleName" : "EFM-CU-MIB",
1733
+ "oid" : "1.3.6.1.2.1.167.1.2.3.1.1",
1734
+ "status" : "current",
1735
+ "syntax" : {
1736
+ "type" : {
1737
+ "basetype" : "Enumeration",
1738
+ "up" : {
1739
+ "nodetype" : "namednumber",
1740
+ "number" : "1"
1741
+ },
1742
+ "downNotReady" : {
1743
+ "nodetype" : "namednumber",
1744
+ "number" : "2"
1745
+ },
1746
+ "downReady" : {
1747
+ "nodetype" : "namednumber",
1748
+ "number" : "3"
1749
+ },
1750
+ "init" : {
1751
+ "nodetype" : "namednumber",
1752
+ "number" : "4"
1753
+ },
1754
+ },
1755
+ },
1756
+ "access" : "readonly",
1757
+ "description" :
1758
+ """Current PME link Operational Status. Possible values are:
1759
+ up(1) - The link is Up and ready to pass
1760
+ 64/65-octet encoded frames or fragments.
1761
+ downNotReady(2) - The link is Down and the PME does not
1762
+ detect Handshake tones from its peer.
1763
+ This value may indicate a possible
1764
+ problem with the peer PME.
1765
+ downReady(3) - The link is Down and the PME detects
1766
+ Handshake tones from its peer.
1767
+ init(4) - The link is Initializing, as a result of
1768
+ ifAdminStatus being set to 'up' for a
1769
+ particular PME or a PCS to which the PME
1770
+ is connected.
1771
+
1772
+ This object is intended to supplement the Down(2) state of
1773
+ ifOperStatus.
1774
+
1775
+ This object partially maps to the Clause 30 attribute
1776
+ aPMEStatus.
1777
+
1778
+ If a Clause 45 MDIO Interface to the PME is present, then this
1779
+ object partially maps to PMA/PMD link status bits in 10P/2B
1780
+ PMA/PMD status register.""",
1781
+ "reference" :
1782
+ """[802.3ah] 30.11.2.1.3, 45.2.1.12.4""",
1783
+ }, # column
1784
+ "efmCuPmeFltStatus" : {
1785
+ "nodetype" : "column",
1786
+ "moduleName" : "EFM-CU-MIB",
1787
+ "oid" : "1.3.6.1.2.1.167.1.2.3.1.2",
1788
+ "status" : "current",
1789
+ "syntax" : {
1790
+ "type" : {
1791
+ "basetype" : "Bits",
1792
+ "lossOfFraming" : {
1793
+ "nodetype" : "namednumber",
1794
+ "number" : "0"
1795
+ },
1796
+ "snrMgnDefect" : {
1797
+ "nodetype" : "namednumber",
1798
+ "number" : "1"
1799
+ },
1800
+ "lineAtnDefect" : {
1801
+ "nodetype" : "namednumber",
1802
+ "number" : "2"
1803
+ },
1804
+ "deviceFault" : {
1805
+ "nodetype" : "namednumber",
1806
+ "number" : "3"
1807
+ },
1808
+ "configInitFailure" : {
1809
+ "nodetype" : "namednumber",
1810
+ "number" : "4"
1811
+ },
1812
+ "protocolInitFailure" : {
1813
+ "nodetype" : "namednumber",
1814
+ "number" : "5"
1815
+ },
1816
+ },
1817
+ },
1818
+ "access" : "readonly",
1819
+ "description" :
1820
+ """Current/Last PME link Fault Status. This is a bitmap of
1821
+ possible conditions. The various bit positions are:
1822
+
1823
+ lossOfFraming - Loss of Framing for 10P or
1824
+ Loss of Sync word for 2B PMD or
1825
+ Loss of 64/65-octet framing.
1826
+
1827
+
1828
+
1829
+ snrMgnDefect - SNR margin dropped below the
1830
+ threshold.
1831
+ lineAtnDefect - Line Attenuation exceeds the
1832
+ threshold.
1833
+ deviceFault - Indicates a vendor-dependent
1834
+ diagnostic or self-test fault
1835
+ has been detected.
1836
+ configInitFailure - Configuration initialization failure,
1837
+ due to inability of the PME link to
1838
+ support the configuration profile,
1839
+ requested during initialization.
1840
+ protocolInitFailure - Protocol initialization failure, due
1841
+ to an incompatible protocol used by
1842
+ the peer PME during init (that could
1843
+ happen if a peer PMD is a regular
1844
+ G.SDHSL/VDSL modem instead of a
1845
+ 2BASE-TL/10PASS-TS PME).
1846
+
1847
+ This object is intended to supplement ifOperStatus in IF-MIB.
1848
+
1849
+ This object holds information about the last fault.
1850
+ efmCuPmeFltStatus is cleared by the device restart.
1851
+ In addition, lossOfFraming, configInitFailure, and
1852
+ protocolInitFailure are cleared by PME init;
1853
+ deviceFault is cleared by successful diagnostics/test;
1854
+ snrMgnDefect and lineAtnDefect are cleared by SNR margin
1855
+ and Line attenuation, respectively, returning to norm and by
1856
+ PME init.
1857
+
1858
+ This object partially maps to the Clause 30 attribute
1859
+ aPMEStatus.
1860
+
1861
+ If a Clause 45 MDIO Interface to the PME is present, then this
1862
+ object consolidates information from various PMA/PMD
1863
+ registers, namely: Fault bit in PMA/PMD status 1 register,
1864
+ 10P/2B PMA/PMD link loss register,
1865
+ 10P outgoing indicator bits status register,
1866
+ 10P incoming indicator bits status register,
1867
+ 2B state defects register.""",
1868
+ "reference" :
1869
+ """[802.3ah] 30.11.2.1.3, 45.2.1.2.1, 45.2.1.38,
1870
+ 45.2.1.39, 45.2.1.54""",
1871
+ }, # column
1872
+ "efmCuPmeOperSubType" : {
1873
+ "nodetype" : "column",
1874
+ "moduleName" : "EFM-CU-MIB",
1875
+ "oid" : "1.3.6.1.2.1.167.1.2.3.1.3",
1876
+ "status" : "current",
1877
+ "syntax" : {
1878
+ "type" : {
1879
+ "basetype" : "Enumeration",
1880
+ "ieee2BaseTLO" : {
1881
+ "nodetype" : "namednumber",
1882
+ "number" : "1"
1883
+ },
1884
+ "ieee2BaseTLR" : {
1885
+ "nodetype" : "namednumber",
1886
+ "number" : "2"
1887
+ },
1888
+ "ieee10PassTSO" : {
1889
+ "nodetype" : "namednumber",
1890
+ "number" : "3"
1891
+ },
1892
+ "ieee10PassTSR" : {
1893
+ "nodetype" : "namednumber",
1894
+ "number" : "4"
1895
+ },
1896
+ },
1897
+ },
1898
+ "access" : "readonly",
1899
+ "description" :
1900
+ """Current operational subtype of the PME.
1901
+ Possible values are:
1902
+ ieee2BaseTLO - PME operates as 2BaseTL-O
1903
+ ieee2BaseTLR - PME operates as 2BaseTL-R
1904
+ ieee10PassTSO - PME operates as 10PassTS-O
1905
+ ieee10PassTSR - PME operates as 10PassTS-R
1906
+
1907
+ The desired operational subtype of the PME can be configured
1908
+ via the efmCuPmeAdminSubType variable.
1909
+
1910
+ If a Clause 45 MDIO Interface to the PMA/PMD is present, then
1911
+ this object combines values of the Port subtype select
1912
+ bits, the PMA/PMD type selection bits in the 10P/2B
1913
+ PMA/PMD control register, and the PMA/PMD link status bits in
1914
+ the 10P/2B PMA/PMD status register.""",
1915
+ "reference" :
1916
+ """[802.3ah] 61.1, 45.2.1.11.4, 45.2.1.11.7, 45.2.1.12.4""",
1917
+ }, # column
1918
+ "efmCuPmeOperProfile" : {
1919
+ "nodetype" : "column",
1920
+ "moduleName" : "EFM-CU-MIB",
1921
+ "oid" : "1.3.6.1.2.1.167.1.2.3.1.4",
1922
+ "status" : "current",
1923
+ "syntax" : {
1924
+ "type" : { "module" :"EFM-CU-MIB", "name" : "EfmProfileIndexOrZero"},
1925
+ },
1926
+ "access" : "readonly",
1927
+ "description" :
1928
+ """PME current operating profile. This object is a pointer to
1929
+ an entry in either the efmCuPme2BProfileTable or the
1930
+ efmCuPme10PProfileTable, depending on the current operating
1931
+ SubType of the PME as indicated by efmCuPmeOperSubType.
1932
+ Note that a profile entry to which efmCuPmeOperProfile is
1933
+ pointing can be created automatically to reflect achieved
1934
+ parameters in adaptive (not fixed) initialization,
1935
+ i.e., values of efmCuPmeOperProfile and efmCuAdminProfile or
1936
+ efmCuPmeAdminProfile may differ.
1937
+ The value of zero indicates that the PME is Down or
1938
+ Initializing.
1939
+
1940
+ This object partially maps to the aOperatingProfile attribute
1941
+ in Clause 30.""",
1942
+ "reference" :
1943
+ """[802.3ah] 30.11.2.1.7""",
1944
+ }, # column
1945
+ "efmCuPmeSnrMgn" : {
1946
+ "nodetype" : "column",
1947
+ "moduleName" : "EFM-CU-MIB",
1948
+ "oid" : "1.3.6.1.2.1.167.1.2.3.1.5",
1949
+ "status" : "current",
1950
+ "syntax" : {
1951
+ "type" : {
1952
+ "basetype" : "Integer32",
1953
+ "ranges" : [
1954
+ {
1955
+ "min" : "-127",
1956
+ "max" : "128"
1957
+ },
1958
+ {
1959
+ "min" : "65535",
1960
+ "max" : "65535"
1961
+ },
1962
+ ],
1963
+ "range" : {
1964
+ "min" : "-127",
1965
+ "max" : "65535"
1966
+ },
1967
+ },
1968
+ },
1969
+ "access" : "readonly",
1970
+ "units" : "dB",
1971
+ "description" :
1972
+ """The current Signal to Noise Ratio (SNR) margin with respect
1973
+ to the received signal as perceived by the local PME.
1974
+ The value of 65535 is returned when the PME is Down or
1975
+ Initializing.
1976
+
1977
+ This object maps to the aPMESNRMgn attribute in Clause 30.
1978
+
1979
+ If a Clause 45 MDIO Interface is present, then this
1980
+ object maps to the 10P/2B RX SNR margin register.""",
1981
+ "reference" :
1982
+ """[802.3ah] 30.11.2.1.4, 45.2.1.16""",
1983
+ }, # column
1984
+ "efmCuPmePeerSnrMgn" : {
1985
+ "nodetype" : "column",
1986
+ "moduleName" : "EFM-CU-MIB",
1987
+ "oid" : "1.3.6.1.2.1.167.1.2.3.1.6",
1988
+ "status" : "current",
1989
+ "syntax" : {
1990
+ "type" : {
1991
+ "basetype" : "Integer32",
1992
+ "ranges" : [
1993
+ {
1994
+ "min" : "-127",
1995
+ "max" : "128"
1996
+ },
1997
+ {
1998
+ "min" : "65535",
1999
+ "max" : "65535"
2000
+ },
2001
+ ],
2002
+ "range" : {
2003
+ "min" : "-127",
2004
+ "max" : "65535"
2005
+ },
2006
+ },
2007
+ },
2008
+ "access" : "readonly",
2009
+ "units" : "dB",
2010
+ "description" :
2011
+ """The current SNR margin in dB with respect to the received
2012
+ signal, as perceived by the remote (link partner) PME.
2013
+ The value of 65535 is returned when the PME is Down or
2014
+ Initializing.
2015
+
2016
+ This object is irrelevant for the -R PME subtypes. The value
2017
+ of 65535 SHALL be returned in this case.
2018
+
2019
+ If a Clause 45 MDIO Interface is present, then this
2020
+ object maps to the 10P/2B link partner RX SNR margin
2021
+ register.""",
2022
+ "reference" :
2023
+ """[802.3ah] 45.2.1.17""",
2024
+ }, # column
2025
+ "efmCuPmeLineAtn" : {
2026
+ "nodetype" : "column",
2027
+ "moduleName" : "EFM-CU-MIB",
2028
+ "oid" : "1.3.6.1.2.1.167.1.2.3.1.7",
2029
+ "status" : "current",
2030
+ "syntax" : {
2031
+ "type" : {
2032
+ "basetype" : "Integer32",
2033
+ "ranges" : [
2034
+ {
2035
+ "min" : "-127",
2036
+ "max" : "128"
2037
+ },
2038
+ {
2039
+ "min" : "65535",
2040
+ "max" : "65535"
2041
+ },
2042
+ ],
2043
+ "range" : {
2044
+ "min" : "-127",
2045
+ "max" : "65535"
2046
+ },
2047
+ },
2048
+ },
2049
+ "access" : "readonly",
2050
+ "units" : "dB",
2051
+ "description" :
2052
+ """The current Line Attenuation in dB as perceived by the local
2053
+ PME.
2054
+
2055
+
2056
+
2057
+ The value of 65535 is returned when the PME is Down or
2058
+ Initializing.
2059
+
2060
+ If a Clause 45 MDIO Interface is present, then this
2061
+ object maps to the Line Attenuation register.""",
2062
+ "reference" :
2063
+ """[802.3ah] 45.2.1.18""",
2064
+ }, # column
2065
+ "efmCuPmePeerLineAtn" : {
2066
+ "nodetype" : "column",
2067
+ "moduleName" : "EFM-CU-MIB",
2068
+ "oid" : "1.3.6.1.2.1.167.1.2.3.1.8",
2069
+ "status" : "current",
2070
+ "syntax" : {
2071
+ "type" : {
2072
+ "basetype" : "Integer32",
2073
+ "ranges" : [
2074
+ {
2075
+ "min" : "-127",
2076
+ "max" : "128"
2077
+ },
2078
+ {
2079
+ "min" : "65535",
2080
+ "max" : "65535"
2081
+ },
2082
+ ],
2083
+ "range" : {
2084
+ "min" : "-127",
2085
+ "max" : "65535"
2086
+ },
2087
+ },
2088
+ },
2089
+ "access" : "readonly",
2090
+ "units" : "dB",
2091
+ "description" :
2092
+ """The current Line Attenuation in dB as perceived by the remote
2093
+ (link partner) PME.
2094
+ The value of 65535 is returned when the PME is Down or
2095
+ Initializing.
2096
+
2097
+ This object is irrelevant for the -R PME subtypes. The value
2098
+ of 65535 SHALL be returned in this case.
2099
+
2100
+ If a Clause 45 MDIO Interface is present, then this
2101
+ object maps to the 20P/2B link partner Line Attenuation
2102
+ register.""",
2103
+ "reference" :
2104
+ """[802.3ah] 45.2.1.19""",
2105
+ }, # column
2106
+ "efmCuPmeEquivalentLength" : {
2107
+ "nodetype" : "column",
2108
+ "moduleName" : "EFM-CU-MIB",
2109
+ "oid" : "1.3.6.1.2.1.167.1.2.3.1.9",
2110
+ "status" : "current",
2111
+ "syntax" : {
2112
+ "type" : {
2113
+ "basetype" : "Unsigned32",
2114
+ "ranges" : [
2115
+ {
2116
+ "min" : "0",
2117
+ "max" : "8192"
2118
+ },
2119
+ {
2120
+ "min" : "65535",
2121
+ "max" : "65535"
2122
+ },
2123
+ ],
2124
+ "range" : {
2125
+ "min" : "0",
2126
+ "max" : "65535"
2127
+ },
2128
+ },
2129
+ },
2130
+ "access" : "readonly",
2131
+ "units" : "m",
2132
+ "description" :
2133
+ """An estimate of the equivalent loop's physical length in
2134
+ meters, as perceived by the PME after the link is established.
2135
+ An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a
2136
+ perfect square root attenuation characteristic, without any
2137
+ bridged taps.
2138
+ The value of 65535 is returned if the link is Down or
2139
+ Initializing or the PME is unable to estimate the equivalent
2140
+ length.
2141
+
2142
+ For a 10BASE-TL PME, if a Clause 45 MDIO Interface to the PME
2143
+ is present, then this object maps to the 10P Electrical Length
2144
+ register.""",
2145
+ "reference" :
2146
+ """[802.3ah] 45.2.1.21""",
2147
+ }, # column
2148
+ "efmCuPmeTCCodingErrors" : {
2149
+ "nodetype" : "column",
2150
+ "moduleName" : "EFM-CU-MIB",
2151
+ "oid" : "1.3.6.1.2.1.167.1.2.3.1.10",
2152
+ "status" : "current",
2153
+ "syntax" : {
2154
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
2155
+ },
2156
+ "access" : "readonly",
2157
+ "description" :
2158
+ """The number of 64/65-octet encapsulation errors. This counter
2159
+ is incremented for each 64/65-octet encapsulation error
2160
+ detected by the 64/65-octet receive function.
2161
+
2162
+ This object maps to aTCCodingViolations attribute in
2163
+ Clause 30.
2164
+
2165
+ If a Clause 45 MDIO Interface to the PME TC is present, then
2166
+ this object maps to the TC coding violations register
2167
+ (see 45.2.6.12).
2168
+
2169
+ Discontinuities in the value of this counter can occur at
2170
+ re-initialization of the management system, and at other times
2171
+ as indicated by the value of ifCounterDiscontinuityTime,
2172
+ defined in IF-MIB.""",
2173
+ "reference" :
2174
+ """[802.3ah] 61.3.3.1, 30.11.2.1.5, 45.2.6.12""",
2175
+ }, # column
2176
+ "efmCuPmeTCCrcErrors" : {
2177
+ "nodetype" : "column",
2178
+ "moduleName" : "EFM-CU-MIB",
2179
+ "oid" : "1.3.6.1.2.1.167.1.2.3.1.11",
2180
+ "status" : "current",
2181
+ "syntax" : {
2182
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
2183
+ },
2184
+ "access" : "readonly",
2185
+ "description" :
2186
+ """The number of TC-CRC errors. This counter is incremented for
2187
+ each TC-CRC error detected by the 64/65-octet receive function
2188
+ (see 61.3.3.3 and Figure 61-19).
2189
+
2190
+ This object maps to aTCCRCErrors attribute in
2191
+ Clause 30.
2192
+
2193
+ If a Clause 45 MDIO Interface to the PME TC is present, then
2194
+ this object maps to the TC CRC error register
2195
+ (see 45.2.6.11).
2196
+
2197
+ Discontinuities in the value of this counter can occur at
2198
+ re-initialization of the management system, and at other times
2199
+ as indicated by the value of ifCounterDiscontinuityTime,
2200
+ defined in IF-MIB.""",
2201
+ "reference" :
2202
+ """[802.3ah] 61.3.3.3, 30.11.2.1.10, 45.2.6.11""",
2203
+ }, # column
2204
+ "efmCuPme2B" : {
2205
+ "nodetype" : "node",
2206
+ "moduleName" : "EFM-CU-MIB",
2207
+ "oid" : "1.3.6.1.2.1.167.1.2.5",
2208
+ }, # node
2209
+ "efmCuPme2BProfileTable" : {
2210
+ "nodetype" : "table",
2211
+ "moduleName" : "EFM-CU-MIB",
2212
+ "oid" : "1.3.6.1.2.1.167.1.2.5.2",
2213
+ "status" : "current",
2214
+ "description" :
2215
+ """This table supports definitions of administrative and
2216
+ operating profiles for 2BASE-TL PMEs.
2217
+ The first 14 entries in this table SHALL always be defined as
2218
+ follows (see 802.3ah Annex 63A):
2219
+ -------+-------+-------+-----+------+-------------+-----------
2220
+ Profile MinRate MaxRate Power Region Constellation Comment
2221
+ index (Kbps) (Kbps) (dBm)
2222
+ -------+-------+-------+-----+------+-------------+-----------
2223
+ 1 5696 5696 13.5 1 32-TCPAM default
2224
+ 2 3072 3072 13.5 1 32-TCPAM
2225
+ 3 2048 2048 13.5 1 16-TCPAM
2226
+ 4 1024 1024 13.5 1 16-TCPAM
2227
+ 5 704 704 13.5 1 16-TCPAM
2228
+ 6 512 512 13.5 1 16-TCPAM
2229
+ 7 5696 5696 14.5 2 32-TCPAM
2230
+ 8 3072 3072 14.5 2 32-TCPAM
2231
+ 9 2048 2048 14.5 2 16-TCPAM
2232
+ 10 1024 1024 13.5 2 16-TCPAM
2233
+ 11 704 704 13.5 2 16-TCPAM
2234
+ 12 512 512 13.5 2 16-TCPAM
2235
+ 13 192 5696 0 1 0 best effort
2236
+ 14 192 5696 0 2 0 best effort
2237
+ -------+-------+-------+-----+------+-------------+-----------
2238
+
2239
+ These default entries SHALL be created during agent
2240
+ initialization and MUST NOT be deleted.
2241
+
2242
+ Entries following the first 14 can be dynamically created and
2243
+ deleted to provide custom administrative (configuration)
2244
+ profiles and automatic operating profiles.
2245
+
2246
+ This table MUST be maintained in a persistent manner.""",
2247
+ "reference" :
2248
+ """[802.3ah] Annex 63A, 30.11.2.1.6""",
2249
+ }, # table
2250
+ "efmCuPme2BProfileEntry" : {
2251
+ "nodetype" : "row",
2252
+ "moduleName" : "EFM-CU-MIB",
2253
+ "oid" : "1.3.6.1.2.1.167.1.2.5.2.1",
2254
+ "create" : "true",
2255
+ "status" : "current",
2256
+ "linkage" : [
2257
+ "efmCuPme2BProfileIndex",
2258
+ ],
2259
+ "description" :
2260
+ """Each entry corresponds to a single 2BASE-TL PME profile.
2261
+ Each profile contains a set of parameters, used either for
2262
+ configuration or representation of a 2BASE-TL PME.
2263
+ In case a particular profile is referenced via the
2264
+ efmCuPmeAdminProfile object (or efmCuAdminProfile if
2265
+ efmCuPmeAdminProfile is zero), it represents the desired
2266
+ parameters for the 2BaseTL-O PME initialization.
2267
+ If a profile is referenced via an efmCuPmeOperProfile object,
2268
+ it represents the current operating parameters of an
2269
+ operational PME.
2270
+
2271
+ Profiles may be created/deleted using the row creation/
2272
+ deletion mechanism via efmCuPme2BProfileRowStatus. If an
2273
+ active entry is referenced, the entry MUST remain 'active'
2274
+ until all references are removed.
2275
+ Default entries MUST NOT be removed.""",
2276
+ }, # row
2277
+ "efmCuPme2BProfileIndex" : {
2278
+ "nodetype" : "column",
2279
+ "moduleName" : "EFM-CU-MIB",
2280
+ "oid" : "1.3.6.1.2.1.167.1.2.5.2.1.1",
2281
+ "status" : "current",
2282
+ "syntax" : {
2283
+ "type" : { "module" :"EFM-CU-MIB", "name" : "EfmProfileIndex"},
2284
+ },
2285
+ "access" : "noaccess",
2286
+ "description" :
2287
+ """2BASE-TL PME profile index.
2288
+ This object is the unique index associated with this profile.
2289
+ Entries in this table are referenced via efmCuAdminProfile or
2290
+ efmCuPmeAdminProfile objects.""",
2291
+ }, # column
2292
+ "efmCuPme2BProfileDescr" : {
2293
+ "nodetype" : "column",
2294
+ "moduleName" : "EFM-CU-MIB",
2295
+ "oid" : "1.3.6.1.2.1.167.1.2.5.2.1.2",
2296
+ "status" : "current",
2297
+ "syntax" : {
2298
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
2299
+ },
2300
+ "access" : "readwrite",
2301
+ "description" :
2302
+ """A textual string containing information about a 2BASE-TL PME
2303
+ profile. The string may include information about the data
2304
+ rate and spectral limitations of this particular profile.""",
2305
+ }, # column
2306
+ "efmCuPme2BRegion" : {
2307
+ "nodetype" : "column",
2308
+ "moduleName" : "EFM-CU-MIB",
2309
+ "oid" : "1.3.6.1.2.1.167.1.2.5.2.1.3",
2310
+ "status" : "current",
2311
+ "syntax" : {
2312
+ "type" : {
2313
+ "basetype" : "Enumeration",
2314
+ "region1" : {
2315
+ "nodetype" : "namednumber",
2316
+ "number" : "1"
2317
+ },
2318
+ "region2" : {
2319
+ "nodetype" : "namednumber",
2320
+ "number" : "2"
2321
+ },
2322
+ },
2323
+ },
2324
+ "access" : "readwrite",
2325
+ "description" :
2326
+ """Regional settings for a 2BASE-TL PME, as specified in the
2327
+ relevant Regional Annex of [G.991.2].
2328
+ Regional settings specify the Power Spectral Density (PSD)
2329
+ mask and the Power Back-Off (PBO) values, and place
2330
+ limitations on the max allowed data rate, power, and
2331
+ constellation.
2332
+
2333
+ Possible values for this object are:
2334
+ region1 - Annexes A and F (e.g., North America)
2335
+ region2 - Annexes B and G (e.g., Europe)
2336
+
2337
+ Annex A/B specify regional settings for data rates 192-2304
2338
+ Kbps using 16-TCPAM encoding.
2339
+ Annex F/G specify regional settings for rates 2320-3840 Kbps
2340
+ using 16-TCPAM encoding and 768-5696 Kbps using 32-TCPAM
2341
+ encoding.
2342
+
2343
+ If a Clause 45 MDIO Interface to the PME is present, then this
2344
+ object partially maps to the Region bits in the 2B general
2345
+ parameter register.""",
2346
+ "reference" :
2347
+ """[802.3ah] 45.2.1.42; [G.991.2] Annexes A, B, F and G""",
2348
+ }, # column
2349
+ "efmCuPme2BsMode" : {
2350
+ "nodetype" : "column",
2351
+ "moduleName" : "EFM-CU-MIB",
2352
+ "oid" : "1.3.6.1.2.1.167.1.2.5.2.1.4",
2353
+ "status" : "current",
2354
+ "syntax" : {
2355
+ "type" : { "module" :"EFM-CU-MIB", "name" : "EfmProfileIndexOrZero"},
2356
+ },
2357
+ "access" : "readwrite",
2358
+ "default" : "0",
2359
+ "description" :
2360
+ """Desired custom Spectral Mode for a 2BASE-TL PME. This object
2361
+
2362
+
2363
+
2364
+ is a pointer to an entry in efmCuPme2BsModeTable and a block
2365
+ of entries in efmCuPme2BRateReachTable, which together define
2366
+ (country-specific) reach-dependent rate limitations in
2367
+ addition to those defined by efmCuPme2BRegion.
2368
+
2369
+ The value of this object is the index of the referenced
2370
+ spectral mode.
2371
+ The value of zero (default) indicates that no specific
2372
+ spectral mode is applicable.
2373
+
2374
+ Attempts to set this object to a value that is not the value
2375
+ of the index for an active entry in the corresponding spectral
2376
+ mode table MUST be rejected.""",
2377
+ "reference" :
2378
+ """efmCuPme2BsModeTable, efmCuPme2BRateReachTable""",
2379
+ }, # column
2380
+ "efmCuPme2BMinDataRate" : {
2381
+ "nodetype" : "column",
2382
+ "moduleName" : "EFM-CU-MIB",
2383
+ "oid" : "1.3.6.1.2.1.167.1.2.5.2.1.5",
2384
+ "status" : "current",
2385
+ "syntax" : {
2386
+ "type" : {
2387
+ "basetype" : "Unsigned32",
2388
+ "ranges" : [
2389
+ {
2390
+ "min" : "192",
2391
+ "max" : "5696"
2392
+ },
2393
+ ],
2394
+ "range" : {
2395
+ "min" : "192",
2396
+ "max" : "5696"
2397
+ },
2398
+ },
2399
+ },
2400
+ "access" : "readwrite",
2401
+ "units" : "Kbps",
2402
+ "description" :
2403
+ """Minimum Data Rate for the 2BASE-TL PME.
2404
+ This object can take values of (n x 64)Kbps,
2405
+ where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM encoding.
2406
+
2407
+ The data rate of the 2BASE-TL PME is considered 'fixed' when
2408
+ the value of this object equals that of efmCuPme2BMaxDataRate.
2409
+ If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in
2410
+ the administrative profile, the data rate is considered
2411
+ 'adaptive', and SHALL be set to the maximum attainable rate
2412
+ not exceeding efmCuPme2BMaxDataRate, under the spectral
2413
+ limitations placed by the efmCuPme2BRegion and
2414
+ efmCuPme2BsMode.
2415
+
2416
+ Note that the current operational data rate of the PME is
2417
+ represented by the ifSpeed object of IF-MIB.
2418
+
2419
+ If a Clause 45 MDIO Interface to the PME is present, then this
2420
+ object maps to the Min Data Rate1 bits in the 2B PMD
2421
+ parameters register.
2422
+
2423
+ This object MUST be maintained in a persistent manner.""",
2424
+ "reference" :
2425
+ """[802.3ah] 45.2.1.43""",
2426
+ }, # column
2427
+ "efmCuPme2BMaxDataRate" : {
2428
+ "nodetype" : "column",
2429
+ "moduleName" : "EFM-CU-MIB",
2430
+ "oid" : "1.3.6.1.2.1.167.1.2.5.2.1.6",
2431
+ "status" : "current",
2432
+ "syntax" : {
2433
+ "type" : {
2434
+ "basetype" : "Unsigned32",
2435
+ "ranges" : [
2436
+ {
2437
+ "min" : "192",
2438
+ "max" : "5696"
2439
+ },
2440
+ ],
2441
+ "range" : {
2442
+ "min" : "192",
2443
+ "max" : "5696"
2444
+ },
2445
+ },
2446
+ },
2447
+ "access" : "readwrite",
2448
+ "units" : "Kbps",
2449
+ "description" :
2450
+ """Maximum Data Rate for the 2BASE-TL PME.
2451
+ This object can take values of (n x 64)Kbps,
2452
+ where n=3..60 for 16-TCPAM and n=12..89 for 32-TCPAM encoding.
2453
+
2454
+ The data rate of the 2BASE-TL PME is considered 'fixed' when
2455
+ the value of this object equals that of efmCuPme2BMinDataRate.
2456
+ If efmCuPme2BMinDataRate is less than efmCuPme2BMaxDataRate in
2457
+ the administrative profile, the data rate is considered
2458
+ 'adaptive', and SHALL be set to the maximum attainable rate
2459
+ not exceeding efmCuPme2BMaxDataRate, under the spectral
2460
+ limitations placed by the efmCuPme2BRegion and
2461
+ efmCuPme2BsMode.
2462
+
2463
+ Note that the current operational data rate of the PME is
2464
+ represented by the ifSpeed object of IF-MIB.
2465
+
2466
+ If a Clause 45 MDIO Interface to the PME is present, then this
2467
+ object maps to the Max Data Rate1 bits in the 2B PMD
2468
+ parameters register.
2469
+
2470
+ This object MUST be maintained in a persistent manner.""",
2471
+ "reference" :
2472
+ """[802.3ah] 45.2.1.43""",
2473
+ }, # column
2474
+ "efmCuPme2BPower" : {
2475
+ "nodetype" : "column",
2476
+ "moduleName" : "EFM-CU-MIB",
2477
+ "oid" : "1.3.6.1.2.1.167.1.2.5.2.1.7",
2478
+ "status" : "current",
2479
+ "syntax" : {
2480
+ "type" : {
2481
+ "basetype" : "Unsigned32",
2482
+ "ranges" : [
2483
+ {
2484
+ "min" : "0",
2485
+ "max" : "0"
2486
+ },
2487
+ {
2488
+ "min" : "10",
2489
+ "max" : "42"
2490
+ },
2491
+ ],
2492
+ "range" : {
2493
+ "min" : "0",
2494
+ "max" : "42"
2495
+ },
2496
+ },
2497
+ },
2498
+ "access" : "readwrite",
2499
+ "units" : "0.5 dBm",
2500
+ "description" :
2501
+ """Signal Transmit Power. Multiple of 0.5 dBm.
2502
+ The value of 0 in the administrative profile means that the
2503
+ signal transmit power is not fixed and SHALL be set to
2504
+ maximize the attainable rate, under the spectral limitations
2505
+ placed by the efmCuPme2BRegion and efmCuPme2BsMode.
2506
+
2507
+ If a Clause 45 MDIO Interface to the PME is present, then this
2508
+ object maps to the Power1 bits in the 2B PMD parameters
2509
+ register.""",
2510
+ "reference" :
2511
+ """[802.3ah] 45.2.1.43""",
2512
+ }, # column
2513
+ "efmCuPme2BConstellation" : {
2514
+ "nodetype" : "column",
2515
+ "moduleName" : "EFM-CU-MIB",
2516
+ "oid" : "1.3.6.1.2.1.167.1.2.5.2.1.8",
2517
+ "status" : "current",
2518
+ "syntax" : {
2519
+ "type" : {
2520
+ "basetype" : "Enumeration",
2521
+ "adaptive" : {
2522
+ "nodetype" : "namednumber",
2523
+ "number" : "0"
2524
+ },
2525
+ "tcpam16" : {
2526
+ "nodetype" : "namednumber",
2527
+ "number" : "1"
2528
+ },
2529
+ "tcpam32" : {
2530
+ "nodetype" : "namednumber",
2531
+ "number" : "2"
2532
+ },
2533
+ },
2534
+ },
2535
+ "access" : "readwrite",
2536
+ "description" :
2537
+ """TCPAM Constellation of the 2BASE-TL PME.
2538
+ The possible values are:
2539
+ adaptive(0) - either 16- or 32-TCPAM
2540
+ tcpam16(1) - 16-TCPAM
2541
+ tcpam32(2) - 32-TCPAM
2542
+
2543
+ The value of adaptive(0) in the administrative profile means
2544
+ that the constellation is not fixed and SHALL be set to
2545
+ maximize the attainable rate, under the spectral limitations
2546
+ placed by the efmCuPme2BRegion and efmCuPme2BsMode.
2547
+
2548
+ If a Clause 45 MDIO Interface to the PME is present, then this
2549
+ object maps to the Constellation1 bits in the 2B general
2550
+ parameter register.""",
2551
+ "reference" :
2552
+ """[802.3ah] 45.2.1.43""",
2553
+ }, # column
2554
+ "efmCuPme2BProfileRowStatus" : {
2555
+ "nodetype" : "column",
2556
+ "moduleName" : "EFM-CU-MIB",
2557
+ "oid" : "1.3.6.1.2.1.167.1.2.5.2.1.9",
2558
+ "status" : "current",
2559
+ "syntax" : {
2560
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
2561
+ },
2562
+ "access" : "readwrite",
2563
+ "description" :
2564
+ """This object controls the creation, modification, or deletion
2565
+ of the associated entry in the efmCuPme2BProfileTable per the
2566
+ semantics of RowStatus.
2567
+
2568
+ If an 'active' entry is referenced via efmCuAdminProfile or
2569
+ efmCuPmeAdminProfile instance(s), the entry MUST remain
2570
+ 'active'.
2571
+
2572
+ An 'active' entry SHALL NOT be modified. In order to modify
2573
+ an existing entry, it MUST be taken out of service (by setting
2574
+ this object to 'notInService'), modified, and set 'active'
2575
+ again.""",
2576
+ }, # column
2577
+ "efmCuPme2BsModeTable" : {
2578
+ "nodetype" : "table",
2579
+ "moduleName" : "EFM-CU-MIB",
2580
+ "oid" : "1.3.6.1.2.1.167.1.2.5.3",
2581
+ "status" : "current",
2582
+ "description" :
2583
+ """This table, together with efmCu2BReachRateTable, supports
2584
+ definition of administrative custom spectral modes for
2585
+ 2BASE-TL PMEs, describing spectral limitations in addition to
2586
+ those specified by efmCuPme2BRegion.
2587
+
2588
+ In some countries, spectral regulations (e.g., UK ANFP) limit
2589
+ the length of the loops for certain data rates. This table
2590
+ allows these country-specific limitations to be specified.
2591
+
2592
+ Entries in this table referenced by the efmCuPme2BsMode
2593
+ MUST NOT be deleted until all the active references are
2594
+ removed.
2595
+
2596
+ This table MUST be maintained in a persistent manner.""",
2597
+ "reference" :
2598
+ """efmCu2BReachRateTable""",
2599
+ }, # table
2600
+ "efmCuPme2BsModeEntry" : {
2601
+ "nodetype" : "row",
2602
+ "moduleName" : "EFM-CU-MIB",
2603
+ "oid" : "1.3.6.1.2.1.167.1.2.5.3.1",
2604
+ "create" : "true",
2605
+ "status" : "current",
2606
+ "linkage" : [
2607
+ "efmCuPme2BsModeIndex",
2608
+ ],
2609
+ "description" :
2610
+ """Each entry specifies a spectral mode description and its
2611
+ index, which is used to reference corresponding entries in the
2612
+ efmCu2BReachRateTable.
2613
+
2614
+ Entries may be created/deleted using the row creation/
2615
+ deletion mechanism via efmCuPme2BsModeRowStatus.""",
2616
+ }, # row
2617
+ "efmCuPme2BsModeIndex" : {
2618
+ "nodetype" : "column",
2619
+ "moduleName" : "EFM-CU-MIB",
2620
+ "oid" : "1.3.6.1.2.1.167.1.2.5.3.1.1",
2621
+ "status" : "current",
2622
+ "syntax" : {
2623
+ "type" : { "module" :"EFM-CU-MIB", "name" : "EfmProfileIndex"},
2624
+ },
2625
+ "access" : "noaccess",
2626
+ "description" :
2627
+ """2BASE-TL PME Spectral Mode index.
2628
+ This object is the unique index associated with this spectral
2629
+ mode.
2630
+ Entries in this table are referenced via the efmCuPme2BsMode
2631
+ object.""",
2632
+ }, # column
2633
+ "efmCuPme2BsModeDescr" : {
2634
+ "nodetype" : "column",
2635
+ "moduleName" : "EFM-CU-MIB",
2636
+ "oid" : "1.3.6.1.2.1.167.1.2.5.3.1.2",
2637
+ "status" : "current",
2638
+ "syntax" : {
2639
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
2640
+ },
2641
+ "access" : "readwrite",
2642
+ "description" :
2643
+ """A textual string containing information about a 2BASE-TL PME
2644
+ spectral mode. The string may include information about
2645
+ corresponding (country-specific) spectral regulations
2646
+ and rate/reach limitations of this particular spectral mode.""",
2647
+ }, # column
2648
+ "efmCuPme2BsModeRowStatus" : {
2649
+ "nodetype" : "column",
2650
+ "moduleName" : "EFM-CU-MIB",
2651
+ "oid" : "1.3.6.1.2.1.167.1.2.5.3.1.3",
2652
+ "status" : "current",
2653
+ "syntax" : {
2654
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
2655
+ },
2656
+ "access" : "readwrite",
2657
+ "description" :
2658
+ """This object controls creation, modification, or deletion of
2659
+ the associated entry in efmCuPme2BsModeTable per the semantics
2660
+ of RowStatus.
2661
+
2662
+ If an 'active' entry is referenced via efmCuPme2BsMode
2663
+ instance(s), the entry MUST remain 'active'.
2664
+
2665
+ An 'active' entry SHALL NOT be modified. In order to modify
2666
+ an existing entry, it MUST be taken out of service (by setting
2667
+ this object to 'notInService'), modified, and set 'active'
2668
+ again.""",
2669
+ }, # column
2670
+ "efmCuPme2BReachRateTable" : {
2671
+ "nodetype" : "table",
2672
+ "moduleName" : "EFM-CU-MIB",
2673
+ "oid" : "1.3.6.1.2.1.167.1.2.5.4",
2674
+ "status" : "current",
2675
+ "description" :
2676
+ """This table supports the definition of administrative custom
2677
+ spectral modes for 2BASE-TL PMEs, providing spectral
2678
+ limitations in addition to those specified by
2679
+ efmCuPme2BRegion.
2680
+
2681
+
2682
+
2683
+
2684
+ The spectral regulations in some countries (e.g., UK ANFP)
2685
+ limit the length of the loops for certain data rates.
2686
+ This table allows these country-specific limitations to be
2687
+ specified.
2688
+
2689
+ Below is an example of this table for [ANFP]:
2690
+ ----------+-------+-------
2691
+ Equivalent MaxRate MaxRate
2692
+ Length PAM16 PAM32
2693
+ (m) (Kbps) (Kbps)
2694
+ ----------+-------+-------
2695
+ 975 2304 5696
2696
+ 1125 2304 5504
2697
+ 1275 2304 5120
2698
+ 1350 2304 4864
2699
+ 1425 2304 4544
2700
+ 1500 2304 4288
2701
+ 1575 2304 3968
2702
+ 1650 2304 3776
2703
+ 1725 2304 3520
2704
+ 1800 2304 3264
2705
+ 1875 2304 3072
2706
+ 1950 2048 2688
2707
+ 2100 1792 2368
2708
+ 2250 1536 0
2709
+ 2400 1408 0
2710
+ 2550 1280 0
2711
+ 2775 1152 0
2712
+ 2925 1152 0
2713
+ 3150 1088 0
2714
+ 3375 1024 0
2715
+ ----------+-------+-------
2716
+
2717
+ Entries in this table referenced by an efmCuPme2BsMode
2718
+ instance MUST NOT be deleted.
2719
+
2720
+ This table MUST be maintained in a persistent manner.""",
2721
+ "reference" :
2722
+ """[ANFP]""",
2723
+ }, # table
2724
+ "efmCuPme2BReachRateEntry" : {
2725
+ "nodetype" : "row",
2726
+ "moduleName" : "EFM-CU-MIB",
2727
+ "oid" : "1.3.6.1.2.1.167.1.2.5.4.1",
2728
+ "create" : "true",
2729
+ "status" : "current",
2730
+ "linkage" : [
2731
+ "efmCuPme2BsModeIndex",
2732
+ "efmCuPme2BReachRateIndex",
2733
+ ],
2734
+ "description" :
2735
+ """Each entry specifies maximum 2BASE-TL PME data rates
2736
+ allowed for a certain equivalent loop length, when using
2737
+
2738
+
2739
+
2740
+ 16-TCPAM or 32-TCPAM encoding.
2741
+
2742
+ When a 2BASE-TL PME is initialized, its data rate MUST NOT
2743
+ exceed one of the following limitations:
2744
+ - the value of efmCuPme2BMaxDataRate
2745
+ - maximum data rate allowed by efmCuPme2BRegion and
2746
+ efmCuPme2BPower
2747
+ - maximum data rate for a given encoding specified in the
2748
+ efmCuPme2BsModeEntry, corresponding to the equivalent loop
2749
+ length, estimated by the PME
2750
+
2751
+ It is RECOMMENDED that the efmCuPme2BEquivalentLength values
2752
+ are assigned in increasing order, starting from the minimum
2753
+ value.
2754
+
2755
+ Entries may be created/deleted using the row creation/
2756
+ deletion mechanism via efmCuPme2ReachRateRowStatus.""",
2757
+ }, # row
2758
+ "efmCuPme2BReachRateIndex" : {
2759
+ "nodetype" : "column",
2760
+ "moduleName" : "EFM-CU-MIB",
2761
+ "oid" : "1.3.6.1.2.1.167.1.2.5.4.1.1",
2762
+ "status" : "current",
2763
+ "syntax" : {
2764
+ "type" : { "module" :"EFM-CU-MIB", "name" : "EfmProfileIndex"},
2765
+ },
2766
+ "access" : "noaccess",
2767
+ "description" :
2768
+ """2BASE-TL custom spectral mode Reach-Rate table index.
2769
+ This object is the unique index associated with each entry.""",
2770
+ }, # column
2771
+ "efmCuPme2BEquivalentLength" : {
2772
+ "nodetype" : "column",
2773
+ "moduleName" : "EFM-CU-MIB",
2774
+ "oid" : "1.3.6.1.2.1.167.1.2.5.4.1.2",
2775
+ "status" : "current",
2776
+ "syntax" : {
2777
+ "type" : {
2778
+ "basetype" : "Unsigned32",
2779
+ "ranges" : [
2780
+ {
2781
+ "min" : "0",
2782
+ "max" : "8192"
2783
+ },
2784
+ ],
2785
+ "range" : {
2786
+ "min" : "0",
2787
+ "max" : "8192"
2788
+ },
2789
+ },
2790
+ },
2791
+ "access" : "readwrite",
2792
+ "units" : "m",
2793
+ "description" :
2794
+ """Maximum allowed equivalent loop's physical length in meters
2795
+ for the specified data rates.
2796
+ An equivalent loop is a hypothetical 26AWG (0.4mm) loop with a
2797
+ perfect square root attenuation characteristic, without any
2798
+
2799
+
2800
+
2801
+ bridged taps.""",
2802
+ }, # column
2803
+ "efmCuPme2BMaxDataRatePam16" : {
2804
+ "nodetype" : "column",
2805
+ "moduleName" : "EFM-CU-MIB",
2806
+ "oid" : "1.3.6.1.2.1.167.1.2.5.4.1.3",
2807
+ "status" : "current",
2808
+ "syntax" : {
2809
+ "type" : {
2810
+ "basetype" : "Unsigned32",
2811
+ "ranges" : [
2812
+ {
2813
+ "min" : "0",
2814
+ "max" : "0"
2815
+ },
2816
+ {
2817
+ "min" : "192",
2818
+ "max" : "5696"
2819
+ },
2820
+ ],
2821
+ "range" : {
2822
+ "min" : "0",
2823
+ "max" : "5696"
2824
+ },
2825
+ },
2826
+ },
2827
+ "access" : "readwrite",
2828
+ "units" : "Kbps",
2829
+ "description" :
2830
+ """Maximum data rate for a 2BASE-TL PME at the specified
2831
+ equivalent loop's length using TC-PAM16 encoding.
2832
+ The value of zero means that TC-PAM16 encoding should not be
2833
+ used at this distance.""",
2834
+ }, # column
2835
+ "efmCuPme2BMaxDataRatePam32" : {
2836
+ "nodetype" : "column",
2837
+ "moduleName" : "EFM-CU-MIB",
2838
+ "oid" : "1.3.6.1.2.1.167.1.2.5.4.1.4",
2839
+ "status" : "current",
2840
+ "syntax" : {
2841
+ "type" : {
2842
+ "basetype" : "Unsigned32",
2843
+ "ranges" : [
2844
+ {
2845
+ "min" : "0",
2846
+ "max" : "0"
2847
+ },
2848
+ {
2849
+ "min" : "192",
2850
+ "max" : "5696"
2851
+ },
2852
+ ],
2853
+ "range" : {
2854
+ "min" : "0",
2855
+ "max" : "5696"
2856
+ },
2857
+ },
2858
+ },
2859
+ "access" : "readwrite",
2860
+ "units" : "Kbps",
2861
+ "description" :
2862
+ """Maximum data rate for a 2BASE-TL PME at the specified
2863
+ equivalent loop's length using TC-PAM32 encoding.
2864
+ The value of zero means that TC-PAM32 encoding should not be
2865
+ used at this distance.""",
2866
+ }, # column
2867
+ "efmCuPme2BReachRateRowStatus" : {
2868
+ "nodetype" : "column",
2869
+ "moduleName" : "EFM-CU-MIB",
2870
+ "oid" : "1.3.6.1.2.1.167.1.2.5.4.1.5",
2871
+ "status" : "current",
2872
+ "syntax" : {
2873
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
2874
+ },
2875
+ "access" : "readwrite",
2876
+ "description" :
2877
+ """This object controls the creation, modification, or deletion
2878
+ of the associated entry in the efmCuPme2BReachRateTable per
2879
+ the semantics of RowStatus.
2880
+
2881
+ If an 'active' entry is referenced via efmCuPme2BsMode
2882
+ instance(s), the entry MUST remain 'active'.
2883
+
2884
+ An 'active' entry SHALL NOT be modified. In order to modify
2885
+ an existing entry, it MUST be taken out of service (by setting
2886
+ this object to 'notInService'), modified, and set 'active'
2887
+ again.""",
2888
+ }, # column
2889
+ "efmCuPme10P" : {
2890
+ "nodetype" : "node",
2891
+ "moduleName" : "EFM-CU-MIB",
2892
+ "oid" : "1.3.6.1.2.1.167.1.2.6",
2893
+ }, # node
2894
+ "efmCuPme10PProfileTable" : {
2895
+ "nodetype" : "table",
2896
+ "moduleName" : "EFM-CU-MIB",
2897
+ "oid" : "1.3.6.1.2.1.167.1.2.6.1",
2898
+ "status" : "current",
2899
+ "description" :
2900
+ """This table supports definitions of configuration profiles for
2901
+ 10PASS-TS PMEs.
2902
+ The first 22 entries in this table SHALL always be defined as
2903
+ follows (see 802.3ah Annex 62B.3, table 62B-1):
2904
+ -------+--------+----+---------+-----+-----+---------------
2905
+ Profile Bandplan UPBO BandNotch DRate URate Comment
2906
+ Index PSDMask# p# p# p# p#
2907
+ -------+--------+----+---------+-----+-----+---------------
2908
+ 1 1 3 2,6,10,11 20 20 default profile
2909
+ 2 13 5 0 20 20
2910
+ 3 1 1 0 20 20
2911
+ 4 16 0 0 100 100
2912
+ 5 16 0 0 70 50
2913
+ 6 6 0 0 50 10
2914
+ 7 17 0 0 30 30
2915
+ 8 8 0 0 30 5
2916
+ 9 4 0 0 25 25
2917
+ 10 4 0 0 15 15
2918
+ 11 23 0 0 10 10
2919
+ 12 23 0 0 5 5
2920
+ 13 16 0 2,5,9,11 100 100
2921
+ 14 16 0 2,5,9,11 70 50
2922
+ 15 6 0 2,6,10,11 50 10
2923
+ 16 17 0 2,5,9,11 30 30
2924
+ 17 8 0 2,6,10,11 30 5
2925
+ 18 4 0 2,6,10,11 25 25
2926
+ 19 4 0 2,6,10,11 15 15
2927
+ 20 23 0 2,5,9,11 10 10
2928
+ 21 23 0 2,5,9,11 5 5
2929
+ 22 30 0 0 200 50
2930
+ -------+--------+----+---------+-----+-----+---------------
2931
+
2932
+ These default entries SHALL be created during agent
2933
+ initialization and MUST NOT be deleted.
2934
+
2935
+ Entries following the first 22 can be dynamically created and
2936
+ deleted to provide custom administrative (configuration)
2937
+ profiles and automatic operating profiles.
2938
+
2939
+ This table MUST be maintained in a persistent manner.""",
2940
+ "reference" :
2941
+ """[802.3ah] Annex 62B.3, 30.11.2.1.6""",
2942
+ }, # table
2943
+ "efmCuPme10PProfileEntry" : {
2944
+ "nodetype" : "row",
2945
+ "moduleName" : "EFM-CU-MIB",
2946
+ "oid" : "1.3.6.1.2.1.167.1.2.6.1.1",
2947
+ "create" : "true",
2948
+ "status" : "current",
2949
+ "linkage" : [
2950
+ "efmCuPme10PProfileIndex",
2951
+ ],
2952
+ "description" :
2953
+ """Each entry corresponds to a single 10PASS-TS PME profile.
2954
+
2955
+ Each profile contains a set of parameters, used either for
2956
+ configuration or representation of a 10PASS-TS PME.
2957
+ In case a particular profile is referenced via the
2958
+ efmCuPmeAdminProfile object (or efmCuAdminProfile if
2959
+ efmCuPmeAdminProfile is zero), it represents the desired
2960
+ parameters for the 10PassTS-O PME initialization.
2961
+ If a profile is referenced via an efmCuPmeOperProfile object,
2962
+ it represents the current operating parameters of the PME.
2963
+
2964
+ Profiles may be created/deleted using the row creation/
2965
+ deletion mechanism via efmCuPme10PProfileRowStatus. If an
2966
+ 'active' entry is referenced, the entry MUST remain 'active'
2967
+ until all references are removed.
2968
+ Default entries MUST NOT be removed.""",
2969
+ }, # row
2970
+ "efmCuPme10PProfileIndex" : {
2971
+ "nodetype" : "column",
2972
+ "moduleName" : "EFM-CU-MIB",
2973
+ "oid" : "1.3.6.1.2.1.167.1.2.6.1.1.1",
2974
+ "status" : "current",
2975
+ "syntax" : {
2976
+ "type" : { "module" :"EFM-CU-MIB", "name" : "EfmProfileIndex"},
2977
+ },
2978
+ "access" : "noaccess",
2979
+ "description" :
2980
+ """10PASS-TS PME profile index.
2981
+ This object is the unique index associated with this profile.
2982
+ Entries in this table are referenced via efmCuAdminProfile or
2983
+ efmCuPmeAdminProfile.""",
2984
+ }, # column
2985
+ "efmCuPme10PProfileDescr" : {
2986
+ "nodetype" : "column",
2987
+ "moduleName" : "EFM-CU-MIB",
2988
+ "oid" : "1.3.6.1.2.1.167.1.2.6.1.1.2",
2989
+ "status" : "current",
2990
+ "syntax" : {
2991
+ "type" : { "module" :"SNMP-FRAMEWORK-MIB", "name" : "SnmpAdminString"},
2992
+ },
2993
+ "access" : "readwrite",
2994
+ "description" :
2995
+ """A textual string containing information about a 10PASS-TS PME
2996
+ profile. The string may include information about data rate
2997
+ and spectral limitations of this particular profile.""",
2998
+ }, # column
2999
+ "efmCuPme10PBandplanPSDMskProfile" : {
3000
+ "nodetype" : "column",
3001
+ "moduleName" : "EFM-CU-MIB",
3002
+ "oid" : "1.3.6.1.2.1.167.1.2.6.1.1.3",
3003
+ "status" : "current",
3004
+ "syntax" : {
3005
+ "type" : {
3006
+ "basetype" : "Enumeration",
3007
+ "profile1" : {
3008
+ "nodetype" : "namednumber",
3009
+ "number" : "1"
3010
+ },
3011
+ "profile2" : {
3012
+ "nodetype" : "namednumber",
3013
+ "number" : "2"
3014
+ },
3015
+ "profile3" : {
3016
+ "nodetype" : "namednumber",
3017
+ "number" : "3"
3018
+ },
3019
+ "profile4" : {
3020
+ "nodetype" : "namednumber",
3021
+ "number" : "4"
3022
+ },
3023
+ "profile5" : {
3024
+ "nodetype" : "namednumber",
3025
+ "number" : "5"
3026
+ },
3027
+ "profile6" : {
3028
+ "nodetype" : "namednumber",
3029
+ "number" : "6"
3030
+ },
3031
+ "profile7" : {
3032
+ "nodetype" : "namednumber",
3033
+ "number" : "7"
3034
+ },
3035
+ "profile8" : {
3036
+ "nodetype" : "namednumber",
3037
+ "number" : "8"
3038
+ },
3039
+ "profile9" : {
3040
+ "nodetype" : "namednumber",
3041
+ "number" : "9"
3042
+ },
3043
+ "profile10" : {
3044
+ "nodetype" : "namednumber",
3045
+ "number" : "10"
3046
+ },
3047
+ "profile11" : {
3048
+ "nodetype" : "namednumber",
3049
+ "number" : "11"
3050
+ },
3051
+ "profile12" : {
3052
+ "nodetype" : "namednumber",
3053
+ "number" : "12"
3054
+ },
3055
+ "profile13" : {
3056
+ "nodetype" : "namednumber",
3057
+ "number" : "13"
3058
+ },
3059
+ "profile14" : {
3060
+ "nodetype" : "namednumber",
3061
+ "number" : "14"
3062
+ },
3063
+ "profile15" : {
3064
+ "nodetype" : "namednumber",
3065
+ "number" : "15"
3066
+ },
3067
+ "profile16" : {
3068
+ "nodetype" : "namednumber",
3069
+ "number" : "16"
3070
+ },
3071
+ "profile17" : {
3072
+ "nodetype" : "namednumber",
3073
+ "number" : "17"
3074
+ },
3075
+ "profile18" : {
3076
+ "nodetype" : "namednumber",
3077
+ "number" : "18"
3078
+ },
3079
+ "profile19" : {
3080
+ "nodetype" : "namednumber",
3081
+ "number" : "19"
3082
+ },
3083
+ "profile20" : {
3084
+ "nodetype" : "namednumber",
3085
+ "number" : "20"
3086
+ },
3087
+ "profile21" : {
3088
+ "nodetype" : "namednumber",
3089
+ "number" : "21"
3090
+ },
3091
+ "profile22" : {
3092
+ "nodetype" : "namednumber",
3093
+ "number" : "22"
3094
+ },
3095
+ "profile23" : {
3096
+ "nodetype" : "namednumber",
3097
+ "number" : "23"
3098
+ },
3099
+ "profile24" : {
3100
+ "nodetype" : "namednumber",
3101
+ "number" : "24"
3102
+ },
3103
+ "profile25" : {
3104
+ "nodetype" : "namednumber",
3105
+ "number" : "25"
3106
+ },
3107
+ "profile26" : {
3108
+ "nodetype" : "namednumber",
3109
+ "number" : "26"
3110
+ },
3111
+ "profile27" : {
3112
+ "nodetype" : "namednumber",
3113
+ "number" : "27"
3114
+ },
3115
+ "profile28" : {
3116
+ "nodetype" : "namednumber",
3117
+ "number" : "28"
3118
+ },
3119
+ "profile29" : {
3120
+ "nodetype" : "namednumber",
3121
+ "number" : "29"
3122
+ },
3123
+ "profile30" : {
3124
+ "nodetype" : "namednumber",
3125
+ "number" : "30"
3126
+ },
3127
+ },
3128
+ },
3129
+ "access" : "readwrite",
3130
+ "description" :
3131
+ """The 10PASS-TS PME Bandplan and PSD Mask Profile, as specified
3132
+ in 802.3ah Annex 62A, table 62A-1. Possible values are:
3133
+ --------------+------------------------+------------+--------
3134
+ Profile Name PSD Mask Bands G.993.1
3135
+ 0/1/2/3/4/5 Bandplan
3136
+ --------------+------------------------+------------+--------
3137
+ profile1(1) T1.424 FTTCab.M1 x/D/U/D/U A
3138
+ profile2(2) T1.424 FTTEx.M1 x/D/U/D/U A
3139
+ profile3(3) T1.424 FTTCab.M2 x/D/U/D/U A
3140
+ profile4(4) T1.424 FTTEx.M2 x/D/U/D/U A
3141
+ profile5(5) T1.424 FTTCab.M1 D/D/U/D/U A
3142
+ profile6(6) T1.424 FTTEx.M1 D/D/U/D/U A
3143
+ profile7(7) T1.424 FTTCab.M2 D/D/U/D/U A
3144
+ profile8(8) T1.424 FTTEx.M2 D/D/U/D/U A
3145
+ profile9(9) T1.424 FTTCab.M1 U/D/U/D/x A
3146
+ profile10(10) T1.424 FTTEx.M1 U/D/U/D/x A
3147
+ profile11(11) T1.424 FTTCab.M2 U/D/U/D/x A
3148
+ profile12(12) T1.424 FTTEx.M2 U/D/U/D/x A
3149
+ profile13(13) TS 101 270-1 Pcab.M1.A x/D/U/D/U B
3150
+ profile14(14) TS 101 270-1 Pcab.M1.B x/D/U/D/U B
3151
+ profile15(15) TS 101 270-1 Pex.P1.M1 x/D/U/D/U B
3152
+ profile16(16) TS 101 270-1 Pex.P2.M1 x/D/U/D/U B
3153
+ profile17(17) TS 101 270-1 Pcab.M2 x/D/U/D/U B
3154
+ profile18(18) TS 101 270-1 Pex.P1.M2 x/D/U/D/U B
3155
+ profile19(19) TS 101 270-1 Pex.P2.M2 x/D/U/D/U B
3156
+ profile20(20) TS 101 270-1 Pcab.M1.A U/D/U/D/x B
3157
+ profile21(21) TS 101 270-1 Pcab.M1.B U/D/U/D/x B
3158
+ profile22(22) TS 101 270-1 Pex.P1.M1 U/D/U/D/x B
3159
+ profile23(23) TS 101 270-1 Pex.P2.M1 U/D/U/D/x B
3160
+ profile24(24) TS 101 270-1 Pcab.M2 U/D/U/D/x B
3161
+ profile25(25) TS 101 270-1 Pex.P1.M2 U/D/U/D/x B
3162
+ profile26(26) TS 101 270-1 Pex.P2.M2 U/D/U/D/x B
3163
+ profile27(27) G.993.1 F.1.2.1 x/D/U/D/U Annex F
3164
+ profile28(28) G.993.1 F.1.2.2 x/D/U/D/U Annex F
3165
+ profile29(29) G.993.1 F.1.2.3 x/D/U/D/U Annex F
3166
+ profile30(30) T1.424 FTTCab.M1 (ext.) x/D/U/D/U/D Annex A
3167
+ --------------+------------------------+------------+--------""",
3168
+ "reference" :
3169
+ """[802.3ah] Annex 62A""",
3170
+ }, # column
3171
+ "efmCuPme10PUPBOReferenceProfile" : {
3172
+ "nodetype" : "column",
3173
+ "moduleName" : "EFM-CU-MIB",
3174
+ "oid" : "1.3.6.1.2.1.167.1.2.6.1.1.4",
3175
+ "status" : "current",
3176
+ "syntax" : {
3177
+ "type" : {
3178
+ "basetype" : "Enumeration",
3179
+ "profile0" : {
3180
+ "nodetype" : "namednumber",
3181
+ "number" : "0"
3182
+ },
3183
+ "profile1" : {
3184
+ "nodetype" : "namednumber",
3185
+ "number" : "1"
3186
+ },
3187
+ "profile2" : {
3188
+ "nodetype" : "namednumber",
3189
+ "number" : "2"
3190
+ },
3191
+ "profile3" : {
3192
+ "nodetype" : "namednumber",
3193
+ "number" : "3"
3194
+ },
3195
+ "profile4" : {
3196
+ "nodetype" : "namednumber",
3197
+ "number" : "4"
3198
+ },
3199
+ "profile5" : {
3200
+ "nodetype" : "namednumber",
3201
+ "number" : "5"
3202
+ },
3203
+ "profile6" : {
3204
+ "nodetype" : "namednumber",
3205
+ "number" : "6"
3206
+ },
3207
+ "profile7" : {
3208
+ "nodetype" : "namednumber",
3209
+ "number" : "7"
3210
+ },
3211
+ "profile8" : {
3212
+ "nodetype" : "namednumber",
3213
+ "number" : "8"
3214
+ },
3215
+ "profile9" : {
3216
+ "nodetype" : "namednumber",
3217
+ "number" : "9"
3218
+ },
3219
+ },
3220
+ },
3221
+ "access" : "readwrite",
3222
+ "description" :
3223
+ """The 10PASS-TS PME Upstream Power Back-Off (UPBO) Reference
3224
+ PSD Profile, as specified in 802.3 Annex 62A, table 62A-3.
3225
+ Possible values are:
3226
+ ------------+-----------------------------
3227
+ Profile Name Reference PSD
3228
+ ------------+-----------------------------
3229
+ profile0(0) no profile
3230
+ profile1(1) T1.424 Noise A M1
3231
+ profile2(2) T1.424 Noise A M2
3232
+ profile3(3) T1.424 Noise F M1
3233
+ profile4(4) T1.424 Noise F M2
3234
+ profile5(5) TS 101 270-1 Noise A&B
3235
+ profile6(6) TS 101 270-1 Noise C
3236
+ profile7(7) TS 101 270-1 Noise D
3237
+ profile8(8) TS 101 270-1 Noise E
3238
+ profile9(9) TS 101 270-1 Noise F
3239
+ ------------+-----------------------------""",
3240
+ "reference" :
3241
+ """[802.3ah] Annex 62A.3.5""",
3242
+ }, # column
3243
+ "efmCuPme10PBandNotchProfiles" : {
3244
+ "nodetype" : "column",
3245
+ "moduleName" : "EFM-CU-MIB",
3246
+ "oid" : "1.3.6.1.2.1.167.1.2.6.1.1.5",
3247
+ "status" : "current",
3248
+ "syntax" : {
3249
+ "type" : {
3250
+ "basetype" : "Bits",
3251
+ "profile0" : {
3252
+ "nodetype" : "namednumber",
3253
+ "number" : "0"
3254
+ },
3255
+ "profile1" : {
3256
+ "nodetype" : "namednumber",
3257
+ "number" : "1"
3258
+ },
3259
+ "profile2" : {
3260
+ "nodetype" : "namednumber",
3261
+ "number" : "2"
3262
+ },
3263
+ "profile3" : {
3264
+ "nodetype" : "namednumber",
3265
+ "number" : "3"
3266
+ },
3267
+ "profile4" : {
3268
+ "nodetype" : "namednumber",
3269
+ "number" : "4"
3270
+ },
3271
+ "profile5" : {
3272
+ "nodetype" : "namednumber",
3273
+ "number" : "5"
3274
+ },
3275
+ "profile6" : {
3276
+ "nodetype" : "namednumber",
3277
+ "number" : "6"
3278
+ },
3279
+ "profile7" : {
3280
+ "nodetype" : "namednumber",
3281
+ "number" : "7"
3282
+ },
3283
+ "profile8" : {
3284
+ "nodetype" : "namednumber",
3285
+ "number" : "8"
3286
+ },
3287
+ "profile9" : {
3288
+ "nodetype" : "namednumber",
3289
+ "number" : "9"
3290
+ },
3291
+ "profile10" : {
3292
+ "nodetype" : "namednumber",
3293
+ "number" : "10"
3294
+ },
3295
+ "profile11" : {
3296
+ "nodetype" : "namednumber",
3297
+ "number" : "11"
3298
+ },
3299
+ },
3300
+ },
3301
+ "access" : "readwrite",
3302
+ "description" :
3303
+ """The 10PASS-TS PME Egress Control Band Notch Profile bitmap,
3304
+ as specified in 802.3 Annex 62A, table 62A-4. Possible values
3305
+ are:
3306
+ --------------+--------+------+------------+------+------
3307
+ Profile Name G.991.3 T1.424 TS 101 270-1 StartF EndF
3308
+ table table table (MHz) (MHz)
3309
+ --------------+--------+------+------------+------+------
3310
+ profile0(0) no profile
3311
+ profile1(1) F-5 #01 - - 1.810 1.825
3312
+ profile2(2) 6-2 15-1 17 1.810 2.000
3313
+ profile3(3) F-5 #02 - - 1.907 1.912
3314
+ profile4(4) F-5 #03 - - 3.500 3.575
3315
+ profile5(5) 6-2 - 17 3.500 3.800
3316
+ profile6(6) - 15-1 - 3.500 4.000
3317
+ profile7(7) F-5 #04 - - 3.747 3.754
3318
+ profile8(8) F-5 #05 - - 3.791 3.805
3319
+ profile9(9) 6-2 - 17 7.000 7.100
3320
+ profile10(10) F-5 #06 15-1 - 7.000 7.300
3321
+ profile11(11) 6-2 15-1 1 10.100 10.150
3322
+ --------------+--------+------+------------+------+------
3323
+
3324
+ Any combination of profiles can be specified by ORing
3325
+ individual profiles, for example, a value of 0x2230 selects
3326
+ profiles 2, 6, 10, and 11.""",
3327
+ "reference" :
3328
+ """[802.3ah] Annex 62A.3.5""",
3329
+ }, # column
3330
+ "efmCuPme10PPayloadDRateProfile" : {
3331
+ "nodetype" : "column",
3332
+ "moduleName" : "EFM-CU-MIB",
3333
+ "oid" : "1.3.6.1.2.1.167.1.2.6.1.1.6",
3334
+ "status" : "current",
3335
+ "syntax" : {
3336
+ "type" : {
3337
+ "basetype" : "Enumeration",
3338
+ "profile5" : {
3339
+ "nodetype" : "namednumber",
3340
+ "number" : "5"
3341
+ },
3342
+ "profile10" : {
3343
+ "nodetype" : "namednumber",
3344
+ "number" : "10"
3345
+ },
3346
+ "profile15" : {
3347
+ "nodetype" : "namednumber",
3348
+ "number" : "15"
3349
+ },
3350
+ "profile20" : {
3351
+ "nodetype" : "namednumber",
3352
+ "number" : "20"
3353
+ },
3354
+ "profile25" : {
3355
+ "nodetype" : "namednumber",
3356
+ "number" : "25"
3357
+ },
3358
+ "profile30" : {
3359
+ "nodetype" : "namednumber",
3360
+ "number" : "30"
3361
+ },
3362
+ "profile50" : {
3363
+ "nodetype" : "namednumber",
3364
+ "number" : "50"
3365
+ },
3366
+ "profile70" : {
3367
+ "nodetype" : "namednumber",
3368
+ "number" : "70"
3369
+ },
3370
+ "profile100" : {
3371
+ "nodetype" : "namednumber",
3372
+ "number" : "100"
3373
+ },
3374
+ "profile140" : {
3375
+ "nodetype" : "namednumber",
3376
+ "number" : "140"
3377
+ },
3378
+ "profile200" : {
3379
+ "nodetype" : "namednumber",
3380
+ "number" : "200"
3381
+ },
3382
+ },
3383
+ },
3384
+ "access" : "readwrite",
3385
+ "description" :
3386
+ """The 10PASS-TS PME Downstream Payload Rate Profile, as
3387
+
3388
+
3389
+
3390
+ specified in 802.3 Annex 62A. Possible values are:
3391
+ profile5(5) - 2.5 Mbps
3392
+ profile10(10) - 5 Mbps
3393
+ profile15(15) - 7.5 Mbps
3394
+ profile20(20) - 10 Mbps
3395
+ profile25(25) - 12.5 Mbps
3396
+ profile30(30) - 15 Mbps
3397
+ profile50(50) - 25 Mbps
3398
+ profile70(70) - 35 Mbps
3399
+ profile100(100) - 50 Mbps
3400
+ profile140(140) - 70 Mbps
3401
+ profile200(200) - 100 Mbps
3402
+
3403
+ Each value represents a target for the PME's Downstream
3404
+ Payload Bitrate as seen at the MII. If the payload rate of
3405
+ the selected profile cannot be achieved based on the loop
3406
+ environment, bandplan, and PSD mask, the PME initialization
3407
+ SHALL fail.""",
3408
+ "reference" :
3409
+ """[802.3ah] Annex 62A.3.6""",
3410
+ }, # column
3411
+ "efmCuPme10PPayloadURateProfile" : {
3412
+ "nodetype" : "column",
3413
+ "moduleName" : "EFM-CU-MIB",
3414
+ "oid" : "1.3.6.1.2.1.167.1.2.6.1.1.7",
3415
+ "status" : "current",
3416
+ "syntax" : {
3417
+ "type" : {
3418
+ "basetype" : "Enumeration",
3419
+ "profile5" : {
3420
+ "nodetype" : "namednumber",
3421
+ "number" : "5"
3422
+ },
3423
+ "profile10" : {
3424
+ "nodetype" : "namednumber",
3425
+ "number" : "10"
3426
+ },
3427
+ "profile15" : {
3428
+ "nodetype" : "namednumber",
3429
+ "number" : "15"
3430
+ },
3431
+ "profile20" : {
3432
+ "nodetype" : "namednumber",
3433
+ "number" : "20"
3434
+ },
3435
+ "profile25" : {
3436
+ "nodetype" : "namednumber",
3437
+ "number" : "25"
3438
+ },
3439
+ "profile30" : {
3440
+ "nodetype" : "namednumber",
3441
+ "number" : "30"
3442
+ },
3443
+ "profile50" : {
3444
+ "nodetype" : "namednumber",
3445
+ "number" : "50"
3446
+ },
3447
+ "profile70" : {
3448
+ "nodetype" : "namednumber",
3449
+ "number" : "70"
3450
+ },
3451
+ "profile100" : {
3452
+ "nodetype" : "namednumber",
3453
+ "number" : "100"
3454
+ },
3455
+ },
3456
+ },
3457
+ "access" : "readwrite",
3458
+ "description" :
3459
+ """The 10PASS-TS PME Upstream Payload Rate Profile, as specified
3460
+ in 802.3 Annex 62A. Possible values are:
3461
+ profile5(5) - 2.5 Mbps
3462
+ profile10(10) - 5 Mbps
3463
+ profile15(15) - 7.5 Mbps
3464
+ profile20(20) - 10 Mbps
3465
+ profile25(25) - 12.5 Mbps
3466
+ profile30(30) - 15 Mbps
3467
+ profile50(50) - 25 Mbps
3468
+ profile70(70) - 35 Mbps
3469
+ profile100(100) - 50 Mbps
3470
+
3471
+
3472
+
3473
+ Each value represents a target for the PME's Upstream Payload
3474
+ Bitrate as seen at the MII. If the payload rate of the
3475
+ selected profile cannot be achieved based on the loop
3476
+ environment, bandplan, and PSD mask, the PME initialization
3477
+ SHALL fail.""",
3478
+ "reference" :
3479
+ """[802.3ah] Annex 62A.3.6""",
3480
+ }, # column
3481
+ "efmCuPme10PProfileRowStatus" : {
3482
+ "nodetype" : "column",
3483
+ "moduleName" : "EFM-CU-MIB",
3484
+ "oid" : "1.3.6.1.2.1.167.1.2.6.1.1.8",
3485
+ "status" : "current",
3486
+ "syntax" : {
3487
+ "type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
3488
+ },
3489
+ "access" : "readwrite",
3490
+ "description" :
3491
+ """This object controls creation, modification, or deletion of
3492
+ the associated entry in efmCuPme10PProfileTable per the
3493
+ semantics of RowStatus.
3494
+
3495
+ If an active entry is referenced via efmCuAdminProfile or
3496
+ efmCuPmeAdminProfile, the entry MUST remain 'active' until
3497
+ all references are removed.
3498
+
3499
+ An 'active' entry SHALL NOT be modified. In order to modify
3500
+ an existing entry, it MUST be taken out of service (by setting
3501
+ this object to 'notInService'), modified, and set 'active'
3502
+ again.""",
3503
+ }, # column
3504
+ "efmCuPme10PStatusTable" : {
3505
+ "nodetype" : "table",
3506
+ "moduleName" : "EFM-CU-MIB",
3507
+ "oid" : "1.3.6.1.2.1.167.1.2.6.2",
3508
+ "status" : "current",
3509
+ "description" :
3510
+ """This table provides status information of EFMCu 10PASS-TS
3511
+ PMEs (modems).
3512
+
3513
+ This table contains live data from the equipment. As such,
3514
+ it is NOT persistent.""",
3515
+ }, # table
3516
+ "efmCuPme10PStatusEntry" : {
3517
+ "nodetype" : "row",
3518
+ "moduleName" : "EFM-CU-MIB",
3519
+ "oid" : "1.3.6.1.2.1.167.1.2.6.2.1",
3520
+ "status" : "current",
3521
+ "linkage" : [
3522
+ "ifIndex",
3523
+ ],
3524
+ "description" :
3525
+ """An entry in the EFMCu 10PASS-TS PME Status table.""",
3526
+ }, # row
3527
+ "efmCuPme10PFECCorrectedBlocks" : {
3528
+ "nodetype" : "column",
3529
+ "moduleName" : "EFM-CU-MIB",
3530
+ "oid" : "1.3.6.1.2.1.167.1.2.6.2.1.1",
3531
+ "status" : "current",
3532
+ "syntax" : {
3533
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
3534
+ },
3535
+ "access" : "readonly",
3536
+ "description" :
3537
+ """The number of received and corrected Forward Error Correction
3538
+ (FEC) codewords in this 10PASS-TS PME.
3539
+
3540
+ This object maps to the aPMEFECCorrectedBlocks attribute in
3541
+ Clause 30.
3542
+
3543
+ If a Clause 45 MDIO Interface to the PMA/PMD is present,
3544
+ then this object maps to the 10P FEC correctable errors
3545
+ register.
3546
+
3547
+ Discontinuities in the value of this counter can occur at
3548
+ re-initialization of the management system, and at other times
3549
+ as indicated by the value of ifCounterDiscontinuityTime,
3550
+ defined in IF-MIB.""",
3551
+ "reference" :
3552
+ """[802.3ah] 45.2.1.22, 30.11.2.1.8""",
3553
+ }, # column
3554
+ "efmCuPme10PFECUncorrectedBlocks" : {
3555
+ "nodetype" : "column",
3556
+ "moduleName" : "EFM-CU-MIB",
3557
+ "oid" : "1.3.6.1.2.1.167.1.2.6.2.1.2",
3558
+ "status" : "current",
3559
+ "syntax" : {
3560
+ "type" : { "module" :"SNMPv2-SMI", "name" : "Counter32"},
3561
+ },
3562
+ "access" : "readonly",
3563
+ "description" :
3564
+ """The number of received uncorrectable FEC codewords in this
3565
+ 10PASS-TS PME.
3566
+
3567
+ This object maps to the aPMEFECUncorrectableBlocks attribute
3568
+ in Clause 30.
3569
+
3570
+ If a Clause 45 MDIO Interface to the PMA/PMD is present,
3571
+ then this object maps to the 10P FEC uncorrectable errors
3572
+ register.
3573
+
3574
+ Discontinuities in the value of this counter can occur at
3575
+ re-initialization of the management system, and at other times
3576
+
3577
+
3578
+
3579
+ as indicated by the value of ifCounterDiscontinuityTime,
3580
+ defined in IF-MIB.""",
3581
+ "reference" :
3582
+ """[802.3ah] 45.2.1.23, 30.11.2.1.9""",
3583
+ }, # column
3584
+ "efmCuConformance" : {
3585
+ "nodetype" : "node",
3586
+ "moduleName" : "EFM-CU-MIB",
3587
+ "oid" : "1.3.6.1.2.1.167.2",
3588
+ }, # node
3589
+ "efmCuGroups" : {
3590
+ "nodetype" : "node",
3591
+ "moduleName" : "EFM-CU-MIB",
3592
+ "oid" : "1.3.6.1.2.1.167.2.1",
3593
+ }, # node
3594
+ "efmCuCompliances" : {
3595
+ "nodetype" : "node",
3596
+ "moduleName" : "EFM-CU-MIB",
3597
+ "oid" : "1.3.6.1.2.1.167.2.2",
3598
+ }, # node
3599
+ }, # nodes
3600
+
3601
+ "notifications" : {
3602
+ "efmCuLowRateCrossing" : {
3603
+ "nodetype" : "notification",
3604
+ "moduleName" : "EFM-CU-MIB",
3605
+ "oid" : "1.3.6.1.2.1.167.1.1.0.1",
3606
+ "status" : "current",
3607
+ "objects" : {
3608
+ "ifSpeed" : {
3609
+ "nodetype" : "object",
3610
+ "module" : "IF-MIB"
3611
+ },
3612
+ "efmCuThreshLowRate" : {
3613
+ "nodetype" : "object",
3614
+ "module" : "EFM-CU-MIB"
3615
+ },
3616
+ },
3617
+ "description" :
3618
+ """This notification indicates that the EFMCu port's data rate
3619
+ has reached/dropped below or exceeded the low rate threshold,
3620
+ specified by efmCuThreshLowRate.
3621
+
3622
+ This notification MAY be sent for the -O subtype ports
3623
+ (2BaseTL-O/10PassTS-O) while the port is Up, on the crossing
3624
+ event in both directions: from normal (rate is above the
3625
+ threshold) to low (rate equals the threshold or below it) and
3626
+
3627
+
3628
+
3629
+ from low to normal. This notification is not applicable to
3630
+ the -R subtypes.
3631
+
3632
+ It is RECOMMENDED that a small debouncing period of 2.5 sec,
3633
+ between the detection of the condition and the notification,
3634
+ is implemented to prevent simultaneous LinkUp/LinkDown and
3635
+ efmCuLowRateCrossing notifications to be sent.
3636
+
3637
+ The adaptive nature of the EFMCu technology allows the port to
3638
+ adapt itself to the changes in the copper environment, e.g.,
3639
+ an impulse noise, alien crosstalk, or a micro-interruption may
3640
+ temporarily drop one or more PMEs in the aggregation group,
3641
+ causing a rate degradation of the aggregated EFMCu link.
3642
+ The dropped PMEs would then try to re-initialize, possibly at
3643
+ a lower rate than before, adjusting the rate to provide
3644
+ required target SNR margin.
3645
+
3646
+ Generation of this notification is controlled by the
3647
+ efmCuLowRateCrossingEnable object.""",
3648
+ }, # notification
3649
+ "efmCuPmeLineAtnCrossing" : {
3650
+ "nodetype" : "notification",
3651
+ "moduleName" : "EFM-CU-MIB",
3652
+ "oid" : "1.3.6.1.2.1.167.1.2.0.1",
3653
+ "status" : "current",
3654
+ "objects" : {
3655
+ "efmCuPmeLineAtn" : {
3656
+ "nodetype" : "object",
3657
+ "module" : "EFM-CU-MIB"
3658
+ },
3659
+ "efmCuPmeThreshLineAtn" : {
3660
+ "nodetype" : "object",
3661
+ "module" : "EFM-CU-MIB"
3662
+ },
3663
+ },
3664
+ "description" :
3665
+ """This notification indicates that the loop attenuation
3666
+ threshold (as per the efmCuPmeThreshLineAtn
3667
+ value) has been reached/exceeded for the 2BASE-TL/10PASS-TS
3668
+ PME. This notification MAY be sent on the crossing event in
3669
+ both directions: from normal to exceeded and from exceeded
3670
+ to normal.
3671
+
3672
+ It is RECOMMENDED that a small debouncing period of 2.5 sec,
3673
+ between the detection of the condition and the notification,
3674
+ is implemented to prevent intermittent notifications from
3675
+ being sent.
3676
+
3677
+ Generation of this notification is controlled by the
3678
+ efmCuPmeLineAtnCrossingEnable object.""",
3679
+ }, # notification
3680
+ "efmCuPmeSnrMgnCrossing" : {
3681
+ "nodetype" : "notification",
3682
+ "moduleName" : "EFM-CU-MIB",
3683
+ "oid" : "1.3.6.1.2.1.167.1.2.0.2",
3684
+ "status" : "current",
3685
+ "objects" : {
3686
+ "efmCuPmeSnrMgn" : {
3687
+ "nodetype" : "object",
3688
+ "module" : "EFM-CU-MIB"
3689
+ },
3690
+ "efmCuPmeThreshSnrMgn" : {
3691
+ "nodetype" : "object",
3692
+ "module" : "EFM-CU-MIB"
3693
+ },
3694
+ },
3695
+ "description" :
3696
+ """This notification indicates that the SNR margin threshold
3697
+ (as per the efmCuPmeThreshSnrMgn value) has been
3698
+ reached/exceeded for the 2BASE-TL/10PASS-TS PME.
3699
+ This notification MAY be sent on the crossing event in
3700
+ both directions: from normal to exceeded and from exceeded
3701
+ to normal.
3702
+
3703
+ It is RECOMMENDED that a small debouncing period of 2.5 sec,
3704
+ between the detection of the condition and the notification,
3705
+ is implemented to prevent intermittent notifications from
3706
+ being sent.
3707
+
3708
+ Generation of this notification is controlled by the
3709
+ efmCuPmeSnrMgnCrossingEnable object.""",
3710
+ }, # notification
3711
+ "efmCuPmeDeviceFault" : {
3712
+ "nodetype" : "notification",
3713
+ "moduleName" : "EFM-CU-MIB",
3714
+ "oid" : "1.3.6.1.2.1.167.1.2.0.3",
3715
+ "status" : "current",
3716
+ "objects" : {
3717
+ "efmCuPmeFltStatus" : {
3718
+ "nodetype" : "object",
3719
+ "module" : "EFM-CU-MIB"
3720
+ },
3721
+ },
3722
+ "description" :
3723
+ """This notification indicates that a fault in the PME has been
3724
+ detected by a vendor-specific diagnostic or a self-test.
3725
+
3726
+ Generation of this notification is controlled by the
3727
+ efmCuPmeDeviceFaultEnable object.""",
3728
+ }, # notification
3729
+ "efmCuPmeConfigInitFailure" : {
3730
+ "nodetype" : "notification",
3731
+ "moduleName" : "EFM-CU-MIB",
3732
+ "oid" : "1.3.6.1.2.1.167.1.2.0.4",
3733
+ "status" : "current",
3734
+ "objects" : {
3735
+ "efmCuPmeFltStatus" : {
3736
+ "nodetype" : "object",
3737
+ "module" : "EFM-CU-MIB"
3738
+ },
3739
+ "efmCuAdminProfile" : {
3740
+ "nodetype" : "object",
3741
+ "module" : "EFM-CU-MIB"
3742
+ },
3743
+ "efmCuPmeAdminProfile" : {
3744
+ "nodetype" : "object",
3745
+ "module" : "EFM-CU-MIB"
3746
+ },
3747
+ },
3748
+ "description" :
3749
+ """This notification indicates that PME initialization has
3750
+ failed, due to inability of the PME link to achieve the
3751
+
3752
+
3753
+
3754
+ requested configuration profile.
3755
+
3756
+ Generation of this notification is controlled by the
3757
+ efmCuPmeConfigInitFailEnable object.""",
3758
+ }, # notification
3759
+ "efmCuPmeProtocolInitFailure" : {
3760
+ "nodetype" : "notification",
3761
+ "moduleName" : "EFM-CU-MIB",
3762
+ "oid" : "1.3.6.1.2.1.167.1.2.0.5",
3763
+ "status" : "current",
3764
+ "objects" : {
3765
+ "efmCuPmeFltStatus" : {
3766
+ "nodetype" : "object",
3767
+ "module" : "EFM-CU-MIB"
3768
+ },
3769
+ "efmCuPmeOperSubType" : {
3770
+ "nodetype" : "object",
3771
+ "module" : "EFM-CU-MIB"
3772
+ },
3773
+ },
3774
+ "description" :
3775
+ """This notification indicates that the peer PME was using
3776
+ an incompatible protocol during initialization.
3777
+
3778
+ Generation of this notification is controlled by the
3779
+ efmCuPmeProtocolInitFailEnable object.""",
3780
+ }, # notification
3781
+ }, # notifications
3782
+
3783
+ "groups" : {
3784
+ "efmCuBasicGroup" : {
3785
+ "nodetype" : "group",
3786
+ "moduleName" : "EFM-CU-MIB",
3787
+ "oid" : "1.3.6.1.2.1.167.2.1.1",
3788
+ "status" : "current",
3789
+ "members" : {
3790
+ "efmCuPAFSupported" : {
3791
+ "nodetype" : "member",
3792
+ "module" : "EFM-CU-MIB"
3793
+ },
3794
+ "efmCuAdminProfile" : {
3795
+ "nodetype" : "member",
3796
+ "module" : "EFM-CU-MIB"
3797
+ },
3798
+ "efmCuTargetDataRate" : {
3799
+ "nodetype" : "member",
3800
+ "module" : "EFM-CU-MIB"
3801
+ },
3802
+ "efmCuTargetSnrMgn" : {
3803
+ "nodetype" : "member",
3804
+ "module" : "EFM-CU-MIB"
3805
+ },
3806
+ "efmCuAdaptiveSpectra" : {
3807
+ "nodetype" : "member",
3808
+ "module" : "EFM-CU-MIB"
3809
+ },
3810
+ "efmCuPortSide" : {
3811
+ "nodetype" : "member",
3812
+ "module" : "EFM-CU-MIB"
3813
+ },
3814
+ "efmCuFltStatus" : {
3815
+ "nodetype" : "member",
3816
+ "module" : "EFM-CU-MIB"
3817
+ },
3818
+ }, # members
3819
+ "description" :
3820
+ """A collection of objects representing management information
3821
+ common for all types of EFMCu ports.""",
3822
+ }, # group
3823
+ "efmCuPAFGroup" : {
3824
+ "nodetype" : "group",
3825
+ "moduleName" : "EFM-CU-MIB",
3826
+ "oid" : "1.3.6.1.2.1.167.2.1.2",
3827
+ "status" : "current",
3828
+ "members" : {
3829
+ "efmCuPeerPAFSupported" : {
3830
+ "nodetype" : "member",
3831
+ "module" : "EFM-CU-MIB"
3832
+ },
3833
+ "efmCuPAFCapacity" : {
3834
+ "nodetype" : "member",
3835
+ "module" : "EFM-CU-MIB"
3836
+ },
3837
+ "efmCuPeerPAFCapacity" : {
3838
+ "nodetype" : "member",
3839
+ "module" : "EFM-CU-MIB"
3840
+ },
3841
+ "efmCuPAFAdminState" : {
3842
+ "nodetype" : "member",
3843
+ "module" : "EFM-CU-MIB"
3844
+ },
3845
+ "efmCuPAFDiscoveryCode" : {
3846
+ "nodetype" : "member",
3847
+ "module" : "EFM-CU-MIB"
3848
+ },
3849
+ "efmCuPAFRemoteDiscoveryCode" : {
3850
+ "nodetype" : "member",
3851
+ "module" : "EFM-CU-MIB"
3852
+ },
3853
+ "efmCuNumPMEs" : {
3854
+ "nodetype" : "member",
3855
+ "module" : "EFM-CU-MIB"
3856
+ },
3857
+ }, # members
3858
+ "description" :
3859
+ """A collection of objects supporting OPTIONAL PME
3860
+ Aggregation Function (PAF) and PAF discovery in EFMCu ports.""",
3861
+ }, # group
3862
+ "efmCuPAFErrorsGroup" : {
3863
+ "nodetype" : "group",
3864
+ "moduleName" : "EFM-CU-MIB",
3865
+ "oid" : "1.3.6.1.2.1.167.2.1.3",
3866
+ "status" : "current",
3867
+ "members" : {
3868
+ "efmCuPAFInErrors" : {
3869
+ "nodetype" : "member",
3870
+ "module" : "EFM-CU-MIB"
3871
+ },
3872
+ "efmCuPAFInSmallFragments" : {
3873
+ "nodetype" : "member",
3874
+ "module" : "EFM-CU-MIB"
3875
+ },
3876
+ "efmCuPAFInLargeFragments" : {
3877
+ "nodetype" : "member",
3878
+ "module" : "EFM-CU-MIB"
3879
+ },
3880
+ "efmCuPAFInBadFragments" : {
3881
+ "nodetype" : "member",
3882
+ "module" : "EFM-CU-MIB"
3883
+ },
3884
+ "efmCuPAFInLostFragments" : {
3885
+ "nodetype" : "member",
3886
+ "module" : "EFM-CU-MIB"
3887
+ },
3888
+ "efmCuPAFInLostStarts" : {
3889
+ "nodetype" : "member",
3890
+ "module" : "EFM-CU-MIB"
3891
+ },
3892
+ "efmCuPAFInLostEnds" : {
3893
+ "nodetype" : "member",
3894
+ "module" : "EFM-CU-MIB"
3895
+ },
3896
+ "efmCuPAFInOverflows" : {
3897
+ "nodetype" : "member",
3898
+ "module" : "EFM-CU-MIB"
3899
+ },
3900
+ }, # members
3901
+ "description" :
3902
+ """A collection of objects supporting OPTIONAL error counters
3903
+ of PAF on EFMCu ports.""",
3904
+ }, # group
3905
+ "efmCuPmeGroup" : {
3906
+ "nodetype" : "group",
3907
+ "moduleName" : "EFM-CU-MIB",
3908
+ "oid" : "1.3.6.1.2.1.167.2.1.4",
3909
+ "status" : "current",
3910
+ "members" : {
3911
+ "efmCuPmeAdminProfile" : {
3912
+ "nodetype" : "member",
3913
+ "module" : "EFM-CU-MIB"
3914
+ },
3915
+ "efmCuPmeOperStatus" : {
3916
+ "nodetype" : "member",
3917
+ "module" : "EFM-CU-MIB"
3918
+ },
3919
+ "efmCuPmeFltStatus" : {
3920
+ "nodetype" : "member",
3921
+ "module" : "EFM-CU-MIB"
3922
+ },
3923
+ "efmCuPmeSubTypesSupported" : {
3924
+ "nodetype" : "member",
3925
+ "module" : "EFM-CU-MIB"
3926
+ },
3927
+ "efmCuPmeAdminSubType" : {
3928
+ "nodetype" : "member",
3929
+ "module" : "EFM-CU-MIB"
3930
+ },
3931
+ "efmCuPmeOperSubType" : {
3932
+ "nodetype" : "member",
3933
+ "module" : "EFM-CU-MIB"
3934
+ },
3935
+ "efmCuPAFRemoteDiscoveryCode" : {
3936
+ "nodetype" : "member",
3937
+ "module" : "EFM-CU-MIB"
3938
+ },
3939
+ "efmCuPmeOperProfile" : {
3940
+ "nodetype" : "member",
3941
+ "module" : "EFM-CU-MIB"
3942
+ },
3943
+ "efmCuPmeSnrMgn" : {
3944
+ "nodetype" : "member",
3945
+ "module" : "EFM-CU-MIB"
3946
+ },
3947
+ "efmCuPmePeerSnrMgn" : {
3948
+ "nodetype" : "member",
3949
+ "module" : "EFM-CU-MIB"
3950
+ },
3951
+ "efmCuPmeLineAtn" : {
3952
+ "nodetype" : "member",
3953
+ "module" : "EFM-CU-MIB"
3954
+ },
3955
+ "efmCuPmePeerLineAtn" : {
3956
+ "nodetype" : "member",
3957
+ "module" : "EFM-CU-MIB"
3958
+ },
3959
+ "efmCuPmeEquivalentLength" : {
3960
+ "nodetype" : "member",
3961
+ "module" : "EFM-CU-MIB"
3962
+ },
3963
+ "efmCuPmeTCCodingErrors" : {
3964
+ "nodetype" : "member",
3965
+ "module" : "EFM-CU-MIB"
3966
+ },
3967
+ "efmCuPmeTCCrcErrors" : {
3968
+ "nodetype" : "member",
3969
+ "module" : "EFM-CU-MIB"
3970
+ },
3971
+ "efmCuPmeThreshLineAtn" : {
3972
+ "nodetype" : "member",
3973
+ "module" : "EFM-CU-MIB"
3974
+ },
3975
+ "efmCuPmeThreshSnrMgn" : {
3976
+ "nodetype" : "member",
3977
+ "module" : "EFM-CU-MIB"
3978
+ },
3979
+ }, # members
3980
+ "description" :
3981
+ """A collection of objects providing information about
3982
+ a 2BASE-TL/10PASS-TS PME.""",
3983
+ }, # group
3984
+ "efmCuAlarmConfGroup" : {
3985
+ "nodetype" : "group",
3986
+ "moduleName" : "EFM-CU-MIB",
3987
+ "oid" : "1.3.6.1.2.1.167.2.1.5",
3988
+ "status" : "current",
3989
+ "members" : {
3990
+ "efmCuThreshLowRate" : {
3991
+ "nodetype" : "member",
3992
+ "module" : "EFM-CU-MIB"
3993
+ },
3994
+ "efmCuLowRateCrossingEnable" : {
3995
+ "nodetype" : "member",
3996
+ "module" : "EFM-CU-MIB"
3997
+ },
3998
+ "efmCuPmeThreshLineAtn" : {
3999
+ "nodetype" : "member",
4000
+ "module" : "EFM-CU-MIB"
4001
+ },
4002
+ "efmCuPmeLineAtnCrossingEnable" : {
4003
+ "nodetype" : "member",
4004
+ "module" : "EFM-CU-MIB"
4005
+ },
4006
+ "efmCuPmeThreshSnrMgn" : {
4007
+ "nodetype" : "member",
4008
+ "module" : "EFM-CU-MIB"
4009
+ },
4010
+ "efmCuPmeSnrMgnCrossingEnable" : {
4011
+ "nodetype" : "member",
4012
+ "module" : "EFM-CU-MIB"
4013
+ },
4014
+ "efmCuPmeDeviceFaultEnable" : {
4015
+ "nodetype" : "member",
4016
+ "module" : "EFM-CU-MIB"
4017
+ },
4018
+ "efmCuPmeConfigInitFailEnable" : {
4019
+ "nodetype" : "member",
4020
+ "module" : "EFM-CU-MIB"
4021
+ },
4022
+ "efmCuPmeProtocolInitFailEnable" : {
4023
+ "nodetype" : "member",
4024
+ "module" : "EFM-CU-MIB"
4025
+ },
4026
+ }, # members
4027
+ "description" :
4028
+ """A collection of objects supporting configuration of alarm
4029
+ thresholds and notifications in EFMCu ports.""",
4030
+ }, # group
4031
+ "efmCuNotificationGroup" : {
4032
+ "nodetype" : "group",
4033
+ "moduleName" : "EFM-CU-MIB",
4034
+ "oid" : "1.3.6.1.2.1.167.2.1.6",
4035
+ "status" : "current",
4036
+ "members" : {
4037
+ "efmCuLowRateCrossing" : {
4038
+ "nodetype" : "member",
4039
+ "module" : "EFM-CU-MIB"
4040
+ },
4041
+ "efmCuPmeLineAtnCrossing" : {
4042
+ "nodetype" : "member",
4043
+ "module" : "EFM-CU-MIB"
4044
+ },
4045
+ "efmCuPmeSnrMgnCrossing" : {
4046
+ "nodetype" : "member",
4047
+ "module" : "EFM-CU-MIB"
4048
+ },
4049
+ "efmCuPmeDeviceFault" : {
4050
+ "nodetype" : "member",
4051
+ "module" : "EFM-CU-MIB"
4052
+ },
4053
+ "efmCuPmeConfigInitFailure" : {
4054
+ "nodetype" : "member",
4055
+ "module" : "EFM-CU-MIB"
4056
+ },
4057
+ "efmCuPmeProtocolInitFailure" : {
4058
+ "nodetype" : "member",
4059
+ "module" : "EFM-CU-MIB"
4060
+ },
4061
+ }, # members
4062
+ "description" :
4063
+ """This group supports notifications of significant conditions
4064
+ associated with EFMCu ports.""",
4065
+ }, # group
4066
+ "efmCuPme2BProfileGroup" : {
4067
+ "nodetype" : "group",
4068
+ "moduleName" : "EFM-CU-MIB",
4069
+ "oid" : "1.3.6.1.2.1.167.2.1.7",
4070
+ "status" : "current",
4071
+ "members" : {
4072
+ "efmCuPme2BProfileDescr" : {
4073
+ "nodetype" : "member",
4074
+ "module" : "EFM-CU-MIB"
4075
+ },
4076
+ "efmCuPme2BRegion" : {
4077
+ "nodetype" : "member",
4078
+ "module" : "EFM-CU-MIB"
4079
+ },
4080
+ "efmCuPme2BsMode" : {
4081
+ "nodetype" : "member",
4082
+ "module" : "EFM-CU-MIB"
4083
+ },
4084
+ "efmCuPme2BMinDataRate" : {
4085
+ "nodetype" : "member",
4086
+ "module" : "EFM-CU-MIB"
4087
+ },
4088
+ "efmCuPme2BMaxDataRate" : {
4089
+ "nodetype" : "member",
4090
+ "module" : "EFM-CU-MIB"
4091
+ },
4092
+ "efmCuPme2BPower" : {
4093
+ "nodetype" : "member",
4094
+ "module" : "EFM-CU-MIB"
4095
+ },
4096
+ "efmCuPme2BConstellation" : {
4097
+ "nodetype" : "member",
4098
+ "module" : "EFM-CU-MIB"
4099
+ },
4100
+ "efmCuPme2BProfileRowStatus" : {
4101
+ "nodetype" : "member",
4102
+ "module" : "EFM-CU-MIB"
4103
+ },
4104
+ "efmCuPme2BsModeDescr" : {
4105
+ "nodetype" : "member",
4106
+ "module" : "EFM-CU-MIB"
4107
+ },
4108
+ "efmCuPme2BsModeRowStatus" : {
4109
+ "nodetype" : "member",
4110
+ "module" : "EFM-CU-MIB"
4111
+ },
4112
+ "efmCuPme2BEquivalentLength" : {
4113
+ "nodetype" : "member",
4114
+ "module" : "EFM-CU-MIB"
4115
+ },
4116
+ "efmCuPme2BMaxDataRatePam16" : {
4117
+ "nodetype" : "member",
4118
+ "module" : "EFM-CU-MIB"
4119
+ },
4120
+ "efmCuPme2BMaxDataRatePam32" : {
4121
+ "nodetype" : "member",
4122
+ "module" : "EFM-CU-MIB"
4123
+ },
4124
+ "efmCuPme2BReachRateRowStatus" : {
4125
+ "nodetype" : "member",
4126
+ "module" : "EFM-CU-MIB"
4127
+ },
4128
+ }, # members
4129
+ "description" :
4130
+ """A collection of objects that constitute a configuration
4131
+
4132
+
4133
+
4134
+ profile for configuration of 2BASE-TL ports.""",
4135
+ }, # group
4136
+ "efmCuPme10PProfileGroup" : {
4137
+ "nodetype" : "group",
4138
+ "moduleName" : "EFM-CU-MIB",
4139
+ "oid" : "1.3.6.1.2.1.167.2.1.8",
4140
+ "status" : "current",
4141
+ "members" : {
4142
+ "efmCuPme10PProfileDescr" : {
4143
+ "nodetype" : "member",
4144
+ "module" : "EFM-CU-MIB"
4145
+ },
4146
+ "efmCuPme10PBandplanPSDMskProfile" : {
4147
+ "nodetype" : "member",
4148
+ "module" : "EFM-CU-MIB"
4149
+ },
4150
+ "efmCuPme10PUPBOReferenceProfile" : {
4151
+ "nodetype" : "member",
4152
+ "module" : "EFM-CU-MIB"
4153
+ },
4154
+ "efmCuPme10PBandNotchProfiles" : {
4155
+ "nodetype" : "member",
4156
+ "module" : "EFM-CU-MIB"
4157
+ },
4158
+ "efmCuPme10PPayloadDRateProfile" : {
4159
+ "nodetype" : "member",
4160
+ "module" : "EFM-CU-MIB"
4161
+ },
4162
+ "efmCuPme10PPayloadURateProfile" : {
4163
+ "nodetype" : "member",
4164
+ "module" : "EFM-CU-MIB"
4165
+ },
4166
+ "efmCuPme10PProfileRowStatus" : {
4167
+ "nodetype" : "member",
4168
+ "module" : "EFM-CU-MIB"
4169
+ },
4170
+ }, # members
4171
+ "description" :
4172
+ """A collection of objects that constitute a configuration
4173
+ profile for configuration of 10PASS-TS ports.""",
4174
+ }, # group
4175
+ "efmCuPme10PStatusGroup" : {
4176
+ "nodetype" : "group",
4177
+ "moduleName" : "EFM-CU-MIB",
4178
+ "oid" : "1.3.6.1.2.1.167.2.1.9",
4179
+ "status" : "current",
4180
+ "members" : {
4181
+ "efmCuPme10PFECCorrectedBlocks" : {
4182
+ "nodetype" : "member",
4183
+ "module" : "EFM-CU-MIB"
4184
+ },
4185
+ "efmCuPme10PFECUncorrectedBlocks" : {
4186
+ "nodetype" : "member",
4187
+ "module" : "EFM-CU-MIB"
4188
+ },
4189
+ }, # members
4190
+ "description" :
4191
+ """A collection of objects providing status information
4192
+ specific to 10PASS-TS PMEs.""",
4193
+ }, # group
4194
+ }, # groups
4195
+
4196
+ "compliances" : {
4197
+ "efmCuCompliance" : {
4198
+ "nodetype" : "compliance",
4199
+ "moduleName" : "EFM-CU-MIB",
4200
+ "oid" : "1.3.6.1.2.1.167.2.2.1",
4201
+ "status" : "current",
4202
+ "description" :
4203
+ """The compliance statement for 2BASE-TL/10PASS-TS interfaces.
4204
+ Compliance with the following external compliance statements
4205
+ is REQUIRED:
4206
+
4207
+ MIB Module Compliance Statement
4208
+ ---------- --------------------
4209
+ IF-MIB ifCompliance3
4210
+ EtherLike-MIB dot3Compliance2
4211
+ MAU-MIB mauModIfCompl3
4212
+
4213
+ Compliance with the following external compliance statements
4214
+ is OPTIONAL for implementations supporting PME Aggregation
4215
+ Function (PAF) with flexible cross-connect between the PCS
4216
+
4217
+
4218
+
4219
+ and PME ports:
4220
+
4221
+ MIB Module Compliance Statement
4222
+ ---------- --------------------
4223
+ IF-INVERTED-STACK-MIB ifInvCompliance
4224
+ IF-CAP-STACK-MIB ifCapStackCompliance""",
4225
+ "requires" : {
4226
+ "efmCuBasicGroup" : {
4227
+ "nodetype" : "mandatory",
4228
+ "module" : "EFM-CU-MIB"
4229
+ },
4230
+ "efmCuPmeGroup" : {
4231
+ "nodetype" : "mandatory",
4232
+ "module" : "EFM-CU-MIB"
4233
+ },
4234
+ "efmCuAlarmConfGroup" : {
4235
+ "nodetype" : "mandatory",
4236
+ "module" : "EFM-CU-MIB"
4237
+ },
4238
+ "efmCuNotificationGroup" : {
4239
+ "nodetype" : "mandatory",
4240
+ "module" : "EFM-CU-MIB"
4241
+ },
4242
+ "efmCuPme2BProfileGroup" : {
4243
+ "nodetype" : "optional",
4244
+ "module" : "EFM-CU-MIB",
4245
+ "description" :
4246
+ """Support for this group is only required for implementations
4247
+ supporting 2BASE-TL PHY.""",
4248
+ },
4249
+ "efmCuPme10PProfileGroup" : {
4250
+ "nodetype" : "optional",
4251
+ "module" : "EFM-CU-MIB",
4252
+ "description" :
4253
+ """Support for this group is only required for implementations
4254
+ supporting 10PASS-TS PHY.""",
4255
+ },
4256
+ "efmCuPAFGroup" : {
4257
+ "nodetype" : "optional",
4258
+ "module" : "EFM-CU-MIB",
4259
+ "description" :
4260
+ """Support for this group is only required for
4261
+ implementations supporting PME Aggregation Function (PAF).""",
4262
+ },
4263
+ "efmCuPAFErrorsGroup" : {
4264
+ "nodetype" : "optional",
4265
+ "module" : "EFM-CU-MIB",
4266
+ "description" :
4267
+ """Support for this group is OPTIONAL for implementations
4268
+ supporting PME Aggregation Function (PAF).""",
4269
+ },
4270
+ "efmCuPme10PStatusGroup" : {
4271
+ "nodetype" : "optional",
4272
+ "module" : "EFM-CU-MIB",
4273
+ "description" :
4274
+ """Support for this group is OPTIONAL for implementations
4275
+ supporting 10PASS-TS PHY.""",
4276
+ },
4277
+ }, # requires
4278
+ "refinements" : {
4279
+ "efmCuPmeSubTypesSupported" : {
4280
+ "module" : "EFM-CU-MIB",
4281
+ "syntax" : {
4282
+ "type" : {
4283
+ "basetype" : "Bits",
4284
+ "ieee2BaseTLO" : {
4285
+ "nodetype" : "namednumber",
4286
+ "number" : "0"
4287
+ },
4288
+ "ieee2BaseTLR" : {
4289
+ "nodetype" : "namednumber",
4290
+ "number" : "1"
4291
+ },
4292
+ "ieee10PassTSO" : {
4293
+ "nodetype" : "namednumber",
4294
+ "number" : "2"
4295
+ },
4296
+ "ieee10PassTSR" : {
4297
+ "nodetype" : "namednumber",
4298
+ "number" : "3"
4299
+ },
4300
+ },
4301
+ }, # syntax
4302
+ "description" :
4303
+ """Support for all subtypes is not required. However, at
4304
+ least one value SHALL be supported.""",
4305
+ },
4306
+ "efmCuPmeAdminSubType" : {
4307
+ "module" : "EFM-CU-MIB",
4308
+ "access" : "readonly",
4309
+ "description" :
4310
+ """Write access is not required (needed only for PMEs
4311
+ supporting more than a single subtype, e.g.,
4312
+ ieee2BaseTLO and ieee2BaseTLR or ieee10PassTSO and
4313
+ ieee10PassTSR).""",
4314
+ },
4315
+ "efmCuTargetSnrMgn" : {
4316
+ "module" : "EFM-CU-MIB",
4317
+ "access" : "readonly",
4318
+ "description" :
4319
+ """Write access is OPTIONAL. For PHYs without write access,
4320
+ the target SNR margin SHALL be fixed at 5dB for 2BASE-TL
4321
+ and 6dB for 10PASS-TS.""",
4322
+ },
4323
+ "efmCuAdaptiveSpectra" : {
4324
+ "module" : "EFM-CU-MIB",
4325
+ "access" : "readonly",
4326
+ "description" :
4327
+ """Write access is OPTIONAL. For PHYs without write access,
4328
+ the default value SHOULD be false.""",
4329
+ },
4330
+ }, # refinements
4331
+
4332
+ }, # compliance
4333
+ }, # compliances
4334
+
4335
+ }