MIBs Depot

NETWORK-SERVICES-MIB

Registered at
1.3.6.1.2.1.27
Last updated
2000-03-03 00:00
Organization
IETF Mail and Directory Management Working Group
Revisions
2000-03-03 00:00, 1999-05-12 00:00, 1997-08-17 00:00, 1993-11-28 00:00
Namespace
standard
Source file
NETWORK-SERVICES-MIB
Digest
sha256:baac627a74c3d44c17a37734ddbb438d8dc629136ee6167dfa8a88d71949a84b

Description

The MIB module describing network service applications

Contact

Ned Freed Postal: Innosoft International, Inc. 1050 Lakes Drive West Covina, CA 91790 US Tel: +1 626 919 3600 Fax: +1 626 919 3614 E-Mail: ned.freed@innosoft.com

Imports

FromSymbols
SNMP-FRAMEWORK-MIBSnmpAdminString
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
SNMPv2-SMICounter32, Gauge32, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, iso, mib-2
SNMPv2-TCDisplayString, TEXTUAL-CONVENTION, TimeStamp

Imported by

3 module(s) in this corpus import this one.

Load order

Every file a consumer needs in order to load this module, dependencies first.

NETWORK-SERVICES-MIB
SNMP-FRAMEWORK-MIB
SNMPv2-CONF
SNMPv2-SMI
SNMPv2-TC

Textual conventions

NameOIDSyntaxAccessStatus
DistinguishedName
TEXTUAL-CONVENTION
A Distinguished Name represented in accordance with RFC 2253, presented in the UTF-8 charset defined in RFC 2279.
current
URLString
TEXTUAL-CONVENTION
A Uniform Resource Locator represented in accordance with RFCs 1738 and 2368, presented in the NVT ASCII charset defined in RFC 854.
current

Objects

