Dismiss
There will be a system update on Friday, May 5th, 6 PM ET. You may experience a brief service interruption.
Browse Prior Art Database

Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations (RFC2925)

IP.com Disclosure Number: IPCOM000005107D
Original Publication Date: 2000-Sep-01
Included in the Prior Art Database: 2001-Aug-15

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

K. White: AUTHOR

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.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 2% of the total text.

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 . . . . . . . . . . . . . . . . . . . ....