Definitions of Managed Objects for Monitoring and Controlling the Frame Relay/ATM PVC Service Interworking Function
RFC 2955
|
| Document |
Type |
|
RFC - Proposed Standard
(October 2000; No errata)
|
|
Last updated |
|
2013-03-02
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
RFC 2955 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group K. Rehbehn
Request for Comments: 2955 Megisto Systems
Category: Standards Track O. Nicklass
RAD Data Communications, Ltd.
G. Mouradian
AT&T Labs
October 2000
Definitions of Managed Objects
for Monitoring and Controlling the
Frame Relay/ATM PVC Service Interworking Function
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 a Management Information Base (MIB) to configure,
monitor, and control a service interworking function (IWF) for
Permanent Virtual Connections (PVC) between Frame Relay and
Asynchronous Transfer Mode (ATM) technologies.
Table of Contents
1. The SNMP Management Framework ............................... 2
2. Conventions ................................................. 3
3. Overview .................................................... 3
3.1 Frame Relay/ATM Service Interworking Background ............ 4
3.2 Structure of the MIB ....................................... 4
3.3 Relationship to Other MIBs ................................. 5
3.3.1 Frame Relay Service MIB .................................. 6
3.3.2 Frame Relay DTE MIB ...................................... 6
3.3.3 ATM MIB .................................................. 6
3.3.4 IF MIB ................................................... 7
3.4 Point to Multipoint Considerations ......................... 7
3.5 Theory of Operation ........................................ 7
3.5.1 Creation Process ......................................... 7
3.5.2 Destruction Process ...................................... 10
Rehbehn, et al. Standards Track [Page 1]
RFC 2955 FR to ATM Service Interworking MIB October 2000
3.5.3 Modification Process ..................................... 11
4. Object Definitions .......................................... 11
4.1 The FR/ATM PVC Service IWF Connection Group ................ 13
4.2 The FR/ATM PVC Service IWF Connection Descriptor Group ..... 21
5. Augmentation of ATM MIB VCL Endpoint Entry (atmVclEntry) .... 27
6. Frame Relay/ATM PVC Service Interworking NOTIFICATION ....... 29
7. Conformance Information ..................................... 29
7.1 Compliance Statement For Equipment ......................... 29
7.2 Compliance Statement For Service (CNM Interface) ........... 30
7.3 Units of Conformance ....................................... 32
7.3.1 Basic FR/ATM IWF PVC Connection Group .................... 32
7.3.2 FR/ATM IWF PVC Connection Descriptor Group ............... 32
7.3.3 ATM MIB VCL Endpoint Table Augmentation .................. 33
7.3.4 Notification Group ....................................... 33
8. Acknowledgments ............................................. 34
9. References .................................................. 34
10. Security Considerations .................................... 36
11. Authors' Addresses ......................................... 37
12. Intellectual Property Rights ............................... 38
13. Full Copyright Statement ................................... 39
1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in RFC 2571 [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 STD 58, RFC 2578
[5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [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
Show full document text