Browse Prior Art Database

Definitions of Managed Objects for APPN (RFC2455)

IP.com Disclosure Number: IPCOM000003033D
Original Publication Date: 1998-Nov-01
Included in the Prior Art Database: 2019-Feb-11

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Clouston: AUTHOR [+1]

Related Documents

10.17487/RFC2455: DOI

Abstract

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for monitoring and controlling network devices with APPN (Advanced Peer-to-Peer Networking) capabilities. This memo identifies managed objects for the APPN protocol. [STANDARDS-TRACK]

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

Network Working Group B. Clouston Request for Comments: 2455 Cisco Systems Obsoletes: 2155 B. Moore Category: Standards Track IBM Corporation November 1998

Definitions of Managed Objects for APPN

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 (1998). All Rights Reserved.

Abstract

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for monitoring and controlling network devices with APPN (Advanced Peer-to-Peer Networking) capabilities. This memo identifies managed objects for the APPN protocol.

Table of Contents

1. Introduction .......................................... 2 2. The SNMPv2 Network Management Framework ............... 2 3. Overview .............................................. 3 3.1 Relationship with RFC 2155 ........................... 6 3.2 APPN MIB structure ................................... 7 4. Definitions ........................................... 10 5. Security Considerations ............................... 135 6. Intellectual Property ................................. 136 7. Acknowledgments ....................................... 137 8. References ............................................ 137 9. Authors’ Addresses .................................... 139 10. Full Copyright Statement .............................. 140

Clouston & Moore Standards Track [Page 1]

RFC 2455 APPN MIB November 1998

1. Introduction

This document is a product of the SNA NAU Services MIB Working Group. It defines a MIB module for managing devices with Advanced Peer-to- Peer Networking (APPN) capabilities.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [17].

2. The SNMP Network Management Framework

The SNMP Management Framework presently consists of five major components:

o An overall architecture, described in RFC 2271 [1].

o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The second version, called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 1904 [7].

o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [8]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called...

Processing...
Loading...