⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 rfc2515.txt

📁 RFC 的详细文档!
💻 TXT
📖 第 1 页 / 共 5 页
字号:
   configuration | (3) operational status          |MIB II | *  |
                 | (4) administrative status       |       | ** |
                 | (5) last change status          |       |    |
   _____________________________________________________________
   ATM interface:| (1) active VPI/VCI fields       |ATM MIB|    |
   cell layer    | (2) maximum number of VPCs/VCCs |   (1) |yes |
   configuration | (3) configured VPCs/VCCs        |       | ** |
                 | (4) ILMI VPI/VCI values         |       |    |
                 | (5) Neighbor system info        |       |    |
                 | (6) Max. number of VPI/VCI bits |       |yes |
                 | (7) ATM Subscribed Address      |       |    |
   _____________________________________________________________
   ATM interface:|(1) received/transmitted cells   |       |    |
   cell layer    |(2) cells with HEC error         |MIB II |yes |
   performance   |(3) cell header validation errors|       |    |
   _____________________________________________________________






Tesink                      Standards Track                    [Page 18]

RFC 2515                 ATM Management Objects            February 1999


   _____________________________________________________________
   ATM interface:|(1)DS3 PLCP severely errored     |ATM MIB|    |
   PLCP & TC     |   framing seconds               |    (2)|    |
   layer         |(2)DS3 PLCP unavailable seconds  |       |no  |
   performance   |(3)DS3 PLCP alarm state          |       |    |
                 |(4)out of cell delineation events|       |    |
                 |(5)TC alarm state                |       |    |
   _____________________________________________________________
   VP/VC link:   |(1)VPI or VPI/VCI value          |ATM MIB|    |
   configuration |(2)VCL or VPL operational status |  (3,4)|yes |
                 |(3)VCL/VPL administrative status |       |*** |
                 |(4)VCL/VPL last change status    |       |    |
                 |(5)transmit/receive traffic/     |       |    |
                 |   service category parameters   |       |    |
                 |(6)AAL type                      |       |    |
                 |(7)transmit/receive AAL5 SDU size|       |    |
                 |(8)AAL5 encapsulation type       |       |    |
                 |(9)connection topology type      |       |    |
                 |(10)use of call control          |       |    |
   _____________________________________________________________
   VP/VC         |(1)cross-connect identifier      |       |    |
   Cross-connect:|(2)port identifier of one        |       |    |
   configuration |   end                           |       |    |
                 |(3)port identifier of the other  |ATM MIB|    |
                 |   end                           |    (5)|no  |
                 |(4)VPI or VPI/VCI value          |       |    |
                 |   of one end                    |       |    |
                 |(5)VPI or VPI/VCI value of       |       |    |
                 |   the other end                 |       |    |
                 |(6)VC/VP cross-connect           |       |    |
                 |   operational status            |       |    |
                 |(7)VC/VP cross-connect           |       |    |
                 |   administrative status         |       |    |
                 |(8)VC/VP last change status      |       |    |
   _____________________________________________________________
   VCC AAL5 CPCS |(1)PDUs discarded for CRC errors |ATM MIB|    |
   layer:        |(2)PDUs discarded due to         |   (6) |    |
   performance   |   reassembly time out           |       |no  |
                 |(3)PDUs discarded due to large   |       |    |
                 |   SDUs                          |       |    |
   _____________________________________________________________
   AAL5 entity:  |(1)received/transmitted PDUs     |       |    |
                 |(2)PDUs discarded due to         |       |    |
                 |   protocol errors               |MIB II |no  |
                 |(3)a set of configuration/state  |       |    |
                 |   parameters                    |       |    |
   _____________________________________________________________




Tesink                      Standards Track                    [Page 19]

RFC 2515                 ATM Management Objects            February 1999


   *The operational, administrative, and last change status of the ATM
   interface and the physical transmission type shall be supported by
   the interface table in MIB II [16][17].  ILMI does not contain the
   administrative and last change status of the ATM interface.

   ** The ILMI MIB contains read-only objects for various parameters at
   the ATM interface level.

   ***The ILMI MIBs contain local and end-to-end operational status of
   the VPC/VCC segment.  However, it does not contain the VPC/VCC
   administrative and last change status and the VCC AAL information.

