All MIBs › NETWORK-SERVICES-MIB
Organization: IETF Mail and Directory Management Working Group
Last Updated: 2000-03-03
Category: Web and Application Servers
Description:
Provides a common framework for monitoring any network service application, including a table of monitorable services, association counts, and per-association status information.
Imported Objects
From SNMP-FRAMEWORK-MIB
| SnmpAdminString |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Counter32 | |
| Gauge32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| mib-2 |
From SNMPv2-TC
| TEXTUAL-CONVENTION | |
| TimeStamp |
What Is NETWORK-SERVICES-MIB?
NETWORK-SERVICES-MIB is an IETF standards-based module (from the RFC 2248 application-management family) providing a vendor-neutral framework for monitoring any network service/application running on a managed host, independent of the specific application. It exposes an application table listing each running service application along with its name, directory path, version, and association counts, plus operational status and last-change timestamps. It is explicitly a software-status MIB: applUptime and applOperStatus report how long an application instance has been running and whether it is currently operational, while applInboundAssociations and applOutboundAssociations reveal how many client/peer connections it is currently handling. It is a generic, protocol-independent companion to the IETF Host Resources MIB (for OS-level process/resource data), and is often used alongside application-specific MIBs like DNS-SERVER-MIB for deeper detail; administrators consulting the NETWORK-SERVICES-MIB RFC (RFC 2248) will find the applTable defined exactly as implemented here, anchoring compatibility across different vendors' SNMP agents. It is deployed on any server host where an SNMP agent instruments individual application processes for management visibility.
IPNetwork Monitor allows you to monitor SNMP objects defined in NETWORK-SERVICES-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
What Can Be Monitored
- application operational status
- application uptime
- inbound/outbound association counts
- last state-change time
- application version
Supported Devices
- vendor-neutral, standards-based MIB, not tied to a specific manufacturer — applies to any host running SNMP-instrumented network applications
Monitoring Examples
An operator would poll applTable/applEntry indexed by applIndex to check applOperStatus for a critical service like a mail or DNS daemon, confirming it reports up and not down or restarting. A sudden drop in applInboundAssociations for a service that normally handles many client connections could indicate the application has stopped accepting new connections, while applLastChange shows exactly when its state last changed. applVersion and applUptime together help confirm which software build is running and whether it has been stable since the last restart.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| application | 1.3.6.1.2.1.27 | The MIB module describing network service applications | ||
| applTable | 1.3.6.1.2.1.27.1 | not-accessible | 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. | |
| applEntry | 1.3.6.1.2.1.27.1.1 | not-accessible | An entry associated with a single network service application. | |
| INT applIndex | 1.3.6.1.2.1.27.1.1.1 | INTEGER | not-accessible | An index to uniquely identify the network service application. This attribute is the index used for lexicographic ordering of the table. |
| STR applName | 1.3.6.1.2.1.27.1.1.2 | SnmpAdminString | read-only | The name the network service application chooses to be known by. |
| DIS applDirectoryName | 1.3.6.1.2.1.27.1.1.3 | DistinguishedName | read-only | 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. |
| STR applVersion | 1.3.6.1.2.1.27.1.1.4 | SnmpAdminString | read-only | The version of network service application software. This field is usually defined by the vendor of the network service application software. |
| TIM applUptime | 1.3.6.1.2.1.27.1.1.5 | TimeStamp | read-only | 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. |
| INT applOperStatus | 1.3.6.1.2.1.27.1.1.6 | INTEGER | read-only | 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. |
| TIM applLastChange | 1.3.6.1.2.1.27.1.1.7 | TimeStamp | read-only | 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. |
| G32 applInboundAssociations | 1.3.6.1.2.1.27.1.1.8 | Gauge32 | read-only | 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. |
| G32 applOutboundAssociations | 1.3.6.1.2.1.27.1.1.9 | Gauge32 | read-only | 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. |
| C32 applAccumulatedInboundAssociations | 1.3.6.1.2.1.27.1.1.10 | Counter32 | read-only | The total number of associations to the application entity since application initialization, where it was the responder. |
| C32 applAccumulatedOutboundAssociations | 1.3.6.1.2.1.27.1.1.11 | Counter32 | read-only | The total number of associations to the application entity since application initialization, where it was the initiator. |
| TIM applLastInboundActivity | 1.3.6.1.2.1.27.1.1.12 | TimeStamp | read-only | 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. |
| TIM applLastOutboundActivity | 1.3.6.1.2.1.27.1.1.13 | TimeStamp | read-only | 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. |
| C32 applRejectedInboundAssociations | 1.3.6.1.2.1.27.1.1.14 | Counter32 | read-only | 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. |
| C32 applFailedOutboundAssociations | 1.3.6.1.2.1.27.1.1.15 | Counter32 | read-only | 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. |
| STR applDescription | 1.3.6.1.2.1.27.1.1.16 | SnmpAdminString | read-only | A text description of the application. This information is intended to identify and briefly describe the application in a status display. |
| STR applURL | 1.3.6.1.2.1.27.1.1.17 | URLString | read-only | A URL pointing to a description of the application. This information is intended to identify and describe the application in a status display. |
| assocTable | 1.3.6.1.2.1.27.2 | not-accessible | The table holding a set of all active application associations. | |
| assocEntry | 1.3.6.1.2.1.27.2.1 | not-accessible | An entry associated with an association for a network service application. | |
| INT assocIndex | 1.3.6.1.2.1.27.2.1.1 | INTEGER | not-accessible | 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. |
| STR assocRemoteApplication | 1.3.6.1.2.1.27.2.1.2 | SnmpAdminString | read-only | 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. |
| OID assocApplicationProtocol | 1.3.6.1.2.1.27.2.1.3 | OBJECT IDENTIFIER | read-only | 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. |
| INT assocApplicationType | 1.3.6.1.2.1.27.2.1.4 | INTEGER | read-only | 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. |
| TIM assocDuration | 1.3.6.1.2.1.27.2.1.5 | TimeStamp | read-only | 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. |
| applConformance | 1.3.6.1.2.1.27.3 | |||
| applGroups | 1.3.6.1.2.1.27.3.1 | |||
| assocRFC1565Group | 1.3.6.1.2.1.27.3.1.2 | A collection of objects providing basic monitoring of network service applications' associations. This is the original set of such objects defined in RFC 1565. | ||
| applRFC2248Group | 1.3.6.1.2.1.27.3.1.3 | A collection of objects providing basic monitoring of network service applications. This group was originally defined in RFC 2248; note that applDirectoryName is missing. | ||
| assocRFC2248Group | 1.3.6.1.2.1.27.3.1.4 | A collection of objects providing basic monitoring of network service applications' associations. This group was originally defined by RFC 2248. | ||
| applRFC2788Group | 1.3.6.1.2.1.27.3.1.5 | 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. | ||
| assocRFC2788Group | 1.3.6.1.2.1.27.3.1.6 | A collection of objects providing basic monitoring of network service applications' associations. This is the appropriate group for RFC 2788. | ||
| applRFC1565Group | 1.3.6.1.2.1.27.3.1.7 | A collection of objects providing basic monitoring of network service applications. This is the original set of such objects defined in RFC 1565. | ||
| applCompliances | 1.3.6.1.2.1.27.3.2 | |||
| applCompliance | 1.3.6.1.2.1.27.3.2.1 | 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. | ||
| assocCompliance | 1.3.6.1.2.1.27.3.2.2 | The compliance statement for RFC 1565 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications and their associations. | ||
| applRFC2248Compliance | 1.3.6.1.2.1.27.3.2.3 | The compliance statement for RFC 2248 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications. | ||
| assocRFC2248Compliance | 1.3.6.1.2.1.27.3.2.4 | The compliance statement for RFC 2248 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications and their associations. | ||
| applRFC2788Compliance | 1.3.6.1.2.1.27.3.2.5 | The compliance statement for RFC 2788 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications. | ||
| assocRFC2788Compliance | 1.3.6.1.2.1.27.3.2.6 | The compliance statement for RFC 2788 implementations which support the Network Services Monitoring MIB for basic monitoring of network service applications and their associations. | ||
| applTCPProtoID | 1.3.6.1.2.1.27.4 | |||
| applUDPProtoID | 1.3.6.1.2.1.27.5 |
FAQ
What is NETWORK-SERVICES-MIB used for when monitoring a fleet of mixed-vendor application servers?
It's the IETF RFC 2248 framework for monitoring any SNMP-instrumented network application without needing a vendor-specific MIB. Its applTable lists each running application instance with name, directory path, version, and association counts, so you can build one generic dashboard that works across different vendors' agents instead of writing separate polling logic per application.
How can NETWORK-SERVICES-MIB help detect an application that has silently stopped handling traffic?
By polling applOperStatus and applUptime you can confirm whether an instance is still running and how long it's been up, and applInboundAssociations/applOutboundAssociations show how many client or peer connections it currently has -- a sudden drop to zero associations combined with an unchanged uptime can flag an app that's alive but no longer serving traffic.
RFC description
Provides management objects for network services like DNS, DHCP, and NTP configuration.
Start monitoring Vendor-neutral IETF standard (any host running SNMP-instrumented network applications) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.