idnits 2.17.1 draft-ietf-frnetmib-frs-mib-09.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 85 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 14 instances of too long lines in the document, the longest one being 7 characters in excess of 72. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 2027: '...nected with an ATM PVC MUST return the...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 3268 has weird spacing: '...for the purpo...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 24, 1999) is 8920 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '19' is defined on line 3076, but no explicit reference was found in the text == Unused Reference: '21' is defined on line 3084, but no explicit reference was found in the text == Unused Reference: '24' is defined on line 3097, but no explicit reference was found in the text == Unused Reference: '25' is defined on line 3101, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (ref. '16') (Obsoleted by RFC 3410) -- Possible downref: Non-RFC (?) normative reference: ref. '17' -- Possible downref: Non-RFC (?) normative reference: ref. '21' -- Possible downref: Non-RFC (?) normative reference: ref. '22' -- Possible downref: Non-RFC (?) normative reference: ref. '23' -- Possible downref: Non-RFC (?) normative reference: ref. '24' -- Possible downref: Non-RFC (?) normative reference: ref. '25' ** Obsolete normative reference: RFC 2233 (ref. '26') (Obsoleted by RFC 2863) ** Obsolete normative reference: RFC 1907 (ref. '27') (Obsoleted by RFC 3418) -- Possible downref: Non-RFC (?) normative reference: ref. '28' Summary: 20 errors (**), 0 flaws (~~), 8 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft Frame Relay Service MIB November 1999 3 Definitions of Managed Objects 4 for Frame Relay Service 6 November 24, 1999 8 draft-ietf-frnetmib-frs-mib-09.txt 10 Kenneth Rehbehn 11 Visual Networks 12 krehbehn@visualnetworks.com 14 David Fowler 15 Syndesis Limited 16 fowler@syndesis.com 18 Status of this Memo 20 This document is an Internet-Draft and is in full conformance with 21 all provisions of Section 10 of RFC2026. Internet-Drafts are working 22 documents of the Internet Engineering Task Force (IETF), its areas, 23 and its working groups. Note that other groups may also distribute 24 working documents as Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet- Drafts as reference 29 material or to cite them other than as ``work in progress.'' 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 Abstract 39 This memo defines an extension to the Management Information Base 40 (MIB) for use with network management protocols in TCP/IP-based 41 internets. In particular, it defines objects for managing the frame 42 relay service. 44 When published as an RFC, this document will obsolete RFC 1604. 46 Copyright Notice 48 Copyright (C) The Internet Society (1999). All Rights Reserved. 50 Table of Contents 52 1 The SNMP Management Framework ................................ 4 53 2 Overview ..................................................... 6 54 2.1 Scope of MIB ............................................... 6 55 2.2 Transiting Multiple Frame Relay Networks ................... 8 56 2.3 Access Control ............................................. 9 57 2.4 Frame Relay Service MIB Terminology ........................ 10 58 2.5 Relation to Other MIBs ..................................... 12 59 2.5.1 System Group ............................................. 12 60 2.5.2 Interfaces Table (ifTable, ifXtable) ..................... 12 61 2.5.3 Stack Table for DS1/E1 Environment ....................... 17 62 2.5.4 Stack Table for V.35 Environments ........................ 18 63 2.5.5 The Frame Relay/ATM PVC Service Interworking MIB ......... 19 64 2.6 Textual Convention Change .................................. 20 65 3 Object Definitions ........................................... 21 66 3.1 The Frame Relay Service Logical Port Group ................. 23 67 3.2 The Frame Relay Management VC Signaling Group .............. 29 68 3.3 The PVC End-Point Group .................................... 39 69 3.4 Frame Relay PVC Connection Group ........................... 52 70 3.5 Frame Relay Accounting Groups .............................. 60 71 3.6 Frame Relay Network Service TRAPS .......................... 64 72 3.7 Conformance Information .................................... 65 73 4 Acknowledgments .............................................. 76 74 5 References ................................................... 77 75 6 Security Considerations ...................................... 80 76 7 Authors' Addresses ........................................... 81 77 APPENDIX A Update Information .................................. 82 79 1. The SNMP Management Framework 81 The SNMP Management Framework presently consists of five major 82 components: 84 o An overall architecture, described in RFC 2571 [1]. 86 o Mechanisms for describing and naming objects and events for the 87 purpose of management. The first version of this Structure of 88 Management Information (SMI) is called SMIv1 and described in 89 STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The 90 second version, called SMIv2, is described in STD 58, RFC 2578 91 [5], RFC 2579 [6] and RFC 2580 [7]. 93 o Message protocols for transferring management information. The 94 first version of the SNMP message protocol is called SNMPv1 and 95 described in STD 15, RFC 1157 [8]. A second version of the SNMP 96 message protocol, which is not an Internet standards track 97 protocol, is called SNMPv2c and described in RFC 1901 [9] and 98 RFC 1906 [10]. The third version of the message protocol is 99 called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and 100 RFC 2574 [12]. 102 o Protocol operations for accessing management information. The 103 first set of protocol operations and associated PDU formats is 104 described in STD 15, RFC 1157 [8]. A second set of protocol 105 operations and associated PDU formats is described in RFC 1905 106 [13]. 108 o A set of fundamental applications described in RFC 2573 [14] and 109 the view-based access control mechanism described in RFC 2575 110 [15]. 112 A more detailed introduction to the current SNMP Management Framework 113 can be found in RFC 2570 [16]. 115 Managed objects are accessed via a virtual information store, termed 116 the Management Information Base or MIB. Objects in the MIB are 117 defined using the mechanisms defined in the SMI. 119 This memo specifies a MIB module that is compliant to the SMIv2. A 120 MIB conforming to the SMIv1 can be produced through the appropriate 121 translations. The resulting translated MIB must be semantically 122 equivalent, except where objects or events are omitted because no 123 translation is possible (use of Counter64). Some machine readable 124 information in SMIv2 will be converted into textual descriptions in 125 SMIv1 during the translation process. However, this loss of machine 126 readable information is not considered to change the semantics of the 127 MIB. 129 2. Overview 131 These objects are used to manage a frame relay Service. At present, 132 this applies to the following value of the ifType variable in the 133 IF-MIB [26]: 135 frameRelayService (44) 137 This section provides an overview and background of how to use this 138 MIB and other potential MIBs to manage a frame relay service. 140 Figure 1 shows the MIB stack that could be followed for managing a 141 frame relay service. This is only an example and not meant to be 142 inclusive. 143 ____________________________________________________ 144 | | | | | 145 | | | SIP | RFC2427 | 146 | | X.25 MIB | Relay | (no applic.| 147 | | for IW/Encap.| MIB | MIB) | 148 | | | | | 149 | MIB II |-----------------------------------| 150 | | | 151 | ifTable | Frame Relay Service MIB | 152 | ifXTable | | 153 | ifStackTable |___________________________________| 154 | | | | 155 | | Physical Layer MIBs | ATM MIB | 156 | | e.g., DS1/E1 MIB, |---------| 157 | | RS232-like MIB | Phy. | 158 | | | Layer | 159 | | | MIB | 160 |--------------|-------------------------|---------| 162 Figure 1. Frame Relay MIB Architecture 164 2.1. Scope of MIB 166 The Frame Relay Service MIB supports Customer Network Management (CNM) 167 of a frame relay network service. Through the use of this and other 168 related MIBs, a frame relay service customer's NMS can monitor the 169 customer's UNI/NNI logical ports and PVCs. It provides customers with 170 access to configuration data, performance monitoring information, and 171 fault detection for the delivered frame relay service. As an option, an 172 SNMP agent supporting the Frame Relay Service MIB may allow customer- 173 initiated PVC management operations such as creation, deletion, 174 modification, activation, and deactivation of individual PVCs. However, 175 internal aspects of the network (e.g., switching elements, line cards, 176 and network routing tables) are beyond the scope of this MIB. 178 The Frame Relay Service MIB models all interfaces and PVCs delivered by 179 a frame relay service within a single virtual SNMP system for the 180 purpose of comprehensively representing the customer's frame relay 181 service. The customer's interfaces and PVCs may physically exist on one 182 or more devices within the network topology. An SNMP agent providing 183 support for the Frame Relay Service MIB as well as other appropriate 184 MIBs to model a single virtual frame relay network service is referred 185 to as a Frame Relay Service (FRS) agent. Internal communication 186 mechanisms between the FRS agent and individual devices within the frame 187 relay network delivering the service are implementation specific and 188 beyond the scope of this MIB. 190 The customer's NMS will typically access the SNMP agent implementing the 191 Frame Relay Service MIB over a frame relay permanent virtual connection 192 (PVC). SNMP access over a frame relay PVC is achieved through the use 193 of SNMP over UDP over IP encapsulated in Frame Relay according to STD 194 55, RFC2427 and ITU X.36 Annex D [23]. Alternate access mechanisms and 195 SNMP agent implementations are possible. 197 This MIB will NOT be implemented on user equipment (e.g., DTE). Such 198 devices are managed using the Frame Relay DTE MIB (RFC2115[18]). 199 However, concentrators may use the Frame Relay Service MIB instead of 200 the Frame Relay DTE MIB. 202 This MIB does not define managed objects for the physical layer. 203 Existing physical layer MIBs (e.g., DS1 MIB) and MIB II will be used as 204 needed in FRS Agent implementations. 206 This MIB supports frame relay PVCs. This MIB may be extended at a later 207 time to handle frame relay SVCs. 209 A switch implementation may support this MIB for the purpose of 210 configuration and control of the frame relay service beyond the scope of 211 traditional customer network management applications. A number of 212 objects (e.g. frLportTypeAdmin) support administrative actions that 213 impact the operation of frame relay switch equipment in the network. 214 This is reflected in the differences between the two MIB compliance 215 modules: 217 o the frame relay service compliance module (frnetservCompliance), 218 and 220 o the frame relay switch compliance module 221 (frnetSwitchCompliance). 223 The frame relay service compliance module does not support the 224 administrative control objects used for switch management. 226 2.2. Transiting Multiple Frame Relay Networks 228 This MIB is only used to manage a single frame relay service offering 229 from one network service provider. Therefore, if a customer PVC 230 traverses multiple networks, then the customer must poll a different FRS 231 agent within each frame relay network to retrieve the end-to-end view of 232 service. 234 Figure 2 illustrates a customer ("User B") NMS accessing FRS agents in 235 three different frame relay networks (I, J, and K). 237 +-------------------------------------+ 238 | Customer Network Management Station | 239 | (SNMP based) | 240 +-------------------------------------+ 241 ^ ^ ^ 242 | | | 243 | | | 244 UNI | NNI | NNI | UNI 245 | ^ | ^ | ^ 246 | +-----------+ | +-----------+ | +-----------+ | 247 | | | | | | | | | | 248 Originating | | FR | | | FR | | | FR | | Terminating 249 +--------+ | | Network I | | | Network J | | | Network K | | +--------+ 250 | | | | | | | | | | | | | | 251 | |---| |---| |---| |---| User B | 252 | | | | | | | | | | | | | | 253 | //////////////////////////////////////////////////////////// | 254 | | | | | | | | | | | | | | 255 +--------+ | +-----------+ | +-----------+ | +-----------+ | +--------+ 256 | | | | 257 | | | | 258 | PVC Segment 1 | PVC Segment 2 | PVC Segment 3 | 259 |<------------->|<------------->|<------------->| 260 | | 261 | Multi-network PVC | 262 |<--------------------------------------------->| 263 | NNI = Network-to Network Interface | 264 UNI = User-to-Network Interface 266 Figure 2. Multi-network PVC 268 2.3. Access Control 270 A frame relay network is shared amongst many frame relay subscribers. 271 Each subscriber will only have access to their information (e.g., 272 information with respect to their interfaces and PVCs). The FRS agent 273 SHOULD provide instance level granularity for MIB views. 275 2.4. Frame Relay Service MIB Terminology 277 Access Channel - An access channel generically refers to the DS1/E1 278 or DS3/E3-based UNI access channel or NNI access channel across which 279 frame relay data transits. An access channel is the access pathway 280 for a single stream of user data. 282 Within a given T1 line, an access channel can denote any one of the 283 following: 285 o Unchannelized T1 - the entire T1 line is considered an access 286 channel. Each access channel is comprised of 24 T1 time slots. 288 o Channelized T1 - an access channel is any one of 24 channels. 289 Each access channel is comprised of a single T1 time slot. 291 o Fractional T1 - an access channel is a grouping of N T1 time 292 slots (NX56/64 Kbps, where N = 1-23 T1 Time slots per FT1 Access 293 Channel) that may be assigned in consecutive or non-consecutive 294 order. 296 Within a given E1 line, a channel can denote any one of the following: 298 o Unchannelized E1 - the entire E1 line is considered a single 299 access channel. Each access channel is comprised of 31 E1 time 300 slots. 302 o Channelized E1 - an access channel is any one of 31 channels. 303 Each access channel is comprised of a single E1 time slot. 305 o Fractional E1 - an access channel is a grouping of N E1 time 306 slots (NX64 Kbps, where N = 1-30 E1 time slots per FE1 access 307 channel) that may be assigned in consecutive or non-consecutive 308 order. 310 Within a given unformatted line, the entire unformatted line is 311 considered an access channel. Examples include RS-232, V.35, V.36 and 312 X.21 (non- switched), and unframed E1 (G.703 without G.704). 314 Access Rate - The data rate of the access channel, expressed in 315 bits/second. The speed of the user access channel determines how 316 rapidly the end user can inject data into the network. 318 Bc - The Committed Burst Size (Bc) is the maximum amount of 319 subscriber data (expressed in bits) that the network agrees to 320 transfer, under normal conditions, during a time interval Tc. 322 Be - The Excess Burst Size (Be) is the maximum amount of subscriber 323 data (expressed in bits) in excess of Bc that the network will 324 attempt to deliver during the time interval Tc. This data (Be) is 325 delivered in general with a lower probability than Bc. 327 CIR - The Committed Information Rate (CIR) is the subscriber data 328 rate (expressed in bits/second) that the network commits to deliver 329 under normal network conditions. CIR is averaged over the time 330 interval Tc (CIR = Bc/Tc). 332 DLCI - Data Link Connection Identifier 334 Logical Port - This term is used to model the frame relay "interface" 335 on a device. 337 NNI - Network to Network Interface 339 Permanent Virtual Connection (PVC) - A virtual connection that has 340 its end-points and bearer capabilities defined at subscription time. 342 Time slot (E1) - An octet within the 256-bit information field in 343 each E1 frame is defined as a time slot. Time slots are position 344 sensitive within the 256-bit information field. Fractional E1 service 345 is provided in contiguous or non-contiguous time slot increments. 347 Time slot (T1) - An octet within the 192-bit information field in 348 each T1 frame is defined as a time slot. Time slots are position 349 sensitive within the 192-bit information field. Fractional T1 service 350 is provided in contiguous or non-contiguous time slot increments. 352 UNI - User to Network Interface 354 N391 - Full status (status of all PVCs) polling counter 356 N392 - Error threshold 358 N393 - Monitored events count 360 T391 - Link integrity verification polling timer 362 T392 - Polling verification timer 364 nT3 - Status enquiry timer 365 nN3 - Maximum status enquiry counter 367 2.5. Relation to Other MIBs 369 2.5.1. System Group 371 Use the System Group of the SNMPv2-MIB [27] to describe the Frame 372 Relay Service (FRS) agent. The FRS agent may be monitoring many 373 frame relay devices in one network. The System Group does not 374 describe frame relay devices monitored by the FRS agent. 376 sysDescr: ASCII string describing the FRS agent. 377 Can be up to 255 characters long. This field is 378 generally used to indicate the network providers 379 identification and type of service offered. 381 sysObjectID: Unique OBJECT IDENTIFIER (OID) for the 382 FRS agent. 384 sysUpTime: Clock in the FRS agent; TimeTicks 385 in 1/100s of a second. Elapsed type since 386 the FRS agent came on line. 388 sysContact: Contact for the FRS agent. 389 ASCII string of up to 255 characters. 391 sysName: Domain name of the FRS agent, for example, 392 acme.com 394 sysLocation: Location of the FRS agent. 395 ASCII string of up to 255 characters. 397 sysServices: Services of the managed device. The value "2", 398 which implies that 399 the frame relay network is providing 400 a subnetwork level service, is recommended. 402 2.5.2. Interfaces Table (ifTable, ifXtable) 404 This specifies how the Interfaces Group defined in the IF MIB [26] shall 405 be used for the management of frame relay based interfaces, and in 406 conjunction with the Frame Relay Service MIB module. This memo assumes 407 the interpretation of the evolution of the Interfaces group to be in 408 accordance with: "The interfaces table (ifTable) contains information on 409 the managed resource's interfaces. Each sub- layer below the 410 internetwork layer of a network interface is considered an interface." 411 Thus, the ifTable allows the following frame relay-based interfaces to 412 be represented as table entries: 414 - Frame relay interfaces in the frame relay equipment (e.g., 415 switches, routers or networks) with frame relay interfaces. 416 This level is concerned with generic frame counts and 417 not with individual virtual connections. 419 In accordance with the guidelines of ifTable, frame counts per virtual 420 connection are not covered by ifTable, and are considered interface 421 specific and covered in the Frame Relay Service MIB module. In order to 422 interrelate the ifEntries properly, the Interfaces Stack Group shall be 423 supported. 425 Some specific interpretations of ifTable for frame relay follow. 427 Object Use for the generic Frame Relay layer 428 ====== ============================================= 429 ifIndex Each frame relay port is represented by an 430 ifEntry. 432 ifDescr Description of the frame relay interface. 433 ASCII string describing the UNI/NNI logical 434 port. Can be up to 255 characters long. 436 ifType The value allocated for Frame Relay Service 437 is equal to 44. 439 ifMtu Set to maximum frame size in octets for this 440 frame relay logical port. 442 ifSpeed Peak bandwidth in bits per second available 443 for use. This could be the speed of the 444 logical port and not the access rate. Actual 445 user information transfer rate (i.e., access 446 rate) of the UNI or NNI logical port in bits 447 per second (this is not the clocking speed). 448 For example, it is 1,536,000 bits per second 449 for a DS1-based UNI/NNI logical port and 450 1,984,000 bits per second for an E1-based 451 UNI/NNI logical port. 453 ifPhysAddress The primary address for this logical port 454 assigned by the frame relay interface 455 provider. An octet string of zero length if 456 no address is used for this logical port. 458 ifAdminStatus The desired administrative status of the 459 frame relay logical port. 461 ifOperStatus The current operational status of the Frame 462 Relay UNI or NNI logical port. 464 ifLastChange The value of sysUptime at the last 465 re-initialization of the logical port. The 466 value of sysUpTime at the time the logical 467 port entered its current operational state. 468 If the current state was entered prior to the 469 last re-initialization of the local network 470 management subsystem, then this object 471 contains a zero value. 473 ifInOctets The number of received octets. This counter 474 only counts octets from the beginning of the 475 frame relay header field to the end of user 476 data. 478 ifInUcastPkts The number of received unerrored, unicast 479 frames. 481 ifInDiscards The number of received frames discarded. 482 Specifically, frames discarded due to ingress 483 buffer congestion and traffic policing. 485 ifInErrors The number of received frames that are 486 discarded because of an error. Specifically, 487 frames that are too long or too short, frames 488 that are not a multiple of 8 bits in length, 489 frames with an invalid or unrecognized DLCI, 490 frames with an abort sequence, frames with 491 improper flag delimitation, and frame that 492 fail FCS. 494 ifInUnknownProtos The number of packets discarded because of an 495 unknown or unsupported protocol. For Frame 496 Relay Service interfaces, this counter will 497 always be zero. 499 ifOutOctets The number of transmitted octets. This 500 counter only counts octets from the beginning 501 of the frame relay header field to the end of 502 user data. 504 ifOutUcastpkts The number of unerrored, unicast frames sent. 506 ifOutDiscards The number of frames discarded in the egress 507 direction. Possible reasons are as follows: 508 policing, congestion. 510 ifOutErrors The number of frames discarded in the egress 511 direction because of an error. Specifically, 512 frames that are aborted due to a transmitter 513 underrun. 515 ifName This variable is not applicable for Frame 516 Relay Service interfaces, therefore, this 517 variable contains a zero-length string. 519 ifInMulticastPkts The number of received unerrored, multicast 520 frames. 522 ifInBroadcastPkts This variable is not applicable for Frame 523 Relay Service interfaces, therefore, this 524 counter is always zero. 526 ifOutMulticastPkts The number of sent unerrored, multicast 527 frames. 529 ifOutBroadcastPkts This variable is not applicable for Frame 530 Relay Service interfaces, therefore, this 531 counter is always zero. 533 ifHCInOctets Only used for DS3-based (and greater) Frame 534 Relay logical ports. The number of received 535 octets. This counter only counts octets 536 from the beginning of the frame relay header 537 field to the end of user data. 539 ifHCOutOctets Only used for DS3-based (and greater) Frame 540 Relay logical ports. The number of 541 transmitted octets. This counter only counts 542 octets from the beginning of the frame relay 543 header field to the end of user data. 545 ifLinkUpDownTrapEnable Set to true(1). It is recommended that the 546 underlying physical layer traps be disabled 547 since both are not required. Traps are 548 enabled at the frame relay service layer 549 specifically because PVC traps are not to be 550 sent if the frame relay interface fails. 551 Without a linkUp/linkDown trap, the 552 management station would receive no 553 notification of the failure. 555 ifHighSpeed Set to the user data rate of the frame relay 556 logical port in millions of bits per second. 557 If the user data rate is less than 1 Mbps, 558 then this value is zero. 560 ifPromiscuousMode Set to false(2). 562 ifConnectorPresent Set to false(2). 564 Frame relay network service interfaces support the Interface Stack 565 Group. Frame relay network service interfaces do not support any other 566 groups or objects in the Interfaces group of the IF MIB. 568 2.5.3. Stack Table for DS1/E1 Environment This section describes by 569 example how to use ifStackTable to represent the relationship of frame 570 relay service to ds0 and ds0Bundles with ds1 interfaces. [20] 572 Example: A frame relay service is being carried on 4 ds0s of a ds1. 574 +---------------------+ 575 | Frame Relay Service | 576 +---------------------+ 577 | 578 +---------------------+ 579 | ds0Bundle | 580 +---------------------+ 581 | | | | 582 +---+ +---+ +---+ +---+ 583 |ds0| |ds0| |ds0| |ds0| 584 +---+ +---+ +---+ +---+ 585 | | | | 586 +---------------------+ 587 | ds1 | 588 +---------------------+ 590 The assignment of the index values could for example be: 592 ifIndex Description 593 1 FrameRelayService (type 44) 594 2 ds0Bundle (type 82) 595 3 ds0 #1 (type 81) 596 4 ds0 #2 (type 81) 597 5 ds0 #3 (type 81) 598 6 ds0 #4 (type 81) 599 7 ds1 (type 18) 601 The ifStackTable is then used to show the relationships between the 602 various interfaces. 604 ifStackTable Entries 606 HigherLayer LowerLayer 607 0 1 608 1 2 609 2 3 610 2 4 611 2 5 612 2 6 613 3 7 614 4 7 615 5 7 616 6 7 617 7 0 619 In the case where the frame relay service is using a single ds0, then 620 the ds0Bundle is not required. 622 +---------------------+ 623 | Frame Relay Service | 624 +---------------------+ 625 | 626 +---+ 627 |ds0| 628 +---+ 629 | 630 +---------------------+ 631 | ds1 | 632 +---------------------+ 634 The assignment of the index values could for example be: 636 ifIndex Description 637 1 FrameRelayService (type 44) 638 2 ds0 (type 81) 639 3 ds1 (type 18) 641 The ifStackTable is then used to show the relationships between the 642 various interfaces. 644 ifStackTable Entries 646 HigherLayer LowerLayer 647 0 1 648 1 2 649 2 3 650 3 0 652 2.5.4. Stack Table for V.35 Environments 654 This section describes by example how to use ifStackTable to 655 represent the relationship of frame relay service with V.35 656 interfaces. 658 +---------------------+ 659 | Frame Relay Service | 660 +---------------------+ 661 | 662 +---------------------+ 663 | v35 | 664 +---------------------+ 666 An example of index values in this case could be: 668 ifIndex Description 669 1 FrameRelayService (type 44) 670 2 v35 (type 33) 672 Note type 33 (RS232-like MIB) is used instead of type 45 (V.35). V35 673 does not pertain to this environment. 675 The ifStackTable is then used to show the relationships between the 676 various interfaces. 678 ifStackTable Entries 680 HigherLayer LowerLayer 681 0 1 682 1 2 683 2 0 685 2.5.5. The Frame Relay/ATM PVC Service Interworking MIB 687 Connections between two frame relay endpoints are represented with an 688 entry in the frPVCConnectTable of this MIB. Both endpoints are 689 represented with rows in the frPVCEndptTable. The 690 frPVCEndptConnectIdentifier object of each endpoint points to the 691 frPVCConnectTable cross-connect table row for the connection. 693 In contrast, a connection that spans frame relay and ATM endpoints is 694 represented with an entry in the frAtmIwfConnectionTable of the 695 FR/ATM PVC Service Interworking MIB defined in [28]. 697 In the case of an inter-worked connection, the 698 frPVCEndptConnectIdentifier object is set to zero. Instead, the 699 frPVCEndptAtmIwfConnIndex object is set to the index of the FR/ATM 700 IWF cross-connect table row. 702 The frame relay PVC cross-connect table (frPVCConnectTable) does not 703 contain an entry for the FR/ATM inter-worked connection. 705 2.6. Textual Convention Change 707 Version 1 of the Frame Relay Service MIB contains MIB objects defined 708 with the (now obsolete) DisplayString textual convention. In version 2 709 of this MIB, the syntax for these objects has been updated to use the 710 (now preferred) SnmpAdminString textual convention. 712 The working group realizes that this change is not strictly supported by 713 SMIv2. In our judgment, the alternative of deprecating the old objects 714 and defining new objects would have a more adverse impact on backward 715 compatibility and interoperability, given the particular semantics of 716 these objects. 718 3. Object Definitions 720 FRNETSERV-MIB DEFINITIONS ::= BEGIN 722 IMPORTS 723 MODULE-IDENTITY, OBJECT-TYPE, 724 NOTIFICATION-TYPE, transmission, 725 Counter32, Integer32 FROM SNMPv2-SMI 726 TimeStamp, RowStatus FROM SNMPv2-TC 727 MODULE-COMPLIANCE, OBJECT-GROUP, 728 NOTIFICATION-GROUP FROM SNMPv2-CONF 729 InterfaceIndex, ifIndex FROM IF-MIB 730 SnmpAdminString FROM SNMP-FRAMEWORK-MIB; 732 frnetservMIB MODULE-IDENTITY 733 LAST-UPDATED "9911240000Z" 734 ORGANIZATION "IETF Frame Relay Service MIB Working Group" 735 CONTACT-INFO 736 "Kenneth Rehbehn 737 Postal: Visual Networks 738 2092 Gaither Road 739 Rockville, MD USA 20850 740 Tel: +1 301 296 2325 741 Fax: +1 301 296 2302 742 E-mail: krehbehn@visualnetworks.com 744 David Fowler 745 Postal: Syndesis Limited 746 28 Fulton Way 747 Richmond Hill, Ontario, Canada L4B 1J5 748 Tel: +1 905 886 7818 749 Fax: +1 905 886 9076 750 E-mail: fowler@syndesis.com" 752 DESCRIPTION 753 "The MIB module to describe generic objects for 754 Frame Relay Network Service." 756 -- 757 -- Revision History 758 -- 759 REVISION "9911240000Z" 760 DESCRIPTION 761 "Published as RFC xxxx 762 o Add frPVCEndptAtmIwfConnIndex object to 763 select FR/ATM Service IWF cross-connect entry 764 o Overview re-written for clarity 765 o Clarify role of system group 766 o Removed indexes from NOTIFICATIONS 767 o Add R/W switch-specific compliance module 768 o Add R/W administration objects for switch configuration 769 o Remove reference to obsolete I-D on CNM 770 o Added an instance of frPVCEndptRcvdSigStatus for each 771 endpoint to the Connect Status Change Trap 772 o Additional PVC counters added 773 o Added frPVCConnectUserName and frPVCConnectProviderName 774 o Added MIB objects in support for FRF.12 fragmentation" 776 REVISION "9311161200Z" 777 DESCRIPTION 778 "Published as RFC 1604." 779 ::= { transmission 44 } 781 frnetservObjects OBJECT IDENTIFIER ::= { frnetservMIB 1 } 782 frnetservTraps OBJECT IDENTIFIER ::= { frnetservMIB 2 } 783 frnetservTrapsPrefix OBJECT IDENTIFIER ::= { frnetservTraps 0 } 785 -- The Frame Relay Service Logical Port Group 787 -- the Frame Relay Logical Port Group 788 -- This table is an interface specific addendum 789 -- to the generic ifTable from MIB-II. 791 frLportTable OBJECT-TYPE 792 SYNTAX SEQUENCE OF FrLportEntry 793 MAX-ACCESS not-accessible 794 STATUS current 795 DESCRIPTION 796 "The Frame Relay Logical Port Information table." 797 ::= { frnetservObjects 1 } 799 frLportEntry OBJECT-TYPE 800 SYNTAX FrLportEntry 801 MAX-ACCESS not-accessible 802 STATUS current 803 DESCRIPTION 804 "An entry in the Frame Relay Logical Port 805 Information table." 806 INDEX { ifIndex } 807 ::= { frLportTable 1 } 809 FrLportEntry ::= 810 SEQUENCE { 811 frLportNumPlan INTEGER, 812 frLportContact SnmpAdminString, 813 frLportLocation SnmpAdminString, 814 frLportType INTEGER, 815 frLportAddrDLCILen INTEGER, 816 frLportVCSigProtocol INTEGER, 817 frLportVCSigPointer OBJECT IDENTIFIER, 818 frLportDLCIIndexValue Integer32, 819 frLportTypeAdmin INTEGER, 820 frLportVCSigProtocolAdmin INTEGER, 821 frLportVCSigPointerAdmin OBJECT IDENTIFIER, 822 frLportFragControl INTEGER, 823 frLportFragSize Integer32 824 } 826 frLportNumPlan OBJECT-TYPE 827 SYNTAX INTEGER { 828 other(1), 829 e164(2), 830 x121(3), 831 none(4) 832 } 833 MAX-ACCESS read-only 834 STATUS current 835 DESCRIPTION 836 "The value of this object identifies the network 837 address numbering plan for this UNI/NNI logical 838 port. The network address is the object 839 ifPhysAddress. The value none implies that there 840 is no ifPhysAddress. The FRS agent will return an 841 octet string of zero length for ifPhysAddress. The 842 value other means that an address has been 843 assigned to this interface, but the numbering plan 844 is not enumerated here." 845 ::= { frLportEntry 1 } 847 frLportContact OBJECT-TYPE 848 SYNTAX SnmpAdminString (SIZE(0..255)) 849 MAX-ACCESS read-only 850 STATUS current 851 DESCRIPTION 852 "The value of this object identifies the network 853 contact for this UNI/NNI logical port." 854 ::= { frLportEntry 2 } 856 frLportLocation OBJECT-TYPE 857 SYNTAX SnmpAdminString (SIZE(0..255)) 858 MAX-ACCESS read-only 859 STATUS current 860 DESCRIPTION 861 "The value of this object identifies the frame 862 relay network location for this UNI/NNI logical 863 port." 864 ::= { frLportEntry 3 } 866 frLportType OBJECT-TYPE 867 SYNTAX INTEGER { 868 uni(1), 869 nni(2) 870 } 871 MAX-ACCESS read-only 872 STATUS current 873 DESCRIPTION 874 "The value of this object identifies the type of 875 network interface for this logical port." 876 ::= { frLportEntry 4 } 878 frLportAddrDLCILen OBJECT-TYPE 879 SYNTAX INTEGER { 880 twoOctets10Bits(1), 881 threeOctets10Bits(2), 882 threeOctets16Bits(3), 883 fourOctets17Bits(4), 884 fourOctets23Bits(5) 885 } 886 UNITS "Octets" 887 MAX-ACCESS read-only 888 STATUS current 889 DESCRIPTION 890 "The value of this object identifies the Q.922 891 Address field length and DLCI length for this 892 UNI/NNI logical port." 893 REFERENCE "Q.922 [25]" 894 ::= { frLportEntry 5 } 896 frLportVCSigProtocol OBJECT-TYPE 897 SYNTAX INTEGER { 898 none(1), 899 lmi(2), 900 ansiT1617D(3), 901 ansiT1617B(4), 902 ccittQ933A(5) 903 } 904 MAX-ACCESS read-only 905 STATUS current 906 DESCRIPTION 907 "The value of this object identifies the Local 908 In-Channel Signaling Protocol that is used for 909 this frame relay UNI/NNI logical port." 910 ::= { frLportEntry 6 } 912 frLportVCSigPointer OBJECT-TYPE 913 SYNTAX OBJECT IDENTIFIER 914 MAX-ACCESS read-only 915 STATUS current 916 DESCRIPTION 917 "The value of this object is used as a pointer to 918 the table that contains the Local In-Channel 919 Signaling Protocol parameters and errors for this 920 UNI/NNI logical port. See the Frame Relay 921 Management VC Signaling Parameters and Errors 922 Group." 923 ::= { frLportEntry 7 } 925 frLportDLCIIndexValue OBJECT-TYPE 926 SYNTAX Integer32 927 MAX-ACCESS read-only 928 STATUS current 929 DESCRIPTION 930 "This object contains an appropriate value to be 931 used for frPVCEndptDLCIIndex when creating entries 932 in the frPVCEndptTable. The value 0 indicates 933 that no unassigned entries are available. To 934 obtain the frPVCEndptDLCIIndex value for a new 935 entry, the manager issues a management protocol 936 retrieval operation to obtain the current value of 937 this object. After each retrieval, the agent 938 should modify the value to the next unassigned 939 index." 940 ::= { frLportEntry 8 } 942 frLportTypeAdmin OBJECT-TYPE 943 SYNTAX INTEGER { 944 uni(1), 945 nni(2) 946 } 947 MAX-ACCESS read-write 948 STATUS current 949 DESCRIPTION 950 "The value of this object desired identifies the 951 type of network interface for this logical port." 952 ::= { frLportEntry 9 } 954 frLportVCSigProtocolAdmin OBJECT-TYPE 955 SYNTAX INTEGER { 956 none(1), 957 lmi(2), 958 ansiT1617D(3), 959 ansiT1617B(4), 960 ccittQ933A(5) 961 } 962 MAX-ACCESS read-write 963 STATUS current 964 DESCRIPTION 965 "The value of this object identifies the desired 966 Local In-Channel Signaling Protocol that is used 967 for this frame relay UNI/NNI logical port. This 968 value must be made the active protocol as soon as 969 possible on the device." 970 ::= { frLportEntry 10 } 972 frLportVCSigPointerAdmin OBJECT-TYPE 973 SYNTAX OBJECT IDENTIFIER 974 MAX-ACCESS read-write 975 STATUS current 976 DESCRIPTION 977 "The value of this object is used as the desired 978 value of a pointer to the table that contains the 979 Local In-Channel Signaling Protocol parameters and 980 errors for this UNI/NNI logical port. See the 981 Frame Relay Management VC Signaling Parameters and 982 Errors Group. This value must be made active as 983 soon as possible on the device." 984 ::= { frLportEntry 11 } 986 frLportFragControl OBJECT-TYPE 987 SYNTAX INTEGER { 988 on(1), 989 off(2) 990 } 991 MAX-ACCESS read-write 992 STATUS current 993 DESCRIPTION 994 "This object controls the transmission and 995 reception of fragmentation frames for this UNI or 996 NNI interface. 997 on(1) Frames are fragmented using the interface 998 fragmentation format 999 Note: The customer side of the interface 1000 must also be configured to fragment frames. 1001 off(2) Frames are not fragmented using the interface 1002 fragmentation format." 1003 REFERENCE "FRF.12 [21]" 1004 DEFVAL { off } 1005 ::= { frLportEntry 12 } 1007 frLportFragSize OBJECT-TYPE 1008 SYNTAX Integer32 (0..8184) 1009 UNITS "Octets" 1010 MAX-ACCESS read-write 1011 STATUS current 1012 DESCRIPTION 1013 "The value of this object is the size in octets of 1014 the maximum size of each fragment to be sent when 1015 fragmenting. This object is only used by the 1016 fragmentation transmitter, and the two sides of 1017 the interface may differ. The fragment size 1018 includes the octets for the frame relay header, 1019 the UI octet, the NLPID, the fragmentation header, 1020 and the fragment payload. If frLportFragControl 1021 is set to off, this value should be zero. The 1022 fragment size range is derived as follows: 8192 - 1023 max 4 octet header - max 4 octet FCS" 1024 REFERENCE "FRF.12 [21]" 1025 DEFVAL { 0 } 1026 ::= { frLportEntry 13 } 1028 -- the Frame Relay Management VC Signaling Group 1030 -- This Group contains managed objects for the 1031 -- Local In-Channel Signaling Parameters and 1032 -- for signaling errors. 1034 frMgtVCSigTable OBJECT-TYPE 1035 SYNTAX SEQUENCE OF FrMgtVCSigEntry 1036 MAX-ACCESS not-accessible 1037 STATUS current 1038 DESCRIPTION 1039 "The Frame Relay Management VC Signaling 1040 Parameters and Errors table." 1041 ::= { frnetservObjects 2 } 1043 frMgtVCSigEntry OBJECT-TYPE 1044 SYNTAX FrMgtVCSigEntry 1045 MAX-ACCESS not-accessible 1046 STATUS current 1047 DESCRIPTION 1048 "An entry in the Frame Relay Management VC 1049 Signaling Parameters Errors table." 1050 INDEX { ifIndex } 1051 ::= { frMgtVCSigTable 1 } 1053 FrMgtVCSigEntry ::= 1054 SEQUENCE { 1055 frMgtVCSigProced INTEGER, 1056 frMgtVCSigUserN391 INTEGER, 1057 frMgtVCSigUserN392 INTEGER, 1058 frMgtVCSigUserN393 INTEGER, 1059 frMgtVCSigUserT391 INTEGER, 1060 frMgtVCSigNetN392 INTEGER, 1061 frMgtVCSigNetN393 INTEGER, 1062 frMgtVCSigNetT392 INTEGER, 1063 frMgtVCSigNetnN4 INTEGER, 1064 frMgtVCSigNetnT3 INTEGER, 1065 frMgtVCSigUserLinkRelErrors Counter32, 1066 frMgtVCSigUserProtErrors Counter32, 1067 frMgtVCSigUserChanInactive Counter32, 1068 frMgtVCSigNetLinkRelErrors Counter32, 1069 frMgtVCSigNetProtErrors Counter32, 1070 frMgtVCSigNetChanInactive Counter32, 1071 frMgtVCSigProcedAdmin INTEGER, 1072 frMgtVCSigUserN391Admin INTEGER, 1073 frMgtVCSigUserN392Admin INTEGER, 1074 frMgtVCSigUserN393Admin INTEGER, 1075 frMgtVCSigUserT391Admin INTEGER, 1076 frMgtVCSigNetN392Admin INTEGER, 1077 frMgtVCSigNetN393Admin INTEGER, 1078 frMgtVCSigNetT392Admin INTEGER, 1079 frMgtVCSigNetnT3Admin INTEGER 1080 } 1082 frMgtVCSigProced OBJECT-TYPE 1083 SYNTAX INTEGER { 1084 u2nnet(1), 1085 bidirect(2), 1086 u2nuser(3) 1087 } 1088 MAX-ACCESS read-only 1089 STATUS current 1090 DESCRIPTION 1091 "The value of this object identifies the Local 1092 In-Channel Signaling Procedure that is used for 1093 this UNI/NNI logical port. Bidirectional 1094 procedures implies that both user-side and 1095 network-side procedures are used." 1096 ::= { frMgtVCSigEntry 1 } 1098 frMgtVCSigUserN391 OBJECT-TYPE 1099 SYNTAX INTEGER (1..255) 1100 UNITS "Polls" 1101 MAX-ACCESS read-only 1102 STATUS current 1103 DESCRIPTION 1104 "The value of this object identifies the User-side 1105 N391 full status polling cycle value for this 1106 UNI/NNI logical port. If the logical port is not 1107 performing user-side (bidirectional) procedures, 1108 then this object is not instantiated and an 1109 attempt to read will result in the noSuchInstance 1110 exception response." 1111 REFERENCE "Q.933 Annex A [22], 1112 T1.617 Annex D [17]" 1113 DEFVAL { 6 } 1114 ::= { frMgtVCSigEntry 2 } 1116 frMgtVCSigUserN392 OBJECT-TYPE 1117 SYNTAX INTEGER (1..10) 1118 UNITS "Events" 1119 MAX-ACCESS read-only 1120 STATUS current 1121 DESCRIPTION 1122 "The value of this object identifies the User-side 1123 N392 error threshold value for this UNI/NNI 1124 logical port. If the logical port is not 1125 performing user-side (bidirectional) procedures, 1126 then this object is not instantiated." 1127 REFERENCE "Q.933 Annex A [22], 1128 T1.617 Annex D [17]" 1129 DEFVAL { 3 } 1130 ::= { frMgtVCSigEntry 3 } 1132 frMgtVCSigUserN393 OBJECT-TYPE 1133 SYNTAX INTEGER (1..10) 1134 UNITS "Events" 1135 MAX-ACCESS read-only 1136 STATUS current 1137 DESCRIPTION 1138 "The value of this object identifies the User-side 1139 N393 monitored events count value for this UNI/NNI 1140 logical port. If the logical port is not 1141 performing user-side (bidirectional) procedures, 1142 then this object is not instantiated." 1143 REFERENCE "Q.933 Annex A [22], 1144 T1.617 Annex D [17]" 1145 DEFVAL { 4 } 1146 ::= { frMgtVCSigEntry 4 } 1148 frMgtVCSigUserT391 OBJECT-TYPE 1149 SYNTAX INTEGER (5..30) 1150 UNITS "Seconds" 1151 MAX-ACCESS read-only 1152 STATUS current 1153 DESCRIPTION 1154 "The value of this object identifies the User-side 1155 T391 link integrity verification polling timer 1156 value for this UNI/NNI logical port. If the 1157 logical port is not performing user-side 1158 procedures, then this object is not instantiated." 1159 REFERENCE "Q.933 Annex A [22], 1160 T1.617 Annex D [17]" 1161 DEFVAL { 10 } 1162 ::= { frMgtVCSigEntry 5 } 1164 frMgtVCSigNetN392 OBJECT-TYPE 1165 SYNTAX INTEGER (1..10) 1166 UNITS "Events" 1167 MAX-ACCESS read-only 1168 STATUS current 1169 DESCRIPTION 1170 "The value of this object identifies the Network- 1171 side N392 error threshold value (nN2 for LMI) for 1172 this UNI/NNI logical port. If the logical port is 1173 not performing network-side procedures, then this 1174 object is not instantiated." 1175 REFERENCE "Q.933 Annex A [22], 1176 T1.617 Annex D [17], 1177 LMI [24]" 1178 DEFVAL { 3 } 1179 ::= { frMgtVCSigEntry 6 } 1181 frMgtVCSigNetN393 OBJECT-TYPE 1182 SYNTAX INTEGER (1..10) 1183 UNITS "Events" 1184 MAX-ACCESS read-only 1185 STATUS current 1186 DESCRIPTION 1187 "The value of this object identifies the Network- 1188 side N393 monitored events count value (nN3 for 1189 LMI) for this UNI/NNI logical port. If the 1190 logical port is not performing network-side 1191 procedures, then this object is not instantiated." 1192 REFERENCE "Q.933 Annex A [22], 1193 T1.617 Annex D [17], 1194 LMI [24]" 1195 DEFVAL { 4 } 1196 ::= { frMgtVCSigEntry 7 } 1198 frMgtVCSigNetT392 OBJECT-TYPE 1199 SYNTAX INTEGER (5..30) 1200 UNITS "Seconds" 1201 MAX-ACCESS read-only 1202 STATUS current 1203 DESCRIPTION 1204 "The value of this object identifies the Network- 1205 side T392 polling verification timer value (nT2 1206 for LMI) for this UNI/NNI logical port. If the 1207 logical port is not performing network-side 1208 procedures, then this object is not instantiated." 1210 REFERENCE "Q.933 Annex A [22], 1211 T1.617 Annex D [17], 1212 LMI [24]" 1213 DEFVAL { 15 } 1214 ::= { frMgtVCSigEntry 8 } 1216 frMgtVCSigNetnN4 OBJECT-TYPE 1217 SYNTAX INTEGER (5..5) 1218 UNITS "Events" 1219 MAX-ACCESS read-only 1220 STATUS current 1221 DESCRIPTION 1222 "The value of this object identifies the Network- 1223 side nN4 maximum status enquires received value 1224 for this UNI/NNI logical port. If the logical 1225 port is not performing network-side procedures or 1226 is not performing LMI procedures, then this object 1227 is not instantiated. 1229 This object applies only to LMI and always has a 1230 value of 5." 1231 REFERENCE "LMI [24]" 1232 ::= { frMgtVCSigEntry 9 } 1234 frMgtVCSigNetnT3 OBJECT-TYPE 1235 SYNTAX INTEGER (5 | 10 | 15 | 20 | 25 | 30) 1236 UNITS "Seconds" 1237 MAX-ACCESS read-only 1238 STATUS current 1239 DESCRIPTION 1240 "The value of this object identifies the Network- 1241 side nT3 timer (for nN4 status enquires received) 1242 value for this UNI/NNI logical port. If the 1243 logical port is not performing network-side 1244 procedures or is not performing LMI procedures, 1245 then this object is not instantiated. 1247 This object applies only to LMI." 1248 REFERENCE "LMI [24]" 1249 DEFVAL { 20 } 1250 ::= { frMgtVCSigEntry 10 } 1252 frMgtVCSigUserLinkRelErrors OBJECT-TYPE 1253 SYNTAX Counter32 1254 UNITS "Errors" 1255 MAX-ACCESS read-only 1256 STATUS current 1257 DESCRIPTION 1258 "The number of user-side local in-channel 1259 signaling link reliability errors (i.e., non- 1260 receipt of Status/Status Enquiry messages or 1261 invalid sequence numbers in a Link Integrity 1262 Verification Information Element) for this UNI/NNI 1263 logical port. If the logical port is not 1264 performing user-side procedures, then this object 1265 is not instantiated." 1266 ::= { frMgtVCSigEntry 11 } 1268 frMgtVCSigUserProtErrors OBJECT-TYPE 1269 SYNTAX Counter32 1270 UNITS "Errors" 1271 MAX-ACCESS read-only 1272 STATUS current 1273 DESCRIPTION 1274 "The number of user-side local in-channel 1275 signaling protocol errors (i.e., protocol 1276 discriminator, unnumbered information, message 1277 type, call reference, and mandatory information 1278 element errors) for this UNI/NNI logical port. If 1279 the logical port is not performing user-side 1280 procedures, then this object is not instantiated." 1281 ::= { frMgtVCSigEntry 12 } 1283 frMgtVCSigUserChanInactive OBJECT-TYPE 1284 SYNTAX Counter32 1285 UNITS "Events" 1286 MAX-ACCESS read-only 1287 STATUS current 1288 DESCRIPTION 1289 "The number of times the user-side channel was 1290 declared inactive (i.e., N392 errors in N393 1291 events) for this UNI/NNI logical port. If the 1292 logical port is not performing user-side 1293 procedures, then this object is not instantiated." 1294 ::= { frMgtVCSigEntry 13 } 1296 frMgtVCSigNetLinkRelErrors OBJECT-TYPE 1297 SYNTAX Counter32 1298 UNITS "Errors" 1299 MAX-ACCESS read-only 1300 STATUS current 1301 DESCRIPTION 1302 "The number of network-side local in-channel 1303 signaling link reliability errors (i.e., non- 1304 receipt of Status/Status Enquiry messages or 1305 invalid sequence numbers in a Link Integrity 1306 Verification Information Element) for this UNI/NNI 1307 logical port." 1308 ::= { frMgtVCSigEntry 14 } 1310 frMgtVCSigNetProtErrors OBJECT-TYPE 1311 SYNTAX Counter32 1312 UNITS "Errors" 1313 MAX-ACCESS read-only 1314 STATUS current 1315 DESCRIPTION 1316 "The number of network-side local in-channel 1317 signaling protocol errors (i.e., protocol 1318 discriminator, message type, call reference, and 1319 mandatory information element errors) for this 1320 UNI/NNI logical port." 1321 ::= { frMgtVCSigEntry 15 } 1323 frMgtVCSigNetChanInactive OBJECT-TYPE 1324 SYNTAX Counter32 1325 UNITS "Events" 1326 MAX-ACCESS read-only 1327 STATUS current 1328 DESCRIPTION 1329 "The number of times the network-side channel was 1330 declared inactive (i.e., N392 errors in N393 1331 events) for this UNI/NNI logical port." 1332 ::= { frMgtVCSigEntry 16 } 1334 frMgtVCSigProcedAdmin OBJECT-TYPE 1335 SYNTAX INTEGER { 1336 u2nnet(1), 1337 bidirect(2) 1338 } 1339 MAX-ACCESS read-write 1340 STATUS current 1341 DESCRIPTION 1342 "The value of this object identifies the desired 1343 Local In-Channel Signaling Procedure that is used 1344 for this UNI/NNI logical port. The UNI/NNI 1345 logical port can be performing only user-to- 1346 network network-side procedures or bidirectional 1347 procedures. Bidirectional procedures implies that 1348 both user-side and network-side procedures are 1349 used." 1350 ::= { frMgtVCSigEntry 17 } 1352 frMgtVCSigUserN391Admin OBJECT-TYPE 1353 SYNTAX INTEGER (1..255) 1354 UNITS "Polls" 1355 MAX-ACCESS read-write 1356 STATUS current 1357 DESCRIPTION 1358 "The value of this object identifies the desired 1359 User-side N391 full status polling cycle value for 1360 this UNI/NNI logical port. If the logical port is 1361 not performing user-side (bidirectional) 1362 procedures, then this object is not instantiated." 1363 REFERENCE "Q.933 Annex A [22], 1364 T1.617 Annex D [17]" 1365 ::= { frMgtVCSigEntry 18 } 1367 frMgtVCSigUserN392Admin OBJECT-TYPE 1368 SYNTAX INTEGER (1..10) 1369 UNITS "Events" 1370 MAX-ACCESS read-write 1371 STATUS current 1372 DESCRIPTION 1373 "The value of this object identifies the desired 1374 User-side N392 error threshold value for this 1375 UNI/NNI logical port. If the logical port is not 1376 performing user-side (bidirectional) procedures, 1377 then this object is not instantiated." 1378 REFERENCE "Q.933 Annex A [22], 1379 T1.617 Annex D [17]" 1380 ::= { frMgtVCSigEntry 19 } 1382 frMgtVCSigUserN393Admin OBJECT-TYPE 1383 SYNTAX INTEGER (1..10) 1384 UNITS "Events" 1385 MAX-ACCESS read-write 1386 STATUS current 1387 DESCRIPTION 1388 "The value of this object identifies the desired 1389 User-side N393 monitored events count value for 1390 this UNI/NNI logical port. If the logical port is 1391 not performing user-side (bidirectional) 1392 procedures, then this object is not instantiated." 1393 REFERENCE "Q.933 Annex A [22], 1394 T1.617 Annex D [17]" 1395 ::= { frMgtVCSigEntry 20 } 1397 frMgtVCSigUserT391Admin OBJECT-TYPE 1398 SYNTAX INTEGER (5..30) 1399 UNITS "Seconds" 1400 MAX-ACCESS read-write 1401 STATUS current 1402 DESCRIPTION 1403 "The value of this object identifies the desired 1404 User-side T391 link integrity verification polling 1405 timer value for this UNI/NNI logical port. If the 1406 logical port is not performing user-side 1407 procedures, then this object is not instantiated." 1408 REFERENCE "Q.933 Annex A [22], 1409 T1.617 Annex D [17]" 1410 ::= { frMgtVCSigEntry 21 } 1412 frMgtVCSigNetN392Admin OBJECT-TYPE 1413 SYNTAX INTEGER (1..10) 1414 UNITS "Events" 1415 MAX-ACCESS read-write 1416 STATUS current 1417 DESCRIPTION 1418 "The value of this object identifies the desired 1419 Network-side N392 error threshold value (nN2 for 1420 LMI) for this UNI/NNI logical port. If the 1421 logical port is not performing network-side 1422 procedures, then this object is not instantiated." 1423 REFERENCE "Q.933 Annex A [22], 1424 T1.617 Annex D [17], 1425 LMI [24]" 1426 ::= { frMgtVCSigEntry 22 } 1428 frMgtVCSigNetN393Admin OBJECT-TYPE 1429 SYNTAX INTEGER (1..10) 1430 UNITS "Events" 1431 MAX-ACCESS read-write 1432 STATUS current 1433 DESCRIPTION 1434 "The value of this object identifies the desired 1435 Network-side N393 monitored events count value 1436 (nN3 for LMI) for this UNI/NNI logical port. If 1437 the logical port is not performing network-side 1438 procedures, then this object is not instantiated." 1439 REFERENCE "Q.933 Annex A [22], 1440 T1.617 Annex D [17], 1441 LMI [24]" 1442 ::= { frMgtVCSigEntry 23 } 1444 frMgtVCSigNetT392Admin OBJECT-TYPE 1445 SYNTAX INTEGER (5..30) 1446 UNITS "Seconds" 1447 MAX-ACCESS read-write 1448 STATUS current 1449 DESCRIPTION 1450 "The value of this object identifies the desired 1451 Network-side T392 polling verification timer value 1452 (nT2 for LMI) for this UNI/NNI logical port. If 1453 the logical port is not performing network-side 1454 procedures, then this object is not instantiated." 1455 REFERENCE "Q.933 Annex A [22], 1456 T1.617 Annex D [17], 1457 LMI [24]" 1458 ::= { frMgtVCSigEntry 24 } 1460 frMgtVCSigNetnT3Admin OBJECT-TYPE 1461 SYNTAX INTEGER (5 | 10 | 15 | 20 | 25 | 30) 1462 UNITS "Seconds" 1463 MAX-ACCESS read-write 1464 STATUS current 1465 DESCRIPTION 1466 "The value of this object identifies the desired 1467 Network-side nT3 timer (for nN4 status enquires 1468 received) value for this UNI/NNI logical port. If 1469 the logical port is not performing network-side 1470 procedures or is not performing LMI procedures, 1471 then this object is not instantiated. This object 1472 applies only to LMI." 1473 REFERENCE "LMI [24]" 1474 ::= { frMgtVCSigEntry 25 } 1476 -- The PVC End-Point Group 1478 -- This table is used to identify the traffic parameters 1479 -- for a bi-directional PVC segment end-point, and it also 1480 -- provides statistics for a PVC segment 1481 -- end-point. 1483 -- A PVC segment end-point is identified by a UNI/NNI 1484 -- logical port index value and DLCI index value. 1486 -- If the frame relay service provider allows 1487 -- the frame relay CNM subscriber to create, modify 1488 -- or delete PVCs using SNMP, then this table is used 1489 -- to identify and reserve 1490 -- the requested traffic parameters of each 1491 -- PVC segment end-point. The Connection table 1492 -- is used to "connect" the end-points together. 1493 -- Not all implementations will support the 1494 -- capability of creating/modifying/deleting 1495 -- PVCs using SNMP as a feature of frame relay 1496 -- CNM service. 1498 -- Uni-directional PVCs are modeled with zero 1499 -- valued traffic parameters in one of the 1500 -- directions (In or Out direction) in this table. 1502 -- To create a PVC, the following procedures 1503 -- shall be followed: 1504 -- 1). Create the entries for the PVC segment endpoints in the 1505 -- frPVCEndptTable by specifying the traffic parameters 1506 -- for the bi-directional PVC segment endpoints. 1507 -- As shown in the figure, a point-to-point PVC has 1508 -- two endpoints, thus two entries in this table. 1509 -- Uni-directional PVCs are modeled 1510 -- with zero valued traffic parameters in one 1511 -- direction; all the `In' direction parameters 1512 -- for one frame relay PVC End-point or 1513 -- all the `Out' direction 1514 -- parameters for the other frame relay PVC 1515 -- End-point. 1517 -- In ____________________________________ Out 1518 -- >>>>>>| |>>>>>>>> 1519 -- ______| Frame Relay Network |__________ 1520 -- Out | | In 1521 -- <<<<<<| |<<<<<<<< 1522 -- |___________________________________| 1523 -- Frame Relay PVC Frame Relay 1524 -- End-point PVC End-point 1526 -- 2). Go to the Frame Relay Connection Group. 1527 -- 1529 -- The Frame Relay PVC End-point Table 1531 frPVCEndptTable OBJECT-TYPE 1532 SYNTAX SEQUENCE OF FrPVCEndptEntry 1533 MAX-ACCESS not-accessible 1534 STATUS current 1535 DESCRIPTION 1536 "The Frame Relay PVC End-Point table. This table 1537 is used to model a PVC end-point. This table 1538 contains the traffic parameters and statistics for 1539 a PVC end-point." 1540 ::= { frnetservObjects 3 } 1542 frPVCEndptEntry OBJECT-TYPE 1543 SYNTAX FrPVCEndptEntry 1544 MAX-ACCESS not-accessible 1545 STATUS current 1546 DESCRIPTION 1547 "An entry in the Frame Relay PVC Endpoint table." 1548 INDEX { ifIndex, frPVCEndptDLCIIndex } 1549 ::= { frPVCEndptTable 1 } 1551 FrPVCEndptEntry ::= 1552 SEQUENCE { 1553 frPVCEndptDLCIIndex Integer32, 1554 frPVCEndptInMaxFrameSize Integer32, 1555 frPVCEndptInBc Integer32, 1556 frPVCEndptInBe Integer32, 1557 frPVCEndptInCIR Integer32, 1558 frPVCEndptOutMaxFrameSize Integer32, 1559 frPVCEndptOutBc Integer32, 1560 frPVCEndptOutBe Integer32, 1561 frPVCEndptOutCIR Integer32, 1562 frPVCEndptConnectIdentifier Integer32, 1563 frPVCEndptRowStatus RowStatus, 1564 frPVCEndptRcvdSigStatus INTEGER, 1565 frPVCEndptInFrames Counter32, 1566 frPVCEndptOutFrames Counter32, 1567 frPVCEndptInDEFrames Counter32, 1568 frPVCEndptInExcessFrames Counter32, 1569 frPVCEndptOutExcessFrames Counter32, 1570 frPVCEndptInDiscards Counter32, 1571 frPVCEndptInOctets Counter32, 1572 frPVCEndptOutOctets Counter32, 1573 frPVCEndptInDiscardsDESet Counter32, 1574 frPVCEndptInFramesFECNSet Counter32, 1575 frPVCEndptOutFramesFECNSet Counter32, 1576 frPVCEndptInFramesBECNSet Counter32, 1577 frPVCEndptOutFramesBECNSet Counter32, 1578 frPVCEndptInCongDiscards Counter32, 1579 frPVCEndptInDECongDiscards Counter32, 1580 frPVCEndptOutCongDiscards Counter32, 1581 frPVCEndptOutDECongDiscards Counter32, 1582 frPVCEndptOutDEFrames Counter32, 1583 frPVCEndptAtmIwfConnIndex Integer32 1585 } 1587 frPVCEndptDLCIIndex OBJECT-TYPE 1588 SYNTAX Integer32 (16..4194303) 1589 MAX-ACCESS not-accessible 1590 STATUS current 1591 DESCRIPTION 1592 "The value of this object is equal to the DLCI 1593 value for this PVC end-point." 1594 ::= { frPVCEndptEntry 1 } 1596 frPVCEndptInMaxFrameSize OBJECT-TYPE 1597 SYNTAX Integer32 1598 UNITS "Octets" 1599 MAX-ACCESS read-create 1600 STATUS current 1601 DESCRIPTION 1602 "The value of this object is the size in octets of 1603 the largest frame relay information field for this 1604 PVC end-point in the ingress direction (into the 1605 frame relay network). The value of 1606 frPVCEndptInMaxFrameSize must be less than or 1607 equal to the corresponding ifMtu for this frame 1608 relay UNI/NNI logical port." 1609 ::= { frPVCEndptEntry 2 } 1611 frPVCEndptInBc OBJECT-TYPE 1612 SYNTAX Integer32 1613 UNITS "Bits" 1614 MAX-ACCESS read-create 1615 STATUS current 1616 DESCRIPTION 1617 "The value of this object is equal to the 1618 committed burst size (Bc) parameter (measured in 1619 bits) for this PVC end-point in the ingress 1620 direction (into the frame relay network)." 1621 ::= { frPVCEndptEntry 3 } 1623 frPVCEndptInBe OBJECT-TYPE 1624 SYNTAX Integer32 1625 UNITS "Bits" 1626 MAX-ACCESS read-create 1627 STATUS current 1628 DESCRIPTION 1629 "The value of this object is equal to the excess 1630 burst size (Be) parameter (measured in bits) for 1631 this PVC end-point in the ingress direction (into 1632 the frame relay network)." 1633 ::= { frPVCEndptEntry 4 } 1635 frPVCEndptInCIR OBJECT-TYPE 1636 SYNTAX Integer32 1637 UNITS "Bits per Second" 1638 MAX-ACCESS read-create 1639 STATUS current 1640 DESCRIPTION 1641 "The value of this object is equal to the 1642 committed information rate (CIR) parameter 1643 (measured in bits per second) for this PVC end- 1644 point in the ingress direction (into the frame 1645 relay network)." 1646 ::= { frPVCEndptEntry 5 } 1648 frPVCEndptOutMaxFrameSize OBJECT-TYPE 1649 SYNTAX Integer32 1650 UNITS "Octets" 1651 MAX-ACCESS read-create 1652 STATUS current 1653 DESCRIPTION 1654 "The value of this object is the size in octets of 1655 the largest frame relay information field for this 1656 PVC end-point in the egress direction (out of the 1657 frame relay network). The value of 1658 frPVCEndptOutMaxFrameSize must be less than or 1659 equal to the corresponding ifMtu for this frame 1660 relay UNI/NNI logical port." 1661 ::= { frPVCEndptEntry 6 } 1663 frPVCEndptOutBc OBJECT-TYPE 1664 SYNTAX Integer32 1665 UNITS "Bits" 1666 MAX-ACCESS read-create 1667 STATUS current 1668 DESCRIPTION 1669 "The value of this object is equal to the 1670 committed burst size (Bc) parameter (measured in 1671 bits) for this PVC end-point in the egress 1672 direction (out of the frame relay network)." 1673 ::= { frPVCEndptEntry 7 } 1675 frPVCEndptOutBe OBJECT-TYPE 1676 SYNTAX Integer32 1677 UNITS "Bits" 1678 MAX-ACCESS read-create 1679 STATUS current 1680 DESCRIPTION 1681 "The value of this object is equal to the excess 1682 burst size (Be) parameter (measured in bits) for 1683 this PVC end-point in the egress direction (out of 1684 the frame relay network)." 1685 ::= { frPVCEndptEntry 8 } 1687 frPVCEndptOutCIR OBJECT-TYPE 1688 SYNTAX Integer32 1689 UNITS "Bits per Second" 1690 MAX-ACCESS read-create 1691 STATUS current 1692 DESCRIPTION 1693 "The value of this object is equal to the 1694 committed information rate (CIR) parameter 1695 (measured in bits per second) for this PVC end- 1696 point in the egress direction (out of the frame 1697 relay network)." 1698 ::= { frPVCEndptEntry 9 } 1700 frPVCEndptConnectIdentifier OBJECT-TYPE 1701 SYNTAX Integer32 1702 MAX-ACCESS read-only 1703 STATUS current 1704 DESCRIPTION 1705 "This object is used to associate PVC end-points 1706 as being part of one PVC segment connection. This 1707 value of this object is equal to the value of 1708 frPVCConnectIndex, which is used as one of the 1709 indices into the frPVCConnectTable. 1711 A connection that has been cross-connected via the 1712 FR/ATM PVC Service IWF cross-connect table will 1713 return the value zero when this object is read. In 1714 case of these interworked connections, the 1715 frPVCEndptAtmIwfConnIndex object must be accessed 1716 to select the entry in the FR/ATM PVC Service IWF 1717 cross-connect table. 1719 The value of this object is provided by the agent, 1720 after the associated entries in the 1721 frPVCConnectTable or frAtmIwfConnectionTable have 1722 been created." 1723 ::= { frPVCEndptEntry 10 } 1725 frPVCEndptRowStatus OBJECT-TYPE 1726 SYNTAX RowStatus 1727 MAX-ACCESS read-create 1728 STATUS current 1729 DESCRIPTION 1730 "This object is used to create new rows in this 1731 table, modify existing rows, and to delete 1732 existing rows. To create a new PVC, the entries 1733 for the PVC segment end-points in the 1734 frPVCEndptTable must first be created. Next, the 1735 frPVCConnectTable is used to associate the frame 1736 relay PVC segment end-points. In order for the 1737 manager to have the necessary error diagnostics, 1738 the frPVCEndptRowStatus object must initially be 1739 set to `createAndWait'. While the 1740 frPVCEndptRowStatus object is in the 1741 `createAndWait' state, the manager can set each 1742 columnar object and get the necessary error 1743 diagnostics. The frPVCEndptRowStatus object may 1744 not be set to `active' unless the following 1745 columnar objects exist in this row: 1746 frPVCEndptInMaxFrameSize, frPVCEndptInBc, 1747 frPVCEndptInBe, frPVCEndptInCIR, 1748 frPVCEndptOutMaxFrameSize, frPVCEndptOutBc, 1749 frPVCEndptOutBe, and frPVCEndptOutCIR." 1750 ::= { frPVCEndptEntry 11 } 1752 frPVCEndptRcvdSigStatus OBJECT-TYPE 1753 SYNTAX INTEGER { 1754 deleted(1), 1755 active(2), 1756 inactive(3), 1757 none(4) 1758 } 1759 MAX-ACCESS read-only 1760 STATUS current 1761 DESCRIPTION 1762 "The value of this object identifies the PVC 1763 status received via the local in-channel signaling 1764 procedures for this PVC end-point. This object is 1765 only pertinent for interfaces that perform the 1766 bidirectional procedures. 1768 Each value has the following meaning: 1769 deleted(1): This PVC is not listed in the full 1770 status reports received from the 1771 user device. The object retains 1772 this value for as long as the PVC 1773 is not listed in the full status 1774 reports 1776 active(2): This PVC is reported as active, or 1777 operational, by the user device. 1779 inactive(3): This PVC is reported as inactive, 1780 or non-operational, by the user 1781 device. 1783 none(4): This interface is only using the 1784 network-side in-channel signaling 1785 procedures, so this object does 1786 not apply." 1788 ::= { frPVCEndptEntry 12 } 1790 frPVCEndptInFrames OBJECT-TYPE 1791 SYNTAX Counter32 1792 UNITS "Frames" 1793 MAX-ACCESS read-only 1794 STATUS current 1795 DESCRIPTION 1796 "The number of frames received by the network 1797 (ingress) for this PVC end-point. This includes 1798 any frames discarded by the network due to 1799 submitting more than Bc + Be data or due to any 1800 network congestion recovery procedures." 1801 ::= { frPVCEndptEntry 13 } 1803 frPVCEndptOutFrames OBJECT-TYPE 1804 SYNTAX Counter32 1805 UNITS "Frames" 1806 MAX-ACCESS read-only 1807 STATUS current 1808 DESCRIPTION 1809 "The number of frames sent by the network (egress) 1810 regardless of whether they are Bc or Be frames for 1811 this PVC end-point." 1812 ::= { frPVCEndptEntry 14 } 1814 frPVCEndptInDEFrames OBJECT-TYPE 1815 SYNTAX Counter32 1816 UNITS "Frames" 1817 MAX-ACCESS read-only 1818 STATUS current 1819 DESCRIPTION 1820 "The number of frames received by the network 1821 (ingress) with the DE bit set to (1) for this PVC 1822 end-point." 1823 ::= { frPVCEndptEntry 15 } 1825 frPVCEndptInExcessFrames OBJECT-TYPE 1826 SYNTAX Counter32 1827 UNITS "Frames" 1828 MAX-ACCESS read-only 1829 STATUS current 1830 DESCRIPTION 1831 "The number of frames received by the network 1832 (ingress) for this PVC end-point which were 1833 treated as excess traffic. Frames which are sent 1834 to the network with DE set to zero are treated as 1835 excess when more than Bc bits are submitted to the 1836 network during the Committed Information Rate 1837 Measurement Interval (Tc). Excess traffic may or 1838 may not be discarded at the ingress if more than 1839 Bc + Be bits are submitted to the network during 1840 Tc. Traffic discarded at the ingress is not 1841 recorded in frPVCEndptInExcessFrames. Frames 1842 which are sent to the network with DE set to one 1843 are also treated as excess traffic." 1844 ::= { frPVCEndptEntry 16 } 1846 frPVCEndptOutExcessFrames OBJECT-TYPE 1847 SYNTAX Counter32 1848 UNITS "Frames" 1849 MAX-ACCESS read-only 1850 STATUS current 1851 DESCRIPTION 1852 "The number of frames sent by the network (egress) 1853 for this PVC end-point which were treated as 1854 excess traffic. (The DE bit may be set to one.)" 1855 ::= { frPVCEndptEntry 17 } 1857 frPVCEndptInDiscards OBJECT-TYPE 1858 SYNTAX Counter32 1859 UNITS "Frames" 1860 MAX-ACCESS read-only 1861 STATUS current 1862 DESCRIPTION 1863 "The number of frames received by the the network 1864 (ingress) that were discarded due to traffic 1865 enforcement for this PVC end-point. Congestion 1866 discards are not counted in this object." 1867 ::= { frPVCEndptEntry 18 } 1869 frPVCEndptInOctets OBJECT-TYPE 1870 SYNTAX Counter32 1871 UNITS "Octets" 1872 MAX-ACCESS read-only 1873 STATUS current 1874 DESCRIPTION 1875 "The number of octets received by the network 1876 (ingress) for this PVC end-point. This counter 1877 should only count octets from the beginning of the 1878 frame relay header field to the end of user data. 1879 If the network supporting frame relay can not 1880 count octets, then this count should be an 1881 approximation." 1882 ::= { frPVCEndptEntry 19 } 1884 frPVCEndptOutOctets OBJECT-TYPE 1885 SYNTAX Counter32 1886 UNITS "Octets" 1887 MAX-ACCESS read-only 1888 STATUS current 1889 DESCRIPTION 1890 "The number of octets sent by the network (egress) 1891 for this PVC end-point. This counter should only 1892 count octets from the beginning of the frame relay 1893 header field to the end of user data. If the 1894 network supporting frame relay can not count 1895 octets, then this count should be an 1896 approximation." 1897 ::= { frPVCEndptEntry 20 } 1899 frPVCEndptInDiscardsDESet OBJECT-TYPE 1900 SYNTAX Counter32 1901 UNITS "Frames" 1902 MAX-ACCESS read-only 1903 STATUS current 1904 DESCRIPTION 1905 "The number of frames received by the network 1906 (ingress) that were discarded with the DE bit set 1907 due to traffic enforcement for this PVC end-point. 1908 Congestion discards are not counted in this 1909 object." 1910 ::= { frPVCEndptEntry 21 } 1912 frPVCEndptInFramesFECNSet OBJECT-TYPE 1913 SYNTAX Counter32 1914 UNITS "Frames" 1915 MAX-ACCESS read-only 1916 STATUS current 1917 DESCRIPTION 1918 "The number of frames received by the network 1919 (ingress) that have the FECN bit set for this PVC 1920 end-point. If the logical port is not performing 1921 network-side procedures, then this object is not 1922 instantiated." 1924 ::= { frPVCEndptEntry 22 } 1926 frPVCEndptOutFramesFECNSet OBJECT-TYPE 1927 SYNTAX Counter32 1928 UNITS "Frames" 1929 MAX-ACCESS read-only 1930 STATUS current 1931 DESCRIPTION 1932 "The number of frames sent by the network (egress) 1933 that have the FECN bit set for this PVC end- 1934 point." 1935 ::= { frPVCEndptEntry 23 } 1937 frPVCEndptInFramesBECNSet OBJECT-TYPE 1938 SYNTAX Counter32 1939 UNITS "Frames" 1940 MAX-ACCESS read-only 1941 STATUS current 1942 DESCRIPTION 1943 "The number of frames received by the network 1944 (ingress) that have the BECN bit set for this PVC 1945 end-point. If the logical port is not performing 1946 network-side procedures, then this object is not 1947 instantiated." 1948 ::= { frPVCEndptEntry 24 } 1950 frPVCEndptOutFramesBECNSet OBJECT-TYPE 1951 SYNTAX Counter32 1952 UNITS "Frames" 1953 MAX-ACCESS read-only 1954 STATUS current 1955 DESCRIPTION 1956 "The number of frames sent by the network (egress) 1957 that have the BECN bit set for this PVC end- 1958 point." 1959 ::= { frPVCEndptEntry 25 } 1961 frPVCEndptInCongDiscards OBJECT-TYPE 1962 SYNTAX Counter32 1963 UNITS "Frames" 1964 MAX-ACCESS read-only 1965 STATUS current 1966 DESCRIPTION 1967 "The number of frames received by the network 1968 (ingress) that were discarded due to input buffer 1969 congestion, rather than traffic enforcement, for 1970 this PVC end-point." 1971 ::= { frPVCEndptEntry 26 } 1973 frPVCEndptInDECongDiscards OBJECT-TYPE 1974 SYNTAX Counter32 1975 UNITS "Frames" 1976 MAX-ACCESS read-only 1977 STATUS current 1978 DESCRIPTION 1979 "The number of frames counted by 1980 frPVCEndptInCongDiscards with the DE bit set to 1981 (1)." 1982 ::= { frPVCEndptEntry 27 } 1984 frPVCEndptOutCongDiscards OBJECT-TYPE 1985 SYNTAX Counter32 1986 UNITS "Frames" 1987 MAX-ACCESS read-only 1988 STATUS current 1989 DESCRIPTION 1990 "The number of frames sent by the network (egress) 1991 that were discarded due to output buffer 1992 congestion for this PVC end-point." 1993 ::= { frPVCEndptEntry 28 } 1995 frPVCEndptOutDECongDiscards OBJECT-TYPE 1996 SYNTAX Counter32 1997 UNITS "Frames" 1998 MAX-ACCESS read-only 1999 STATUS current 2000 DESCRIPTION 2001 "The number of frames counted by 2002 frPVCEndptOutCongDiscards with the DE bit set to 2003 (1)." 2004 ::= { frPVCEndptEntry 29 } 2006 frPVCEndptOutDEFrames OBJECT-TYPE 2007 SYNTAX Counter32 2008 UNITS "Frames" 2009 MAX-ACCESS read-only 2010 STATUS current 2011 DESCRIPTION 2012 "The number of frames sent by the network (egress) 2013 with the DE bit set to (1) for this PVC end- 2014 point." 2015 ::= { frPVCEndptEntry 30 } 2017 frPVCEndptAtmIwfConnIndex OBJECT-TYPE 2018 SYNTAX Integer32 (1..2147483647) 2019 MAX-ACCESS read-only 2020 STATUS current 2021 DESCRIPTION 2022 "This object contains the index value of the 2023 FR/ATM cross-connect table entry used to link the 2024 frame relay PVC with an ATM PVC. 2026 Each row of the frPVCEndptTable that is not 2027 cross-connected with an ATM PVC MUST return the 2028 value zero when this object is read. 2030 The value of this object is initialized by the 2031 agent after the associated entries in the 2032 frAtmIwfConnectionTable have been created. 2034 The value of this object is reset to zero 2035 following destruction of the associated entry in 2036 the frAtmIwfConnectionTable" 2037 ::= { frPVCEndptEntry 31 } 2039 -- The Frame Relay PVC Connection Group 2041 -- The Frame Relay PVC Connection Group 2042 -- is used to model the bi-directional 2043 -- PVC segment flows; 2044 -- point-to-point PVCs, point-to-multipoint 2045 -- PVCs, and multipoint-to-multipoint 2046 -- PVCs. 2048 -- This table has read-create access and 2049 -- is used to associate PVC end-points 2050 -- together as belonging to one connection. 2051 -- The frPVCConnectIndex is used to associate 2052 -- all the bi-directional flows. 2053 -- Not all implementations will support the 2054 -- capability of creating/modifying/deleting 2055 -- PVCs using SNMP as a feature of frame relay 2056 -- CNM service. 2058 -- Once the entries in the frPVCEndptTable 2059 -- are created, the following step are used 2060 -- to associate the PVC end-points as belonging 2061 -- to one PVC connection: 2062 -- 1). Obtain a unique frPVCConnectIndex 2063 -- using the frPVCConnectIndexValue object. 2064 -- 2). Connect the PVC segment endpoints together 2065 -- with the applicable frPVCConnectIndex value 2066 -- obtained via 2067 -- frPVCConnectIndexValue. 2068 -- The entries in this table are created by using 2069 -- the frPVCConnectRowStatus object. 2070 -- 3). The agent will provide the value of the 2071 -- corresponding instances of 2072 -- frPVCEndptConnectIdentifier with the 2073 -- the frPVCConnectIndex value. 2074 -- 4). Set frPVCConnectAdminStatus to `active' in all 2075 -- rows for this PVC segment to 2076 -- turn the PVC on. 2078 -- For example, the Frame Relay PVC Connection Group 2079 -- models a bi-directional, point-to-point PVC segment 2080 -- as one entry in this table. 2082 -- Frame Relay Network Frame Relay Network 2083 -- Low Port ____________________________________ High Port 2084 -- | | 2085 -- ______| >> from low to high PVC flow >> |____________ 2086 -- | << from high to low PVC flow << | 2087 -- |___________________________________| 2088 -- 2090 -- The terms low and high are chosen to represent numerical 2091 -- ordering of a PVC segment's endpoints for representation 2092 -- in this table. That is, the endpoint with the lower value 2093 -- of ifIndex is termed 'low', while the opposite endpoint 2094 -- of the segment is termed 'high'. 2095 -- This terminology is to provide directional information; 2096 -- for example the frPVCConnectL2hOperStatus and 2097 -- frPVCConnectH2lOperStatus as illustrated above. 2099 -- If the Frame Relay Connection table is used to model 2100 -- a unidirectional PVC, then one direction (either from low 2101 -- to high or from high to low) has its Operational Status 2102 -- equal to down. 2104 -- A PVC segment is a portion of a PVC that traverses one 2105 -- Frame Relay Network, and a PVC segment is identified 2106 -- by its two end-points (UNI/NNI logical port index value 2107 -- and DLCI index value) through one Frame Relay Network. 2109 frPVCConnectIndexValue OBJECT-TYPE 2110 SYNTAX INTEGER (0..2147483647) 2111 MAX-ACCESS read-only 2112 STATUS current 2113 DESCRIPTION 2114 "This object contains an appropriate value to be 2115 used for frPVCConnectIndex when creating entries 2116 in the frPVCConnectTable. The value 0 indicates 2117 that no unassigned entries are available. To 2118 obtain the frPVCConnectIndex value for a new 2119 entry, the manager issues a management protocol 2120 retrieval operation to obtain the current value of 2121 this object. After each retrieval, the agent 2122 should modify the value to the next unassigned 2123 index." 2124 ::= { frnetservObjects 4 } 2126 -- The Frame Relay PVC Connection Table 2128 frPVCConnectTable OBJECT-TYPE 2129 SYNTAX SEQUENCE OF FrPVCConnectEntry 2130 MAX-ACCESS not-accessible 2131 STATUS current 2132 DESCRIPTION 2133 "The Frame Relay PVC Connect table. A bi- 2134 directional PVC segment is modeled as one entry in 2135 this table." 2136 ::= { frnetservObjects 5 } 2138 frPVCConnectEntry OBJECT-TYPE 2139 SYNTAX FrPVCConnectEntry 2140 MAX-ACCESS not-accessible 2141 STATUS current 2142 DESCRIPTION 2143 "An entry in the Frame Relay PVC Connect table. 2144 This entry is used to model a PVC segment in two 2145 directions." 2146 INDEX { frPVCConnectIndex, 2147 frPVCConnectLowIfIndex, 2148 frPVCConnectLowDLCIIndex, 2149 frPVCConnectHighIfIndex, 2150 frPVCConnectHighDLCIIndex } 2151 ::= { frPVCConnectTable 1 } 2153 FrPVCConnectEntry ::= 2154 SEQUENCE { 2155 frPVCConnectIndex Integer32, 2156 frPVCConnectLowIfIndex InterfaceIndex, 2157 frPVCConnectLowDLCIIndex Integer32, 2158 frPVCConnectHighIfIndex InterfaceIndex, 2159 frPVCConnectHighDLCIIndex Integer32, 2160 frPVCConnectAdminStatus INTEGER, 2161 frPVCConnectL2hOperStatus INTEGER, 2162 frPVCConnectH2lOperStatus INTEGER, 2163 frPVCConnectL2hLastChange TimeStamp, 2164 frPVCConnectH2lLastChange TimeStamp, 2165 frPVCConnectRowStatus RowStatus, 2166 frPVCConnectUserName SnmpAdminString, 2167 frPVCConnectProviderName SnmpAdminString 2168 } 2170 frPVCConnectIndex OBJECT-TYPE 2171 SYNTAX Integer32 (0..2147483647) 2172 MAX-ACCESS not-accessible 2173 STATUS current 2174 DESCRIPTION 2175 "The value of this object is equal to the 2176 frPVCConnectIndexValue obtained to uniquely 2177 identify this PVC segment connection." 2178 ::= { frPVCConnectEntry 1 } 2180 frPVCConnectLowIfIndex OBJECT-TYPE 2181 SYNTAX InterfaceIndex 2182 MAX-ACCESS not-accessible 2183 STATUS current 2184 DESCRIPTION 2185 "The value of this object is equal to IF-MIB 2186 ifIndex value of the UNI/NNI logical port for this 2187 PVC segment. The term low implies that this PVC 2188 segment end-point has the numerically lower 2189 ifIndex value than the connected/associated PVC 2190 segment end-point." 2191 ::= { frPVCConnectEntry 2 } 2193 frPVCConnectLowDLCIIndex OBJECT-TYPE 2194 SYNTAX Integer32 (16..4194303) 2195 MAX-ACCESS not-accessible 2196 STATUS current 2197 DESCRIPTION 2198 "The value of this object is equal to the DLCI 2199 value for this end-point of the PVC segment." 2200 ::= { frPVCConnectEntry 3 } 2202 frPVCConnectHighIfIndex OBJECT-TYPE 2203 SYNTAX InterfaceIndex 2204 MAX-ACCESS not-accessible 2205 STATUS current 2206 DESCRIPTION 2207 "The value of this object is equal to IF-MIB 2208 ifIndex value for the UNI/NNI logical port for 2209 this PVC segment. The term high implies that this 2210 PVC segment end-point has the numerically higher 2211 ifIndex value than the connected/associated PVC 2212 segment end-point." 2213 ::= { frPVCConnectEntry 4 } 2215 frPVCConnectHighDLCIIndex OBJECT-TYPE 2216 SYNTAX Integer32 (16..4194303) 2217 MAX-ACCESS not-accessible 2218 STATUS current 2219 DESCRIPTION 2220 "The value of this object is equal to the egress 2221 DLCI value for this end-point of the PVC segment." 2222 ::= { frPVCConnectEntry 5 } 2224 frPVCConnectAdminStatus OBJECT-TYPE 2225 SYNTAX INTEGER { 2226 active(1), 2227 inactive(2), 2228 testing(3) 2229 } 2230 MAX-ACCESS read-create 2231 STATUS current 2232 DESCRIPTION 2233 "The value of this object identifies the desired 2234 administrative status of this bi-directional PVC 2235 segment. The active state means the PVC segment 2236 is currently operational; the inactive state means 2237 the PVC segment is currently not operational; the 2238 testing state means the PVC segment is currently 2239 undergoing a test. This state is set by an 2240 administrative entity. This value affects the PVC 2241 status indicated across the ingress NNI/UNI of 2242 both end-points of the bi-directional PVC segment. 2243 When a PVC segment connection is created using 2244 this table, this object is initially set to 2245 `inactive'. After the frPVCConnectRowStatus 2246 object is set to `active' (and the 2247 corresponding/associated entries in the 2248 frPVCEndptTable have their frPVCEndptRowStatus 2249 object set to `active'), the 2250 frPVCConnectAdminStatus object may be set to 2251 `active' to turn on the PVC segment connection." 2252 ::= { frPVCConnectEntry 6 } 2254 frPVCConnectL2hOperStatus OBJECT-TYPE 2255 SYNTAX INTEGER { 2256 active(1), 2257 inactive(2), 2258 testing(3), 2259 unknown(4) 2260 } 2261 MAX-ACCESS read-only 2262 STATUS current 2263 DESCRIPTION 2264 "The value of this object identifies the current 2265 operational status of the PVC segment connection 2266 in one direction; (i.e., in the low to high 2267 direction). This value affects the PVC status 2268 indicated across the ingress NNI/UNI (low side) of 2269 the PVC segment. 2271 The values mean: 2272 active - PVC is currently operational 2273 inactive - PVC is currently not operational. This 2274 may be because of an underlying LMI or 2275 DS1 failure. 2276 testing - PVC is currently undergoing a test. 2277 This may be because of an underlying 2278 frLport or DS1 undergoing a test. 2279 unknown - the status of the PVC currently can not 2280 be determined." 2281 ::= { frPVCConnectEntry 7 } 2283 frPVCConnectH2lOperStatus OBJECT-TYPE 2284 SYNTAX INTEGER { 2285 active(1), 2286 inactive(2), 2287 testing(3), 2288 unknown(4) 2289 } 2290 MAX-ACCESS read-only 2291 STATUS current 2292 DESCRIPTION 2293 "The value of this object identifies the current 2294 operational status of the PVC segment connection 2295 in one direction; (i.e., in the high to low 2296 direction).. This value affects the PVC status 2297 indicated across the ingress NNI/UNI (high side) 2298 of the PVC segment. 2300 The values mean: 2301 active - PVC is currently operational 2302 inactive - PVC is currently not operational. This 2303 may be because of an underlying LMI or 2304 DS1 failure. 2305 testing - PVC is currently undergoing a test. 2306 This may be because of an underlying 2307 frLport or DS1 undergoing a test. 2308 unknown - the status of the PVC currently can not 2309 be determined." 2310 ::= { frPVCConnectEntry 8 } 2312 frPVCConnectL2hLastChange OBJECT-TYPE 2313 SYNTAX TimeStamp 2314 MAX-ACCESS read-only 2315 STATUS current 2316 DESCRIPTION 2317 "The value of MIB II's sysUpTime object at the 2318 time this PVC segment entered its current 2319 operational state in the low to high direction. 2320 If the current state was entered prior to the last 2321 re-initialization of the FRS agent, then this 2322 object contains a zero value." 2323 ::= { frPVCConnectEntry 9 } 2325 frPVCConnectH2lLastChange OBJECT-TYPE 2326 SYNTAX TimeStamp 2327 MAX-ACCESS read-only 2328 STATUS current 2329 DESCRIPTION 2330 "The value of MIB II's sysUpTime object at the 2331 time this PVC segment entered its current 2332 operational state in the high to low direction. 2333 If the current state was entered prior to the last 2334 re-initialization of the FRS agent, then this 2335 object contains a zero value." 2336 ::= { frPVCConnectEntry 10 } 2338 frPVCConnectRowStatus OBJECT-TYPE 2339 SYNTAX RowStatus 2340 MAX-ACCESS read-create 2341 STATUS current 2342 DESCRIPTION 2343 "The status of this entry in the 2344 frPVCConnectTable. This variable is used to 2345 create new connections for the PVC end-points and 2346 to change existing connections of the PVC end- 2347 points. This object must be initially set to 2348 `createAndWait'. In this state, the agent checks 2349 the parameters in the associated entries in the 2350 frPVCEndptTable to verify that the PVC end-points 2351 can be connected (i.e., the In parameters for one 2352 PVC end-point are equal to the Out parameters for 2353 the other PVC end-point). This object can not be 2354 set to `active' unless the following columnar 2355 object exists in this row: 2356 frPVCConnectAdminStatus. The agent also supplies 2357 the associated value of frPVCConnectIndex for the 2358 frPVCEndptConnectIdentifier instances. To turn on 2359 a PVC segment connection, the 2360 frPVCConnectAdminStatus is set to `active'." 2361 ::= { frPVCConnectEntry 11 } 2363 frPVCConnectUserName OBJECT-TYPE 2364 SYNTAX SnmpAdminString (0..255) 2365 MAX-ACCESS read-create 2366 STATUS current 2367 DESCRIPTION 2368 "This is a service user assigned textual 2369 representation of a PVC." 2370 ::= { frPVCConnectEntry 12 } 2372 frPVCConnectProviderName OBJECT-TYPE 2373 SYNTAX SnmpAdminString (0..255) 2374 MAX-ACCESS read-only 2375 STATUS current 2376 DESCRIPTION 2377 "This is a system supplied textual representation 2378 of PVC. It is assigned by the service provider." 2379 ::= { frPVCConnectEntry 13 } 2381 -- The Frame Relay Accounting Groups 2383 -- The groups are the following: 2384 -- Accounting on a PVC basis 2385 -- Accounting on an Interface/Logical Port basis 2387 -- The Accounting on a Frame Relay PVC basis Group 2389 -- The accounting information is collected for a PVC 2390 -- segment end-point. 2392 frAccountPVCTable OBJECT-TYPE 2393 SYNTAX SEQUENCE OF FrAccountPVCEntry 2394 MAX-ACCESS not-accessible 2395 STATUS current 2396 DESCRIPTION 2397 "The Frame Relay Accounting PVC table. This table 2398 is used to perform accounting on a PVC segment 2399 end-point basis." 2400 ::= { frnetservObjects 6 } 2402 frAccountPVCEntry OBJECT-TYPE 2403 SYNTAX FrAccountPVCEntry 2404 MAX-ACCESS not-accessible 2405 STATUS current 2406 DESCRIPTION 2407 "An entry in the Frame Relay Accounting PVC 2408 table." 2409 INDEX { ifIndex, 2410 frAccountPVCDLCIIndex } 2411 ::= { frAccountPVCTable 1 } 2413 FrAccountPVCEntry ::= 2414 SEQUENCE { 2415 frAccountPVCDLCIIndex Integer32, 2416 frAccountPVCSegmentSize Integer32, 2417 frAccountPVCInSegments Counter32, 2418 frAccountPVCOutSegments Counter32 2419 } 2421 frAccountPVCDLCIIndex OBJECT-TYPE 2422 SYNTAX Integer32 (16..4194303) 2423 MAX-ACCESS not-accessible 2424 STATUS current 2425 DESCRIPTION 2426 "The value of this object is equal to the DLCI 2427 value for this PVC segment end-point." 2428 ::= { frAccountPVCEntry 1 } 2430 frAccountPVCSegmentSize OBJECT-TYPE 2431 SYNTAX Integer32 2432 UNITS "Octets" 2433 MAX-ACCESS read-only 2434 STATUS current 2435 DESCRIPTION 2436 "The value of this object is equal to the Segment 2437 Size for this PVC segment end-point." 2438 ::= { frAccountPVCEntry 2 } 2440 frAccountPVCInSegments OBJECT-TYPE 2441 SYNTAX Counter32 2442 UNITS "Segments" 2443 MAX-ACCESS read-only 2444 STATUS current 2445 DESCRIPTION 2446 "The value of this object is equal to the number 2447 of segments received by this PVC segment end- 2448 point." 2449 ::= { frAccountPVCEntry 3 } 2451 frAccountPVCOutSegments OBJECT-TYPE 2452 SYNTAX Counter32 2453 UNITS "Segments" 2454 MAX-ACCESS read-only 2455 STATUS current 2456 DESCRIPTION 2457 "The value of this object is equal to the number 2458 of segments sent by this PVC segment end-point." 2459 ::= { frAccountPVCEntry 4 } 2461 -- The Accounting on a Frame Relay Logical Port basis Group 2463 frAccountLportTable OBJECT-TYPE 2464 SYNTAX SEQUENCE OF FrAccountLportEntry 2465 MAX-ACCESS not-accessible 2466 STATUS current 2467 DESCRIPTION 2468 "The Frame Relay Accounting Logical Port table. 2469 This table is used to perform accounting on a 2470 UNI/NNI Logical Port basis." 2471 ::= { frnetservObjects 7 } 2473 frAccountLportEntry OBJECT-TYPE 2474 SYNTAX FrAccountLportEntry 2475 MAX-ACCESS not-accessible 2476 STATUS current 2477 DESCRIPTION 2478 "An entry in the Frame Relay Accounting Logical 2479 Port table." 2480 INDEX { ifIndex } 2481 ::= { frAccountLportTable 1 } 2483 FrAccountLportEntry ::= 2484 SEQUENCE { 2485 frAccountLportSegmentSize 2486 Integer32, 2487 frAccountLportInSegments 2488 Counter32, 2489 frAccountLportOutSegments 2490 Counter32 2491 } 2493 frAccountLportSegmentSize OBJECT-TYPE 2494 SYNTAX Integer32 2495 UNITS "Octets" 2496 MAX-ACCESS read-only 2497 STATUS current 2498 DESCRIPTION 2499 "The value of this object is equal to the Segment 2500 Size for this UNI/NNI logical port." 2501 ::= { frAccountLportEntry 1 } 2503 frAccountLportInSegments OBJECT-TYPE 2504 SYNTAX Counter32 2505 UNITS "Segments" 2506 MAX-ACCESS read-only 2507 STATUS current 2508 DESCRIPTION 2509 "The value of this object is equal to the number 2510 of segments received by this UNI/NNI logical 2511 port." 2512 ::= { frAccountLportEntry 2 } 2514 frAccountLportOutSegments OBJECT-TYPE 2515 SYNTAX Counter32 2516 UNITS "Segments" 2517 MAX-ACCESS read-only 2518 STATUS current 2519 DESCRIPTION 2520 "The value of this object is equal to the number 2521 of segments sent by this UNI/NNI logical port." 2522 ::= { frAccountLportEntry 3 } 2524 -- Frame Relay Network Service TRAPS 2526 frPVCConnectStatusChange NOTIFICATION-TYPE 2527 OBJECTS { frPVCConnectIndex, 2528 frPVCConnectLowIfIndex, 2529 frPVCConnectLowDLCIIndex, 2530 frPVCConnectHighIfIndex, 2531 frPVCConnectHighDLCIIndex, 2532 frPVCConnectL2hOperStatus, 2533 frPVCConnectH2lOperStatus, 2534 frPVCEndptRcvdSigStatus } 2535 STATUS obsolete 2536 DESCRIPTION 2537 "Refer to the description of the 2538 frPVCConnectStatusNotif object that has replaced 2539 this object. The object is obsolete due to the 2540 incorrect inclusion of index values and to take 2541 advantage of the trap prefix for automatic 2542 conversion from SMIv2 to SMIv1 by making the one 2543 but last sub-ID a zero (i.e. the so-called trap 2544 prefix)." 2545 ::= { frnetservTraps 1 } 2547 frPVCConnectStatusNotif NOTIFICATION-TYPE 2548 OBJECTS { frPVCConnectL2hOperStatus, 2549 frPVCConnectH2lOperStatus, 2550 frPVCEndptRcvdSigStatus } 2551 STATUS current 2552 DESCRIPTION 2553 "This trap indicates that the indicated PVC has 2554 changed state. This trap is not sent if an FR-UNI 2555 changes state; a linkDown or linkUp trap should be 2556 sent instead. The first instance of 2557 frPVCEndptRcvdSigStatus is for the endpoint with 2558 LowIfIndex, LowDLCIIndex. The second instance of 2559 frPVCEndptRcvdSigStatus is for the endpoint with 2560 HighIfIndex, HighDLCIIndex" 2561 ::= { frnetservTrapsPrefix 1 } 2563 -- Conformance Information 2565 frnetservConformance OBJECT IDENTIFIER ::= { frnetservMIB 3 } 2567 frnetservGroups OBJECT IDENTIFIER 2568 ::= { frnetservConformance 1 } 2569 frnetservCompliances OBJECT IDENTIFIER 2570 ::= { frnetservConformance 2 } 2572 frnetSwitchGroups OBJECT IDENTIFIER 2573 ::= { frnetservConformance 3 } 2574 frnetSwitchCompliances OBJECT IDENTIFIER 2575 ::= { frnetservConformance 4 } 2577 -- 2578 -- Compliance Statements 2579 -- 2581 frnetservCompliance2 MODULE-COMPLIANCE 2582 STATUS current 2583 DESCRIPTION 2584 "The compliance statement for SNMP entities which 2585 have Frame Relay Network Service Interfaces." 2586 MODULE -- this module 2587 MANDATORY-GROUPS { frnetservLportGroup, 2588 frnetservMgtVCSigGroup, 2589 frnetservPVCEndptGroup, 2590 frnetservPVCConnectGroup, 2591 frnetservPVCNotifGroup2 } 2593 GROUP frnetservAccountPVCGroup 2594 DESCRIPTION 2595 "This group is optional for frame relay 2596 interfaces. It is mandatory if and only if 2597 accounting is performed on a PVC basis this frame 2598 relay interface." 2599 GROUP frnetservAccountLportGroup 2600 DESCRIPTION 2601 "This group is optional for frame relay 2602 interfaces. It is mandatory if and only if 2603 accounting is performed on a logical port basis 2604 this frame relay interface." 2606 OBJECT frPVCEndptInMaxFrameSize 2607 MIN-ACCESS read-only 2608 DESCRIPTION 2609 "Write access is not required." 2611 OBJECT frPVCEndptInBc 2612 MIN-ACCESS read-only 2613 DESCRIPTION 2614 "Write access is not required." 2616 OBJECT frPVCEndptInBe 2617 MIN-ACCESS read-only 2618 DESCRIPTION 2619 "Write access is not required." 2621 OBJECT frPVCEndptInCIR 2622 MIN-ACCESS read-only 2623 DESCRIPTION 2624 "Write access is not required." 2626 OBJECT frPVCEndptOutMaxFrameSize 2627 MIN-ACCESS read-only 2628 DESCRIPTION 2629 "Write access is not required." 2631 OBJECT frPVCEndptOutBc 2632 MIN-ACCESS read-only 2633 DESCRIPTION 2634 "Write access is not required." 2636 OBJECT frPVCEndptOutBe 2637 MIN-ACCESS read-only 2638 DESCRIPTION 2639 "Write access is not required." 2641 OBJECT frPVCEndptOutCIR 2642 MIN-ACCESS read-only 2643 DESCRIPTION 2644 "Write access is not required." 2646 OBJECT frPVCEndptRowStatus 2647 -- subset of RowStatus 2648 SYNTAX INTEGER { active(1) } 2649 MIN-ACCESS read-only 2650 DESCRIPTION 2651 "Write access is not required, and only one of the 2652 six enumerated values for the RowStatus textual 2653 convention need be supported, specifically: 2654 active(1)." 2656 OBJECT frPVCConnectAdminStatus 2657 MIN-ACCESS read-only 2658 DESCRIPTION 2659 "Write access is not required." 2661 OBJECT frPVCConnectRowStatus 2662 -- subset of RowStatus 2663 SYNTAX INTEGER { active(1) } 2664 MIN-ACCESS read-only 2665 DESCRIPTION 2666 "Write access is not required, and only one of the 2667 six enumerated values for the RowStatus textual 2668 convention need be supported, specifically: 2669 active(1)." 2670 ::= { frnetservCompliances 2 } 2672 -- 2673 -- Frame Relay Switch (R/W) Compliance Module 2674 -- 2675 -- The switch provides read/write 2676 -- access to all MIB objects. 2677 -- 2679 frnetSwitchCompliance MODULE-COMPLIANCE 2680 STATUS current 2681 DESCRIPTION 2682 "The compliance statement for SNMP entities which 2683 have Frame Relay Network Switch objects." 2684 MODULE -- this module 2685 MANDATORY-GROUPS { frnetSwitchLportGroup, 2686 frnetSwitchMgtVCSigGroup, 2687 frnetservPVCEndptGroup, 2688 frnetservPVCConnectGroup, 2689 frnetservPVCNotifGroup2 } 2691 GROUP frnetservAccountPVCGroup 2692 DESCRIPTION 2693 "This group is optional for frame relay 2694 interfaces. It is mandatory if and only if 2695 accounting is performed on a PVC basis this frame 2696 relay interface." 2697 GROUP frnetservAccountLportGroup 2698 DESCRIPTION 2699 "This group is optional for frame relay 2700 interfaces. It is mandatory if and only if 2701 accounting is performed on a logical port basis 2702 this frame relay interface." 2704 ::= { frnetSwitchCompliances 1 } 2706 -- 2707 -- Deprecated Compliance Modules 2708 -- 2710 frnetservCompliance MODULE-COMPLIANCE 2711 STATUS deprecated 2712 DESCRIPTION 2713 "The compliance statement for SNMP entities which 2714 have frame relay network service interfaces." 2715 MODULE -- this module 2716 MANDATORY-GROUPS { frnetservLportGroup, 2717 frnetservMgtVCSigGroup, 2718 frnetservPVCEndptGroup, 2719 frnetservPVCConnectGroup } 2721 GROUP frnetservAccountPVCGroup 2722 DESCRIPTION 2723 "This group is optional for frame relay 2724 interfaces. It is mandatory if and only if 2725 accounting is performed on a PVC basis this frame 2726 relay interface." 2727 GROUP frnetservAccountLportGroup 2728 DESCRIPTION 2729 "This group is optional for frame relay 2730 interfaces. It is mandatory if and only if 2731 accounting is performed on a logical port basis 2732 this frame relay interface." 2734 OBJECT frPVCEndptInMaxFrameSize 2735 MIN-ACCESS read-only 2736 DESCRIPTION 2737 "Write access is not required." 2739 OBJECT frPVCEndptInBc 2740 MIN-ACCESS read-only 2741 DESCRIPTION 2742 "Write access is not required." 2744 OBJECT frPVCEndptInBe 2745 MIN-ACCESS read-only 2746 DESCRIPTION 2747 "Write access is not required." 2749 OBJECT frPVCEndptInCIR 2750 MIN-ACCESS read-only 2751 DESCRIPTION 2752 "Write access is not required." 2754 OBJECT frPVCEndptOutMaxFrameSize 2755 MIN-ACCESS read-only 2756 DESCRIPTION 2757 "Write access is not required." 2759 OBJECT frPVCEndptOutBc 2760 MIN-ACCESS read-only 2761 DESCRIPTION 2762 "Write access is not required." 2764 OBJECT frPVCEndptOutBe 2765 MIN-ACCESS read-only 2766 DESCRIPTION 2767 "Write access is not required." 2769 OBJECT frPVCEndptOutCIR 2770 MIN-ACCESS read-only 2771 DESCRIPTION 2772 "Write access is not required." 2774 OBJECT frPVCEndptRowStatus 2775 -- subset of RowStatus 2776 SYNTAX INTEGER { active(1) } 2777 MIN-ACCESS read-only 2778 DESCRIPTION 2779 "Write access is not required, and only one of the 2780 six enumerated values for the RowStatus textual 2781 convention need be supported, specifically: 2782 active(1)." 2784 OBJECT frPVCConnectAdminStatus 2785 MIN-ACCESS read-only 2786 DESCRIPTION 2787 "Write access is not required." 2789 OBJECT frPVCConnectRowStatus -- subset of RowStatus 2790 SYNTAX INTEGER { active(1) } 2791 MIN-ACCESS read-only 2792 DESCRIPTION 2793 "Write access is not required, and only one of the 2794 six enumerated values for the RowStatus textual 2795 convention need be supported, specifically: 2796 active(1)." 2797 ::= { frnetservCompliances 1 } 2799 -- 2800 -- Units of Conformance 2801 -- 2803 -- 2804 -- Frame Relay Network Service Groups 2805 -- 2807 frnetservLportGroup OBJECT-GROUP 2808 OBJECTS { frLportNumPlan, 2809 frLportContact, 2810 frLportLocation, 2811 frLportType, 2812 frLportAddrDLCILen, 2813 frLportVCSigProtocol, 2814 frLportVCSigPointer, 2815 frLportDLCIIndexValue, 2816 frLportFragControl, 2817 frLportFragSize } 2818 STATUS current 2819 DESCRIPTION 2820 "A collection of objects providing information 2821 applicable to a Frame Relay Logical Port." 2822 ::= { frnetservGroups 1 } 2824 frnetservMgtVCSigGroup OBJECT-GROUP 2825 OBJECTS { frMgtVCSigProced, 2826 frMgtVCSigUserN391, 2827 frMgtVCSigUserN392, 2828 frMgtVCSigUserN393, 2829 frMgtVCSigUserT391, 2830 frMgtVCSigNetN392, 2831 frMgtVCSigNetN393, 2832 frMgtVCSigNetT392, 2833 frMgtVCSigNetnN4, 2834 frMgtVCSigNetnT3, 2835 frMgtVCSigUserLinkRelErrors, 2836 frMgtVCSigUserProtErrors, 2837 frMgtVCSigUserChanInactive, 2838 frMgtVCSigNetLinkRelErrors, 2839 frMgtVCSigNetProtErrors, 2840 frMgtVCSigNetChanInactive } 2841 STATUS current 2842 DESCRIPTION 2843 "A collection of objects providing information 2844 applicable to the Local In-Channel Signaling 2845 Procedures used for a UNI/NNI logical port." 2846 ::= { frnetservGroups 2 } 2848 frnetservPVCEndptGroup OBJECT-GROUP 2849 OBJECTS { frPVCConnectIndexValue, 2850 frPVCEndptInMaxFrameSize, 2851 frPVCEndptInBc, 2852 frPVCEndptInBe, 2853 frPVCEndptInCIR, 2854 frPVCEndptOutMaxFrameSize, 2855 frPVCEndptOutBc, 2856 frPVCEndptOutBe, 2857 frPVCEndptOutCIR, 2858 frPVCEndptConnectIdentifier, 2859 frPVCEndptRowStatus, 2860 frPVCEndptRcvdSigStatus, 2861 frPVCEndptInFrames, 2862 frPVCEndptOutFrames, 2863 frPVCEndptInDEFrames, 2864 frPVCEndptInExcessFrames, 2865 frPVCEndptOutExcessFrames, 2866 frPVCEndptInDiscards, 2867 frPVCEndptInOctets, 2868 frPVCEndptOutOctets, 2869 frPVCEndptInDiscardsDESet, 2870 frPVCEndptInFramesFECNSet, 2871 frPVCEndptOutFramesFECNSet, 2872 frPVCEndptInFramesBECNSet, 2873 frPVCEndptOutFramesBECNSet, 2874 frPVCEndptInCongDiscards, 2875 frPVCEndptInDECongDiscards, 2876 frPVCEndptOutCongDiscards, 2877 frPVCEndptOutDECongDiscards, 2878 frPVCEndptOutDEFrames, 2879 frPVCEndptAtmIwfConnIndex } 2880 STATUS current 2881 DESCRIPTION 2882 "A collection of objects providing information 2883 application to a frame relay PVC end-point." 2884 ::= { frnetservGroups 3 } 2886 frnetservPVCConnectGroup OBJECT-GROUP 2887 OBJECTS { frPVCConnectAdminStatus, 2888 frPVCConnectL2hOperStatus, 2889 frPVCConnectH2lOperStatus, 2890 frPVCConnectL2hLastChange, 2891 frPVCConnectH2lLastChange, 2892 frPVCConnectRowStatus, 2893 frPVCConnectUserName, 2894 frPVCConnectProviderName } 2895 STATUS current 2896 DESCRIPTION 2897 "A collection of objects providing information 2898 applicable to a frame relay PVC connection." 2899 ::= { frnetservGroups 4 } 2901 frnetservAccountPVCGroup OBJECT-GROUP 2902 OBJECTS { frAccountPVCSegmentSize, 2903 frAccountPVCInSegments, 2904 frAccountPVCOutSegments } 2905 STATUS current 2906 DESCRIPTION 2907 "A collection of objects providing accounting 2908 information application to a frame relay PVC end- 2909 point." 2910 ::= { frnetservGroups 5 } 2912 frnetservAccountLportGroup OBJECT-GROUP 2913 OBJECTS { frAccountLportSegmentSize, 2914 frAccountLportInSegments, 2915 frAccountLportOutSegments } 2916 STATUS current 2917 DESCRIPTION 2918 "A collection of objects providing accounting 2919 information application frame relay logical port." 2920 ::= { frnetservGroups 6 } 2922 frnetservPVCNotifGroup2 NOTIFICATION-GROUP 2923 NOTIFICATIONS { frPVCConnectStatusNotif } 2924 STATUS current 2925 DESCRIPTION 2926 "A collection of notifications that apply to frame 2927 relay PVC Connections " 2928 ::= { frnetservGroups 8 } 2930 -- 2931 -- Frame Relay Switch (Read/Write) Groups 2932 -- 2933 frnetSwitchLportGroup OBJECT-GROUP 2934 OBJECTS { frLportNumPlan, 2935 frLportContact, 2936 frLportLocation, 2937 frLportType, 2938 frLportAddrDLCILen, 2939 frLportVCSigProtocol, 2940 frLportVCSigPointer, 2941 frLportDLCIIndexValue, 2942 frLportTypeAdmin, 2943 frLportVCSigProtocolAdmin, 2944 frLportVCSigPointerAdmin, 2945 frLportFragControl, 2946 frLportFragSize } 2947 STATUS current 2948 DESCRIPTION 2949 "A collection of objects providing information 2950 applicable to a Frame Relay Logical Port." 2951 ::= { frnetSwitchGroups 1 } 2953 frnetSwitchMgtVCSigGroup OBJECT-GROUP 2954 OBJECTS { frMgtVCSigProced, 2955 frMgtVCSigUserN391, 2956 frMgtVCSigUserN392, 2957 frMgtVCSigUserN393, 2958 frMgtVCSigUserT391, 2959 frMgtVCSigNetN392, 2960 frMgtVCSigNetN393, 2961 frMgtVCSigNetT392, 2962 frMgtVCSigNetnN4, 2963 frMgtVCSigNetnT3, 2964 frMgtVCSigUserLinkRelErrors, 2965 frMgtVCSigUserProtErrors, 2966 frMgtVCSigUserChanInactive, 2967 frMgtVCSigNetLinkRelErrors, 2968 frMgtVCSigNetProtErrors, 2969 frMgtVCSigNetChanInactive, 2970 frMgtVCSigProcedAdmin, 2971 frMgtVCSigUserN391Admin, 2972 frMgtVCSigUserN392Admin, 2973 frMgtVCSigUserN393Admin, 2974 frMgtVCSigUserT391Admin, 2975 frMgtVCSigNetN392Admin, 2976 frMgtVCSigNetN393Admin, 2977 frMgtVCSigNetT392Admin, 2978 frMgtVCSigNetnT3Admin } 2979 STATUS current 2980 DESCRIPTION 2981 "A collection of objects providing information 2982 applicable to the Local In-Channel Signaling 2983 Procedures used for a UNI/NNI logical port." 2984 ::= { frnetSwitchGroups 2 } 2986 -- 2987 -- Deprecated Groups 2988 -- 2990 frnetservPVCNotifGroup NOTIFICATION-GROUP 2991 NOTIFICATIONS { frPVCConnectStatusChange } 2992 STATUS obsolete 2993 DESCRIPTION 2994 "Deprecated notification group." 2995 ::= { frnetservGroups 7 } 2997 END 2999 4. Acknowledgments 3001 This document was produced by the Frame Relay Service MIB Working 3002 Group. 3004 The working group thanks Bert Wijnen and Bob Stewart for their 3005 assistance in reviewing the MIB. 3007 5. References 3009 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 3010 Describing SNMP Management Frameworks", RFC 2571, April 1999 3012 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 3013 Management Information for TCP/IP-based Internets", STD 16, RFC 3014 1155, May 1990 3016 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 3017 1212, March 1991 3019 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 3020 RFC 1215, March 1991 3022 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 3023 and S. Waldbusser, "Structure of Management Information Version 2 3024 (SMIv2)", STD 58, RFC 2578, April 1999 3026 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 3027 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 3028 2579, April 1999 3030 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 3031 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 3032 2580, April 1999 3034 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 3035 Management Protocol", STD 15, RFC 1157, May 1990. 3037 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3038 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 3040 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 3041 Mappings for Version 2 of the Simple Network Management Protocol 3042 (SNMPv2)", RFC 1906, January 1996. 3044 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 3045 Processing and Dispatching for the Simple Network Management 3046 Protocol (SNMP)", RFC 2572, April 1999 3048 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 3049 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 3050 2574, April 1999 3052 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 3053 Operations for Version 2 of the Simple Network Management Protocol 3054 (SNMPv2)", RFC 1905, January 1996. 3056 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 3057 2573, April 1999 3059 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 3060 Control Model (VACM) for the Simple Network Management Protocol 3061 (SNMP)", RFC 2575, April 1999 3063 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 3064 Version 3 of the Internet-standard Network Management Framework", 3065 RFC 2570, April 1999 3067 [17] ANSI T1.617-1991, American National Standard for Telecommunications 3068 - Integrated Services Digital Network (ISDN) - Digital Subscriber 3069 Signaling System No. 1 (DSS1) - Signaling Specification for Frame 3070 Relay Bearer Service. 3072 [18] Brown, C., and F. Baker, "Management Information Base for Frame 3073 Relay DTEs", RFC 2115, Cadia Networks, Cisco Systems, September 3074 1997. 3076 [19] Brown, C., and A. Malis, "Multi-Protocol Interconnect over Frame 3077 Relay", STD 55, RFC 2427, Consultant, Ascend Communications, Inc., 3078 September 1998. 3080 [20] Fowler, D, "Definitions of Managed Objects for the DS0 and DS0 3081 Bundle Interface Types", RFC 2494, Newbridge Networks, January 3082 1999. 3084 [21] Frame Relay Forum, "Frame Relay Fragmentation Implementation 3085 Agreement", FRF.12, December 1997. 3087 [22] ITU-T Recommendation Q.933,Integrated Services Digital Network 3088 (ISDN) Digital Subscriber Signalling System No. 1 (DSS 1) - 3089 Signalling Specifications for Frame Mode Switched and Permanent 3090 Virtual Connection Control and Status Monitoring, December 1995 3092 [23] ITU-T Recommendation X.36, Interface Between Data Terminal 3093 Equipment (DTE) and Data Circuit-Terminating Equipment (DCE) For 3094 Public Data Networks Providing Frame Relay Data Transmission 3095 Service By Dedicated Circuit, April 1995 3097 [24] Digital Equipment Corporation, et. al., "Frame Relay Specification 3098 with Extensions Based on Proposed T1S1 Standards", Revision 1.0, 3099 September 18, 1990 3101 [25] ITU-T Recommendation Q.922, Integrated Services Digital Network 3102 (ISDN) Data Link Layer Specification For Frame Mode Bearer 3103 Services, February 1992 3105 [26] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 3106 2233, Cisco Systems, FTP Software, November 1997. 3108 [27] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Management 3109 Information Base for Version 2 of the Simple Network Management 3110 Protocol (SNMPv2)", RFC 1907, SNMP Reserach, Cisco Systems, Dover 3111 Beach Consulting, and International Network Services, January 1996. 3113 [28] Rehbehn, K., Nicklass, O., and G. Mouradian, "Definitions of 3114 Managed Objects for Monitoring and Controlling the Frame Relay/ATM 3115 PVC Service Interworking Function", RFC xxxFRATMMIBxxx, Visual 3116 Networks, RAD Data Communications, AT&T Labs, October 1999. 3118 6. Security Considerations 3120 There are a number of management objects defined in this MIB that 3121 have a MAX-ACCESS clause of read-write and/or read-create. Such 3122 objects may be considered sensitive or vulnerable in some network 3123 environments. The support for SET operations in a non-secure 3124 environment without proper protection can have a negative effect on 3125 network operations. 3127 No managed objects in this MIB contain sensitive information. 3129 SNMPv1 by itself is not a secure environment. Even if the network 3130 itself is secure (for example by using IPSec), even then, there is no 3131 control as to who on the secure network is allowed to access and 3132 GET/SET (read/change/create/delete) the objects in this MIB. 3134 It is recommended that the implementers consider the security 3135 features as provided by the SNMPv3 framework. Specifically, the use 3136 of the User-based Security Model RFC 2574 [12] and the View-based 3137 Access Control Model RFC 2575 [15] is recommended. 3139 It is then a customer/user responsibility to ensure that the SNMP 3140 entity giving access to an instance of this MIB, is properly 3141 configured to give access to the objects only to those principals 3142 (users) that have legitimate rights to indeed GET or SET 3143 (change/create/delete) them. 3145 7. Authors' Addresses 3147 Kenneth Rehbehn 3148 Visual Networks 3149 2092 Gaither Road 3150 Rockville, MD, USA 20850 3152 Phone: (301) 296-2325 3154 EMail: krehbehn@visualnetworks.com 3156 David Fowler 3157 Newbridge Networks 3158 600 March Road 3159 Kanata, Ontario, Canada K2K 2E6 3161 Phone: (613) 599-3600, ext 6559 3163 EMail: davef@newbridge.com 3165 APPENDIX A Update Information 3167 The changes from RFC 1604 are the following: 3169 (1) This MIB works for switches too. Read-writable 3170 versions of a number of frLport and frVCSig objects 3171 were created to allow this. 3173 (2) frPVCEndptInDiscards was clarified. Congestion 3174 discards are not counted. 3176 (3) Descriptions were added for the values of 3177 frPVCEndptRcvdSigStatus. 3179 (4) An additional instance of frPVCEndptRcvdSigStatus was 3180 added to the Connect Status Change Trap. There is now 3181 one for each endpoint. 3183 (5) ifLinkUpDownTrapEnable is now recommended to be on. 3185 (6) frVCSigProced was slightly unclear. The values are 3186 clarified along with associated counter definitions. 3188 (7) The behaviour of the PVC statuses and the Endpt Sig 3189 Statuses are clarified when an underlying layer fails. 3191 (8) frPVCConnectIndexValue was added. 3193 (9) An ifStackTable example was added. 3195 (10) Additional counters for PVCs were added. 3197 (11) Names for PVCs were added. 3199 (12) Addition of counters to track frames offered (in) 3200 and delivered (out) for increased visibility into 3201 policing-driven discards, congestion-driven discards, 3202 DE bit setting, and congestion bit setting. 3203 frPVCEndptInDiscardsDESet 3204 frPVCEndptInFramesFECNSet 3205 frPVCEndptOutFramesFECNSet 3206 frPVCEndptInFramesBECNSet 3207 frPVCEndptOutFramesBECNSet 3208 frPVCEndptInCongDiscards 3209 frPVCEndptInDECongDiscards 3210 frPVCEndptOutCongDiscards 3211 frPVCEndptOutDECongDiscards 3212 frPVCEndptOutDEFrames 3214 (13) Addition of Frame Relay Fragmentation objects 3215 frLportFragControl and frLportFragSize. 3217 (14) Reference to RFC 1490 changed to STD 55, RFC 2427. 3219 (15) Created a NOTIFICATION object identified using the 3220 trap prefix convention to support automatic generation 3221 of SMIv1 MIB. The new object is named 3222 frPVCConnectStatusNotif. The old object 3223 frPVCConnectStatusChange has been obsoleted. The 3224 compliance statements have been obsoleted/created 3225 to match. 3227 (16) Add frPVCEndptAtmIwfConnIndex object to select a 3228 FR/ATM Service IWF cross-connect entry instead of 3229 the FR-specific cross-connect table. 3231 (17) Utilized SnmpAdminString syntax in place of 3232 DisplayString syntax. 3234 Intellectual Property Rights 3236 The IETF takes no position regarding the validity or scope of any 3237 intellectual property or other rights that might be claimed to 3238 pertain to the implementation or use of the technology described in 3239 this document or the extent to which any license under such rights 3240 might or might not be available; neither does it represent that it 3241 has made any effort to identify any such rights. Information on the 3242 IETF's procedures with respect to rights in standards-track and 3243 standards-related documentation can be found in BCP-11. Copies of 3244 claims of rights made available for publication and any assurances of 3245 licenses to be made available, or the result of an attempt made to 3246 obtain a general license or permission for the use of such 3247 proprietary rights by implementors or users of this specification can 3248 be obtained from the IETF Secretariat. 3250 The IETF invites any interested party to bring to its attention any 3251 copyrights, patents or patent applications, or other proprietary 3252 rights which may cover technology that may be required to practice 3253 this standard. Please address the information to the IETF Executive 3254 Director. 3256 Full Copyright Statement 3258 Copyright (C) The Internet Society (1999). All Rights Reserved. 3260 This document and translations of it may be copied and furnished to 3261 others, and derivative works that comment on or otherwise explain it 3262 or assist in its implementation may be prepared, copied, published 3263 and distributed, in whole or in part, without restriction of any 3264 kind, provided that the above copyright notice and this paragraph are 3265 included on all such copies and derivative works. However, this 3266 document itself may not be modified in any way, such as by removing 3267 the copyright notice or references to the Internet Society or other 3268 Internet organizations, except as needed for the purpose of 3269 developing Internet standards in which case the procedures for 3270 copyrights defined in the Internet Standards process must be 3271 followed, or as required to translate it into languages other than 3272 English. 3274 The limited permissions granted above are perpetual and will not be 3275 revoked by the Internet Society or its successors or assigns. 3277 This document and the information contained herein is provided on an 3278 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 3279 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 3280 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 3281 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 3282 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.