NETWORK-SERVICES-MIB
AI MIB Summary
The NETWORK-SERVICES-MIB defines managed objects for monitoring the operational status, configuration parameters, and performance counters of generic network service applications running on network devices. It enables the tracking of service-specific metrics such as active session counts, protocol state transitions, and resource utilization for services like HTTP, DNS, or FTP to facilitate fault detection and capacity planning.
The MIB module describing network service applications
Main OID:
application.1.3.6.1.2.1.27
44
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
44 total| Object Name |
|---|
applicationThe MIB module describing network service applications MODULE-IDENTITY .1.3.6.1.2.1.27 |
applTableThe 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. SEQUENCE OF ApplEntry .1.3.6.1.2.1.27.1 |
applEntryAn entry associated with a single network service application. ApplEntry .1.3.6.1.2.1.27.1.1 |
applIndexAn index to uniquely identify the network service application. This attribute is the index used for lexicographic ordering of the table. INTEGER .1.3.6.1.2.1.27.1.1.1 |
applNameThe name the network service application chooses to be known by.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.27.1.1.2 |
applDirectoryNameThe 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.ro DistinguishedName .1.3.6.1.2.1.27.1.1.3 |
applVersionThe version of network service application software. This field is usually defined by the vendor of the network service application software.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.27.1.1.4 |
applUptimeThe 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.ro TimeStamp (SNMPv2-TC) .1.3.6.1.2.1.27.1.1.5 |
applOperStatusIndicates 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.ro Enumeration .1.3.6.1.2.1.27.1.1.6 |
applLastChangeThe 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.ro TimeStamp (SNMPv2-TC) .1.3.6.1.2.1.27.1.1.7 |
applInboundAssociationsThe 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.ro Gauge32 .1.3.6.1.2.1.27.1.1.8 |
applOutboundAssociationsThe 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.ro Gauge32 .1.3.6.1.2.1.27.1.1.9 |
applAccumulatedInboundAssociationsThe total number of associations to the application entity since application initialization, where it was the responder.ro Counter32 .1.3.6.1.2.1.27.1.1.10 |
applAccumulatedOutboundAssociationsThe total number of associations to the application entity since application initialization, where it was the initiator.ro Counter32 .1.3.6.1.2.1.27.1.1.11 |
applLastInboundActivityThe 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.ro TimeStamp (SNMPv2-TC) .1.3.6.1.2.1.27.1.1.12 |
applLastOutboundActivityThe 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.ro TimeStamp (SNMPv2-TC) .1.3.6.1.2.1.27.1.1.13 |
applRejectedInboundAssociationsThe 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.ro Counter32 .1.3.6.1.2.1.27.1.1.14 |
applFailedOutboundAssociationsThe 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.ro Counter32 .1.3.6.1.2.1.27.1.1.15 |
applDescriptionA text description of the application. This information is intended to identify and briefly describe the application in a status display.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.27.1.1.16 |
applURLA URL pointing to a description of the application. This information is intended to identify and describe the application in a status display.ro URLString .1.3.6.1.2.1.27.1.1.17 |
assocTableThe table holding a set of all active application associations. SEQUENCE OF AssocEntry .1.3.6.1.2.1.27.2 |
assocEntryAn entry associated with an association for a network service application. AssocEntry .1.3.6.1.2.1.27.2.1 |
assocIndexAn 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. INTEGER .1.3.6.1.2.1.27.2.1.1 |
assocRemoteApplicationThe 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.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.2.1.27.2.1.2 |
assocApplicationProtocolAn 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.ro OBJECT IDENTIFIER .1.3.6.1.2.1.27.2.1.3 |
assocApplicationTypeThis 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.ro Enumeration .1.3.6.1.2.1.27.2.1.4 |
assocDurationThe 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.ro TimeStamp (SNMPv2-TC) .1.3.6.1.2.1.27.2.1.5 |
applConformance OBJECT IDENTIFIER .1.3.6.1.2.1.27.3 |
applGroups OBJECT IDENTIFIER .1.3.6.1.2.1.27.3.1 |
assocRFC1565GroupA collection of objects providing basic monitoring of network service applications' associations. This is the original set of such objects defined in RFC 1565.obsolete Unknown .1.3.6.1.2.1.27.3.1.2 |
applRFC2248GroupA collection of objects providing basic monitoring of network service applications. This group was originally defined in RFC 2248; note that applDirectoryName is missing.deprecated Unknown .1.3.6.1.2.1.27.3.1.3 |
assocRFC2248GroupA collection of objects providing basic monitoring of network service applications' associations. This group was originally defined by RFC 2248.deprecated Unknown .1.3.6.1.2.1.27.3.1.4 |
applRFC2788GroupA 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. Unknown .1.3.6.1.2.1.27.3.1.5 |
assocRFC2788GroupA collection of objects providing basic monitoring of network service applications' associations. This is the appropriate group for RFC 2788. Unknown .1.3.6.1.2.1.27.3.1.6 |
applRFC1565GroupA collection of objects providing basic monitoring of network service applications. This is the original set of such objects defined in RFC 1565.obsolete Unknown .1.3.6.1.2.1.27.3.1.7 |
applCompliances OBJECT IDENTIFIER .1.3.6.1.2.1.27.3.2 |
applComplianceThe 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.obsolete Unknown .1.3.6.1.2.1.27.3.2.1 |
assocComplianceThe compliance statement for RFC 1565 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications and their associations.obsolete Unknown .1.3.6.1.2.1.27.3.2.2 |
applRFC2248ComplianceThe compliance statement for RFC 2248 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications.deprecated Unknown .1.3.6.1.2.1.27.3.2.3 |
assocRFC2248ComplianceThe compliance statement for RFC 2248 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications and their associations.deprecated Unknown .1.3.6.1.2.1.27.3.2.4 |
applRFC2788ComplianceThe compliance statement for RFC 2788 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications. Unknown .1.3.6.1.2.1.27.3.2.5 |
assocRFC2788ComplianceThe compliance statement for RFC 2788 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications and their associations. Unknown .1.3.6.1.2.1.27.3.2.6 |
applTCPProtoID OBJECT IDENTIFIER .1.3.6.1.2.1.27.4 |
applUDPProtoID OBJECT IDENTIFIER .1.3.6.1.2.1.27.5 |