RFC 1596 (rfc1596) - Page 3 of 46

Definitions of Managed Objects for Frame Relay Service

Alternative Format: Original Text Document
< Previous
Next >
RFC 1596                Frame Relay Service MIB               March 1994


                ____________________________________________________
                |              |              |       |            |
                |              |              | SIP   |  RFC 1490   |
                |              | X.25 MIB     | Relay | (no applic.|
                |              | for IW/Encap.| MIB   |  MIB)      |
                |              |              |       |            |
                |    MIB II    |-----------------------------------|
                |              |                                   |
                |   ifTable    |      Frame Relay Service MIB      |
                |  ifXTable    |                                   |
                | ifStackTable |___________________________________|
                |              |                         |         |
                |              | Physical Layer MIBs     | ATM MIB |
                |              |  e.g., DS1/E1 MIB,      |---------|
                |              |  RS232-like MIB         | Phy.    |
                |              |                         | Layer   |
                |              |                         |  MIB    |
                |--------------|-------------------------|---------|


                     Figure 1. Frame Relay MIB Architecture

3.1.  Scope of MIB

   The Frame Relay Service MIB will only manage the Frame Relay portion
   of the network.  This MIB is based upon the Customer Network
   Management concepts presented in the document "Service Management
   Architecture for Virtual Connection Services" [6].

   This MIB will NOT be implemented on User Equipment (e.g., DTE), and
   the Frame Relay DTE MIB (RFC 1315) should be used to manage those
   devices [8].

   Frame Relay Service MIB is intended to be used for Customer Network
   Management (CNM) of a Frame Relay Network Service.  It provides
   information that allows end-customers to obtain performance
   monitoring, fault detection, and configuration information about
   their Frame Relay Service.  It is an implementation decision as to
   whether this MIB is used to create/delete/modify PVCs and to turn
   PVCs on or off.

   By using this and other related MIBs, a customer's NMS can monitor
   their PVCs and UNI/NNI logical ports.  Internal aspects of the
   network (e.g., switching elements, line cards, and network routing
   tables) are outside the scope of this MIB.  The Customer's NMS will
   typically access the SNMP proxy-agent within the Frame Relay network
   using SNMP over UDP over IP with IP encapsulated in Frame Relay
   according to RFC 1490/ANSI T1.617 Annex F [7,9].  The customer, thus,



Frame Relay Service MIB Working Group
< Previous
Next >