snmp4j-agent-2.3.2-distribution.zip_JAVA SNMP监控_SNMP 监控_snmp监控

-- -- @(#)JVM-MANAGEMENT-MIB.mib 1.32 04/07/16 -- -- Copyright 2004 Sun Microsystems, Inc. All rights reserved. -- This software is the proprietary information of Sun Microsystems, Inc. -- Use is subject to license terms. -- -- The JVM-MANAGEMENT-MIB Module -- -- See jvmManagementMIB MODULE-IDENTITY for a description overview. -- See conformance statements for mandatory objects -- JVM-MANAGEMENT-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32, Gauge32, Integer32, Counter64, enterprises FROM SNMPv2-SMI DisplayString, TEXTUAL-CONVENTION, RowPointer FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF; -- Module Identity ------------------ jvmMgtMIB MODULE-IDENTITY LAST-UPDATED "200403041800Z" -- Format is "YYYYMMDDhhmmZ" ORGANIZATION "Sun Microsystems, Inc." CONTACT-INFO "Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 1-800-555-9SUN or 1-650-960-1300 http://www.sun.com or contact your local support representative" DESCRIPTION "Copyright 2004 Sun Microsystems, Inc. All rights reserved. This module defines the MIB that provides access to the Java[tm] Virtual Machine monitoring data. This module is derived from the Java[tm] programming language APIs described in the java.lang.management package of Java[tm] 2, Standard Edition, 5.0. See the Java programming language APIs of JSR 163 for 'Monitoring and Management of the Java[TM] Virtual Machine' for more details. Where the Java programming language API uses long, or int, the MIB often uses the corresponding unsigned quantity - which is closer to the object semantics. In those cases, it often happens that the -1 value that might be used by the API to indicate an unknown/unimplemented value cannot be used. Instead the MIB uses the value 0, which stricly speaking cannot be distinguished from a valid value. In many cases however, a running system will have non-zero values, so using 0 instead of -1 to indicate an unknown quantity does not lose any functionality. " REVISION "200403041800Z" -- Format is "YYYYMMDDhhmmZ" DESCRIPTION " JVM-MANAGEMENT-MIB - JSR 163 Final Release 1.0 " ::= { standard jsr163(163) 1 } -- Enterprise OIDs ------------------ -- internet OBJECT IDENTIFIER ::= { iso(1) org(3) dod(6) 1 } -- private OBJECT IDENTIFIER ::= { internet 4 } -- enterprises OBJECT IDENTIFIER ::= { private 1 } sun OBJECT IDENTIFIER ::= { enterprises 42 } jmgt OBJECT IDENTIFIER ::= { sun products(2) 145 } -- experimental OBJECT IDENTIFIER ::= { jmgt 1 } standard OBJECT IDENTIFIER ::= { jmgt 3 } ---------------------------------------------------------------------------- -- Textual Conventions ---------------------- -- -- Note: Some of the TEXTUAL-CONVENTIONs defined in this module are -- OCTET STRING with a 1023 size limitation (SIZE(0..1023)). -- -- As per RFC2578, section 7.1.2. OCTET STRING: -- -- "The OCTET STRING type represents arbitrary binary or textual data. -- Although the SMI-specified size limitation for this type is 65535 -- octets, MIB designers should realize that there may be -- implementation and interoperability limitations for sizes in -- excess of 255 octets." -- -- As a consequence an agent implementing this MIB may decide to -- restrict this maximum size to a lesser value than 1023, provided that -- it makes it clear in an AGENT-CAPABILITY statement. -- ---------------------------------------------------------------------------- JvmUnsigned64TC ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A non-negative 64-bit bit integer, without counter semantics." -- We have cloned the Unsigned64TC defined in RFC 2564 rather -- than importing it because the JVM-MANAGEMENT-MIB and the -- APPLICATION-MIB are not related. -- REFERENCE "RFC 2564 - APPLICATION-MIB, Unsigned64TC." SYNTAX Counter64 JvmJavaObjectNameTC ::= TEXTUAL-CONVENTION DISPLAY-HINT "255a" STATUS current DESCRIPTION "An Object Name, as implemented by the java.lang.management API, which identify a runtime Object (e.g. a Class Loader, a Memory Manager, etc...). The name is assumed to be unique in the scope of the object's class. This object syntax is equivalent to a DisplayString, but with a a 1023 bytes size limits (instead of 255 for a DisplayString). Note that the SNMP agent may have to truncate the string returned by the underlying API if it does not fit in this type. (1023 bytes max). " SYNTAX OCTET STRING (SIZE (0..1023)) JvmPathElementTC ::= TEXTUAL-CONVENTION DISPLAY-HINT "255a" STATUS current DESCRIPTION "A file or directory element in a PATH/CLASSPATH/LIBRARY_PATH structure. This object syntax is equivalent to a DisplayString, but with a a 1023 bytes size limits (instead of 255 for a DisplayString). Note that the SNMP agent may have to truncate the string returned by the underlying API if it does not fit in this type. (1023 bytes max). " SYNTAX OCTET STRING (SIZE (0..1023)) JvmArgValueTC ::= TEXTUAL-CONVENTION DISPLAY-HINT "255a" STATUS current DESCRIPTION "A string representing an input argument. This object syntax is equivalent to a DisplayString, but with a a 1023 bytes size limits (instead of 255 for a DisplayString). Note that the SNMP agent may have to truncate the string returned by the underlying API if it does not fit in this type. (1023 bytes max). " SYNTAX OCTET STRING (SIZE (0..1023)) JvmVerboseLevelTC ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Defines whether the verbose flag for a feature is active. verbose: the flag is on. silent: the flag is off. " SYNTAX INTEGER { silent(1), verbose(2) } JvmImplSupportStateTC ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Defines whether a feature is supported or not. " SYNTAX INTEGER { unsupported(1), supported(2) } JvmImplOptFeatureStateTC ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Defines whether an optional feature is supported, enabled, or disabled. An optional feature can be: unsupported: The JVM does not support this feature. enabled : The JVM supports this feature, and it is enabled. disabled : The JVM supports this feature, and it is disabled. Only enabled(3) and disabled(4) may be supplied as values to a SET request. unsupported(1) can only be set internally by the agent. " SYNTAX INTEGER { unsupported(1), enabled(3), disabled(4) } JvmTimeMillis64TC ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An elapsed time, expressed in milli-seconds. This type is based on Counter64, but without its specific semantics. " SYNTAX Counter64 JvmTimeNanos64TC ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An elapsed tim