9.  Definitions

     ATM-MIB DEFINITIONS ::= BEGIN

     IMPORTS
        MODULE-IDENTITY, OBJECT-TYPE,
        Counter32, Integer32, IpAddress, mib-2
            FROM SNMPv2-SMI
        DisplayString, RowStatus, TruthValue
            FROM SNMPv2-TC
        MODULE-COMPLIANCE, OBJECT-GROUP
            FROM SNMPv2-CONF
        InterfaceIndex, ifIndex
            FROM IF-MIB
        AtmAddr, AtmConnKind, AtmConnCastType,
        AtmServiceCategory, AtmTrafficDescrParamIndex,
        AtmVpIdentifier, AtmVcIdentifier,
        AtmVorXAdminStatus, AtmVorXLastChange,
        AtmVorXOperStatus, atmNoClpNoScr
            FROM ATM-TC-MIB;


     atmMIB MODULE-IDENTITY
          LAST-UPDATED "9810191200Z"
          ORGANIZATION "IETF AToM MIB Working Group"
          CONTACT-INFO
            "          Kaj Tesink
              Postal:  Bellcore
                       331 Newman Springs Road
                       Red Bank, NJ 07701
              Tel:     732-758-5254
              Fax:     732-758-2269
              E-mail:  kaj@bellcore.com"
          DESCRIPTION
           "This is the MIB Module for ATM and AAL5-related
            objects for managing ATM interfaces, ATM virtual



Tesink                      Standards Track                    [Page 20]

RFC 2515                 ATM Management Objects            February 1999


            links, ATM cross-connects, AAL5 entities, and
            and AAL5 connections."
          REVISION      "9810191200Z"
          DESCRIPTION
           "The initial revision of this module was published
            as RFC 1695. Key revisions include:
            o  Textual Conventions and OBJECT IDENTITIES have
               been moved to a separate MIB module.
            o  Applicability of objects to PVCs, SVCs and Soft
               PVCs has been clarified.
            o  DEFVAL clauses have been added.
            o  The relationship of ifIndex values with different
               layers and sublayers related to ATM has been
               clarified.
            o  atmTrafficQosClass has been deprecated
               and replaced with atmServiceCategory.
            o  atmInterfaceCurrentMaxVpiBits and
               atmInterfaceCurrentMaxVciBits have been added with
               a description on their relationship with other
               objects.
            o  atmInterfaceAddressType and atmInterfaceAdminAddress
               have been deprecated and replaced by
               atmInterfaceSubscrAddress.
            o  atmInterfaceTCAlarmState has been clarified.
            o  atmTrafficDescrParamIndexNext has been introduced
               in order to provide a manager a free
               atmTrafficDescrParamIndex value.
            o  The atmTrafficFrameDiscard capability has been added.
            o  A connection topology type (atmVpl/VclCastType) and
               a call control type (atmVpl/VclConnKind) have been
               added.
            o  aal2 has been added to atmVccAalType."
          REVISION      "9406072245Z"
          DESCRIPTION
           "The RFC1695 version of this MIB module."
          ::= { mib-2 37 }


     atmMIBObjects  OBJECT IDENTIFIER ::= {atmMIB 1}

     -- {atmMIBObjects 1} has been moved to a separate
     -- specification [19].


     -- This ATM MIB Module consists of the following tables:
     -- (1) ATM Interface configuration table
     -- (2) ATM Interface DS3 PLCP table
     -- (3) ATM Interface TC Sublayer table



Tesink                      Standards Track                    [Page 21]

