Browse Prior Art Database

V2ToV1 Mapping SNMPv2 onto SNMPv1 within a bi-lingual SNMP agent (RFC2089)

IP.com Disclosure Number: IPCOM000002641D
Original Publication Date: 1997-Jan-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 14 page(s) / 22K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Wijnen: AUTHOR [+2]

Abstract

The goal of this memo is to document a common way of mapping an SNMPv2 response into an SNMPv1 response within a bi-lingual SNMP agent (one that supports both SNMPv1 and SNMPv2).

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

Network Working Group B. Wijnen

Request for Comments: 2089 IBM

Category: Informational D. Levi

SNMP Research, Inc

January 1997

V2ToV1

Mapping SNMPv2 onto SNMPv1

within a bi-lingual SNMP agent

Status of this Memo

This memo provides information for the Internet community. This memo

does not specify an Internet standard of any kind. Distribution of

this memo is unlimited.

Abstract

The goal of this memo is to document a common way of mapping an

SNMPv2 response into an SNMPv1 response within a bi-lingual SNMP

agent (one that supports both SNMPv1 and SNMPv2).

Table of Contents

1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . 2

2.0 Mapping SNMPv2 into SNMPv1 . . . . . . . . . . . . . . . . 2

2.1 Mapping SNMPv2 error-status into SNMPv1 error-status . . . 3

2.2 Mapping SNMPv2 exceptions into SNMPv1 . . . . . . . . . . 3

2.3 Mapping noSuchObject and noSuchInstance . . . . . . . . . 4

2.4 Mapping endOfMibView . . . . . . . . . . . . . . . . . . . 5

2.5 Mapping SNMPv2 SMI into SNMPv1 . . . . . . . . . . . . . . 5

3.0 Processing SNMPv1 requests . . . . . . . . . . . . . . . . 6

3.1 Processing an SNMPv1 GET request . . . . . . . . . . . . . 6

3.2 Processing an SNMPv1 GETNEXT request . . . . . . . . . . . 7

3.3 Processing an outgoing SNMPv2 trap . . . . . . . . . . . . 8

4.0 Acknowledgements . . . . . . . . . . . . . . . . . . . . . 10

5.0 References . . . . . . . . . . . . . . . . . . . . . . . . 10

6.0 Security Considerations . . . . . . . . . . . . . . . . . 10

7.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 11

Appendix A. Background Information . . . . . . . . . . . . . 12

A.1 Mapping of error-status Values . . . . . . . . . . . . . 12

A.2 SNMPv1 traps without Counter64 varBinds. . . . . . . . . 12

1.0 Introduction

We now have the SNMPv1 protocol (RFC1157 [1]) as a full standard and

the SNMPv2 protocol (RFC1905 [1]) as a DRAFT standard. It can be

expected that many agent implementations will support both SNMPv1 and

SNMPv2 requests coming from SNMP management entities. In many cases

the underlying instrumentation will be implemented using the new

SNMPv2 SMI and SNMPv2 protocol. The SNMP engine then gets the task

to ensure that any SNMPv2 response ...