Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations
RFC 4560

 
Document Type RFC - Proposed Standard (June 2006; No errata)
Obsoletes RFC 2925
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 4560 (Proposed Standard)
Telechat date
Responsible AD Dan Romascanu
Send notices to randy_presuhn@mindspring.com, quittek@netlab.nec.de; Juergen Schoenwaelder
Network Working Group                                    J. Quittek, Ed.
Request for Comments: 4560                                           NEC
Obsoletes: 2925                                            K. White, Ed.
Category: Standards Track                                      IBM Corp.
                                                               June 2006

                    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 (2006).

Abstract

   This memo defines Management Information Bases (MIBs) for performing
   ping, traceroute, and lookup operations at a host.  When managing a
   network, it is useful to be able to initiate and retrieve the results
   of ping or traceroute operations when they are performed at a remote
   host.  A lookup capability is defined in order to enable resolution
   of either an IP address to an DNS name or a 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.

Quittek & White             Standards Track                     [Page 1]
RFC 4560                       REMOPS MIB                      June 2006

Table of Contents

   1. Introduction ....................................................3
      1.1. Ping .......................................................3
      1.2. Traceroute .................................................4
      1.3. Lookup .....................................................5
      1.4. Remote Operations ..........................................5
   2. The Internet-Standard Management Framework ......................5
   3. Structure of the MIBs ...........................................6
      3.1. Ping MIB ...................................................6
           3.1.1. pingMaxConcurrentRequests ...........................7
           3.1.2. pingCtlTable ........................................7
           3.1.3. pingResultsTable ....................................7
           3.1.4. pingProbeHistoryTable ...............................8
      3.2. Traceroute MIB .............................................8
           3.2.1. traceRouteMaxConcurrentRequests .....................8
           3.2.2. traceRouteCtlTable ..................................8
           3.2.3. traceRouteResultsTable ..............................9
           3.2.4. traceRouteProbeHistoryTable ........................10
           3.2.5. traceRouteHopsTable ................................10
      3.3. Lookup MIB ................................................10
           3.3.1. lookupMaxConcurrentRequests and lookupPurgeTime ....11
           3.3.2. lookupCtlTable .....................................11
           3.3.3. lookupResultsTable .................................12
      3.4. Conformance ...............................................12
   4. Definitions ....................................................13
      4.1. DISMAN-PING-MIB ...........................................13
      4.2. DISMAN-TRACEROUTE-MIB .....................................46
      4.3. DISMAN-NSLOOKUP-MIB .......................................84
   5. Security Considerations ........................................95
   6. Acknowledgements ...............................................97
   7. References .....................................................97
      7.1. Normative References ......................................97
      7.2. Informative References ....................................98

Quittek & White             Standards Track                     [Page 2]
RFC 4560                       REMOPS MIB                      June 2006

1.  Introduction

   This document defines 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 whether a path exists
   between two hosts, whereas traceroute shows an actual path.

   Both ping and traceroute yield round-trip times measured in
   milliseconds.  These times can be used as a rough approximation for
Show full document text