rfc3202.txt

RFC 的详细文档！

         frsldPvcSmplFrDeliveredE, or frsldPvcSmplHCFrDeliveredE.

   o  FrOfferedC

         The number of frames offered by the transmitting device through
         the transmit reference point that were sent within CIR.  This
         is represented within the MIB module by one of
         frsldPvcDataFrOfferedC, frsldPvcDataHCFrOfferedC,
         frsldPvcSmplFrOfferedC, or frsldPvcSmplHCFrOfferedC.







Steinberger & Nicklass      Standards Track                    [Page 18]

RFC 3202           Frame Relay Service Level Defs MIB       January 2002


   o  FrOfferedE

         The number of frames offered by the transmitting device through
         the transmit reference point that were sent in excess of CIR.
         This is represented within the MIB module by one of
         frsldPvcDataFrOfferedE, frsldPvcDataHCFrOfferedE,
         frsldPvcSmplFrOfferedE, or frsldPvcSmplHCFrOfferedE.

   o  DataDeliveredC

         The number of octets received by the receiving device through
         the receive reference point that were delivered within CIR.
         This is represented within the MIB module by one of
         frsldPvcDataDataDeliveredC, frsldPvcDataHCDataDeliveredC,
         frsldPvcSmplDataDeliveredC, or frsldPvcSmplHCDataDeliveredC.

   o  DataDeliveredE

         The number of octets received by the receiving device through
         the receive reference point that were delivered in excess of
         CIR.  This is represented within the MIB module by one of
         frsldPvcDataDataDeliveredE, frsldPvcDataHCDataDeliveredE,
         frsldPvcSmplDataDeliveredE, or frsldPvcSmplHCDataDeliveredE.

   o  DataOfferedC

         The number of octets offered by the transmitting device through
         the transmit reference point that were sent within CIR.  This
         is represented within the MIB module by one of
         frsldPvcDataDataOfferedC, frsldPvcDataHCDataOfferedC,
         frsldPvcSmplDataOfferedC, or frsldPvcSmplHCDataOfferedC.

   o  DataOfferedE

         The number of octets offered by the transmitting device through
         the transmit reference point that were sent in excess of CIR.
         This is represented within the MIB module by one of
         frsldPvcDataDataOfferedE, frsldPvcDataHCDataOfferedE,
         frsldPvcSmplDataOfferedE, or frsldPvcSmplHCDataOfferedE.

   o  UnavailableTime

         The amount of time the PVC was not available during the
         interval of interest.  This is represented within the MIB
         module by either frsldPvcDataUnavailableTime or
         frsldPvcSmplUnavailableTime.





Steinberger & Nicklass      Standards Track                    [Page 19]

RFC 3202           Frame Relay Service Level Defs MIB       January 2002


   o  Unavailables

         The number of times the PVC was declared to be unavailable
         during the interval of interest.  This is represented within
         the MIB module by either frsldPvcDataUnavailables or
         frsldPvcSmplUnavailables.

3.6.8.  Delay

   The frame transfer delay is defined as the amount of time elapsed, in
   microseconds, from the time a frame exits the source to the time it
   reaches the destination.  The average delay can be found using the
   MIB variable described in DelayAvg above.  The delay may be
   calculated as either round trip or one way, and this information is
   held in the frsldPvcCtrlDelayType MIB variable.  If the delay be
   calculated as round trip, the value of DelayAvg represents the
   average of the total delays of the round trips.  In this case, the
   manager SHOULD divide the value returned by the agent by two to
   obtain the frame transfer delay.  In the case that
   frsldPvcCtrlDelayType is oneWay, the value of DelayAvg represents the
   average of the frame transfer delays and SHOULD be used as is.

3.6.9.  Frame Delivery Ratio

   The frame delivery ratio is defined as the total number of frames
   delivered to the destination divided by the frames offered by the
   source.  The destination values can be obtained using FrDeliveredC
   and FrDeliveredE.  The source values can be obtained using FrOfferedC
   and FrOfferedE.

                          FrDeliveredC + FrDeliveredE
   Frame Delivery Ratio = ---------------------------
                            FrOfferedC + FrOfferedE

                                     FrDeliveredC
   Committed Frame Delivery Ratio =  ------------
                                      FrOfferedC

                                  FrDeliveredE
   Excess Frame Delivery Ratio =  ------------
                                   FrOfferedE










Steinberger & Nicklass      Standards Track                    [Page 20]

RFC 3202           Frame Relay Service Level Defs MIB       January 2002


3.6.10.  Data Delivery Ratio

   The data delivery ratio is defined as the total amount of data
   delivered to the destination divided by the data offered by the
   source.  The destination values can be obtained using DataDeliveredC
   and DataDeliveredE.  The source values can be obtained using
   DataOfferedC and DataOfferedE.

                         DataDeliveredC + DataDeliveredE
   Data Delivery Ratio = -------------------------------
                           DataOfferedC + DataOfferedE

                                   DataDeliveredC
   Committed Data Delivery Ratio = --------------
                                    DataOfferedC

                                DataDeliveredE
   Excess Data Delivery Ratio = --------------
                                 DataOfferedE

