NETWORK-SERVICES-MIB: View SNMP OID List / Download MIB

VENDOR: INTERNET-STANDARD


 Home MIB: NETWORK-SERVICES-MIB
Download as:   

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 application 1.3.6.1.2.1.27
The MIB module describing network service applications
       applTable 1.3.6.1.2.1.27.1 no-access
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 no-access
An entry associated with a single network service application.
               applIndex 1.3.6.1.2.1.27.1.1.1 integer no-access
An index to uniquely identify the network service application. This attribute is the index used for lexicographic ordering of the table.
               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.
               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.
               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.
               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.
               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. Enumeration: 'halted': 3, 'up': 1, 'down': 2, 'restarting': 5, 'quiescing': 6, 'congested': 4.
               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.
               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.
               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.
               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.
               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.
               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.
               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.
               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.
               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.
               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.
               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 no-access
The table holding a set of all active application associations.
           assocEntry 1.3.6.1.2.1.27.2.1 no-access
An entry associated with an association for a network service application.
               assocIndex 1.3.6.1.2.1.27.2.1.1 integer no-access
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.
               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.
               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.
               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. Enumeration: 'uainitiator': 1, 'uaresponder': 2, 'peerinitiator': 3, 'peerresponder': 4.
               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