Internet DRAFT - draft-ietf-snmp-smdsipmib

draft-ietf-snmp-smdsipmib




          Internet Draft           SIP Objects               August 1991


                   Experimental Definitions of Managed Objects
                            for the SIP Interface Type

                                   August 1991
                                    Version 3


                                SNMP Working Group

                               Kaj Tesink (editor)
                           Bell Communications Research
                             331 Newman Springs Road
                               Red Bank, NJ  07701

                            kaj@nvuxr.cc.bellcore.com






          1.  Status of this Memo

          This draft document will be submitted to the RFC editor as an
          experimental extension to the SNMP MIB.  Distribution of this
          memo is unlimited.  Please send comments to the editor.

          2.  Abstract

          This memo defines an experimental 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 SIP (SMDS Interface Protocol)
          objects.

          This memo does not specify a standard for the Internet
          community.













          Kaj Tesink (editor)                                   [Page 1]





          Internet Draft           SIP Objects               August 1991


          3.  The Network Management Framework

          The Internet-standard Network Management Framework consists of
          three components.  They are:

               RFC 1155 which defines the SMI, the mechanisms used for
               describing and naming objects for the purpose of
               management.  RFC 1212 defines a more concise description
               mechanism, which is wholly consistent with the SMI.

               RFC 1156 which defines MIB-I, the core set of managed
               objects for the Internet suite of protocols.  RFC 1213,
               defines MIB-II, an evolution of MIB-I based on
               implementation experience and new operational
               requirements.

               RFC 1157 which defines the SNMP, the protocol used for
               network access to managed objects.


          The Framework permits new objects to be defined for the
          purpose of experimentation and evaluation.




























          Kaj Tesink (editor)                                   [Page 2]





          Internet Draft           SIP Objects               August 1991


          4.  Objects

          Managed objects are accessed via a virtual information store,
          termed the Management Information Base or MIB.  Objects in the
          MIB are defined using the subset of Abstract Syntax Notation
          One (ASN.1) [7] defined in the SMI.  In particular, each
          object has a name, a syntax, and an encoding.  The name is an
          object identifier, an administratively assigned name, which
          specifies an object type.  The object type together with an
          object instance serves to uniquely identify a specific
          instantiation of the object.  For human convenience, we often
          use a textual string, termed the OBJECT DESCRIPTOR, to also
          refer to the object type.

          The syntax of an object type defines the abstract data
          structure corresponding to that object type.  The ASN.1
          language is used for this purpose.  However, the SMI [3]
          purposely restricts the ASN.1 constructs which may be used.
          These restrictions are explicitly made for simplicity.

          The encoding of an object type is simply how that object type
          is represented using the object type's syntax.  Implicitly
          tied to the notion of an object type's syntax and encoding is
          how the object type is represented when being transmitted on
          the network.  The SMI specifies the use of the basic encoding
          rules of ASN.1 [8], subject to the additional requirements
          imposed by the SNMP.

          4.1.  Format of Definitions

          Section 6 contains contains the specification of all object
          types contained in this MIB module.  The object types are
          defined using the conventions defined in the SMI, as amended
          by the extensions specified in [9].
















          Kaj Tesink (editor)                                   [Page 3]





          Internet Draft           SIP Objects               August 1991


          5.  Overview

          These objects are used when the particular media being used to
          realize an interface is a SIP interface.  At present, this
          applies to these values of the ifType variable in the
          Internet-standard MIB:

               sip (31)

          The definitions contained herein are based on the SIP
          specifications in Bellcore TR-TSV-000772 Issue 1, and TR-TSV-
          000773 Issue 1 [11,12].

          The SIP (SMDS Interface Protocol) protocol stack is defined as
          follows in [11]:

                              ____________________
                              |                   |
                              | SIP Level 3 [11]  |
                              |___________________|
                              |                   |
                              | SIP Level 2 [11]  |
                              |___________________|
                              |                   |
                              | PLCP [12]         |
                              |___________________|
                              |                   |
                              | DS1 or DS3 [12]   |
                              |___________________|

          The PLCP (Physical Layer Convergence Procedure) adapts the
          capabilities of the transmission system (DS1 or DS3 formats)
          to the service expected by SIP Level 2.  Managed objects for
          DS1 and DS3 Interface Types are defined in [13] and [14]
          respectively (and amended in [17]), and can be utilized for
          management of SIP interfaces. This document defines managed
          objects for the remaining protocol levels of the SIP Interface
          Type.  This document does not specify objects for the
          management of subscription or configuration of Subscriber
          Network Interfaces (SNIs). Those objects are defined in [18].
          Bellcore requirements on these objects are specified in [16].









          Kaj Tesink (editor)                                   [Page 4]





          Internet Draft           SIP Objects               August 1991


          6.  Object Definitions

               RFCxxxx-MIB DEFINITIONS ::= BEGIN

               IMPORTS
                       experimental, Counter, TimeTicks, IpAddress
                               FROM RFC1155-SMI
                       OBJECT-TYPE
                               FROM RFC1212;

               --  This MIB module uses the extended OBJECT-TYPE macro as
               --  defined in [9].

               --  This is the MIB module for the SIP objects.


               sip     OBJECT IDENTIFIER ::= { experimental 16 }

               -- All representations of SMDS addresses in this MIB module use,
               -- as a textual convention (i.e., this convention does not affect
               -- their encoding), the data type:

               SMDSAddress ::= OCTET STRING (SIZE (8))
               -- the 60-bit SMDS address, preceded by 4 bits with the
               -- following values:
               -- "1100" when representing an individual address
               -- "1110" when representing a group address























          Kaj Tesink (editor)                                   [Page 5]





          Internet Draft           SIP Objects               August 1991


          6.1.  The SIP Level 3 group

          -- The SIP Level 3 group
          -- Implementation of the SIP Level 3 group is mandatory
          -- for all systems implementing SIP Level 3.

          sipL3Table  OBJECT-TYPE
              SYNTAX  SEQUENCE OF SIPL3Entry
              ACCESS  not-accessible
              STATUS  mandatory
              DESCRIPTION
                      "This table contains SIP-L3 parameters and state
                      variables, one entry per SIP port."
              ::= { sip 1 }

          sipL3Entry  OBJECT-TYPE
              SYNTAX  SIPL3Entry
              ACCESS  not-accessible
              STATUS  mandatory
              DESCRIPTION
                      "This list contains SIP L3 parameters and state
                      variables."
              INDEX   { sipL3Index }
              ::= { sipL3Table 1 }

          SIPL3Entry  ::= SEQUENCE {
              sipL3Index
                  INTEGER,
              receivedIndividualDAedSIPL3PDUs
                  Counter,
              receivedGAedSIPL3PDUs
                  Counter,
              sentIndividualDAedSIPL3PDUs
                  Counter,
              sentGAedSIPL3PDUs
                  Counter,
              erroredSIPL3PDUs
                  Counter,
              unrecognizedDestinationAddresses
                  Counter,
              unrecognizedGroupAddresses
                  Counter,
              invalidSMDSAddressTypes
                  Counter,
              versionSupport





          Kaj Tesink (editor)                                   [Page 6]





          Internet Draft           SIP Objects               August 1991


                  INTEGER
              }


          sipL3Index  OBJECT-TYPE
              SYNTAX  INTEGER
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The value of this object identifies the SIP port
                      interface for which this entry contains management
                      information.  The value of this object for a
                      particular interface has the same value as the
                      ifIndex object, defined in [4,6], for the same
                      interface."
              ::= { sipL3Entry 1 }

          receivedIndividualDAedSIPL3PDUs OBJECT-TYPE
              SYNTAX  Counter
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The total number of SIP Level 3 PDUs received
                      from the remote system across the SNI and
                      containing an individual destination address.  The
                      total includes only unerrored L3-PDUs."
              ::= { sipL3Entry 2 }

          receivedGAedSIPL3PDUs OBJECT-TYPE
              SYNTAX  Counter
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The total number of SIP Level 3 PDUs received
                      from the remote system across the SNI and
                      containing an group destination address.  The
                      total  includes only unerrored L3-PDUs."
              ::= { sipL3Entry 3 }

          sentIndividualDAedSIPL3PDUs OBJECT-TYPE
              SYNTAX  Counter
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The number of SIP Level 3 PDUs that have been





          Kaj Tesink (editor)                                   [Page 7]





          Internet Draft           SIP Objects               August 1991


                      sent by this system across the SNI and that
                      contain an individual destination address."
              ::= { sipL3Entry 4 }

          sentGAedSIPL3PDUs OBJECT-TYPE
              SYNTAX  Counter
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The number of group addressed SIP L3-PDUs that
                      have been sent by this system across the SNI."
              ::= { sipL3Entry 5 }


          -- The total number of SIPL3-PDU errors can be calculated as
          -- (Syntactic errors + Semantic Service errors )
          -- Syntactic errors include:
          --    erroredSIPL3PDUs
          -- Latest occurrences of syntactic error types are logged in
          --    sipL3PDUErrorTable.
          -- Semantic Service errors include:
          --    unrecognizedDestinationAddresses
          --    unrecognizedGroupAddresses
          --    invalidSMDSAddressTypes
          -- Note that public networks supporting SMDS may discard
          -- SIPL3-PDUs due to subscription violations. Related
          -- managed objects are defined in [18].

          erroredSIPL3PDUs OBJECT-TYPE
              SYNTAX  Counter
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The total number of SIP Level 3 PDUs received
                      from the remote system that were discovered to
                      have errors (including protocol processing and bit
                      errors but excluding addressing-related errors)
                      and were discarded.  Includes both group addressed
                      L3-PDUs and L3-PDUs containing an individual
                      destination address."
              ::= { sipL3Entry 6 }

          unrecognizedDestinationAddresses OBJECT-TYPE
              SYNTAX  Counter
              ACCESS  read-only





          Kaj Tesink (editor)                                   [Page 8]





          Internet Draft           SIP Objects               August 1991


              STATUS  mandatory
              DESCRIPTION
                      "The number of SIP Level 3 PDUs received from the
                      remote system with invalid or unknown destination
                      addresses (Source or Destination Address Screening
                      violations are not included)."
              ::= { sipL3Entry 7 }

          unrecognizedGroupAddresses OBJECT-TYPE
              SYNTAX  Counter
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The number of SIP Level 3 PDUs received from the
                      remote system with invalid or unknown group
                      addresses."
              ::= { sipL3Entry 8 }

          invalidSMDSAddressTypes OBJECT-TYPE
              SYNTAX  Counter
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The number of SIP Level 3 PDUs received from the
                      remote system with invalid or unknown destination
                      addresses (Source or Destination Address Screening
                      violations are not included)."
              ::= { sipL3Entry 9 }

          versionSupport  OBJECT-TYPE
              SYNTAX  INTEGER
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "A value which indicates the version(s) of SIP
                      that this interface supports.  The value is a sum.
                      This sum initially takes the value zero.  For each
                      version, V, that this interface supports, 2 raised
                      to (V - 1) is added to the sum. For example, a
                      port supporting versions 1 and 2 would have a
                      value of (2^(1-1)+2^(2-1))=3."
              ::= { sipL3Entry 10 }








          Kaj Tesink (editor)                                   [Page 9]





          Internet Draft           SIP Objects               August 1991


          6.2.  The SIP Level 2 group

          -- The SIP Level 2 group
          -- Implementation of the SIP Level 2 group is mandatory
          -- for all systems implementing SIP Level 2.


          sipL2Table  OBJECT-TYPE
              SYNTAX  SEQUENCE OF SIPL2Entry
              ACCESS  not-accessible
              STATUS  mandatory
              DESCRIPTION
                      "This table contains SIP-L2 parameters and state
                      variables, one entry per SIP port."
              ::= { sip 2 }

          sipL2Entry  OBJECT-TYPE
              SYNTAX  SIPL2Entry
              ACCESS  not-accessible
              STATUS  mandatory
              DESCRIPTION
                      "This list contains SIP L2 parameters and state
                      variables."
              INDEX   { sipL2Index }
              ::= { sipL2Table 1 }

          SIPL2Entry  ::= SEQUENCE {
              sipL2Index
                  INTEGER,
              receivedSIPL2PDUs
                  Counter,
              sentSIPL2PDUs
                  Counter,
              hcsOrCRCErrors
                  Counter,
              payloadLengthErrors
                  Counter,
              sequenceNumberErrors
                  Counter,
              midCurrentlyActiveErrors
                  Counter,
              bomOrSSMsMIDErrors
                  Counter,
              eomsMIDErrors
                  Counter





          Kaj Tesink (editor)                                  [Page 10]





          Internet Draft           SIP Objects               August 1991


              }


          sipL2Index  OBJECT-TYPE
              SYNTAX  INTEGER
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The value of this object identifies the SIP port
                      interface for which this entry contains management
                      information.  The value of this object for a
                      particular interface has the same value as the
                      ifIndex object, defined in [4,6], for the same
                      interface."
              ::= { sipL2Entry 1 }

          receivedSIPL2PDUs OBJECT-TYPE
              SYNTAX  Counter
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The number of SIP Level 2 PDUs received from the
                      remote system across the SNI. The total includes
                      only unerrored L2-PDUs."
              ::= { sipL2Entry 2 }

          sentSIPL2PDUs OBJECT-TYPE
              SYNTAX  Counter
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The number of SIP Level 2 PDUs that have been
                      sent by this system across the SNI."
              ::= { sipL2Entry 3 }

          -- The total number of SIPL2-PDU errors can be calculated as the
          -- sum of:
          --    hcsOrCRCErrors
          --    payloadLengthErrors
          --    sequenceNumberErrors
          --    midCurrentlyActiveErrors
          --    bomOrSSMsMIDErrors
          --    eomsMIDErrors

          hcsOrCRCErrors  OBJECT-TYPE





          Kaj Tesink (editor)                                  [Page 11]





          Internet Draft           SIP Objects               August 1991


              SYNTAX  Counter
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The number of received SIP Level 2 PDUs that were
                      discovered to have either a Header Check Sequence
                      error or a Payload CRC violation."
              ::= { sipL2Entry 4 }

          payloadLengthErrors  OBJECT-TYPE
              SYNTAX  Counter
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The number of received SIP Level 2 PDUs that had
                      Payload Length errors that fall in the following
                      specifications:
                      - Payload length field value not equal to a
                      - multiple of 4 octets,

                      - SSM L2_PDU payload length field value less
                      - than 28 octets or greater than 44 octets,

                      - BOM or COM L2_PDU payload length field not
                      - equal to 44 octets,

                      - EOM L2_PDU payload length field value less
                      - than 4 octets or greater than 44 octets."
              ::= { sipL2Entry 5 }

          sequenceNumberErrors  OBJECT-TYPE
              SYNTAX  Counter
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The number of received SIP Level 2 PDUs that had
                      a sequence number within the L2_PDU not equal to
                      the expected sequence number of the SMDS SS
                      receive process."
              ::= { sipL2Entry 6 }

          midCurrentlyActiveErrors  OBJECT-TYPE
              SYNTAX Counter
              ACCESS  read-only
              STATUS  mandatory





          Kaj Tesink (editor)                                  [Page 12]





          Internet Draft           SIP Objects               August 1991


              DESCRIPTION
                      "The number of received SIP Level 2 PDUs that are
                      BOMs for which an active receive process is
                      already started."
              ::= { sipL2Entry 7 }

          bomOrSSMsMIDErrors  OBJECT-TYPE
              SYNTAX  Counter
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The number of received SIP Level 2 PDUs that are
                      SSMs with a MID not equal to zero or are BOMs with
                      MIDs equal to zero."
              ::= { sipL2Entry 8 }

          eomsMIDErrors  OBJECT-TYPE
              SYNTAX  Counter
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The number of received SIP Level 2 PDUs that are
                      EOMs for which there is no active receive process
                      for the MID (i.e., the receipt of an EOM which
                      does not correspond to a BOM) OR the EOM has a MID
                      equal to zero."
              ::= { sipL2Entry 9 }























          Kaj Tesink (editor)                                  [Page 13]





          Internet Draft           SIP Objects               August 1991


          6.3.  The SIP PLCP group

          -- The SIP PLCP group
          -- Implementation of one of these groups is mandatory
          -- if the PLCP is implemented.

          sipPLCP OBJECT IDENTIFIER ::= { sip 3 }











































          Kaj Tesink (editor)                                  [Page 14]





          Internet Draft           SIP Objects               August 1991


          6.3.1.  The SIP DS1 PLCP group

          -- The SIP DS1 PLCP group
          -- Implementation of this group is mandatory
          -- if the DS1 PLCP is implemented.

          sipDS1PLCPTable  OBJECT-TYPE
              SYNTAX  SEQUENCE OF SIPDS1PLCPEntry
              ACCESS  not-accessible
              STATUS  mandatory
              DESCRIPTION
                      "This table contains SIP DS1-PLCP parameters and
                      state variables, one entry per SIP port."
              ::= { sipPLCP 1 }

          sipDS1PLCPEntry  OBJECT-TYPE
              SYNTAX  SIPDS1PLCPEntry
              ACCESS  not-accessible
              STATUS  mandatory
              DESCRIPTION
                      "This list contains SIP DS1-PLCP parameters and
                      state variables."
              INDEX   { sipDS1PLCPIndex }
              ::= { sipDS1PLCPTable 1 }

          SIPDS1PLCPEntry  ::= SEQUENCE {
              sipDS1PLCPIndex
                  INTEGER,
              ds1PLCPSEFSs
                  Counter,
              ds1PLCPYellowSignal
                  INTEGER,
              ds1PLCPRedAlarm
                  INTEGER,
              ds1PLCPUASs
                  Counter
              }


          sipDS1PLCPIndex  OBJECT-TYPE
              SYNTAX  INTEGER
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The value of this object identifies the SIP port





          Kaj Tesink (editor)                                  [Page 15]





          Internet Draft           SIP Objects               August 1991


                      interface for which this entry contains management
                      information.  The value of this object for a
                      particular interface has the same value as the
                      ifIndex object, defined in [4,6], for the same
                      interface."
              ::= { sipDS1PLCPEntry 1 }


          ds1PLCPSEFSs OBJECT-TYPE
              SYNTAX  Counter
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "A DS1 Severely Errored Framing Second (SEFS) is a
                      count of one-second intervals containing one or
                      more SEF events.  A Severely Errored Framing (SEF)
                      event is declared when an error in the A1 octet
                      and an error in the A2 octet of a framing octet
                      pair (i.e., errors in both framing octets), or two
                      consecutive invalid and/or nonsequential Path
                      Overhead Identifier octets are detected."
              ::= { sipDS1PLCPEntry 2 }

          ds1PLCPYellowSignal OBJECT-TYPE
              SYNTAX  INTEGER {
                          ds1PLCPYellowSignal(1),
                          ds1PLCPNoYellowSignal(2)
                      }
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "This variable indicates if a Yellow Signal is
                      received as defined in [12]."
              ::= { sipDS1PLCPEntry 3 }

          ds1PLCPRedAlarm OBJECT-TYPE
              SYNTAX  INTEGER {
                          ds1PLCPRedAlarm(1),
                          ds1PLCPNoRedAlarm(2)
                      }
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "This variable indicates if a Red Alarm condition
                      exists.  A Red Alarm condition is sent when the





          Kaj Tesink (editor)                                  [Page 16]





          Internet Draft           SIP Objects               August 1991


                      declaration of a PLCP Loss of Frame failure
                      condition occurs as defined in [12]."
              ::= { sipDS1PLCPEntry 4 }

          ds1PLCPUASs OBJECT-TYPE
              SYNTAX  Counter
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The counter associated with the number of
                      Unavailable Seconds, as defined by [12],
                      encountered by the PLCP."
              ::= { sipDS1PLCPEntry 5 }





































          Kaj Tesink (editor)                                  [Page 17]





          Internet Draft           SIP Objects               August 1991


          6.3.2.  The SIP DS3 PLCP group

          -- The SIP DS3-PLCP group
          -- Implementation of this group is mandatory
          -- if the DS3 PLCP is implemented.

          sipDS3PLCPTable  OBJECT-TYPE
              SYNTAX  SEQUENCE OF SIPDS1PLCPEntry
              ACCESS  not-accessible
              STATUS  mandatory
              DESCRIPTION
                      "This table contains SIP DS3-PLCP parameters and
                      state variables, one entry per SIP port."
              ::= { sipPLCP 2 }

          sipDS3PLCPEntry  OBJECT-TYPE
              SYNTAX  SIPDS3PLCPEntry
              ACCESS  not-accessible
              STATUS  mandatory
              DESCRIPTION
                      "This list contains SIP DS3-PLCP parameters and
                      state variables."
              INDEX   { sipDS3PLCPIndex }
              ::= { sipDS3PLCPTable 1 }

          SIPDS3PLCPEntry  ::= SEQUENCE {
              sipDS3PLCPIndex
                  INTEGER,
              ds3PLCPSEFSs
                  Counter,
              ds3PLCPYellowSignal
                  INTEGER,
              ds3PLCPRedAlarm
                  INTEGER,
              ds3PLCPUASs
                  Counter
              }


          sipDS3PLCPIndex  OBJECT-TYPE
              SYNTAX  INTEGER
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The value of this object identifies the SIP port





          Kaj Tesink (editor)                                  [Page 18]





          Internet Draft           SIP Objects               August 1991


                      interface for which this entry contains management
                      information.  The value of this object for a
                      particular interface has the same value as the
                      ifIndex object, defined in [4,6], for the same
                      interface."
              ::= { sipDS3PLCPEntry 1 }

          ds3PLCPSEFSs OBJECT-TYPE
              SYNTAX  Counter
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "A DS3 Severely Errored Framing Second (SEFS) is a
                      count of one-second intervals containing one or
                      more SEF events.  A Severely Errored Framing (SEF)
                      event is declared when an error in the A1 octet
                      and an error in the A2 octet of a framing octet
                      pair (i.e., errors in both framing octets), or two
                      consecutive invalid and/or nonsequential Path
                      Overhead Identifier octets are detected."
              ::= { sipDS3PLCPEntry 2 }

          ds3PLCPYellowSignal OBJECT-TYPE
              SYNTAX  INTEGER {
                          ds3PLCPYellowSignal(1),
                          ds3PLCPNoYellowSignal(2)
                      }
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "This variable indicates if a Yellow Signal is
                      received as defined in [12]."
              ::= { sipDS3PLCPEntry 3 }

          ds3PLCPRedAlarm OBJECT-TYPE
              SYNTAX  INTEGER {
                          ds3PLCPRedAlarm(1),
                          ds3PLCPNoRedAlarm(2)
                      }
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "This variable indicates if a Red Alarm condition
                      exists.  A Red Alarm condition is sent when the
                      declaration of a PLCP Loss of Frame failure





          Kaj Tesink (editor)                                  [Page 19]





          Internet Draft           SIP Objects               August 1991


                      condition occurs as defined in [12]."
              ::= { sipDS3PLCPEntry 4 }

          ds3PLCPUASs OBJECT-TYPE
              SYNTAX  Counter
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The counter associated with the number of
                      Unavailable Seconds, as defined by [12],
                      encountered by the PLCP."
              ::= { sipDS3PLCPEntry 5 }






































          Kaj Tesink (editor)                                  [Page 20]





          Internet Draft           SIP Objects               August 1991


          6.4.  The SMDS Applications group

          -- The SMDS Applications group
          -- Applications that have been identified for this group are:
          --          * IP-over-SMDS (details are specified in [15])
          -- Implementation of this group is mandatory for systems
          -- that implement IP over SMDS Interface Protocol.

          smdsApplications OBJECT IDENTIFIER ::= { sip 4 }

          ipOverSMDS OBJECT IDENTIFIER ::= { smdsApplications 1 }

          -- Although the objects in this group are read-only, at the
          -- agent's discretion they may be made read-write so that the
          -- management station, when appropriately authorized, may
          -- change the addressing information related to the configuration
          -- of a logical IP subnetwork over SMDS.

          ipOverSMDSAddressTable OBJECT-TYPE
              SYNTAX  SEQUENCE OF IpOverSMDSAddressEntry
              ACCESS  not-accessible
              STATUS  mandatory
              DESCRIPTION
                      "The table of addressing information relevant to
                      this entity's IP addresses."
              ::= { ipOverSMDS 1 }

          ipOverSMDSAddressEntry OBJECT-TYPE
              SYNTAX  IpOverSMDSAddressEntry
              ACCESS  not-accessible
              STATUS  mandatory
              DESCRIPTION
                      "The addressing information for one of this
                      entity's IP addresses."
              INDEX   { ipEntryAddressIfIndex, ipEntryAddress }
              ::= { ipOverSMDSAddressTable 1 }

          IpOverSMDSAddressEntry ::=
              SEQUENCE {
                 ipEntryAddressIfIndex
                     INTEGER,
                 ipEntryAddress
                     IpAddress,
                 smdsHA
                     SMDSAddress,





          Kaj Tesink (editor)                                  [Page 21]





          Internet Draft           SIP Objects               August 1991


                 smdsLISGA
                     SMDSAddress,
                 smdsARPReq
                     SMDSAddress
                 }

          ipEntryAddressIfIndex OBJECT-TYPE
              SYNTAX  INTEGER
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The value of this object identifies the SIP port
                      interface for which this entry contains management
                      information.  The value of this object for a
                      particular interface has the same value as the
                      ifIndex object, defined in [4,6], for the same
                      interface."
              ::= { ipOverSMDSAddressEntry 1 }

          ipEntryAddress OBJECT-TYPE
               SYNTAX  IpAddress
               ACCESS  read-only
               STATUS  mandatory
               DESCRIPTION
                      "The IP address to which this entry's addressing
                      information pertains."
              ::= { ipOverSMDSAddressEntry 2 }

          smdsHA OBJECT-TYPE
               SYNTAX  SMDSAddress
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The SMDS Individual address of the IP station."
              ::= { ipOverSMDSAddressEntry 3 }

          smdsLISGA OBJECT-TYPE
              SYNTAX  SMDSAddress
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The SMDS Group Address that has been configured
                      to identify the SMDS Subscriber Network Interfaces
                      (SNIs) of all members of the Logical IP Subnetwork
                      (LIS) connected to the SMDS Service."





          Kaj Tesink (editor)                                  [Page 22]





          Internet Draft           SIP Objects               August 1991


              ::= { ipOverSMDSAddressEntry 4 }

          smdsARPReq OBJECT-TYPE
              SYNTAX  SMDSAddress
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The SMDS address (individual or group) to which
                      ARP Requests are to be sent."
              ::= { ipOverSMDSAddressEntry 5 }








































          Kaj Tesink (editor)                                  [Page 23]





          Internet Draft           SIP Objects               August 1991


          6.5.  The SMDS Carrier Selection group

          -- The SMDS Carrier Selection group
          -- This group is used as a place holder
          -- for carrier selection objects.

          smdsCarrierSelection OBJECT IDENTIFIER ::= { sip 5}











































          Kaj Tesink (editor)                                  [Page 24]





          Internet Draft           SIP Objects               August 1991


          6.6.  The SIP Error Log group

          -- The SIP Error Log
          -- Implementation of this group is mandatory
          -- for all systems that implement SIP Level 3.

          sipErrorLog OBJECT IDENTIFIER ::= { sip 6 }

          sipL3PDUErrorTable OBJECT-TYPE
              SYNTAX  SEQUENCE OF SIPL3PDUErrorEntry
              ACCESS  not-accessible
              STATUS  mandatory
              DESCRIPTION
                      "A table that contains the latest occurrence of
                      the following syntactical SIPL3PDU errors:

                      - Destination Address Field Format Error,
                      The following pertains to the 60 least significant
                      bits of the 64 bit address field.  For initial
                      availability of SMDS, the address shall use 10
                      digits.  An error is considered to have occurred
                      if the four most significant bits of the Address
                      subfield are not populated with the value 0001, OR
                      the 40 bits which follow are not Binary Coded
                      Decimal (BCD) encoded values of 10 digits, OR the
                      remaining 16 least significant bits are not
                      populated with 1's.

                      - Source Address Field Format Error,
                      The description of this parameter is the same as
                      the description of the Destination Address Field
                      Format Error parameter.

                      - Invalid BAsize Field Value,
                      An error is considered to have occurred when the
                      BAsize field of an SIPL3PDU contains a value less
                      that 32, greater than 9220 octets without the
                      CRC32 field present, or greater than 9224 octets
                      with the CRC32 field present.

                      - Invalid Header Extension Length Field Value,
                      An error is considered to have occurred when the
                      Header Extension Length field value is not equal
                      3.






          Kaj Tesink (editor)                                  [Page 25]





          Internet Draft           SIP Objects               August 1991


                      - Invalid Header Extension - Element Length,
                      An error is considered to have occurred when the
                      Header Extension - Element Length is greater than
                      12.

                      - Invalid Header Extension - Version Element
                      Position, Length, or Value,
                      An error is considered to have occurred when a
                      Version element with Length=3, Type=0, and Value=1
                      does not appear first within the Header Extension,
                      or an element Type=0 appears somewhere other than
                      within the first three octets in the Header
                      Extension.

                      - Invalid Header Extension - Carrier Selection
                      Element Position, Length, Value or Format,
                      An error is considered to have occurred when a
                      Carrier Selection element does not appear second
                      within the Header Extension, if the Element Type
                      does not equal 1, the Element Length does not
                      equal 4, 6, or 8, the Element Value field is not
                      four BCD encoded decimal digits used in specifying
                      the Carrier Identification Code (CIC), or the
                      identified CIC code is invalid.

                      - Header Extension PAD Error
                      An error is considered to have occurred when the
                      Header Extension PAD is 9 octets in length, or if
                      the Header Extension PAD is greater than zero
                      octets in length and the Header Extension PAD does
                      not follow all Header Extension elements or does
                      not begin with at least one octet of all zeros.

                      - BEtag Mismatch Error,
                      An error is considered to have occurred when the
                      Beginning-End Tags in the SIPL3PDU header and
                      trailer are not equal.

                      - BAsize Field not equal to Length Field Error,
                      An error is considered to have occurred when the
                      value of the BAsize Field does not equal the value
                      of the Length Field.

                      - Incorrect Length Error, and
                      An error is considered to have occurred when the





          Kaj Tesink (editor)                                  [Page 26]





          Internet Draft           SIP Objects               August 1991


                      the Length field value is not equal to the portion
                      of the SIPL3PDU which extends from the Destination
                      Address field up to and including the CRC32 field
                      (if present) or up to and including the PAD field
                      (if the CRC32 field is not present).

                      - MRI Timeout Error.
                      An error is considered to have occurred when the
                      elapsed time between receipt of BOM and
                      corresponding EOM exceeds the value of the MRI for
                      a particular transport signal format.

                      An entry is indexed by interface number and error
                      type, and contains Source Address, Destination
                      Address and a timestamp. All these errors are
                      counted in the erroredSIPL3PDUs counter.  When
                      sipL3PDUErrorTimeStamp is equal to zero, the
                      sipErrorLog does not contain any information."
              ::= { sipErrorLog 1 }

          sipL3PDUErrorEntry  OBJECT-TYPE
              SYNTAX SIPL3PDUErrorEntry
              ACCESS  not-accessible
              STATUS  mandatory
              DESCRIPTION
                      "An entry in the service disagreement table."
              INDEX   { sipL3PDUErrorIndex, sipL3PDUErrorType }
              ::= { sipL3PDUErrorTable 1 }

          SIPL3PDUErrorEntry ::= SEQUENCE {
              sipL3PDUErrorIndex
                  INTEGER,
              sipL3PDUErrorType
                  INTEGER,
              erroredL3PDUSourceAddress
                  SMDSAddress,
              erroredL3PDUDestinationAddress
                  SMDSAddress,
              sipL3PDUErrorTimeStamp
                  TimeTicks
              }

          sipL3PDUErrorIndex OBJECT-TYPE
              SYNTAX  INTEGER
              ACCESS  read-only





          Kaj Tesink (editor)                                  [Page 27]





          Internet Draft           SIP Objects               August 1991


              STATUS  mandatory
              DESCRIPTION
                      "The value of this object identifies the SIP port
                      interface for which this entry contains management
                      information.   The value of this object for a
                      particular interface has the same value as the
                      ifIndex object, defined in [4,6], for the same
                      interface."
              ::= { sipL3PDUErrorEntry 1 }

           sipL3PDUErrorType OBJECT-TYPE
              SYNTAX  INTEGER {
                   erroredDAFieldFormat (1),
                   erroredSAFieldFormat (2),
                   invalidBAsizeFieldValue (3),
                   invalidHdrExtLength (4),
                   invalidHdrExtElementLength (5),
                   invalidHdrExtVersionElementPositionLenthOrValue (6),
                   invalidHdrExtCarSelectElementPositionLenghtValueOrFormat (7),
                   hePADError (8),
                   beTagMismatch (9),
                   baSizeFieldNotEqualToLengthField (10),
                   incorrectLength (11),
                   mriTimeout (12)
              }
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The type of error."
              ::= { sipL3PDUErrorEntry 2 }

          erroredL3PDUSourceAddress OBJECT-TYPE
              SYNTAX  SMDSAddress
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "A rejected SMDS source address."
              ::= { sipL3PDUErrorEntry 3 }

          erroredL3PDUDestinationAddress OBJECT-TYPE
              SYNTAX  SMDSAddress
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "A rejected SMDS destination address."





          Kaj Tesink (editor)                                  [Page 28]





          Internet Draft           SIP Objects               August 1991


              ::= { sipL3PDUErrorEntry 4 }

          sipL3PDUErrorTimeStamp OBJECT-TYPE
              SYNTAX  TimeTicks
              ACCESS  read-only
              STATUS  mandatory
              DESCRIPTION
                      "The timestamp for the service disagreement.  The
                      timestamp contains the value of sysUpTime at the
                      latest occurrence of this type of service
                      disagreement.  See textual description under
                      sipL3PDUErrorTable for boundary conditions."
              ::= { sipL3PDUErrorEntry 5 }

          END



































          Kaj Tesink (editor)                                  [Page 29]





          Internet Draft           SIP Objects               August 1991


          7.  Acknowledgments

          This document was produced by the SNMP Working Group:


          In addition, the comments of the following individuals are
          also acknowledged: Ted Brunner, Jeff Case, Tracy Cox, Sherri
          Hiller, Steve Jaffe, Deirdre Kostick, Dave Piscitello, and Ron
          Reuss.









































          Kaj Tesink (editor)                                  [Page 30]





          Internet Draft           SIP Objects               August 1991


          8.  References

          [1]  V. Cerf, IAB Recommendations for the Development of
               Internet Network Management Standards.  Internet Working
               Group Request for Comments 1052.  Network Information
               Center, SRI International, Menlo Park, California,
               (April, 1988).

          [2]  V. Cerf, Report of the Second Ad Hoc Network Management
               Review Group, Internet Working Group Request for Comments
               1109.  Network Information Center, SRI International,
               Menlo Park, California, (August, 1989).

          [3]  M.T. Rose and K. McCloghrie, Structure and Identification
               of Management Information for TCP/IP-based internets,
               Internet Working Group Request for Comments 1155.
               Network Information Center, SRI International, Menlo
               Park, California, (May, 1990).

          [4]  K. McCloghrie and M.T. Rose, Management Information Base
               for Network Management of TCP/IP-based internets,
               Internet Working Group Request for Comments 1156.
               Network Information Center, SRI International, Menlo
               Park, California, (May, 1990).

          [5]  J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin,
               Simple Network Management Protocol, Internet Working
               Group Request for Comments 1157.  Network Information
               Center, SRI International, Menlo Park, California, (May,
               1990).

          [6]  M.T. Rose (editor), Management Information Base for
               Network Management of TCP/IP-based internets, Internet
               Working Group Request for Comments 1213.  Network
               Information Center, SRI International, Menlo Park,
               California, (March, 1991).

          [7]  Information processing systems - Open Systems
               Interconnection - Specification of Abstract Syntax
               Notation One (ASN.1), International Organization for
               Standardization.  International Standard 8824, (December,
               1987).

          [8]  Information processing systems - Open Systems
               Interconnection - Specification of Basic Encoding Rules





          Kaj Tesink (editor)                                  [Page 31]





          Internet Draft           SIP Objects               August 1991


               for Abstract Notation One (ASN.1), International
               Organization for Standardization.  International Standard
               8825, (December, 1987).

          [9]  M.T. Rose, K. McCloghrie (editors), Concise MIB
               Definitions, Internet Working Group Request for Comments
               1212.  Network Information Center, SRI International,
               Menlo Park, California, (March, 1991).

          [10] M.T. Rose (editor), A Convention for Defining Traps for
               use with the SNMP, Internet Working Group Request for
               Comments 1215.  Network Information Center, SRI
               International, Menlo Park, California, (March, 1991).

          [11] Generic System Requirements in Support of Switched
               Multi-megabit Data Service, Bellcore Technical Reference,
               TR-TSV-000772, Issue 1, May 1991.

          [12] Local Access System Generic Requirements, Objectives, and
               Interfaces in Support of Switched Multi-megabit Data
               Service, Bellcore Technical Reference, TR-TSV-000773,
               Issue 1, June 1990.

          [13] F. Baker and C. Kolb (editors), Definitions of Managed
               Objects for the DS1 Interface Type, Internet Working
               Group Request for Comments 1232.  Network Information
               Center, SRI International, Menlo Park, California, (May,
               1991).

          [14] T. A. Cox and K. Tesink (editors), Definitions of Managed
               Objects for the DS3 Interface Type, Internet Working
               Group Request for Comments 1233.  Network Information
               Center, SRI International, Menlo Park, California, (May,
               1991).

          [15] Dave Piscitello and Joseph Lawrence (editors), The
               Transmission of IP Datagrams over the SMDS Service,
               Internet Working Group Request for Comments 1209, Network
               Information Center, SRI International, Menlo Park, CA,
               (March, 1991).

          [16] Generic Requirements For SMDS Customer Network Management
               Service, TA-TSV-001062, Issue 1, February 1991, and
               Supplement 1, April 1991.






          Kaj Tesink (editor)                                  [Page 32]





          Internet Draft           SIP Objects               August 1991


          [17] J. Reynolds, Reassignment of Experimental MIBs to
               Standard MIBs, Internet Working Group Request for
               Comments 1239.  Network Information Center, SRI
               International, Menlo Park, California, (June, 1991).

          [18] K. Tesink, Definitions of Managed Objects for SMDS
               Subscription, Version 1.0, Bellcore, March 1991.











































          Kaj Tesink (editor)                                  [Page 33]





          Internet Draft           SIP Objects               August 1991


          Table of Contents


          1 Status of this Memo ...................................    1
          2 Abstract ..............................................    1
          3 The Network Management Framework ......................    2
          4 Objects ...............................................    3
          4.1 Format of Definitions ...............................    3
          5 Overview ..............................................    4
          6 Object Definitions ....................................    5
          6.1 The SIP Level 3 group ...............................    6
          6.2 The SIP Level 2 group ...............................   10
          6.3 The SIP PLCP group ..................................   14
          6.3.1 The SIP DS1 PLCP group ............................   15
          6.3.2 The SIP DS3 PLCP group ............................   18
          6.4 The SMDS Applications group .........................   21
          6.5 The SMDS Carrier Selection group ....................   24
          6.6 The SIP Error Log group .............................   25
          7 Acknowledgments .......................................   30
          8 References ............................................   31






























          Kaj Tesink (editor)                                  [Page 34]