As per Relevance of the word reference, we have this rfc below:
Network Working Group K.
Request for Comments: 2954 Megisto
Obsoletes: 1604 D.
Category: Standards Track Syndesis
October 2000
Definitions of Managed
for Frame Relay
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
This memo defines an extension to the Management Information
(MIB) for use with network management protocols in
Control Protocol/Internet Protocol-based (TCP/IP) internets.
particular, it defines objects for managing the frame relay service
This document obsoletes RFC 1604.
Table of
1 The SNMP Management Framework ................................ 2
2 Overview ..................................................... 3
2.1 Scope of MIB ............................................... 3
2.2 Transiting Multiple Frame Relay Networks ................... 5
2.3 Access Control ............................................. 5
2.4 Frame Relay Service MIB Terminology ........................ 6
2.5 Relation to Other MIBs ..................................... 8
2.5.1 System Group ............................................. 8
2.5.2 Interfaces Table (ifTable, ifXtable) ..................... 8
2.5.3 Stack Table for DS1/E1 Environment ....................... 12
2.5.4 Stack Table for V.35 Environments ........................ 14
2.5.5 The Frame Relay/ATM PVC Service Interworking MIB ......... 14
2.6 Textual Convention Change .................................. 15
3 Object Definitions ........................................... 15
3.1 The Frame Relay Service Logical Port ....................... 17
Rehbehn & Fowler Standards Track [Page 1]
RFC 2954 Frame Relay Service MIB October 2000
3.2 Frame Relay Management VC Signaling ........................ 22
3.3 Frame Relay PVC End-Points ................................. 32
3.4 Frame Relay PVC Connections ................................ 45
3.5 Frame Relay Accounting ..................................... 53
3.6 Frame Relay Network Service Notifications .................. 56
3.7 Conformance Information .................................... 57
4 Acknowledgments .............................................. 67
5 References ................................................... 67
6 Security Considerations ...................................... 69
7 Authors' Addresses ........................................... 70
APPENDIX A Update Information .................................. 71
Intellectual Property Rights ................................... 75
Full Copyright Statement ....................................... 76
1. The SNMP Management
The SNMP Management Framework presently consists of five
components
o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for
purpose of management. The first version of this Structure
Management Information (SMI) is called SMIv1 and described in
16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].
second version, called SMIv2, is described in STD 58, RFC 2578
[5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7].
o Message protocols for transferring management information.
first version of the SNMP message protocol is called SNMPv1
described in STD 15, RFC 1157 [8]. A second version of the
message protocol, which is not an Internet standards
protocol, is called SNMPv2c and described in RFC 1901 [9] and
1906 [10]. The third version of the message protocol is
SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574
[12].
o Protocol operations for accessing management information.
first set of protocol operations and associated PDU formats
described in STD 15, RFC 1157 [8]. A second set of
operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2573 [14]
the view-based access control mechanism described in RFC 2575
[15].
Rehbehn & Fowler Standards Track [Page 2]
RFC 2954 Frame Relay Service MIB October 2000
A more detailed introduction to the current SNMP Management
can be found in RFC 2570 [16].
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the mechanisms defined in the SMI
This memo specifies a MIB module that is compliant to the SMIv2.
MIB conforming to the SMIv1 can be produced through the
translations. The resulting translated MIB must be
equivalent, except where objects or events are omitted because
translation is possible (use of Counter64). Some machine
information in SMIv2 will be converted into textual descriptions
SMIv1 during the translation process. However, this loss of
readable information is not considered to change the semantics of
MIB
2.
These objects are used to manage a frame relay Service. At present
this applies to the following value of the ifType variable in
IF-MIB [26]:
frameRelayService (44)
This section provides an overview and background of how to use
MIB and other potential MIBs to manage a frame relay service
2.1. Scope of
The Frame Relay Service MIB supports Customer Network
(CNM) of a frame relay network service. Through the use of this
other related MIBs, a frame relay service customer's NMS can
the customer's UNI/NNI logical ports and PVCs. It provides
with access to configuration data, performance
information, and fault detection for the delivered frame
service. As an option, an SNMP agent supporting the Frame
Service MIB may allow customer-initiated PVC management
such as creation, deletion, modification, activation,
deactivation of individual PVCs. However, internal aspects of
network (e.g., switching elements, line cards, and network
tables) are beyond the scope of this MIB
The Frame Relay Service MIB models all interfaces and PVCs
by a frame relay service within a single virtual SNMP system for
purpose of comprehensively representing the customer's frame
service. The customer's interfaces and PVCs may physically exist
one or more devices within the network topology. An SNMP
Rehbehn & Fowler Standards Track [Page 3]
RFC 2954 Frame Relay Service MIB October 2000
providing support for the Frame Relay Service MIB as well as
appropriate MIBs to model a single virtual frame relay
service is referred to as a Frame Relay Service (FRS) agent
Internal communication mechanisms between the FRS agent
individual devices within the frame relay network delivering
service are implementation specific and beyond the scope of this MIB
The customer's NMS will typically access the SNMP agent
the Frame Relay Service MIB over a frame relay permanent
connection (PVC). SNMP access over a frame relay PVC is
through the use of SNMP over UDP over IP encapsulated in Frame
according to STD 55, RFC2427 and ITU X.36 Annex D [23].
access mechanisms and SNMP agent implementations are possible
This MIB will NOT be implemented on user equipment (e.g., DTE).
devices are managed using the Frame Relay DTE MIB (RFC2115[18]).
However, concentrators may use the Frame Relay Service MIB instead
the Frame Relay DTE MIB
This MIB does not define managed objects for the physical layer
Existing physical layer MIBs (e.g., DS1 MIB) and Interface MIB
be used as needed in FRS Agent implementations
This MIB supports frame relay PVCs. This MIB may be extended at
later time to handle frame relay SVCs
A switch implementation may support this MIB for the purpose
configuration and control of the frame relay service beyond the
of traditional customer network management applications. A number
objects (e.g. frLportTypeAdmin) support administrative actions
impact the operation of frame relay switch equipment in the network
This is reflected in the differences between the two MIB
modules
o the frame relay service compliance
(frnetservCompliance),
o the frame relay switch compliance
(frnetSwitchCompliance).
The frame relay service compliance module does not support
administrative control objects used for switch management
Rehbehn & Fowler Standards Track [Page 4]
RFC 2954 Frame Relay Service MIB October 2000
2.2. Transiting Multiple Frame Relay
This MIB is only used to manage a single frame relay service
from one network service provider. Therefore, if a customer
traverses multiple networks, then the customer must poll a
FRS agent within each frame relay network to retrieve the end-to-
view of service
Figure 1 illustrates a customer ("User B") NMS accessing FRS
in three different frame relay networks (I, J, and K).
+-------------------------------------+
| Customer Network Management Station |
| (SNMP based) |
+-------------------------------------+
^ ^ ^
| | |
| | |
UNI | NNI | NNI |
| ^ | ^ | ^
| +-----------+ | +-----------+ | +-----------+ |
| | | | | | | | | |
Originating | | FR | | | FR | | | FR | |
+--------+ | | Network I | | | Network J | | | Network K | | +--------+
| | | | | | | | | | | | | |
| |---| |---| |---| |---| User B |
| | | | | | | | | | | | | |
| //////////////////////////////////////////////////////////// |
| | | | | | | | | | | | | |
+--------+ | +-----------+ | +-----------+ | +-----------+ | +--------+
| | | |
| | | |
| PVC Segment 1 | PVC Segment 2 | PVC Segment 3 |
|<------------->|<------------->|<------------->|
| |
| Multi-network PVC |
|<--------------------------------------------->|
| NNI = Network-to Network Interface |
UNI = User-to-Network
Figure 1, Multi-network
2.3. Access
A frame relay network is shared amongst many frame relay subscribers
Each subscriber will only have access to their information (e.g.,
information with respect to their interfaces and PVCs). The FRS
should provide instance level granularity for MIB views
Rehbehn & Fowler Standards Track [Page 5]
RFC 2954 Frame Relay Service MIB October 2000
2.4. Frame Relay Service MIB
Access Channel - An access channel generically refers to the DS1/E
or DS3/E3-based UNI access channel or NNI access channel across
frame relay data transits. An access channel is the access
for a single stream of user data
Within a given DS1 line, an access channel can denote any one of
following
o Unchannelized DS1 - the entire DS1 line is considered an
channel. Each access channel is comprised of 24 DS0 time slots
o Channelized DS1 - an access channel is any one of 24 channels
Each access channel is comprised of a single DS0 time slot
o Fractional DS1 - an access channel is a grouping of NxDS0
slots (NX56/64 Kbps, where N = 1-23 DS0 Time slots per
DS1 Access Channel) that may be assigned in consecutive
non-consecutive order
Within a given E1 line, a channel can denote any one of the following
o Unchannelized E1 - the entire E1 line is considered a
access channel. Each access channel is comprised of 31 E1
slots
o Channelized E1 - an access channel is any one of 31 channels
Each access channel is comprised of a single E1 time slot
o Fractional E1 - an access channel is a grouping of N E1
slots (NX64 Kbps, where N = 1-30 E1 time slots per FE1
channel) that may be assigned in consecutive or non-
order
Within a given unformatted line, the entire unformatted line
considered an access channel. Examples include RS-232, V.35, V.36
X.21 (non-switched), and unframed E1 (G.703 without G.704).
Access Rate - The data rate of the access channel, expressed
bits/second. The speed of the user access channel determines
rapidly the end user can inject data into the network
Bc - The Committed Burst Size (Bc) is the maximum amount
subscriber data (expressed in bits) that the network agrees
transfer, under normal conditions, during a time interval Tc
Rehbehn & Fowler Standards Track [Page 6]
RFC 2954 Frame Relay Service MIB October 2000
Be - The Excess Burst Size (Be) is the maximum amount of
data (expressed in bits) in excess of Bc that the network
attempt to deliver during the time interval Tc. This data (Be)
delivered in general with a lower probability than Bc
CIR - The Committed Information Rate (CIR) is the subscriber
rate (expressed in bits/second) that the network commits to
under normal network conditions. CIR is averaged over the
interval Tc (CIR = Bc/Tc).
DLCI - Data Link Connection
Logical Port - This term is used to model the frame relay "interface
on a device
NNI - Network to Network
Permanent Virtual Connection (PVC) - A virtual connection that
its end-points and bearer capabilities defined at subscription time
Time slot (E1) - An octet within the 256-bit information field
each E1 frame is defined as a time slot. Time slots are
sensitive within the 256-bit information field. Fractional E1
is provided in contiguous or non-contiguous time slot increments
Time slot (DS0) - An octet within the 192-bit information field
each DS1 frame is defined as a time slot. Time slots are
sensitive within the 192-bit information field. Fractional DS
service is provided in contiguous or non-contiguous time
increments
UNI - User to Network
N391 - Full status (status of all PVCs) polling
N392 - Error
N393 - Monitored events
T391 - Link integrity verification polling
T392 - Polling verification
nT3 - Status enquiry
nN3 - Maximum status enquiry
Rehbehn & Fowler Standards Track [Page 7]
RFC 2954 Frame Relay Service MIB October 2000
2.5. Relation to Other
2.5.1. System
Use the System Group of the SNMPv2-MIB [27] to describe the
Relay Service (FRS) agent. The FRS agent may be monitoring
frame relay devices in one network. The System Group does
describe frame relay devices monitored by the FRS agent
sysDescr: ASCII string describing the FRS agent
Can be up to 255 characters long. This field
generally used to indicate the network
identification and type of service offered
sysObjectID: Unique OBJECT IDENTIFIER (OID) for
FRS agent
sysUpTime: Clock in the FRS agent;
in 1/100s of a second. Elapsed type
the FRS agent came on line
sysContact: Contact for the FRS agent
ASCII string of up to 255 characters
sysName: Domain name of the FRS agent, for example
acme.
sysLocation: Location of the FRS agent
ASCII string of up to 255 characters
sysServices: Services of the managed device. The value "2",
which implies
the frame relay network is
a subnetwork level service, is recommended
2.5.2. Interfaces Table (ifTable, ifXtable
This specifies how the Interfaces Group defined in the IF MIB [26]
shall be used for the management of frame relay based interfaces,
in conjunction with the Frame Relay Service MIB module. This
assumes the interpretation of the evolution of the Interfaces
to be in accordance with: "The interfaces table (ifTable)
information on the managed resource's interfaces. Each sub-
below the internetwork layer of a network interface is considered
interface." Thus, the ifTable allows the following frame relay-
interfaces to be represented as table entries
Rehbehn & Fowler Standards Track [Page 8]
RFC 2954 Frame Relay Service MIB October 2000
- Frame relay interfaces in equipment (e.g., switches, routers
networks) supporting frame relay. This level is concerned
generic frame counts and not with individual virtual connections
In accordance with the guidelines of ifTable, frame counts
virtual connection are not covered by ifTable, and are
interface specific and covered in the Frame Relay Service MIB module
In order to interrelate the ifEntries properly, the Interfaces
Group shall be supported
Some specific interpretations of ifTable for frame relay follow
Object Use for the generic Frame Relay
====== =============================================
ifIndex Each frame relay port is represented by
ifEntry
ifDescr Description of the frame relay interface
ASCII string describing the UNI/NNI
port. Can be up to 255 characters long
ifType The value allocated for Frame Relay
is equal to 44.
ifMtu Set to maximum frame size in octets for
frame relay logical port
ifSpeed Peak bandwidth in bits per second
for use. This could be the speed of
logical port and not the access rate.
user information transfer rate (i.e.,
rate) of the UNI or NNI logical port in
per second (this is not the clocking speed).
For example, it is 1,536,000 bits per
for a DS1-based UNI/NNI logical port
1,984,000 bits per second for an E1-
UNI/NNI logical port
ifPhysAddress The primary address for this logical
assigned by the frame relay
provider. An octet string of zero length
no address is used for this logical port
ifAdminStatus The desired administrative status of
frame relay logical port
Rehbehn & Fowler Standards Track [Page 9]
RFC 2954 Frame Relay Service MIB October 2000
ifOperStatus The current operational status of the
Relay UNI or NNI logical port
ifLastChange The value of sysUptime at the
re-initialization of the logical port.
value of sysUpTime at the time the
port entered its current operational state
If the current state was entered prior to
last re-initialization of the local
management subsystem, then this
contains a zero value
ifInOctets The number of received octets. This
only counts octets from the beginning of
frame relay header field to the end of
data
ifInUcastPkts The number of received unerrored,
frames
ifInDiscards The number of received frames discarded
Specifically, frames discarded due to
buffer congestion and traffic policing
ifInErrors The number of received frames that
discarded because of an error. Specifically
frames that are too long or too short,
that are not a multiple of 8 bits in length
frames with an invalid or unrecognized DLCI
frames with an abort sequence, frames
improper flag delimitation, and frame
fail FCS
ifInUnknownProtos The number of packets discarded because of
unknown or unsupported protocol. For
Relay Service interfaces, this counter
always be zero
ifOutOctets The number of transmitted octets.
counter only counts octets from the
of the frame relay header field to the end
user data
ifOutUcastpkts The number of unerrored, unicast frames sent
ifOutDiscards The number of frames discarded in the
direction. Possible reasons are as follows
policing, congestion
Rehbehn & Fowler Standards Track [Page 10]
RFC 2954 Frame Relay Service MIB October 2000
ifOutErrors The number of frames discarded in the
direction because of an error. Specifically
frames that are aborted due to a
underrun
ifName This variable is not applicable for
Relay Service interfaces, therefore,
variable contains a zero-length string
ifInMulticastPkts The number of received unerrored,
frames
ifInBroadcastPkts This variable is not applicable for
Relay Service interfaces, therefore,
counter is always zero
ifOutMulticastPkts The number of sent unerrored,
frames
ifOutBroadcastPkts This variable is not applicable for
Relay Service interfaces, therefore,
counter is always zero
ifHCInOctets Only used for DS3-based (and greater)
Relay logical ports. The number of
octets. This counter only counts
from the beginning of the frame relay
field to the end of user data
ifHCOutOctets Only used for DS3-based (and greater)
Relay logical ports. The number
transmitted octets. This counter only
octets from the beginning of the frame
header field to the end of user data
ifLinkUpDownTrapEnable Set to true(1). It is recommended that
underlying physical layer notifications
disabled since both are not required
Notifications are enabled at the frame
service layer specifically because
notifications are not to be sent if the
relay interface fails. Without
linkUp/linkDown notification, the
station would receive no notification of
failure
Rehbehn & Fowler Standards Track [Page 11]
RFC 2954 Frame Relay Service MIB October 2000
ifHighSpeed Set to the user data rate of the frame
logical port in millions of bits per second
If the user data rate is less than 1 Mbps
then this value is zero
ifPromiscuousMode Set to false(2).
ifConnectorPresent Set to false(2).
Frame relay network service interfaces support the Interface
Group. Frame relay network service interfaces do not support
other groups or objects in the Interfaces group of the IF MIB
2.5.3. Stack Table for DS1/E1
This section describes by example how to use ifStackTable
represent the relationship of frame relay service to ds0
ds0Bundles with ds1 interfaces [20].
Example: A frame relay service is being carried on 4 ds0s of a ds1.
+---------------------+
| Frame Relay Service |
+---------------------+
|
+---------------------+
| ds0Bundle |
+---------------------+
| | | |
+---+ +---+ +---+ +---+
|ds0| |ds0| |ds0| |ds0|
+---+ +---+ +---+ +---+
| | | |
+---------------------+
| ds1 |
+---------------------+
The assignment of the index values could for example be
ifIndex
1 FrameRelayService (type 44)
2 ds0Bundle (type 82)
3 ds0 #1 (type 81)
4 ds0 #2 (type 81)
5 ds0 #3 (type 81)
6 ds0 #4 (type 81)
7 ds1 (type 18)
Rehbehn & Fowler Standards Track [Page 12]
RFC 2954 Frame Relay Service MIB October 2000
The ifStackTable is then used to show the relationships between
various interfaces
ifStackTable
HigherLayer
0 1
1 2
2 3
2 4
2 5
2 6
3 7
4 7
5 7
6 7
7 0
In the case where the frame relay service is using a single ds0,
the ds0Bundle is not required
+---------------------+
| Frame Relay Service |
+---------------------+
|
+---+
|ds0|
+---+
|
+---------------------+
| ds1 |
+---------------------+
The assignment of the index values could for example be
ifIndex
1 FrameRelayService (type 44)
2 ds0 (type 81)
3 ds1 (type 18)
The ifStackTable is then used to show the relationships between
various interfaces
Rehbehn & Fowler Standards Track [Page 13]
RFC 2954 Frame Relay Service MIB October 2000
ifStackTable
HigherLayer
0 1
1 2
2 3
3 0
2.5.4. Stack Table for V.35
This section describes by example how to use ifStackTable
represent the relationship of frame relay service with V.35
interfaces
+---------------------+
| Frame Relay Service |
+---------------------+
|
+---------------------+
| v35 |
+---------------------+
An example of index values in this case could be
ifIndex
1 FrameRelayService (type 44)
2 v35 (type 33)
Note type 33 (RS232-like MIB) is used instead of type 45 (V.35). V35
does not pertain to this environment
The ifStackTable is then used to show the relationships between
various interfaces
ifStackTable
HigherLayer
0 1
1 2
2 0
2.5.5. The Frame Relay/ATM PVC Service Interworking
Connections between two frame relay endpoints are represented with
entry in the frPVCConnectTable of this MIB. Both endpoints
represented with rows in the frPVCEndptTable.
frPVCEndptConnectIdentifier object of each endpoint points to
frPVCConnectTable cross-connect table row for the connection
Rehbehn & Fowler Standards Track [Page 14]
RFC 2954 Frame Relay Service MIB October 2000
In contrast, a connection that spans frame relay and ATM endpoints
represented with an entry in the frAtmIwfConnectionTable of
FR/ATM PVC Service Interworking MIB defined in [28].
In the case of an inter-worked connection,
frPVCEndptConnectIdentifier object is set to zero. Instead,
frPVCEndptAtmIwfConnIndex object is set to the index of the FR/
IWF cross-connect table row
The frame relay PVC cross-connect table (frPVCConnectTable) does
contain an entry for the FR/ATM inter-worked connection
2.6. Textual Convention
Version 1 of the Frame Relay Service MIB contains MIB objects
with the DisplayString textual convention. In version 2 of this MIB
the syntax for these objects has been updated to use the (
preferred) SnmpAdminString textual convention. The new TC
support for a greater variety of international character sets
The working group realizes that this change is not strictly
by SMIv2. In our judgment, the alternative of deprecating the
objects and defining new objects would have a more adverse impact
backward compatibility and interoperability, given the
semantics of these objects
3. Object
FRNETSERV-MIB DEFINITIONS ::=
MODULE-IDENTITY, OBJECT-TYPE
NOTIFICATION-TYPE, transmission
Counter32, Integer32 FROM SNMPv2-
TimeStamp, RowStatus FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-GROUP
NOTIFICATION-GROUP FROM SNMPv2-
InterfaceIndex, ifIndex FROM IF-
SnmpAdminString FROM SNMP-FRAMEWORK-MIB
frnetservMIB MODULE-
LAST-UPDATED "200009280000Z" -- September 28, 2000
ORGANIZATION "IETF Frame Relay Service MIB Working Group
CONTACT-
"WG Charter
http://www.ietf.org/html.charters/frnetmib-
WG-email
frnetmib@sunroof.eng.sun.
Rehbehn & Fowler Standards Track [Page 15]
RFC 2954 Frame Relay Service MIB October 2000
Subscribe
frnetmib-request@sunroof.eng.sun.
Email Archive
ftp://ftp.ietf.org/ietf-mail-archive/
Chair: Andy
Vivace Networks, Inc
Email: Andy.Malis@vivacenetworks.
WG editor: Kenneth
Megisto Systems, Inc
Email: krehbehn@megisto.
Co-author: David
Syndesis Limited
EMail: fowler@syndesis.com
"The MIB module to describe generic objects
Frame Relay Network Service."
--
-- Revision
--
REVISION "200009280000Z
"Published as RFC 2954.
The major new features of this revision include
o Support for read-write capability
provision switch components providing service
o Support for cross-connection via a frame
to ATM service interworking function
o Support for frame relay fragmentation
o Additional frame counters to track
loss
Refer to Appendix A for a comprehensive list
changes since RFC 1604."
REVISION "199311161200Z
"Published as RFC 1604."
::= { transmission 44 }
Rehbehn & Fowler Standards Track [Page 16]
RFC 2954 Frame Relay Service MIB October 2000
OBJECT IDENTIFIER ::= { frnetservMIB 1 }
OBJECT IDENTIFIER ::= { frnetservMIB 2 }
OBJECT IDENTIFIER ::= { frnetservTraps 0 }
--
-- The Frame Relay Service Logical
--
frLportTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"The Frame Relay Logical Port Information table
an interface-specific addendum to the
ifTable of the Interface MIB."
::= { frnetservObjects 1 }
frLportEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry in the Frame Relay Logical
Information table."
INDEX { ifIndex }
::= { frLportTable 1 }
FrLportEntry ::=
SEQUENCE {
frLportNumPlan INTEGER
frLportContact SnmpAdminString
frLportLocation SnmpAdminString
frLportType INTEGER
frLportAddrDLCILen INTEGER
frLportVCSigProtocol INTEGER
frLportVCSigPointer OBJECT IDENTIFIER
frLportDLCIIndexValue Integer32,
frLportTypeAdmin INTEGER
frLportVCSigProtocolAdmin INTEGER
frLportFragControl INTEGER
frLportFragSize Integer32
}
Rehbehn & Fowler Standards Track [Page 17]
RFC 2954 Frame Relay Service MIB October 2000
frLportNumPlan OBJECT-
SYNTAX INTEGER {
other(1),
e164(2),
x121(3),
none(4)
}
MAX-ACCESS read-
STATUS
"The value of this object identifies the
address numbering plan for this UNI/NNI
port. The network address is the
ifPhysAddress. The value none(4) implies
there is no ifPhysAddress. The FRS agent
return an octet string of zero length
ifPhysAddress. The value other(1) means that
address has been assigned to this interface,
the numbering plan is not enumerated here."
REFERENCE "E.164 [29]
X.121 [30]"
::= { frLportEntry 1 }
frLportContact OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of this object identifies the
contact for this UNI/NNI logical port."
::= { frLportEntry 2 }
frLportLocation OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of this object identifies the
relay network location for this UNI/NNI
port."
::= { frLportEntry 3 }
frLportType OBJECT-
SYNTAX INTEGER {
uni(1),
nni(2)
}
MAX-ACCESS read-
Rehbehn & Fowler Standards Track [Page 18]
RFC 2954 Frame Relay Service MIB October 2000
STATUS
"The value of this object identifies the type
network interface for this logical port."
::= { frLportEntry 4 }
frLportAddrDLCILen OBJECT-
SYNTAX INTEGER {
twoOctets10Bits(1),
threeOctets10Bits(2),
threeOctets16Bits(3),
fourOctets17Bits(4),
fourOctets23Bits(5)
}
UNITS "Octets
MAX-ACCESS read-
STATUS
"The value of this object identifies the Q.922
Address field length and DLCI length for
UNI/NNI logical port."
REFERENCE "Q.922 [25]"
::= { frLportEntry 5 }
frLportVCSigProtocol OBJECT-
SYNTAX INTEGER {
none(1),
lmi(2),
ansiT1617D(3),
ansiT1617B(4),
ccittQ933A(5)
}
MAX-ACCESS read-
STATUS
"The value of this object identifies the
In-Channel Signaling Protocol that is used
this frame relay UNI/NNI logical port
none(1): Interface does not use a
signaling
lmi(2): Interface operates the Stratacom
Nortel/DEC Local
Interface Specification
ansiT1617D(3): Interface operates the ANSI T1.617
Annex D PVC status
Rehbehn & Fowler Standards Track [Page 19]
RFC 2954 Frame Relay Service MIB October 2000
ansiT1617B(4): Interface operates the
T1.617
Annex B
ccittQ933A(5): Interface operates the ITU Q.933
Annex A PVC status protocol
REFERENCE "LMI [24]
T1.617 Annex D [17],
Q.933 Annex A [22]"
::= { frLportEntry 6 }
frLportVCSigPointer OBJECT-
SYNTAX OBJECT
MAX-ACCESS read-
STATUS
"The value of this object is used as a pointer
the table that contains the Local In-
Signaling Protocol parameters and errors for
UNI/NNI logical port
This object has been deprecated to reflect
fact that the local in-channel
parameters are accessed from a single
(frMgtVCSigTable) that includes parameters for
possible signaling protocols. Early
anticipated multiple tables, one for
signaling protocol."
::= { frLportEntry 7 }
frLportDLCIIndexValue OBJECT-
SYNTAX Integer32 (16..4194303)
MAX-ACCESS read-
STATUS
"This object contains a hint to be used
frPVCEndptDLCIIndex when creating entries in
frPVCEndptTable. The SYNTAX of this
matches the SYNTAX of the frPVCEndptDLCIIndex -
object that is restricted to legal Q.922
values for the size of the address field
The value 0 indicates that no unassigned
are available
To obtain the frPVCEndptDLCIIndex value for a
entry, the manager issues a management
retrieval operation to obtain the current value
Rehbehn & Fowler Standards Track [Page 20]
RFC 2954 Frame Relay Service MIB October 2000
this object. After each retrieval, the agent
modify the value to the next unassigned index
prevent assignment of the same value to
management systems
A management system should repeat the read
obtain a new value should an attempt to create
new row using the previously returned hint fail."
REFERENCE "Q.922 [25]"
::= { frLportEntry 8 }
frLportTypeAdmin OBJECT-
SYNTAX INTEGER {
uni(1),
nni(2)
}
MAX-ACCESS read-
STATUS
"The value of this object desired identifies
type of network interface for this logical port."
::= { frLportEntry 9 }
frLportVCSigProtocolAdmin OBJECT-
SYNTAX INTEGER {
none(1),
lmi(2),
ansiT1617D(3),
ansiT1617B(4),
ccittQ933A(5)
}
MAX-ACCESS read-
STATUS
"The value of this object identifies the
Local In-Channel Signaling Protocol that is
for this frame relay UNI/NNI logical port.
value must be made the active protocol as soon
possible on the device
Refer to frLportVCSigProtocol for a description
each signaling protocol choices."
REFERENCE "LMI [24]
T1.617 Annex D [17],
Q.933 Annex A [22]"
::= { frLportEntry 10 }
frLportFragControl OBJECT-
Rehbehn & Fowler Standards Track [Page 21]
RFC 2954 Frame Relay Service MIB October 2000
SYNTAX INTEGER {
on(1),
off(2)
}
MAX-ACCESS read-
STATUS
"This object controls the transmission
reception of fragmentation frames for this UNI
NNI interface
on(1) Frames are fragmented using the
fragmentation
Note: The customer side of the
must also be configured to
frames
off(2) Frames are not fragmented using
interface fragmentation format."
REFERENCE "FRF.12 [21]"
DEFVAL { off }
::= { frLportEntry 11 }
frLportFragSize OBJECT-
SYNTAX Integer32 (0..4096)
UNITS "Octets
MAX-ACCESS read-
STATUS
"The value of this object is the size in octets
the maximum size of each fragment to be sent
fragmenting. This object is only used by
fragmentation transmitter, and the two sides
the interface may differ. The fragment
includes the octets for the frame relay header
the UI octet, the NLPID, the fragmentation header
and the fragment payload. If frLportFragControl
set to off, this value should be zero."
REFERENCE "FRF.12 [21]"
DEFVAL { 0 }
::= { frLportEntry 12 }
--
-- Frame Relay Management VC
--
frMgtVCSigTable OBJECT-
SYNTAX SEQUENCE OF
Rehbehn & Fowler Standards Track [Page 22]
RFC 2954 Frame Relay Service MIB October 2000
MAX-ACCESS not-
STATUS
"The Frame Relay Management VC
Parameters and Errors table."
::= { frnetservObjects 2 }
frMgtVCSigEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry in the Frame Relay Management
Signaling Parameters Errors table."
INDEX { ifIndex }
::= { frMgtVCSigTable 1 }
FrMgtVCSigEntry ::=
SEQUENCE {
frMgtVCSigProced INTEGER
frMgtVCSigUserN391 INTEGER
frMgtVCSigUserN392 INTEGER
frMgtVCSigUserN393 INTEGER
frMgtVCSigUserT391 INTEGER
frMgtVCSigNetN392 INTEGER
frMgtVCSigNetN393 INTEGER
frMgtVCSigNetT392 INTEGER
frMgtVCSigNetnN4 INTEGER
frMgtVCSigNetnT3 INTEGER
frMgtVCSigUserLinkRelErrors Counter32,
frMgtVCSigUserProtErrors Counter32,
frMgtVCSigUserChanInactive Counter32,
frMgtVCSigNetLinkRelErrors Counter32,
frMgtVCSigNetProtErrors Counter32,
frMgtVCSigNetChanInactive Counter32,
frMgtVCSigProcedAdmin INTEGER
frMgtVCSigUserN391Admin INTEGER
frMgtVCSigUserN392Admin INTEGER
frMgtVCSigUserN393Admin INTEGER
frMgtVCSigUserT391Admin INTEGER
frMgtVCSigNetN392Admin INTEGER
frMgtVCSigNetN393Admin INTEGER
frMgtVCSigNetT392Admin INTEGER
frMgtVCSigNetnT3Admin
}
frMgtVCSigProced OBJECT-
SYNTAX INTEGER {
Rehbehn & Fowler Standards Track [Page 23]
RFC 2954 Frame Relay Service MIB October 2000
u2nnet(1),
bidirect(2),
u2nuser(3)
}
MAX-ACCESS read-
STATUS
"The value of this object identifies the
in-channel signaling procedural role that is
for this UNI/NNI logical port.
procedures implies that both user-side
network-side procedural roles are used
u2nnet(1) Logical port operates user to
procedure in the role of the
bidirect(2) Logical port operates
bidirectional procedure (both
and network side roles
u2nuser(3) Logical port operates user to
procedure in the role of the
side
REFERENCE "Q.933 Annex A [22],
T1.617 Annex D [17]"
::= { frMgtVCSigEntry 1 }
frMgtVCSigUserN391 OBJECT-
SYNTAX INTEGER (1..255)
UNITS "Polls
MAX-ACCESS read-
STATUS
"The value of this object identifies the User-
N391 full status polling cycle value for
UNI/NNI logical port. If the logical port is
performing user-side (bidirectional) procedures
then this object is not instantiated and
attempt to read will result in the
exception response."
REFERENCE "Q.933 Annex A [22],
T1.617 Annex D [17]"
DEFVAL { 6 }
::= { frMgtVCSigEntry 2 }
frMgtVCSigUserN392 OBJECT-
SYNTAX INTEGER (1..10)
Rehbehn & Fowler Standards Track [Page 24]
RFC 2954 Frame Relay Service MIB October 2000
UNITS "Events
MAX-ACCESS read-
STATUS
"The value of this object identifies the User-
N392 error threshold value for this UNI/
logical port. If the logical port is
performing user-side (bidirectional) procedures
then this object is not instantiated."
REFERENCE "Q.933 Annex A [22],
T1.617 Annex D [17]"
DEFVAL { 3 }
::= { frMgtVCSigEntry 3 }
frMgtVCSigUserN393 OBJECT-
SYNTAX INTEGER (1..10)
UNITS "Events
MAX-ACCESS read-
STATUS
"The value of this object identifies the User-
N393 monitored events count value for this UNI/
logical port. If the logical port is
performing user-side (bidirectional) procedures
then this object is not instantiated."
REFERENCE "Q.933 Annex A [22],
T1.617 Annex D [17]"
DEFVAL { 4 }
::= { frMgtVCSigEntry 4 }
frMgtVCSigUserT391 OBJECT-
SYNTAX INTEGER (5..30)
UNITS "Seconds
MAX-ACCESS read-
STATUS
"The value of this object identifies the User-
T391 link integrity verification polling
value for this UNI/NNI logical port. If
logical port is not performing user-
procedures, then this object is not instantiated."
REFERENCE "Q.933 Annex A [22],
T1.617 Annex D [17]"
DEFVAL { 10 }
::= { frMgtVCSigEntry 5 }
frMgtVCSigNetN392 OBJECT-
SYNTAX INTEGER (1..10)
Rehbehn & Fowler Standards Track [Page 25]
RFC 2954 Frame Relay Service MIB October 2000
UNITS "Events
MAX-ACCESS read-
STATUS
"The value of this object identifies the Network
side N392 error threshold value (nN2 for LMI)
this UNI/NNI logical port. If the logical port
not performing network-side procedures, then
object is not instantiated."
REFERENCE "Q.933 Annex A [22],
T1.617 Annex D [17],
LMI [24]"
DEFVAL { 3 }
::= { frMgtVCSigEntry 6 }
frMgtVCSigNetN393 OBJECT-
SYNTAX INTEGER (1..10)
UNITS "Events
MAX-ACCESS read-
STATUS
"The value of this object identifies the Network
side N393 monitored events count value (nN3
LMI) for this UNI/NNI logical port. If
logical port is not performing network-
procedures, then this object is not instantiated."
REFERENCE "Q.933 Annex A [22],
T1.617 Annex D [17],
LMI [24]"
DEFVAL { 4 }
::= { frMgtVCSigEntry 7 }
frMgtVCSigNetT392 OBJECT-
SYNTAX INTEGER (5..30)
UNITS "Seconds
MAX-ACCESS read-
STATUS
"The value of this object identifies the Network
side T392 polling verification timer value (nT
for LMI) for this UNI/NNI logical port. If
logical port is not performing network-
procedures, then this object is not instantiated."
REFERENCE "Q.933 Annex A [22],
T1.617 Annex D [17],
LMI [24]"
DEFVAL { 15 }
::= { frMgtVCSigEntry 8 }
Rehbehn & Fowler Standards Track [Page 26]
RFC 2954 Frame Relay Service MIB October 2000
frMgtVCSigNetnN4 OBJECT-
SYNTAX INTEGER (5..5)
UNITS "Events
MAX-ACCESS read-
STATUS
"The value of this object identifies the Network
side nN4 maximum status enquires received
for this UNI/NNI logical port. If the
port is not performing network-side procedures
is not performing LMI procedures, then this
is not instantiated
This object applies only to LMI and always has
value of 5."
REFERENCE "LMI [24]"
::= { frMgtVCSigEntry 9 }
frMgtVCSigNetnT3 OBJECT-
SYNTAX INTEGER (5 | 10 | 15 | 20 | 25 | 30)
UNITS "Seconds
MAX-ACCESS read-
STATUS
"The value of this object identifies the Network
side nT3 timer (for nN4 status enquires received
value for this UNI/NNI logical port. If
logical port is not performing network-
procedures or is not performing LMI procedures
then this object is not instantiated
This object applies only to LMI."
REFERENCE "LMI [24]"
DEFVAL { 20 }
::= { frMgtVCSigEntry 10 }
frMgtVCSigUserLinkRelErrors OBJECT-
SYNTAX Counter32
UNITS "Errors
MAX-ACCESS read-
STATUS
"The number of user-side local in-
signaling link reliability errors (i.e., non
receipt of Status/Status Enquiry messages
invalid sequence numbers in a Link
Verification Information Element) for this UNI/
logical port. If the logical port is
Rehbehn & Fowler Standards Track [Page 27]
RFC 2954 Frame Relay Service MIB October 2000
performing user-side procedures, then this
is not instantiated."
::= { frMgtVCSigEntry 11 }
frMgtVCSigUserProtErrors OBJECT-
SYNTAX Counter32
UNITS "Errors
MAX-ACCESS read-
STATUS
"The number of user-side local in-
signaling protocol errors (i.e.,
discriminator, unnumbered information,
type, call reference, and mandatory
element errors) for this UNI/NNI logical port.
the logical port is not performing user-
procedures, then this object is not instantiated."
::= { frMgtVCSigEntry 12 }
frMgtVCSigUserChanInactive OBJECT-
SYNTAX Counter32
UNITS "Events
MAX-ACCESS read-
STATUS
"The number of times the user-side channel
declared inactive (i.e., N392 errors in N393
events) for this UNI/NNI logical port. If
logical port is not performing user-
procedures, then this object is not instantiated."
::= { frMgtVCSigEntry 13 }
frMgtVCSigNetLinkRelErrors OBJECT-
SYNTAX Counter32
UNITS "Errors
MAX-ACCESS read-
STATUS
"The number of network-side local in-
signaling link reliability errors (i.e., non
receipt of Status/Status Enquiry messages
invalid sequence numbers in a Link
Verification Information Element) for this UNI/
logical port."
::= { frMgtVCSigEntry 14 }
frMgtVCSigNetProtErrors OBJECT-
SYNTAX Counter32
Rehbehn & Fowler Standards Track [Page 28]
RFC 2954 Frame Relay Service MIB October 2000
UNITS "Errors
MAX-ACCESS read-
STATUS
"The number of network-side local in-
signaling protocol errors (i.e.,
discriminator, message type, call reference,
mandatory information element errors) for
UNI/NNI logical port."
::= { frMgtVCSigEntry 15 }
frMgtVCSigNetChanInactive OBJECT-
SYNTAX Counter32
UNITS "Events
MAX-ACCESS read-
STATUS
"The number of times the network-side channel
declared inactive (i.e., N392 errors in N393
events) for this UNI/NNI logical port."
::= { frMgtVCSigEntry 16 }
frMgtVCSigProcedAdmin OBJECT-
SYNTAX INTEGER {
u2nnet(1),
bidirect(2),
u2nuser(3)
}
MAX-ACCESS read-
STATUS
"The value of this object identifies the
in-channel signaling procedural role that is
for this UNI/NNI logical port.
procedures implies that both user-side
network-side procedural roles are used
u2nnet(1) Logical port operates user to
procedure in the role of the
bidirect(2) Logical port operates
bidirectional procedure (both
and network side roles
u2nuser(3) Logical port operates user to
procedure in the role of the
side
Rehbehn & Fowler Standards Track [Page 29]
RFC 2954 Frame Relay Service MIB October 2000
REFERENCE "Q.933 Annex A [22],
T1.617 Annex D [17]"
DEFVAL { u2nnet }
::= { frMgtVCSigEntry 17 }
frMgtVCSigUserN391Admin OBJECT-
SYNTAX INTEGER (1..255)
UNITS "Polls
MAX-ACCESS read-
STATUS
"The value of this object identifies the
User-side N391 full status polling cycle value
this UNI/NNI logical port. If the logical port
not performing user-side (bidirectional
procedures, then this object is not instantiated."
REFERENCE "Q.933 Annex A [22],
T1.617 Annex D [17]"
::= { frMgtVCSigEntry 18 }
frMgtVCSigUserN392Admin OBJECT-
SYNTAX INTEGER (1..10)
UNITS "Events
MAX-ACCESS read-
STATUS
"The value of this object identifies the
User-side N392 error threshold value for
UNI/NNI logical port. If the logical port is
performing user-side (bidirectional) procedures
then this object is not instantiated."
REFERENCE "Q.933 Annex A [22],
T1.617 Annex D [17]"
::= { frMgtVCSigEntry 19 }
frMgtVCSigUserN393Admin OBJECT-
SYNTAX INTEGER (1..10)
UNITS "Events
MAX-ACCESS read-
STATUS
"The value of this object identifies the
User-side N393 monitored events count value
this UNI/NNI logical port. If the logical port
not performing user-side (bidirectional
procedures, then this object is not instantiated."
REFERENCE "Q.933 Annex A [22],
T1.617 Annex D [17]"
Rehbehn & Fowler Standards Track [Page 30]
RFC 2954 Frame Relay Service MIB October 2000
::= { frMgtVCSigEntry 20 }
frMgtVCSigUserT391Admin OBJECT-
SYNTAX INTEGER (5..30)
UNITS "Seconds
MAX-ACCESS read-
STATUS
"The value of this object identifies the
User-side T391 link integrity verification
timer value for this UNI/NNI logical port. If
logical port is not performing user-
procedures, then this object is not instantiated."
REFERENCE "Q.933 Annex A [22],
T1.617 Annex D [17]"
::= { frMgtVCSigEntry 21 }
frMgtVCSigNetN392Admin OBJECT-
SYNTAX INTEGER (1..10)
UNITS "Events
MAX-ACCESS read-
STATUS
"The value of this object identifies the
Network-side N392 error threshold value (nN2
LMI) for this UNI/NNI logical port. If
logical port is not performing network-
procedures, then this object is not instantiated."
REFERENCE "Q.933 Annex A [22],
T1.617 Annex D [17],
LMI [24]"
::= { frMgtVCSigEntry 22 }
frMgtVCSigNetN393Admin OBJECT-
SYNTAX INTEGER (1..10)
UNITS "Events
MAX-ACCESS read-
STATUS
"The value of this object identifies the
Network-side N393 monitored events count
(nN3 for LMI) for this UNI/NNI logical port.
the logical port is not performing network-
procedures, then this object is not instantiated."
REFERENCE "Q.933 Annex A [22],
T1.617 Annex D [17],
LMI [24]"
::= { frMgtVCSigEntry 23 }
Rehbehn & Fowler Standards Track [Page 31]
RFC 2954 Frame Relay Service MIB October 2000
frMgtVCSigNetT392Admin OBJECT-
SYNTAX INTEGER (5..30)
UNITS "Seconds
MAX-ACCESS read-
STATUS
"The value of this object identifies the
Network-side T392 polling verification timer
(nT2 for LMI) for this UNI/NNI logical port.
the logical port is not performing network-
procedures, then this object is not instantiated."
REFERENCE "Q.933 Annex A [22],
T1.617 Annex D [17],
LMI [24]"
::= { frMgtVCSigEntry 24 }
frMgtVCSigNetnT3Admin OBJECT-
SYNTAX INTEGER (5 | 10 | 15 | 20 | 25 | 30)
UNITS "Seconds
MAX-ACCESS read-
STATUS
"The value of this object identifies the
Network-side nT3 timer (for nN4 status
received) value for this UNI/NNI logical port.
the logical port is not performing network-
procedures or is not performing LMI procedures
then this object is not instantiated. This
applies only to LMI."
REFERENCE "LMI [24]"
::= { frMgtVCSigEntry 25 }
--
-- Frame Relay PVC End-
--
frPVCEndptTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"The Frame Relay PVC End-Point table. This
is used to model a PVC end-point. This
contains the traffic parameters and statistics
a PVC end-point
This table is used to identify the
parameters for a bi-directional PVC segment end
Rehbehn & Fowler Standards Track [Page 32]
RFC 2954 Frame Relay Service MIB October 2000
point, and it also provides statistics for a
segment end-point
A PVC segment end-point is identified by a UNI/
logical port index value and DLCI index value
If the frame relay service provider allows
frame relay CNM subscriber to create, modify
delete PVCs using SNMP, then this table is used
identify and reserve the requested
parameters of each PVC segment end-point.
Connection table is used to 'connect' the end
points together. Not all implementations
support the capability
creating/modifying/deleting PVCs using SNMP as
feature of frame relay CNM service
Uni-directional PVCs are modeled with zero
traffic parameters in one of the directions (In
Out direction) in this table
To create a PVC, the following procedures shall
followed
1) Create the entries for the PVC
endpoints in the frPVCEndptTable by
the traffic parameters for the bi-
PVC segment endpoints. As shown in figure 2,
point-to-point PVC has two endpoints, thus
entries in this table. Uni-directional
are modeled with zero valued
parameters in one direction; all the `In
direction parameters for one frame relay
End-point or all the `Out'
parameters for the other frame relay
Endpoint
In _____________________________
>>>>>>| |>>>>>>>>
______| Frame Relay Network |________
Out | |
<<<<<<|_____________________________|<<<<<<<<
Frame Relay Frame
PVC
Endpoint
Figure 2, PVC
Rehbehn & Fowler Standards Track [Page 33]
RFC 2954 Frame Relay Service MIB October 2000
2) Go to the Frame Relay Connection Group."
::= { frnetservObjects 3 }
frPVCEndptEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry in the Frame Relay PVC Endpoint table."
INDEX { ifIndex, frPVCEndptDLCIIndex }
::= { frPVCEndptTable 1 }
FrPVCEndptEntry ::=
SEQUENCE {
frPVCEndptDLCIIndex Integer32,
frPVCEndptInMaxFrameSize Integer32,
frPVCEndptInBc Integer32,
frPVCEndptInBe Integer32,
frPVCEndptInCIR Integer32,
frPVCEndptOutMaxFrameSize Integer32,
frPVCEndptOutBc Integer32,
frPVCEndptOutBe Integer32,
frPVCEndptOutCIR Integer32,
frPVCEndptConnectIdentifier Integer32,
frPVCEndptRowStatus RowStatus
frPVCEndptRcvdSigStatus INTEGER
frPVCEndptInFrames Counter32,
frPVCEndptOutFrames Counter32,
frPVCEndptInDEFrames Counter32,
frPVCEndptInExcessFrames Counter32,
frPVCEndptOutExcessFrames Counter32,
frPVCEndptInDiscards Counter32,
frPVCEndptInOctets Counter32,
frPVCEndptOutOctets Counter32,
frPVCEndptInDiscardsDESet Counter32,
frPVCEndptInFramesFECNSet Counter32,
frPVCEndptOutFramesFECNSet Counter32,
frPVCEndptInFramesBECNSet Counter32,
frPVCEndptOutFramesBECNSet Counter32,
frPVCEndptInCongDiscards Counter32,
frPVCEndptInDECongDiscards Counter32,
frPVCEndptOutCongDiscards Counter32,
frPVCEndptOutDECongDiscards Counter32,
frPVCEndptOutDEFrames Counter32,
frPVCEndptAtmIwfConnIndex Integer32
}
Rehbehn & Fowler Standards Track [Page 34]
RFC 2954 Frame Relay Service MIB October 2000
frPVCEndptDLCIIndex OBJECT-
SYNTAX Integer32 (16..4194303)
MAX-ACCESS not-
STATUS
"The value of this object is equal to the
value for this PVC end-point
The values are restricted to the legal range
the size of address field supported by the
port (frLportAddrDLCILen)."
REFERENCE "Q.922 [25]"
::= { frPVCEndptEntry 1 }
frPVCEndptInMaxFrameSize OBJECT-
SYNTAX Integer32 (1..4096)
UNITS "Octets
MAX-ACCESS read-
STATUS
"The value of this object is the size in octets
the largest frame relay information field for
PVC end-point in the ingress direction (into
frame relay network). The value
frPVCEndptInMaxFrameSize must be less than
equal to the corresponding ifMtu for this
relay UNI/NNI logical port."
REFERENCE "FRF.1 [31]
Q.922 [25]
Q.933 [22]"
DEFVAL { 1600 }
::= { frPVCEndptEntry 2 }
frPVCEndptInBc OBJECT-
SYNTAX Integer32 (1..2147483647)
UNITS "Bits
MAX-ACCESS read-
STATUS
"The value of this object is equal to
committed burst size (Bc) parameter (measured
bits) for this PVC end-point in the
direction (into the frame relay network).
Note that the max value of this range is
than the max value allowed by Q.933 (16383 *
10**6).
Rehbehn & Fowler Standards Track [Page 35]
RFC 2954 Frame Relay Service MIB October 2000
Note that the value is encoded in bits whilst
Q.933 Link layer core parameters
element encodes this information using
units."
REFERENCE "Q.933 [22]"
::= { frPVCEndptEntry 3 }
frPVCEndptInBe OBJECT-
SYNTAX Integer32 (1..2147483647)
UNITS "Bits
MAX-ACCESS read-
STATUS
"The value of this object is equal to the
burst size (Be) parameter (measured in bits)
this PVC end-point in the ingress direction (
the frame relay network).
Note that the max value of this range is
than the max value allowed by Q.933 (16383 *
10**6).
Note that the value is encoded in bits whilst
Q.933 Link layer core parameters
element encodes this information using
units."
REFERENCE "Q.933 [22]"
::= { frPVCEndptEntry 4 }
frPVCEndptInCIR OBJECT-
SYNTAX Integer32 (1..2147483647)
UNITS "Bits per Second
MAX-ACCESS read-
STATUS
"The value of this object is equal to
committed information rate (CIR)
(measured in bits per second) for this PVC end
point in the ingress direction (into the
relay network).
Note that the max value of this range is
than the max value allowed by Q.933 (2047 *
10**6)."
REFERENCE "Q.933 [22]"
::= { frPVCEndptEntry 5 }
frPVCEndptOutMaxFrameSize OBJECT-
Rehbehn & Fowler Standards Track [Page 36]
RFC 2954 Frame Relay Service MIB October 2000
SYNTAX Integer32 (1..4096)
UNITS "Octets
MAX-ACCESS read-
STATUS
"The value of this object is the size in octets
the largest frame relay information field for
PVC end-point in the egress direction (out of
frame relay network). The value
frPVCEndptOutMaxFrameSize must be less than
equal to the corresponding ifMtu for this
relay UNI/NNI logical port."
REFERENCE "FRF.1 [31]
Q.922 [25]
Q.933 [22]"
DEFVAL { 1600 }
::= { frPVCEndptEntry 6 }
frPVCEndptOutBc OBJECT-
SYNTAX Integer32 (1..2147483647)
UNITS "Bits
MAX-ACCESS read-
STATUS
"The value of this object is equal to
committed burst size (Bc) parameter (measured
bits) for this PVC end-point in the
direction (out of the frame relay network).
Note that the max value of this range is
than the max value allowed by Q.933 (16383 *
10**6).
Note that the value is encoded in bits whilst
Q.933 Link layer core parameters
element encodes this information using
units."
REFERENCE "Q.933 [22]"
::= { frPVCEndptEntry 7 }
frPVCEndptOutBe OBJECT-
SYNTAX Integer32 (1..2147483647)
UNITS "Bits
MAX-ACCESS read-
STATUS
"The value of this object is equal to the
burst size (Be) parameter (measured in bits)
Rehbehn & Fowler Standards Track [Page 37]
RFC 2954 Frame Relay Service MIB October 2000
this PVC end-point in the egress direction (out
the frame relay network).
Note that the max value of this range is
than the max value allowed by Q.933 (16383 *
10**6).
Note that the value is encoded in bits whilst
Q.933 Link layer core parameters
element encodes this information using
units."
REFERENCE "Q.933 [22]"
::= { frPVCEndptEntry 8 }
frPVCEndptOutCIR OBJECT-
SYNTAX Integer32 (1..2147483647)
UNITS "Bits per Second
MAX-ACCESS read-
STATUS
"The value of this object is equal to
committed information rate (CIR)
(measured in bits per second) for this PVC end
point in the egress direction (out of the
relay network).
Note that the max value of this range is
than the max value allowed by Q.933 (2047 *
10**6)."
REFERENCE "Q.933 [22]"
::= { frPVCEndptEntry 9 }
frPVCEndptConnectIdentifier OBJECT-
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-
STATUS
"This object is used to associate PVC end-
as being part of one PVC segment connection.
value of this object is equal to the value
frPVCConnectIndex, which is used as one of
indices into the frPVCConnectTable
A connection that has been cross-connected via
FR/ATM PVC Service IWF cross-connect table
return the value zero when this object is read.
case of these interworked connections,
frPVCEndptAtmIwfConnIndex object must be
Rehbehn & Fowler Standards Track [Page 38]
RFC 2954 Frame Relay Service MIB October 2000
to select the entry in the FR/ATM PVC Service
cross-connect table
The value of this object is provided by the agent
after the associated entries in
frPVCConnectTable or frAtmIwfConnectionTable
been created."
::= { frPVCEndptEntry 10 }
frPVCEndptRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This object is used to create new rows in
table, modify existing rows, and to
existing rows. To create a new PVC, the
for the PVC segment end-points in
frPVCEndptTable must first be created. Next,
frPVCConnectTable is used to associate the
relay PVC segment end-points. In order for
manager to have the necessary error diagnostics
the frPVCEndptRowStatus object must initially
set to `createAndWait(5)'. While
frPVCEndptRowStatus object is in
`createAndWait(5)' state, the manager can set
columnar object and get the necessary
diagnostics. The frPVCEndptRowStatus object
not be set to `active(1)' unless the
columnar objects exist in this row
frPVCEndptInMaxFrameSize, frPVCEndptInBc
frPVCEndptInBe, frPVCEndptInCIR
frPVCEndptOutMaxFrameSize, frPVCEndptOutBc
frPVCEndptOutBe, and frPVCEndptOutCIR."
::= { frPVCEndptEntry 11 }
frPVCEndptRcvdSigStatus OBJECT-
SYNTAX INTEGER {
deleted(1),
active(2),
inactive(3),
none(4)
}
MAX-ACCESS read-
STATUS
"The value of this object identifies the
status received via the local in-channel
Rehbehn & Fowler Standards Track [Page 39]
RFC 2954 Frame Relay Service MIB October 2000
procedures for this PVC end-point. This object
only pertinent for interfaces that perform
bidirectional procedures
Each value has the following meaning
deleted(1): This PVC is not listed in the
status reports received from
user device. The object
this value for as long as the
is not listed in the full
active(2): This PVC is reported as active,
operational, by the user device
inactive(3): This PVC is reported as inactive
or non-operational, by the
device
none(4): This interface is only using
network-side in-channel
procedures, so this object
not apply."
::= { frPVCEndptEntry 12 }
frPVCEndptInFr