Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) Architectures
RFC 3498

 
Document Type RFC - Proposed Standard (March 2003; No errata)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 3498 (Proposed Standard)
Telechat date
Responsible AD Erik Nordmark
IESG note Published as RFC 3498 in March 2003
Send notices to <fayely98@hotmail.com>, <hklam@lucent.com>
Network Working Group                                         J. Kuhfeld
Request for Comments: 3498                                    J. Johnson
Category:Standards Track                                     M. Thatcher
                                                        Redback Networks
                                                              March 2003

                    Definitions of Managed Objects
                for Synchronous Optical Network (SONET)
       Linear Automatic Protection Switching (APS) Architectures

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

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in TCP/IP based internets.
   In particular, it defines objects for managing networks using
   Synchronous Optical Network (SONET) linear Automatic Protection
   Switching (APS) architectures.

Table of Contents

   1.  Introduction................................................. 2
   2.  The Internet-Standard Management Framework................... 2
   3.  Overview..................................................... 2
   4.  Definitions.................................................. 4
   5.  Intellectual Property........................................39
   6.  Acknowledgments..............................................40
   7.  Normative References.........................................40
   8.  Informative References.......................................40
   9.  Security Considerations......................................41
   10. Editors' Addresses...........................................42
   11. Full Copyright Statement.....................................43

Kuhfeld, et al.             Standards Track                     [Page 1]
RFC 3498                  SONET LINEAR APS MIB                March 2003

1. Introduction

   This memo defines a portion of the Management Information Base (MIB)
   used for managing SONET linear Automatic Protection Switching (APS)
   architectures.  Two linear APS architectures are supported, the 1+1
   architecture and the 1:n architecture.

2. The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).
   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB
   module that is compliant to the SMIv2, which is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
   [RFC2580].

3. Overview

   These objects are used to control and manage SONET linear APS
   architectures.  Ring APS groups are not currently supported by this
   MIB.

   The MIB includes three scalars, containing counts of APS groups and
   SONET LTEs, a notification enable object, and six tables.

   The apsMapTable contains entries for each SONET LTE interface
   available on the system.  The table serves two purposes.  It can be
   used to locate SONET LTE interfaces that are not currently included
   in APS groups.  It also provides a mapping from InterfaceIndex to
   group name and channel number for those SONET LTE interfaces that are
   included in APS groups.  Entries in apsMapTable cannot be added or
   deleted through operations defined in this MIB.  However, an
   apsMapEntry may be added or deleted through other system mechanisms,
   such as hot swap.  Also, existing entries cannot be directly modified
   and instead, such modifications occur as a result of side-effects of
   operations on the apsChanConfigTable.

   The apsChanConfigTable supports addition, modification and deletion
   of entries representing linear APS channels.  Entries are indexed by
   a text group name and integer channel number.  Each entry contains an
   InterfaceIndex value identifying the SONET LTE used for the channel
   and the priority of the channel.  A side effect of row creation or

Kuhfeld, et al.             Standards Track                     [Page 2]
Show full document text