The MIB module describing network service applications    

The table holding objects which apply to all different
kinds of applications providing network services.    

An entry associated with a network service application.    

An index to uniquely identify the network service
application.    

The total number of associations to the application entity
since application initialization, where it was the responder.
For  dynamic single threaded processes, this will be the
number of application instances.    

The total number of associations to the application entity
since application initialization, where it was the initiator.
For dynamic single threaded processes, this will be the
number of application instances.    

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.    

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.    

The total number of inbound associations the application
entity has rejected, since application initialization.    

The total number associations where the application entity
is initiator and association establishment has failed,
since application initialization.    

The name the network service application chooses to be
known by.    

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.    

The version of network service application software.    

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.    

Possible values are:


up, down, halted, congested, restarting
                

Indicates the operational status of the network service
application. 'down' indicates that the network service is
not available. 'running' 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 accomodated.  'restarting'
indicates that the service is currently unavailable but is
in the process of restarting and will be available soon.    

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.    

The number of current associations to the network service
application, where it is the responder.  For dynamic single
threaded processes, this will be the number of application
instances.    

The number of current associations to the network service
application, where it is the initiator.  For dynamic single
threaded processes, this will be the number of application
instances.    

The table holding a set of all active application
associations.    

An entry associated with an association for a network
service application.    

An index to uniquely identify each association for a network
service application.    

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(84) MTAs which do not have a
Distinguished Name, the RFC1327 [6] syntax
'mta in globalid' should be used.    

An identification of the protocol being used for the
application.  For an OSI Application, this will be the
Application Context.  For Internet applications, the IANA
maintains a registry of the OIDs which correspond to
well-known applications.  If the application protocol is
not listed in the registry, an OID value of the form
{applTCPProtoID port} or {applUDProtoID 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.    

Possible values are:


ua-initiator, ua-responder, 
peer-initiator, peer-responder

This indicates whether the remote application is some type of
client making use of this network service (e.g. a 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.    

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.    

Values are:


applName, applVersion, applUptime, 
applOperStatus, applLastChange, 
applInboundAssociations, 
applOutboundAssociations, 
applAccumulatedInboundAssociations, 
applAccumulatedOutboundAssociations, 
applLastInboundActivity, 
applLastOutboundActivity, 
applRejectedInboundAssociations, 
applFailedOutboundAssociations

A collection of objects providing basic monitoring of
network service applications.    

Values are:


assocRemoteApplication, 
assocApplicationProtocol, 
assocApplicationType, assocDuration

A collection of objects providing basic monitoring of
network service applications' associations.    

The compliance statement for SNMPv2 entities
which implement the Network Services Monitoring MIB
for basic monitoring of network service applications.    

The compliance statement for SNMPv2 entities which
implement the Network Services Monitoring MIB for basic
monitoring of network service applications and their
associations.