Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework (RFC3584)

IP.com Disclosure Number: IPCOM000018950D
Original Publication Date: 2003-Aug-01
Included in the Prior Art Database: 2003-Aug-22

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Frye: AUTHOR [+4]

Abstract

The purpose of this document is to describe coexistence between version 3 of the Internet-standard Network Management Framework, (SNMPv3), version 2 of the Internet-standard Network Management Framework (SNMPv2), and the original Internet-standard Network Management Framework (SNMPv1). This document also describes how to convert MIB modules from SMIv1 format to SMIv2 format. This document obsoletes RFC 2576.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 4% of the total text.

Network Working Group R. Frye

Request for Comments: 3584 Vibrant Solutions

BCP: 74 D. Levi

Obsoletes: 2576 Nortel Networks

Category: Best Current Practice S. Routhier

Wind River Systems, Inc.

B. Wijnen

Lucent Technologies

August 2003

Coexistence between Version 1, Version 2, and Version 3

of the Internet-standard Network Management Framework

Status of this Memo

This document specifies an Internet Best Current Practices for the

Internet Community, and requests discussion and suggestions for

improvements. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2003). All Rights Reserved.

Abstract

The purpose of this document is to describe coexistence between

version 3 of the Internet-standard Network Management Framework,

(SNMPv3), version 2 of the Internet-standard Network Management

Framework (SNMPv2), and the original Internet-standard Network

Management Framework (SNMPv1). This document also describes how to

convert MIB modules from SMIv1 format to SMIv2 format. This document

obsoletes RFC 2576.

Frye, et al. Best Current Practice [Page 1]

RFC 3584 Coexistence between SNMP versions August 2003

Table Of Contents

1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.1. SNMPv1 . . . . . . . . . . . . . . . . . . . . . . . . 4

1.2. SNMPv2 . . . . . . . . . . . . . . . . . . . . . . . . 4

1.3. SNMPv3 . . . . . . . . . . . . . . . . . . . . . . . . 5

2. SMI and Management Information Mappings. . . . . . . . . . . 5

2.1. MIB Modules. . . . . . . . . . . . . . . . . . . . . . 6

2.1.1. Object Definitions . . . . . . . . . . . . . . 6

2.1.2. Trap and Notification Definitions . . . . . . 8

2.2. Compliance Statements. . . . . . . . . . . . . . . . . 9

2.3. Capabilities Statements. . . . . . . . . . . . . . . . 9

3. Translating Notification Parameters. . . . . . . . . . . . . 10

3.1. Translating SNMPv1 Notification Parameters to

SNMPv2 Notification Parameters . . . . . . . . . . . . 11

3.2. Translating SNMPv2 Notification Parameters to

SNMPv1 Notification Parameters . . . . . . . . . . . . 12

4. Approaches to Coexistence in a Multi-lingual Network . . . . 14

4.1. SNMPv1 and SNMPv2 Access to MIB Data . . . . . . . . . 14

4.2. Multi-lingual implementations. . . . . . . . . . . . . 15

4.2.1. Command Generator. . . . . . . . . . . . . . . 15

4.2.2. Command Responder. . . . . . . . . . . . . . . 16

4.2.2.1. Handling Counter64 . . . . . . . . . 16

4.2.2.2. Mapping SNMPv2 Exceptions. . . . . . 17

4.2.2.2.1. Mapping noSuchObject

and noSuchInstance. . . . 18

4.2.2.2.2. Mapping endOfMibView. . . 18

4.2.2.3. Processing An SNMPv1 GetReques . . . 18

4.2.2.4. Processing An SNMPv1 GetNextRequest. 19

4.2.2.5. Processing An SNMPv1 SetRequest. . . 20

4.2.3. Notification Originator. . . . . . . . . . . . 21

4.2.4. Notification Receiver. . . . . . . . . . . . . 21

4.3. Proxy Implementations. . . . . . . . . . . . . . . . . 22

4.3.1. Upstream Version Greater Than Downstream

Version. . . . . . . . . . . . . . . . . . . . 22

...