idnits 2.17.1 draft-ietf-frnetmib-spvc-00.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** 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? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** 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 90 instances of too long lines in the document, the longest one being 12 characters in excess of 72. ** The abstract seems to contain references ([1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 61 has weird spacing: '...Objects in t...' == Line 64 has weird spacing: '... object type ...' == Line 65 has weird spacing: '... with an o...' == Line 66 has weird spacing: '...pecific insta...' == Line 67 has weird spacing: '...tor, is used ...' == (1 more instance...) -- 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 (July 1, 1997) is 9796 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) ** Obsolete normative reference: RFC 1604 (ref. '1') (Obsoleted by RFC 2954) ** Obsolete normative reference: RFC 1902 (ref. '2') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1905 (ref. '4') (Obsoleted by RFC 3416) -- Possible downref: Non-RFC (?) normative reference: ref. '5' Summary: 15 errors (**), 0 flaws (~~), 7 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET DRAFT B. Coutts 2 Cascade Communications Corp. 3 February 1, 1997 4 Expires July 1, 1997 6 Frame Relay Service Extensions MIB for Switched PVCs 8 1. Status of this Memo 10 This document is an Internet-Draft. Internet-Drafts are working 11 documents of the Internet Engineering Task Force (IETF), its areas, 12 and its working groups. Note that other groups may also distribute 13 working documents as Internet-Drafts. 15 Internet-Drafts are draft documents valid for a maximum of six 16 months. Internet-Drafts may be updated, replaced, or obsoleted by 17 other documents at any time. It is not appropriate to use Internet- 18 Drafts as reference material or to cite them other than as a 19 ``working draft'' or ``work in progress.'' 21 To learn the current status of any Internet-Draft, please check the 22 ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow 23 Directories on ds.internic.net (US East Coast), nic.nordu.net 24 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific 25 Rim). 27 This draft document will be submitted to the RFC editor as an 28 extension to the SNMP MIB. Please send comments to the author, 29 copying iplpdn@cnri.reston.va.us. It expires July 1997. 31 2. Abstract 33 This memo defines a portion of the Management Information Base (MIB) 34 for use with network management protocols in TCP/IP- based internets. 35 In particular, it defines objects for managing Frame Relay Switched 36 Permanent Virtual Circuits (SPVCs) as extensions to RFC 1604 [1]. 37 This memo does not specify a standard for the Internet community. 39 3. The SNMPv2 Network Management Framework 41 The major components of the SNMPv2 Network Management framework are 42 described in the documents listed below. 44 o RFC 1902 [2] defines the Structure of Management 45 Information (SMI), the mechanisms used for describing and 46 naming objects for the purpose of management. 48 o STD 17, RFC 1213 [3] defines MIB-II, the core set of 49 managed objects (MO) for the Internet suite of protocols. 51 o RFC 1905 [4] defines the protocol used for network access 52 to managed objects. 54 o RFC 1604 [1] defines the protocol used for managing 55 Frame Relay services. 57 The framework is adaptable/extensible by defining new MIBs to suit 58 the requirements of specific applications/protocols/situations. 60 Managed objects are accessed via a virtual information store, the 61 MIB. Objects in the MIB are defined using the subset of 62 Abstract Syntax Notation One (ASN.1) defined in the SMI. In 63 particular, each object type is named by an OBJECT IDENTIFIER, which 64 is an administratively assigned name. The object type together 65 with an object instance serves to uniquely identify a 66 specific instantiation of the object. For human convenience, often 67 a textual string, termed the descriptor, is used to refer to the 68 object type. 70 4. Overview 72 Section 3 "Overview" of RFC 1604 [1] and its subsections provide 73 overview and background of how to use the Frame Relay Service MIB. 74 This material is pertinent to the RFC 1604 extensions provided in 75 this draft, and should be followed. 77 4.1. Frame Relay Service MIB Extensions for SPVCs 79 This MIB addresses the instances needed to manage the Frame Relay 80 Forum's Implementation Agreement for SPVCs (FRF.10). These instances 81 are based on the ATM Forum Soft PVC MIB [5] objects to provide a 82 consistent Switched PVC management model for both ATM and Frame Relay 83 SPVCs. 85 A Switched PVC (SPVC) is a virtual circuit that appears to the user 86 to be a PVC but spans multiple networks as an SVC. The originating 87 network "ingress" endpoint is configured as one PVC endpoint and is 88 configured with information (including a destination address) 89 required to signal and establish an SVC across the NNI interfaces 90 between networks. The destination network "egress" endpoint is 91 configured as the second PVC endpoint and is configured with the 92 destination address. The originating endpoint has the responsibility 93 for establishing, releasing, and re-establishing the SPVC. 95 Note that the MIB extensions defined herein allow either or both ends 96 of the SPVC to be configured as originating endpoints. Note, also, 97 that these SPVC MIB extensions define configuration of only the 98 originating endpoint SPVC parameters. 100 In order to configure the originating endpoint SPVC parameters, an 101 entry in the PVC End-Point table and an entry in the Switched PVC 102 table must be defined. The PVC End-Point table entry (see the PVC 103 End-Point Group in RFC 1604 [1]) identifies the bi-directional 104 traffic parameters for the originating endpoint of the SPVC. The 105 Switched PVC table entry (defined in these SPVC MIB Extensions) 106 identifies the destination address information (e.g., E.164 address) 107 of the SPVC. Together these two entries provide the information 108 required (by the network originating the SPVC) to signal an SVC 109 across the NNI. 111 A row in the PVC End-Point table must be created prior to creating a 112 row in the Switched PVC table. And the corresponding row in the PVC 113 End-Point table must be active prior to activating the Switched PVC 114 table row. When the Switched PVC table row is made active, an 115 attempt is made to set up a switched connection to an interface at 116 the destination switch. 118 Presently, the Frame Relay Service MIB does not include an SVC 119 cross-connect table. Once such a table is defined, an SVC cross- 120 connect table entry should be created at the time the SPVC table row 121 is made active; and deleted at the time the SPVC table row is made 122 inactive. 124 5. Definitions 126 FRNETSERV-MIB DEFINITIONS ::= BEGIN 128 IMPORTS 129 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE 130 Counter32, Integer32, 131 TimeTicks FROM SNMPv2-SMI 132 TEXTUAL-CONVENTION, DisplayString, PhysAddress, 133 TimeStamp, RowStatus FROM SNMPv2-TC 134 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 135 ifIndex, transmission FROM RFC-1213 137 frnetservMIB MODULE-IDENTITY 138 . 139 . 140 . 142 IfIndex ::= TEXTUAL-CONVENTION 143 . 144 . 145 . 147 frnetservObjects OBJECT IDENTIFIER ::= { frnetservMIB 1 } 148 frnetservTraps OBJECT IDENTIFIER ::= { frnetservMIB 2 } 150 . 151 . 152 . 154 -- 155 -- Switched PVC Extensions 156 -- 157 -- 158 -- A Switched PVC (SPVC) is a virtual circuit that appears to the user to be a 159 -- PVC but spans multiple networks as an SVC. 160 -- The PVC End-Point table entry (see the PVC End-Point Group) identifies the 161 -- bi-directional traffic parameters for the originating endpoint of the SPVC; 162 -- and the Switched PVC table entry (of these Switched PVC Extensions) 163 -- identifies the destination address information (e.g., E.164 address) of the 164 -- SPVC. Together these two entries provide the information required (by the 165 -- network originating the SPVC) to signal an SVC across the NNI. 166 -- 167 -- To create and activate an SPVC, the following procedures shall be followed: 168 -- 1). Create an entry in the frPVCEndptTable. 169 -- 2). Create an entry in the frSwitchedPVCTable. 170 -- 3). Activate the frPVCEndptTable entry. 171 -- 4). When the corresponding row in the frSwitchedPVCTable (i.e., the rows with 172 -- matching UNI/NNI logical port and matching DLCI index values) is set to 173 -- 'active', an attempt is made to set up a switched connection to an 174 -- interface at the destination switch. 176 -- The Frame Relay Switched PVC Table 178 frSwitchedPVCTable OBJECT-TYPE 179 SYNTAX SEQUENCE OF FrSwitchedPVCEntry 180 MAX-ACCESS not-accessible 181 STATUS current 182 DESCRIPTION 183 "The (conceptual) table used to manage Switched Permanent 184 Virtual Connections (SPVCs). The SPVC table is applicable 185 only to switches." 186 ::= { frnetservObjects 8 } 188 frSwitchedPVCEntry OBJECT-TYPE 189 SYNTAX FrSwitchedPVCEntry 190 MAX-ACCESS not-accessible 191 STATUS current 192 DESCRIPTION 193 "Each entry in this table represents a Switched Permanent 194 Virtual Connection (SPVC) Originating at a switch interface. 195 An SPVC is a VC that is : 196 - provisioned at the originating (source) interface of the 197 connection. 198 - established by signalling procedures across a network to a 199 destination interface. 201 A row in the frPVCEndptTable must be created, defining a PVC 202 endpoint on the source interface, prior to creating an 203 frSwitchedPVCEntry row. The row in the frPVCEndptTable must 204 be active prior to activating the frSwitchedPVCEntry row. The 205 contents of this table reflect only the characteristics unique 206 to a Switched PVC. The traffic and signalling parameters are 207 defined in the PVC endpoint row for the source interface. 208 Since the Low Layer Compatibility, Called Party Subaddress, 209 and Calling Party Subaddress information elements are used to 210 carry end-to-end information, they are not used in the 211 configuration of Switched PVC. Note that the User-User 212 Information information element may be used to contain the 213 frSwitchedPVCTargetDlci if 'specificSPVCCorrelator' is 214 selected in the frSwitchedPVCTargetSelectType. For Switched 215 PVC configuration, all parameters in the bearer capability 216 parameters shall be set to their default values. 218 When a row is made active, an attempt is made to set up a 219 switched connection to an interface at the destination switch. 221 No objects (other that frSwitchedPVCRowStatus) can be set 222 while the row is active. 224 The combination of frSwitchedPVCIfIndex and 225 frSwitchedPVCDlciIndex specified in index clause of this entry 226 serves to identify the PVC endpoint on the source interface. 228 In accordance with ITU-T X.76 Annex A, if the 229 frSwitchedPVCTargetSelectType is provisioned for either 230 'specificDLCI' or 'specificSPVCCorrelator', SPVC 231 establishment can be attempted from either one or both 232 endpoints. Otherwise, SPVC establishment must be 233 attempted from a single endpoint chosen through bilateral 234 agreement - that is, the SPVC need only be provisioned at a 235 single endpoint" 236 INDEX { frSwitchedPVCIfIndex, frSwitchedPVCDlciIndex } 237 ::= { frSwitchedPVCTable 1 } 239 FrSwitchedPVCEntry ::= 240 SEQUENCE { 241 frSwitchedPVCIfIndex 242 ifIndex, 243 frSwitchedPVCDlciIndex 244 Integer32, 245 frSwitchedPVCTargetAddress 246 OCTET STRING, 247 frSwitchedPVCTargetAddressType 248 INTEGER, 249 frSwitchedPVCTargetSelectType 250 INTEGER, 251 frSwitchedPVCTargetDlci 252 Integer32, 253 frSwitchedPVCLastReleaseCause 254 INTEGER, 255 frSwitchedPVCLastReleaseDiagnostic 256 OCTET STRING, 257 frSwitchedPVCOperStatus 258 INTEGER, 259 frSwitchedPVCRestart 260 INTEGER, 261 frSwitchedPVCRetryInterval 262 INTEGER, 263 frSwitchedPVCRetryTimer 264 INTEGER, 265 frSwitchedPVCRetryFailures 266 INTEGER, 267 frSwitchedPVCRetryLimit 268 INTEGER, 270 frSwitchedPVCRowStatus 271 RowStatus 272 } 274 frSwitchedPVCIfIndex OBJECT-TYPE 275 SYNTAX IfIndex 276 MAX-ACCESS not-accessible 277 STATUS current 278 DESCRIPTION 279 "The value of this object is equal to MIB II's ifIndex value of 280 the UNI/NNI logical port for thisPVC endpoint." 281 ::= { frSwitchedPVCEntry 1 } 283 frSwitchedPVCDlciIndex OBJECT-TYPE 284 SYNTAX Integer32 285 MAX-ACCESS not-accessible 286 STATUS current 287 DESCRIPTION 288 "The value of this object is equal to the DLCI value for this 289 PVC endpoint." 290 ::= { frSwitchedPVCEntry 2 } 292 frSwitchedPVCTargetAddress OBJECT-TYPE 293 SYNTAX OCTET STRING 294 MAX-ACCESS read-create 295 STATUS current 296 DESCRIPTION 297 "The target Address of this SPVC." 298 ::= { frSwitchedPVCEntry 3 } 300 frSwitchedPVCTargetAddressType OBJECT-TYPE 301 SYNTAX INTEGER { 302 e164 (2) -- E.164 addressing format 303 } 304 MAX-ACCESS read-create 305 STATUS current 306 DESCRIPTION 307 "The target Address Type of this SPVC." 308 ::= { frSwitchedPVCEntry 4 } 310 frSwitchedPVCTargetSelectType OBJECT-TYPE 311 SYNTAX INTEGER { 312 anyDLCI(1), 313 specificDLCI(2), 314 specificSPVCCorrelator(3) 315 } 316 MAX-ACCESS read-create 317 STATUS current 318 DESCRIPTION 319 "Indicates whether the target DLCI value or SPVC correlator is 320 to be used at the destination. If the value 'anyDLCI' is 321 specified, the destination switch will choose the DLCI value. 322 In such a case, once the SPVC frSwitchedPvcOperStatus value is 323 'connected', the DLCI value chosen will be available for 324 reading in frSwitchedPVCTargetDlci. If the value 325 'specificDLCI' or 'specificSPVCCorrelator' is specified, then 326 a value must be supplied for object frSwitchedPVCTargetDlci 327 prior to activation of the row. This value is then to be used 328 at the destination." 329 DEFVAL { specificDLCI } 330 ::= { frSwitchedPVCEntry 5 } 332 frSwitchedPVCTargetDlci OBJECT-TYPE 333 SYNTAX INTEGER (0..8388607) 334 MAX-ACCESS read-create 335 STATUS current 336 DESCRIPTION 337 "The DLCI value of the SPVC used at the target interface when 338 the frSwitchedPVCTargetSelectType is set to 'specificDLCI'. 339 Or the value of the specific SPVC correlator to be passed in 340 the SETUP message User-User information element and to be used 341 at the target interface when the frSwitchedPVCTargetSelectType 342 is set to 'specificSPVCCorrelator'." 343 ::= { frSwitchedPVCEntry 6 } 345 frSwitchedPVCLastReleaseCause OBJECT-TYPE 346 SYNTAX INTEGER(1..127) 347 MAX-ACCESS read-only 348 STATUS current 349 DESCRIPTION 350 "Value of the Cause field of the Cause Information Element in 351 the last Release Signalling message received for this SPVC. 352 Indicates the reason for the Disconnect." 353 ::= { frSwitchedPVCEntry 7 } 355 frSwitchedPVCLastReleaseDiagnostic OBJECT-TYPE 356 SYNTAX OCTET STRING (SIZE(0..8)) 357 MAX-ACCESS read-only 358 STATUS current 359 DESCRIPTION 360 "Value of the first 8 bytes of diagnostic information from the 361 Cause field of the Cause Information Element in the last 362 Release Signalling message received for this SPVC." 363 ::= { frSwitchedPVCEntry 8 } 365 frSwitchedPVCOperStatus OBJECT-TYPE 366 SYNTAX INTEGER { 367 other(1), 368 setupInProgress(2), 369 connected(3), 370 failed(4) 371 } 372 MAX-ACCESS read-only 373 STATUS current 374 DESCRIPTION 375 "Describes the status of the SPVC. If the row is not active, 376 the value of this object is 'other'." 377 ::= { frSwitchedPVCEntry 9 } 379 frSwitchedPVCRestart OBJECT-TYPE 380 SYNTAX INTEGER { 381 restart(1), 382 noop(2) 383 } 384 MAX-ACCESS read-create 385 STATUS current 386 DESCRIPTION 387 "When the value is set to 'noop' then no action is taken; 388 otherwise, when the value is set to 'restart', the PVC is 389 released if necessary and a new setup procedure is begun. As a 390 result of this action, the frSwitchedPVCOperStatus object 391 transitions to 'setupInProgress' (either from the 'connected' 392 or 'failed' state). When read, the value 'noop' is returned." 393 ::= { frSwitchedPVCEntry 10 } 395 frSwitchedPVCRetryInterval OBJECT-TYPE 396 SYNTAX INTEGER (0..3600) 397 UNITS "seconds" 398 MAX-ACCESS read-create 399 STATUS current 400 DESCRIPTION 401 "Defines the period to wait (in seconds) before attempting to 402 establish the SPVC connection after the first failed call 403 attempt. Zero represents an infinite interval indicating no 404 retries." 405 DEFVAL { 0 } 406 ::= { frSwitchedPVCEntry 11 } 408 frSwitchedPVCRetryTimer OBJECT-TYPE 409 SYNTAX INTEGER 410 UNITS "seconds" 411 MAX-ACCESS read-only 412 STATUS current 413 DESCRIPTION 414 "Indicates the current value of the retry timer (in seconds) 415 for this connection. When the value reaches zero, an attempt 416 will be made to establish the SPVC connection" 417 ::= { frSwitchedPVCEntry 12 } 419 frSwitchedPVCRetryFailures OBJECT-TYPE 420 SYNTAX INTEGER 421 MAX-ACCESS read-only 422 STATUS current 423 DESCRIPTION 424 "Indicates how many attempts to establish the connection have 425 failed. This counter is reset whenever a connection is 426 successfully established or the SPVC is restarted." 427 ::= { frSwitchedPVCEntry 13 } 429 frSwitchedPVCRetryLimit OBJECT-TYPE 430 SYNTAX INTEGER 431 MAX-ACCESS read-create 432 STATUS current 433 DESCRIPTION 434 "Sets a maximum limit on how many consecutive unsuccessful call 435 setup attempts can be made before stopping the attempt to set 436 up the connection. If this limit is reached then management 437 action will be required to initiate a new attempt to establish 438 the connection. A value of zero indicates no limit - the 439 attempt will continue until successful." 440 DEFVAL { 0 } 441 ::= { frSwitchedPVCEntry 14 } 443 frSwitchedPVCRowStatus OBJECT-TYPE 444 SYNTAX RowStatus 445 MAX-ACCESS read-create 446 STATUS current 447 DESCRIPTION 448 "Used to create and delete an SPVC. When this object is set to 449 'active' an attempt is made to set up the SPVC. When this 450 object has the value 'active' and is set to another value, any 451 set-up or connection in-progress is released." 452 ::= { frSwitchedPVCEntry 15 } 454 -- 455 -- Currently Failing Switched PVC table. 456 -- 458 frCurrentlyFailingSwitchedPVCTable OBJECT-TYPE 459 SYNTAX SEQUENCE OF FrCurrentlyFailingSwitchedPVCEntry 460 MAX-ACCESS not-accessible 461 STATUS current 462 DESCRIPTION 463 "A table indicating all Switched Permanent Virtual Connections 464 (Switched PVCs) for which the frSwitchedPVCRowStatus is 465 'active' and the frSwitchedPVCOperStatus is other than 466 'connected'." 467 ::= { frSwitchedPvcMIBObjects 11 } 469 frCurrentlyFailingSwitchedPVCEntry OBJECT-TYPE 470 SYNTAX FrCurrentlyFailingSwitchedPVCEntry 471 MAX-ACCESS not-accessible 472 STATUS current 473 DESCRIPTION 474 "Each entry in this table represents a Switched Permanent 475 Virtual Connection (Switched PVC) for which the 476 frSwitchedPVCRowStatus is 'active' and the 477 frSwitchedPVCOperStatus is other than 'connected'." 478 INDEX { ifIndex, frDlci } 479 ::= { frCurrentlyFailingSwitchedPVCTable 1 } 481 FrCurrentlyFailingSwitchedPVCEntry ::= 482 SEQUENCE { 483 frCurrentlyFailingSwitchedPVCTimeStamp 484 TimeStamp 485 } 487 frCurrentlyFailingSwitchedPVCTimeStamp OBJECT-TYPE 488 SYNTAX TimeStamp 489 MAX-ACCESS read-only 490 STATUS current 491 DESCRIPTION 492 "The time at which this Switched PVC began to fail." 493 ::= { frCurrentlyFailingSwitchedPVCEntry 1 } 495 -- 496 -- Switched PVC MIB Definitions 497 -- 499 frSwitchedPvcBaseGroup OBJECT IDENTIFIER ::= { frnetservObjects 12 } 501 frSwitchedPvcCallFailuresTrapEnable OBJECT-TYPE 502 SYNTAX TruthValue 503 MAX-ACCESS read-write 504 STATUS current 505 DESCRIPTION 506 "Allows the generation of traps in response to call failures." 507 ::= { frSwitchedPvcBaseGroup 1 } 509 frSwitchedPvcCallFailures OBJECT-TYPE 510 SYNTAX TruthValue 511 MAX-ACCESS read-only 512 STATUS current 513 DESCRIPTION 514 "The number of times a series of call attempts has failed to 515 establish a Switched PVC." 516 ::= { frSwitchedPvcBaseGroup 2 } 518 frSwitchedPvcCurrentlyFailingSwitchedPVCs OBJECT-TYPE 519 SYNTAX Gauge32 520 MAX-ACCESS read-only 521 STATUS current 522 DESCRIPTION 523 "The current number of Switched-PVC connections for which the 524 frSwitchedPVCOperStatus does not have the value 'connected'." 525 ::= { frSwitchedPvcBaseGroup 3 } 527 frSwitchedPvcNotificationInterval OBJECT-TYPE 528 SYNTAX Integer32 (0..3600) 529 UNITS "seconds" 530 MAX-ACCESS read-write 531 DESCRIPTION 532 "The minimum interval in seconds between the sending of 533 frSwitchedPvcCallFailuresTrap notifications." 534 ::= { frSwitchedPvcBaseGroup 4 } 536 END 538 6. Acknowledgments 540 Special thanks to Andy Malis and Ron Parker of Cascade 541 Communications and Dave Sinicrope of IBM for their 542 valuable comments. 544 7. References 546 [1] Brown, T., "Definitions of Managed Objects for Frame 547 Relay Service", RFC 1604, Bell Communications Research, 548 March 1994. 550 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 551 and S. Waldbusser, "Structure of Management Information 552 for Version 2 of the Simple Network Management Protocol 553 (SNMPv2)", RFC 1902, January 1996. 555 [3] McCloghrie, K., and M. Rose, Editors, "Management 556 Information Base for Network Management of TCP/IP-based 557 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 558 Performance Systems International, March 1991. 560 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 561 and S. Waldbusser, "Protocol Operations for Version 2 of 562 the Simple Network Management Protocol (SNMPv2)", RFC 563 1905, January 1996. 565 [5] ATM Forum Technical Committee, "Private Network-Network 566 Specification Version 1.0 Addendum (Soft PVC MIB)", 567 af-pnni-0066.000, July 1996. 569 8. Author's Address 571 Bill Coutts 572 Cascade Communications Corp 573 5 Carlisle Road 574 Westford, MA 01886 575 USA 577 Phone: +1 508 692 2600 x1516 578 Email: bcoutts@casc.com