NameOIDSyntaxAccessStatus
applTable
OBJECT-TYPE
The table holding objects which apply to all different kinds of applications providing network services. Each network service application capable of being monitored should have a single entry in this table.
1.3.6.1.2.1.27.1not-accessiblecurrent
applEntry
OBJECT-TYPE
An entry associated with a single network service application.
1.3.6.1.2.1.27.1.1not-accessiblecurrent
applIndex
OBJECT-TYPE
An index to uniquely identify the network service application. This attribute is the index used for lexicographic ordering of the table.
1.3.6.1.2.1.27.1.1.1INTEGER (1..2147483647)not-accessiblecurrent
applName
OBJECT-TYPE
The name the network service application chooses to be known by.
1.3.6.1.2.1.27.1.1.2SnmpAdminStringread-onlycurrent
applDirectoryName
OBJECT-TYPE
The Distinguished Name of the directory entry where static information about this application is stored. An empty string indicates that no information about the application is available in the directory.
1.3.6.1.2.1.27.1.1.3DistinguishedNameread-onlycurrent
applVersion
OBJECT-TYPE
The version of network service application software. This field is usually defined by the vendor of the network service application software.
1.3.6.1.2.1.27.1.1.4SnmpAdminStringread-onlycurrent
applUptime
OBJECT-TYPE
The value of sysUpTime at the time the network service application was last initialized. If the application was last initialized prior to the last initialization of the network management subsystem, then this object contains a zero value.
1.3.6.1.2.1.27.1.1.5TimeStampread-onlycurrent
applOperStatus
OBJECT-TYPE
Indicates the operational status of the network service application. 'down' indicates that the network service is not available. 'up' indicates that the network service is operational and available. 'halted' indicates that the service is operational but not available. 'congested' indicates that the service is operational but no additional inbound associations can be accommodated. 'restarting' indicates that the service is currently unavailable but is in the process of restarting and will be available soon. 'quiescing' indicates that service is currently operational but is in the process of shutting down. Additional inbound associations may be rejected by applications in the 'quiescing' state.
1.3.6.1.2.1.27.1.1.6INTEGER {up(1), down(2), halted(3), congested(4), restarting(5), quiescing(6)}read-onlycurrent
applLastChange
OBJECT-TYPE
The value of sysUpTime at the time the network service application entered its current operational state. If the current state was entered prior to the last initialization of the local network management subsystem, then this object contains a zero value.
1.3.6.1.2.1.27.1.1.7TimeStampread-onlycurrent
applInboundAssociations
OBJECT-TYPE
The number of current associations to the network service application, where it is the responder. An inbound association occurs when another application successfully connects to this one.
1.3.6.1.2.1.27.1.1.8Gauge32read-onlycurrent
applOutboundAssociations
OBJECT-TYPE
The number of current associations to the network service application, where it is the initiator. An outbound association occurs when this application successfully connects to another one.
1.3.6.1.2.1.27.1.1.9Gauge32read-onlycurrent
applAccumulatedInboundAssociations
OBJECT-TYPE
The total number of associations to the application entity since application initialization, where it was the responder.
1.3.6.1.2.1.27.1.1.10Counter32read-onlycurrent
applAccumulatedOutboundAssociations
OBJECT-TYPE
The total number of associations to the application entity since application initialization, where it was the initiator.
1.3.6.1.2.1.27.1.1.11Counter32read-onlycurrent
applLastInboundActivity
OBJECT-TYPE
The value of sysUpTime at the time this application last had an inbound association. If the last association occurred prior to the last initialization of the network subsystem, then this object contains a zero value.
1.3.6.1.2.1.27.1.1.12TimeStampread-onlycurrent
applLastOutboundActivity
OBJECT-TYPE
The value of sysUpTime at the time this application last had an outbound association. If the last association occurred prior to the last initialization of the network subsystem, then this object contains a zero value.
1.3.6.1.2.1.27.1.1.13TimeStampread-onlycurrent
applRejectedInboundAssociations
OBJECT-TYPE
The total number of inbound associations the application entity has rejected, since application initialization. Rejected associations are not counted in the accumulated association totals. Note that this only counts associations the application entity has rejected itself; it does not count rejections that occur at lower layers of the network. Thus, this counter may not reflect the true number of failed inbound associations.
1.3.6.1.2.1.27.1.1.14Counter32read-onlycurrent
applFailedOutboundAssociations
OBJECT-TYPE
The total number associations where the application entity is initiator and association establishment has failed, since application initialization. Failed associations are not counted in the accumulated association totals.
1.3.6.1.2.1.27.1.1.15Counter32read-onlycurrent
applDescription
OBJECT-TYPE
A text description of the application. This information is intended to identify and briefly describe the application in a status display.
1.3.6.1.2.1.27.1.1.16SnmpAdminStringread-onlycurrent
applURL
OBJECT-TYPE
A URL pointing to a description of the application. This information is intended to identify and describe the application in a status display.
1.3.6.1.2.1.27.1.1.17URLStringread-onlycurrent
assocTable
OBJECT-TYPE
The table holding a set of all active application associations.
1.3.6.1.2.1.27.2not-accessiblecurrent
assocEntry
OBJECT-TYPE
An entry associated with an association for a network service application.
1.3.6.1.2.1.27.2.1not-accessiblecurrent
assocIndex
OBJECT-TYPE
An index to uniquely identify each association for a network service application. This attribute is the index that is used for lexicographic ordering of the table. Note that the table is also indexed by the applIndex.
1.3.6.1.2.1.27.2.1.1INTEGER (1..2147483647)not-accessiblecurrent
assocRemoteApplication
OBJECT-TYPE
The name of the system running remote network service application. For an IP-based application this should be either a domain name or IP address. For an OSI application it should be the string encoded distinguished name of the managed object. For X.400(1984) MTAs which do not have a Distinguished Name, the RFC 2156 syntax 'mta in globalid' used in X400-Received: fields can be used. Note, however, that not all connections an MTA makes are necessarily to another MTA.
1.3.6.1.2.1.27.2.1.2SnmpAdminStringread-onlycurrent
assocApplicationProtocol
OBJECT-TYPE
An identification of the protocol being used for the application. For an OSI Application, this will be the Application Context. For Internet applications, OID values of the form {applTCPProtoID port} or {applUDPProtoID port} are used for TCP-based and UDP-based protocols, respectively. In either case 'port' corresponds to the primary port number being used by the protocol. The usual IANA procedures may be used to register ports for new protocols.
1.3.6.1.2.1.27.2.1.3OBJECT IDENTIFIERread-onlycurrent
assocApplicationType
OBJECT-TYPE
This indicates whether the remote application is some type of client making use of this network service (e.g., a Mail User Agent) or a server acting as a peer. Also indicated is whether the remote end initiated an incoming connection to the network service or responded to an outgoing connection made by the local application. MTAs and messaging gateways are considered to be peers for the purposes of this variable.
1.3.6.1.2.1.27.2.1.4INTEGER {uainitiator(1), uaresponder(2), peerinitiator(3), peerresponder(4)}read-onlycurrent
assocDuration
OBJECT-TYPE
The value of sysUpTime at the time this association was started. If this association started prior to the last initialization of the network subsystem, then this object contains a zero value.
1.3.6.1.2.1.27.2.1.5TimeStampread-onlycurrent
applConformance
OBJECT-IDENTITY
1.3.6.1.2.1.27.3
applGroups
OBJECT-IDENTITY
1.3.6.1.2.1.27.3.1
applCompliances
OBJECT-IDENTITY
1.3.6.1.2.1.27.3.2
applTCPProtoID
OBJECT-IDENTITY
1.3.6.1.2.1.27.4
applUDPProtoID
OBJECT-IDENTITY
1.3.6.1.2.1.27.5

