logstash-input-snmp 0.1.0.beta4 → 0.1.0.beta5
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +5 -0
- data/lib/logstash/inputs/snmp.rb +75 -12
- data/lib/logstash/inputs/snmp/base_client.rb +162 -0
- data/lib/logstash/inputs/snmp/client.rb +11 -109
- data/lib/logstash/inputs/snmp/clientv3.rb +139 -0
- data/lib/logstash/inputs/snmp/mib.rb +22 -20
- data/lib/mibs/ietf/ACCOUNTING-CONTROL-MIB.dic +1316 -0
- data/lib/mibs/ietf/ADSL-LINE-EXT-MIB.dic +1724 -0
- data/lib/mibs/ietf/ADSL-LINE-MIB.dic +7297 -0
- data/lib/mibs/ietf/ADSL-TC-MIB.dic +160 -0
- data/lib/mibs/ietf/ADSL2-LINE-MIB.dic +8663 -0
- data/lib/mibs/ietf/ADSL2-LINE-TC-MIB.dic +1462 -0
- data/lib/mibs/ietf/AGENTX-MIB.dic +817 -0
- data/lib/mibs/ietf/AGGREGATE-MIB.dic +708 -0
- data/lib/mibs/ietf/ALARM-MIB.dic +1734 -0
- data/lib/mibs/ietf/APM-MIB.dic +2870 -0
- data/lib/mibs/ietf/APPC-MIB.dic +8687 -0
- data/lib/mibs/ietf/APPLETALK-MIB.dic +4399 -0
- data/lib/mibs/ietf/APPLICATION-MIB.dic +3750 -0
- data/lib/mibs/ietf/APPN-DLUR-MIB.dic +972 -0
- data/lib/mibs/ietf/APPN-MIB.dic +9364 -0
- data/lib/mibs/ietf/APPN-TRAP-MIB.dic +664 -0
- data/lib/mibs/ietf/APS-MIB.dic +2430 -0
- data/lib/mibs/ietf/ARC-MIB.dic +552 -0
- data/lib/mibs/ietf/ATM-ACCOUNTING-INFORMATION-MIB.dic +816 -0
- data/lib/mibs/ietf/ATM-MIB.dic +4104 -0
- data/lib/mibs/ietf/ATM-TC-MIB.dic +914 -0
- data/lib/mibs/ietf/ATM2-MIB.dic +4715 -0
- data/lib/mibs/ietf/BFD-STD-MIB.dic +2367 -0
- data/lib/mibs/ietf/BFD-TC-STD-MIB.dic +202 -0
- data/lib/mibs/ietf/BGP4-MIB.dic +1931 -0
- data/lib/mibs/ietf/BLDG-HVAC-MIB.dic +812 -0
- data/lib/mibs/ietf/BRIDGE-MIB.dic +2257 -0
- data/lib/mibs/ietf/CAPWAP-BASE-MIB.dic +4128 -0
- data/lib/mibs/ietf/CAPWAP-DOT11-MIB.dic +482 -0
- data/lib/mibs/ietf/CHARACTER-MIB.dic +1140 -0
- data/lib/mibs/ietf/CIRCUIT-IF-MIB.dic +493 -0
- data/lib/mibs/ietf/CLNS-MIB.dic +1702 -0
- data/lib/mibs/ietf/COFFEE-POT-MIB.dic +282 -0
- data/lib/mibs/ietf/COPS-CLIENT-MIB.dic +1270 -0
- data/lib/mibs/ietf/DECNET-PHIV-MIB.dic +5837 -0
- data/lib/mibs/ietf/DIAL-CONTROL-MIB.dic +2139 -0
- data/lib/mibs/ietf/DIFFSERV-CONFIG-MIB.dic +378 -0
- data/lib/mibs/ietf/DIFFSERV-MIB.dic +5073 -0
- data/lib/mibs/ietf/DIRECTORY-SERVER-MIB.dic +1041 -0
- data/lib/mibs/ietf/DISMAN-EVENT-MIB.dic +3151 -0
- data/lib/mibs/ietf/DISMAN-EXPRESSION-MIB.dic +1716 -0
- data/lib/mibs/ietf/DISMAN-NSLOOKUP-MIB.dic +698 -0
- data/lib/mibs/ietf/DISMAN-PING-MIB.dic +2635 -0
- data/lib/mibs/ietf/DISMAN-SCHEDULE-MIB.dic +1744 -0
- data/lib/mibs/ietf/DISMAN-SCRIPT-MIB.dic +2820 -0
- data/lib/mibs/ietf/DISMAN-TRACEROUTE-MIB.dic +3239 -0
- data/lib/mibs/ietf/DLSW-MIB.dic +5635 -0
- data/lib/mibs/ietf/DNS-RESOLVER-MIB.dic +1765 -0
- data/lib/mibs/ietf/DNS-SERVER-MIB.dic +1593 -0
- data/lib/mibs/ietf/DOCS-BPI-MIB.dic +2634 -0
- data/lib/mibs/ietf/DOCS-CABLE-DEVICE-MIB.dic +5042 -0
- data/lib/mibs/ietf/DOCS-IETF-BPI2-MIB.dic +5478 -0
- data/lib/mibs/ietf/DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB.dic +2447 -0
- data/lib/mibs/ietf/DOCS-IETF-QOS-MIB.dic +4886 -0
- data/lib/mibs/ietf/DOCS-IETF-SUBMGT-MIB.dic +1331 -0
- data/lib/mibs/ietf/DOCS-IF-MIB.dic +7980 -0
- data/lib/mibs/ietf/DOT12-IF-MIB.dic +1066 -0
- data/lib/mibs/ietf/DOT12-RPTR-MIB.dic +2669 -0
- data/lib/mibs/ietf/DOT3-EPON-MIB.dic +3297 -0
- data/lib/mibs/ietf/DOT3-OAM-MIB.dic +2830 -0
- data/lib/mibs/ietf/DS0-MIB.dic +466 -0
- data/lib/mibs/ietf/DS0BUNDLE-MIB.dic +468 -0
- data/lib/mibs/ietf/DS1-MIB.dic +4890 -0
- data/lib/mibs/ietf/DS3-MIB.dic +2719 -0
- data/lib/mibs/ietf/DSA-MIB.dic +888 -0
- data/lib/mibs/ietf/DSMON-MIB.dic +6177 -0
- data/lib/mibs/ietf/DVB-RCS-MIB.dic +5764 -0
- data/lib/mibs/ietf/EBN-MIB.dic +1026 -0
- data/lib/mibs/ietf/EFM-CU-MIB.dic +4335 -0
- data/lib/mibs/ietf/ENTITY-MIB.dic +2235 -0
- data/lib/mibs/ietf/ENTITY-SENSOR-MIB.dic +653 -0
- data/lib/mibs/ietf/ENTITY-STATE-MIB.dic +457 -0
- data/lib/mibs/ietf/ENTITY-STATE-TC-MIB.dic +260 -0
- data/lib/mibs/ietf/ETHER-CHIPSET-MIB.dic +787 -0
- data/lib/mibs/ietf/EtherLike-MIB.dic +2548 -0
- data/lib/mibs/ietf/FC-MGMT-MIB.dic +3465 -0
- data/lib/mibs/ietf/FCIP-MGMT-MIB.dic +1596 -0
- data/lib/mibs/ietf/FDDI-SMT73-MIB.dic +3378 -0
- data/lib/mibs/ietf/FIBRE-CHANNEL-FE-MIB.dic +2504 -0
- data/lib/mibs/ietf/FLOAT-TC-MIB.dic +128 -0
- data/lib/mibs/ietf/FLOW-METER-MIB.dic +3201 -0
- data/lib/mibs/ietf/FORCES-MIB.dic +598 -0
- data/lib/mibs/ietf/FR-ATM-PVC-SERVICE-IWF-MIB.dic +1601 -0
- data/lib/mibs/ietf/FR-MFR-MIB.dic +1351 -0
- data/lib/mibs/ietf/FRAME-RELAY-DTE-MIB.dic +1688 -0
- data/lib/mibs/ietf/FRNETSERV-MIB.dic +3940 -0
- data/lib/mibs/ietf/FRSLD-MIB.dic +2580 -0
- data/lib/mibs/ietf/Finisher-MIB.dic +1416 -0
- data/lib/mibs/ietf/GMPLS-LABEL-STD-MIB.dic +965 -0
- data/lib/mibs/ietf/GMPLS-LSR-STD-MIB.dic +693 -0
- data/lib/mibs/ietf/GMPLS-TC-STD-MIB.dic +180 -0
- data/lib/mibs/ietf/GMPLS-TE-STD-MIB.dic +2542 -0
- data/lib/mibs/ietf/GSMP-MIB.dic +2468 -0
- data/lib/mibs/ietf/HC-ALARM-MIB.dic +1050 -0
- data/lib/mibs/ietf/HC-PerfHist-TC-MIB.dic +310 -0
- data/lib/mibs/ietf/HC-RMON-MIB.dic +4456 -0
- data/lib/mibs/ietf/HDSL2-SHDSL-LINE-MIB.dic +3955 -0
- data/lib/mibs/ietf/HOST-RESOURCES-MIB.dic +2453 -0
- data/lib/mibs/ietf/HPR-IP-MIB.dic +640 -0
- data/lib/mibs/ietf/HPR-MIB.dic +1959 -0
- data/lib/mibs/ietf/IANA-ITU-ALARM-TC-MIB.dic +936 -0
- data/lib/mibs/ietf/IF-CAP-STACK-MIB.dic +356 -0
- data/lib/mibs/ietf/IF-INVERTED-STACK-MIB.dic +220 -0
- data/lib/mibs/ietf/IF-MIB.dic +2753 -0
- data/lib/mibs/ietf/IFCP-MGMT-MIB.dic +1717 -0
- data/lib/mibs/ietf/IGMP-STD-MIB.dic +809 -0
- data/lib/mibs/ietf/INET-ADDRESS-MIB.dic +570 -0
- data/lib/mibs/ietf/INTEGRATED-SERVICES-GUARANTEED-MIB.dic +319 -0
- data/lib/mibs/ietf/INTEGRATED-SERVICES-MIB.dic +1196 -0
- data/lib/mibs/ietf/INTERFACETOPN-MIB.dic +1705 -0
- data/lib/mibs/ietf/IP-FORWARD-MIB.dic +1853 -0
- data/lib/mibs/ietf/IP-MIB.dic +7064 -0
- data/lib/mibs/ietf/IPATM-IPMC-MIB.dic +4830 -0
- data/lib/mibs/ietf/IPFIX-MIB.dic +2334 -0
- data/lib/mibs/ietf/IPFIX-SELECTOR-MIB.dic +215 -0
- data/lib/mibs/ietf/IPMCAST-MIB.dic +3390 -0
- data/lib/mibs/ietf/IPMROUTE-STD-MIB.dic +1246 -0
- data/lib/mibs/ietf/IPOA-MIB.dic +2372 -0
- data/lib/mibs/ietf/IPS-AUTH-MIB.dic +1609 -0
- data/lib/mibs/ietf/IPSEC-SPD-MIB.dic +3989 -0
- data/lib/mibs/ietf/IPV6-FLOW-LABEL-MIB.dic +110 -0
- data/lib/mibs/ietf/IPV6-ICMP-MIB.dic +748 -0
- data/lib/mibs/ietf/IPV6-MIB.dic +2028 -0
- data/lib/mibs/ietf/IPV6-MLD-MIB.dic +659 -0
- data/lib/mibs/ietf/IPV6-TCP-MIB.dic +332 -0
- data/lib/mibs/ietf/IPV6-UDP-MIB.dic +209 -0
- data/lib/mibs/ietf/ISCSI-MIB.dic +4613 -0
- data/lib/mibs/ietf/ISDN-MIB.dic +1796 -0
- data/lib/mibs/ietf/ISIS-MIB.dic +6215 -0
- data/lib/mibs/ietf/ISNS-MIB.dic +6578 -0
- data/lib/mibs/ietf/ITU-ALARM-MIB.dic +665 -0
- data/lib/mibs/ietf/ITU-ALARM-TC-MIB.dic +137 -0
- data/lib/mibs/ietf/Job-Monitoring-MIB.dic +2519 -0
- data/lib/mibs/ietf/L2TP-MIB.dic +4050 -0
- data/lib/mibs/ietf/LANGTAG-TC-MIB.dic +104 -0
- data/lib/mibs/ietf/LISP-MIB.dic +4067 -0
- data/lib/mibs/ietf/LMP-MIB.dic +5166 -0
- data/lib/mibs/ietf/MALLOC-MIB.dic +2156 -0
- data/lib/mibs/ietf/MAU-MIB.dic +2619 -0
- data/lib/mibs/ietf/MIDCOM-MIB.dic +2856 -0
- data/lib/mibs/ietf/MIOX25-MIB.dic +828 -0
- data/lib/mibs/ietf/MIP-MIB.dic +3473 -0
- data/lib/mibs/ietf/MOBILEIPV6-MIB.dic +5228 -0
- data/lib/mibs/ietf/MPLS-FTN-STD-MIB.dic +1594 -0
- data/lib/mibs/ietf/MPLS-L3VPN-STD-MIB.dic +2548 -0
- data/lib/mibs/ietf/MPLS-LC-ATM-STD-MIB.dic +491 -0
- data/lib/mibs/ietf/MPLS-LC-FR-STD-MIB.dic +395 -0
- data/lib/mibs/ietf/MPLS-LDP-ATM-STD-MIB.dic +1019 -0
- data/lib/mibs/ietf/MPLS-LDP-FRAME-RELAY-STD-MIB.dic +862 -0
- data/lib/mibs/ietf/MPLS-LDP-GENERIC-STD-MIB.dic +445 -0
- data/lib/mibs/ietf/MPLS-LDP-STD-MIB.dic +3657 -0
- data/lib/mibs/ietf/MPLS-LSR-STD-MIB.dic +3103 -0
- data/lib/mibs/ietf/MPLS-TC-STD-MIB.dic +911 -0
- data/lib/mibs/ietf/MPLS-TE-STD-MIB.dic +3673 -0
- data/lib/mibs/ietf/MSDP-MIB.dic +1893 -0
- data/lib/mibs/ietf/MTA-MIB.dic +1898 -0
- data/lib/mibs/ietf/Modem-MIB.dic +2054 -0
- data/lib/mibs/ietf/NAT-MIB.dic +3866 -0
- data/lib/mibs/ietf/NETWORK-SERVICES-MIB.dic +1034 -0
- data/lib/mibs/ietf/NHDP-MIB.dic +3005 -0
- data/lib/mibs/ietf/NHRP-MIB.dic +3660 -0
- data/lib/mibs/ietf/NOTIFICATION-LOG-MIB.dic +1156 -0
- data/lib/mibs/ietf/NTPv4-MIB.dic +1535 -0
- data/lib/mibs/ietf/OPT-IF-MIB.dic +8972 -0
- data/lib/mibs/ietf/OSPF-MIB.dic +5963 -0
- data/lib/mibs/ietf/OSPF-TRAP-MIB.dic +1190 -0
- data/lib/mibs/ietf/OSPFV3-MIB.dic +5708 -0
- data/lib/mibs/ietf/P-BRIDGE-MIB.dic +1499 -0
- data/lib/mibs/ietf/PARALLEL-MIB.dic +476 -0
- data/lib/mibs/ietf/PIM-MIB.dic +1393 -0
- data/lib/mibs/ietf/PIM-STD-MIB.dic +6819 -0
- data/lib/mibs/ietf/PINT-MIB.dic +830 -0
- data/lib/mibs/ietf/PKTC-IETF-MTA-MIB.dic +3191 -0
- data/lib/mibs/ietf/PKTC-IETF-SIG-MIB.dic +4713 -0
- data/lib/mibs/ietf/PMIPV6-MIB.dic +3010 -0
- data/lib/mibs/ietf/PMIPV6-TC-MIB.dic +293 -0
- data/lib/mibs/ietf/POLICY-BASED-MANAGEMENT-MIB.dic +3316 -0
- data/lib/mibs/ietf/POWER-ETHERNET-MIB.dic +959 -0
- data/lib/mibs/ietf/PPP-BRIDGE-NCP-MIB.dic +587 -0
- data/lib/mibs/ietf/PPP-IP-NCP-MIB.dic +269 -0
- data/lib/mibs/ietf/PPP-LCP-MIB.dic +994 -0
- data/lib/mibs/ietf/PPP-SEC-MIB.dic +411 -0
- data/lib/mibs/ietf/PSAMP-MIB.dic +998 -0
- data/lib/mibs/ietf/PTOPO-MIB.dic +1135 -0
- data/lib/mibs/ietf/PW-ATM-MIB.dic +1642 -0
- data/lib/mibs/ietf/PW-CEP-STD-MIB.dic +3661 -0
- data/lib/mibs/ietf/PW-STD-MIB.dic +3592 -0
- data/lib/mibs/ietf/PW-TC-STD-MIB.dic +437 -0
- data/lib/mibs/ietf/PW-TDM-MIB.dic +1896 -0
- data/lib/mibs/ietf/PerfHist-TC-MIB.dic +152 -0
- data/lib/mibs/ietf/Printer-MIB.dic +6665 -0
- data/lib/mibs/ietf/Q-BRIDGE-MIB.dic +3115 -0
- data/lib/mibs/ietf/RADIUS-ACC-CLIENT-MIB.dic +991 -0
- data/lib/mibs/ietf/RADIUS-ACC-SERVER-MIB.dic +1183 -0
- data/lib/mibs/ietf/RADIUS-AUTH-CLIENT-MIB.dic +1073 -0
- data/lib/mibs/ietf/RADIUS-AUTH-SERVER-MIB.dic +1251 -0
- data/lib/mibs/ietf/RADIUS-DYNAUTH-CLIENT-MIB.dic +1116 -0
- data/lib/mibs/ietf/RADIUS-DYNAUTH-SERVER-MIB.dic +1003 -0
- data/lib/mibs/ietf/RAQMON-MIB.dic +2695 -0
- data/lib/mibs/ietf/RBRIDGE-MIB.dic +2981 -0
- data/lib/mibs/ietf/RDBMS-MIB.dic +1935 -0
- data/lib/mibs/ietf/RFC1065-SMI.dic +108 -0
- data/lib/mibs/ietf/RFC1155-SMI.dic +118 -0
- data/lib/mibs/ietf/RFC1158-MIB.dic +2440 -0
- data/lib/mibs/ietf/RFC1213-MIB.dic +3434 -0
- data/lib/mibs/ietf/RFC1269-MIB.dic +557 -0
- data/lib/mibs/ietf/RFC1271-MIB.dic +4135 -0
- data/lib/mibs/ietf/RFC1285-MIB.dic +2842 -0
- data/lib/mibs/ietf/RFC1316-MIB.dic +800 -0
- data/lib/mibs/ietf/RFC1381-MIB.dic +1347 -0
- data/lib/mibs/ietf/RFC1382-MIB.dic +3820 -0
- data/lib/mibs/ietf/RFC1414-MIB.dic +214 -0
- data/lib/mibs/ietf/RIPv2-MIB.dic +773 -0
- data/lib/mibs/ietf/RMON-MIB.dic +5551 -0
- data/lib/mibs/ietf/RMON2-MIB.dic +8224 -0
- data/lib/mibs/ietf/ROHC-MIB.dic +1613 -0
- data/lib/mibs/ietf/ROHC-RTP-MIB.dic +859 -0
- data/lib/mibs/ietf/ROHC-UNCOMPRESSED-MIB.dic +267 -0
- data/lib/mibs/ietf/RPKI-ROUTER-MIB.dic +1363 -0
- data/lib/mibs/ietf/RS-232-MIB.dic +1335 -0
- data/lib/mibs/ietf/RSERPOOL-MIB.dic +2501 -0
- data/lib/mibs/ietf/RSTP-MIB.dic +427 -0
- data/lib/mibs/ietf/RSVP-MIB.dic +4135 -0
- data/lib/mibs/ietf/RTP-MIB.dic +1376 -0
- data/lib/mibs/ietf/SCSI-MIB.dic +3804 -0
- data/lib/mibs/ietf/SCTP-MIB.dic +1924 -0
- data/lib/mibs/ietf/SFLOW-MIB.dic +568 -0
- data/lib/mibs/ietf/SIP-COMMON-MIB.dic +2769 -0
- data/lib/mibs/ietf/SIP-MIB.dic +1438 -0
- data/lib/mibs/ietf/SIP-SERVER-MIB.dic +1150 -0
- data/lib/mibs/ietf/SIP-TC-MIB.dic +257 -0
- data/lib/mibs/ietf/SIP-UA-MIB.dic +268 -0
- data/lib/mibs/ietf/SLAPM-MIB.dic +4527 -0
- data/lib/mibs/ietf/SMON-MIB.dic +1758 -0
- data/lib/mibs/ietf/SNA-NAU-MIB.dic +4042 -0
- data/lib/mibs/ietf/SNA-SDLC-MIB.dic +3858 -0
- data/lib/mibs/ietf/SNMP-COMMUNITY-MIB.dic +715 -0
- data/lib/mibs/ietf/SNMP-FRAMEWORK-MIB.dic +709 -0
- data/lib/mibs/ietf/SNMP-MPD-MIB.dic +230 -0
- data/lib/mibs/ietf/SNMP-NOTIFICATION-MIB.dic +859 -0
- data/lib/mibs/ietf/SNMP-PROXY-MIB.dic +414 -0
- data/lib/mibs/ietf/SNMP-REPEATER-MIB.dic +4335 -0
- data/lib/mibs/ietf/SNMP-SSH-TM-MIB.dic +447 -0
- data/lib/mibs/ietf/SNMP-TARGET-MIB.dic +924 -0
- data/lib/mibs/ietf/SNMP-TLS-TM-MIB.dic +1449 -0
- data/lib/mibs/ietf/SNMP-TSM-MIB.dic +315 -0
- data/lib/mibs/ietf/SNMP-USER-BASED-SM-MIB.dic +1164 -0
- data/lib/mibs/ietf/SNMP-USM-AES-MIB.dic +95 -0
- data/lib/mibs/ietf/SNMP-USM-DH-OBJECTS-MIB.dic +653 -0
- data/lib/mibs/ietf/SNMP-VIEW-BASED-ACM-MIB.dic +1202 -0
- data/lib/mibs/ietf/SNMPv2-MIB.dic +1382 -0
- data/lib/mibs/ietf/SNMPv2-SMI.dic +223 -0
- data/lib/mibs/ietf/SNMPv2-USEC-MIB.dic +405 -0
- data/lib/mibs/ietf/SONET-MIB.dic +3308 -0
- data/lib/mibs/ietf/SOURCE-ROUTING-MIB.dic +542 -0
- data/lib/mibs/ietf/SSPM-MIB.dic +1530 -0
- data/lib/mibs/ietf/SYSAPPL-MIB.dic +2092 -0
- data/lib/mibs/ietf/T11-FC-FABRIC-ADDR-MGR-MIB.dic +1779 -0
- data/lib/mibs/ietf/T11-FC-FABRIC-CONFIG-SERVER-MIB.dic +2822 -0
- data/lib/mibs/ietf/T11-FC-FABRIC-LOCK-MIB.dic +700 -0
- data/lib/mibs/ietf/T11-FC-FSPF-MIB.dic +1889 -0
- data/lib/mibs/ietf/T11-FC-NAME-SERVER-MIB.dic +1775 -0
- data/lib/mibs/ietf/T11-FC-ROUTE-MIB.dic +655 -0
- data/lib/mibs/ietf/T11-FC-RSCN-MIB.dic +1110 -0
- data/lib/mibs/ietf/T11-FC-VIRTUAL-FABRIC-MIB.dic +770 -0
- data/lib/mibs/ietf/T11-FC-ZONE-SERVER-MIB.dic +3886 -0
- data/lib/mibs/ietf/T11-TC-MIB.dic +110 -0
- data/lib/mibs/ietf/TCP-ESTATS-MIB.dic +3926 -0
- data/lib/mibs/ietf/TCP-MIB.dic +1319 -0
- data/lib/mibs/ietf/TCPIPX-MIB.dic +457 -0
- data/lib/mibs/ietf/TE-LINK-STD-MIB.dic +2876 -0
- data/lib/mibs/ietf/TE-MIB.dic +2924 -0
- data/lib/mibs/ietf/TED-MIB.dic +1749 -0
- data/lib/mibs/ietf/TIME-AGGREGATE-MIB.dic +550 -0
- data/lib/mibs/ietf/TN3270E-MIB.dic +2785 -0
- data/lib/mibs/ietf/TN3270E-RT-MIB.dic +1317 -0
- data/lib/mibs/ietf/TOKEN-RING-RMON-MIB.dic +2820 -0
- data/lib/mibs/ietf/TOKENRING-MIB.dic +1184 -0
- data/lib/mibs/ietf/TOKENRING-STATION-SR-MIB.dic +292 -0
- data/lib/mibs/ietf/TRANSPORT-ADDRESS-MIB.dic +610 -0
- data/lib/mibs/ietf/TRIP-MIB.dic +3159 -0
- data/lib/mibs/ietf/TRIP-TC-MIB.dic +241 -0
- data/lib/mibs/ietf/TUNNEL-MIB.dic +1095 -0
- data/lib/mibs/ietf/UDP-MIB.dic +751 -0
- data/lib/mibs/ietf/UDPLITE-MIB.dic +704 -0
- data/lib/mibs/ietf/UPS-MIB.dic +3088 -0
- data/lib/mibs/ietf/URI-TC-MIB.dic +193 -0
- data/lib/mibs/ietf/UUID-TC-MIB.dic +135 -0
- data/lib/mibs/ietf/VDSL-LINE-EXT-MCM-MIB.dic +989 -0
- data/lib/mibs/ietf/VDSL-LINE-EXT-SCM-MIB.dic +605 -0
- data/lib/mibs/ietf/VDSL-LINE-MIB.dic +4518 -0
- data/lib/mibs/ietf/VDSL2-LINE-MIB.dic +11029 -0
- data/lib/mibs/ietf/VDSL2-LINE-TC-MIB.dic +3152 -0
- data/lib/mibs/ietf/VPN-TC-STD-MIB.dic +121 -0
- data/lib/mibs/ietf/VRRP-MIB.dic +1163 -0
- data/lib/mibs/ietf/VRRPV3-MIB.dic +1403 -0
- data/lib/mibs/ietf/WWW-MIB.dic +1810 -0
- data/lib/mibs/logstash/iso.dic +18 -0
- data/logstash-input-snmp.gemspec +1 -1
- data/spec/inputs/snmp/mib_spec.rb +10 -17
- data/spec/inputs/snmp_spec.rb +27 -1
- metadata +302 -2
@@ -0,0 +1,700 @@
|
|
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 T11-FC-FABRIC-LOCK-MIB
|
6
|
+
|
7
|
+
FILENAME = "./libsmi-0.5.0/mibs/ietf/T11-FC-FABRIC-LOCK-MIB"
|
8
|
+
|
9
|
+
MIB = {
|
10
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
11
|
+
|
12
|
+
"T11-FC-FABRIC-LOCK-MIB" : {
|
13
|
+
"nodetype" : "module",
|
14
|
+
"language" : "SMIv2",
|
15
|
+
"organization" :
|
16
|
+
"""For the initial versions, T11.
|
17
|
+
For later versions, the IETF's IMSS Working Group.""",
|
18
|
+
"contact" :
|
19
|
+
""" Claudio DeSanti
|
20
|
+
Cisco Systems, Inc.
|
21
|
+
170 West Tasman Drive
|
22
|
+
San Jose, CA 95134 USA
|
23
|
+
EMail: cds@cisco.com
|
24
|
+
|
25
|
+
Keith McCloghrie
|
26
|
+
|
27
|
+
|
28
|
+
|
29
|
+
Cisco Systems, Inc.
|
30
|
+
170 West Tasman Drive
|
31
|
+
San Jose, CA 95134 USA
|
32
|
+
EMail: kzm@cisco.com""",
|
33
|
+
"description" :
|
34
|
+
"""The MIB module for the management of locks on a Fibre
|
35
|
+
Channel Fabric. A Fibre Channel Fabric lock is used to
|
36
|
+
ensure serialized access to some types of management data
|
37
|
+
related to a Fabric, e.g., the Fabric's Zoning Database.
|
38
|
+
|
39
|
+
Some (managing) applications generate Fabric locks by
|
40
|
+
initiating server sessions. Server sessions are
|
41
|
+
defined generically in FC-GS-5 to represent a collection of
|
42
|
+
one or more requests to the session's server, e.g., to the
|
43
|
+
Zone Server. Such a session is started by a Server Session
|
44
|
+
Begin (SSB) request, and terminated by a Server Session End
|
45
|
+
(SSE) request. The switch receiving the SSB is called the
|
46
|
+
'managing' switch. Some applications require the
|
47
|
+
'managing' switch to lock the Fabric for the particular
|
48
|
+
application, e.g., for Enhanced Zoning, before it can
|
49
|
+
respond successfully to the SSB. On receipt of the
|
50
|
+
subsequent SSE, the lock is released. For this usage, the
|
51
|
+
managing switch sends an Acquire Change Authorization (ACA)
|
52
|
+
request to other switches to lock the Fabric.
|
53
|
+
|
54
|
+
For some other applications, a managing switch locks the
|
55
|
+
Fabric using an Enhanced Acquire Change Authorization (EACA)
|
56
|
+
request, which identifies the application on whose behalf
|
57
|
+
the Fabric is being locked with an Application_ID.
|
58
|
+
|
59
|
+
Fabric locks can also be requested more directly, e.g.,
|
60
|
+
through the use of this MIB. In these situations, the term
|
61
|
+
'managing' switch is used to indicate the switch that
|
62
|
+
receives such a request and executes it by issuing either
|
63
|
+
ACA or EACA requests to other switches in the Fabric.
|
64
|
+
|
65
|
+
This MIB module defines information about the 'managing'
|
66
|
+
switch for currently-active Fabric locks.
|
67
|
+
|
68
|
+
Copyright (C) The IETF Trust (2007). This version
|
69
|
+
of this MIB module is part of RFC 4936; see the RFC
|
70
|
+
itself for full legal notices.""",
|
71
|
+
"revisions" : (
|
72
|
+
{
|
73
|
+
"date" : "2007-06-27 00:00",
|
74
|
+
"description" :
|
75
|
+
"""Initial version of this MIB module, published as RFC 4936.""",
|
76
|
+
},
|
77
|
+
),
|
78
|
+
"identity node" : "t11FabricLockMIB",
|
79
|
+
},
|
80
|
+
|
81
|
+
"imports" : (
|
82
|
+
{"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
|
83
|
+
{"module" : "SNMPv2-SMI", "name" : "OBJECT-TYPE"},
|
84
|
+
{"module" : "SNMPv2-SMI", "name" : "mib-2"},
|
85
|
+
{"module" : "SNMPv2-TC", "name" : "RowStatus"},
|
86
|
+
{"module" : "SNMPv2-CONF", "name" : "MODULE-COMPLIANCE"},
|
87
|
+
{"module" : "SNMPv2-CONF", "name" : "OBJECT-GROUP"},
|
88
|
+
{"module" : "INET-ADDRESS-MIB", "name" : "InetAddressType"},
|
89
|
+
{"module" : "INET-ADDRESS-MIB", "name" : "InetAddress"},
|
90
|
+
{"module" : "FC-MGMT-MIB", "name" : "fcmInstanceIndex"},
|
91
|
+
{"module" : "FC-MGMT-MIB", "name" : "fcmSwitchIndex"},
|
92
|
+
{"module" : "T11-FC-NAME-SERVER-MIB", "name" : "T11NsGs4RejectReasonCode"},
|
93
|
+
{"module" : "T11-TC-MIB", "name" : "T11FabricIndex"},
|
94
|
+
),
|
95
|
+
|
96
|
+
"nodes" : {
|
97
|
+
"t11FabricLockMIB" : {
|
98
|
+
"nodetype" : "node",
|
99
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
100
|
+
"oid" : "1.3.6.1.2.1.159",
|
101
|
+
"status" : "current",
|
102
|
+
}, # node
|
103
|
+
"t11FLockMIBNotifications" : {
|
104
|
+
"nodetype" : "node",
|
105
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
106
|
+
"oid" : "1.3.6.1.2.1.159.0",
|
107
|
+
}, # node
|
108
|
+
"t11FLockMIBObjects" : {
|
109
|
+
"nodetype" : "node",
|
110
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
111
|
+
"oid" : "1.3.6.1.2.1.159.1",
|
112
|
+
}, # node
|
113
|
+
"t11FLockConfiguration" : {
|
114
|
+
"nodetype" : "node",
|
115
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
116
|
+
"oid" : "1.3.6.1.2.1.159.1.1",
|
117
|
+
}, # node
|
118
|
+
"t11FLockTable" : {
|
119
|
+
"nodetype" : "table",
|
120
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
121
|
+
"oid" : "1.3.6.1.2.1.159.1.1.1",
|
122
|
+
"status" : "current",
|
123
|
+
"description" :
|
124
|
+
"""A table containing information about the 'managing'
|
125
|
+
switch of each current Fabric lock, e.g., for the
|
126
|
+
types of Servers defined in FC-GS-5.
|
127
|
+
|
128
|
+
Each entry in this table represents either:
|
129
|
+
|
130
|
+
1) a current Fabric lock,
|
131
|
+
2) an in-progress attempt, requested via SNMP, to set up
|
132
|
+
a lock, or
|
133
|
+
3) a failed attempt, requested via SNMP, to set up a lock.
|
134
|
+
|
135
|
+
If an entry is created via t11FLockRowStatus, but the
|
136
|
+
attempt to obtain the lock fails, then the entry continues
|
137
|
+
to exist until it is deleted via t11FLockRowStatus, or
|
138
|
+
it is overwritten by the lock being established via
|
139
|
+
a means other than SNMP. However, rows created via
|
140
|
+
t11FLockRowStatus are not retained over restarts.""",
|
141
|
+
"reference" :
|
142
|
+
"""Fibre Channel - Generic Services-5 (FC-GS-5),
|
143
|
+
ANSI INCITS 427-2007, sections 4.9.5 and 6.4.10.2.""",
|
144
|
+
}, # table
|
145
|
+
"t11FLockEntry" : {
|
146
|
+
"nodetype" : "row",
|
147
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
148
|
+
"oid" : "1.3.6.1.2.1.159.1.1.1.1",
|
149
|
+
"create" : "true",
|
150
|
+
"status" : "current",
|
151
|
+
"linkage" : [
|
152
|
+
"fcmInstanceIndex",
|
153
|
+
"fcmSwitchIndex",
|
154
|
+
"t11FLockFabricIndex",
|
155
|
+
"t11FLockApplicationID",
|
156
|
+
],
|
157
|
+
"description" :
|
158
|
+
"""Each entry contains information specific to a current
|
159
|
+
Fabric lock set up by a particular 'managing' switch on a
|
160
|
+
particular Fabric. The 'managing switch' is identified by
|
161
|
+
values of fcmInstanceIndex and fcmSwitchIndex.
|
162
|
+
|
163
|
+
Server sessions for several different types of servers
|
164
|
+
are defined in FC-GS-5. The behavior of a server with
|
165
|
+
|
166
|
+
|
167
|
+
|
168
|
+
respect to commands received within a server session is
|
169
|
+
specified for each type of server. For some types,
|
170
|
+
parameter changes can only be made within the context of a
|
171
|
+
session, and the setting up of a session requires that the
|
172
|
+
Fabric be locked. A Fabric is locked by one switch, called
|
173
|
+
the 'managing' switch, sending Acquire Change Authorization
|
174
|
+
(ACA) requests to all other switches in the Fabric.
|
175
|
+
|
176
|
+
For other applications, a Fabric lock is established by the
|
177
|
+
'managing' switch sending Enhanced Acquire Change
|
178
|
+
Authorization (EACA) requests to other switches in the
|
179
|
+
Fabric. Each EACA request includes an Application_ID
|
180
|
+
value to identify the application requesting the lock.
|
181
|
+
|
182
|
+
For the benefit of this MIB module, a distinct value of
|
183
|
+
Application_ID has also been assigned/reserved (see
|
184
|
+
ANSI INCITS T11/06-679v0, titled 'FC-SW-5 Letter to
|
185
|
+
T11.5') as a means of distinguishing locks established via
|
186
|
+
Acquire Change Authorization (ACA) requests. This
|
187
|
+
additional assignment allows an Application_ID to be used to
|
188
|
+
uniquely identify any active lock amongst all those
|
189
|
+
established by either an EACA or an ACA.
|
190
|
+
|
191
|
+
Whenever a Fabric is locked, by the sending of either an ACA
|
192
|
+
or an EACA, a row gets created in the representation of this
|
193
|
+
table for the 'managing' switch.
|
194
|
+
|
195
|
+
In order to process SNMP SetRequests that make parameter
|
196
|
+
changes for the relevant types of servers (e.g., to the
|
197
|
+
Zoning Database), the SNMP agent must get serialized access
|
198
|
+
to the Fabric (for the relevant type of management data),
|
199
|
+
i.e., the Fabric must be locked by creating an entry in
|
200
|
+
this table via an SNMP SetRequest. Creating an entry in
|
201
|
+
this table via an SNMP SetRequest causes an ACA or an EACA
|
202
|
+
to be sent to all other switches in the Fabric. The value
|
203
|
+
of t11FLockApplicationID for such an entry determines
|
204
|
+
whether an ACA or an EACA is sent.
|
205
|
+
|
206
|
+
If an entry in this table is created by an SNMP SetRequest,
|
207
|
+
the value of the t11FLockInitiatorType object in that entry
|
208
|
+
will normally be 'snmp'. A row for which the value of
|
209
|
+
t11FLockInitiatorType is not 'snmp' cannot be modified
|
210
|
+
via SNMP. In particular, it cannot be deleted via
|
211
|
+
t11FLockRowStatus. Note that it's possible for a row to be
|
212
|
+
created by an SNMP SetRequest, but for the setup of the lock
|
213
|
+
to fail, and immediately thereafter be replaced by a lock
|
214
|
+
successfully set up by some other means; in such a case, the
|
215
|
+
value of t11FLockInitiatorType would change as and when the
|
216
|
+
|
217
|
+
|
218
|
+
|
219
|
+
lock was set up by the other means, and so the row could
|
220
|
+
not thereafter be deleted via t11FLockRowStatus.
|
221
|
+
|
222
|
+
FC-GS-5 mentions various error situations in which a
|
223
|
+
Fabric lock is released so as to avoid a deadlock. In
|
224
|
+
such situations, the agent removes the corresponding row
|
225
|
+
in this table as and when the lock is released. This can
|
226
|
+
happen for all values of t11FLockInitiatorType.""",
|
227
|
+
"reference" :
|
228
|
+
"""Fibre Channel - Generic Services-5 (FC-GS-5),
|
229
|
+
ANSI INCITS 427-2007, sections 4.9.5.5 and 6.4.7.1.
|
230
|
+
|
231
|
+
Fibre Channel - Switch Fabric-4 (FC-SW-4),
|
232
|
+
ANSI INCITS 418-2006, sections 6.1.17, 10.6.6, and 13.2,
|
233
|
+
and table 116.
|
234
|
+
|
235
|
+
'FC-SW-5 Letter to T11.5' ANSI INCITS T11/06-679v0,
|
236
|
+
http://www.t11.org/ftp/t11/pub/fc/sw-5/06-679v0.pdf,
|
237
|
+
21 September 2006.""",
|
238
|
+
}, # row
|
239
|
+
"t11FLockFabricIndex" : {
|
240
|
+
"nodetype" : "column",
|
241
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
242
|
+
"oid" : "1.3.6.1.2.1.159.1.1.1.1.1",
|
243
|
+
"status" : "current",
|
244
|
+
"syntax" : {
|
245
|
+
"type" : { "module" :"T11-TC-MIB", "name" : "T11FabricIndex"},
|
246
|
+
},
|
247
|
+
"access" : "noaccess",
|
248
|
+
"description" :
|
249
|
+
"""A unique index value that uniquely identifies a
|
250
|
+
particular Fabric.
|
251
|
+
|
252
|
+
In a Fabric conformant to FC-SW-4, multiple Virtual Fabrics
|
253
|
+
can operate within one (or more) physical infrastructures,
|
254
|
+
and this index value is used to uniquely identify a
|
255
|
+
|
256
|
+
|
257
|
+
|
258
|
+
particular (physical or virtual) Fabric within a physical
|
259
|
+
infrastructure.
|
260
|
+
|
261
|
+
In a Fabric conformant to versions earlier than FC-SW-4,
|
262
|
+
only a single Fabric could operate within a physical
|
263
|
+
infrastructure, and thus, the value of this Fabric Index
|
264
|
+
was defined to always be 1.""",
|
265
|
+
}, # column
|
266
|
+
"t11FLockApplicationID" : {
|
267
|
+
"nodetype" : "column",
|
268
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
269
|
+
"oid" : "1.3.6.1.2.1.159.1.1.1.1.2",
|
270
|
+
"status" : "current",
|
271
|
+
"syntax" : {
|
272
|
+
"type" : {
|
273
|
+
"basetype" : "OctetString",
|
274
|
+
"ranges" : [
|
275
|
+
{
|
276
|
+
"min" : "1",
|
277
|
+
"max" : "1"
|
278
|
+
},
|
279
|
+
],
|
280
|
+
"range" : {
|
281
|
+
"min" : "1",
|
282
|
+
"max" : "1"
|
283
|
+
},
|
284
|
+
},
|
285
|
+
},
|
286
|
+
"access" : "noaccess",
|
287
|
+
"description" :
|
288
|
+
"""The Application_ID value that identifies the type of
|
289
|
+
application for which the Fabric is locked.
|
290
|
+
|
291
|
+
A lock established via Acquire Change Authorization (ACA)
|
292
|
+
does not, strictly speaking, have an Application_ID value.
|
293
|
+
However, the value 'FF'h (255 decimal) has been reserved
|
294
|
+
by T11 to be used as the value of this MIB object as and
|
295
|
+
when a lock is established by an ACA. This value was
|
296
|
+
initially documented in a letter from the FC-SW-5 Editor
|
297
|
+
to T11.5, which was approved by the T11 and T11.5 plenary
|
298
|
+
meetings on October 5, 2006.""",
|
299
|
+
"reference" :
|
300
|
+
"""Fibre Channel - Switch Fabric-4 (FC-SW-4),
|
301
|
+
ANSI INCITS 418-2006, April 2006, Table 116.
|
302
|
+
|
303
|
+
'FC-SW-5 Letter to T11.5' ANSI INCITS T11/06-679v0,
|
304
|
+
http://www.t11.org/ftp/t11/pub/fc/sw-5/06-679v0.pdf,
|
305
|
+
21 September 2006.""",
|
306
|
+
}, # column
|
307
|
+
"t11FLockInitiatorType" : {
|
308
|
+
"nodetype" : "column",
|
309
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
310
|
+
"oid" : "1.3.6.1.2.1.159.1.1.1.1.3",
|
311
|
+
"status" : "current",
|
312
|
+
"syntax" : {
|
313
|
+
"type" : {
|
314
|
+
"basetype" : "Enumeration",
|
315
|
+
"other" : {
|
316
|
+
"nodetype" : "namednumber",
|
317
|
+
"number" : "1"
|
318
|
+
},
|
319
|
+
"ssb" : {
|
320
|
+
"nodetype" : "namednumber",
|
321
|
+
"number" : "2"
|
322
|
+
},
|
323
|
+
"cli" : {
|
324
|
+
"nodetype" : "namednumber",
|
325
|
+
"number" : "3"
|
326
|
+
},
|
327
|
+
"snmp" : {
|
328
|
+
"nodetype" : "namednumber",
|
329
|
+
"number" : "4"
|
330
|
+
},
|
331
|
+
},
|
332
|
+
},
|
333
|
+
"access" : "readonly",
|
334
|
+
"description" :
|
335
|
+
"""This object specifies what type of initiator generated
|
336
|
+
the request that caused this lock to be established:
|
337
|
+
|
338
|
+
other - none of the following.
|
339
|
+
|
340
|
+
|
341
|
+
|
342
|
+
ssb - this lock was established due to the
|
343
|
+
receipt of an SSB, e.g., from a GS-5
|
344
|
+
client.
|
345
|
+
cli - this lock was established in order
|
346
|
+
to process a Command Line Interface
|
347
|
+
(CLI) command.
|
348
|
+
snmp - this lock was established as a result
|
349
|
+
of an SNMP SetRequest.""",
|
350
|
+
}, # column
|
351
|
+
"t11FLockInitiator" : {
|
352
|
+
"nodetype" : "column",
|
353
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
354
|
+
"oid" : "1.3.6.1.2.1.159.1.1.1.1.4",
|
355
|
+
"status" : "current",
|
356
|
+
"syntax" : {
|
357
|
+
"type" : {
|
358
|
+
"basetype" : "OctetString",
|
359
|
+
"ranges" : [
|
360
|
+
{
|
361
|
+
"min" : "0",
|
362
|
+
"max" : "64"
|
363
|
+
},
|
364
|
+
],
|
365
|
+
"range" : {
|
366
|
+
"min" : "0",
|
367
|
+
"max" : "64"
|
368
|
+
},
|
369
|
+
},
|
370
|
+
},
|
371
|
+
"access" : "readonly",
|
372
|
+
"description" :
|
373
|
+
"""This object specifies the initiator whose request
|
374
|
+
caused this lock to be established.
|
375
|
+
|
376
|
+
If the value of the corresponding instance
|
377
|
+
of t11FLockInitiatorType is 'ssb', this
|
378
|
+
object will contain the FC_ID of the client
|
379
|
+
that issued the Server Session Begin (SSB)
|
380
|
+
that required the lock to be established.
|
381
|
+
|
382
|
+
If the value of the corresponding instance
|
383
|
+
of t11FLockInitiatorType object is 'cli', this
|
384
|
+
object will contain the user name of the CLI
|
385
|
+
(Command Line Interface) user on whose behalf
|
386
|
+
the lock was established.
|
387
|
+
|
388
|
+
If the value of the corresponding instance of
|
389
|
+
t11FLockInitiatorType is 'snmp', this object
|
390
|
+
will contain the SNMP securityName used by the
|
391
|
+
SNMPv3 message containing the SetRequest that
|
392
|
+
created this row. (If the row was created via
|
393
|
+
SNMPv1 or SNMPv2c, then the appropriate value of
|
394
|
+
the snmpCommunitySecurityName is used.)""",
|
395
|
+
"reference" :
|
396
|
+
"""Fibre Channel - Generic Services-5 (FC-GS-5),
|
397
|
+
ANSI INCITS 427-2007, section 4.9.5.2.
|
398
|
+
|
399
|
+
SNMP securityName is defined in RFC 3411, 'An
|
400
|
+
Architecture for Describing Simple Network
|
401
|
+
Management Protocol (SNMP) Management Frameworks'.
|
402
|
+
|
403
|
+
snmpCommunitySecurityName is defined in RFC 3584,
|
404
|
+
'Coexistence between Version 1, Version 2, and
|
405
|
+
|
406
|
+
|
407
|
+
|
408
|
+
Version 3 of the Internet-standard Network
|
409
|
+
Management Framework.'""",
|
410
|
+
}, # column
|
411
|
+
"t11FLockInitiatorIpAddrType" : {
|
412
|
+
"nodetype" : "column",
|
413
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
414
|
+
"oid" : "1.3.6.1.2.1.159.1.1.1.1.5",
|
415
|
+
"status" : "current",
|
416
|
+
"syntax" : {
|
417
|
+
"type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetAddressType"},
|
418
|
+
},
|
419
|
+
"access" : "readonly",
|
420
|
+
"description" :
|
421
|
+
"""This object specifies the type of IP address contained
|
422
|
+
in the corresponding instance of t11FLockInitiatorIpAddr.
|
423
|
+
If the IP address of the location of the initiator is
|
424
|
+
unknown or not applicable, this object has the value:
|
425
|
+
'unknown'.""",
|
426
|
+
}, # column
|
427
|
+
"t11FLockInitiatorIpAddr" : {
|
428
|
+
"nodetype" : "column",
|
429
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
430
|
+
"oid" : "1.3.6.1.2.1.159.1.1.1.1.6",
|
431
|
+
"status" : "current",
|
432
|
+
"syntax" : {
|
433
|
+
"type" : { "module" :"INET-ADDRESS-MIB", "name" : "InetAddress"},
|
434
|
+
},
|
435
|
+
"access" : "readonly",
|
436
|
+
"description" :
|
437
|
+
"""This object specifies the IP address of the location
|
438
|
+
of the initiator that established this lock via a
|
439
|
+
request of the type given by the corresponding instance
|
440
|
+
of t11FLockInitiatorType. In cases where the
|
441
|
+
corresponding instance of t11FLockInitiatorIpAddrType has
|
442
|
+
the value: 'unknown', the value of this object is the
|
443
|
+
zero-length string.""",
|
444
|
+
}, # column
|
445
|
+
"t11FLockStatus" : {
|
446
|
+
"nodetype" : "column",
|
447
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
448
|
+
"oid" : "1.3.6.1.2.1.159.1.1.1.1.7",
|
449
|
+
"status" : "current",
|
450
|
+
"syntax" : {
|
451
|
+
"type" : {
|
452
|
+
"basetype" : "Enumeration",
|
453
|
+
"active" : {
|
454
|
+
"nodetype" : "namednumber",
|
455
|
+
"number" : "1"
|
456
|
+
},
|
457
|
+
"settingUp" : {
|
458
|
+
"nodetype" : "namednumber",
|
459
|
+
"number" : "2"
|
460
|
+
},
|
461
|
+
"rejectFailure" : {
|
462
|
+
"nodetype" : "namednumber",
|
463
|
+
"number" : "3"
|
464
|
+
},
|
465
|
+
"otherFailure" : {
|
466
|
+
"nodetype" : "namednumber",
|
467
|
+
"number" : "4"
|
468
|
+
},
|
469
|
+
},
|
470
|
+
},
|
471
|
+
"access" : "readonly",
|
472
|
+
"description" :
|
473
|
+
"""This object gives the current status of the lock:
|
474
|
+
|
475
|
+
'active' -- the lock is currently established.
|
476
|
+
'settingUp' -- the 'managing' switch is currently
|
477
|
+
attempting to set up the lock, e.g.,
|
478
|
+
it is waiting to receive Accepts
|
479
|
+
for ACAs from every switch in the
|
480
|
+
Fabric.
|
481
|
+
|
482
|
+
|
483
|
+
|
484
|
+
'rejectFailure' -- the 'managing' switch's attempt to
|
485
|
+
set up the lock was rejected with
|
486
|
+
the reason codes given by:
|
487
|
+
t11FLockRejectReasonCode,
|
488
|
+
t11FLockRejectReasonCodeExp and
|
489
|
+
t11FLockRejectReasonVendorCode.
|
490
|
+
'otherFailure' -- the 'managing' switch's attempt
|
491
|
+
to set up the lock failed (but no
|
492
|
+
reason codes are available).
|
493
|
+
|
494
|
+
For values of t11FLockInitiatorType other than 'snmp',
|
495
|
+
a row is only required to be instantiated in this table
|
496
|
+
when the value of this object is 'active'.
|
497
|
+
|
498
|
+
If the value of the corresponding instance of
|
499
|
+
t11FLockInitiatorType is 'snmp', the initial value of this
|
500
|
+
object when the row is first created is 'settingUp'. As
|
501
|
+
and when the setup succeeds, the value transitions to
|
502
|
+
'active'. If the setup fails, the value transitions to
|
503
|
+
either 'rejectFailure' or 'otherFailure'. Note that such a
|
504
|
+
failure value is overwritten on the next attempt to obtain
|
505
|
+
the lock, which could be immediately after the failure,
|
506
|
+
e.g., by a GS-5 client.
|
507
|
+
|
508
|
+
When the value of this object is 'rejectFailure', the
|
509
|
+
rejection's reason codes are given by the corresponding
|
510
|
+
values of t11FLockRejectReasonCode,
|
511
|
+
t11FLockRejectReasonCodeExp and
|
512
|
+
t11FLockRejectReasonVendorCode.""",
|
513
|
+
}, # column
|
514
|
+
"t11FLockRejectReasonCode" : {
|
515
|
+
"nodetype" : "column",
|
516
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
517
|
+
"oid" : "1.3.6.1.2.1.159.1.1.1.1.8",
|
518
|
+
"status" : "current",
|
519
|
+
"syntax" : {
|
520
|
+
"type" : { "module" :"T11-FC-NAME-SERVER-MIB", "name" : "T11NsGs4RejectReasonCode"},
|
521
|
+
},
|
522
|
+
"access" : "readonly",
|
523
|
+
"description" :
|
524
|
+
"""When the value of the corresponding instance of
|
525
|
+
t11FLockStatus is 'rejectFailure', this object contains
|
526
|
+
the rejection's reason code.""",
|
527
|
+
"reference" :
|
528
|
+
"""Fibre Channel - Generic Services-5 (FC-GS-5),
|
529
|
+
ANSI INCITS 427-2007, section 4.4.4 and table 10.""",
|
530
|
+
}, # column
|
531
|
+
"t11FLockRejectReasonCodeExp" : {
|
532
|
+
"nodetype" : "column",
|
533
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
534
|
+
"oid" : "1.3.6.1.2.1.159.1.1.1.1.9",
|
535
|
+
"status" : "current",
|
536
|
+
"syntax" : {
|
537
|
+
"type" : {
|
538
|
+
"basetype" : "OctetString",
|
539
|
+
"ranges" : [
|
540
|
+
{
|
541
|
+
"min" : "0",
|
542
|
+
"max" : "1"
|
543
|
+
},
|
544
|
+
],
|
545
|
+
"range" : {
|
546
|
+
"min" : "0",
|
547
|
+
"max" : "1"
|
548
|
+
},
|
549
|
+
},
|
550
|
+
},
|
551
|
+
"access" : "readonly",
|
552
|
+
"description" :
|
553
|
+
"""When the value of the corresponding instance of
|
554
|
+
t11FLockStatus is 'rejectFailure', this object contains
|
555
|
+
the rejection's reason code explanation.""",
|
556
|
+
"reference" :
|
557
|
+
"""Fibre Channel - Generic Services-5 (FC-GS-5),
|
558
|
+
ANSI INCITS 427-2007, sections 4.4.4 and 6.4.9,
|
559
|
+
tables 10 and 252.""",
|
560
|
+
}, # column
|
561
|
+
"t11FLockRejectReasonVendorCode" : {
|
562
|
+
"nodetype" : "column",
|
563
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
564
|
+
"oid" : "1.3.6.1.2.1.159.1.1.1.1.10",
|
565
|
+
"status" : "current",
|
566
|
+
"syntax" : {
|
567
|
+
"type" : {
|
568
|
+
"basetype" : "OctetString",
|
569
|
+
"ranges" : [
|
570
|
+
{
|
571
|
+
"min" : "0",
|
572
|
+
"max" : "1"
|
573
|
+
},
|
574
|
+
],
|
575
|
+
"range" : {
|
576
|
+
"min" : "0",
|
577
|
+
"max" : "1"
|
578
|
+
},
|
579
|
+
},
|
580
|
+
},
|
581
|
+
"access" : "readonly",
|
582
|
+
"description" :
|
583
|
+
"""When the value of the corresponding instance of
|
584
|
+
t11FLockStatus is 'rejectFailure', this object contains
|
585
|
+
the rejection's vendor-specific code.""",
|
586
|
+
"reference" :
|
587
|
+
"""Fibre Channel - Generic Services-5 (FC-GS-5),
|
588
|
+
ANSI INCITS 427-2007, section 4.4.4.""",
|
589
|
+
}, # column
|
590
|
+
"t11FLockRowStatus" : {
|
591
|
+
"nodetype" : "column",
|
592
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
593
|
+
"oid" : "1.3.6.1.2.1.159.1.1.1.1.11",
|
594
|
+
"status" : "current",
|
595
|
+
"syntax" : {
|
596
|
+
"type" : { "module" :"SNMPv2-TC", "name" : "RowStatus"},
|
597
|
+
},
|
598
|
+
"access" : "readwrite",
|
599
|
+
"description" :
|
600
|
+
"""The status of this conceptual row.
|
601
|
+
|
602
|
+
A row in this table can be modified or deleted via
|
603
|
+
this object only when the row's value of
|
604
|
+
t11FLockInitiatorType is 'snmp'.""",
|
605
|
+
}, # column
|
606
|
+
"t11FLockMIBConformance" : {
|
607
|
+
"nodetype" : "node",
|
608
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
609
|
+
"oid" : "1.3.6.1.2.1.159.2",
|
610
|
+
}, # node
|
611
|
+
"t11FLockMIBCompliances" : {
|
612
|
+
"nodetype" : "node",
|
613
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
614
|
+
"oid" : "1.3.6.1.2.1.159.2.1",
|
615
|
+
}, # node
|
616
|
+
"t11FLockMIBGroups" : {
|
617
|
+
"nodetype" : "node",
|
618
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
619
|
+
"oid" : "1.3.6.1.2.1.159.2.2",
|
620
|
+
}, # node
|
621
|
+
}, # nodes
|
622
|
+
|
623
|
+
"groups" : {
|
624
|
+
"t11FLockActiveGroup" : {
|
625
|
+
"nodetype" : "group",
|
626
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
627
|
+
"oid" : "1.3.6.1.2.1.159.2.2.1",
|
628
|
+
"status" : "current",
|
629
|
+
"members" : {
|
630
|
+
"t11FLockInitiatorType" : {
|
631
|
+
"nodetype" : "member",
|
632
|
+
"module" : "T11-FC-FABRIC-LOCK-MIB"
|
633
|
+
},
|
634
|
+
"t11FLockInitiator" : {
|
635
|
+
"nodetype" : "member",
|
636
|
+
"module" : "T11-FC-FABRIC-LOCK-MIB"
|
637
|
+
},
|
638
|
+
"t11FLockInitiatorIpAddrType" : {
|
639
|
+
"nodetype" : "member",
|
640
|
+
"module" : "T11-FC-FABRIC-LOCK-MIB"
|
641
|
+
},
|
642
|
+
"t11FLockInitiatorIpAddr" : {
|
643
|
+
"nodetype" : "member",
|
644
|
+
"module" : "T11-FC-FABRIC-LOCK-MIB"
|
645
|
+
},
|
646
|
+
"t11FLockStatus" : {
|
647
|
+
"nodetype" : "member",
|
648
|
+
"module" : "T11-FC-FABRIC-LOCK-MIB"
|
649
|
+
},
|
650
|
+
"t11FLockRejectReasonCode" : {
|
651
|
+
"nodetype" : "member",
|
652
|
+
"module" : "T11-FC-FABRIC-LOCK-MIB"
|
653
|
+
},
|
654
|
+
"t11FLockRejectReasonCodeExp" : {
|
655
|
+
"nodetype" : "member",
|
656
|
+
"module" : "T11-FC-FABRIC-LOCK-MIB"
|
657
|
+
},
|
658
|
+
"t11FLockRejectReasonVendorCode" : {
|
659
|
+
"nodetype" : "member",
|
660
|
+
"module" : "T11-FC-FABRIC-LOCK-MIB"
|
661
|
+
},
|
662
|
+
"t11FLockRowStatus" : {
|
663
|
+
"nodetype" : "member",
|
664
|
+
"module" : "T11-FC-FABRIC-LOCK-MIB"
|
665
|
+
},
|
666
|
+
}, # members
|
667
|
+
"description" :
|
668
|
+
"""A collection of objects containing information
|
669
|
+
about current Fabric locks.""",
|
670
|
+
}, # group
|
671
|
+
}, # groups
|
672
|
+
|
673
|
+
"compliances" : {
|
674
|
+
"t11FLockMIBCompliance" : {
|
675
|
+
"nodetype" : "compliance",
|
676
|
+
"moduleName" : "T11-FC-FABRIC-LOCK-MIB",
|
677
|
+
"oid" : "1.3.6.1.2.1.159.2.1.1",
|
678
|
+
"status" : "current",
|
679
|
+
"description" :
|
680
|
+
"""The compliance statement for entities that support
|
681
|
+
Fabric locks in support of GS-5 Server applications.""",
|
682
|
+
"requires" : {
|
683
|
+
"t11FLockActiveGroup" : {
|
684
|
+
"nodetype" : "mandatory",
|
685
|
+
"module" : "T11-FC-FABRIC-LOCK-MIB"
|
686
|
+
},
|
687
|
+
}, # requires
|
688
|
+
"refinements" : {
|
689
|
+
"t11FLockRowStatus" : {
|
690
|
+
"module" : "T11-FC-FABRIC-LOCK-MIB",
|
691
|
+
"access" : "readonly",
|
692
|
+
"description" :
|
693
|
+
"""Write access is not required.""",
|
694
|
+
},
|
695
|
+
}, # refinements
|
696
|
+
|
697
|
+
}, # compliance
|
698
|
+
}, # compliances
|
699
|
+
|
700
|
+
}
|