idnits 2.17.1 draft-ietf-disman-remops-mib-03.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. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard 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 20 instances of too long lines in the document, the longest one being 4 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 exact meaning of the all-uppercase expression 'NOT REQUIRED' is not defined in RFC 2119. If it is intended as a requirements expression, it should be rewritten using one of the combinations defined in RFC 2119; otherwise it should not be all-uppercase. -- 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 (December 1998) is 9235 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 1586, but no explicit reference was found in the text == Unused Reference: '12' is defined on line 1630, but no explicit reference was found in the text ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '1') ** Obsolete normative reference: RFC 1902 (ref. '3') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '4') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '5') (Obsoleted by RFC 2580) ** 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: 23 errors (**), 0 flaws (~~), 4 warnings (==), 3 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: June 1999 5 December 1998 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. Internet Drafts are working 15 documents of the Internet Engineering Task Force (IETF), its Areas, and 16 its Working Groups. Note that other groups may also distribute working 17 documents as Internet Drafts. 19 Internet Drafts are draft documents valid for a maximum of six months. 20 Internet Drafts may be updated, replaced, or obsoleted by other 21 documents at any time. It is not appropriate to use Internet Drafts as 22 reference material or to cite them other than as a "working draft" or 23 "work in progress." 25 Please check the I-D abstract listing contained in each Internet Draft 26 directory to learn the current status of this or any Internet Draft. 27 Distribution of this document is unlimited. 29 Copyright Notice 31 Copyright (C) The Internet Society (1998). All Rights Reserved. 33 Abstract 35 This memo defines Management Information Bases (MIBs) for performing 36 remote ping, traceroute and lookup operations at a remote host. When 37 managing a network it is useful to be able to retrieve the results of 38 either a ping or traceroute operation when performed at a remote host. 39 A Lookup capability is defined to enable resolving either a IP address 40 to a DNS name or a DNS name to a IP address at a remote host. 42 Currently, there exists several enterprise defined MIBs for performing 43 both remote ping or traceroute operations. The purpose of this memo is 44 to defined a standards-based solution to enable interoperibility. 46 Table of Contents 48 1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 50 2.0 The SNMP Network Management Framework . . . . . . . . . . . . 3 52 3.0 Structure of the MIBs . . . . . . . . . . . . . . . . . . . . 4 53 3.1 Ping MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 54 3.2 Traceroute MIB . . . . . . . . . . . . . . . . . . . . . . . . 6 55 3.3 Lookup MIB . . . . . . . . . . . . . . . . . . . . . . . . . . 7 57 4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8 59 5.0 Security Considerations . . . . . . . . . . . . . . . . . . . 30 61 6.0 Intellectual Property . . . . . . . . . . . . . . . . . . . . 30 63 7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 31 65 8.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . 31 67 9.0 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 32 69 10.0 Full Copyright Statement . . . . . . . . . . . . . . . . . . 32 71 1.0 Introduction 73 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 74 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 75 document are to be interpreted as described in RFC 2119, reference [13]. 77 This document is a product of the Distributed Management (DISMAN) 78 Working Group. Its purpose is to define standards-based MIB modules for 79 performing specific remote operations. The remote operations define by 80 this document consist of the ping, traceroute and lookup functions. 82 Ping and traceroute are two very useful functions for managing networks. 83 Ping is typically used to determine if a path exists between two hosts 84 while traceroute shows an actual path. Ping is usually implemented 85 using the InterNet Control Message Protocol (ICMP) "ECHO" facility. It 86 is also possible to implement a ping capability using alternate methods. 87 For example, if the udp echo port (7) is supported at a target host it 88 could be used instead of the ICMP echo facility. 90 Traceroute is usually implemented by transmitting a series of probe 91 packets with increasing time-to-live values. A probe packet is a UDP 92 datagram encapsulated into an IP packet. Each hop in a path to the 93 target (destination) host rejects the probe packets (probe's TTL too 94 small) until its time-to-live value becomes large enough for the probe 95 to be forwarded. Some systems use icmp probes instead of udp ones to 96 implement traceroute. In both cases traceroute relies on the probes 97 being rejected via an ICMP message to discover the hops taken along a 98 path to the final destination. 100 The actually method chosen to implement either the ping or traceroute 101 functions at a remote host is considered to be implementation dependent. 102 An agent implementation SHOULD use whatever method is thought to be best 103 for its environment and document its behavior in its agent's capability 104 statement when referring to the MIBs defined by this document. 106 Both ping and traceroute yield the round-trip times measured in 107 milliseconds. These times can be used as an rough approximation for 108 network transit time. 110 The Lookup operation enables the equivalent of either a gethostbyname() 111 or a gethostbyaddr() call being performed at a remote host. The 112 traceroute function provided does not provide the DNS names of the 113 intermediate hops. The Lookup gethostbyname() capability can be used to 114 determine the symbolic name of a hop in a traceroute path. Neither the 115 remote ping or traceroute operations accept a DNS name as the address of 116 the target host. The Lookup function gethostbyaddr() can be used prior 117 to using a remote ping or traceroute operation in order to determine the 118 numeric address of a host. 120 Consider the following diagram: 122 +----------------------------------------------------------------------+ 123 | | 124 | Remote ping, traceroute, Actual ping, traceroute, | 125 | +-----+or Lookup op. +------+or Lookup op. +------+ | 126 | |Local|---------------->|Remote|---------------->|Target| | 127 | | Host| | Host | | Host | | 128 | +-----+ +------+ +------+ | 129 | | 130 | | 131 +----------------------------------------------------------------------+ 133 A local host is the host from which the remote ping, traceroute, or 134 Lookup operation is initiated from using an SNMP request. The remote 135 host is a host where the MIBs defined by this memo are implemented that 136 receives the remote operation via SNMP and performs the actual ping, 137 traceroute, or lookup function. 139 2.0 The SNMP Network Management Framework 141 The SNMP Management Framework presently consists of five major 142 components: 144 o An overall architecture, described in RFC 2271 [7]. 146 o Mechanisms for describing and naming objects and events for the 147 purpose of management. The first version of this Structure of 148 Management Information (SMI) is called SMIv1 and described in RFC 149 1155 [14], RFC 1212 [15] and RFC 1215 [16]. The second version, 150 called SMIv2, is described in RFC 1902 [3], RFC 1903 [4] and RFC 151 1904 [5]. 153 o Message protocols for transferring management information. The 154 first version of the SNMP message protocol is called SNMPv1 and 155 described in RFC 1157 [1]. A second version of the SNMP message 156 protocol, which is not an Internet standards track protocol, is 157 called SNMPv2c and described in RFC 1901 [17] and RFC 1906 [18]. 158 The third version of the message protocol is called SNMPv3 and 159 described in RFC 1906 [18], RFC 2272 [8] and RFC 2274 [10]. 161 o Protocol operations for accessing management information. The first 162 set of protocol operations and associated PDU formats is described 163 in RFC 1157 [1]. A second set of protocol operations and associated 164 PDU formats is described in RFC 1905 [6]. 166 o A set of fundamental applications described in RFC 2273 [9] and the 167 view-based access control mechanism described in RFC 2275 [11]. 169 Managed objects are accessed via a virtual information store, termed the 170 Management Information Base or MIB. Objects in the MIB are defined 171 ore, using the mechanisms defined in the SMI. 173 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 174 conforming to the SMIv1 can be produced through the appropriate 175 translations. The resulting translated MIB must be semantically 176 equivalent, except where objects or events are omitted because no 177 translation is possible (use of Counter64). Some machine readable 178 information in SMIv2 will be converted into textual descriptions in 179 SMIv1 during the translation process. However, this loss of machine 180 readable information is not considered to change the semantics of the 181 MIB. 183 3.0 Structure of the MIBs 185 This document defines three MIB modules: 187 o DISMAN-PING-MIB 189 Enables the ping function at a remote host. 191 o DISMAN-TRACEROUTE-MIB 193 Enables the traceroute function at a remote host. 195 o DISMAN-LOOKUP-MIB 197 Provides access to the resolver gethostbyname() and gethostbyaddr() 198 functions at a remote host. 200 3.1 Ping MIB 202 The DISMAN-PING-MIB consists of the following components: 204 o pingSpinLock, pingPingMaxConcurrentRequests, and pingPurgeTime 206 o pingTable 208 o pingResultsTable 210 An agent MUST implement the pingSpinLock object to enable management 211 applications to coordinate their use of the DISMAN-PING-MIB. Management 212 application use of pingSpinLock is OPTIONAL. 214 The object pingMaxConcurrentRequests enable control of the maximum 215 number of concurrent requests that an agent implementation is structured 216 to support. It is permissible for an agent to either limit the maximum 217 upper range allowed for this object or to implement this object as 218 read-only with an implementation limit expressed as its value. 220 The object pingPurgeTime provides a method for entries in pingTable and 221 pingResultsTable to be automatically deleted after the associating 222 operation completes. 224 A remote ping operation is initiated by performing an SNMP SET request 225 on pingRowStatus. The first index element, pingOwnerIndex, is of the 226 SnmpAdminString textual convention that allows for use of the SNMPv3 227 VACM security model and also allows for a management application to 228 identify its entries. 230 The 2nd index, pingHostAddress, specifies the target address (ipv4 or 231 ipv6) for the operation. 233 Using the maximum value for the parameters defined within an pingEntry 234 can result in a remote ping operation taking at most 15 minutes 235 (pingTimeOut times pingProbeCount) plus whatever time it takes to send 236 the ping request and receive its response over the network. Use of the 237 defaults for pingTimeOut and pingProbeCount yields a maximum of 3 238 seconds to perform the actual ping operation. The object pingOperStatus 239 can be polled to determine when a ping operation completes prior to 240 retrieve the results of the operation from the pingResultsTable. 242 A management application can delete an active remote ping request by 243 setting the corresponding pingRowStatus object to destroy(6). 245 An implementation SHOULD NOT retain SNMP-created entries in the 246 pingTable and the pingResultsTable across reIPLs (Initial Program Loads) 247 of its agent, since management applications need to see consistent 248 behavior with respect to the persistence of the table entries that they 249 create. 251 3.2 Traceroute MIB 253 The DISMAN-TRACEROUTE-MIB consists of the following components: 255 o traceRouteSpinLock, traceRouteMaxConcurrentRequests, and 256 traceRoutePurgeTime 258 o traceRouteTable 260 o traceRouteResultsTable 262 An agent MUST implement the traceRouteSpinLock object to enable 263 management applications to coordinate their use of the 264 DISMAN-TRACEROUTE-MIB. Management application use of traceRouteSpinLock 265 is OPTIONAL. 267 The object traceRouteMaxConcurrentRequests enable control of the maximum 268 number of concurrent requests that an agent implementation is structured 269 to support. It is permissible for an agent to either limit the maximum 270 upper range allowed for this object or to implement this object as 271 read-only with an implementation limit expressed as its value. 273 The object traceRoutePurgeTime provides a method for entries in 274 traceRouteTable and traceRouteResultsTable to be automatically deleted 275 after the associating operation completes. 277 A remote traceroute operation is initiated by performing an SNMP SET 278 request on traceRouteRowStatus. The first index element, 279 traceRouteOwnerIndex, is of the SnmpAdminString textual convention that 280 allows for use of the SNMPv3 VACM security model and also allows for a 281 management application to identify its entries. 283 The 2nd index, traceRouteHostAddress, specifies the target address (ipv4 284 or ipv6) for the operation. 286 Traceroute has a much longer theoretical maximum time for completion 287 than ping. Basically 42 hours and 30 minutes (the product of 288 traceRouteTimeOut, traceRouteProbesPerHop, and traceRouteMaxTtl) plus 289 some network transit time! Use of the defaults defined within an 290 traceRouteEntry yields a maximum of 4 minutes and 30 seconds for a 291 default traceroute operation. Clearly 42 plus hours is too long to wait 292 for a traceroute operation to complete. 294 The maximum TTL value in effect for traceroute route determines how long 295 the traceroute function will keep increasing the TTL value in the probe 296 it transmits hoping to reach the target host. The function ends 297 whenever the maximum TTL is exceeded or the target host is reached. The 298 object traceRouteSetupMaxFailures was created in order to impose a 299 throttle for how long traceroute continues to increase the TTL field in 300 a probe without receiving any kind of response (timeouts). It is 301 RECOMMENDED that agent implementations impose a time limit for how long 302 it allows a traceroute operation to take relative to how the function is 303 implemented. For example, an implemented that can't process multiple 304 traceroute operations at the same time SHOULD impose a shorter maximum 305 allowed time period. The object traceRouteOperStatus can be examined to 306 determine the state of an traceroute operation. The objects 307 traceRouteCurHopCount and traceRouteCurProbeCount can be exaimed to 308 determine how far the remote traceroute operation has reached. 310 A management application can delete an active remote traceroute request 311 by setting the corresponding traceRouteRowStatus object to destroy(6). 313 An implementation SHOULD NOT retain SNMP-created entries in the 314 traceRouteTable and the traceRouteResultsTable across reIPLs (Initial 315 Program Loads) of its agent, since management applications need to see 316 consistent behavior with respect to the persistence of the table entries 317 that they create. 319 3.3 Lookup MIB 321 The DISMAN-LOOKUP-MIB consists of the following components: 323 o lookupSpinLock, lookupMaxConcurrentRequests, and lookupPurgeTime 325 o lookupTable 327 An agent MUST implement the lookupSpinLock object to enable management 328 applications to coordinate their use of the DISMAN-LOOKUP-MIB. 329 Management application use of lookupSpinLock is OPTIONAL. 331 The object lookupMaxConcurrentRequests enable control of the maximum 332 number of concurrent requests that an agent implementation is structured 333 to support. It is permissible for an agent to either limit the maximum 334 upper range allowed for this object or to implement this object as 335 read-only with an implementation limit expressed as its value. 337 The object lookupPurgeTime provides a method for entries in the 338 lookupTable to be automatically deleted after the associating operation 339 completes. 341 A remote lookup operation is initiated by performing an SNMP SET request 342 on lookupRowStatus. An lookupEntry is indexed by lookupOwnerIndex, 343 which is of the SnmpAdminString textual convention that allows for use 344 of the SNMPv3 VACM security model and also allows for a management 345 application to identify its entries. 347 A remote lookup operation is started by transitioning its 348 lookupRowStatus object to active(1). The object lookupCtl MUST be 349 assigned a value in order for a lookupRowStatus transition to active(1) 350 to succeed. A value of getHostByName(1) for lookupCtl requires that 351 lookupDnsName contain the name to be used prior to activation of the 352 function. The object lookupAddress will contain the result of a 353 successful gethostbyname lookup operation. A value of getHostByAddr(2) 354 for lookupCtl requires that lookupAddress contain the address to be used 355 prior to activation of the function. The object lookupDnsName will 356 contain the result of a successful gethostbyaddr lookup operation. 358 The object lookupOperStatus can be examined to determine the state of an 359 lookup operation. A management application can delete an active remote 360 lookup request by setting the corresponding lookupRowStatus object to 361 destroy(6). 363 An implementation SHOULD NOT retain SNMP-created entries in the 364 lookupTable across reIPLs (Initial Program Loads) of its agent, since 365 management applications need to see consistent behavior with respect to 366 the persistence of the table entries that they create. 368 4.0 Definitions 370 DISMAN-PING-MIB DEFINITIONS ::= BEGIN 372 IMPORTS 373 MODULE-IDENTITY, OBJECT-TYPE, Integer32, 374 experimental 375 FROM SNMPv2-SMI -- RFC1902 376 TEXTUAL-CONVENTION, RowStatus, 377 TestAndIncr 378 FROM SNMPv2-TC -- RFC1903 379 MODULE-COMPLIANCE, OBJECT-GROUP 380 FROM SNMPv2-CONF -- RFC1904 381 SnmpAdminString 382 FROM SNMP-FRAMEWORK-MIB; -- RFC2271 384 pingMIB MODULE-IDENTITY 385 LAST-UPDATED "9812200000Z" 386 ORGANIZATION "IETF Distributed Management Working Group" 387 CONTACT-INFO 388 "Kenneth White 390 International Business Machines Corporation 391 Network Computing Software Division 392 Research Triangle Park, NC, USA 394 E-mail: wkenneth@us.ibm.com" 395 DESCRIPTION 396 "The Ping MIB (DISMAN-PING-MIB) enables use of the ping 397 function via use of the SNMP protocol." 398 ::= { experimental 84 1 } 400 -- Textual Conventions 402 HostAddress ::= TEXTUAL-CONVENTION 403 STATUS current 404 DESCRIPTION 405 "The textual convention for specifying a host 406 address. The type of address can be determined 407 by the octet string length: 409 OCTETs ADDRESS TYPE 410 0 not specified 411 4 ipv4 412 16 ipv6" 413 SYNTAX OCTET STRING (SIZE (0..16)) 415 OperationStatus ::= TEXTUAL-CONVENTION 416 STATUS current 417 DESCRIPTION 418 "The textual convention for specifying the states that 419 an operation can be in." 420 SYNTAX INTEGER { 421 notStarted(1), 422 active(2), 423 completed(3) 424 } 426 -- Top-level structure of the MIB 428 pingNotifications OBJECT IDENTIFIER ::= { pingMIB 0 } 429 pingObjects OBJECT IDENTIFIER ::= { pingMIB 1 } 430 pingConformance OBJECT IDENTIFIER ::= { pingMIB 2 } 432 -- Simple Object Definitions 434 pingSpinLock OBJECT-TYPE 435 SYNTAX TestAndIncr 436 MAX-ACCESS read-write 437 STATUS current 438 DESCRIPTION 439 "An advisory lock used to allow cooperating 440 ping applications to coordinate their 441 use of the pingPingTable. 443 This object should be used when an application seeks to create 444 an new entry or alter an existing entry in the 445 pingTable. A management implementation MAY utilize 446 the pingSpinLock to serialize its changes or additions. 447 Its usage is NOT REQUIRED." 448 ::= { pingObjects 1 } 450 pingMaxConcurrentRequests OBJECT-TYPE 451 SYNTAX Integer32 (1..100) 452 MAX-ACCESS read-write 453 STATUS current 454 DESCRIPTION 455 "The maximum number of concurrent active ping requests 456 that are allowed within an agent implementation." 457 DEFVAL { 10 } 458 ::= { pingObjects 2 } 460 pingPurgeTime OBJECT-TYPE 461 SYNTAX Integer32 (0..86400) 462 UNITS "seconds" 463 MAX-ACCESS read-write 464 STATUS current 465 DESCRIPTION 466 "The amount of time to wait before automatically 467 deleting an entry in the pingTable and all 468 dependent pingResultsTable entries after 469 the ping operation represented by an entry 470 in the pingTable has completed." 471 DEFVAL { 900 } -- 15 minutes as default 472 ::= { pingObjects 3 } 474 -- Ping Table 476 pingTable OBJECT-TYPE 477 SYNTAX SEQUENCE OF PingEntry 478 MAX-ACCESS not-accessible 479 STATUS current 480 DESCRIPTION 481 "Defines the Ping Table for provide 482 via SNMP the capability of invoking ping from a remote 483 host." 484 ::= { pingObjects 4 } 486 pingEntry OBJECT-TYPE 487 SYNTAX PingEntry 488 MAX-ACCESS not-accessible 489 STATUS current 490 DESCRIPTION 491 "Defines an entry in the pingTable." 492 INDEX { 493 pingOwnerIndex, 494 pingHostAddress 495 } 496 ::= { pingTable 1 } 498 PingEntry ::= 499 SEQUENCE { 500 pingOwnerIndex SnmpAdminString, 501 pingHostAddress HostAddress, 502 pingPacketSize Integer32, 503 pingTimeOut Integer32, 504 pingProbeCount Integer32, 505 pingOperStatus OperationStatus, 506 pingRowStatus RowStatus 507 } 509 pingOwnerIndex OBJECT-TYPE 510 SYNTAX SnmpAdminString (SIZE(0..32)) 511 MAX-ACCESS not-accessible 512 STATUS current 513 DESCRIPTION 514 "To facilitate the provisioning of access control by a security 515 administrator using the View-Based Access Control Model (RFC 2275, 516 VACM) for tables in which multiple users may need to independently 517 create or modify entries, the initial index is used as an 'owner 518 index'. Such an initial index has a syntax of SnmpAdminString, 519 and can thus be trivially mapped to a securityName or groupName 520 as defined in VACM, in accordance with a security policy. 522 All entries in that table belonging to a particular user will 523 have the same value for this initial index. For a given user's 524 entries in a particular table, the object identifiers for the 525 information in these entries will have the same subidentifiers 526 (except for the 'column' subidentifier) up to the end of the 527 encoded owner index. To configure VACM to permit access to this 528 portion of the table, one would create vacmViewTreeFamilyTable 529 entries with the value of vacmViewTreeFamilySubtree including the 530 owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the 531 column subidentifier. More elaborate configurations are possible." 532 ::= { pingEntry 1 } 534 pingHostAddress OBJECT-TYPE 535 SYNTAX HostAddress 536 MAX-ACCESS not-accessible 537 STATUS current 538 DESCRIPTION 539 "Specifies the host address used on by ping request by 540 the remote host. The host address type can be determined 541 by its octet string length." 542 ::= { pingEntry 2 } 544 pingPacketSize OBJECT-TYPE 545 SYNTAX Integer32 (0..65507) 546 UNITS "octets" 547 MAX-ACCESS read-create 548 STATUS current 549 DESCRIPTION 550 "Specifies the size of the data portion to be 551 transmitted in a ping request in octets. A ping 552 request is usually an ICMP message encoded 553 into an IP packet. An IP packet has a maximum size 554 of 65535 octets. Subtracting the size of the ICMP 555 header (8 octets) and the size of the IP header 556 (20 octets) yields a maximum size of 65507 octets." 557 DEFVAL { 0 } 558 ::= { pingEntry 3 } 560 pingTimeOut OBJECT-TYPE 561 SYNTAX Integer32 (1..60) 562 UNITS "seconds" 563 MAX-ACCESS read-create 564 STATUS current 565 DESCRIPTION 566 "Specifies the time-out value, in seconds, for the actual 567 PING request made by the remote host. Valid values for 568 time out are from 1 to 60 seconds." 569 DEFVAL { 3 } 570 ::= { pingEntry 4 } 572 pingProbeCount OBJECT-TYPE 573 SYNTAX Integer32 (1..15) 574 MAX-ACCESS read-create 575 STATUS current 576 DESCRIPTION 577 "Specifies the number of times to issue a ping 578 request at a remote host." 579 DEFVAL { 1 } 580 ::= { pingEntry 5 } 582 pingOperStatus OBJECT-TYPE 583 SYNTAX OperationStatus 584 MAX-ACCESS read-only 585 STATUS current 586 DESCRIPTION 587 "Reflects the operational state of a remote 588 ping operation." 589 ::= { pingEntry 6 } 591 pingRowStatus OBJECT-TYPE 592 SYNTAX RowStatus 593 MAX-ACCESS read-create 594 STATUS current 595 DESCRIPTION 596 "This object allows entries to be created and deleted 597 in the pingTable. Deletion of an entry in this 598 table results in all dependent pingResultsTable entries 599 being deleted. 601 A remote ping operation is started when an 602 entry in this table is created via an SNMP SET 603 request and the entry is activated. This 604 can occur by setting the value of this object 605 to CreateAndGo(4) during row creation or 606 by setting this object to active(1) after 607 the row is created. 609 A ping request starts when its entry 610 first becomes active(1). Transitions in and 611 out of active(1) state have no effect on the 612 operational behavior of a remote ping 613 operation, with the exception that deletion of 614 an entry in this table by setting its RowStatus 615 object to destroy(6) will stop an active 616 ping operation. 618 The operational state of an ping operation 619 can be determined by examination of it's 620 pingOperStatus object." 622 REFERENCE 623 "RFC 1903, 'Textual Conventions for version 2 of the 624 Simple Network Management Protocol (SNMPv2).'" 625 ::= { pingEntry 7 } 627 -- Ping Results Table 629 pingResultsTable OBJECT-TYPE 630 SYNTAX SEQUENCE OF PingResultsEntry 631 MAX-ACCESS not-accessible 632 STATUS current 633 DESCRIPTION 634 "Defines the Ping Results Table for 635 storing the results of a ping operation." 636 ::= { pingObjects 5 } 638 pingResultsEntry OBJECT-TYPE 639 SYNTAX PingResultsEntry 640 MAX-ACCESS not-accessible 641 STATUS current 642 DESCRIPTION 643 "Defines an entry in the pingResultsTable." 644 INDEX { 645 pingOwnerIndex, 646 pingHostAddress, 647 pingResultsProbeIndex 648 } 649 ::= { pingResultsTable 1 } 651 PingResultsEntry ::= 652 SEQUENCE { 653 pingResultsProbeIndex Integer32, 654 pingResultsResponse Integer32 655 } 657 pingResultsProbeIndex OBJECT-TYPE 658 SYNTAX Integer32 (1..15) 659 MAX-ACCESS not-accessible 660 STATUS current 661 DESCRIPTION 662 "An entry in this table is created when the results of 663 a ping probe is determined. The initial instance 664 identifier value identifies the pingEntry 665 that a probe result (pingResultsEntry) belongs 666 to." 667 ::= { pingResultsEntry 1 } 669 pingResultsResponse OBJECT-TYPE 670 SYNTAX Integer32 671 MAX-ACCESS read-only 672 STATUS current 673 DESCRIPTION 674 "The result of the ping operation made by a remote host 675 for a particular probe. The results of the probe is 676 indicated as the value of this object as follows: 678 >=0 Round-trip response time in milliseconds. 679 -1 Internal error. 680 -2 ICMP echo request timed out. 681 -3 Unknown destination address. 682 -4 No route to host. 683 -5 Interface inactive to host. 684 -6 Failed to resolve host name. 685 -7 pingMaxConcurrentRequests limit reached." 686 ::= { pingResultsEntry 2 } 688 --------------------------------------------------------------------- 689 -- Conformance information 690 -- Compliance statements 691 --------------------------------------------------------------------- 693 pingCompliances OBJECT IDENTIFIER ::= { pingConformance 1 } 694 pingGroups OBJECT IDENTIFIER ::= { pingConformance 2 } 696 --------------------------------------------------------------------- 697 -- Compliance statements 698 --------------------------------------------------------------------- 700 pingCompliance MODULE-COMPLIANCE 701 STATUS current 702 DESCRIPTION 703 "The compliance statement for the DISMAN-PING-MIB." 704 MODULE -- this module 705 MANDATORY-GROUPS { 706 pingGroup 707 } 709 OBJECT pingMaxConcurrentRequests 710 MIN-ACCESS read-only 711 DESCRIPTION 712 "The agent is not required to support a SET 713 operation to this object." 715 OBJECT pingPurgeTime 716 MIN-ACCESS read-only 717 DESCRIPTION 718 "The agent is not required to support a SET 719 operation to this object." 720 ::= { pingCompliances 1 } 722 --------------------------------------------------------------------- 723 -- MIB groupings 724 --------------------------------------------------------------------- 726 pingGroup OBJECT-GROUP 727 OBJECTS { 728 pingSpinLock, 729 pingMaxConcurrentRequests, 730 pingPurgeTime, 731 pingPacketSize, 732 pingTimeOut, 733 pingProbeCount, 734 pingOperStatus, 735 pingRowStatus, 736 pingResultsResponse 737 } 738 STATUS current 739 DESCRIPTION 740 "The group of objects that comprise the ping 741 operation." 742 ::= { pingGroups 1 } 744 END 745 DISMAN-TRACEROUTE-MIB DEFINITIONS ::= BEGIN 747 IMPORTS 748 MODULE-IDENTITY, OBJECT-TYPE, Integer32, 749 experimental 750 FROM SNMPv2-SMI -- RFC1902 751 RowStatus, 752 TestAndIncr, TruthValue 753 FROM SNMPv2-TC -- RFC1903 754 MODULE-COMPLIANCE, OBJECT-GROUP 755 FROM SNMPv2-CONF -- RFC1904 756 Utf8String 757 FROM SYSAPPL-MIB -- RFC2287 758 SnmpAdminString 759 FROM SNMP-FRAMEWORK-MIB -- RFC2271 760 HostAddress, OperationStatus 761 FROM DISMAN-PING-MIB; 763 traceRouteMIB MODULE-IDENTITY 764 LAST-UPDATED "9812200000Z" 765 ORGANIZATION "IETF Distributed Management Working Group" 766 CONTACT-INFO 767 "Kenneth White 769 International Business Machines Corporation 770 Network Computing Software Division 771 Research Triangle Park, NC, USA 773 E-mail: wkenneth@us.ibm.com" 774 DESCRIPTION 775 "The Traceroute MIB (DISMAN-TRACEROUTE-MIB) enables use 776 of the tracerroute via use of the SNMP protocol." 777 ::= { experimental 84 2 } 779 -- Top-level structure of the MIB 780 traceRouteNotifications OBJECT IDENTIFIER ::= { traceRouteMIB 0 } 781 traceRouteObjects OBJECT IDENTIFIER ::= { traceRouteMIB 1 } 782 traceRouteConformance OBJECT IDENTIFIER ::= { traceRouteMIB 2 } 784 -- Simple Object Definitions 786 traceRouteSpinLock OBJECT-TYPE 787 SYNTAX TestAndIncr 788 MAX-ACCESS read-write 789 STATUS current 790 DESCRIPTION 791 "An advisory lock used to allow cooperating 792 traceroute applications to coordinate their 793 use of the traceRouteTable. 795 This object should be used when an application seeks to create 796 an new entry or alter an existing entry in the traceRouteTable. 797 A management implementation MAY utilize 798 the traceRouteSpinLock to serialize its changes or additions. 799 Its usage is NOT REQUIRED." 800 ::= { traceRouteObjects 1 } 802 traceRouteMaxConcurrentRequests OBJECT-TYPE 803 SYNTAX Integer32 (1..100) 804 MAX-ACCESS read-write 805 STATUS current 806 DESCRIPTION 807 "The maximum number of concurrent active traceroute requests 808 that are allowed within an agent implementation." 809 DEFVAL { 10 } 810 ::= { traceRouteObjects 2 } 812 traceRoutePurgeTime OBJECT-TYPE 813 SYNTAX Integer32 (0..86400) 814 UNITS "seconds" 815 MAX-ACCESS read-write 816 STATUS current 817 DESCRIPTION 818 "The amount of time to wait before automatically 819 deleting an entry in traceRouteTable and all 820 dependent traceRouteResultsTable entries after 821 the traceroute operation represented by an 822 traceRouteEntry has completed." 823 DEFVAL { 900 } -- 15 minutes as default 824 ::= { traceRouteObjects 3 } 826 -- Traceroute Table 828 traceRouteTable OBJECT-TYPE 829 SYNTAX SEQUENCE OF TraceRouteEntry 830 MAX-ACCESS not-accessible 831 STATUS current 832 DESCRIPTION 833 "Defines the Remote Operations Traceroute Table for provide 834 via SNMP the capability of invoking traceroute 835 from a remote host." 836 ::= { traceRouteObjects 4 } 838 traceRouteEntry OBJECT-TYPE 839 SYNTAX TraceRouteEntry 840 MAX-ACCESS not-accessible 841 STATUS current 842 DESCRIPTION 843 "Defines an entry in the traceRouteTable." 844 INDEX { 845 traceRouteOwnerIndex, 846 traceRouteHostAddress 847 } 848 ::= { traceRouteTable 1 } 850 TraceRouteEntry ::= 851 SEQUENCE { 852 traceRouteOwnerIndex SnmpAdminString, 853 traceRouteHostAddress HostAddress, 854 traceRouteByPassRouteTable TruthValue, 855 traceRoutePacketSize Integer32, 856 traceRouteTimeOut Integer32, 857 traceRouteProbesPerHop Integer32, 858 traceRoutePort Integer32, 859 traceRouteMaxTtl Integer32, 860 traceRouteTos Integer32, 861 traceRouteSourceAddress HostAddress, 862 traceRouteInterfaceName OCTET STRING, 863 traceRouteMiscOptions Utf8String, 864 traceRouteMaxFailures Integer32, 865 traceRouteOperStatus OperationStatus, 866 traceRouteCurHopCount Integer32, 867 traceRouteCurProbeCount Integer32, 868 traceRouteRowStatus RowStatus 869 } 871 traceRouteOwnerIndex OBJECT-TYPE 872 SYNTAX SnmpAdminString (SIZE(0..32)) 873 MAX-ACCESS not-accessible 874 STATUS current 875 DESCRIPTION 876 "To facilitate the provisioning of access control by a security 877 administrator using the View-Based Access Control Model (RFC 2275, 878 VACM) for tables in which multiple users may need to independently 879 create or modify entries, the initial index is used as an 'owner 880 index'. Such an initial index has a syntax of SnmpAdminString, 881 and can thus be trivially mapped to a securityName or groupName 882 as defined in VACM, in accordance with a security policy. 884 All entries in this table belonging to a particular user will 885 have the same value for this initial index. For a given user's 886 entries in a particular table, the object identifiers for the 887 information in these entries will have the same subidentifiers 888 (except for the 'column' subidentifier) up to the end of the 889 encoded owner index. To configure VACM to permit access to this 890 portion of the table, one would create vacmViewTreeFamilyTable 891 entries with the value of vacmViewTreeFamilySubtree including the 892 owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the 893 column subidentifier. More elaborate configurations are possible." 894 ::= { traceRouteEntry 1 } 896 traceRouteHostAddress OBJECT-TYPE 897 SYNTAX HostAddress 898 MAX-ACCESS not-accessible 899 STATUS current 900 DESCRIPTION 901 "Specifies the host address used on the 902 traceroute request at the remote host. The 903 host address type can be determined by the 904 length of the corresponding octet string." 905 ::= { traceRouteEntry 2 } 907 traceRouteByPassRouteTable OBJECT-TYPE 908 SYNTAX TruthValue 909 MAX-ACCESS read-create 910 STATUS current 911 DESCRIPTION 912 "The purpose of this object is optionally enable 913 bypassing the route table. If enabled bypass the 914 normal routing tables and send directly to a 915 host on an attached network. If the host 916 is not on a directly-attached network, an 917 error is returned. This option can be 918 used to ping a local host through an 919 interface that has no route through it 920 (e.g., after the interface was dropped by 921 routed)." 922 DEFVAL { false } 923 ::= { traceRouteEntry 3 } 925 traceRoutePacketSize OBJECT-TYPE 926 SYNTAX Integer32 (0..65507) 927 UNITS "octets" 928 MAX-ACCESS read-create 929 STATUS current 930 DESCRIPTION 931 "Specifies the size of the data portion of a traceroute 932 request in octets. A traceroute request is essentially 933 transmitted by encoding a UDP datagram into a 934 IP packet. So subtracting the size of a UDP header 935 (8 octets) and the size of a IP header (20 octets) 936 yields a maximum of 65507 octets." 937 DEFVAL { 0 } 938 ::= { traceRouteEntry 4 } 940 traceRouteTimeOut OBJECT-TYPE 941 SYNTAX Integer32 (1..60) 942 UNITS "seconds" 943 MAX-ACCESS read-create 944 STATUS current 945 DESCRIPTION 946 "Specifies the time-out value, in seconds, for 947 a traceroute request." 948 DEFVAL { 3 } 949 ::= { traceRouteEntry 5 } 951 traceRouteProbesPerHop OBJECT-TYPE 952 SYNTAX Integer32 (1..10) 953 UNITS "count" 954 MAX-ACCESS read-create 955 STATUS current 956 DESCRIPTION 957 "Specifies the number of times to reissue a traceroute 958 request with the same time-to-live (TTL) value." 959 DEFVAL { 3 } 960 ::= { traceRouteEntry 6 } 962 traceRoutePort OBJECT-TYPE 963 SYNTAX Integer32 (1..65535) 964 UNITS "UDP Port" 965 MAX-ACCESS read-create 966 STATUS current 967 DESCRIPTION 968 "Specifies the UDP port to sent the traceroute 969 request to. Need to specify a port that is not in 970 use at the destination host." 971 DEFVAL { 4096 } 972 ::= { traceRouteEntry 7 } 974 traceRouteMaxTtl OBJECT-TYPE 975 SYNTAX Integer32 (1..255) 976 UNITS "time-to-live maximum" 977 MAX-ACCESS read-create 978 STATUS current 979 DESCRIPTION 980 "Specifies the maximum time-to-live value." 981 DEFVAL { 30 } 982 ::= { traceRouteEntry 8 } 984 traceRouteTos OBJECT-TYPE 985 SYNTAX Integer32 (0..255) 986 MAX-ACCESS read-create 987 STATUS current 988 DESCRIPTION 989 "Specifies the value to store in the TOS OCTET in 990 the IP probe packet that is transmitted as the 991 traceroute request. The value must be a decimal 992 integer in the range 0 to 255. This option can be 993 used to see if different types-of-service result 994 in different paths. Not all values of TOS are 995 legal or meaningful. TOS is often not supported 996 by IP implementations. Useful values are probably 997 '16' (low delay) and '8' (high throughput)." 998 DEFVAL { 0 } 999 ::= { traceRouteEntry 9 } 1001 traceRouteSourceAddress OBJECT-TYPE 1002 SYNTAX HostAddress 1003 MAX-ACCESS read-create 1004 STATUS current 1005 DESCRIPTION 1006 "Use the specified IP address 1007 (which must be given as an IP number, not a hostname) 1008 as the source address in outgoing probe packets. On 1009 hosts with more than one IP address, this option can 1010 be used to force the source address to be something 1011 other than the IP address of the interface the probe 1012 packet is sent on. If the IP address is not one of this 1013 machine's interface addresses, an error is returned and 1014 nothing is sent." 1015 DEFVAL { ''H } 1016 ::= { traceRouteEntry 10 } 1018 traceRouteInterfaceName OBJECT-TYPE 1019 SYNTAX OCTET STRING (SIZE(0..32)) 1020 MAX-ACCESS read-create 1021 STATUS current 1022 DESCRIPTION 1023 "Setting this object to an interface's name prior 1024 to starting a remote traceroute operation directs 1025 the traceroute probes to be transmitted over the 1026 specified interface." 1027 DEFVAL { ''H } 1028 ::= { traceRouteEntry 11 } 1030 traceRouteMiscOptions OBJECT-TYPE 1031 SYNTAX Utf8String (SIZE(0..64)) 1032 MAX-ACCESS read-create 1033 STATUS current 1034 DESCRIPTION 1035 "Enables an application to specify implementation 1036 dependent options." 1037 DEFVAL { ''H } 1038 ::= { traceRouteEntry 12 } 1040 traceRouteMaxFailures OBJECT-TYPE 1041 SYNTAX Integer32 (1..255) 1042 MAX-ACCESS read-create 1043 STATUS current 1044 DESCRIPTION 1045 "The value of this object indicates the maximum number 1046 of consecutive timeouts allowed before terminating 1047 a remote traceroute request. A value of 255 (maximum 1048 hop count) indicate that the function of terminating 1049 a remote traceroute request when a number of successive 1050 timeouts are detected is disabled." 1051 DEFVAL { 5 } 1052 ::= { traceRouteEntry 13 } 1054 traceRouteOperStatus OBJECT-TYPE 1055 SYNTAX OperationStatus 1056 MAX-ACCESS read-only 1057 STATUS current 1058 DESCRIPTION 1059 "Reflects the operational state of a remote 1060 traceroute operation." 1061 ::= { traceRouteEntry 14 } 1063 traceRouteCurHopCount OBJECT-TYPE 1064 SYNTAX Integer32 (1..255) 1065 MAX-ACCESS read-only 1066 STATUS current 1067 DESCRIPTION 1068 "Reflects the current TTL value for an remote 1069 traceroute operation. Maximum TTL value is 1070 determined by traceRouteMaxTtl." 1071 ::= { traceRouteEntry 15 } 1073 traceRouteCurProbeCount OBJECT-TYPE 1074 SYNTAX Integer32 (1..10) 1075 MAX-ACCESS read-only 1076 STATUS current 1077 DESCRIPTION 1078 "Reflects the current probe count for an remote 1079 traceroute operation. The maximum probe count 1080 is determined by traceRouteProbesPerHop." 1081 ::= { traceRouteEntry 16 } 1083 traceRouteRowStatus OBJECT-TYPE 1084 SYNTAX RowStatus 1085 MAX-ACCESS read-create 1086 STATUS current 1087 DESCRIPTION 1088 "This object allows entries to be created and deleted 1089 in the traceRouteTable. 1091 A remote traceroute operation is started when an 1092 entry in this table is created via an SNMP SET 1093 request and the entry is activated. This 1094 can occur by setting the value of this object 1095 to CreateAndGo(4) during row creation or 1096 by setting this object to active(1) after 1097 the row is created. 1099 A remote traceroute request starts when its entry 1100 first becomes active(1). Transitions in and 1101 out of active(1) state have no effect on the 1102 operational behavior of a remote traceroute 1103 operation, with the exception that deletion of 1104 an entry in this table by setting its RowStatus 1105 object to destroy(6) will stop an active 1106 remote traceroute operation." 1107 REFERENCE 1108 "RFC 1903, 'Textual Conventions for version 2 of the 1109 Simple Network Management Protocol (SNMPv2).'" 1110 ::= { traceRouteEntry 17 } 1112 -- Remote Operations Traceroute Results Table 1114 traceRouteResultsTable OBJECT-TYPE 1115 SYNTAX SEQUENCE OF TraceRouteResultsEntry 1116 MAX-ACCESS not-accessible 1117 STATUS current 1118 DESCRIPTION 1119 "Defines the Remote Operations Traceroute Results Table for 1120 storing the results of a traceroute operation." 1121 ::= { traceRouteObjects 5 } 1123 traceRouteResultsEntry OBJECT-TYPE 1124 SYNTAX TraceRouteResultsEntry 1125 MAX-ACCESS not-accessible 1126 STATUS current 1127 DESCRIPTION 1128 "Defines an entry in the traceRouteResultsTable." 1129 INDEX { 1130 traceRouteOwnerIndex, 1131 traceRouteHostAddress, 1132 traceRouteResultsHopIndex, 1133 traceRouteResultsProbeIndex 1134 } 1135 ::= { traceRouteResultsTable 1 } 1137 TraceRouteResultsEntry ::= 1138 SEQUENCE { 1139 traceRouteResultsHopIndex Integer32, 1140 traceRouteResultsProbeIndex Integer32, 1141 traceRouteResultsHopAddress HostAddress, 1142 traceRouteResultsResponse Integer32 1143 } 1145 traceRouteResultsHopIndex OBJECT-TYPE 1146 SYNTAX Integer32 (1..255) 1147 MAX-ACCESS not-accessible 1148 STATUS current 1149 DESCRIPTION 1150 "An entry in this table has as its initial instance identifier 1151 the value of its corresponding traceRouteEntry's 1152 instance identifier." 1153 ::= { traceRouteResultsEntry 1 } 1155 traceRouteResultsProbeIndex OBJECT-TYPE 1156 SYNTAX Integer32 (1..10) 1157 MAX-ACCESS not-accessible 1158 STATUS current 1159 DESCRIPTION 1160 "Indicates the index of a probe for determining a 1161 hop in a traceroute path." 1162 ::= { traceRouteResultsEntry 2 } 1164 traceRouteResultsHopAddress OBJECT-TYPE 1165 SYNTAX HostAddress 1166 MAX-ACCESS read-only 1167 STATUS current 1168 DESCRIPTION 1169 "The address of a hop in a traceroute path. This object 1170 is not allowed to be a DNS name. The length of the 1171 octet string returned determines the address type." 1172 ::= { traceRouteResultsEntry 3 } 1174 traceRouteResultsResponse OBJECT-TYPE 1175 SYNTAX Integer32 1176 MAX-ACCESS read-only 1177 STATUS current 1178 DESCRIPTION 1179 "The value of this object indicated the result of a 1180 traceroute probe: 1182 >=0 Round-trip response time in milliseconds. 1183 -1 Internal error. 1184 -2 probe timed out. 1185 -3 Unknown destination address. 1186 -4 No route to host. 1187 -5 Interface inactive to host. 1188 -6 Failed to resolve host name. 1189 -7 traceRouteMaxConcurrentRequests limit reached." 1190 ::= { traceRouteResultsEntry 4 } 1192 --------------------------------------------------------------------- 1193 -- Conformance information 1194 -- Compliance statements 1195 --------------------------------------------------------------------- 1197 traceRouteCompliances OBJECT IDENTIFIER ::= { traceRouteConformance 1 } 1198 traceRouteGroups OBJECT IDENTIFIER ::= { traceRouteConformance 2 } 1200 --------------------------------------------------------------------- 1201 -- Compliance statements 1202 --------------------------------------------------------------------- 1203 traceRouteCompliance MODULE-COMPLIANCE 1204 STATUS current 1205 DESCRIPTION 1206 "The compliance statement for the DISMAN-TRACEROUTE-MIB." 1207 MODULE -- this module 1208 MANDATORY-GROUPS { 1209 traceRouteGroup 1210 } 1212 OBJECT traceRouteMaxConcurrentRequests 1213 MIN-ACCESS read-only 1214 DESCRIPTION 1215 "The agent is not required to support a SET 1216 operation to this object." 1218 OBJECT traceRoutePurgeTime 1219 MIN-ACCESS read-only 1220 DESCRIPTION 1221 "The agent is not required to support a SET 1222 operation to this object." 1223 ::= { traceRouteCompliances 1 } 1225 --------------------------------------------------------------------- 1226 -- MIB groupings 1227 --------------------------------------------------------------------- 1229 traceRouteGroup OBJECT-GROUP 1230 OBJECTS { 1231 traceRouteSpinLock, 1232 traceRouteMaxConcurrentRequests, 1233 traceRoutePurgeTime, 1234 traceRouteByPassRouteTable, 1235 traceRoutePacketSize, 1236 traceRouteTimeOut, 1237 traceRouteProbesPerHop, 1238 traceRoutePort, 1239 traceRouteMaxTtl, 1240 traceRouteTos, 1241 traceRouteSourceAddress, 1242 traceRouteInterfaceName, 1243 traceRouteMiscOptions, 1244 traceRouteMaxFailures, 1245 traceRouteOperStatus, 1246 traceRouteCurHopCount, 1247 traceRouteCurProbeCount, 1248 traceRouteRowStatus, 1249 traceRouteResultsHopAddress, 1250 traceRouteResultsResponse 1251 } 1252 STATUS current 1253 DESCRIPTION 1254 "The group of objects that comprise the remote traceroute 1255 operation." 1257 ::= { traceRouteGroups 1 } 1259 END 1260 DISMAN-LOOKUP-MIB DEFINITIONS ::= BEGIN 1262 IMPORTS 1263 MODULE-IDENTITY, OBJECT-TYPE, Integer32, 1264 experimental 1265 FROM SNMPv2-SMI -- RFC1902 1266 RowStatus, TestAndIncr 1267 FROM SNMPv2-TC -- RFC1903 1268 MODULE-COMPLIANCE, OBJECT-GROUP 1269 FROM SNMPv2-CONF -- RFC1904 1270 SnmpAdminString 1271 FROM SNMP-FRAMEWORK-MIB -- RFC2271 1272 DnsName 1273 FROM DNS-SERVER-MIB -- RFC1611 1274 HostAddress, OperationStatus 1275 FROM DISMAN-PING-MIB; 1277 lookupMIB MODULE-IDENTITY 1278 LAST-UPDATED "9812200000Z" 1279 ORGANIZATION "IETF Distributed Management Working Group" 1280 CONTACT-INFO 1281 "Kenneth White 1283 International Business Machines Corporation 1284 Network Computing Software Division 1285 Research Triangle Park, NC, USA 1287 E-mail: wkenneth@us.ibm.com" 1288 DESCRIPTION 1289 "The Lookup MIB (DISMAN-LOOKUP-MIB) enables determination 1290 of either the name corresponding to a host address or of 1291 the address associated with a host name at a remote host 1292 via use of the SNMP protocol," 1293 ::= { experimental 84 3 } 1295 -- Top-level structure of the MIB 1297 lookupNotifications OBJECT IDENTIFIER ::= { lookupMIB 0 } 1298 lookupObjects OBJECT IDENTIFIER ::= { lookupMIB 1 } 1299 lookupConformance OBJECT IDENTIFIER ::= { lookupMIB 2 } 1301 -- Simple Object Definitions 1303 lookupSpinLock OBJECT-TYPE 1304 SYNTAX TestAndIncr 1305 MAX-ACCESS read-write 1306 STATUS current 1307 DESCRIPTION 1308 "An advisory lock used to allow cooperating applications 1309 to coordinate their use of the lookupTable. 1311 This object should be used when an application seeks to create 1312 an new entry or alter an existing entry in the lookupTable. 1313 A management implementation MAY utilize the lookupSpinLock 1314 to serialize its changes or additions. Its usage is NOT 1315 REQUIRED." 1316 ::= { lookupObjects 1 } 1318 lookupMaxConcurrentRequests OBJECT-TYPE 1319 SYNTAX Integer32 (1..100) 1320 MAX-ACCESS read-write 1321 STATUS current 1322 DESCRIPTION 1323 "The maximum number of concurrent active Lookup requests 1324 that are allowed within an agent implementation." 1325 DEFVAL { 10 } 1326 ::= { lookupObjects 2 } 1328 lookupPurgeTime OBJECT-TYPE 1329 SYNTAX Integer32 (0..86400) 1330 UNITS "seconds" 1331 MAX-ACCESS read-write 1332 STATUS current 1333 DESCRIPTION 1334 "The amount of time to wait before automatically 1335 deleting an entry in the lookupTable 1336 after the Lookup operation represented by an 1337 lookupEntry has completed." 1338 DEFVAL { 900 } -- 15 minutes as default 1339 ::= { lookupObjects 3 } 1341 -- Lookup Table 1343 lookupTable OBJECT-TYPE 1344 SYNTAX SEQUENCE OF LookupEntry 1345 MAX-ACCESS not-accessible 1346 STATUS current 1347 DESCRIPTION 1348 "Defines the Lookup Table for provide 1349 via SNMP the capability of performing a lookup operation, 1350 gethostbyname or gethostbyaddr, from a remote host." 1351 ::= { lookupObjects 4 } 1353 lookupEntry OBJECT-TYPE 1354 SYNTAX LookupEntry 1355 MAX-ACCESS not-accessible 1356 STATUS current 1357 DESCRIPTION 1358 "Defines an entry in the lookupTable." 1359 INDEX { 1360 lookupOwnerIndex 1361 } 1362 ::= { lookupTable 1 } 1364 LookupEntry ::= 1365 SEQUENCE { 1366 lookupOwnerIndex SnmpAdminString, 1367 lookupCtl INTEGER, 1368 lookupTimeOut Integer32, 1369 lookupOperStatus OperationStatus, 1370 lookupAddress HostAddress, 1371 lookupDnsName DnsName, 1372 lookupRowStatus RowStatus 1373 } 1375 lookupOwnerIndex OBJECT-TYPE 1376 SYNTAX SnmpAdminString (SIZE(0..32)) 1377 MAX-ACCESS not-accessible 1378 STATUS current 1379 DESCRIPTION 1380 "To facilitate the provisioning of access control by a security 1381 administrator using the View-Based Access Control Model (RFC 2275, 1382 VACM) for tables in which multiple users may need to independently 1383 create or modify entries, the initial index is used as an 'owner 1384 index'. Such an initial index has a syntax of SnmpAdminString, 1385 and can thus be trivially mapped to a securityName or groupName 1386 as defined in VACM, in accordance with a security policy. 1388 All entries in that table belonging to a particular user will 1389 have the same value for this initial index. For a given user's 1390 entries in a particular table, the object identifiers for the 1391 information in these entries will have the same subidentifiers 1392 (except for the 'column' subidentifier) up to the end of the 1393 encoded owner index. To configure VACM to permit access to this 1394 portion of the table, one would create vacmViewTreeFamilyTable 1395 entries with the value of vacmViewTreeFamilySubtree including the 1396 owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the 1397 column subidentifier. More elaborate configurations are possible." 1398 ::= { lookupEntry 1 } 1400 lookupCtl OBJECT-TYPE 1401 SYNTAX INTEGER { 1402 getHostByName(1), 1403 getHostByAddr(2) 1404 } 1405 MAX-ACCESS read-create 1406 STATUS current 1407 DESCRIPTION 1408 "The value of this object determines whether the 1409 getHostByName or the getHostByAddr resolver function 1410 will be invoked at a remote host." 1411 ::= { lookupEntry 2 } 1413 lookupTimeOut OBJECT-TYPE 1414 SYNTAX Integer32 (1..600) 1415 UNITS "seconds" 1416 MAX-ACCESS read-create 1417 STATUS current 1418 DESCRIPTION 1419 "Specifies the time-out value, in seconds, for the 1420 Lookup operation made at a remote host. Valid values 1421 for timeout are from 1 to 600 seconds." 1422 DEFVAL { 3 } 1423 ::= { lookupEntry 3 } 1425 lookupOperStatus OBJECT-TYPE 1426 SYNTAX OperationStatus 1427 MAX-ACCESS read-only 1428 STATUS current 1429 DESCRIPTION 1430 "Reflects the operational state of a 1431 Lookup operation." 1432 ::= { lookupEntry 4 } 1434 lookupAddress OBJECT-TYPE 1435 SYNTAX HostAddress 1436 MAX-ACCESS read-create 1437 STATUS current 1438 DESCRIPTION 1439 "Specifies the address used for a getHostByAddr Lookup 1440 operation at a remote host." 1441 ::= { lookupEntry 5 } 1443 lookupDnsName OBJECT-TYPE 1444 SYNTAX DnsName 1445 MAX-ACCESS read-create 1446 STATUS current 1447 DESCRIPTION 1448 "Specifies the address used for a getHostByName Lookup 1449 operation at a remote host." 1450 ::= { lookupEntry 6 } 1452 lookupRowStatus OBJECT-TYPE 1453 SYNTAX RowStatus 1454 MAX-ACCESS read-create 1455 STATUS current 1456 DESCRIPTION 1457 "This object allows entries to be created and deleted 1458 in the lookupTable. 1460 A remote DNS Lookup operation is started when an 1461 entry in this table is created via an SNMP SET 1462 request and the entry is activated. This 1463 can occur by setting the value of this object 1464 to CreateAndGo(4) during row creation or 1465 by setting this object to active(1) after 1466 the row is created. 1468 A remote DNS Lookup operation starts when its entry 1469 first becomes active(1). Transitions in and 1470 out of active(1) state have no effect on the 1471 operational behavior of a remote DNS Lookup 1472 operation, with the exception that deletion of 1473 an entry in this table by setting its RowStatus 1474 object to destroy(6) will stop an active 1475 remote DNS Lookup operation. 1477 The operational state of a remote DNS Lookup operation 1478 can be determined by examination of it's 1479 lookupOperStatus object." 1480 REFERENCE 1481 "RFC 1903, 'Textual Conventions for version 2 of the 1482 Simple Network Management Protocol (SNMPv2).'" 1483 ::= { lookupEntry 7 } 1485 --------------------------------------------------------------------- 1486 -- Conformance information 1487 -- Compliance statements 1488 --------------------------------------------------------------------- 1490 lookupCompliances OBJECT IDENTIFIER ::= { lookupConformance 1 } 1491 lookupGroups OBJECT IDENTIFIER ::= { lookupConformance 2 } 1493 --------------------------------------------------------------------- 1494 -- Compliance statements 1495 --------------------------------------------------------------------- 1497 lookupCompliance MODULE-COMPLIANCE 1498 STATUS current 1499 DESCRIPTION 1500 "The compliance statement for the DISMAN-LOOKUP-MIB." 1501 MODULE -- this module 1502 MANDATORY-GROUPS { 1503 lookupGroup 1504 } 1506 OBJECT lookupMaxConcurrentRequests 1507 MIN-ACCESS read-only 1508 DESCRIPTION 1509 "The agent is not required to support a SET 1510 operation to this object." 1512 OBJECT lookupPurgeTime 1513 MIN-ACCESS read-only 1514 DESCRIPTION 1515 "The agent is not required to support a SET 1516 operation to this object." 1517 ::= { lookupCompliances 1 } 1519 --------------------------------------------------------------------- 1520 -- MIB groupings 1521 --------------------------------------------------------------------- 1522 lookupGroup OBJECT-GROUP 1523 OBJECTS { 1524 lookupSpinLock, 1525 lookupMaxConcurrentRequests, 1526 lookupPurgeTime, 1527 lookupCtl, 1528 lookupTimeOut, 1529 lookupOperStatus, 1530 lookupAddress, 1531 lookupDnsName, 1532 lookupRowStatus 1533 } 1534 STATUS current 1535 DESCRIPTION 1536 "The group of objects that comprise the remote 1537 Lookup operation." 1538 ::= { lookupGroups 1 } 1540 END 1542 5.0 Security Considerations 1544 Certain management information in the MIBs defined by this document may 1545 be considered sensitive in some network environments. Therefore, 1546 authentication of received SNMP requests and controlled access to 1547 management information SHOULD be employed in such environments. The 1548 method for this authentication is a function of the SNMP Administrative 1549 Framework, and has not been expanded by this MIB. 1551 It is RECOMMENDED that this MIB not be supported in insecure 1552 environments. 1554 6.0 Intellectual Property 1556 The IETF takes no position regarding the validity or scope of any 1557 intellectual property or other rights that might be claimed to pertain 1558 to the implementation or use of the technology described in this 1559 document or the extent to which any license under such rights might or 1560 might not be available; neither does it represent that it has made any 1561 effort to identify any such rights. Information on the IETF's 1562 procedures with respect to rights in standards-track and 1563 standards-related documentation can be found in BCP-11. Copies of 1564 claims of rights made available for publication and any assurances of 1565 licenses to be made available, or the result of an attempt made to 1566 obtain a general license or permission for the use of such proprietary 1567 rights by implementers or users of this specification can be obtained 1568 from the IETF Secretariat. 1570 The IETF invites any interested party to bring to its attention any 1571 copyrights, patents or patent applications, or other proprietary rights 1572 which may cover technology that may be required to practice this 1573 standard. Please address the information to the IETF Executive 1574 Director. 1576 7.0 Acknowledgments 1578 This document is a product of the DISMAN Working Group. 1580 8.0 References 1582 [1] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 1583 Management Protocol", RFC 1157, SNMP Research, Performance Systems 1584 International, MIT Laboratory for Computer Science, May 1990. 1586 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 1587 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 1588 RFC 1213, Hughes LAN Systems, Performance Systems International, 1589 March 1991. 1591 [3] Case, J., McCloghrie, K., Rose, M., and Waldbusser S., "Structure 1592 of Management Information for Version 2 of the Simple Network 1593 Management Protocol (SNMPv2)", RFC 1902, January 1996. 1595 [4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Textual 1596 Conventions for Version 2 of the Simple Network Management Protocol 1597 (SNMPv2)", RFC 1903, January 1996. 1599 [5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 1600 "Conformance Statements for Version 2 of the Simple Network 1601 Management Protocol (SNMPv2)", RFC 1904, January 1996. 1603 [6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol 1604 Operations for Version 2 of the Simple Network Management Protocol 1605 (SNMPv2)", RFC 1905, January 1996. 1607 [7] Harrington D., Presuhn, R., Wijnen, B., "An Architecture for 1608 Describing SNMP Management Frameworks", RFC 2271, Cabletron 1609 Systems, BMC Software, Inc., IBM T.J. Watson Research, January 1610 1998. 1612 [8] Harrington D., Presuhn, R., Wijnen, B., "Message Processing and 1613 Dispatching for the Simple Network Management Protocol (SNMP)", RFC 1614 2272, Cabletron Systems, BMC Software, Inc., IBM T.J. Watson 1615 Research, January 1998. 1617 [9] Levi D., Meyer P., Stewart, B., "SNMPv3 Applications", RFC 2273, 1618 SNMP Research, Inc., Secure Computing Corporation, Cisco Systems, 1619 January 1998. 1621 [10] Blumenthal, U., Wijnen, B., "User-based Security Model (USM) for 1622 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1623 2274, IBM T. J. Watson Research, January 1998. 1625 [11] Wijnen, B., Presuhn, R., McCloghrie, K., "View-based Access Control 1626 Model (VACM) for the Simple Network Management Protocol (SNMP)", 1627 RFC 2275, IBM T.J. Watson Research, BMC Software, Inc., Cisco 1628 Systems, Inc., January 1998. 1630 [12] Hovey, R., and S. Bradner, "The Organizations Involved in the IETF 1631 Standards Process", BCP 11, RFC 2028, October 1996. 1633 [13] Bradner, S., "Key words for use in RFCs to Indicate Requirement 1634 Levels", BCP 14, RFC 2119, March 1997. 1636 [14] Rose, M., and K. McCloghrie, "Structure and Identification of 1637 Management Information for TCP/IP-based Internets", RFC 1155, 1638 Performance Systems International, Hughes LAN Systems, May 1990. 1640 [15] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1641 Performance Systems International, Hughes LAN Systems, March 1991. 1643 [16] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1644 RFC 1215, Performance Systems International, March 1991. 1646 [17] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1647 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 1648 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1649 International Network Services, January 1996. 1651 [18] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1652 Mappings for Version 2 of the Simple Network Management Protocol 1653 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1654 Dover Beach Consulting, Inc., International Network Services, 1655 January 1996. 1657 9.0 Author's Address 1659 Kenneth D. White 1660 Dept. BRQA/Bldg. 501/G114 1661 IBM Corporation 1662 P.O.Box 12195 1663 3039 Cornwallis 1664 Research Triangle Park, NC 27709, USA 1665 E-mail: wkenneth@us.ibm.com 1667 10.0 Full Copyright Statement 1669 Copyright (C) The Internet Society (1997). All Rights Reserved. 1671 This document and translations of it may be copied and furnished to 1672 others, and derivative works that comment on or otherwise explain it or 1673 assist in its implementation may be prepared, copied, published and 1674 distributed, in whole or in part, without restriction of any kind, 1675 provided that the above copyright notice and this paragraph are included 1676 on all such copies and derivative works. However, this document itself 1677 may not be modified in any way, such as by removing the copyright notice 1678 or references to the Internet Society or other Internet organizations, 1679 except as needed for the purpose of developing Internet standards in 1680 which case the procedures for copyrights defined in the Internet 1681 Standards process must be followed, or as required to translate it into 1682 languages other than English. 1684 The limited permissions granted above are perpetual and will not be 1685 revoked by the Internet Society or its successors or assigns. 1687 This document and the information contained herein is provided on an "AS 1688 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1689 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1690 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1691 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1692 FITNESS FOR A PARTICULAR PURPOSE.