3.6.11.  Service Availability

   Some forms of service availability measurement defined in FRF.13 [17]
   require knowledge of the amount of time the network is allowed to be
   unavailable during the period of measurement.  This is called the
   excluded outage time and will be represented in the measurements
   below as ExcludedTime.  It is assumed that the management software
   will maintain this information in that it often relates to specific
   times and dates that many devices are not capable of maintaining.
   Further, it may change based on a moving maintenance window that the
   device cannot track well.

   Mean Time to Repair (FRMTTR) = 0 if Unavailables is 0.

                       UnavailableTime
   Otherwise, FRMTTR = ---------------
                        Unavailables


   Virtual Connection Availability (FRVCA) = 0 if IntervalTime equals
                                                  ExcludedTime.

                      IntervalTime - ExcludedTime - UnavailableTime
   Otherwise, FRVCA = --------------------------------------------- *100
                               IntervalTime - ExcludedTime


   Mean Time Between Service Outages (FRMTBSO) = 0 if Unavailables is 0.



Steinberger & Nicklass      Standards Track                    [Page 21]

RFC 3202           Frame Relay Service Level Defs MIB       January 2002


   Otherwise, FRMTBSO = IntervalTime - ExcludedTime - UnavailableTime
                        ---------------------------------------------
                                       Unavailables

4.  Relation to Other MIB Modules

   There is no explicit relation to any other frame relay MIB module nor
   are any required to implement this MIB module.  However, there is a
   need for knowledge of ifIndexes and some understanding of DLCIs.  The
   ifIndex information can be found in the IF-MIB [21] which is
   required.  The DLCI information can be found in either the Frame
   Relay DTE MIB (RFC 2115) [20] or the Frame Relay Network Services MIB
   (RFC 2954) [18]; however, neither is required.

   Upon setting of frsldPvcCtrlStatus in the frsldPvcCtrlTable to
   active(1) the system can be in one of the following three states:

   (1) The respective DLCI is known and is active.  This corresponds to
       a state in which frPVCEndptRowStatus is active(1) and
       frPVCEndptRcvdSigStatus is either active(2) or none(4) for the
       Frame Relay Network Services MIB (RFC 2954) [18].  For the Frame
       Relay DTE MIB, the same state is shown by frCircuitRowStatus of
       active(1) and  frCircuitState of active(2).

   (2) The respective DLCI has not been created.  This corresponds to a
       state in which the row with either frPVCEndptDLCIIndex or
       frCircuitDlci equal to the respective DLCI does not exist in
       either the frPVCEndptTable or the frCircuitTable respectively.

   (3) The respective DLCI has just been removed.  This corresponds to a
       state in which either frPVCEndptRowStatus is no longer active(1)
       or frPVCEndptRcvdSigStatus is no longer active(2) or none(4) for
       the Frame Relay Network Services MIB (RFC 2954) [18].  For the
       Frame Relay DTE MIB, the same state is shown when either
       frCircuitRowStatus is no longer active(1) or frCircuitState is no
       longer active(2).

   For the first case, the row in the frsldPvcDataTable will be filled.
   If frsldSmplCtrlStatus in the frsldSmplCtrlTable for the respective
   DLCI is also `active' the frsldPvcSampleTable will be filled as well.

   For the second case, the respective rows will not be added to any of
   the data or sample tables and frsldPvcCtrlStatus SHOULD report
   notReady(3).







Steinberger & Nicklass      Standards Track                    [Page 22]

RFC 3202           Frame Relay Service Level Defs MIB       January 2002


   For the third case, frsldPvcCtrlDeleteOnPurge should direct the
   behavior of the system.  If all tables are purged, this case will be
   equivalent to the second case above.  Otherwise, frsldPvcCtrlStatus
   SHOULD remain active(1).

5.  Structure of the MIB Module

   The FRSLD-MIB consists of the following components:

   o  frsldPvcCtrlTable

   o  frsldSmplCtrlTable

   o  frsldPvcDataTable

   o  frsldPvcSampleTable

   o  frsldCapabilities

   Refer to the compliance statement defined within for a definition of
   what objects MUST be implemented.

5.1.  frsldPvcCtrlTable

   The frsldPvcCtrlTable is the central control table for operations of
   the Frame Relay Service Level Definitions MIB.  It provides variables
   to control the parameters required to calculate the objects in the
   other tables.

   A row in this table MUST exist in order for a row to exist in any
   other table in this MIB module.

5.2.  frsldSmplCtrlTable

   This is an optional table to allow control of sampling of the data in
   the data table.

5.3.  frsldPvcDataTable

   This table contains the calculated data.  It relies on configuration
   from the control table.










Steinberger & Nicklass      Standards Track                    [Page 23]

RFC 3202           Frame Relay Service Level Defs MIB       January 2002


5.4.  frsldPvcSampleTable

   This table contains samples of the delivery and availability
   information from the data table as well as delay information
   calculated over the sample period.  It relies on configuration from
   both the control table and the sample control table.

5.5.  frsldCapabilities

   This is a group of objects that define write capabilities of the
   read-create objects in the tables above.

6.  Persistence of Data

   The data in frsldPvcCtrlTable and frsldSmplCtrlTable SHOULD persist
   through power cycles.  Note, however, that the symantics of readiness
   for the rows still applies.  This means that it is possible for a row
   to be reprovisioned as notReady(3) if the underlying DLCI does not
   persist.  The data collected in the other tables SHOULD NOT persist
   through power cycles in that the reference TimeStamp is no longer
   valid.

7.  Object Definitions

FRSLD-MIB DEFINITIONS ::= BEGIN

IMPORTS
    MODULE-IDENTITY, OBJECT-TYPE,
    Counter32, Gauge32, Integer32,
    Counter64, TimeTicks, mib-2             FROM SNMPv2-SMI