Conformance

NameOIDStatus
assocRFC1565Group
OBJECT-GROUP
A collection of objects providing basic monitoring of network service applications' associations. This is the original set of such objects defined in RFC 1565.
1.3.6.1.2.1.27.3.1.2obsolete
applRFC2248Group
OBJECT-GROUP
A collection of objects providing basic monitoring of network service applications. This group was originally defined in RFC 2248; note that applDirectoryName is missing.
1.3.6.1.2.1.27.3.1.3deprecated
assocRFC2248Group
OBJECT-GROUP
A collection of objects providing basic monitoring of network service applications' associations. This group was originally defined by RFC 2248.
1.3.6.1.2.1.27.3.1.4deprecated
applRFC2788Group
OBJECT-GROUP
A collection of objects providing basic monitoring of network service applications. This is the appropriate group for RFC 2788 -- it adds the applDirectoryName object missing in RFC 2248.
1.3.6.1.2.1.27.3.1.5current
assocRFC2788Group
OBJECT-GROUP
A collection of objects providing basic monitoring of network service applications' associations. This is the appropriate group for RFC 2788.
1.3.6.1.2.1.27.3.1.6current
applRFC1565Group
OBJECT-GROUP
A collection of objects providing basic monitoring of network service applications. This is the original set of such objects defined in RFC 1565.
1.3.6.1.2.1.27.3.1.7obsolete
applCompliance
MODULE-COMPLIANCE
The compliance statement for RFC 1565 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications. This is the basic compliance statement for RFC 1565.
1.3.6.1.2.1.27.3.2.1obsolete
assocCompliance
MODULE-COMPLIANCE
The compliance statement for RFC 1565 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications and their associations.
1.3.6.1.2.1.27.3.2.2obsolete
applRFC2248Compliance
MODULE-COMPLIANCE
The compliance statement for RFC 2248 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications.
1.3.6.1.2.1.27.3.2.3deprecated
assocRFC2248Compliance
MODULE-COMPLIANCE
The compliance statement for RFC 2248 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications and their associations.
1.3.6.1.2.1.27.3.2.4deprecated
applRFC2788Compliance
MODULE-COMPLIANCE
The compliance statement for RFC 2788 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications.
1.3.6.1.2.1.27.3.2.5current
assocRFC2788Compliance
MODULE-COMPLIANCE
The compliance statement for RFC 2788 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications and their associations.
1.3.6.1.2.1.27.3.2.6current