Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations
RFC 2925
Document | Type |
RFC - Proposed Standard
(September 2000; Errata)
Obsoleted by RFC 4560
|
|
---|---|---|---|
Author | Kenneth White | ||
Last updated | 2020-01-21 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized with errata bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 2925 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
Network Working Group K. White Request for Comments: 2925 IBM Corp. Category: Standards Track September 2000 Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2000). All Rights Reserved. Abstract This memo defines Management Information Bases (MIBs) for performing remote ping, traceroute and lookup operations at a remote host. When managing a network it is useful to be able to initiate and retrieve the results of ping or traceroute operations when performed at a remote host. A Lookup capability is defined in order to enable resolving of either an IP address to an DNS name or an DNS name to an IP address at a remote host. Currently, there are several enterprise-specific MIBs for performing remote ping or traceroute operations. The purpose of this memo is to define a standards-based solution to enable interoperability. Table of Contents 1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2.0 The SNMP Network Management Framework . . . . . . . . . . . 4 3.0 Structure of the MIBs . . . . . . . . . . . . . . . . . . . 5 3.1 Ping MIB . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.1.1 pingMaxConcurrentRequests . . . . . . . . . . . . . . . 6 3.1.2 pingCtlTable . . . . . . . . . . . . . . . . . . . . . . 6 3.1.3 pingResultsTable . . . . . . . . . . . . . . . . . . . . 7 3.1.4 pingProbeHistoryTable . . . . . . . . . . . . . . . . . 7 3.2 Traceroute MIB . . . . . . . . . . . . . . . . . . . . . . . 8 3.2.1 traceRouteMaxConcurrentRequests . . . . . . . . . . . . 8 3.2.2 traceRouteCtlTable . . . . . . . . . . . . . . . . . . . 8 3.2.3 traceRouteResultsTable . . . . . . . . . . . . . . . . . 9 White Standards Track [Page 1] RFC 2925 Ping, Traceroute, and Lookup MIBs September 2000 3.2.4 traceRouteProbeHistoryTable . . . . . . . . . . . . . . 9 3.2.5 traceRouteHopsTable . . . . . . . . . . . . . . . . . . 10 3.3 Lookup MIB . . . . . . . . . . . . . . . . . . . . . . . . . 10 3.3.1 lookupMaxConcurrentRequests and lookupPurgeTime . . . . 10 3.3.2 lookupCtlTable . . . . . . . . . . . . . . . . . . . . . 10 3.3.3 lookupResultsTable . . . . . . . . . . . . . . . . . . . 11 4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . 12 4.1 DISMAN-PING-MIB . . . . . . . . . . . . . . . . . . . . . . 12 4.2 DISMAN-TRACEROUTE-MIB . . . . . . . . . . . . . . . . . . . 36 4.3 DISMAN-NSLOOKUP-MIB . . . . . . . . . . . . . . . . . . . . 63 5.0 Security Considerations . . . . . . . . . . . . . . . . . . 73 6.0 Intellectual Property . . . . . . . . . . . . . . . . . . . 74 7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 74 8.0 References . . . . . . . . . . . . . . . . . . . . . . . . . 74 9.0 Author's Address . . . . . . . . . . . . . . . . . . . . . . 76 10.0 Full Copyright Statement . . . . . . . . . . . . . . . . . 77 1.0 Introduction The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119, reference [13]. This document is a product of the Distributed Management (DISMAN) Working Group. Its purpose is to define standards-based MIB modules for performing specific remote operations. The remote operations defined by this document consist of the ping, traceroute and lookup functions. Ping and traceroute are two very useful functions for managing networks. Ping is typically used to determine if a path exists between two hosts while traceroute shows an actual path. Ping is usually implemented using the Internet Control Message Protocol (ICMP) "ECHO" facility. It is also possible to implement a ping capability using alternate methods, some of which are: o Using the UDP echo port (7), if supported. This is defined by RFC 862 [2]. o Timing an SNMP query. o Timing a TCP connect attempt. In general, almost any request/response flow can be used to generate a round-trip time. Often many of the non-ICMP ECHO facility methods stand a better chance of yielding a good response (not timing out forShow full document text