RFC 2515                 ATM Management Objects            February 1999


     -- (4) Atm Traffic Descriptor table
     -- (5) ATM Interface VPL configuration table
     -- (6) ATM Interface VCL configuration table
     -- (7) ATM VP Cross Connect table (for PVCs)
     -- (8) ATM VC Cross Connect table (for PVCs)
     -- (9) ATM Interface AAL5 VCC performance statistics
     --     table

     --    ATM Interface Configuration Parameters Table

     -- This table contains ATM specific
     -- configuration information associated with
     -- an ATM interface beyond those
     -- supported using the ifTable.




     atmInterfaceConfTable  OBJECT-TYPE
          SYNTAX         SEQUENCE OF AtmInterfaceConfEntry
          MAX-ACCESS     not-accessible
          STATUS         current
          DESCRIPTION
           "This table contains ATM local interface
            configuration parameters, one entry per ATM
            interface port."
          ::= { atmMIBObjects 2 }

     atmInterfaceConfEntry    OBJECT-TYPE
          SYNTAX         AtmInterfaceConfEntry
          MAX-ACCESS     not-accessible
          STATUS         current
          DESCRIPTION
           "This list contains ATM interface configuration
            parameters and state variables and is indexed
            by ifIndex values of ATM interfaces."
          INDEX { ifIndex }
          ::= { atmInterfaceConfTable  1}

     AtmInterfaceConfEntry    ::= SEQUENCE  {
          atmInterfaceMaxVpcs             INTEGER,
          atmInterfaceMaxVccs             INTEGER,
          atmInterfaceConfVpcs            INTEGER,
          atmInterfaceConfVccs            INTEGER,
          atmInterfaceMaxActiveVpiBits    INTEGER,
          atmInterfaceMaxActiveVciBits    INTEGER,
          atmInterfaceIlmiVpi             AtmVpIdentifier,
          atmInterfaceIlmiVci             AtmVcIdentifier,



Tesink                      Standards Track                    [Page 22]

RFC 2515                 ATM Management Objects            February 1999


          atmInterfaceAddressType         INTEGER,
          atmInterfaceAdminAddress        AtmAddr,
          atmInterfaceMyNeighborIpAddress IpAddress,
          atmInterfaceMyNeighborIfName    DisplayString,
          atmInterfaceCurrentMaxVpiBits   INTEGER,
          atmInterfaceCurrentMaxVciBits   INTEGER,
          atmInterfaceSubscrAddress       AtmAddr
               }


     atmInterfaceMaxVpcs OBJECT-TYPE
          SYNTAX         INTEGER  (0..4096)
          MAX-ACCESS     read-write
          STATUS         current
          DESCRIPTION
           "The maximum number of VPCs (PVPCs and SVPCs)
            supported at this ATM interface. At the ATM UNI,
            the maximum number of VPCs (PVPCs and SVPCs)
            ranges from 0 to 256 only."
          ::= { atmInterfaceConfEntry 1}

     atmInterfaceMaxVccs OBJECT-TYPE
          SYNTAX         INTEGER  (0..65536)
          MAX-ACCESS     read-write
          STATUS         current
          DESCRIPTION
           "The maximum number of VCCs (PVCCs and SVCCs)
            supported at this ATM interface."
          ::= { atmInterfaceConfEntry 2}

     atmInterfaceConfVpcs  OBJECT-TYPE
          SYNTAX         INTEGER  (0..4096)
          MAX-ACCESS     read-only
          STATUS         current
          DESCRIPTION
           "The number of VPCs (PVPC, Soft PVPC and SVPC)
            currently in use at this ATM interface.  It includes
            the number of PVPCs and Soft PVPCs that are configured
            at the interface, plus the number of SVPCs
            that are currently  established at the
            interface.

            At the ATM UNI, the configured number of
            VPCs (PVPCs and SVPCs) can range from
            0 to 256 only."
          ::= { atmInterfaceConfEntry 3}

     atmInterfaceConfVccs  OBJECT-TYPE



Tesink                      Standards Track                    [Page 23]

RFC 2515                 ATM Management Objects            February 1999


          SYNTAX         INTEGER  (0..65536)
          MAX-ACCESS     read-only
          STATUS         current
          DESCRIPTION
           "The number of VCCs (PVCC, Soft PVCC and SVCC)
            currently in use at this ATM interface.  It includes
            the number of PVCCs and Soft PVCCs that are configured
            at the interface, plus the number of SVCCs
            that are currently  established at the
            interface."
          ::= { atmInterfaceConfEntry 4}

     atmInterfaceMaxActiveVpiBits  OBJECT-TYPE
          SYNTAX         INTEGER (0..12)
          MAX-ACCESS     read-write
          STATUS         current
          DESCRIPTION
           "The  maximum number of active VPI bits
            configured for use at the ATM interface.
            At the ATM UNI, the maximum number of active
            VPI bits configured for use ranges from
            0 to 8 only."

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -