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"
20 Postal: Innosoft International, Inc.
28 E-Mail: ned.freed@innosoft.com"
30 "The MIB module describing network service applications"
31 REVISION "200003030000Z"
33 "This revision, published in RFC 2788, changes a number of
34 DisplayStrings to SnmpAdminStrings. Note that this change
35 is not strictly supported by SMIv2. However, the alternative
36 of deprecating the old objects and defining new objects
37 would have a more adverse impact on backward compatibility
38 and interoperability, given the particular semantics of
39 these objects. The defining reference for distinguished
40 names has also been updated from RFC 1779 to RFC 2253."
41 REVISION "199905120000Z"
43 "This revision fixes a few small technical problems found
44 in previous versions, mostly in regards to the conformance
45 groups for different versions of this MIB. No changes have
46 been made to the objects this MIB defines since RFC 2248."
47 REVISION "199708170000Z"
49 "This revision, published in RFC 2248, adds the
50 applDescription and applURL objects, adds the quiescing
51 state to the applOperStatus object and renames the MIB
52 from the APPLICATION-MIB to the NETWORK-SERVICE-MIB."
53 REVISION "199311280000Z"
55 "The original version of this MIB was published in RFC 1565"
58 -- Textual conventions
60 -- DistinguishedName is used to refer to objects in the
63 DistinguishedName ::= TEXTUAL-CONVENTION
67 "A Distinguished Name represented in accordance with
68 RFC 2253, presented in the UTF-8 charset defined in
70 SYNTAX OCTET STRING (SIZE (0..255))
72 -- Uniform Resource Locators are stored in URLStrings.
74 URLString ::= TEXTUAL-CONVENTION
78 "A Uniform Resource Locator represented in accordance
79 with RFCs 1738 and 2368, presented in the NVT ASCII
80 charset defined in RFC 854."
81 SYNTAX OCTET STRING (SIZE (0..255))
83 -- The basic applTable contains a list of the application
87 SYNTAX SEQUENCE OF ApplEntry
88 MAX-ACCESS not-accessible
91 "The table holding objects which apply to all different
92 kinds of applications providing network services.
93 Each network service application capable of being
94 monitored should have a single entry in this table."
99 MAX-ACCESS not-accessible
102 "An entry associated with a single network service
107 ApplEntry ::= SEQUENCE {
123 applInboundAssociations
125 applOutboundAssociations
127 applAccumulatedInboundAssociations
129 applAccumulatedOutboundAssociations
131 applLastInboundActivity
133 applLastOutboundActivity
135 applRejectedInboundAssociations
137 applFailedOutboundAssociations
145 applIndex OBJECT-TYPE
146 SYNTAX INTEGER (1..2147483647)
147 MAX-ACCESS not-accessible
150 "An index to uniquely identify the network service
151 application. This attribute is the index used for
152 lexicographic ordering of the table."
156 SYNTAX SnmpAdminString
160 "The name the network service application chooses to be
164 applDirectoryName OBJECT-TYPE
165 SYNTAX DistinguishedName
169 "The Distinguished Name of the directory entry where
170 static information about this application is stored.
171 An empty string indicates that no information about
172 the application is available in the directory."
175 applVersion OBJECT-TYPE
176 SYNTAX SnmpAdminString
180 "The version of network service application software.
181 This field is usually defined by the vendor of the
182 network service application software."
184 applUptime OBJECT-TYPE
189 "The value of sysUpTime at the time the network service
190 application was last initialized. If the application was
191 last initialized prior to the last initialization of the
192 network management subsystem, then this object contains
196 applOperStatus OBJECT-TYPE
208 "Indicates the operational status of the network service
209 application. 'down' indicates that the network service is
211 not available. 'up' indicates that the network service
212 is operational and available. 'halted' indicates that the
213 service is operational but not available. 'congested'
214 indicates that the service is operational but no additional
215 inbound associations can be accommodated. 'restarting'
216 indicates that the service is currently unavailable but is
217 in the process of restarting and will be available soon.
218 'quiescing' indicates that service is currently operational
219 but is in the process of shutting down. Additional inbound
220 associations may be rejected by applications in the
224 applLastChange OBJECT-TYPE
229 "The value of sysUpTime at the time the network service
230 application entered its current operational state. If
231 the current state was entered prior to the last
232 initialization of the local network management subsystem,
233 then this object contains a zero value."
236 applInboundAssociations OBJECT-TYPE
241 "The number of current associations to the network service
242 application, where it is the responder. An inbound
243 association occurs when another application successfully
244 connects to this one."
247 applOutboundAssociations OBJECT-TYPE
252 "The number of current associations to the network service
253 application, where it is the initiator. An outbound
254 association occurs when this application successfully
255 connects to another one."
258 applAccumulatedInboundAssociations OBJECT-TYPE
263 "The total number of associations to the application entity
264 since application initialization, where it was the responder."
267 applAccumulatedOutboundAssociations OBJECT-TYPE
272 "The total number of associations to the application entity
273 since application initialization, where it was the initiator."
276 applLastInboundActivity OBJECT-TYPE
281 "The value of sysUpTime at the time this application last
282 had an inbound association. If the last association
283 occurred prior to the last initialization of the network
284 subsystem, then this object contains a zero value."
287 applLastOutboundActivity OBJECT-TYPE
292 "The value of sysUpTime at the time this application last
293 had an outbound association. If the last association
294 occurred prior to the last initialization of the network
295 subsystem, then this object contains a zero value."
298 applRejectedInboundAssociations OBJECT-TYPE
303 "The total number of inbound associations the application
304 entity has rejected, since application initialization.
305 Rejected associations are not counted in the accumulated
306 association totals. Note that this only counts
308 associations the application entity has rejected itself;
309 it does not count rejections that occur at lower layers
310 of the network. Thus, this counter may not reflect the
311 true number of failed inbound associations."
314 applFailedOutboundAssociations OBJECT-TYPE
319 "The total number associations where the application entity
320 is initiator and association establishment has failed,
321 since application initialization. Failed associations are
322 not counted in the accumulated association totals."
325 applDescription OBJECT-TYPE
326 SYNTAX SnmpAdminString
330 "A text description of the application. This information
331 is intended to identify and briefly describe the
332 application in a status display."
340 "A URL pointing to a description of the application.
341 This information is intended to identify and describe
342 the application in a status display."
345 -- The assocTable augments the information in the applTable
346 -- with information about associations. Note that two levels
347 -- of compliance are specified below, depending on whether
348 -- association monitoring is mandated.
350 assocTable OBJECT-TYPE
351 SYNTAX SEQUENCE OF AssocEntry
352 MAX-ACCESS not-accessible
355 "The table holding a set of all active application
360 assocEntry OBJECT-TYPE
362 MAX-ACCESS not-accessible
365 "An entry associated with an association for a network
366 service application."
367 INDEX {applIndex, assocIndex}
370 AssocEntry ::= SEQUENCE {
373 assocRemoteApplication
375 assocApplicationProtocol
383 assocIndex OBJECT-TYPE
384 SYNTAX INTEGER (1..2147483647)
385 MAX-ACCESS not-accessible
388 "An index to uniquely identify each association for a network
389 service application. This attribute is the index that is
390 used for lexicographic ordering of the table. Note that the
391 table is also indexed by the applIndex."
394 assocRemoteApplication OBJECT-TYPE
395 SYNTAX SnmpAdminString
399 "The name of the system running remote network service
400 application. For an IP-based application this should be
401 either a domain name or IP address. For an OSI application
402 it should be the string encoded distinguished name of the
403 managed object. For X.400(1984) MTAs which do not have a
404 Distinguished Name, the RFC 2156 syntax 'mta in
406 globalid' used in X400-Received: fields can be used. Note,
407 however, that not all connections an MTA makes are
408 necessarily to another MTA."
411 assocApplicationProtocol OBJECT-TYPE
412 SYNTAX OBJECT IDENTIFIER
416 "An identification of the protocol being used for the
417 application. For an OSI Application, this will be the
418 Application Context. For Internet applications, OID
419 values of the form {applTCPProtoID port} or {applUDPProtoID
420 port} are used for TCP-based and UDP-based protocols,
421 respectively. In either case 'port' corresponds to the
422 primary port number being used by the protocol. The
423 usual IANA procedures may be used to register ports for
427 assocApplicationType OBJECT-TYPE
436 "This indicates whether the remote application is some type of
437 client making use of this network service (e.g., a Mail User
438 Agent) or a server acting as a peer. Also indicated is whether
439 the remote end initiated an incoming connection to the network
440 service or responded to an outgoing connection made by the
441 local application. MTAs and messaging gateways are
442 considered to be peers for the purposes of this variable."
445 assocDuration OBJECT-TYPE
450 "The value of sysUpTime at the time this association was
451 started. If this association started prior to the last
452 initialization of the network subsystem, then this
453 object contains a zero value."
456 -- Conformance information
458 applConformance OBJECT IDENTIFIER ::= {application 3}
460 applGroups OBJECT IDENTIFIER ::= {applConformance 1}
461 applCompliances OBJECT IDENTIFIER ::= {applConformance 2}
463 -- Compliance statements
465 applCompliance MODULE-COMPLIANCE
468 "The compliance statement for RFC 1565 implementations
469 which support the Network Services Monitoring MIB
470 for basic monitoring of network service applications.
471 This is the basic compliance statement for RFC 1565."
473 MANDATORY-GROUPS {applRFC1565Group}
474 ::= {applCompliances 1}
476 assocCompliance MODULE-COMPLIANCE
479 "The compliance statement for RFC 1565 implementations
480 which support the Network Services Monitoring MIB
481 for basic monitoring of network service applications
482 and their associations."
484 MANDATORY-GROUPS {applRFC1565Group, assocRFC1565Group}
485 ::= {applCompliances 2}
487 applRFC2248Compliance MODULE-COMPLIANCE
490 "The compliance statement for RFC 2248 implementations
491 which support the Network Services Monitoring MIB
492 for basic monitoring of network service applications."
494 MANDATORY-GROUPS {applRFC2248Group}
495 ::= {applCompliances 3}
497 assocRFC2248Compliance MODULE-COMPLIANCE
500 "The compliance statement for RFC 2248 implementations
502 which support the Network Services Monitoring MIB for
503 basic monitoring of network service applications and
506 MANDATORY-GROUPS {applRFC2248Group, assocRFC2248Group}
507 ::= {applCompliances 4}
509 applRFC2788Compliance MODULE-COMPLIANCE
512 "The compliance statement for RFC 2788 implementations
513 which support the Network Services Monitoring MIB
514 for basic monitoring of network service applications."
516 MANDATORY-GROUPS {applRFC2788Group}
517 ::= {applCompliances 5}
519 assocRFC2788Compliance MODULE-COMPLIANCE
522 "The compliance statement for RFC 2788 implementations
523 which support the Network Services Monitoring MIB for
524 basic monitoring of network service applications and
527 MANDATORY-GROUPS {applRFC2788Group, assocRFC2788Group}
528 ::= {applCompliances 6}
530 -- Units of conformance
532 applRFC1565Group OBJECT-GROUP
534 applName, applVersion, applUptime, applOperStatus,
535 applLastChange, applInboundAssociations,
536 applOutboundAssociations, applAccumulatedInboundAssociations,
537 applAccumulatedOutboundAssociations, applLastInboundActivity,
538 applLastOutboundActivity, applRejectedInboundAssociations,
539 applFailedOutboundAssociations}
542 "A collection of objects providing basic monitoring of
543 network service applications. This is the original set
544 of such objects defined in RFC 1565."
547 assocRFC1565Group OBJECT-GROUP
550 assocRemoteApplication, assocApplicationProtocol,
551 assocApplicationType, assocDuration}
554 "A collection of objects providing basic monitoring of
555 network service applications' associations. This is the
556 original set of such objects defined in RFC 1565."
559 applRFC2248Group OBJECT-GROUP
561 applName, applVersion, applUptime, applOperStatus,
562 applLastChange, applInboundAssociations,
563 applOutboundAssociations, applAccumulatedInboundAssociations,
564 applAccumulatedOutboundAssociations, applLastInboundActivity,
565 applLastOutboundActivity, applRejectedInboundAssociations,
566 applFailedOutboundAssociations, applDescription, applURL}
569 "A collection of objects providing basic monitoring of
570 network service applications. This group was originally
571 defined in RFC 2248; note that applDirectoryName is
575 assocRFC2248Group OBJECT-GROUP
577 assocRemoteApplication, assocApplicationProtocol,
578 assocApplicationType, assocDuration}
581 "A collection of objects providing basic monitoring of
582 network service applications' associations. This group
583 was originally defined by RFC 2248."
586 applRFC2788Group OBJECT-GROUP
588 applName, applDirectoryName, applVersion, applUptime,
589 applOperStatus, applLastChange, applInboundAssociations,
590 applOutboundAssociations, applAccumulatedInboundAssociations,
591 applAccumulatedOutboundAssociations, applLastInboundActivity,
592 applLastOutboundActivity, applRejectedInboundAssociations,
593 applFailedOutboundAssociations, applDescription, applURL}
596 "A collection of objects providing basic monitoring of
597 network service applications. This is the appropriate
599 group for RFC 2788 -- it adds the applDirectoryName object
600 missing in RFC 2248."
603 assocRFC2788Group OBJECT-GROUP
605 assocRemoteApplication, assocApplicationProtocol,
606 assocApplicationType, assocDuration}
609 "A collection of objects providing basic monitoring of
610 network service applications' associations. This is
611 the appropriate group for RFC 2788."
614 -- OIDs of the form {applTCPProtoID port} are intended to be used
615 -- for TCP-based protocols that don't have OIDs assigned by other
616 -- means. {applUDPProtoID port} serves the same purpose for
617 -- UDP-based protocols. In either case 'port' corresponds to
618 -- the primary port number being used by the protocol. For example,
619 -- assuming no other OID is assigned for SMTP, an OID of
620 -- {applTCPProtoID 25} could be used, since SMTP is a TCP-based
621 -- protocol that uses port 25 as its primary port.
623 applTCPProtoID OBJECT IDENTIFIER ::= {application 4}
624 applUDPProtoID OBJECT IDENTIFIER ::= {application 5}