Browse Prior Art Database

Definitions of Managed Objects for Circuit to Interface Translation (RFC3201)

IP.com Disclosure Number: IPCOM000006461D
Original Publication Date: 2002-Jan-01
Included in the Prior Art Database: 2002-Jan-07
Document File: 24 page(s) / 46K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Steinberger: AUTHOR [+2]

Abstract

This memo defines an extension of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the insertion of interesting Circuit Interfaces into the ifTable. This is important for circuits that must be used within other MIB modules which require an ifEntry. It allows for integrated monitoring of circuits as well as routing to circuits using unaltered, pre-existing MIB modules.

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

Network Working Group                                     R. Steinberger

Request for Comments: 3201                             Paradyne Networks

Category: Standards Track                                    O. Nicklass

                                            RAD Data Communications Ltd.

                                                            January 2002

                     Definitions of Managed Objects

                  for Circuit to Interface Translation

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

Abstract

   This memo defines an extension of the Management Information Base

   (MIB) for use with network management protocols in TCP/IP-based

   internets.  In particular, it defines objects for managing the

   insertion of interesting Circuit Interfaces into the ifTable.  This

   is important for circuits that must be used within other MIB modules

   which require an ifEntry.  It allows for integrated monitoring of

   circuits as well as routing to circuits using unaltered, pre-existing

   MIB modules.

Table of Contents

   1. The SNMP Management Framework ...............................    2

   2. Conventions .................................................    3

   3. Overview ....................................................    3

   3.1. Circuit Concepts ..........................................    4

   3.2. Theory of Operation .......................................    4

   3.2.1. Creation Process ........................................    4

   3.2.2. Destruction Process .....................................    5

   3.2.2.1. Manual Row Destruction ................................    5

   3.2.2.2. Automatic Row Destruction .............................    5

   3.2.3. Modification Process ....................................    5

   3.2.4. Persistence of Data .....................................    5

   4. Relation to Other MIB Modules ...............................    6

   4.1. Frame Relay DTE MIB .......................................    6

Steinberger & Nicklass      Standards Track                     [Page 1]

RFC 3201                Circuit to Interface MIB            January 2002

   4.2. Frame Relay Service MIB ...................................    6

   4.3. ATM MIB ...................................................    6

   4.4. Interfaces Group MIB ......................................    6

   4.4.1. Interfaces Table (ifTable, ifXtable) ....................    6

   4.4.2. Stack Table (ifStackTable) ..............................    9

   4.5. Other MIB Modules .........................................   11

   5. Structure of the MIB Module .................................   11

   5.1. ciCircuitTable ............................................   11

   5.2. ciIfMapTable ..............................................   11

   6. Object Definitions ..........................................   11

   7. Acknowledgments .............................................   19

   8. References ..................................................   19

   9. Security Considerations .........................