0N/A NETWORK-SERVICES-MIB DEFINITIONS ::= BEGIN
0N/A OBJECT-TYPE, Counter32, Gauge32, MODULE-IDENTITY, mib-2
2362N/A TimeStamp, TEXTUAL-CONVENTION
2362N/A MODULE-COMPLIANCE, OBJECT-GROUP
0N/A FROM SNMP-FRAMEWORK-MIB;
0N/A application MODULE-IDENTITY
0N/A LAST-UPDATED "200003030000Z"
0N/A ORGANIZATION "IETF Mail and Directory Management Working Group"
0N/A Postal: Innosoft International, Inc.
0N/A Tel: +1 626 919 3600
0N/A Fax: +1 626 919 3614
0N/A E-Mail: ned.freed@innosoft.com"
0N/A "The MIB module describing network service applications"
2693N/A "This revision, published in RFC 2788, changes a number of
6271N/A DisplayStrings to SnmpAdminStrings. Note that this change
0N/A is not strictly supported by SMIv2. However, the alternative
0N/A of deprecating the old objects and defining new objects
0N/A would have a more adverse impact on backward compatibility
0N/A and interoperability, given the particular semantics of
0N/A these objects. The defining reference for distinguished
0N/A names has also been updated from RFC 1779 to RFC 2253."
0N/A REVISION "199905120000Z"
0N/A "This revision fixes a few small technical problems found
0N/A in previous versions, mostly in regards to the conformance
0N/A groups for different versions of this MIB. No changes have
0N/A been made to the objects this MIB defines since RFC 2248."
0N/A REVISION "199708170000Z"
0N/A "This revision, published in RFC 2248, adds the
0N/A applDescription and applURL objects, adds the quiescing
0N/A state to the applOperStatus object and renames the MIB
0N/A from the APPLICATION-MIB to the NETWORK-SERVICE-MIB."
2693N/A "The original version of this MIB was published in RFC 1565"
0N/A -- Textual conventions
0N/A -- DistinguishedName is used to refer to objects in the
0N/A DistinguishedName ::= TEXTUAL-CONVENTION
0N/A "A Distinguished Name represented in accordance with
0N/A RFC 2253, presented in the UTF-8 charset defined in
0N/A SYNTAX OCTET STRING (SIZE (0..255))
0N/A -- Uniform Resource Locators are stored in URLStrings.
0N/A URLString ::= TEXTUAL-CONVENTION
0N/A "A Uniform Resource Locator represented in accordance
0N/A with RFCs 1738 and 2368, presented in the NVT ASCII
2693N/A charset defined in RFC 854."
0N/A SYNTAX OCTET STRING (SIZE (0..255))
0N/A -- The basic applTable contains a list of the application
0N/A applTable OBJECT-TYPE
0N/A SYNTAX SEQUENCE OF ApplEntry
0N/A MAX-ACCESS not-accessible
0N/A "The table holding objects which apply to all different
0N/A kinds of applications providing network services.
0N/A Each network service application capable of being
0N/A monitored should have a single entry in this table."
0N/A applEntry OBJECT-TYPE
0N/A MAX-ACCESS not-accessible
0N/A "An entry associated with a single network service
0N/A ApplEntry ::= SEQUENCE {
0N/A applInboundAssociations
0N/A applOutboundAssociations
0N/A applAccumulatedInboundAssociations
0N/A applAccumulatedOutboundAssociations
0N/A applLastInboundActivity
0N/A applLastOutboundActivity
0N/A applRejectedInboundAssociations
0N/A applFailedOutboundAssociations
0N/A applIndex OBJECT-TYPE
0N/A SYNTAX INTEGER (1..2147483647)
0N/A MAX-ACCESS not-accessible
0N/A "An index to uniquely identify the network service
0N/A application. This attribute is the index used for
0N/A lexicographic ordering of the table."
0N/A applName OBJECT-TYPE
0N/A SYNTAX SnmpAdminString
0N/A MAX-ACCESS read-only
0N/A "The name the network service application chooses to be
0N/A applDirectoryName OBJECT-TYPE
0N/A SYNTAX DistinguishedName
0N/A MAX-ACCESS read-only
0N/A "The Distinguished Name of the directory entry where
0N/A static information about this application is stored.
0N/A An empty string indicates that no information about
0N/A the application is available in the directory."
0N/A applVersion OBJECT-TYPE
0N/A SYNTAX SnmpAdminString
0N/A MAX-ACCESS read-only
0N/A "The version of network service application software.
0N/A This field is usually defined by the vendor of the
0N/A network service application software."
0N/A applUptime OBJECT-TYPE
0N/A MAX-ACCESS read-only
0N/A "The value of sysUpTime at the time the network service
0N/A application was last initialized. If the application was
0N/A last initialized prior to the last initialization of the
0N/A network management subsystem, then this object contains
0N/A applOperStatus OBJECT-TYPE
0N/A MAX-ACCESS read-only
0N/A "Indicates the operational status of the network service
0N/A application. 'down' indicates that the network service is
0N/A not available. 'up' indicates that the network service
0N/A is operational and available. 'halted' indicates that the
0N/A service is operational but not available. 'congested'
0N/A indicates that the service is operational but no additional
0N/A inbound associations can be accommodated. 'restarting'
0N/A indicates that the service is currently unavailable but is
0N/A in the process of restarting and will be available soon.
0N/A 'quiescing' indicates that service is currently operational
0N/A but is in the process of shutting down. Additional inbound
0N/A associations may be rejected by applications in the
0N/A applLastChange OBJECT-TYPE
0N/A MAX-ACCESS read-only
0N/A "The value of sysUpTime at the time the network service
0N/A application entered its current operational state. If
0N/A the current state was entered prior to the last
0N/A initialization of the local network management subsystem,
0N/A then this object contains a zero value."
0N/A applInboundAssociations OBJECT-TYPE
0N/A MAX-ACCESS read-only
0N/A "The number of current associations to the network service
0N/A application, where it is the responder. An inbound
0N/A association occurs when another application successfully
0N/A connects to this one."
0N/A applOutboundAssociations OBJECT-TYPE
0N/A MAX-ACCESS read-only
0N/A "The number of current associations to the network service
0N/A application, where it is the initiator. An outbound
0N/A association occurs when this application successfully
0N/A connects to another one."
0N/A applAccumulatedInboundAssociations OBJECT-TYPE
0N/A MAX-ACCESS read-only
0N/A "The total number of associations to the application entity
0N/A since application initialization, where it was the responder."
0N/A applAccumulatedOutboundAssociations OBJECT-TYPE
0N/A MAX-ACCESS read-only
0N/A "The total number of associations to the application entity
0N/A since application initialization, where it was the initiator."
0N/A applLastInboundActivity OBJECT-TYPE
0N/A MAX-ACCESS read-only
0N/A "The value of sysUpTime at the time this application last
0N/A had an inbound association. If the last association
0N/A occurred prior to the last initialization of the network
0N/A subsystem, then this object contains a zero value."
0N/A applLastOutboundActivity OBJECT-TYPE
0N/A MAX-ACCESS read-only
0N/A "The value of sysUpTime at the time this application last
0N/A had an outbound association. If the last association
0N/A occurred prior to the last initialization of the network
0N/A subsystem, then this object contains a zero value."
0N/A applRejectedInboundAssociations OBJECT-TYPE
2693N/A "The total number of inbound associations the application
2693N/A entity has rejected, since application initialization.
2693N/A Rejected associations are not counted in the accumulated
0N/A association totals. Note that this only counts
2693N/A associations the application entity has rejected itself;
2693N/A it does not count rejections that occur at lower layers
2693N/A of the network. Thus, this counter may not reflect the
2693N/A true number of failed inbound associations."
2693N/A applFailedOutboundAssociations OBJECT-TYPE
0N/A MAX-ACCESS read-only
0N/A "The total number associations where the application entity
2693N/A is initiator and association establishment has failed,
0N/A since application initialization. Failed associations are
0N/A not counted in the accumulated association totals."
2693N/A applDescription OBJECT-TYPE
0N/A SYNTAX SnmpAdminString
0N/A "A text description of the application. This information
0N/A is intended to identify and briefly describe the
2693N/A application in a status display."
0N/A MAX-ACCESS read-only
2693N/A "A URL pointing to a description of the application.
0N/A This information is intended to identify and describe
2693N/A the application in a status display."
2693N/A -- The assocTable augments the information in the applTable
0N/A -- with information about associations. Note that two levels
2693N/A -- of compliance are specified below, depending on whether
0N/A -- association monitoring is mandated.
0N/A SYNTAX SEQUENCE OF AssocEntry
2693N/A "The table holding a set of all active application
0N/A assocEntry OBJECT-TYPE
0N/A MAX-ACCESS not-accessible
0N/A "An entry associated with an association for a network
0N/A service application."
0N/A INDEX {applIndex, assocIndex}
0N/A AssocEntry ::= SEQUENCE {
0N/A assocRemoteApplication
0N/A assocApplicationProtocol
0N/A assocApplicationType
2693N/A SYNTAX INTEGER (1..2147483647)
0N/A MAX-ACCESS not-accessible
2693N/A "An index to uniquely identify each association for a network
2693N/A service application. This attribute is the index that is
2693N/A used for lexicographic ordering of the table. Note that the
2693N/A table is also indexed by the applIndex."
2693N/A assocRemoteApplication OBJECT-TYPE
2693N/A "The name of the system running remote network service
2693N/A application. For an IP-based application this should be
2693N/A either a domain name or IP address. For an OSI application
2693N/A it should be the string encoded distinguished name of the
2693N/A managed object. For X.400(1984) MTAs which do not have a
2693N/A Distinguished Name, the RFC 2156 syntax 'mta in
0N/A globalid' used in X400-Received: fields can be used. Note,
0N/A however, that not all connections an MTA makes are
0N/A necessarily to another MTA."
0N/A assocApplicationProtocol OBJECT-TYPE
0N/A SYNTAX OBJECT IDENTIFIER
0N/A MAX-ACCESS read-only
0N/A "An identification of the protocol being used for the
2693N/A application. For an OSI Application, this will be the
0N/A Application Context. For Internet applications, OID
0N/A values of the form {applTCPProtoID port} or {applUDPProtoID
0N/A port} are used for TCP-based and UDP-based protocols,
2693N/A respectively. In either case 'port' corresponds to the
0N/A primary port number being used by the protocol. The
0N/A usual IANA procedures may be used to register ports for
0N/A assocApplicationType OBJECT-TYPE
0N/A MAX-ACCESS read-only
0N/A "This indicates whether the remote application is some type of
0N/A client making use of this network service (
e.g., a Mail User
2693N/A Agent) or a server acting as a peer. Also indicated is whether
0N/A the remote end initiated an incoming connection to the network
0N/A service or responded to an outgoing connection made by the
0N/A local application. MTAs and messaging gateways are
0N/A considered to be peers for the purposes of this variable."
0N/A assocDuration OBJECT-TYPE
0N/A MAX-ACCESS read-only
0N/A "The value of sysUpTime at the time this association was
0N/A started. If this association started prior to the last
2693N/A initialization of the network subsystem, then this
0N/A object contains a zero value."
0N/A -- Conformance information
0N/A applConformance OBJECT IDENTIFIER ::= {application 3}
0N/A applGroups OBJECT IDENTIFIER ::= {applConformance 1}
0N/A applCompliances OBJECT IDENTIFIER ::= {applConformance 2}
2693N/A applCompliance MODULE-COMPLIANCE
0N/A "The compliance statement for RFC 1565 implementations
0N/A which support the Network Services Monitoring MIB
0N/A for basic monitoring of network service applications.
0N/A This is the basic compliance statement for RFC 1565."
0N/A MANDATORY-GROUPS {applRFC1565Group}
0N/A ::= {applCompliances 1}
0N/A assocCompliance MODULE-COMPLIANCE
2693N/A "The compliance statement for RFC 1565 implementations
0N/A which support the Network Services Monitoring MIB
2693N/A for basic monitoring of network service applications
2693N/A MANDATORY-GROUPS {applRFC1565Group, assocRFC1565Group}
2693N/A applRFC2248Compliance MODULE-COMPLIANCE
2693N/A "The compliance statement for RFC 2248 implementations
2693N/A which support the Network Services Monitoring MIB
2693N/A for basic monitoring of network service applications."
0N/A MANDATORY-GROUPS {applRFC2248Group}
0N/A ::= {applCompliances 3}
0N/A assocRFC2248Compliance MODULE-COMPLIANCE
0N/A "The compliance statement for RFC 2248 implementations
2693N/A which support the Network Services Monitoring MIB for
0N/A basic monitoring of network service applications and
0N/A MANDATORY-GROUPS {applRFC2248Group, assocRFC2248Group}
2693N/A applRFC2788Compliance MODULE-COMPLIANCE
2693N/A "The compliance statement for RFC 2788 implementations
0N/A which support the Network Services Monitoring MIB
0N/A for basic monitoring of network service applications."
0N/A MANDATORY-GROUPS {applRFC2788Group}
0N/A assocRFC2788Compliance MODULE-COMPLIANCE
0N/A "The compliance statement for RFC 2788 implementations
0N/A which support the Network Services Monitoring MIB for
0N/A basic monitoring of network service applications and
0N/A their associations."
0N/A MANDATORY-GROUPS {applRFC2788Group, assocRFC2788Group}
0N/A ::= {applCompliances 6}
2693N/A applRFC1565Group OBJECT-GROUP
0N/A applName, applVersion, applUptime, applOperStatus,
0N/A applLastChange, applInboundAssociations,
2693N/A applOutboundAssociations, applAccumulatedInboundAssociations,
0N/A applAccumulatedOutboundAssociations, applLastInboundActivity,
2693N/A applLastOutboundActivity, applRejectedInboundAssociations,
2693N/A applFailedOutboundAssociations}
2693N/A "A collection of objects providing basic monitoring of
2693N/A network service applications. This is the original set
2693N/A of such objects defined in RFC 1565."
2693N/A assocRFC1565Group OBJECT-GROUP
2693N/A assocRemoteApplication, assocApplicationProtocol,
2693N/A assocApplicationType, assocDuration}
2693N/A "A collection of objects providing basic monitoring of
2693N/A network service applications' associations. This is the
2693N/A original set of such objects defined in RFC 1565."
2693N/A applRFC2248Group OBJECT-GROUP
2693N/A applName, applVersion, applUptime, applOperStatus,
2693N/A applLastChange, applInboundAssociations,
2693N/A applOutboundAssociations, applAccumulatedInboundAssociations,
0N/A applAccumulatedOutboundAssociations, applLastInboundActivity,
2693N/A applLastOutboundActivity, applRejectedInboundAssociations,
0N/A applFailedOutboundAssociations, applDescription, applURL}
0N/A "A collection of objects providing basic monitoring of
0N/A network service applications. This group was originally
0N/A defined in RFC 2248; note that applDirectoryName is
0N/A assocRFC2248Group OBJECT-GROUP
0N/A assocRemoteApplication, assocApplicationProtocol,
0N/A assocApplicationType, assocDuration}
2693N/A "A collection of objects providing basic monitoring of
0N/A network service applications' associations. This group
0N/A was originally defined by RFC 2248."
0N/A applRFC2788Group OBJECT-GROUP
6271N/A applName, applDirectoryName, applVersion, applUptime,
2693N/A applOperStatus, applLastChange, applInboundAssociations,
0N/A applOutboundAssociations, applAccumulatedInboundAssociations,
2693N/A applAccumulatedOutboundAssociations, applLastInboundActivity,
0N/A applLastOutboundActivity, applRejectedInboundAssociations,
0N/A applFailedOutboundAssociations, applDescription, applURL}
0N/A "A collection of objects providing basic monitoring of
0N/A network service applications. This is the appropriate
0N/A group for RFC 2788 -- it adds the applDirectoryName object
0N/A missing in RFC 2248."
0N/A assocRFC2788Group OBJECT-GROUP
0N/A assocRemoteApplication, assocApplicationProtocol,
0N/A assocApplicationType, assocDuration}
0N/A "A collection of objects providing basic monitoring of
0N/A network service applications' associations. This is
0N/A the appropriate group for RFC 2788."
0N/A -- OIDs of the form {applTCPProtoID port} are intended to be used
0N/A -- for TCP-based protocols that don't have OIDs assigned by other
2693N/A -- means. {applUDPProtoID port} serves the same purpose for
0N/A -- UDP-based protocols. In either case 'port' corresponds to
0N/A -- the primary port number being used by the protocol. For example,
0N/A -- assuming no other OID is assigned for SMTP, an OID of
0N/A -- {applTCPProtoID 25} could be used, since SMTP is a TCP-based
2693N/A -- protocol that uses port 25 as its primary port.
2693N/A applTCPProtoID OBJECT IDENTIFIER ::= {application 4}
2693N/A applUDPProtoID OBJECT IDENTIFIER ::= {application 5}