1 NETWORK-SERVICES-MIB DEFINITIONS ::= BEGIN
4 OBJECT-TYPE, Counter32, Gauge32, MODULE-IDENTITY, mib-2
6 TimeStamp, TEXTUAL-CONVENTION
8 MODULE-COMPLIANCE, OBJECT-GROUP
11 FROM SNMP-FRAMEWORK-MIB;
13 application MODULE-IDENTITY
14 LAST-UPDATED "200003030000Z"
15 ORGANIZATION "IETF Mail and Directory Management Working Group"
19 Postal: Innosoft International, Inc.
27 E-Mail: ned.freed@innosoft.com"
29 "The MIB module describing network service applications"
30 REVISION "200003030000Z"
32 "This revision, published in RFC 2788, changes a number of
33 DisplayStrings to SnmpAdminStrings. Note that this change
34 is not strictly supported by SMIv2. However, the alternative
35 of deprecating the old objects and defining new objects
36 would have a more adverse impact on backward compatibility
37 and interoperability, given the particular semantics of
38 these objects. The defining reference for distinguished
39 names has also been updated from RFC 1779 to RFC 2253."
40 REVISION "199905120000Z"
42 "This revision fixes a few small technical problems found
43 in previous versions, mostly in regards to the conformance
44 groups for different versions of this MIB. No changes have
45 been made to the objects this MIB defines since RFC 2248."
46 REVISION "199708170000Z"
48 "This revision, published in RFC 2248, adds the
49 applDescription and applURL objects, adds the quiescing
50 state to the applOperStatus object and renames the MIB
51 from the APPLICATION-MIB to the NETWORK-SERVICE-MIB."
52 REVISION "199311280000Z"
54 "The original version of this MIB was published in RFC 1565"
57 -- Textual conventions
59 -- DistinguishedName is used to refer to objects in the
62 DistinguishedName ::= TEXTUAL-CONVENTION
66 "A Distinguished Name represented in accordance with
67 RFC 2253, presented in the UTF-8 charset defined in
69 SYNTAX OCTET STRING (SIZE (0..255))
71 -- Uniform Resource Locators are stored in URLStrings.
73 URLString ::= TEXTUAL-CONVENTION
77 "A Uniform Resource Locator represented in accordance
78 with RFCs 1738 and 2368, presented in the NVT ASCII
79 charset defined in RFC 854."
80 SYNTAX OCTET STRING (SIZE (0..255))
82 -- The basic applTable contains a list of the application
86 SYNTAX SEQUENCE OF ApplEntry
87 MAX-ACCESS not-accessible
90 "The table holding objects which apply to all different
91 kinds of applications providing network services.
92 Each network service application capable of being
93 monitored should have a single entry in this table."
98 MAX-ACCESS not-accessible
101 "An entry associated with a single network service
106 ApplEntry ::= SEQUENCE {
121 applInboundAssociations
123 applOutboundAssociations
125 applAccumulatedInboundAssociations
127 applAccumulatedOutboundAssociations
129 applLastInboundActivity
131 applLastOutboundActivity
133 applRejectedInboundAssociations
135 applFailedOutboundAssociations
143 applIndex OBJECT-TYPE
144 SYNTAX INTEGER (1..2147483647)
145 MAX-ACCESS not-accessible
148 "An index to uniquely identify the network service
149 application. This attribute is the index used for
150 lexicographic ordering of the table."
154 SYNTAX SnmpAdminString
158 "The name the network service application chooses to be
162 applDirectoryName OBJECT-TYPE
163 SYNTAX DistinguishedName
167 "The Distinguished Name of the directory entry where
168 static information about this application is stored.
169 An empty string indicates that no information about
170 the application is available in the directory."
173 applVersion OBJECT-TYPE
174 SYNTAX SnmpAdminString
178 "The version of network service application software.
179 This field is usually defined by the vendor of the
180 network service application software."
182 applUptime OBJECT-TYPE
187 "The value of sysUpTime at the time the network service
188 application was last initialized. If the application was
189 last initialized prior to the last initialization of the
190 network management subsystem, then this object contains
194 applOperStatus OBJECT-TYPE
206 "Indicates the operational status of the network service
207 application. 'down' indicates that the network service is
208 not available. 'up' indicates that the network service
209 is operational and available. 'halted' indicates that the
210 service is operational but not available. 'congested'
211 indicates that the service is operational but no additional
212 inbound associations can be accommodated. 'restarting'
213 indicates that the service is currently unavailable but is
214 in the process of restarting and will be available soon.
215 'quiescing' indicates that service is currently operational
216 but is in the process of shutting down. Additional inbound
217 associations may be rejected by applications in the
221 applLastChange OBJECT-TYPE
226 "The value of sysUpTime at the time the network service
227 application entered its current operational state. If
228 the current state was entered prior to the last
229 initialization of the local network management subsystem,
230 then this object contains a zero value."
233 applInboundAssociations OBJECT-TYPE
238 "The number of current associations to the network service
239 application, where it is the responder. An inbound
240 association occurs when another application successfully
241 connects to this one."
244 applOutboundAssociations OBJECT-TYPE
249 "The number of current associations to the network service
250 application, where it is the initiator. An outbound
251 association occurs when this application successfully
252 connects to another one."
255 applAccumulatedInboundAssociations OBJECT-TYPE
260 "The total number of associations to the application entity
261 since application initialization, where it was the responder."
264 applAccumulatedOutboundAssociations OBJECT-TYPE
269 "The total number of associations to the application entity
270 since application initialization, where it was the initiator."
273 applLastInboundActivity OBJECT-TYPE
278 "The value of sysUpTime at the time this application last
279 had an inbound association. If the last association
280 occurred prior to the last initialization of the network
281 subsystem, then this object contains a zero value."
284 applLastOutboundActivity OBJECT-TYPE
289 "The value of sysUpTime at the time this application last
290 had an outbound association. If the last association
291 occurred prior to the last initialization of the network
292 subsystem, then this object contains a zero value."
295 applRejectedInboundAssociations OBJECT-TYPE
300 "The total number of inbound associations the application
301 entity has rejected, since application initialization.
302 Rejected associations are not counted in the accumulated
303 association totals. Note that this only counts
304 associations the application entity has rejected itself;
305 it does not count rejections that occur at lower layers
306 of the network. Thus, this counter may not reflect the
307 true number of failed inbound associations."
310 applFailedOutboundAssociations OBJECT-TYPE
315 "The total number associations where the application entity
316 is initiator and association establishment has failed,
317 since application initialization. Failed associations are
318 not counted in the accumulated association totals."
321 applDescription OBJECT-TYPE
322 SYNTAX SnmpAdminString
326 "A text description of the application. This information
327 is intended to identify and briefly describe the
328 application in a status display."
336 "A URL pointing to a description of the application.
337 This information is intended to identify and describe
338 the application in a status display."
341 -- The assocTable augments the information in the applTable
342 -- with information about associations. Note that two levels
343 -- of compliance are specified below, depending on whether
344 -- association monitoring is mandated.
346 assocTable OBJECT-TYPE
347 SYNTAX SEQUENCE OF AssocEntry
348 MAX-ACCESS not-accessible
351 "The table holding a set of all active application
355 assocEntry OBJECT-TYPE
357 MAX-ACCESS not-accessible
360 "An entry associated with an association for a network
361 service application."
362 INDEX {applIndex, assocIndex}
365 AssocEntry ::= SEQUENCE {
368 assocRemoteApplication
370 assocApplicationProtocol
378 assocIndex OBJECT-TYPE
379 SYNTAX INTEGER (1..2147483647)
380 MAX-ACCESS not-accessible
383 "An index to uniquely identify each association for a network
384 service application. This attribute is the index that is
385 used for lexicographic ordering of the table. Note that the
386 table is also indexed by the applIndex."
389 assocRemoteApplication OBJECT-TYPE
390 SYNTAX SnmpAdminString
394 "The name of the system running remote network service
395 application. For an IP-based application this should be
396 either a domain name or IP address. For an OSI application
397 it should be the string encoded distinguished name of the
398 managed object. For X.400(1984) MTAs which do not have a
399 Distinguished Name, the RFC 2156 syntax 'mta in
400 globalid' used in X400-Received: fields can be used. Note,
401 however, that not all connections an MTA makes are
402 necessarily to another MTA."
405 assocApplicationProtocol OBJECT-TYPE
406 SYNTAX OBJECT IDENTIFIER
410 "An identification of the protocol being used for the
411 application. For an OSI Application, this will be the
412 Application Context. For Internet applications, OID
413 values of the form {applTCPProtoID port} or {applUDPProtoID
414 port} are used for TCP-based and UDP-based protocols,
415 respectively. In either case 'port' corresponds to the
416 primary port number being used by the protocol. The
417 usual IANA procedures may be used to register ports for
421 assocApplicationType OBJECT-TYPE
430 "This indicates whether the remote application is some type of
431 client making use of this network service (e.g., a Mail User
432 Agent) or a server acting as a peer. Also indicated is whether
433 the remote end initiated an incoming connection to the network
434 service or responded to an outgoing connection made by the
435 local application. MTAs and messaging gateways are
436 considered to be peers for the purposes of this variable."
439 assocDuration OBJECT-TYPE
444 "The value of sysUpTime at the time this association was
445 started. If this association started prior to the last
446 initialization of the network subsystem, then this
447 object contains a zero value."
451 -- Conformance information
453 applConformance OBJECT IDENTIFIER ::= {application 3}
455 applGroups OBJECT IDENTIFIER ::= {applConformance 1}
456 applCompliances OBJECT IDENTIFIER ::= {applConformance 2}
458 -- Compliance statements
460 applCompliance MODULE-COMPLIANCE
463 "The compliance statement for RFC 1565 implementations
464 which support the Network Services Monitoring MIB
465 for basic monitoring of network service applications.
466 This is the basic compliance statement for RFC 1565."
468 MANDATORY-GROUPS {applRFC1565Group}
469 ::= {applCompliances 1}
471 assocCompliance MODULE-COMPLIANCE
474 "The compliance statement for RFC 1565 implementations
475 which support the Network Services Monitoring MIB
476 for basic monitoring of network service applications
477 and their associations."
479 MANDATORY-GROUPS {applRFC1565Group, assocRFC1565Group}
480 ::= {applCompliances 2}
482 applRFC2248Compliance MODULE-COMPLIANCE
485 "The compliance statement for RFC 2248 implementations
486 which support the Network Services Monitoring MIB
487 for basic monitoring of network service applications."
489 MANDATORY-GROUPS {applRFC2248Group}
490 ::= {applCompliances 3}
492 assocRFC2248Compliance MODULE-COMPLIANCE
495 "The compliance statement for RFC 2248 implementations
496 which support the Network Services Monitoring MIB for
497 basic monitoring of network service applications and
500 MANDATORY-GROUPS {applRFC2248Group, assocRFC2248Group}
501 ::= {applCompliances 4}
503 applRFC2788Compliance MODULE-COMPLIANCE
506 "The compliance statement for RFC 2788 implementations
507 which support the Network Services Monitoring MIB
508 for basic monitoring of network service applications."
510 MANDATORY-GROUPS {applRFC2788Group}
511 ::= {applCompliances 5}
513 assocRFC2788Compliance MODULE-COMPLIANCE
516 "The compliance statement for RFC 2788 implementations
517 which support the Network Services Monitoring MIB for
518 basic monitoring of network service applications and
521 MANDATORY-GROUPS {applRFC2788Group, assocRFC2788Group}
522 ::= {applCompliances 6}
525 -- Units of conformance
527 applRFC1565Group OBJECT-GROUP
529 applName, applVersion, applUptime, applOperStatus,
530 applLastChange, applInboundAssociations,
531 applOutboundAssociations, applAccumulatedInboundAssociations,
532 applAccumulatedOutboundAssociations, applLastInboundActivity,
533 applLastOutboundActivity, applRejectedInboundAssociations,
534 applFailedOutboundAssociations}
537 "A collection of objects providing basic monitoring of
538 network service applications. This is the original set
539 of such objects defined in RFC 1565."
542 assocRFC1565Group OBJECT-GROUP
544 assocRemoteApplication, assocApplicationProtocol,
545 assocApplicationType, assocDuration}
548 "A collection of objects providing basic monitoring of
549 network service applications' associations. This is the
550 original set of such objects defined in RFC 1565."
553 applRFC2248Group OBJECT-GROUP
555 applName, applVersion, applUptime, applOperStatus,
556 applLastChange, applInboundAssociations,
557 applOutboundAssociations, applAccumulatedInboundAssociations,
558 applAccumulatedOutboundAssociations, applLastInboundActivity,
559 applLastOutboundActivity, applRejectedInboundAssociations,
560 applFailedOutboundAssociations, applDescription, applURL}
563 "A collection of objects providing basic monitoring of
564 network service applications. This group was originally
565 defined in RFC 2248; note that applDirectoryName is
569 assocRFC2248Group OBJECT-GROUP
571 assocRemoteApplication, assocApplicationProtocol,
572 assocApplicationType, assocDuration}
575 "A collection of objects providing basic monitoring of
576 network service applications' associations. This group
577 was originally defined by RFC 2248."
580 applRFC2788Group OBJECT-GROUP
582 applName, applDirectoryName, applVersion, applUptime,
583 applOperStatus, applLastChange, applInboundAssociations,
584 applOutboundAssociations, applAccumulatedInboundAssociations,
585 applAccumulatedOutboundAssociations, applLastInboundActivity,
586 applLastOutboundActivity, applRejectedInboundAssociations,
587 applFailedOutboundAssociations, applDescription, applURL}
590 "A collection of objects providing basic monitoring of
591 network service applications. This is the appropriate
592 group for RFC 2788 -- it adds the applDirectoryName object
593 missing in RFC 2248."
596 assocRFC2788Group OBJECT-GROUP
598 assocRemoteApplication, assocApplicationProtocol,
599 assocApplicationType, assocDuration}
602 "A collection of objects providing basic monitoring of
603 network service applications' associations. This is
604 the appropriate group for RFC 2788."
607 -- OIDs of the form {applTCPProtoID port} are intended to be used
608 -- for TCP-based protocols that don't have OIDs assigned by other
609 -- means. {applUDPProtoID port} serves the same purpose for
610 -- UDP-based protocols. In either case 'port' corresponds to
611 -- the primary port number being used by the protocol. For example,
612 -- assuming no other OID is assigned for SMTP, an OID of
613 -- {applTCPProtoID 25} could be used, since SMTP is a TCP-based
614 -- protocol that uses port 25 as its primary port.
616 applTCPProtoID OBJECT IDENTIFIER ::= {application 4}
617 applUDPProtoID OBJECT IDENTIFIER ::= {application 5}