idnits 2.17.1 draft-ietf-disman-remops-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 51 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 28 instances of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 1999) is 9106 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '2' is defined on line 2490, but no explicit reference was found in the text == Unused Reference: '12' is defined on line 2538, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 2565, but no explicit reference was found in the text ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '1') ** Obsolete normative reference: RFC 1905 (ref. '6') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2271 (ref. '7') (Obsoleted by RFC 2571) ** Obsolete normative reference: RFC 2272 (ref. '8') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2273 (ref. '9') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2274 (ref. '10') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 2275 (ref. '11') (Obsoleted by RFC 2575) ** Obsolete normative reference: RFC 2028 (ref. '12') (Obsoleted by RFC 9281) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '16') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '17') ** Obsolete normative reference: RFC 1906 (ref. '18') (Obsoleted by RFC 3417) Summary: 18 errors (**), 0 flaws (~~), 6 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 DISMAN Working Group Kenneth White 2 INTERNET DRAFT: IBM Corp. 3 Expiration Date: November 1999 5 May 1999 7 Definitions of Managed Objects for 8 Remote Ping, Traceroute, and 9 Lookup Operations Using SMIv2 10 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with all 15 provisions of Section 10 of RFC2026. Internet Drafts are working 16 documents of the Internet Engineering Task Force (IETF), its Areas, and 17 its Working Groups. Note that other groups may also distribute working 18 documents as Internet Drafts. 20 Internet Drafts are draft documents valid for a maximum of six months. 21 Internet Drafts may be updated, replaced, or obsoleted by other 22 documents at any time. It is not appropriate to use Internet Drafts as 23 reference material or to cite them other than as a "working draft" or 24 "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 Please check the I-D abstract listing contained in each Internet Draft 33 directory to learn the current status of this or any Internet Draft. 34 Distribution of this document is unlimited. 36 Copyright Notice 38 Copyright (C) The Internet Society (1999). All Rights Reserved. 40 Abstract 42 This memo defines Management Information Bases (MIBs) for performing 43 remote ping, traceroute and lookup operations at a remote host. When 44 managing a network it is useful to be able to initiate and retrieve the 45 results of ping or traceroute operations when performed at a remote 46 host. A Lookup capability is defined in order to enable resolving of 47 either an IP address to an DNS name or an DNS name to an IP address at a 48 remote host. 50 Currently, there exists several enterprise defined MIBs for performing 51 both remote ping or traceroute operations. The purpose of this memo is 52 to defined a standards-based solution to enable interoperibility. 54 Table of Contents 56 1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2.0 The SNMP Network Management Framework . . . . . . . . . . . . 4 60 3.0 Structure of the MIBs . . . . . . . . . . . . . . . . . . . . 5 61 3.1 Ping MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 62 3.1.1 pingMaxConcurrentRequests . . . . . . . . . . . . . . . . 6 63 3.1.2 pingCtlTable . . . . . . . . . . . . . . . . . . . . . . . 6 64 3.1.3 pingResultsTable . . . . . . . . . . . . . . . . . . . . . 6 65 3.1.4 pingProbeHistoryTable . . . . . . . . . . . . . . . . . . 6 66 3.2 Traceroute MIB . . . . . . . . . . . . . . . . . . . . . . . . 7 67 3.2.1 traceRouteMaxConcurrentRequests . . . . . . . . . . . . . 7 68 3.2.2 traceRouteCtlTable . . . . . . . . . . . . . . . . . . . . 7 69 3.2.3 traceRouteResultsTable . . . . . . . . . . . . . . . . . . 8 70 3.2.4 traceRouteProbeHistoryTable . . . . . . . . . . . . . . . 8 71 3.3 Lookup MIB . . . . . . . . . . . . . . . . . . . . . . . . . . 8 73 4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 10 74 4.1 DISMAN-PING-MIB . . . . . . . . . . . . . . . . . . . . . . . 10 75 4.2 DISMAN-TRACEROUTE-MIB . . . . . . . . . . . . . . . . . . . . 26 76 4.3 DISMAN-LOOKUP-MIB . . . . . . . . . . . . . . . . . . . . . . 42 78 5.0 Security Considerations . . . . . . . . . . . . . . . . . . . 48 80 6.0 Intellectual Property . . . . . . . . . . . . . . . . . . . . 48 82 7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 48 84 8.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . 48 86 9.0 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 50 88 10.0 Full Copyright Statement . . . . . . . . . . . . . . . . . . 50 90 1.0 Introduction 92 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 93 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 94 document are to be interpreted as described in RFC 2119, reference [13]. 96 This document is a product of the Distributed Management (DISMAN) 97 Working Group. Its purpose is to define standards-based MIB modules for 98 performing specific remote operations. The remote operations define by 99 this document consist of the ping, traceroute and lookup functions. 101 Ping and traceroute are two very useful functions for managing networks. 102 Ping is typically used to determine if a path exists between two hosts 103 while traceroute shows an actual path. Ping is usually implemented 104 using the InterNet Control Message Protocol (ICMP) "ECHO" facility. It 105 is also possible to implement a ping capability using alternate methods. 106 Some of which are: 108 o Using the udp echo port (7), if supported. 110 o Timing an SNMP query. 112 o Timing an TCP connect attempt. 114 In general, almost any request/response flow can be used to generate a 115 round-trip time. Often many of the non-ICMP ECHO facility methods stand 116 a better chance of yielding a good response (not timing out for example) 117 since some routers don't honor Echo Requests (timeout situation) or they 118 are handled at lower priority, hence possibly giving false indications 119 of round trip times. 121 It must be noted that almost any of the various methods used for 122 generating a round-trip time can be considered a form of system attack 123 when used excessively. Sending a system requests too often can 124 negatively effect its performance. Attempting to connect to an used 125 port can be very unpredictable. There are tools that attempt to connect 126 to a range of TCP ports to test that any receiving server can handle 127 erroneous connections attempts. 129 It also can be important to the management application using a remote 130 ping capability to know which method is being used. Different methods 131 will yield different response times since the protocol and resulting 132 processing will be different. It is RECOMMENDED that the ping 133 capability defined within this memo be implemented using the ICMP Echo 134 Facility. 136 Traceroute is usually implemented by transmitting a series of probe 137 packets with increasing time-to-live values. A probe packet is a UDP 138 datagram encapsulated into an IP packet. Each hop in a path to the 139 target (destination) host rejects the probe packet (probe's TTL too 140 small) until its time-to-live value becomes large enough for the probe 141 to be forwarded. Some systems use icmp probes instead of udp ones to 142 implement traceroute. In both cases traceroute relies on the probes 143 being rejected via an ICMP message to discover the hops taken along a 144 path to the final destination. ;p.Implementations of the remote 145 traceroute capability as defined within this memo MUST be done using UDP 146 packets to a (hopefully) unused port. ICMP Echo Request packets MUST 147 NOT be used. Many PC implementations do it incorrectly, which, in turn, 148 causes intermediate hops to be invisible when the router either refuses 149 to send an ICMP TTL expired in response to an incoming ICMP packet or 150 simply tosses ICMP echo requests altogether. 152 Both ping and traceroute yield round-trip times measured in 153 milliseconds. These times can be used as an rough approximation for 154 network transit time. 156 The Lookup operation enables the equivalent of either a gethostbyname() 157 or a gethostbyaddr() call being performed at a remote host. The Lookup 158 gethostbyname() capability can be used to determine the symbolic name of 159 a hop in a traceroute path. 161 Consider the following diagram: 163 +----------------------------------------------------------------------+ 164 | | 165 | Remote ping, traceroute, Actual ping, traceroute, | 166 | +-----+or Lookup op. +------+or Lookup op. +------+ | 167 | |Local|---------------->|Remote|---------------->|Target| | 168 | | Host| | Host | | Host | | 169 | +-----+ +------+ +------+ | 170 | | 171 | | 172 +----------------------------------------------------------------------+ 174 A local host is the host from which the remote ping, traceroute, or 175 Lookup operation is initiated from using an SNMP request. The remote 176 host is a host where the MIBs defined by this memo are implemented that 177 receives the remote operation via SNMP and performs the actual ping, 178 traceroute, or lookup function. 180 2.0 The SNMP Network Management Framework 182 The SNMP Management Framework presently consists of five major 183 components: 185 o An overall architecture, described in RFC 2271 [7]. 187 o Mechanisms for describing and naming objects and events for the 188 purpose of management. The first version of this Structure of 189 Management Information (SMI) is called SMIv1 and described in RFC 190 1155 [14], RFC 1212 [15] and RFC 1215 [16]. The second version, 191 called SMIv2, is described in RFC 2578 [3], RFC 2579 [4] and RFC 192 2580 [5]. 194 o Message protocols for transferring management information. The 195 first version of the SNMP message protocol is called SNMPv1 and 196 described in RFC 1157 [1]. A second version of the SNMP message 197 protocol, which is not an Internet standards track protocol, is 198 called SNMPv2c and described in RFC 1901 [17] and RFC 1906 [18]. 199 The third version of the message protocol is called SNMPv3 and 200 described in RFC 1906 [18], RFC 2272 [8] and RFC 2274 [10]. 202 o Protocol operations for accessing management information. The first 203 set of protocol operations and associated PDU formats is described 204 in RFC 1157 [1]. A second set of protocol operations and associated 205 PDU formats is described in RFC 1905 [6]. 207 o A set of fundamental applications described in RFC 2273 [9] and the 208 view-based access control mechanism described in RFC 2275 [11]. 210 Managed objects are accessed via a virtual information store, termed the 211 Management Information Base or MIB. Objects in the MIB are defined 212 using the mechanisms defined in the SMI. 214 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 215 conforming to the SMIv1 can be produced through the appropriate 216 translations. The resulting translated MIB must be semantically 217 equivalent, except where objects or events are omitted because no 218 translation is possible (use of Counter64). Some machine readable 219 information in SMIv2 will be converted into textual descriptions in 220 SMIv1 during the translation process. However, this loss of machine 221 readable information is not considered to change the semantics of the 222 MIB. 224 3.0 Structure of the MIBs 226 This document defines three MIB modules: 228 o DISMAN-PING-MIB 230 Enables the ping function at a remote host. 232 o DISMAN-TRACEROUTE-MIB 234 Enables the traceroute function at a remote host. 236 o DISMAN-LOOKUP-MIB 238 Provides access to the resolver gethostbyname() and gethostbyaddr() 239 functions at a remote host. 241 The ping and traceroute MIBs are structured to allow creation of ping or 242 traceroute tests that can be setup to periodically issue a series of 243 operations and generate NOTIFICATIONs to report on test results. Many 244 network administrators have in the past written UNIX shell scripts or 245 command bat files to operate in a similar fashion to the functionality 246 provided by the ping and traceroute MIBs defined within this memo. The 247 intent of this document is to acknowledge the importance of these 248 functions and to provide a standards based solution. 250 3.1 Ping MIB 252 The DISMAN-PING-MIB consists of the following components: 254 o pingMaxConcurrentRequests 255 o pingCtlTable 257 o pingResultsTable :li,pingProbeHistoryTable 259 3.1.1 pingMaxConcurrentRequests 261 The object pingMaxConcurrentRequests enable control of the maximum 262 number of concurrent requests that an agent implementation is structured 263 to support. It is permissible for an agent to either limit the maximum 264 upper range allowed for this object or to implement this object as 265 read-only with an implementation limit expressed as its value. 267 3.1.2 pingCtlTable 269 A remote ping test is started by setting pingCtlAdminStatus to up(1). 270 The associating pingCtlEntry MUST have been created and its 271 pingCtlRowStatus set to active(1) prior to starting the test. 273 The 1st index element, pingCtlOwnerIndex, is of the SnmpAdminString 274 textual convention that allows for use of the SNMPv3 View-Based Access 275 Control Model (RFC 2275 [11], VACM) and also allows for a management 276 application to identify its entries. The 2nd index, pingCtlTestName 277 (also an SnmpAdminString), enables the same management application to 278 have multiple requests outstanding. 280 The 3rd and 4th indexes, pingCtlHostAddressType and pingCtlHostAddress, 281 specifies the target address (ipv4, ipv6, or an dnsName) for the 282 operation. 284 Using the maximum value for the parameters defined within an pingEntry 285 can result in a single remote ping test taking at most 15 minutes 286 (pingCtlTimeOut times pingCtlProbeCount) plus whatever time it takes to 287 send the ping request and receive its response over the network from the 288 target host. Use of the defaults for pingCtlTimeOut and 289 pingCtlProbeCount yields a maximum of 3 seconds to perform a "normal" 290 ping test. 292 A management application can delete an active remote ping request by 293 setting the corresponding pingCtlRowStatus object to destroy(6). 295 The contents of the pingCtlTable is preserved across reIPLs (Initial 296 Program Loads) of its agent according the the values of each of the 297 pingCtlStorageType objects. 299 3.1.3 pingResultsTable 301 An entry in the pingResultsTable is created for a corresponding 302 pingCtlEntry once the test defined by this entry is started. 304 3.1.4 pingProbeHistoryTable 306 The results of past ping probes can be stored in this table on an per 307 pingCtlEntry basis. This table is initially indexed by 308 pingCtlOwnerIndex and pingCtlTestName in order for the results of a 309 probe to relate to the pingCtlEntry that caused it. The number of 310 entries stored in this table per pingCtlEntry is determined by the value 311 of pingCtlMaxRows. 313 An implementation of this MIB will remove the oldest entry in the 314 pingProbeHistoryTable to allow the addition of an new entry once the 315 number of rows in the pingProbeHistoryTable reaches the value specified 316 by pingCtlMaxRows. Entries will be removed on the basis of oldest 317 pingProbeHistoryTime value first. 319 3.2 Traceroute MIB 321 The DISMAN-TRACEROUTE-MIB consists of the following components: 323 o traceRouteMaxConcurrentRequests 325 o traceRouteCtlTable 327 o traceRouteResultsTable 329 o traceRouteProbeHistoryTable 331 3.2.1 traceRouteMaxConcurrentRequests 333 The object traceRouteMaxConcurrentRequests enable control of the maximum 334 number of concurrent requests that an agent implementation is structured 335 to support. It is permissible for an agent to either limit the maximum 336 upper range allowed for this object or to implement this object as 337 read-only with an implementation limit expressed as its value. 339 3.2.2 traceRouteCtlTable 341 A remote traceroute test is started by setting traceRouteCtlAdminStatus 342 to up(1). The associating traceRouteCtlEntry MUST have been created and 343 its traceRouteCtlRowStatus set to active(1) prior to starting the test. 345 The 1st index element, traceRouteCtlOwnerIndex, is of the 346 SnmpAdminString textual convention that allows for use of the SNMPv3 347 View-Based Access Control Model (RFC 2275 [11], VACM) and also allows 348 for a management application to identify its entries. The 2nd index, 349 traceRouteCtlTestName (also an SnmpAdminString), enables the same 350 management application to have multiple requests outstanding. 352 The 3rd and 4th indexes, traceRouteCtlHostAddressType and 353 traceRouteCtlHostAddress, specifies the target address (ipv4, ipv6, or 354 an dnsName) for the operation. 356 Traceroute has a much longer theoretical maximum time for completion 357 then ping. Basically 42 hours and 30 minutes (the product of 358 traceRouteCtlTimeOut, traceRouteCtlProbesPerHop, and 359 traceRouteCtlMaxTtl) plus some network transit time! Use of the 360 defaults defined within an traceRouteCtlEntry yields a maximum of 4 361 minutes and 30 seconds for a default traceroute operation. Clearly 42 362 plus hours is too long to wait for a traceroute operation to complete. 364 The maximum TTL value in effect for traceroute determines how long the 365 traceroute function will keep increasing the TTL value in the probe it 366 transmits hoping to reach the target host. The function ends whenever 367 the maximum TTL is exceeded or the target host is reached. The object 368 traceRouteCtlMaxFailures was created in order to impose a throttle for 369 how long traceroute continues to increase the TTL field in a probe 370 without receiving any kind of response (timeouts). It is RECOMMENDED 371 that agent implementations impose a time limit for how long it allows a 372 traceroute operation to take relative to how the function is 373 implemented. For example, an implemented that can't process multiple 374 traceroute operations at the same time SHOULD impose a shorter maximum 375 allowed time period. 377 A management application can delete an active remote traceroute request 378 by setting the corresponding traceRouteCtlRowStatus object to 379 destroy(6). 381 The contents of the traceRouteCtlTable is preserved across reIPLs 382 (Initial Program Loads) of its agent according the the values of each of 383 the pingCtlStorageType objects. 385 3.2.3 traceRouteResultsTable 387 An entry in the traceRouteResultsTable is created for a corresponding 388 traceRouteCtlEntry once the test defined by this entry is started. The 389 objects traceRouteResultsCurHopCount and traceRouteResultsCurProbeCount 390 can be examined to determine how far the current remote traceroute 391 operation has reached. 393 3.2.4 traceRouteProbeHistoryTable 395 The results of past traceroute probes can be stored in this table on an 396 per traceRouteCtlEntry basis. This table is initially indexed by 397 traceRouteCtlOwnerIndex and traceRouteCtlTestName in order for the 398 results of a probe to relate to the traceRouteCtlEntry that caused it. 399 The number of entries stored in this table per traceRouteCtlEntry is 400 determined by the value of traceRouteCtlMaxRows. 402 An implementation of this MIB will remove the oldest entry in the 403 traceRouteProbeHistoryTable to allow the addition of an new entry once 404 the number of rows in the traceRouteProbeHistoryTable reaches the value 405 of traceRouteCtlMaxRows. Entries will be removed on the basis of oldest 406 traceRouteProbeHistoryTime value first. 408 3.3 Lookup MIB 410 The DISMAN-LOOKUP-MIB consists of the following components: 412 o lookupMaxConcurrentRequests, and lookupPurgeTime 413 o lookupTable 415 The object lookupMaxConcurrentRequests enable control of the maximum 416 number of concurrent requests that an agent implementation is structured 417 to support. It is permissible for an agent to either limit the maximum 418 upper range allowed for this object or to implement this object as 419 read-only with an implementation limit expressed as its value. 421 The object lookupPurgeTime provides a method for entries in the 422 lookupTable to be automatically deleted after the associating operation 423 completes. 425 A remote lookup operation is initiated by performing an SNMP SET request 426 on lookupRowStatus. An lookupEntry is initially indexed by 427 lookupOwnerIndex, which is of the SnmpAdminString textual convention 428 that allows for use of the SNMPv3 View-Based Access Control Model (RFC 429 2275 [11], VACM) and also allows for a management application to 430 identify its entries. The lookupOwnerIndex portion of the index is then 431 followed by lookupOperationName, lookupAddressType, and lookupAddress. 432 lookupOperationName enables the same lookupOwnerIndex entity to have 433 multiple outstanding requests. 435 The index element lookupAddressType preceeds lookupAddress and specifies 436 the type of address for either performing a gethostbyname or a 437 gethostbyaddr call at a remote host. The value of this index element 438 determines whether to invoke either the gethostbyname or the 439 gethostbyaddr operation. Specification of a dnsName(2) implies that 440 gethostbyname should be called to return a numeric address. Use of a 441 value of either ipv4(3) or ipv6(4) implies that a gethostbyaddr call 442 should occur to return the symbolic name of a remote host. 444 A remote lookup operation is started by transitioning its 445 lookupRowStatus object to active(1). The object lookupOperStatus can be 446 examined to determine the state of an lookup operation. A management 447 application can delete an active remote lookup request by setting the 448 corresponding lookupRowStatus object to destroy(6). 450 An implementation SHOULD NOT retain SNMP-created entries in the 451 lookupTable across reIPLs (Initial Program Loads) of its agent, since 452 management applications need to see consistent behavior with respect to 453 the persistence of the table entries that they create. 455 4.0 Definitions 457 4.1 DISMAN-PING-MIB 459 DISMAN-PING-MIB DEFINITIONS ::= BEGIN 461 IMPORTS 462 MODULE-IDENTITY, OBJECT-TYPE, Integer32, 463 experimental, Counter32, Unsigned32, 464 NOTIFICATION-TYPE 465 FROM SNMPv2-SMI -- RFC1902 466 TEXTUAL-CONVENTION, RowStatus, 467 StorageType, DateAndTime 468 FROM SNMPv2-TC -- RFC1903 469 MODULE-COMPLIANCE, OBJECT-GROUP, 470 NOTIFICATION-GROUP 471 FROM SNMPv2-CONF -- RFC1904 472 SnmpAdminString 473 FROM SNMP-FRAMEWORK-MIB; -- RFC2271 475 pingMIB MODULE-IDENTITY 476 LAST-UPDATED "9904300000Z" 477 ORGANIZATION "IETF Distributed Management Working Group" 478 CONTACT-INFO 479 "Kenneth White 481 International Business Machines Corporation 482 Network Computing Software Division 483 Research Triangle Park, NC, USA 485 E-mail: wkenneth@us.ibm.com" 486 DESCRIPTION 487 "The Ping MIB (DISMAN-PING-MIB) provides the capability of 488 controlling the use of the ping function at a remote 489 host." 490 ::= { experimental 84 1 } 492 -- Textual Conventions 494 HostAddressType ::= TEXTUAL-CONVENTION 495 STATUS current 496 DESCRIPTION 497 "The textual convention for defining the type of 498 a destination address." 499 SYNTAX INTEGER { 500 none(1), 501 dnsName(2), -- Utf8string encoded DNS name 502 ipv4(3), -- ipv4 address 503 ipv6(4) -- ipv6 address 504 } 506 HostAddress ::= TEXTUAL-CONVENTION 507 STATUS current 508 DESCRIPTION 509 "The textual convention for specifying a host 510 address. The type of address can be determined 511 by examining the value of the preceding 512 HostAddressType object: 514 HostAddressType OCTETs ADDRESS TYPE 515 none(0) 0 not specified 516 dnsName(2) 1-255 DNS name 517 ipv4(3) 4 ipv4 518 ipv6(4) 16 ipv6" 519 SYNTAX OCTET STRING (SIZE (0..65)) 521 IpHostAddress ::= TEXTUAL-CONVENTION 522 STATUS current 523 DESCRIPTION 524 "The textual convention for specifying an IP host 525 address. The type of address can be determined 526 by the octet string length: 528 OCTETs ADDRESS TYPE 529 0 not specified 530 4 ipv4 531 16 ipv6" 532 SYNTAX OCTET STRING (SIZE (0..16)) 534 OperationResponseStatus ::= TEXTUAL-CONVENTION 535 STATUS current 536 DESCRIPTION 537 "Used to report the result of an operation: 539 responseReceived(1) - Operation completes successfully. 540 unknown(2) - Operation failed due to unknown error. 541 internalError(3) - An implementation detected an error 542 in its own processing that caused an operation 543 to fail. 544 requestTimedOut(4) - Operation failed to receive a 545 valid reply within the time limit imposed on it. 546 unknownDestinationAddress(5) - Invalid destination 547 address. 548 noRouteToTarget(6) - Could not find a route to target. 549 interfaceInactiveToTarget(7) - The interface to be 550 used in sending a probe is inactive without an 551 alternate route existing. 552 arpFailure(8) - Unable to resolve a target address to a 553 media specific address. 554 maxConcurrentLimitReached(9) - The maximum number of 555 concurrent operations would have been exceeded if 556 the associating operation was allowed. 557 unableToResolveDnsName(10) - The DNS name specified was 558 unable to be mapped to an IP address." 559 SYNTAX INTEGER { 560 responseReceived(1), 561 unknown(2), 562 internalError(3), 563 requestTimedOut(4), 564 unknownDestinationAddress(5), 565 noRouteToTarget(6), 566 interfaceInactiveToTarget(7), 567 arpFailure(8), 568 maxConcurrentLimitReached(9), 569 unableToResolveDnsName(10) 570 } 572 -- Top level structure of the MIB 574 pingNotifications OBJECT IDENTIFIER ::= { pingMIB 0 } 575 pingObjects OBJECT IDENTIFIER ::= { pingMIB 1 } 576 pingConformance OBJECT IDENTIFIER ::= { pingMIB 2 } 578 -- Simple Object Definitions 580 pingMaxConcurrentRequests OBJECT-TYPE 581 SYNTAX Integer32 (1..100) 582 MAX-ACCESS read-write 583 STATUS current 584 DESCRIPTION 585 "The maximum number of concurrent active ping requests 586 that are allowed within an agent implementation." 587 DEFVAL { 10 } 588 ::= { pingObjects 1 } 590 -- Ping Control Table 592 pingCtlTable OBJECT-TYPE 593 SYNTAX SEQUENCE OF PingCtlEntry 594 MAX-ACCESS not-accessible 595 STATUS current 596 DESCRIPTION 597 "Defines the ping Control Table for provide, via SNMP, 598 the capability of performing ping operations at 599 a remote host. The results of these operations are 600 stored in the pingResultsTable and the pingProbeHistoryTable." 601 ::= { pingObjects 2 } 603 pingCtlEntry OBJECT-TYPE 604 SYNTAX PingCtlEntry 605 MAX-ACCESS not-accessible 606 STATUS current 607 DESCRIPTION 608 "Defines an entry in the pingCtlTable." 609 INDEX { 610 pingCtlOwnerIndex, 611 pingCtlTestName 612 } 614 ::= { pingCtlTable 1 } 616 PingCtlEntry ::= 617 SEQUENCE { 618 pingCtlOwnerIndex SnmpAdminString, 619 pingCtlTestName SnmpAdminString, 620 pingCtlHostAddressType HostAddressType, 621 pingCtlHostAddress HostAddress, 622 pingCtlDataSize Integer32, 623 pingCtlTimeOut Integer32, 624 pingCtlProbeCount Integer32, 625 pingCtlAdminStatus INTEGER, 626 pingCtlDataFill OCTET STRING, 627 pingCtlFrequency Integer32, 628 pingCtlMaxRows Integer32, 629 pingCtlStorageType StorageType, 630 pingCtlTrapGeneration INTEGER, 631 pingCtlTrapFilter Integer32, 632 pingCtlRowStatus RowStatus 633 } 635 pingCtlOwnerIndex OBJECT-TYPE 636 SYNTAX SnmpAdminString (SIZE(0..32)) 637 MAX-ACCESS not-accessible 638 STATUS current 639 DESCRIPTION 640 "To facilitate the provisioning of access control by a security 641 administrator using the View-Based Access Control Model (RFC 2275, 642 VACM) for tables in which multiple users may need to independently 643 create or modify entries, the initial index is used as an 'owner 644 index'. Such an initial index has a syntax of SnmpAdminString, 645 and can thus be trivially mapped to a securityName or groupName 646 as defined in VACM, in accordance with a security policy. 648 All entries in that table belonging to a particular user will 649 have the same value for this initial index. For a given user's 650 entries in a particular table, the object identifiers for the 651 information in these entries will have the same subidentifiers 652 (except for the 'column' subidentifier) up to the end of the 653 encoded owner index. To configure VACM to permit access to this 654 portion of the table, one would create vacmViewTreeFamilyTable 655 entries with the value of vacmViewTreeFamilySubtree including the 656 owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the 657 column subidentifier. More elaborate configurations are 658 possible." 659 ::= { pingCtlEntry 1 } 661 pingCtlTestName OBJECT-TYPE 662 SYNTAX SnmpAdminString 663 MAX-ACCESS not-accessible 664 STATUS current 665 DESCRIPTION 666 "The name of the ping test. This is locally unique, within 667 the scope of an pingCtlOwnerIndex." 668 ::= { pingCtlEntry 2 } 670 pingCtlHostAddressType OBJECT-TYPE 671 SYNTAX HostAddressType 672 MAX-ACCESS read-create 673 STATUS current 674 DESCRIPTION 675 "Specifies the type of host address to be used at a remote host 676 for performing a ping operation." 677 DEFVAL { ipv4 } 678 ::= { pingCtlEntry 3 } 680 pingCtlHostAddress OBJECT-TYPE 681 SYNTAX HostAddress 682 MAX-ACCESS read-create 683 STATUS current 684 DESCRIPTION 685 "Specifies the host address to be used at a remote host for 686 performing a ping operation. The host address type is 687 determined by its octet string length. Refer to the 688 definition of the TEXTUAL-CONVENTION HostAddress." 689 ::= { pingCtlEntry 4 } 691 pingCtlDataSize OBJECT-TYPE 692 SYNTAX Integer32 (0..65507) 693 UNITS "octets" 694 MAX-ACCESS read-create 695 STATUS current 696 DESCRIPTION 697 "Specifies the size of the data portion to be 698 transmitted in a ping operation in octets. A ping 699 request is usually an ICMP message encoded 700 into an IP packet. An IP packet has a maximum size 701 of 65535 octets. Subtracting the size of the ICMP 702 header (8 octets) and the size of the IP header 703 (20 octets) yields a maximum size of 65507 octets." 704 DEFVAL { 0 } 705 ::= { pingCtlEntry 5 } 707 pingCtlTimeOut OBJECT-TYPE 708 SYNTAX Integer32 (1..60) 709 UNITS "seconds" 710 MAX-ACCESS read-create 711 STATUS current 712 DESCRIPTION 713 "Specifies the time-out value, in seconds, for an 714 remote ping operation." 715 DEFVAL { 3 } 716 ::= { pingCtlEntry 6 } 718 pingCtlProbeCount OBJECT-TYPE 719 SYNTAX Integer32 (1..15) 720 UNITS "probes" 721 MAX-ACCESS read-create 722 STATUS current 723 DESCRIPTION 724 "Specifies the number of times to perform a ping 725 opertion at a remote host." 726 DEFVAL { 1 } 727 ::= { pingCtlEntry 7 } 729 pingCtlAdminStatus OBJECT-TYPE 730 SYNTAX INTEGER { 731 up(1), -- test should be started 732 down(2) -- test should be stop 733 } 734 MAX-ACCESS read-create 735 STATUS current 736 DESCRIPTION 737 "Reflects the desired state that a pingCtlEntry should be 738 in: 740 up(1) - Attempt to active the test as defined by 741 this pingCtlEntry. 742 down(1) - Deactivate the test as defined by this 743 pingCtlEntry. 745 Refer to the corresponding pingResultsOperStatus to 746 determine the operational state of the test defined by 747 this entry." 748 DEFVAL { down } 749 ::= { pingCtlEntry 8 } 751 pingCtlDataFill OBJECT-TYPE 752 SYNTAX OCTET STRING (SIZE(0..1024)) 753 MAX-ACCESS read-create 754 STATUS current 755 DESCRIPTION 756 "The content of this object is used together with the correspond 757 pingCtlDataSize value to determine how to fill the data portion 758 of a probe packet. The option of selecting a data fill pattern 759 can be useful when links are compressed or have data pattern 760 sensitivities." 761 DEFVAL { '00'H } 762 ::= { pingCtlEntry 9 } 764 pingCtlFrequency OBJECT-TYPE 765 SYNTAX Integer32 766 UNITS "seconds" 767 MAX-ACCESS read-create 768 STATUS current 769 DESCRIPTION 770 "The number of seconds to wait before repeating a ping test 771 as defined by the value of the various objects in the 772 corresponding row." 774 DEFVAL { 0 } 775 ::= { pingCtlEntry 10 } 777 pingCtlMaxRows OBJECT-TYPE 778 SYNTAX Integer32 (0..1500) 779 MAX-ACCESS read-create 780 STATUS current 781 DESCRIPTION 782 "The maximum number of entries allowed in the 783 pingProbeHistoryTable. An implementation of this 784 MIB will remove the oldest entry in the 785 pingProbeHistoryTable to allow the addition of an 786 new entry once the number of rows in the 787 pingProbeHistoryTable reaches this value. 788 Entries will be removed on the basis of oldest 789 pingProbeHistoryTime value first. 791 A value of 0 for this object disables creation of 792 pingProbeHistoryTable entries." 793 DEFVAL { 50 } 794 ::= { pingCtlEntry 11 } 796 pingCtlStorageType OBJECT-TYPE 797 SYNTAX StorageType 798 MAX-ACCESS read-create 799 STATUS current 800 DESCRIPTION 801 "The storage type for this conceptual row. 802 Conceptual rows having the value 'permanent' need not 803 allow write-access to any columnar objects in the row." 804 DEFVAL { nonVolatile } 805 ::= { pingCtlEntry 12 } 807 pingCtlTrapGeneration OBJECT-TYPE 808 SYNTAX INTEGER { 809 none(1), 810 probeFailure(2), 811 testFailure(3), 812 testCompletion(4) 813 } 814 MAX-ACCESS read-create 815 STATUS current 816 DESCRIPTION 817 "The value of this object determines when and if to 818 to generation a notification for this entry: 820 none(1) - Don't generation any notifications. 821 probeFailure(2) - Generate a pingProbeFailed 822 notification subject to the value of 823 pingCtlTrapFilter. pingCtlTrapFilter can be used 824 to specify the number of successive probe failures 825 that are required before a pingProbeFailed 826 notification can be generated. 828 testFailure(3) - Generate a pingTestFailed 829 notification. In this instance pingCtlTrapFilter 830 should specify the number of probe failures 831 required in a test to have failed in order to 832 considered the test as failed. 833 testCompletion(4) - Generate a pingTestCompleted 834 notification." 835 DEFVAL { none } 836 ::= { pingCtlEntry 13 } 838 pingCtlTrapFilter OBJECT-TYPE 839 SYNTAX Integer32 (0..15) 840 MAX-ACCESS read-create 841 STATUS current 842 DESCRIPTION 843 "The value of this object is used to determine when 844 to generate either a pingProbeFailed or a 845 pingTestFailed NOTIFICATION. Which NOTIFICATION 846 to generate is determined by the value of 847 pingCtlTrapGeneration. 849 Setting pingCtlTrapGeneration 850 to probeFailure(2) implies that a pingProbeFailed 851 NOTIFICATION is generated only when the number of 852 successive probe failures as indicated by the 853 value of pingCtlTrapFilter fail within a given ping 854 test. 856 Setting pingCtlTrapGeneration to testFailure(3) 857 implies that a pingTestFailed NOTIFICATION is 858 generated only when the number of ping failures 859 within a test exceed the value of 860 pingCtlTrapFilter." 861 DEFVAL { 1 } 862 ::= { pingCtlEntry 14 } 864 pingCtlRowStatus OBJECT-TYPE 865 SYNTAX RowStatus 866 MAX-ACCESS read-create 867 STATUS current 868 DESCRIPTION 869 "This object allows entries to be created and deleted 870 in the pingCtlTable. Deletion of an entry in this 871 table results in all corresponding (same 872 pingCtlOwnerIndex and pingCtlTestName index values) 873 pingResultsTable and pingProbeHistoryTable entries 874 being deleted. 876 Activation of a remote ping operation is controlled 877 via pingCtlAdminStatus and not by transitioning of 878 this object's value to active(1). 880 Transitions in and out of active(1) state are not 881 allowed while an entry's pingResultsOperStatus is 882 active(1) with the exception that deletion of 883 an entry in this table by setting its RowStatus 884 object to destroy(6) will stop an active 885 ping operation. 887 The operational state of an ping operation 888 can be determined by examination of it's 889 pingResultsOperStatus object." 890 REFERENCE 891 "RFC 2579, 'Textual Conventions for SMIv2.'" 892 ::= { pingCtlEntry 15 } 894 -- Ping Results Table 896 pingResultsTable OBJECT-TYPE 897 SYNTAX SEQUENCE OF PingResultsEntry 898 MAX-ACCESS not-accessible 899 STATUS current 900 DESCRIPTION 901 "Defines the Ping Results Table for providing 902 the capability of performing ping operations at 903 a remote host. The results of these operations are 904 stored in the pingResultsTable and the pingPastProbeTable." 905 ::= { pingObjects 3 } 907 pingResultsEntry OBJECT-TYPE 908 SYNTAX PingResultsEntry 909 MAX-ACCESS not-accessible 910 STATUS current 911 DESCRIPTION 912 "Defines an entry in the pingResultsTable." 913 INDEX { 914 pingCtlOwnerIndex, 915 pingCtlTestName 916 } 917 ::= { pingResultsTable 1 } 919 PingResultsEntry ::= 920 SEQUENCE { 921 pingResultsOperStatus INTEGER, 922 pingResultsIpHostAddress IpHostAddress, 923 pingResultsMinRtt Unsigned32, 924 pingResultsMaxRtt Unsigned32, 925 pingResultsAverageRtt Unsigned32, 926 pingResultsProbeResponses Counter32, 927 pingResultsSentProbes Counter32, 928 pingResultsRttSumOfSquares Unsigned32, 929 pingResultsLastGoodProbe DateAndTime 930 } 932 pingResultsOperStatus OBJECT-TYPE 933 SYNTAX INTEGER { 934 up(1), -- test is in progress 935 down(2) -- test has stopped 936 } 937 MAX-ACCESS read-only 938 STATUS current 939 DESCRIPTION 940 "Reflects the operational state of an pingCtlEntry: 942 up(1) - Test is active. 943 down(1) - Test has stopped." 944 ::= { pingResultsEntry 1 } 946 pingResultsIpHostAddress OBJECT-TYPE 947 SYNTAX IpHostAddress 948 MAX-ACCESS read-only 949 STATUS current 950 DESCRIPTION 951 "This objects reports the IP address associated 952 with a pingCtlHostAddress value when the destination 953 address is specified as a DNS name. The value of 954 this object should be a zero length octet string 955 when a DNS name is not specified or when a 956 specified DNS name fails to resolve." 957 ::= { pingResultsEntry 2 } 959 pingResultsMinRtt OBJECT-TYPE 960 SYNTAX Unsigned32 961 MAX-ACCESS read-only 962 STATUS current 963 DESCRIPTION 964 "The minimum ping round-trip-time (RTT) received. A value 965 of 0 for this object implies that no RTT has been received." 966 ::= { pingResultsEntry 3 } 968 pingResultsMaxRtt OBJECT-TYPE 969 SYNTAX Unsigned32 970 MAX-ACCESS read-only 971 STATUS current 972 DESCRIPTION 973 "The maximum ping round-trip-time (RTT) received. A value 974 of 0 for this object implies that no RTT has been received." 975 ::= { pingResultsEntry 4 } 977 pingResultsAverageRtt OBJECT-TYPE 978 SYNTAX Unsigned32 979 MAX-ACCESS read-only 980 STATUS current 981 DESCRIPTION 982 "The current average ping round-trip-time (RTT)." 983 ::= { pingResultsEntry 5 } 985 pingResultsProbeResponses OBJECT-TYPE 986 SYNTAX Counter32 987 MAX-ACCESS read-only 988 STATUS current 989 DESCRIPTION 990 "Number of responses received for the corresponding 991 pingCtlEntry and pingResultsEntry." 992 ::= { pingResultsEntry 6 } 994 pingResultsSentProbes OBJECT-TYPE 995 SYNTAX Counter32 996 MAX-ACCESS read-only 997 STATUS current 998 DESCRIPTION 999 "The value of this object reflects the number of probes sent 1000 for the corresponding pingCtlEntry and pingResultsEntry." 1001 ::= { pingResultsEntry 7 } 1003 pingResultsRttSumOfSquares OBJECT-TYPE 1004 SYNTAX Unsigned32 1005 MAX-ACCESS read-only 1006 STATUS current 1007 DESCRIPTION 1008 "This object contains the sum of all ping responses received. 1009 Its purpose is to enable standard deviation calculation." 1010 ::= { pingResultsEntry 8 } 1012 pingResultsLastGoodProbe OBJECT-TYPE 1013 SYNTAX DateAndTime 1014 MAX-ACCESS read-only 1015 STATUS current 1016 DESCRIPTION 1017 "Date and time was the last response was received for a probe." 1018 ::= { pingResultsEntry 9 } 1020 -- Ping Probe History Table 1022 pingProbeHistoryTable OBJECT-TYPE 1023 SYNTAX SEQUENCE OF PingProbeHistoryEntry 1024 MAX-ACCESS not-accessible 1025 STATUS current 1026 DESCRIPTION 1027 "Defines a table for storing the results of a ping 1028 operation. Entries in this table is limited by 1029 the value of the corresponding pingCtlMaxRows 1030 object. 1032 An implementation of this MIB will remove the oldest 1033 entry in the pingProbeHistoryTable to allow the 1034 addition of an new entry once the number of rows in 1035 the pingProbeHistoryTable reaches the value specified 1036 by pingCtlMaxRows. Entries will be removed on the 1037 basis of oldest pingProbeHistoryTime value first." 1039 ::= { pingObjects 4 } 1041 pingProbeHistoryEntry OBJECT-TYPE 1042 SYNTAX PingProbeHistoryEntry 1043 MAX-ACCESS not-accessible 1044 STATUS current 1045 DESCRIPTION 1046 "Defines a table for storing the results of a ping 1047 operation. Entries in this table is limited by 1048 the value of the corresponding pingCtlMaxRows 1049 object. 1051 An implementation of this MIB will remove the oldest 1052 entry in the pingProbeHistoryTable to allow the 1053 addition of an new entry once the number of rows in 1054 the pingProbeHistoryTable reaches the value specified 1055 by pingCtlMaxRows. Entries will be removed on the 1056 basis of oldest pingProbeHistoryTime value first." 1057 INDEX { 1058 pingCtlOwnerIndex, 1059 pingCtlTestName, 1060 pingProbeHistoryIndex 1061 } 1062 ::= { pingProbeHistoryTable 1 } 1064 PingProbeHistoryEntry ::= 1065 SEQUENCE { 1066 pingProbeHistoryIndex Unsigned32, 1067 pingProbeHistoryResponse Integer32, 1068 pingProbeHistoryStatus OperationResponseStatus, 1069 pingProbeHistoryLastReplyCode Integer32, 1070 pingProbeHistoryTime DateAndTime 1071 } 1073 pingProbeHistoryIndex OBJECT-TYPE 1074 SYNTAX Unsigned32 (1..'ffffffff'h) 1075 MAX-ACCESS not-accessible 1076 STATUS current 1077 DESCRIPTION 1078 "An entry in this table is created when the results of 1079 a ping probe is determined. The initial 2 instance 1080 identifier index values identifies the pingCtlEntry 1081 that a probe result (pingProbeHistoryEntry) belongs 1082 to." 1083 ::= { pingProbeHistoryEntry 1 } 1085 pingProbeHistoryResponse OBJECT-TYPE 1086 SYNTAX Integer32 1087 UNITS "milliseconds" 1088 MAX-ACCESS read-only 1089 STATUS current 1090 DESCRIPTION 1091 "The amount of time measured in milliseconds from when 1092 a probe was sent to when its response was received or 1093 when it timed out. The value of this object is reported 1094 as 0 when it is not possible to transmit a probe." 1095 ::= { pingProbeHistoryEntry 2 } 1097 pingProbeHistoryStatus OBJECT-TYPE 1098 SYNTAX OperationResponseStatus 1099 MAX-ACCESS read-only 1100 STATUS current 1101 DESCRIPTION 1102 "The result of a ping operation made by a remote host 1103 for a particular probe." 1104 ::= { pingProbeHistoryEntry 3 } 1106 pingProbeHistoryLastReplyCode OBJECT-TYPE 1107 SYNTAX Integer32 1108 MAX-ACCESS read-only 1109 STATUS current 1110 DESCRIPTION 1111 "The last implementation method specific reply code received. 1112 If the ICMP Echo capability is being used then a successful 1113 probe ends when an ICMP response is received that contains 1114 the code ICMP_ECHOREPLY(0)." 1115 ::= { pingProbeHistoryEntry 4 } 1117 pingProbeHistoryTime OBJECT-TYPE 1118 SYNTAX DateAndTime 1119 MAX-ACCESS read-only 1120 STATUS current 1121 DESCRIPTION 1122 "Timestamp for when this probe results was determined." 1123 ::= { pingProbeHistoryEntry 5 } 1125 -- Notification Definition section 1127 pingProbeFailed NOTIFICATION-TYPE 1128 OBJECTS { 1129 pingCtlHostAddressType, 1130 pingCtlHostAddress, 1131 pingResultsOperStatus, 1132 pingResultsIpHostAddress, 1133 pingResultsMinRtt, 1134 pingResultsMaxRtt, 1135 pingResultsAverageRtt, 1136 pingResultsProbeResponses, 1137 pingResultsSentProbes, 1138 pingResultsRttSumOfSquares, 1139 pingResultsLastGoodProbe 1140 } 1141 STATUS current 1142 DESCRIPTION 1143 "Generated when a probe failure is detected when the 1144 corresponding pingCtlTrapGeneration object is set to 1145 probeFailure(2) subject to the value of pingCtlTrapFilter. 1146 pingCtlTrapFilter can be used to specify the number of 1147 successive probe failures that are required before this 1148 notification can be generated." 1149 ::= { pingNotifications 1 } 1151 pingTestFailed NOTIFICATION-TYPE 1152 OBJECTS { 1153 pingCtlHostAddressType, 1154 pingCtlHostAddress, 1155 pingResultsOperStatus, 1156 pingResultsIpHostAddress, 1157 pingResultsMinRtt, 1158 pingResultsMaxRtt, 1159 pingResultsAverageRtt, 1160 pingResultsProbeResponses, 1161 pingResultsSentProbes, 1162 pingResultsRttSumOfSquares, 1163 pingResultsLastGoodProbe 1164 } 1165 STATUS current 1166 DESCRIPTION 1167 "Generated when a ping test is determined to have failed 1168 when the corresponding pingCtlTrapGeneration object is set to 1169 testFailure(3). In this instance pingCtlTrapFilter 1170 should specify the number of probe failures 1171 required in a test to have failed in order to 1172 considered the test as failed." 1173 ::= { pingNotifications 2 } 1175 pingTestCompleted NOTIFICATION-TYPE 1176 OBJECTS { 1177 pingCtlHostAddressType, 1178 pingCtlHostAddress, 1179 pingResultsOperStatus, 1180 pingResultsIpHostAddress, 1181 pingResultsMinRtt, 1182 pingResultsMaxRtt, 1183 pingResultsAverageRtt, 1184 pingResultsProbeResponses, 1185 pingResultsSentProbes, 1186 pingResultsRttSumOfSquares, 1187 pingResultsLastGoodProbe 1188 } 1189 STATUS current 1190 DESCRIPTION 1191 "Generated at the completion of a ping test when the 1192 corresponding pingCtlTrapGeneration object is set to 1193 testCompletion(4)." 1194 ::= { pingNotifications 3 } 1196 -- Conformance information 1197 -- Compliance statements 1199 pingCompliances OBJECT IDENTIFIER ::= { pingConformance 1 } 1200 pingGroups OBJECT IDENTIFIER ::= { pingConformance 2 } 1202 -- Compliance statements 1204 pingCompliance MODULE-COMPLIANCE 1205 STATUS current 1206 DESCRIPTION 1207 "The compliance statement for the DISMAN-PING-MIB." 1208 MODULE -- this module 1209 MANDATORY-GROUPS { 1210 pingGroup, 1211 pingNotificationsGroup 1212 } 1213 GROUP pingTimeStampGroup 1214 DESCRIPTION 1215 "This group is mandatory for implementations that have 1216 access to a system clock and are capable of setting 1217 the values for DateAndTime objects." 1219 OBJECT pingMaxConcurrentRequests 1220 MIN-ACCESS read-only 1221 DESCRIPTION 1222 "The agent is not required to support a SET 1223 operation to this object." 1225 OBJECT pingCtlStorageType 1226 MIN-ACCESS read-only 1227 DESCRIPTION 1228 "Write access is not required." 1230 ::= { pingCompliances 1 } 1232 -- MIB groupings 1234 pingGroup OBJECT-GROUP 1235 OBJECTS { 1236 pingMaxConcurrentRequests, 1237 pingCtlHostAddressType, 1238 pingCtlHostAddress, 1239 pingCtlDataSize, 1240 pingCtlTimeOut, 1241 pingCtlProbeCount, 1242 pingCtlAdminStatus, 1243 pingCtlDataFill, 1244 pingCtlFrequency, 1245 pingCtlMaxRows, 1246 pingCtlStorageType, 1247 pingCtlTrapGeneration, 1248 pingCtlTrapFilter, 1249 pingCtlRowStatus, 1250 pingResultsOperStatus, 1251 pingResultsIpHostAddress, 1252 pingResultsMinRtt, 1253 pingResultsMaxRtt, 1254 pingResultsAverageRtt, 1255 pingResultsProbeResponses, 1256 pingResultsSentProbes, 1257 pingResultsRttSumOfSquares, 1258 pingProbeHistoryResponse, 1259 pingProbeHistoryStatus, 1260 pingProbeHistoryLastReplyCode 1261 } 1262 STATUS current 1263 DESCRIPTION 1264 "The group of objects that comprise the remote ping 1265 capability." 1266 ::= { pingGroups 1 } 1268 pingTimeStampGroup OBJECT-GROUP 1269 OBJECTS { 1270 pingResultsLastGoodProbe, 1271 pingProbeHistoryTime 1272 } 1273 STATUS current 1274 DESCRIPTION 1275 "The group of DateAndTime objects." 1276 ::= { pingGroups 2 } 1278 pingNotificationsGroup NOTIFICATION-GROUP 1279 NOTIFICATIONS { 1280 pingProbeFailed, 1281 pingTestFailed, 1282 pingTestCompleted 1283 } 1284 STATUS current 1285 DESCRIPTION 1286 "The notification which are required to be supported by 1287 implementations of this MIB." 1288 ::= { pingGroups 3 } 1290 END 1292 4.2 DISMAN-TRACEROUTE-MIB 1294 DISMAN-TRACEROUTE-MIB DEFINITIONS ::= BEGIN 1296 IMPORTS 1297 MODULE-IDENTITY, OBJECT-TYPE, Integer32, 1298 experimental, Gauge32, Unsigned32, 1299 Counter32, NOTIFICATION-TYPE 1300 FROM SNMPv2-SMI -- RFC1902 1301 RowStatus, StorageType, 1302 TruthValue, DateAndTime 1303 FROM SNMPv2-TC -- RFC1903 1304 MODULE-COMPLIANCE, OBJECT-GROUP, 1305 NOTIFICATION-GROUP 1306 FROM SNMPv2-CONF -- RFC1904 1307 SnmpAdminString 1308 FROM SNMP-FRAMEWORK-MIB -- RFC2271 1309 InterfaceIndexOrZero -- RFC2233 1310 FROM IF-MIB 1311 HostAddressType, HostAddress, 1312 IpHostAddress, OperationResponseStatus 1313 FROM DISMAN-PING-MIB; 1315 traceRouteMIB MODULE-IDENTITY 1316 LAST-UPDATED "9904270000Z" 1317 ORGANIZATION "IETF Distributed Management Working Group" 1318 CONTACT-INFO 1319 "Kenneth White 1321 International Business Machines Corporation 1322 Network Computing Software Division 1323 Research Triangle Park, NC, USA 1325 E-mail: wkenneth@us.ibm.com" 1326 DESCRIPTION 1327 "The Traceroute MIB (DISMAN-TRACEROUTE-MIB) provides 1328 access to the traceroute capability at a remote host." 1329 ::= { experimental 84 2 } 1331 -- Top level structure of the MIB 1333 traceRouteNotifications OBJECT IDENTIFIER ::= { traceRouteMIB 0 } 1334 traceRouteObjects OBJECT IDENTIFIER ::= { traceRouteMIB 1 } 1335 traceRouteConformance OBJECT IDENTIFIER ::= { traceRouteMIB 2 } 1337 -- Simple Object Definitions 1339 traceRouteMaxConcurrentRequests OBJECT-TYPE 1340 SYNTAX Integer32 (1..100) 1341 MAX-ACCESS read-write 1342 STATUS current 1343 DESCRIPTION 1344 "The maximum number of concurrent active traceroute requests 1345 that are allowed within an agent implementation." 1346 DEFVAL { 10 } 1347 ::= { traceRouteObjects 1 } 1349 -- Traceroute Control Table 1351 traceRouteCtlTable OBJECT-TYPE 1352 SYNTAX SEQUENCE OF TraceRouteCtlEntry 1353 MAX-ACCESS not-accessible 1354 STATUS current 1355 DESCRIPTION 1356 "Defines the Remote Operations Traceroute Control Table for 1357 providing the capability of invoking traceroute from a remote 1358 host. The results of traceroute operations are stored in 1359 the traceRouteResultsTable and traceRouteProbeHistoryTable." 1360 ::= { traceRouteObjects 2 } 1362 traceRouteCtlEntry OBJECT-TYPE 1363 SYNTAX TraceRouteCtlEntry 1364 MAX-ACCESS not-accessible 1365 STATUS current 1366 DESCRIPTION 1367 "Defines an entry in the traceRouteCtlTable." 1368 INDEX { 1369 traceRouteCtlOwnerIndex, 1370 traceRouteCtlTestName 1371 } 1372 ::= { traceRouteCtlTable 1 } 1374 TraceRouteCtlEntry ::= 1375 SEQUENCE { 1376 traceRouteCtlOwnerIndex SnmpAdminString, 1377 traceRouteCtlTestName SnmpAdminString, 1378 traceRouteCtlHostAddressType HostAddressType, 1379 traceRouteCtlHostAddress HostAddress, 1380 traceRouteCtlByPassRouteTable TruthValue, 1381 traceRouteCtlDataSize Integer32, 1382 traceRouteCtlTimeOut Integer32, 1383 traceRouteCtlProbesPerHop Integer32, 1384 traceRouteCtlPort Integer32, 1385 traceRouteCtlMaxTtl Integer32, 1386 traceRouteCtlTos Integer32, 1387 traceRouteCtlSourceAddress HostAddress, 1388 traceRouteCtlIfIndex InterfaceIndexOrZero, 1389 traceRouteCtlMiscOptions SnmpAdminString, 1390 traceRouteCtlMaxFailures Integer32, 1391 traceRouteCtlDontFragment TruthValue, 1392 traceRouteCtlInitialTtl Integer32, 1393 traceRouteCtlFrequency Integer32, 1394 traceRouteCtlStorageType StorageType, 1395 traceRouteCtlAdminStatus INTEGER, 1396 traceRouteCtlMaxRows Integer32, 1397 traceRouteCtlTrapGeneration INTEGER, 1398 traceRouteCtlRowStatus RowStatus 1399 } 1401 traceRouteCtlOwnerIndex OBJECT-TYPE 1402 SYNTAX SnmpAdminString (SIZE(0..32)) 1403 MAX-ACCESS not-accessible 1404 STATUS current 1405 DESCRIPTION 1406 "To facilitate the provisioning of access control by a security 1407 administrator using the View-Based Access Control Model (RFC 2275, 1408 VACM) for tables in which multiple users may need to independently 1409 create or modify entries, the initial index is used as an 'owner 1410 index'. Such an initial index has a syntax of SnmpAdminString, 1411 and can thus be trivially mapped to a securityName or groupName 1412 as defined in VACM, in accordance with a security policy. 1414 All entries in this table belonging to a particular user will 1415 have the same value for this initial index. For a given user's 1416 entries in a particular table, the object identifiers for the 1417 information in these entries will have the same subidentifiers 1418 (except for the 'column' subidentifier) up to the end of the 1419 encoded owner index. To configure VACM to permit access to this 1420 portion of the table, one would create vacmViewTreeFamilyTable 1421 entries with the value of vacmViewTreeFamilySubtree including the 1422 owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the 1423 column subidentifier. More elaborate configurations are 1424 possible." 1425 ::= { traceRouteCtlEntry 1 } 1427 traceRouteCtlTestName OBJECT-TYPE 1428 SYNTAX SnmpAdminString 1429 MAX-ACCESS not-accessible 1430 STATUS current 1431 DESCRIPTION 1432 "The name of a traceroute test. This is locally unique, within 1433 the scope of an traceRouteCtlOwnerIndex." 1434 ::= { traceRouteCtlEntry 2 } 1436 traceRouteCtlHostAddressType OBJECT-TYPE 1437 SYNTAX HostAddressType 1438 MAX-ACCESS read-create 1439 STATUS current 1440 DESCRIPTION 1441 "Specifies the type of host address to be used on the 1442 traceroute request at the remote host." 1443 DEFVAL { ipv4 } 1444 ::= { traceRouteCtlEntry 3 } 1446 traceRouteCtlHostAddress OBJECT-TYPE 1447 SYNTAX HostAddress 1448 MAX-ACCESS read-create 1449 STATUS current 1450 DESCRIPTION 1451 "Specifies the host address used on the 1452 traceroute request at the remote host. The 1453 host address type can be determined by the 1454 examining the value of the corresponding 1455 traceRouteCtlHostAddressType index element." 1456 ::= { traceRouteCtlEntry 4 } 1458 traceRouteCtlByPassRouteTable OBJECT-TYPE 1459 SYNTAX TruthValue 1460 MAX-ACCESS read-create 1461 STATUS current 1462 DESCRIPTION 1463 "The purpose of this object is optionally enable 1464 bypassing the route table. If enabled bypass the 1465 normal routing tables and send directly to a 1466 host on an attached network. If the host 1467 is not on a directly-attached network, an 1468 error is returned. This option can be 1469 used to ping a local host through an 1470 interface that has no route through it 1471 (e.g., after the interface was dropped by 1472 routed)." 1473 DEFVAL { false } 1474 ::= { traceRouteCtlEntry 5 } 1476 traceRouteCtlDataSize OBJECT-TYPE 1477 SYNTAX Integer32 (0..65507) 1478 UNITS "octets" 1479 MAX-ACCESS read-create 1480 STATUS current 1481 DESCRIPTION 1482 "Specifies the size of the data portion of a traceroute 1483 request in octets. A traceroute request is essentially 1484 transmitted by encoding a UDP datagram into a 1485 IP packet. So subtracting the size of a UDP header 1486 (8 octets) and the size of a IP header (20 octets) 1487 yields a maximum of 65507 octets." 1488 DEFVAL { 0 } 1489 ::= { traceRouteCtlEntry 6 } 1491 traceRouteCtlTimeOut OBJECT-TYPE 1492 SYNTAX Integer32 (1..60) 1493 UNITS "seconds" 1494 MAX-ACCESS read-create 1495 STATUS current 1496 DESCRIPTION 1497 "Specifies the time-out value, in seconds, for 1498 a traceroute request." 1499 DEFVAL { 3 } 1500 ::= { traceRouteCtlEntry 7 } 1502 traceRouteCtlProbesPerHop OBJECT-TYPE 1503 SYNTAX Integer32 (1..10) 1504 UNITS "probes" 1505 MAX-ACCESS read-create 1506 STATUS current 1507 DESCRIPTION 1508 "Specifies the number of times to reissue a traceroute 1509 request with the same time-to-live (TTL) value." 1510 DEFVAL { 3 } 1511 ::= { traceRouteCtlEntry 8 } 1513 traceRouteCtlPort OBJECT-TYPE 1514 SYNTAX Integer32 (1..65535) 1515 UNITS "UDP Port" 1516 MAX-ACCESS read-create 1517 STATUS current 1518 DESCRIPTION 1519 "Specifies the UDP port to sent the traceroute 1520 request to. Need to specify a port that is not in 1521 use at the destination host." 1522 DEFVAL { 4096 } 1523 ::= { traceRouteCtlEntry 9 } 1525 traceRouteCtlMaxTtl OBJECT-TYPE 1526 SYNTAX Integer32 (1..255) 1527 UNITS "time-to-live value" 1528 MAX-ACCESS read-create 1529 STATUS current 1530 DESCRIPTION 1531 "Specifies the maximum time-to-live value." 1532 DEFVAL { 30 } 1533 ::= { traceRouteCtlEntry 10 } 1535 traceRouteCtlTos OBJECT-TYPE 1536 SYNTAX Integer32 (0..255) 1537 MAX-ACCESS read-create 1538 STATUS current 1539 DESCRIPTION 1540 "Specifies the value to store in the TOS OCTET in 1541 the IP probe packet that is transmitted as the 1542 traceroute request. The value must be a decimal 1543 integer in the range 0 to 255. This option can be 1544 used to see if different types-of-service result 1545 in different paths. Not all values of TOS are 1546 legal or meaningful. TOS is often not supported 1547 by IP implementations. Useful values are probably 1548 '16' (low delay) and '8' (high throughput)." 1549 REFERENCE 1550 "RFC 1812 Section 5.3.2, Type of Service (TOS)" 1551 DEFVAL { 0 } 1552 ::= { traceRouteCtlEntry 11 } 1554 traceRouteCtlSourceAddress OBJECT-TYPE 1555 SYNTAX HostAddress 1556 MAX-ACCESS read-create 1557 STATUS current 1558 DESCRIPTION 1559 "Use the specified IP address 1560 (which must be given as an IP number, not a hostname) 1561 as the source address in outgoing probe packets. On 1562 hosts with more than one IP address, this option can 1563 be used to force the source address to be something 1564 other than the IP address of the interface the probe 1565 packet is sent on. If the IP address is not one of this 1566 machine's interface addresses, an error is returned and 1567 nothing is sent." 1568 DEFVAL { ''H } 1569 ::= { traceRouteCtlEntry 12 } 1571 traceRouteCtlIfIndex OBJECT-TYPE 1572 SYNTAX InterfaceIndexOrZero 1573 MAX-ACCESS read-create 1574 STATUS current 1575 DESCRIPTION 1576 "Setting this object to an interface's ifIndex prior 1577 to starting a remote traceroute operation directs 1578 the traceroute probes to be transmitted over the 1579 specified interface. A value of zero for this object 1580 implies that this option is not enabled." 1581 DEFVAL { 0 } 1582 ::= { traceRouteCtlEntry 13 } 1584 traceRouteCtlMiscOptions OBJECT-TYPE 1585 SYNTAX SnmpAdminString (SIZE(0..64)) 1586 MAX-ACCESS read-create 1587 STATUS current 1588 DESCRIPTION 1589 "Enables an application to specify implementation 1590 dependent options." 1591 DEFVAL { ''H } 1592 ::= { traceRouteCtlEntry 14 } 1594 traceRouteCtlMaxFailures OBJECT-TYPE 1595 SYNTAX Integer32 (0..255) 1596 MAX-ACCESS read-create 1597 STATUS current 1598 DESCRIPTION 1599 "The value of this object indicates the maximum number 1600 of consecutive timeouts allowed before terminating 1601 a remote traceroute request. A value of either 255 (maximum 1602 hop count/possible TTL value) or a 0 indicates that the 1603 function of terminating a remote traceroute request when a 1604 specific number of successive timeouts are detected is 1605 disabled." 1606 DEFVAL { 5 } 1607 ::= { traceRouteCtlEntry 15 } 1609 traceRouteCtlDontFragment OBJECT-TYPE 1610 SYNTAX TruthValue 1611 MAX-ACCESS read-create 1612 STATUS current 1613 DESCRIPTION 1614 "This object enables setting of the don't fragment flag (DF) 1615 in the IP header for a probe. Use of this object enables 1616 performing a manual PATH MTU test." 1617 DEFVAL { false } 1618 ::= { traceRouteCtlEntry 16 } 1620 traceRouteCtlInitialTtl OBJECT-TYPE 1621 SYNTAX Integer32 (0..255) 1622 MAX-ACCESS read-create 1623 STATUS current 1624 DESCRIPTION 1625 "The value of this object specifies the initial TTL value to 1626 use. This enables bypassing the initial (often well known) 1627 portion of a path." 1628 DEFVAL { 1 } 1629 ::= { traceRouteCtlEntry 17 } 1631 traceRouteCtlFrequency OBJECT-TYPE 1632 SYNTAX Integer32 1633 UNITS "seconds" 1634 MAX-ACCESS read-create 1635 STATUS current 1636 DESCRIPTION 1637 "The number of seconds to wait before repeating a 1638 traceRoute test as defined by the value of the 1639 various objects in the corresponding row." 1640 DEFVAL { 0 } 1641 ::= { traceRouteCtlEntry 18 } 1643 traceRouteCtlStorageType OBJECT-TYPE 1644 SYNTAX StorageType 1645 MAX-ACCESS read-create 1646 STATUS current 1647 DESCRIPTION 1648 "The storage type for this conceptual row. 1649 Conceptual rows having the value 'permanent' need not 1650 allow write-access to any columnar objects in the row." 1651 DEFVAL { nonVolatile } 1652 ::= { traceRouteCtlEntry 19 } 1654 traceRouteCtlAdminStatus OBJECT-TYPE 1655 SYNTAX INTEGER { 1656 up(1), -- operation should be started 1657 down(2) -- operation should be stop 1658 } 1659 MAX-ACCESS read-create 1660 STATUS current 1661 DESCRIPTION 1662 "Reflects the desired state that an traceRouteCtlEntry 1663 should be in: 1665 up(1) - Attempt to active the test as defined by 1666 this traceRouteCtlEntry. 1667 down(1) - Deactive the test as defined by this 1668 traceRouteCtlEntry. 1670 Refer to the corresponding traceRouteResultsOperStatus to 1671 determine the operational state of the test defined by 1672 this entry." 1673 DEFVAL { down } 1674 ::= { traceRouteCtlEntry 20 } 1676 traceRouteCtlMaxRows OBJECT-TYPE 1677 SYNTAX Integer32 (0..1500) 1678 MAX-ACCESS read-create 1679 STATUS current 1680 DESCRIPTION 1681 "The maximum number of entries allowed in the 1682 traceRouteProbeHistoryTable. An implementation of 1683 this MIB will remove the oldest entry in the 1684 traceRouteProbeHistoryTable to allow the addition 1685 of an new entry once the number of rows in the 1686 traceRouteProbeHistoryTable reaches this value. 1687 Entries will be removed on the basis of oldest 1688 traceRouteProbeHistoryTime value first. 1690 A value of 0 for this object disables creation of 1691 traceRouteProbeHistoryTable entries." 1692 DEFVAL { 50 } 1693 ::= { traceRouteCtlEntry 21 } 1695 traceRouteCtlTrapGeneration OBJECT-TYPE 1696 SYNTAX INTEGER { 1697 none(1), 1698 pathChange(2), 1699 testFailure(3), 1700 testCompletion(4) 1701 } 1702 MAX-ACCESS read-create 1703 STATUS current 1704 DESCRIPTION 1705 "The value of this object determines when and if to 1706 to generation a notification for this entry: 1708 none(1) - Don't generation any notifications. 1709 pathChange(2) - Generate a traceRoutePathChange 1710 notification when the current path varies from a 1711 previously determined path. 1712 testFailure(3) - Generate a traceRouteTestFailed 1713 notification when the full path to a target 1714 can't be determined. 1715 testCompletion(4) - Generate a traceRouteTestCompleted 1716 notification when the path to a target has been 1717 determined." 1718 DEFVAL { none } 1719 ::= { traceRouteCtlEntry 22 } 1721 traceRouteCtlRowStatus OBJECT-TYPE 1722 SYNTAX RowStatus 1723 MAX-ACCESS read-create 1724 STATUS current 1725 DESCRIPTION 1726 "This object allows entries to be created and deleted 1727 in the traceRouteCtlTable. Deletion of an entry in 1728 this table results in all corresponding (same 1729 traceRouteCtlOwnerIndex and traceRouteCtlTestName 1730 index values) traceRouteResultsTable and 1731 traceRouteProbeHistoryTable entries being deleted. 1733 Activation of a remote traceroute operation is 1734 controled via traceRouteCtlAdminStatus and not 1735 by transitioning of this object's value to active(1). 1737 Transitions in and out of active(1) state are not 1738 allowed while an entry's traceRouteResultsOperStatus 1739 is active(1) with the exception that deletion of 1740 an entry in this table by setting its RowStatus 1741 object to destroy(6) will stop an active 1742 ping operation. 1744 The operational state of an traceroute operation 1745 can be determined by examination of it's 1746 traceRouteResultsOperStatus object." 1747 REFERENCE 1748 "RFC 2579, 'Textual Conventions for SMIv2.'" 1749 ::= { traceRouteCtlEntry 23 } 1751 -- Traceroute Results Table 1753 traceRouteResultsTable OBJECT-TYPE 1754 SYNTAX SEQUENCE OF TraceRouteResultsEntry 1755 MAX-ACCESS not-accessible 1756 STATUS current 1757 DESCRIPTION 1758 "Defines the Remote Operations Traceroute Results Table for 1759 keeping track of the status of an traceRouteCtlEntry." 1760 ::= { traceRouteObjects 3 } 1762 traceRouteResultsEntry OBJECT-TYPE 1763 SYNTAX TraceRouteResultsEntry 1764 MAX-ACCESS not-accessible 1765 STATUS current 1766 DESCRIPTION 1767 "Defines an entry in the traceRouteResultsTable." 1768 INDEX { 1769 traceRouteCtlOwnerIndex, 1770 traceRouteCtlTestName 1771 } 1772 ::= { traceRouteResultsTable 1 } 1774 TraceRouteResultsEntry ::= 1775 SEQUENCE { 1776 traceRouteResultsOperStatus INTEGER, 1777 traceRouteResultsCurHopCount Gauge32, 1778 traceRouteResultsCurProbeCount Gauge32, 1779 traceRouteResultsIpHostAddress IpHostAddress, 1780 traceRouteResultsTestAttempts Counter32, 1781 traceRouteResultsTestSuccesses Counter32, 1782 traceRouteResultsLastGoodPath DateAndTime 1783 } 1785 traceRouteResultsOperStatus OBJECT-TYPE 1786 SYNTAX INTEGER { 1787 up(1), -- test is in progress 1788 down(2) -- test has stopped 1789 } 1790 MAX-ACCESS read-only 1791 STATUS current 1792 DESCRIPTION 1793 "Reflects the operational state of an traceRouteCtlEntry: 1795 up(1) - Test is active. 1796 down(1) - Test has stopped." 1797 ::= { traceRouteResultsEntry 1 } 1799 traceRouteResultsCurHopCount OBJECT-TYPE 1800 SYNTAX Gauge32 1801 MAX-ACCESS read-only 1802 STATUS current 1803 DESCRIPTION 1804 "Reflects the current TTL value (range from 1 to 1805 255) for an remote traceroute operation. 1806 Maximum TTL value is determined by 1807 traceRouteCtlMaxTtl." 1808 ::= { traceRouteResultsEntry 2 } 1810 traceRouteResultsCurProbeCount OBJECT-TYPE 1811 SYNTAX Gauge32 1812 MAX-ACCESS read-only 1813 STATUS current 1814 DESCRIPTION 1815 "Reflects the current probe count (1..10) for 1816 an remote traceroute operation. The maximum 1817 probe count is determined by 1818 traceRouteCtlProbesPerHop." 1819 ::= { traceRouteResultsEntry 3 } 1821 traceRouteResultsIpHostAddress OBJECT-TYPE 1822 SYNTAX IpHostAddress 1823 MAX-ACCESS read-only 1824 STATUS current 1825 DESCRIPTION 1826 "This objects reports the IP address associated 1827 with a traceRouteCtlHostAddress value when the destination 1828 address is specified as a DNS name. The value of 1829 this object should be a zero length octet string 1830 when a DNS name is not specified or when a 1831 specified DNS name fails to resolve." 1832 ::= { traceRouteResultsEntry 4 } 1834 traceRouteResultsTestAttempts OBJECT-TYPE 1835 SYNTAX Counter32 1836 MAX-ACCESS read-only 1837 STATUS current 1838 DESCRIPTION 1839 "The current number of attempts to determine a path 1840 to a target." 1841 ::= { traceRouteResultsEntry 5 } 1843 traceRouteResultsTestSuccesses OBJECT-TYPE 1844 SYNTAX Counter32 1845 MAX-ACCESS read-only 1846 STATUS current 1847 DESCRIPTION 1848 "The current number of attempts to determine a path 1849 to a target that have succeeded." 1850 ::= { traceRouteResultsEntry 6 } 1852 traceRouteResultsLastGoodPath OBJECT-TYPE 1853 SYNTAX DateAndTime 1854 MAX-ACCESS read-only 1855 STATUS current 1856 DESCRIPTION 1857 "The date and time when the last path was determined." 1858 ::= { traceRouteResultsEntry 7 } 1860 -- Trace Route Probe History Table 1862 traceRouteProbeHistoryTable OBJECT-TYPE 1863 SYNTAX SEQUENCE OF TraceRouteProbeHistoryEntry 1864 MAX-ACCESS not-accessible 1865 STATUS current 1866 DESCRIPTION 1867 "Defines the Remote Operations Traceroute Results Table for 1868 storing the results of a traceroute operation." 1869 ::= { traceRouteObjects 4 } 1871 traceRouteProbeHistoryEntry OBJECT-TYPE 1872 SYNTAX TraceRouteProbeHistoryEntry 1873 MAX-ACCESS not-accessible 1874 STATUS current 1875 DESCRIPTION 1876 "Defines a table for storing the results of a traceroute 1877 operation. Entries in this table is limited by 1878 the value of the corresponding traceRouteCtlMaxRows 1879 object. 1881 An implementation of this MIB will remove the oldest 1882 entry in the traceRouteProbeHistoryTable to allow the 1883 addition of an new entry once the number of rows in 1884 the traceRouteProbeHistoryTable reaches the value specified 1885 by traceRouteCtlMaxRows. Entries will be removed on the 1886 basis of oldest traceRouteProbeHistoryTime value first." 1887 INDEX { 1888 traceRouteCtlOwnerIndex, 1889 traceRouteCtlTestName, 1890 traceRouteProbeHistoryIndex, 1891 traceRouteProbeHistoryHopIndex, 1892 traceRouteProbeHistoryProbeIndex 1893 } 1894 ::= { traceRouteProbeHistoryTable 1 } 1896 TraceRouteProbeHistoryEntry ::= 1897 SEQUENCE { 1898 traceRouteProbeHistoryIndex Unsigned32, 1899 traceRouteProbeHistoryHopIndex Integer32, 1900 traceRouteProbeHistoryProbeIndex Integer32, 1901 traceRouteProbeHistoryHopAddress HostAddress, 1902 traceRouteProbeHistoryResponse Integer32, 1903 traceRouteProbeHistoryStatus OperationResponseStatus, 1904 traceRouteProbeHistoryLastReplyCode Integer32, 1905 traceRouteProbeHistoryTime DateAndTime 1906 } 1908 traceRouteProbeHistoryIndex OBJECT-TYPE 1909 SYNTAX Unsigned32 (1..'ffffffff'h) 1910 MAX-ACCESS not-accessible 1911 STATUS current 1912 DESCRIPTION 1913 "An entry in this table is created when the results of 1914 a traceroute probe is determined. The initial 2 instance 1915 identifier index values identifies the traceRouteCtlEntry 1916 that a probe result (traceRouteProbeHistoryEntry) belongs 1917 to." 1918 ::= { traceRouteProbeHistoryEntry 1 } 1920 traceRouteProbeHistoryHopIndex OBJECT-TYPE 1921 SYNTAX Integer32 (1..255) 1922 MAX-ACCESS not-accessible 1923 STATUS current 1924 DESCRIPTION 1925 "Indicates which hop in a traceroute path that the probe's 1926 results is for." 1927 ::= { traceRouteProbeHistoryEntry 2 } 1929 traceRouteProbeHistoryProbeIndex OBJECT-TYPE 1930 SYNTAX Integer32 (1..10) 1931 MAX-ACCESS not-accessible 1932 STATUS current 1933 DESCRIPTION 1934 "Indicates the index of a probe for determining for a 1935 hop in a traceroute path. The value of this object is 1936 initially determined by the value of traceRouteCtlInitialTtl." 1937 ::= { traceRouteProbeHistoryEntry 3 } 1939 traceRouteProbeHistoryHopAddress OBJECT-TYPE 1940 SYNTAX HostAddress 1941 MAX-ACCESS read-only 1942 STATUS current 1943 DESCRIPTION 1944 "The address of a hop in a traceroute path. This object 1945 is not allowed to be a DNS name. The length of the 1946 octet string returned determines the address type." 1947 ::= { traceRouteProbeHistoryEntry 4 } 1949 traceRouteProbeHistoryResponse OBJECT-TYPE 1950 SYNTAX Integer32 1951 MAX-ACCESS read-only 1952 STATUS current 1953 DESCRIPTION 1954 "The amount of time measured in milliseconds from when 1955 a probe was sent to when its response was received or 1956 when it timed out. The value of this object is reported 1957 as 0 when it is not possible to transmit a probe." 1958 ::= { traceRouteProbeHistoryEntry 5 } 1960 traceRouteProbeHistoryStatus OBJECT-TYPE 1961 SYNTAX OperationResponseStatus 1962 MAX-ACCESS read-only 1963 STATUS current 1964 DESCRIPTION 1965 "The result of a traceroute operation made by a remote 1966 host for a particular probe." 1967 ::= { traceRouteProbeHistoryEntry 6 } 1969 traceRouteProbeHistoryLastReplyCode OBJECT-TYPE 1970 SYNTAX Integer32 1971 MAX-ACCESS read-only 1972 STATUS current 1973 DESCRIPTION 1974 "The last implementation method specific reply code received. 1976 Traceroute is usually implemented by transmitting a series of 1977 probe packets with increasing time-to-live values. A probe 1978 packet is a UDP datagram encapsulated into an IP packet. 1979 Each hop in a path to the target (destination) host rejects 1980 the probe packets (probe's TTL too small, ICMP reply) until 1981 either the maximum TTL is exceeded or the target host is 1982 received." 1983 ::= { traceRouteProbeHistoryEntry 7 } 1985 traceRouteProbeHistoryTime OBJECT-TYPE 1986 SYNTAX DateAndTime 1987 MAX-ACCESS read-only 1988 STATUS current 1989 DESCRIPTION 1990 "Timestamp for when this probe results was determined." 1991 ::= { traceRouteProbeHistoryEntry 8 } 1993 -- Notification Definition section 1995 traceRoutePathChange NOTIFICATION-TYPE 1996 OBJECTS { 1997 traceRouteCtlHostAddressType, 1998 traceRouteCtlHostAddress, 1999 traceRouteResultsIpHostAddress 2000 } 2001 STATUS current 2002 DESCRIPTION 2003 "The path to a target has changed." 2004 ::= { traceRouteNotifications 1 } 2006 traceRouteTestFailed NOTIFICATION-TYPE 2007 OBJECTS { 2008 traceRouteCtlHostAddressType, 2009 traceRouteCtlHostAddress, 2010 traceRouteResultsIpHostAddress 2011 } 2012 STATUS current 2013 DESCRIPTION 2014 "Could not determine the path to a target." 2015 ::= { traceRouteNotifications 2 } 2017 traceRouteTestCompleted NOTIFICATION-TYPE 2018 OBJECTS { 2019 traceRouteCtlHostAddressType, 2020 traceRouteCtlHostAddress, 2021 traceRouteResultsIpHostAddress 2022 } 2023 STATUS current 2024 DESCRIPTION 2025 "The path to a target has just been determined." 2026 ::= { traceRouteNotifications 3 } 2028 -- Conformance information 2029 -- Compliance statements 2031 traceRouteCompliances OBJECT IDENTIFIER ::= { traceRouteConformance 1 } 2032 traceRouteGroups OBJECT IDENTIFIER ::= { traceRouteConformance 2 } 2033 -- Compliance statements 2035 traceRouteCompliance MODULE-COMPLIANCE 2036 STATUS current 2037 DESCRIPTION 2038 "The compliance statement for the DISMAN-TRACEROUTE-MIB." 2039 MODULE -- this module 2040 MANDATORY-GROUPS { 2041 traceRouteGroup, 2042 traceRouteNotificationsGroup 2043 } 2044 GROUP traceRouteTimeStampGroup 2045 DESCRIPTION 2046 "This group is mandatory for implementations that have 2047 access to a system clock and are capable of setting 2048 the values for DateAndTime objects." 2050 OBJECT traceRouteMaxConcurrentRequests 2051 MIN-ACCESS read-only 2052 DESCRIPTION 2053 "The agent is not required to support a SET 2054 operation to this object." 2056 OBJECT traceRouteCtlByPassRouteTable 2057 MIN-ACCESS read-only 2058 DESCRIPTION 2059 "This object is not required by implementations that are not 2060 capable of its implementation. The function represented by 2061 this object is implementable if the setsockopt SOL_SOCKET 2062 SO_DONTROUTE option is supported." 2064 OBJECT traceRouteCtlSourceAddress 2065 MIN-ACCESS read-only 2066 DESCRIPTION 2067 "This object is not required by implementations that are not 2068 capable of binding the send socket (udp) with a source 2069 address." 2070 ::= { traceRouteCompliances 1 } 2072 -- MIB groupings 2074 traceRouteGroup OBJECT-GROUP 2075 OBJECTS { 2076 traceRouteMaxConcurrentRequests, 2077 traceRouteCtlHostAddressType, 2078 traceRouteCtlHostAddress, 2079 traceRouteCtlByPassRouteTable, 2080 traceRouteCtlDataSize, 2081 traceRouteCtlTimeOut, 2082 traceRouteCtlProbesPerHop, 2083 traceRouteCtlPort, 2084 traceRouteCtlMaxTtl, 2085 traceRouteCtlTos, 2086 traceRouteCtlSourceAddress, 2087 traceRouteCtlIfIndex, 2088 traceRouteCtlMiscOptions, 2089 traceRouteCtlMaxFailures, 2090 traceRouteCtlDontFragment, 2091 traceRouteCtlInitialTtl, 2092 traceRouteCtlFrequency, 2093 traceRouteCtlStorageType, 2094 traceRouteCtlAdminStatus, 2095 traceRouteCtlMaxRows, 2096 traceRouteCtlTrapGeneration, 2097 traceRouteCtlRowStatus, 2098 traceRouteResultsOperStatus, 2099 traceRouteResultsCurHopCount, 2100 traceRouteResultsCurProbeCount, 2101 traceRouteResultsIpHostAddress, 2102 traceRouteResultsTestAttempts, 2103 traceRouteResultsTestSuccesses, 2104 traceRouteProbeHistoryHopAddress, 2105 traceRouteProbeHistoryResponse, 2106 traceRouteProbeHistoryStatus, 2107 traceRouteProbeHistoryLastReplyCode 2108 } 2109 STATUS current 2110 DESCRIPTION 2111 "The group of objects that comprise the remote traceroute 2112 operation." 2113 ::= { traceRouteGroups 1 } 2115 traceRouteTimeStampGroup OBJECT-GROUP 2116 OBJECTS { 2117 traceRouteResultsLastGoodPath, 2118 traceRouteProbeHistoryTime 2119 } 2120 STATUS current 2121 DESCRIPTION 2122 "The group of DateAndTime objects." 2123 ::= { traceRouteGroups 2 } 2125 traceRouteNotificationsGroup NOTIFICATION-GROUP 2126 NOTIFICATIONS { 2127 traceRoutePathChange, 2128 traceRouteTestFailed, 2129 traceRouteTestCompleted 2130 } 2131 STATUS current 2132 DESCRIPTION 2133 "The notification which are required to be supported by 2134 implemenations of this MIB." 2135 ::= { traceRouteGroups 3 } 2137 END 2139 4.3 DISMAN-LOOKUP-MIB 2141 DISMAN-LOOKUP-MIB DEFINITIONS ::= BEGIN 2143 IMPORTS 2144 MODULE-IDENTITY, OBJECT-TYPE, Integer32, 2145 experimental, Unsigned32 2146 FROM SNMPv2-SMI -- RFC1902 2147 RowStatus 2148 FROM SNMPv2-TC -- RFC1903 2149 MODULE-COMPLIANCE, OBJECT-GROUP 2150 FROM SNMPv2-CONF -- RFC1904 2151 SnmpAdminString 2152 FROM SNMP-FRAMEWORK-MIB -- RFC2271 2153 HostAddressType, HostAddress 2154 FROM DISMAN-PING-MIB; 2156 lookupMIB MODULE-IDENTITY 2157 LAST-UPDATED "9904230000Z" 2158 ORGANIZATION "IETF Distributed Management Working Group" 2159 CONTACT-INFO 2160 "Kenneth White 2162 International Business Machines Corporation 2163 Network Computing Software Division 2164 Research Triangle Park, NC, USA 2166 E-mail: wkenneth@us.ibm.com" 2167 DESCRIPTION 2168 "The Lookup MIB (DISMAN-LOOKUP-MIB) enables determination 2169 of either the name corresponding to a host address or of 2170 the address associated with a host name at a remote host." 2171 ::= { experimental 84 3 } 2173 -- Top level structure of the MIB 2175 lookupObjects OBJECT IDENTIFIER ::= { lookupMIB 1 } 2176 lookupConformance OBJECT IDENTIFIER ::= { lookupMIB 2 } 2178 -- Simple Object Definitions 2180 lookupMaxConcurrentRequests OBJECT-TYPE 2181 SYNTAX Integer32 (1..100) 2182 MAX-ACCESS read-write 2183 STATUS current 2184 DESCRIPTION 2185 "The maximum number of concurrent active lookup requests 2186 that are allowed within an agent implementation." 2187 DEFVAL { 10 } 2188 ::= { lookupObjects 1 } 2190 lookupPurgeTime OBJECT-TYPE 2191 SYNTAX Integer32 (0..86400) 2192 UNITS "seconds" 2193 MAX-ACCESS read-write 2194 STATUS current 2195 DESCRIPTION 2196 "The amount of time to wait before automatically 2197 deleting an entry in the lookupTable 2198 after the lookup operation represented by an 2199 lookupEntry has completed." 2200 DEFVAL { 900 } -- 15 minutes as default 2201 ::= { lookupObjects 2 } 2203 -- Lookup Table 2205 lookupTable OBJECT-TYPE 2206 SYNTAX SEQUENCE OF LookupEntry 2207 MAX-ACCESS not-accessible 2208 STATUS current 2209 DESCRIPTION 2210 "Defines the Lookup Table for provide 2211 the capability of performing a lookup operation, 2212 gethostbyname or gethostbyaddr, from a remote host." 2213 ::= { lookupObjects 3 } 2215 lookupEntry OBJECT-TYPE 2216 SYNTAX LookupEntry 2217 MAX-ACCESS not-accessible 2218 STATUS current 2219 DESCRIPTION 2220 "Defines an entry in the lookupTable." 2221 INDEX { 2222 lookupOwnerIndex, 2223 lookupOperationName, 2224 lookupAddressType, 2225 lookupAddress 2226 } 2227 ::= { lookupTable 1 } 2229 LookupEntry ::= 2230 SEQUENCE { 2231 lookupOwnerIndex SnmpAdminString, 2232 lookupOperationName SnmpAdminString, 2233 lookupAddressType HostAddressType, 2234 lookupAddress HostAddress, 2235 lookupOperStatus INTEGER, 2236 lookupResultType HostAddressType, 2237 lookupResult HostAddress, 2238 lookupTime Unsigned32, 2239 lookupRc Unsigned32, 2240 lookupRowStatus RowStatus 2241 } 2243 lookupOwnerIndex OBJECT-TYPE 2244 SYNTAX SnmpAdminString (SIZE(0..32)) 2245 MAX-ACCESS not-accessible 2246 STATUS current 2247 DESCRIPTION 2248 "To facilitate the provisioning of access control by a security 2249 administrator using the View-Based Access Control Model (RFC 2275, 2250 VACM) for tables in which multiple users may need to independently 2251 create or modify entries, the initial index is used as an 'owner 2252 index'. Such an initial index has a syntax of SnmpAdminString, 2253 and can thus be trivially mapped to a securityName or groupName 2254 as defined in VACM, in accordance with a security policy. 2256 All entries in that table belonging to a particular user will 2257 have the same value for this initial index. For a given user's 2258 entries in a particular table, the object identifiers for the 2259 information in these entries will have the same subidentifiers 2260 (except for the 'column' subidentifier) up to the end of the 2261 encoded owner index. To configure VACM to permit access to this 2262 portion of the table, one would create vacmViewTreeFamilyTable 2263 entries with the value of vacmViewTreeFamilySubtree including the 2264 owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the 2265 column subidentifier. More elaborate configurations are 2266 possible." 2267 ::= { lookupEntry 1 } 2269 lookupOperationName OBJECT-TYPE 2270 SYNTAX SnmpAdminString 2271 MAX-ACCESS not-accessible 2272 STATUS current 2273 DESCRIPTION 2274 "The name of a lookup operation. This is locally unique, within 2275 the scope of an lookupOwnerIndex." 2276 ::= { lookupEntry 2 } 2278 lookupAddressType OBJECT-TYPE 2279 SYNTAX HostAddressType 2280 MAX-ACCESS not-accessible 2281 STATUS current 2282 DESCRIPTION 2283 "Specifies the type of address for either performing a 2284 gethostbyname or a gethostbyaddr call at a remote host. 2285 Specification of a dnsName(2) implies that gethostbyname 2286 should be called to return a numeric address. 2287 Use of a value of either ipv4(3) or ipv6(4) implies that 2288 a gethostbyaddr call should occur to return the symbolic 2289 name of a remote host." 2290 ::= { lookupEntry 3 } 2292 lookupAddress OBJECT-TYPE 2293 SYNTAX HostAddress 2294 MAX-ACCESS not-accessible 2295 STATUS current 2296 DESCRIPTION 2297 "Specifies the address used for a DNS Lookup at a 2298 remote host. The corresponding lookupAddressType 2299 objects determines its type as well as the function 2300 that can be requested." 2301 ::= { lookupEntry 4 } 2303 lookupOperStatus OBJECT-TYPE 2304 SYNTAX INTEGER { 2305 up(1), -- operation is in progress 2306 down(2) -- operation has stopped 2307 } 2308 MAX-ACCESS read-only 2309 STATUS current 2310 DESCRIPTION 2311 "Reflects the operational state of an lookupEntry: 2313 up(1) - Operation is active. 2314 down(1) - Operation has stopped." 2315 ::= { lookupEntry 5 } 2317 lookupResultType OBJECT-TYPE 2318 SYNTAX HostAddressType 2319 MAX-ACCESS read-only 2320 STATUS current 2321 DESCRIPTION 2322 "Indicates the type of result of a remote lookup 2323 operation. A value of none(1) implies that 2324 either the operation hasn't been started or that 2325 it has failed." 2326 ::= { lookupEntry 6 } 2328 lookupResult OBJECT-TYPE 2329 SYNTAX HostAddress 2330 MAX-ACCESS read-only 2331 STATUS current 2332 DESCRIPTION 2333 "Reflects the results of a remote lookup operation 2334 as per the value of lookupResultType." 2335 ::= { lookupEntry 7 } 2337 lookupTime OBJECT-TYPE 2338 SYNTAX Unsigned32 2339 UNITS "seconds" 2340 MAX-ACCESS read-only 2341 STATUS current 2342 DESCRIPTION 2343 "Reports the number of seconds that a lookup 2344 operation required to be completed at a remote host. 2345 Completed means operation failure as well as 2346 success." 2347 ::= { lookupEntry 8 } 2349 lookupRc OBJECT-TYPE 2350 SYNTAX Unsigned32 2351 MAX-ACCESS read-only 2352 STATUS current 2353 DESCRIPTION 2354 "The system specific return code from a lookup 2355 operation. All implementations must return a value 2356 of 0 for this object when the remote lookup 2357 operation succeeds. A non-zero value for this 2358 objects indicates failure. It is recommended that 2359 implementations that support errno use it as the 2360 value of this object to aid a management 2361 application in determining the cause of failure." 2362 ::= { lookupEntry 9 } 2364 lookupRowStatus OBJECT-TYPE 2365 SYNTAX RowStatus 2366 MAX-ACCESS read-create 2367 STATUS current 2368 DESCRIPTION 2369 "This object allows entries to be created and deleted 2370 in the lookupTable. 2372 A remote DNS Lookup operation is started when an 2373 entry in this table is created via an SNMP SET 2374 request and the entry is activated. This 2375 can occur by setting the value of this object 2376 to CreateAndGo(4) during row creation or 2377 by setting this object to active(1) after 2378 the row is created. 2380 A remote lookup operation starts when its entry 2381 first becomes active(1). Transitions in and 2382 out of active(1) state have no effect on the 2383 operational behavior of a remote lookup 2384 operation, with the exception that deletion of 2385 an entry in this table by setting its RowStatus 2386 object to destroy(6) will stop an active 2387 remote DNS Lookup operation. 2389 The operational state of a remote lookup operation 2390 can be determined by examination of it's 2391 lookupOperStatus object." 2392 REFERENCE 2393 "RFC 2579, 'Textual Conventions for SMIv2.'" 2394 ::= { lookupEntry 10 } 2396 -- Conformance information 2397 -- Compliance statements 2399 lookupCompliances OBJECT IDENTIFIER ::= { lookupConformance 1 } 2400 lookupGroups OBJECT IDENTIFIER ::= { lookupConformance 2 } 2402 -- Compliance statements 2403 lookupCompliance MODULE-COMPLIANCE 2404 STATUS current 2405 DESCRIPTION 2406 "The compliance statement for the DISMAN-LOOKUP-MIB." 2407 MODULE -- this module 2408 MANDATORY-GROUPS { 2409 lookupGroup 2410 } 2412 OBJECT lookupMaxConcurrentRequests 2413 MIN-ACCESS read-only 2414 DESCRIPTION 2415 "The agent is not required to support a SET 2416 operation to this object." 2418 OBJECT lookupPurgeTime 2419 MIN-ACCESS read-only 2420 DESCRIPTION 2421 "The agent is not required to support a SET 2422 operation to this object." 2423 ::= { lookupCompliances 1 } 2425 -- MIB groupings 2427 lookupGroup OBJECT-GROUP 2428 OBJECTS { 2429 lookupMaxConcurrentRequests, 2430 lookupPurgeTime, 2431 lookupOperStatus, 2432 lookupResultType, 2433 lookupResult, 2434 lookupTime, 2435 lookupRc, 2436 lookupRowStatus 2437 } 2438 STATUS current 2439 DESCRIPTION 2440 "The group of objects that comprise the remote 2441 Lookup operation." 2442 ::= { lookupGroups 1 } 2444 END 2446 5.0 Security Considerations 2448 Certain management information in the MIBs defined by this document may 2449 be considered sensitive in some network environments. Therefore, 2450 authentication of received SNMP requests and controlled access to 2451 management information SHOULD be employed in such environments. The 2452 method for this authentication is a function of the SNMP Administrative 2453 Framework, and has not been expanded by this MIB. 2455 It is RECOMMENDED that the MIBs defined within this memo not be 2456 supported in insecure environments. 2458 6.0 Intellectual Property 2460 The IETF takes no position regarding the validity or scope of any 2461 intellectual property or other rights that might be claimed to pertain 2462 to the implementation or use of the technology described in this 2463 document or the extent to which any license under such rights might or 2464 might not be available; neither does it represent that it has made any 2465 effort to identify any such rights. Information on the IETF's 2466 procedures with respect to rights in standards-track and 2467 standards-related documentation can be found in BCP-11. Copies of 2468 claims of rights made available for publication and any assurances of 2469 licenses to be made available, or the result of an attempt made to 2470 obtain a general license or permission for the use of such proprietary 2471 rights by implementers or users of this specification can be obtained 2472 from the IETF Secretariat. 2474 The IETF invites any interested party to bring to its attention any 2475 copyrights, patents or patent applications, or other proprietary rights 2476 which may cover technology that may be required to practice this 2477 standard. Please address the information to the IETF Executive 2478 Director. 2480 7.0 Acknowledgments 2482 This document is a product of the DISMAN Working Group. 2484 8.0 References 2486 [1] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 2487 Management Protocol", RFC 1157, SNMP Research, Performance Systems 2488 International, MIT Laboratory for Computer Science, May 1990. 2490 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 2491 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 2492 RFC 1213, Hughes LAN Systems, Performance Systems International, 2493 March 1991. 2495 [3] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 2496 and S. Waldbusser, "Structure of Management Information Version 2 2497 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 2498 Braunschweig, SNMP Research, First Virtual Holdings, International 2499 Network Services, April 1999. 2501 [4] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 2502 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 2503 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 2504 Virtual Holdings, International Network Services, April 1999. 2506 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 2507 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, 2508 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 2509 First Virtual Holdings, International Network Services, April 1999. 2511 [6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol 2512 Operations for Version 2 of the Simple Network Management Protocol 2513 (SNMPv2)", RFC 1905, January 1996. 2515 [7] Harrington D., Presuhn, R., Wijnen, B., "An Architecture for 2516 Describing SNMP Management Frameworks", RFC 2271, Cabletron 2517 Systems, BMC Software, Inc., IBM T.J. Watson Research, January 2518 1998. 2520 [8] Harrington D., Presuhn, R., Wijnen, B., "Message Processing and 2521 Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2522 2272, Cabletron Systems, BMC Software, Inc., IBM T.J. Watson 2523 Research, January 1998. 2525 [9] Levi D., Meyer P., Stewart, B., "SNMPv3 Applications", RFC 2273, 2526 SNMP Research, Inc., Secure Computing Corporation, Cisco Systems, 2527 January 1998. 2529 [10] Blumenthal, U., Wijnen, B., "User-based Security Model (USM) for 2530 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2531 2274, IBM T. J. Watson Research, January 1998. 2533 [11] Wijnen, B., Presuhn, R., McCloghrie, K., "View-based Access Control 2534 Model (VACM) for the Simple Network Management Protocol (SNMP)", 2535 RFC 2275, IBM T.J. Watson Research, BMC Software, Inc., Cisco 2536 Systems, Inc., January 1998. 2538 [12] Hovey, R., and S. Bradner, "The Organizations Involved in the IETF 2539 Standards Process", BCP 11, RFC 2028, October 1996. 2541 [13] Bradner, S., "Key words for use in RFCs to Indicate Requirement 2542 Levels", BCP 14, RFC 2119, March 1997. 2544 [14] Rose, M., and K. McCloghrie, "Structure and Identification of 2545 Management Information for TCP/IP-based Internets", RFC 1155, 2546 Performance Systems International, Hughes LAN Systems, May 1990. 2548 [15] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 2549 Performance Systems International, Hughes LAN Systems, March 1991. 2551 [16] M. Rose, "A Convention for Defining Traps for use with the SNMP", 2552 RFC 1215, Performance Systems International, March 1991. 2554 [17] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2555 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 2556 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 2557 International Network Services, January 1996. 2559 [18] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 2560 Mappings for Version 2 of the Simple Network Management Protocol 2561 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 2562 Dover Beach Consulting, Inc., International Network Services, 2563 January 1996. 2565 [19] Bradner, S., "The Internet Standards Process -- Revision 3", RFC 2566 2026, BCP 9, Harvard University, October 1996. 2568 9.0 Author's Address 2570 Kenneth D. White 2571 Dept. BRQA/Bldg. 501/G114 2572 IBM Corporation 2573 P.O.Box 12195 2574 3039 Cornwallis 2575 Research Triangle Park, NC 27709, USA 2576 E-mail: wkenneth@us.ibm.com 2578 10.0 Full Copyright Statement 2580 Copyright (C) The Internet Society (1997). All Rights Reserved. 2582 This document and translations of it may be copied and furnished to 2583 others, and derivative works that comment on or otherwise explain it or 2584 assist in its implementation may be prepared, copied, published and 2585 distributed, in whole or in part, without restriction of any kind, 2586 provided that the above copyright notice and this paragraph are included 2587 on all such copies and derivative works. However, this document itself 2588 may not be modified in any way, such as by removing the copyright notice 2589 or references to the Internet Society or other Internet organizations, 2590 except as needed for the purpose of developing Internet standards in 2591 which case the procedures for copyrights defined in the Internet 2592 Standards process must be followed, or as required to translate it into 2593 languages other than English. 2595 The limited permissions granted above are perpetual and will not be 2596 revoked by the Internet Society or its successors or assigns. 2598 This document and the information contained herein is provided on an "AS 2599 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2600 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2601 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 2602 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 2603 FITNESS FOR A PARTICULAR PURPOSE.