Browse Prior Art Database

SNMP MUX protocol and MIB (RFC1227)

IP.com Disclosure Number: IPCOM000002041D
Original Publication Date: 1991-May-01
Included in the Prior Art Database: 2019-Feb-11
Document File: 13 page(s) / 15K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M.T. Rose: AUTHOR

Related Documents

10.17487/RFC1227: DOI

Abstract

This memo suggests a mechanism by which a user process may associate itself with the local SNMP agent on a host, in order to implement portions of the MIB. This mechanism would be local to the host.This is an Experimental Protocol for the Internet community. It does not specify an Internet standard.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 14% of the total text.

Network Working Group M. Rose Request for Comments: 1227 Performance Systems International, Inc. May 1991

SNMP MUX Protocol and MIB

Status of this Memo

This memo suggests a mechanism by which a user process may associate itself with the local SNMP agent on a host, in order to implement portions of the MIB. This mechanism would be local to the host.

This is an Experimental Protocol for the Internet community. Discussion and suggestions for improvement are requested. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Table of Contents

1. Introduction .......................................... 1 2. Architecture .......................................... 2 3. Protocol .............................................. 3 3.1 Tricky Things ........................................ 3 3.1.1 Registration ....................................... 4 3.1.2 Removing Registration .............................. 4 3.1.3 Atomic Sets ........................................ 4 3.1.4 Variables in Requests .............................. 5 3.1.5 Request-ID ......................................... 5 3.1.6 The powerful get-next operator ..................... 5 3.2 Protocol Data Units .................................. 6 3.3 Mappings on Transport Service ........................ 8 3.3.1 Mapping onto the TCP ............................... 8 4. MIB for the SMUX ...................................... 9 5. Acknowledgements ...................................... 12 6. References ............................................ 12 7. Security Considerations................................ 13 8. Author’s Address....................................... 13

1. Introduction

On typical kernel/user systems, an agent speaking the SNMP [1] is often implemented as a user-process, that reads kernel variables in order to realize the Internet-standard MIB [2]. This approach works fine as long as all of the information needed by the SNMP agent resides in either the kernel or in stable storage (i.e., files). However, when other user-processes are employed to implement other

Rose [Page 1]

RFC 1227 SMUX May 1991

network services, such as routing protocols, communication between the SNMP agent and other processes is problematic.

In order to solve this problem, a new protocol, the SNMP multiplexing (SMUX) protocol is introduced. When a user-process, termed a SMUX peer, wishes to export a MIB module, it initiates a SMUX association to the local SNMP agent, registers itself, and (later) fields management operations for objects in the MIB module.

Carrying this approach to its fullest, it is possible to generalize the SNMP agent so that it knows about only the SNMP group of the Internet-standard MIB. All other portions of the Internet-standard MIB can be implemented by another process. This is quite useful, for example, when a computer manufacturer wishes to provide SNMP access for...

Processing...
Loading...