idnits 2.17.1 draft-ietf-disman-remops-mib-02.txt: -(122): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding -(123): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding 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. == There are 2 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 28 longer pages, the longest (page 2) being 61 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 29 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 18 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 (September 1998) is 9354 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 1401, but no explicit reference was found in the text == Unused Reference: '12' is defined on line 1445, 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 (~~), 7 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: March 1999 5 September 1998 7 Definitions of Managed Objects for 8 Remote Operations Using SMIv2 9 11 Status of this Memo 13 This document is an Internet Draft. Internet Drafts are working 14 documents of the Internet Engineering Task Force (IETF), its Areas, and 15 its Working Groups. Note that other groups may also distribute working 16 documents as Internet Drafts. 18 Internet Drafts are draft documents valid for a maximum of six months. 19 Internet Drafts may be updated, replaced, or obsoleted by other 20 documents at any time. It is not appropriate to use Internet Drafts as 21 reference material or to cite them other than as a "working draft" or 22 "work in progress." 24 Please check the I-D abstract listing contained in each Internet Draft 25 directory to learn the current status of this or any Internet Draft. 26 Distribution of this document is unlimited. 28 Copyright Notice 30 Copyright (C) The Internet Society (1998). All Rights Reserved. 32 Abstract 34 This memo defines a Management Information Base (MIB) for performing 35 remote operations (ping, traceroute and DNS Lookup) at a remote host. 36 When managing a network it is useful to be able to retrieve the results 37 of either a ping or traceroute operation when performed at a remote 38 host. A DNS Lookup capability is defined to determine the DNS of an 39 address at a remote host. 41 Currently, there exists several enterprise defined MIBs for performing 42 both a remote ping or traceroute operation. The purpose of this memo is 43 to defined a standards-based solution to enable interoperibility. 45 Table of Contents 47 1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 48 2.0 The SNMP Network Management Framework . . . . . . . . . . . . 3 50 3.0 Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 4 52 4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 6 54 5.0 Security Considerations . . . . . . . . . . . . . . . . . . . 26 56 6.0 Intellectual Property . . . . . . . . . . . . . . . . . . . . 26 58 7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 27 60 8.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . 27 62 9.0 Author's Address . . . . . . . . . . . . . . . . . . . . . . . 28 64 10.0 Full Copyright Statement . . . . . . . . . . . . . . . . . . 28 66 1.0 Introduction 68 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 69 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 70 document are to be interpreted as described in RFC 2119, reference [13]. 72 This document is a product of the Distributed Management (DISMAN) 73 Working Group. Its purpose is to define a standards-based MIB module 74 for performing remote operations. The remote operations consist of the 75 ping, traceroute and DNS Lookup functions. 77 Ping and traceroute are two very useful functions for managing networks. 78 Ping is typically used to determine if a path exists between two hosts 79 while traceroute shows an actual path. Ping is usually implemented 80 using the InterNet Control Message Protocol (ICMP) "ECHO" facility. It 81 is also possible to implement a ping capability using alternate methods. 82 For example, if the udp echo port (7) is supported at a target host it 83 could be used instead of the ICMP echo facility. 85 Traceroute is usually implemented by transmitting a series of probe 86 packets with increasing time-to-live values. A probe packet is a UDP 87 datagram encapsulated into an IP packet. Each hop in a path to the 88 target (destination) host rejects the probe packets (probe's TTL too 89 small) until its time-to-live value becomes large enough for the probe 90 to be forwarded. Some systems use icmp probes instead of udp ones to 91 implement traceroute. In both cases traceroute relies on the probes 92 being rejected via an ICMP message to discover the hops taken along a 93 path to the final destination. 95 The actually method chosen to implement either the ping or traceroute 96 functions at a remote host is considered to be implementation dependent. 97 An agent implementation SHOULD use whatever method is thought to be best 98 for its environment and document its behavior in its agent's capability 99 statement when referring to the REMOPS-MIB. 101 Both ping and traceroute yield the round-trip times measured in 102 milliseconds. These times can be used as an rough approximation for 103 network transit time. 105 The DNS Lookup operation enables the equivalent of either a 106 gethostbyname or a gethostbyaddr call being performed at a remote host. 107 The traceroute function as provided by REMOP-MIB does not provide the 108 DNS names of the intermediate hops. The DNS Lookup gethostbyname 109 capability can be used to determine the symbolic name of a hop in a 110 traceroute path. Neither the remote ping or traceroute operations 111 accept a DNS name as the address of the target host. The DNS Lookup 112 function gethostbyaddr can be used prior to using a remote ping or 113 traceroute operation in order to determine the numeric address of a 114 host. 116 Consider the following diagram: 118 +----------------------------------------------------------------------+ 119 | | 120 | Remote ping, traceroute, Actual ping, traceroute, | 121 | +-----+or DNS Lookup op.+------+or DNS Lookup op.+------+ | 122 | �Local�---------------->�Remote�---------------->�Target� | 123 | � Host� � Host � � Host � | 124 | +-----+ +------+ +------+ | 125 | | 126 | | 127 +----------------------------------------------------------------------+ 129 A local host is the host from which the remote ping, traceroute, or DNS 130 Lookup operation is initiated from using an SNMP request. The remote 131 host is a host where the MIB defined by this memo (REMOPS-MIB) is 132 implemented that receives the remote operation via SNMP and performs the 133 actual ping, traceroute, or DNS lookup function to the target 134 (destination) host. 136 2.0 The SNMP Network Management Framework 138 The SNMP Management Framework presently consists of five major 139 components: 141 o An overall architecture, described in RFC 2271 [7]. 143 o Mechanisms for describing and naming objects and events for the 144 purpose of management. The first version of this Structure of 145 Management Information (SMI) is called SMIv1 and described in RFC 146 1155 [14], RFC 1212 [15] and RFC 1215 [16]. The second version, 147 called SMIv2, is described in RFC 1902 [3], RFC 1903 [4] and RFC 148 1904 [5]. 150 o Message protocols for transferring management information. The 151 first version of the SNMP message protocol is called SNMPv1 and 152 described in RFC 1157 [1]. A second version of the SNMP message 153 protocol, which is not an Internet standards track protocol, is 154 called SNMPv2c and described in RFC 1901 [17] and RFC 1906 [18]. 155 The third version of the message protocol is called SNMPv3 and 156 described in RFC 1906 [18], RFC 2272 [8] and RFC 2274 [10]. 158 o Protocol operations for accessing management information. The first 159 set of protocol operations and associated PDU formats is described 160 in RFC 1157 [1]. A second set of protocol operations and associated 161 PDU formats is described in RFC 1905 [6]. 163 o A set of fundamental applications described in RFC 2273 [9] and the 164 view-based access control mechanism described in RFC 2275 [11]. 166 Managed objects are accessed via a virtual information store, termed the 167 Management Information Base or MIB. Objects in the MIB are defined 168 ore, using the mechanisms defined in the SMI. 170 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 171 conforming to the SMIv1 can be produced through the appropriate 172 translations. The resulting translated MIB must be semantically 173 equivalent, except where objects or events are omitted because no 174 translation is possible (use of Counter64). Some machine readable 175 information in SMIv2 will be converted into textual descriptions in 176 SMIv1 during the translation process. However, this loss of machine 177 readable information is not considered to change the semantics of the 178 MIB. 180 3.0 Structure of the MIB 182 The REMOPS-MIB consists of the following components: 184 o remopsSpinLock, remopsPingMaxConcurrentRequests, 185 remopsTraceRouteMaxConcurrentRequests, 186 remopsDnsLookupMaxConcurrentRequests, remopsPingPurgeTime, 187 remopsTraceRoutePurgeTime, and remopsDnsLookupPurgeTime 189 o remopsPingTable and remopsPingResultsTable 191 o remopsTraceRouteTable and remopsTraceRouteResultsTable 193 o remopsDnsLookupTable 195 An agent MUST implement the remopsSpinLock object to enable management 196 applications to coordinate their use of the REMOPS-MIB. Management 197 application use of remopsSpinLock is OPTIONAL. 199 The objects remopsPingMaxConcurrentRequests, 200 remopsTraceRouteMaxConcurrentRequests, and 201 remopsDnsLookupMaxConcurrentRequests enable control of the maximum 202 number of concurrent requests that an agent implementation is structured 203 to support. It is permissible for an agent to either limit the maximum 204 upper range allowed for these objects or to implement these objects as 205 read-only with implementation limits expressed as their values. 207 The objects remopsPingPurgeTime, remopsTraceRoutePurgeTime, and 208 remopsDnsLookupPurgeTime provide a method for entries in either 209 remopsPingTable and remopsPingResultsTable; remopsTraceRouteTable and 210 remopsTraceRouteResultsTable; or remopsDnsLookupTable to be 211 automatically deleted after operations complete. 213 A remote ping, traceroute or DNS Lookup operation is initiated by 214 performing an SNMP SET request on either remopsPingRowStatus, 215 remopsTraceRouteRowStatus, or remopsDnsLookupRowStatus.. The first 216 index (either remopsPingOwnerIndex, remopsTraceRouteOwnerIndex, or 217 remopsDnsLookupOwnerIndex) is of the SnmpAdminString textual convention 218 that allows for use of the SNMPv3 VACM security model and also allows 219 for a management application to identify its entries in either table. 221 Remote ping and traceroute have a 2nd index that specifies the target 222 address (ipv4 or ipv6) for the operation. DNS Lookup has two indexes. 223 First, a RemopsDnsAddressType value that indicates the type of address 224 being used: dnsName(1), ipv4(2), or ipv6(4). The last index is an 225 RemopsDnsAddress value to specify the actual address. 227 Remote ping, traceroute, and DNS Lookup require that an entry be created 228 and activated in either remopsPingTable, remopsTraceRouteTable, or 229 remopsDnsLookupTable. 231 Using the maximum value for the parameters defined within an 232 remopsPingEntry can result in a remote ping operation taking at most 15 233 minutes (remopsPingTimeOut times remopsPingProbeCount) plus whatever 234 time it takes to send the ping request and receive its response over the 235 network. Use of the defaults for remopsPingTimeOut and remopsProbeCount 236 yields a maximum of 3 seconds to perform the actual ping operation. The 237 object remopsPingOperStatus can be polled to determine when a ping 238 operation completes prior to retrieve the results of the operation from 239 the remopsPingResultsTable. 241 Traceroute has a much longer theoretical maximum time for completion. 242 Basically 42 hours and 30 minutes (the product of 243 remopsTraceRouteTimeOut, remopsTraceRouteProbesPerHop, and 244 remopsTraceRouteMaxTtl) plus some network transit time! Use of the 245 defaults defined within an remopsTraceRouteEntry yields a maximum of 4 246 minutes and 30 seconds for a default traceroute operation. Clearly 42 247 plus hours is too long to wait for a traceroute operation to complete. 249 The maximum TTL value in effect for traceroute route determines how long 250 the traceroute function will keep increasing the TTL value in the probe 251 it transmits hoping to reach the target host. The function ends 252 whenever the maximum TTL is exceeded or the target host is reached. The 253 object remopsTraceRouteSetupMaxFailures was created in order to impose a 254 throttle for how long traceroute continues to increase the TTL field in 255 a probe without receiving any kind of response (timeouts). It is 256 RECOMMENDED that agent implementations impose a time limit for how long 257 it allows a traceroute operation to take relative to how the function is 258 implemented. For example, an implemented that can't process multiple 259 traceroute operations at the same time SHOULD impose a shorter maximum 260 allowed time period. The object remopsTraceRouteOperStatus can be 261 examined to determine the state of a traceroute operation. The objects 262 remopsTraceRouteResultsHopIndex and remopsTraceRouteResultsProbeIndex 263 can be exaimed to determine how far the remote traceroute operation has 264 reached. 266 A management application can delete a active remote ping traceroute, or 267 DNS Lookup request by setting its remopsPingRowStatus, 268 remopsTraceRouteRowStatus, or remopsDnsLookupRowStatis object to 269 destroy(6). 271 An implementation SHOULD NOT retain SNMP-created entries in either the 272 remopsPingTable, remopsTraceRouteTable or remopsDnsLookupTable across 273 reIPLs (Initial Program Loads) of its agent, since management 274 applications need to see consistent behavior with respect to the 275 persistence of the table entries that they create. 277 4.0 Definitions 279 REMOPS-MIB DEFINITIONS ::= BEGIN 281 IMPORTS 282 MODULE-IDENTITY, OBJECT-TYPE, Integer32, 283 experimental, Unsigned32 284 FROM SNMPv2-SMI -- RFC1902 285 TEXTUAL-CONVENTION, RowStatus, 286 TestAndIncr, TruthValue 287 FROM SNMPv2-TC -- RFC1903 288 MODULE-COMPLIANCE, OBJECT-GROUP 289 FROM SNMPv2-CONF -- RFC1904 290 Utf8String 291 FROM SYSAPPL-MIB -- RFC2287 292 SnmpAdminString 293 FROM SNMP-FRAMEWORK-MIB; -- RFC2271 295 remopsMIB MODULE-IDENTITY 296 LAST-UPDATED "9809010000Z" 297 ORGANIZATION "IETF Distributed Management Working Group" 298 CONTACT-INFO 299 "Kenneth White 301 International Business Machines Corporation 302 Network Computing Software Division 303 Research Triangle Park, NC, USA 305 E-mail: kennethw@vnet.ibm.com" 306 DESCRIPTION 307 "The Remote Operations MIB (REMOPS-MIB) enables use 308 of the ping, traceroute, and the DNS Lookup functions, 309 gethostbyname and gethostbyaddr, via use of the SNMP 310 protocol." 311 ::= { experimental 84 } 313 -- Textual Conventions 314 RemopsHostAddress ::= TEXTUAL-CONVENTION 315 STATUS current 316 DESCRIPTION 317 "The textual convention for specifying a host 318 address. The type of address can be determined 319 by the octet string length: 321 OCTETs ADDRESS TYPE 322 0 not specified 323 4 ipv4 324 16 ipv6" 325 SYNTAX OCTET STRING (SIZE (0..16)) 327 RemopsDnsAddressType ::= TEXTUAL-CONVENTION 328 STATUS current 329 DESCRIPTION 330 "The textual convention for defining the type of 331 an address for a DNS Lookup operation." 332 SYNTAX INTEGER { 333 none(1), 334 dnsName(2), -- Utf8string encoded DNS name 335 ipv4(3), -- ipv4 address 336 ipv6(4) -- ipv6 address 337 } 339 RemopsDnsAddress ::= TEXTUAL-CONVENTION 340 STATUS current 341 DESCRIPTION 342 "The textual convention for specifying a host 343 address. The type of address is determined by 344 the corresponding RemopsDnsAddressType object." 345 SYNTAX OCTET STRING (SIZE (0..65)) 347 RemopsStatus ::= TEXTUAL-CONVENTION 348 STATUS current 349 DESCRIPTION 350 "The textual convention for specifying the states that 351 a remops operation can be in." 352 SYNTAX INTEGER { 353 notStarted(1), 354 active(2), 355 completed(3) 356 } 358 -- Top-level structure of the MIB 360 remopsNotifications OBJECT IDENTIFIER ::= { remopsMIB 0 } 361 remopsObjects OBJECT IDENTIFIER ::= { remopsMIB 1 } 362 remopsConformance OBJECT IDENTIFIER ::= { remopsMIB 2 } 364 -- All simple objects 365 remopsBaseObjects OBJECT IDENTIFIER ::= { remopsObjects 1 } 367 -- SpinLock Definition 369 remopsSpinLock OBJECT-TYPE 370 SYNTAX TestAndIncr 371 MAX-ACCESS read-write 372 STATUS current 373 DESCRIPTION 374 "An advisory lock used to allow cooperating 375 remops applications to coordinate their 376 use of the remopsPingTable or the remopsTraceRouteTable. 378 This object should be used when an application seeks to create 379 an new entry or alter an existing entry in either the 380 remopsPingTable, remopsTraceRouteTable, or 381 remopsDnsLookupTable. A management implementation MAY utilize 382 the remopsSpinLock to serialize its changes or additions. 383 Its usage is NOT REQUIRED." 384 ::= { remopsBaseObjects 1 } 386 remopsPingMaxConcurrentRequests OBJECT-TYPE 387 SYNTAX Unsigned32 (1..100) 388 MAX-ACCESS read-write 389 STATUS current 390 DESCRIPTION 391 "The maximum number of concurrent active ping requests 392 that are allowed within an agent implementation." 393 DEFVAL { 10 } 394 ::= { remopsBaseObjects 2 } 396 remopsTraceRouteMaxConcurrentRequests OBJECT-TYPE 397 SYNTAX Unsigned32 (1..100) 398 MAX-ACCESS read-write 399 STATUS current 400 DESCRIPTION 401 "The maximum number of concurrent active traceroute requests 402 that are allowed within an agent implementation." 403 DEFVAL { 10 } 404 ::= { remopsBaseObjects 3 } 406 remopsDnsLookupMaxConcurrentRequests OBJECT-TYPE 407 SYNTAX Unsigned32 (1..100) 408 MAX-ACCESS read-write 409 STATUS current 410 DESCRIPTION 411 "The maximum number of concurrent active DNS Lookup requests 412 that are allowed within an agent implementation." 413 DEFVAL { 10 } 414 ::= { remopsBaseObjects 4 } 416 remopsPingPurgeTime OBJECT-TYPE 417 SYNTAX Unsigned32 (0..86400) 418 UNITS "seconds" 419 MAX-ACCESS read-write 420 STATUS current 421 DESCRIPTION 422 "The amount of time to wait before automatically 423 deleting an entry in remopsPingTable and all 424 remopsPingResultsTable entries after 425 the ping operation represented by an entry 426 in the remopsPingTable has completed." 427 DEFVAL { 900 } -- 15 minutes as default 428 ::= { remopsBaseObjects 5 } 430 remopsTraceRoutePurgeTime OBJECT-TYPE 431 SYNTAX Unsigned32 (0..86400) 432 UNITS "seconds" 433 MAX-ACCESS read-write 434 STATUS current 435 DESCRIPTION 436 "The amount of time to wait before automatically 437 deleting an entry in remopsTraceRouteTable and all 438 dependent remopsTraceRouteResultsTable entries after 439 the traceroute operation represented by an 440 remopsTraceRouteEntry has completed." 441 DEFVAL { 900 } -- 15 minutes as default 442 ::= { remopsBaseObjects 6 } 444 remopsDnsLookupPurgeTime OBJECT-TYPE 445 SYNTAX Unsigned32 (0..86400) 446 UNITS "seconds" 447 MAX-ACCESS read-write 448 STATUS current 449 DESCRIPTION 450 "The amount of time to wait before automatically 451 deleting an entry in the remopsDnsLookupTable 452 after the DNS Lookup operation represented by an 453 remopsDnsLookupEntry has completed." 454 DEFVAL { 900 } -- 15 minutes as default 455 ::= { remopsBaseObjects 7 } 457 -- Remote Operations Ping Table 459 remopsPingTable OBJECT-TYPE 460 SYNTAX SEQUENCE OF RemopsPingEntry 461 MAX-ACCESS not-accessible 462 STATUS current 463 DESCRIPTION 464 "Defines the Remote Operations Ping Table for provide 465 via SNMP the capability of invoking ping from a remote 466 host." 467 ::= { remopsObjects 2 } 469 remopsPingEntry OBJECT-TYPE 470 SYNTAX RemopsPingEntry 471 MAX-ACCESS not-accessible 472 STATUS current 473 DESCRIPTION 474 "Defines an entry in the remopsPingTable." 475 INDEX { 476 remopsPingOwnerIndex, 477 remopsPingHostAddress 478 } 479 ::= { remopsPingTable 1 } 481 RemopsPingEntry ::= 482 SEQUENCE { 483 remopsPingOwnerIndex SnmpAdminString, 484 remopsPingHostAddress RemopsHostAddress, 485 remopsPingPacketSize Unsigned32, 486 remopsPingTimeOut Unsigned32, 487 remopsPingProbeCount Unsigned32, 488 remopsPingOperStatus RemopsStatus, 489 remopsPingRowStatus RowStatus 490 } 492 remopsPingOwnerIndex OBJECT-TYPE 493 SYNTAX SnmpAdminString (SIZE(0..32)) 494 MAX-ACCESS not-accessible 495 STATUS current 496 DESCRIPTION 497 "To facilitate the provisioning of access control by a security 498 administrator using the View-Based Access Control Model (RFC 2275, 499 VACM) for tables in which multiple users may need to independently 500 create or modify entries, the initial index is used as an 'owner 501 index'. Such an initial index has a syntax of SnmpAdminString, 502 and can thus be trivially mapped to a securityName or groupName 503 as defined in VACM, in accordance with a security policy. 505 All entries in that table belonging to a particular user will 506 have the same value for this initial index. For a given user's 507 entries in a particular table, the object identifiers for the 508 information in these entries will have the same subidentifiers 509 (except for the 'column' subidentifier) up to the end of the 510 encoded owner index. To configure VACM to permit access to this 511 portion of the table, one would create vacmViewTreeFamilyTable 512 entries with the value of vacmViewTreeFamilySubtree including the 513 owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the 514 column subidentifier. More elaborate configurations are possible." 515 ::= { remopsPingEntry 1 } 517 remopsPingHostAddress OBJECT-TYPE 518 SYNTAX RemopsHostAddress 519 MAX-ACCESS not-accessible 520 STATUS current 521 DESCRIPTION 522 "Specifies the host address used on by ping request by 523 the remote host. The host address type can be determined 524 by its octet string length." 525 ::= { remopsPingEntry 2 } 527 remopsPingPacketSize OBJECT-TYPE 528 SYNTAX Unsigned32 (0..65507) 529 UNITS "octets" 530 MAX-ACCESS read-create 531 STATUS current 532 DESCRIPTION 533 "Specifies the size of the data portion to be 534 transmitted in a ping request in octets. A ping 535 request is usually an ICMP message encoded 536 into an IP packet. An IP packet has a maximum size 537 of 65535 octets. Subtracting the size of the ICMP 538 header (8 octets) and the size of the IP header 539 (20 octets) yields a maximum size of 65507 octets." 540 DEFVAL { 0 } 541 ::= { remopsPingEntry 3 } 543 remopsPingTimeOut OBJECT-TYPE 544 SYNTAX Unsigned32 (1..60) 545 UNITS "seconds" 546 MAX-ACCESS read-create 547 STATUS current 548 DESCRIPTION 549 "Specifies the time-out value, in seconds, for the actual 550 PING request made by the remote host. Valid values for 551 time out are from 1 to 60 seconds." 552 DEFVAL { 3 } 553 ::= { remopsPingEntry 4 } 555 remopsPingProbeCount OBJECT-TYPE 556 SYNTAX Unsigned32 (1..15) 557 MAX-ACCESS read-create 558 STATUS current 559 DESCRIPTION 560 "Specifies the number of times to issue a ping 561 request at a remote host." 562 DEFVAL { 1 } 563 ::= { remopsPingEntry 5 } 565 remopsPingOperStatus OBJECT-TYPE 566 SYNTAX RemopsStatus 567 MAX-ACCESS read-only 568 STATUS current 569 DESCRIPTION 570 "Reflects the operational state of a remote 571 ping operation." 572 ::= { remopsPingEntry 6 } 574 remopsPingRowStatus OBJECT-TYPE 575 SYNTAX RowStatus 576 MAX-ACCESS read-create 577 STATUS current 578 DESCRIPTION 579 "This object allows entries to be created and deleted 580 in the remopsPingTable. Deletion of an entry in this 581 table results in all remopsPingResultsTable entries 582 being deleted. 584 A remote ping operation is started when an 585 entry in this table is created via an SNMP SET 586 request and the entry is activated. This 587 can occur by setting the value of this object 588 to CreateAndGo(4) during row creation or 589 by setting this object to active(1) after 590 the row is created. 592 A remote ping request starts when its entry 593 first becomes active(1). Transitions in and 594 out of active(1) state have no effect on the 595 operational behavior of a remote ping 596 operation, with the exception that deletion of 597 an entry in this table by setting its RowStatus 598 object to destroy(6) will stop an active 599 remote ping operation. 601 The operational state of an remote ping operation 602 can be determined by examination of it's 603 remopsPingOperStatus object." 604 REFERENCE 605 "RFC 1903, 'Textual Conventions for version 2 of the 606 Simple Network Management Protocol (SNMPv2).'" 607 ::= { remopsPingEntry 7 } 609 -- Remote Operations Ping Results Table 611 remopsPingResultsTable OBJECT-TYPE 612 SYNTAX SEQUENCE OF RemopsPingResultsEntry 613 MAX-ACCESS not-accessible 614 STATUS current 615 DESCRIPTION 616 "Defines the Remote Operations Result Ping Table for 617 storing the results of a ping operation." 618 ::= { remopsObjects 3 } 620 remopsPingResultsEntry OBJECT-TYPE 621 SYNTAX RemopsPingResultsEntry 622 MAX-ACCESS not-accessible 623 STATUS current 624 DESCRIPTION 625 "Defines an entry in the remopsPingResultsTable." 626 INDEX { 627 remopsPingOwnerIndex, 628 remopsPingHostAddress, 629 remopsPingResultsProbeIndex 630 } 631 ::= { remopsPingResultsTable 1 } 633 RemopsPingResultsEntry ::= 634 SEQUENCE { 635 remopsPingResultsProbeIndex Unsigned32, 636 remopsPingResultsResponse Integer32 637 } 639 remopsPingResultsProbeIndex OBJECT-TYPE 640 SYNTAX Unsigned32 (1..15) 641 MAX-ACCESS not-accessible 642 STATUS current 643 DESCRIPTION 644 "An entry in this table is created when the results of 645 a ping probe is determined. The initial instance 646 identifier value identifies the remopsPingEntry 647 that a probe result (remopsPingResultsEntry) belongs 648 to." 649 ::= { remopsPingResultsEntry 1 } 651 remopsPingResultsResponse OBJECT-TYPE 652 SYNTAX Integer32 653 MAX-ACCESS read-only 654 STATUS current 655 DESCRIPTION 656 "The result of the ping operation made by a remote host 657 for a particular probe. The results of the probe is 658 indicated as the value of this object as follows: 660 >=0 Round-trip response time in milliseconds. 661 -1 Internal error. 662 -2 ICMP echo request timed out. 663 -3 Unknown destination address. 664 -4 No route to host. 665 -5 Interface inactive to host. 666 -6 Failed to resolve host name. 667 -7 remopsPingMaxConcurrentRequests limit reached." 668 ::= { remopsPingResultsEntry 2 } 670 -- Remote Operations Traceroute Table 672 remopsTraceRouteTable OBJECT-TYPE 673 SYNTAX SEQUENCE OF RemopsTraceRouteEntry 674 MAX-ACCESS not-accessible 675 STATUS current 676 DESCRIPTION 677 "Defines the Remote Operations Traceroute Table for provide 678 via SNMP the capability of invoking traceroute 679 from a remote host." 680 ::= { remopsObjects 4 } 682 remopsTraceRouteEntry OBJECT-TYPE 683 SYNTAX RemopsTraceRouteEntry 684 MAX-ACCESS not-accessible 685 STATUS current 686 DESCRIPTION 687 "Defines an entry in the remopsTraceRouteTable." 688 INDEX { 689 remopsTraceRouteOwnerIndex, 690 remopsTraceRouteHostAddress 691 } 692 ::= { remopsTraceRouteTable 1 } 694 RemopsTraceRouteEntry ::= 695 SEQUENCE { 696 remopsTraceRouteOwnerIndex SnmpAdminString, 697 remopsTraceRouteHostAddress RemopsHostAddress, 698 remopsTraceRouteByPassRouteTable TruthValue, 699 remopsTraceRoutePacketSize Unsigned32, 700 remopsTraceRouteTimeOut Unsigned32, 701 remopsTraceRouteProbesPerHop Unsigned32, 702 remopsTraceRoutePort Unsigned32, 703 remopsTraceRouteMaxTtl Unsigned32, 704 remopsTraceRouteTos Unsigned32, 705 remopsTraceRouteSourceAddress RemopsHostAddress, 706 remopsTraceRouteInterfaceName OCTET STRING, 707 remopsTraceRouteMiscOptions Utf8String, 708 remopsTraceRouteMaxFailures Unsigned32, 709 remopsTraceRouteOperStatus RemopsStatus, 710 remopsTraceRouteCurHopCount Unsigned32, 711 remopsTraceRouteCurProbeCount Unsigned32, 712 remopsTraceRouteRowStatus RowStatus 713 } 715 remopsTraceRouteOwnerIndex OBJECT-TYPE 716 SYNTAX SnmpAdminString (SIZE(0..32)) 717 MAX-ACCESS not-accessible 718 STATUS current 719 DESCRIPTION 720 "To facilitate the provisioning of access control by a security 721 administrator using the View-Based Access Control Model (RFC 2275, 722 VACM) for tables in which multiple users may need to independently 723 create or modify entries, the initial index is used as an 'owner 724 index'. Such an initial index has a syntax of SnmpAdminString, 725 and can thus be trivially mapped to a securityName or groupName 726 as defined in VACM, in accordance with a security policy. 728 All entries in this table belonging to a particular user will 729 have the same value for this initial index. For a given user's 730 entries in a particular table, the object identifiers for the 731 information in these entries will have the same subidentifiers 732 (except for the 'column' subidentifier) up to the end of the 733 encoded owner index. To configure VACM to permit access to this 734 portion of the table, one would create vacmViewTreeFamilyTable 735 entries with the value of vacmViewTreeFamilySubtree including the 736 owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the 737 column subidentifier. More elaborate configurations are possible." 738 ::= { remopsTraceRouteEntry 1 } 740 remopsTraceRouteHostAddress OBJECT-TYPE 741 SYNTAX RemopsHostAddress 742 MAX-ACCESS not-accessible 743 STATUS current 744 DESCRIPTION 745 "Specifies the host address used on the 746 traceroute request at the remote host. The 747 host address type can be determined by the 748 length of the corresponding octet string." 749 ::= { remopsTraceRouteEntry 2 } 751 remopsTraceRouteByPassRouteTable OBJECT-TYPE 752 SYNTAX TruthValue 753 MAX-ACCESS read-create 754 STATUS current 755 DESCRIPTION 756 "The purpose of this object is optionally enable 757 bypassing the route table. If enabled bypass the 758 normal routing tables and send directly to a 759 host on an attached network. If the host 760 is not on a directly-attached network, an 761 error is returned. This option can be 762 used to ping a local host through an 763 interface that has no route through it 764 (e.g., after the interface was dropped by 765 routed)." 766 DEFVAL { false } 767 ::= { remopsTraceRouteEntry 3 } 769 remopsTraceRoutePacketSize OBJECT-TYPE 770 SYNTAX Unsigned32 (0..65507) 771 UNITS "octets" 772 MAX-ACCESS read-create 773 STATUS current 774 DESCRIPTION 775 "Specifies the size of the data portion of a traceroute 776 request in octets. A traceroute request is essentially 777 transmitted by encoding a UDP datagram into a 778 IP packet. So subtracting the size of a UDP header 779 (8 octets) and the size of a IP header (20 octets) 780 yields a maximum of 65507 octets." 781 DEFVAL { 0 } 782 ::= { remopsTraceRouteEntry 4 } 784 remopsTraceRouteTimeOut OBJECT-TYPE 785 SYNTAX Unsigned32 (1..60) 786 UNITS "seconds" 787 MAX-ACCESS read-create 788 STATUS current 789 DESCRIPTION 790 "Specifies the time-out value, in seconds, for 791 a traceroute request." 792 DEFVAL { 3 } 793 ::= { remopsTraceRouteEntry 5 } 795 remopsTraceRouteProbesPerHop OBJECT-TYPE 796 SYNTAX Unsigned32 (1..10) 797 UNITS "count" 798 MAX-ACCESS read-create 799 STATUS current 800 DESCRIPTION 801 "Specifies the number of times to reissue a traceroute 802 request with the same time-to-live (TTL) value." 803 DEFVAL { 3 } 804 ::= { remopsTraceRouteEntry 6 } 806 remopsTraceRoutePort OBJECT-TYPE 807 SYNTAX Unsigned32 (1..65535) 808 UNITS "UDP Port" 809 MAX-ACCESS read-create 810 STATUS current 811 DESCRIPTION 812 "Specifies the UDP port to sent the traceroute 813 request to. Need to specify a port that is not in 814 use at the destination host." 815 DEFVAL { 4096 } 816 ::= { remopsTraceRouteEntry 7 } 818 remopsTraceRouteMaxTtl OBJECT-TYPE 819 SYNTAX Unsigned32 (1..255) 820 UNITS "time-to-live maximum" 821 MAX-ACCESS read-create 822 STATUS current 823 DESCRIPTION 824 "Specifies the maximum time-to-live value." 825 DEFVAL { 30 } 826 ::= { remopsTraceRouteEntry 8 } 828 remopsTraceRouteTos OBJECT-TYPE 829 SYNTAX Unsigned32 (0..255) 830 MAX-ACCESS read-create 831 STATUS current 832 DESCRIPTION 833 "Specifies the value to store in the TOS OCTET in 834 the IP probe packet that is transmitted as the 835 traceroute request. The value must be a decimal 836 integer in the range 0 to 255. This option can be 837 used to see if different types-of-service result 838 in different paths. Not all values of TOS are 839 legal or meaningful. TOS is often not supported 840 by IP implementations. Useful values are probably 841 '16' (low delay) and '8' (high throughput)." 842 DEFVAL { 0 } 843 ::= { remopsTraceRouteEntry 9 } 845 remopsTraceRouteSourceAddress OBJECT-TYPE 846 SYNTAX RemopsHostAddress 847 MAX-ACCESS read-create 848 STATUS current 849 DESCRIPTION 850 "Use the specified IP address 851 (which must be given as an IP number, not a hostname) 852 as the source address in outgoing probe packets. On 853 hosts with more than one IP address, this option can 854 be used to force the source address to be something 855 other than the IP address of the interface the probe 856 packet is sent on. If the IP address is not one of this 857 machine's interface addresses, an error is returned and 858 nothing is sent." 859 DEFVAL { ''H } 860 ::= { remopsTraceRouteEntry 10 } 862 remopsTraceRouteInterfaceName OBJECT-TYPE 863 SYNTAX OCTET STRING (SIZE(0..32)) 864 MAX-ACCESS read-create 865 STATUS current 866 DESCRIPTION 867 "Setting this object to an interface's name prior 868 to starting a remote traceroute operation directs 869 the traceroute probes to be transmitted over the 870 specified interface." 871 DEFVAL { ''H } 872 ::= { remopsTraceRouteEntry 11 } 874 remopsTraceRouteMiscOptions OBJECT-TYPE 875 SYNTAX Utf8String (SIZE(0..64)) 876 MAX-ACCESS read-create 877 STATUS current 878 DESCRIPTION 879 "Enables an application to specify implementation 880 dependent options." 881 DEFVAL { ''H } 882 ::= { remopsTraceRouteEntry 12 } 884 remopsTraceRouteMaxFailures OBJECT-TYPE 885 SYNTAX Unsigned32 (1..255) 886 MAX-ACCESS read-create 887 STATUS current 888 DESCRIPTION 889 "The value of this object indicates the maximum number 890 of consecutive timeouts allowed before terminating 891 a remote traceroute request. A value of 255 (maximum 892 hop count) indicate that the function of terminating 893 a remote traceroute request when a number of successive 894 timeouts are detected is disabled." 895 DEFVAL { 5 } 896 ::= { remopsTraceRouteEntry 13 } 898 remopsTraceRouteOperStatus OBJECT-TYPE 899 SYNTAX RemopsStatus 900 MAX-ACCESS read-only 901 STATUS current 902 DESCRIPTION 903 "Reflects the operational state of a remote 904 traceroute operation." 906 ::= { remopsTraceRouteEntry 14 } 908 remopsTraceRouteCurHopCount OBJECT-TYPE 909 SYNTAX Unsigned32 (1..255) 910 MAX-ACCESS read-only 911 STATUS current 912 DESCRIPTION 913 "Reflects the current TTL value for an remote 914 traceroute operation. Maximum TTL value is 915 determined by remopsTraceRouteMaxTtl." 916 ::= { remopsTraceRouteEntry 15 } 918 remopsTraceRouteCurProbeCount OBJECT-TYPE 919 SYNTAX Unsigned32 (1..10) 920 MAX-ACCESS read-only 921 STATUS current 922 DESCRIPTION 923 "Reflects the current probe count for an remote 924 traceroute operation. The maximum probe count 925 is determined by remopsTraceRouteProbesPerHop." 926 ::= { remopsTraceRouteEntry 16 } 928 remopsTraceRouteRowStatus OBJECT-TYPE 929 SYNTAX RowStatus 930 MAX-ACCESS read-create 931 STATUS current 932 DESCRIPTION 933 "This object allows entries to be created and deleted 934 in the remopsTraceRouteTable. 936 A remote traceroute operation is started when an 937 entry in this table is created via an SNMP SET 938 request and the entry is activated. This 939 can occur by setting the value of this object 940 to CreateAndGo(4) during row creation or 941 by setting this object to active(1) after 942 the row is created. 944 A remote traceroute request starts when its entry 945 first becomes active(1). Transitions in and 946 out of active(1) state have no effect on the 947 operational behavior of a remote traceroute 948 operation, with the exception that deletion of 949 an entry in this table by setting its RowStatus 950 object to destroy(6) will stop an active 951 remote traceroute operation." 952 REFERENCE 953 "RFC 1903, 'Textual Conventions for version 2 of the 954 Simple Network Management Protocol (SNMPv2).'" 955 ::= { remopsTraceRouteEntry 17 } 957 -- Remote Operations Traceroute Results Table 959 remopsTraceRouteResultsTable OBJECT-TYPE 960 SYNTAX SEQUENCE OF RemopsTraceRouteResultsEntry 961 MAX-ACCESS not-accessible 962 STATUS current 963 DESCRIPTION 964 "Defines the Remote Operations Traceroute Results Table for 965 storing the results of a traceroute operation." 966 ::= { remopsObjects 5 } 968 remopsTraceRouteResultsEntry OBJECT-TYPE 969 SYNTAX RemopsTraceRouteResultsEntry 970 MAX-ACCESS not-accessible 971 STATUS current 972 DESCRIPTION 973 "Defines an entry in the remopsTraceRouteResultsTable." 974 INDEX { 975 remopsTraceRouteOwnerIndex, 976 remopsTraceRouteHostAddress, 977 remopsTraceRouteResultsHopIndex, 978 remopsTraceRouteResultsProbeIndex 979 } 980 ::= { remopsTraceRouteResultsTable 1 } 982 RemopsTraceRouteResultsEntry ::= 983 SEQUENCE { 984 remopsTraceRouteResultsHopIndex Unsigned32, 985 remopsTraceRouteResultsProbeIndex Unsigned32, 986 remopsTraceRouteResultsHopAddress RemopsHostAddress, 987 remopsTraceRouteResultsResponse Integer32 988 } 990 remopsTraceRouteResultsHopIndex OBJECT-TYPE 991 SYNTAX Unsigned32 (1..255) 992 MAX-ACCESS not-accessible 993 STATUS current 994 DESCRIPTION 995 "An entry in this table has as its initial instance identifier 996 the value of its corresponding remopsTraceRouteEntry's 997 instance identifier." 998 ::= { remopsTraceRouteResultsEntry 1 } 1000 remopsTraceRouteResultsProbeIndex OBJECT-TYPE 1001 SYNTAX Unsigned32 (1..10) 1002 MAX-ACCESS not-accessible 1003 STATUS current 1004 DESCRIPTION 1005 "Indicates the index of a probe for determining a 1006 hop in a traceroute path." 1007 ::= { remopsTraceRouteResultsEntry 2 } 1009 remopsTraceRouteResultsHopAddress OBJECT-TYPE 1010 SYNTAX RemopsHostAddress 1011 MAX-ACCESS read-only 1012 STATUS current 1013 DESCRIPTION 1014 "The address of a hop in a traceroute path. This object 1015 is not allowed to be a DNS name. The length of the 1016 octet string returned determines the address type." 1017 ::= { remopsTraceRouteResultsEntry 3 } 1019 remopsTraceRouteResultsResponse OBJECT-TYPE 1020 SYNTAX Integer32 1021 MAX-ACCESS read-only 1022 STATUS current 1023 DESCRIPTION 1024 "The value of this object indicated the result of a 1025 traceroute probe: 1027 >=0 Round-trip response time in milliseconds. 1028 -1 Internal error. 1029 -2 probe timed out. 1030 -3 Unknown destination address. 1031 -4 No route to host. 1032 -5 Interface inactive to host. 1033 -6 Failed to resolve host name. 1034 -7 remopsTraceRouteMaxConcurrentRequests limit reached." 1035 ::= { remopsTraceRouteResultsEntry 4 } 1037 -- Remote Operations DNS Lookup Table 1039 remopsDnsLookupTable OBJECT-TYPE 1040 SYNTAX SEQUENCE OF RemopsDnsLookupEntry 1041 MAX-ACCESS not-accessible 1042 STATUS current 1043 DESCRIPTION 1044 "Defines the Remote Operations DnsLookup Table for provide 1045 via SNMP the capability of performing a DNS Lookup, 1046 gethostbyname or gethostbyaddr, from a remote host." 1047 ::= { remopsObjects 6 } 1049 remopsDnsLookupEntry OBJECT-TYPE 1050 SYNTAX RemopsDnsLookupEntry 1051 MAX-ACCESS not-accessible 1052 STATUS current 1053 DESCRIPTION 1054 "Defines an entry in the remopsDnsLookupTable." 1055 INDEX { 1056 remopsDnsLookupOwnerIndex, 1057 remopsDnsLookupAddressType, 1058 remopsDnsLookupAddress 1059 } 1060 ::= { remopsDnsLookupTable 1 } 1062 RemopsDnsLookupEntry ::= 1063 SEQUENCE { 1064 remopsDnsLookupOwnerIndex SnmpAdminString, 1065 remopsDnsLookupAddressType RemopsDnsAddressType, 1066 remopsDnsLookupAddress RemopsDnsAddress, 1067 remopsDnsLookupTimeOut Unsigned32, 1068 remopsDnsLookupRetryLimit Unsigned32, 1069 remopsDnsLookupOperStatus RemopsStatus, 1070 remopsDnsLookupRetryCount Unsigned32, 1071 remopsDnsLookupResultType RemopsDnsAddressType, 1072 remopsDnsLookupResult RemopsDnsAddress, 1073 remopsDnsLookupRowStatus RowStatus 1074 } 1076 remopsDnsLookupOwnerIndex OBJECT-TYPE 1077 SYNTAX SnmpAdminString (SIZE(0..32)) 1078 MAX-ACCESS not-accessible 1079 STATUS current 1080 DESCRIPTION 1081 "To facilitate the provisioning of access control by a security 1082 administrator using the View-Based Access Control Model (RFC 2275, 1083 VACM) for tables in which multiple users may need to independently 1084 create or modify entries, the initial index is used as an 'owner 1085 index'. Such an initial index has a syntax of SnmpAdminString, 1086 and can thus be trivially mapped to a securityName or groupName 1087 as defined in VACM, in accordance with a security policy. 1089 All entries in that table belonging to a particular user will 1090 have the same value for this initial index. For a given user's 1091 entries in a particular table, the object identifiers for the 1092 information in these entries will have the same subidentifiers 1093 (except for the 'column' subidentifier) up to the end of the 1094 encoded owner index. To configure VACM to permit access to this 1095 portion of the table, one would create vacmViewTreeFamilyTable 1096 entries with the value of vacmViewTreeFamilySubtree including the 1097 owner index portion, and vacmViewTreeFamilyMask 'wildcarding' the 1098 column subidentifier. More elaborate configurations are possible." 1099 ::= { remopsDnsLookupEntry 1 } 1101 remopsDnsLookupAddressType OBJECT-TYPE 1102 SYNTAX RemopsDnsAddressType 1103 MAX-ACCESS not-accessible 1104 STATUS current 1105 DESCRIPTION 1106 "Specifies the type of address for either performing a 1107 gethostbyname or a gethostbyaddr call at a remote host. 1108 Specification of a dnsName(2) implies that gethostbyname 1109 should be called to return a numeric address. 1110 Use of a value of either ipv4(3) or ipv6(4) implies that 1111 a gethostbyaddr call should occur to return the symbolic 1112 name of a remote host." 1113 ::= { remopsDnsLookupEntry 2 } 1115 remopsDnsLookupAddress OBJECT-TYPE 1116 SYNTAX RemopsDnsAddress 1117 MAX-ACCESS not-accessible 1118 STATUS current 1119 DESCRIPTION 1120 "Specifies the address used for a DNS Lookup at a 1121 remote host. The corresponding remopsDnsLookupAddressType 1122 objects determines its type as well as the function 1123 that can be requested." 1124 ::= { remopsDnsLookupEntry 3 } 1126 remopsDnsLookupTimeOut OBJECT-TYPE 1127 SYNTAX Unsigned32 (1..60) 1128 UNITS "seconds" 1129 MAX-ACCESS read-create 1130 STATUS current 1131 DESCRIPTION 1132 "Specifies the time-out value, in seconds, for the DNS 1133 Lookup operation made at a remote host. Valid values 1134 for timeout are from 1 to 60 seconds." 1135 DEFVAL { 3 } 1136 ::= { remopsDnsLookupEntry 4 } 1138 remopsDnsLookupRetryLimit OBJECT-TYPE 1139 SYNTAX Unsigned32 (1..15) 1140 MAX-ACCESS read-create 1141 STATUS current 1142 DESCRIPTION 1143 "Specifies the number of times to reattempt to 1144 perform an DNS Lookup on encountering a 1145 timeout." 1146 DEFVAL { 1 } 1147 ::= { remopsDnsLookupEntry 5 } 1149 remopsDnsLookupOperStatus OBJECT-TYPE 1150 SYNTAX RemopsStatus 1151 MAX-ACCESS read-only 1152 STATUS current 1153 DESCRIPTION 1154 "Reflects the operational state of a remote 1155 DNS Lookup operation." 1156 ::= { remopsDnsLookupEntry 6 } 1158 remopsDnsLookupRetryCount OBJECT-TYPE 1159 SYNTAX Unsigned32 (1..15) 1160 MAX-ACCESS read-only 1161 STATUS current 1162 DESCRIPTION 1163 "The current retry number." 1164 ::= { remopsDnsLookupEntry 7 } 1166 remopsDnsLookupResultType OBJECT-TYPE 1167 SYNTAX RemopsDnsAddressType 1168 MAX-ACCESS read-only 1169 STATUS current 1170 DESCRIPTION 1171 "The type of address being returned. The value of this 1172 object is none(0) when either the operation hasn't 1173 completed or when the operation fails." 1174 ::= { remopsDnsLookupEntry 8 } 1176 remopsDnsLookupResult OBJECT-TYPE 1177 SYNTAX RemopsDnsAddress 1178 MAX-ACCESS read-only 1179 STATUS current 1180 DESCRIPTION 1181 "The results of a remote DNS Lookup. The value of this 1182 object is the zero length octet string when either the 1183 operation hasn't completed or when the operation fails." 1184 ::= { remopsDnsLookupEntry 9 } 1186 remopsDnsLookupRowStatus OBJECT-TYPE 1187 SYNTAX RowStatus 1188 MAX-ACCESS read-create 1189 STATUS current 1190 DESCRIPTION 1191 "This object allows entries to be created and deleted 1192 in the remopsDnsLookupTable. 1194 A remote DNS Lookup operation is started when an 1195 entry in this table is created via an SNMP SET 1196 request and the entry is activated. This 1197 can occur by setting the value of this object 1198 to CreateAndGo(4) during row creation or 1199 by setting this object to active(1) after 1200 the row is created. 1202 A remote DNS Lookup operation starts when its entry 1203 first becomes active(1). Transitions in and 1204 out of active(1) state have no effect on the 1205 operational behavior of a remote DNS Lookup 1206 operation, with the exception that deletion of 1207 an entry in this table by setting its RowStatus 1208 object to destroy(6) will stop an active 1209 remote DNS Lookup operation. 1211 The operational state of a remote DNS Lookup operation 1212 can be determined by examination of it's 1213 remopsDnsLookupOperStatus object." 1214 REFERENCE 1215 "RFC 1903, 'Textual Conventions for version 2 of the 1216 Simple Network Management Protocol (SNMPv2).'" 1217 ::= { remopsDnsLookupEntry 10 } 1219 --------------------------------------------------------------------- 1220 -- Conformance information 1221 -- Compliance statements 1222 --------------------------------------------------------------------- 1224 remopsCompliances OBJECT IDENTIFIER ::= { remopsConformance 1 } 1225 remopsGroups OBJECT IDENTIFIER ::= { remopsConformance 2 } 1227 --------------------------------------------------------------------- 1228 -- Compliance statements 1229 --------------------------------------------------------------------- 1230 remopsCompliance MODULE-COMPLIANCE 1231 STATUS current 1232 DESCRIPTION 1233 "The compliance statement for the REMOPS-MIB." 1234 MODULE -- this module 1235 MANDATORY-GROUPS { 1236 remopsBaseGroup, 1237 remopsPingGroup, 1238 remopsTraceRouteGroup, 1239 remopsDnsLookupGroup 1240 } 1242 OBJECT remopsPingMaxConcurrentRequests 1243 MIN-ACCESS read-only 1244 DESCRIPTION 1245 "The agent is not required to support a SET 1246 operation to this object." 1248 OBJECT remopsPingPurgeTime 1249 MIN-ACCESS read-only 1250 DESCRIPTION 1251 "The agent is not required to support a SET 1252 operation to this object." 1254 OBJECT remopsTraceRouteMaxConcurrentRequests 1255 MIN-ACCESS read-only 1256 DESCRIPTION 1257 "The agent is not required to support a SET 1258 operation to this object." 1260 OBJECT remopsTraceRoutePurgeTime 1261 MIN-ACCESS read-only 1262 DESCRIPTION 1263 "The agent is not required to support a SET 1264 operation to this object." 1266 OBJECT remopsDnsLookupMaxConcurrentRequests 1267 MIN-ACCESS read-only 1268 DESCRIPTION 1269 "The agent is not required to support a SET 1270 operation to this object." 1272 OBJECT remopsDnsLookupPurgeTime 1273 MIN-ACCESS read-only 1274 DESCRIPTION 1275 "The agent is not required to support a SET 1276 operation to this object." 1277 ::= { remopsCompliances 1 } 1279 --------------------------------------------------------------------- 1280 -- MIB groupings 1281 --------------------------------------------------------------------- 1282 remopsBaseGroup OBJECT-GROUP 1283 OBJECTS { 1284 remopsSpinLock 1285 } 1286 STATUS current 1287 DESCRIPTION 1288 "The group of objects common to both the remote ping and 1289 remote traceroute operations." 1290 ::= { remopsGroups 1 } 1292 remopsPingGroup OBJECT-GROUP 1293 OBJECTS { 1294 remopsPingMaxConcurrentRequests, 1295 remopsPingPurgeTime, 1296 remopsPingPacketSize, 1297 remopsPingTimeOut, 1298 remopsPingProbeCount, 1299 remopsPingOperStatus, 1300 remopsPingRowStatus, 1301 remopsPingResultsResponse 1302 } 1303 STATUS current 1304 DESCRIPTION 1305 "The group of objects that comprise the remote ping 1306 operation." 1307 ::= { remopsGroups 2 } 1309 remopsTraceRouteGroup OBJECT-GROUP 1310 OBJECTS { 1311 remopsTraceRouteMaxConcurrentRequests, 1312 remopsTraceRoutePurgeTime, 1313 remopsTraceRouteByPassRouteTable, 1314 remopsTraceRoutePacketSize, 1315 remopsTraceRouteTimeOut, 1316 remopsTraceRouteProbesPerHop, 1317 remopsTraceRoutePort, 1318 remopsTraceRouteMaxTtl, 1319 remopsTraceRouteTos, 1320 remopsTraceRouteSourceAddress, 1321 remopsTraceRouteInterfaceName, 1322 remopsTraceRouteMiscOptions, 1323 remopsTraceRouteMaxFailures, 1324 remopsTraceRouteOperStatus, 1325 remopsTraceRouteCurHopCount, 1326 remopsTraceRouteCurProbeCount, 1327 remopsTraceRouteRowStatus, 1328 remopsTraceRouteResultsHopAddress, 1329 remopsTraceRouteResultsResponse 1330 } 1331 STATUS current 1332 DESCRIPTION 1333 "The group of objects that comprise the remote traceroute 1334 operation." 1335 ::= { remopsGroups 3 } 1337 remopsDnsLookupGroup OBJECT-GROUP 1338 OBJECTS { 1339 remopsDnsLookupMaxConcurrentRequests, 1340 remopsDnsLookupPurgeTime, 1341 remopsDnsLookupTimeOut, 1342 remopsDnsLookupRetryLimit, 1343 remopsDnsLookupOperStatus, 1344 remopsDnsLookupRetryCount, 1345 remopsDnsLookupResultType, 1346 remopsDnsLookupResult, 1347 remopsDnsLookupRowStatus 1348 } 1349 STATUS current 1350 DESCRIPTION 1351 "The group of objects that comprise the remote DNS 1352 Lookup operation." 1353 ::= { remopsGroups 4 } 1355 END 1357 5.0 Security Considerations 1359 Certain management information defined in this MIB may be considered 1360 sensitive in some network environments. Therefore, authentication of 1361 received SNMP requests and controlled access to management information 1362 SHOULD be employed in such environments. The method for this 1363 authentication is a function of the SNMP Administrative Framework, and 1364 has not been expanded by this MIB. 1366 It is RECOMMENDED that this MIB not be supported in insecure 1367 environments. 1369 6.0 Intellectual Property 1371 The IETF takes no position regarding the validity or scope of any 1372 intellectual property or other rights that might be claimed to pertain 1373 to the implementation or use of the technology described in this 1374 document or the extent to which any license under such rights might or 1375 might not be available; neither does it represent that it has made any 1376 effort to identify any such rights. Information on the IETF's 1377 procedures with respect to rights in standards-track and 1378 standards-related documentation can be found in BCP-11. Copies of 1379 claims of rights made available for publication and any assurances of 1380 licenses to be made available, or the result of an attempt made to 1381 obtain a general license or permission for the use of such proprietary 1382 rights by implementers or users of this specification can be obtained 1383 from the IETF Secretariat. 1385 The IETF invites any interested party to bring to its attention any 1386 copyrights, patents or patent applications, or other proprietary rights 1387 which may cover technology that may be required to practice this 1388 standard. Please address the information to the IETF Executive 1389 Director. 1391 7.0 Acknowledgments 1393 This document is a product of the DISMAN Working Group. 1395 8.0 References 1397 [1] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 1398 Management Protocol", RFC 1157, SNMP Research, Performance Systems 1399 International, MIT Laboratory for Computer Science, May 1990. 1401 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 1402 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 1403 RFC 1213, Hughes LAN Systems, Performance Systems International, 1404 March 1991. 1406 [3] Case, J., McCloghrie, K., Rose, M., and Waldbusser S., "Structure 1407 of Management Information for Version 2 of the Simple Network 1408 Management Protocol (SNMPv2)", RFC 1902, January 1996. 1410 [4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Textual 1411 Conventions for Version 2 of the Simple Network Management Protocol 1412 (SNMPv2)", RFC 1903, January 1996. 1414 [5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 1415 "Conformance Statements for Version 2 of the Simple Network 1416 Management Protocol (SNMPv2)", RFC 1904, January 1996. 1418 [6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol 1419 Operations for Version 2 of the Simple Network Management Protocol 1420 (SNMPv2)", RFC 1905, January 1996. 1422 [7] Harrington D., Presuhn, R., Wijnen, B., "An Architecture for 1423 Describing SNMP Management Frameworks", RFC 2271, Cabletron 1424 Systems, BMC Software, Inc., IBM T.J. Watson Research, January 1425 1998. 1427 [8] Harrington D., Presuhn, R., Wijnen, B., "Message Processing and 1428 Dispatching for the Simple Network Management Protocol (SNMP)", RFC 1429 2272, Cabletron Systems, BMC Software, Inc., IBM T.J. Watson 1430 Research, January 1998. 1432 [9] Levi D., Meyer P., Stewart, B., "SNMPv3 Applications", RFC 2273, 1433 SNMP Research, Inc., Secure Computing Corporation, Cisco Systems, 1434 January 1998. 1436 [10] Blumenthal, U., Wijnen, B., "User-based Security Model (USM) for 1437 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1438 2274, IBM T. J. Watson Research, January 1998. 1440 [11] Wijnen, B., Presuhn, R., McCloghrie, K., "View-based Access Control 1441 Model (VACM) for the Simple Network Management Protocol (SNMP)", 1442 RFC 2275, IBM T.J. Watson Research, BMC Software, Inc., Cisco 1443 Systems, Inc., January 1998. 1445 [12] Hovey, R., and S. Bradner, "The Organizations Involved in the IETF 1446 Standards Process", BCP 11, RFC 2028, October 1996. 1448 [13] Bradner, S., "Key words for use in RFCs to Indicate Requirement 1449 Levels", BCP 14, RFC 2119, March 1997. 1451 [14] Rose, M., and K. McCloghrie, "Structure and Identification of 1452 Management Information for TCP/IP-based Internets", RFC 1155, 1453 Performance Systems International, Hughes LAN Systems, May 1990. 1455 [15] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1456 Performance Systems International, Hughes LAN Systems, March 1991. 1458 [16] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1459 RFC 1215, Performance Systems International, March 1991. 1461 [17] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1462 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 1463 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1464 International Network Services, January 1996. 1466 [18] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1467 Mappings for Version 2 of the Simple Network Management Protocol 1468 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1469 Dover Beach Consulting, Inc., International Network Services, 1470 January 1996. 1472 9.0 Author's Address 1474 Kenneth D. White 1475 Dept. BRQA/Bldg. 501/G114 1476 IBM Corporation 1477 P.O.Box 12195 1478 3039 Cornwallis 1479 Research Triangle Park, NC 27709, USA 1480 E-mail: kennethw@vnet.ibm.com 1482 10.0 Full Copyright Statement 1484 Copyright (C) The Internet Society (1997). All Rights Reserved. 1486 This document and translations of it may be copied and furnished to 1487 others, and derivative works that comment on or otherwise explain it or 1488 assist in its implementation may be prepared, copied, published and 1489 distributed, in whole or in part, without restriction of any kind, 1490 provided that the above copyright notice and this paragraph are included 1491 on all such copies and derivative works. However, this document itself 1492 may not be modified in any way, such as by removing the copyright notice 1493 or references to the Internet Society or other Internet organizations, 1494 except as needed for the purpose of developing Internet standards in 1495 which case the procedures for copyrights defined in the Internet 1496 Standards process must be followed, or as required to translate it into 1497 languages other than English. 1499 The limited permissions granted above are perpetual and will not be 1500 revoked by the Internet Society or its successors or assigns. 1502 This document and the information contained herein is provided on an "AS 1503 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1504 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1505 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1506 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1507 FITNESS FOR A PARTICULAR PURPOSE.