idnits 2.17.1 draft-ietf-frnetmib-spvc-02.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-24) 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. ** The document is more than 15 pages and seems to lack a Table of Contents. == 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 an Introduction section. ** 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.) ** There are 147 instances of too long lines in the document, the longest one being 14 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 62 has weird spacing: '...Objects in t...' == Line 65 has weird spacing: '... object type ...' == Line 66 has weird spacing: '... with an o...' == Line 67 has weird spacing: '...pecific insta...' == Line 68 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 (May 13, 1999) is 9113 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) -- Missing reference section? '2' on line 806 looks like a reference -- Missing reference section? '3' on line 811 looks like a reference -- Missing reference section? '4' on line 816 looks like a reference -- Missing reference section? '1' on line 802 looks like a reference -- Missing reference section? '5' on line 821 looks like a reference Summary: 12 errors (**), 0 flaws (~~), 7 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET DRAFT B. Coutts 3 Ascend Communications Inc. 4 November 13, 1998 5 Expires May 13, 1999 7 Frame Relay Switched PVC MIB 9 1. Status of this Memo 11 This document is an Internet-Draft. Internet-Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its areas, 13 and its working groups. Note that other groups may also distribute 14 working documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six 17 months. Internet-Drafts may be updated, replaced, or obsoleted by 18 other documents at any time. It is not appropriate to use Internet- 19 Drafts as reference material or to cite them other than as a 20 ``working draft'' or ``work in progress.'' 22 To learn the current status of any Internet-Draft, please check the 23 ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow 24 Directories on ftp.ietf.org (US East Coast), nic.nordu.net 25 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific 26 Rim). 28 This draft document will be submitted to the RFC editor as a stand- 29 alone SNMP MIB. Please send comments to the author, copying frs- 30 mib@newbridge.com. It expires May 1999. 32 2. Abstract 34 This memo defines a portion of the Management Information Base (MIB) 35 for use with network management protocols in TCP/IP- based internets. 36 In particular, it defines objects for managing Frame Relay Switched 37 Permanent Virtual Circuits (SPVCs). This memo does not specify a 38 standard for the Internet community. 40 3. The SNMPv2 Network Management Framework 42 The major components of the SNMPv2 Network Management framework are 43 described in the documents listed below. 45 o RFC 1902 [2] defines the Structure of Management 46 Information (SMI), the mechanisms used for describing and 47 naming objects for the purpose of management. 49 o STD 17, RFC 1213 [3] defines MIB-II, the core set of 50 managed objects (MO) for the Internet suite of protocols. 52 o RFC 1905 [4] defines the protocol used for network access 53 to managed objects. 55 o RFC 1604 [1] defines the protocol used for managing 56 Frame Relay services. 58 The framework is adaptable/extensible by defining new MIBs to suit 59 the requirements of specific applications/protocols/situations. 61 Managed objects are accessed via a virtual information store, the 62 MIB. Objects in the MIB are defined using the subset of 63 Abstract Syntax Notation One (ASN.1) defined in the SMI. In 64 particular, each object type is named by an OBJECT IDENTIFIER, which 65 is an administratively assigned name. The object type together 66 with an object instance serves to uniquely identify a 67 specific instantiation of the object. For human convenience, often 68 a textual string, termed the descriptor, is used to refer to the 69 object type. 71 4. Overview 73 This MIB addresses the instances needed to manage the Frame Relay 74 Forum's Implementation Agreement for SPVCs (FRF.10). These instances 75 are based on the ATM Forum Soft PVC MIB [5] objects to provide a 76 consistent Switched PVC management model for both ATM and Frame Relay 77 SPVCs. 79 A Switched PVC (SPVC) is a virtual circuit that appears to the user 80 to be a PVC but spans multiple networks as an SVC. The originating 81 network "ingress" endpoint is configured as one PVC endpoint and is 82 configured with information (including a destination address) 83 required to signal and establish an SVC across the NNI interfaces 84 between networks. The destination network "egress" endpoint is 85 configured as the second PVC endpoint and is configured with the 86 destination address. The originating endpoint has the responsibility 87 for establishing, releasing, and re-establishing the SPVC. 89 4.1. Originating Endpoint 91 In order to configure the originating endpoint SPVC parameters, an 92 entry in the PVC End-Point table and an entry in the Switched PVC 93 table must be defined. The PVC End-Point table entry (see the PVC 94 End-Point Group in RFC 1604 [1]) identifies the bi-directional 95 traffic parameters for the originating endpoint of the SPVC. The 96 Switched PVC table entry (defined in this SPVC MIB) identifies the 97 destination address information (e.g., E.164 address) of the SPVC. 98 Together these two entries provide the information required (by the 99 network originating the SPVC) to signal an SVC across the NNI. 101 A row in the PVC End-Point table must be created prior to creating a 102 row in the Switched PVC table. And the corresponding row in the PVC 103 End-Point table must be active prior to activating the Switched PVC 104 table row. When the Switched PVC table row is made active, an 105 attempt is made to set up a switched connection to an interface at 106 the destination switch. 108 Presently, the Frame Relay Service MIB (RFC 1604 [1]) does not 109 include an SVC cross-connect table. Once such a table is defined, an 110 SVC cross-connect table entry should be created at the time the SPVC 111 table row is made active; and deleted at the time the SPVC table row 112 is made inactive. 114 4.2. Terminating Endpoint 116 The Switched PVC Address Table (defined in this SPVC MIB) is used to 117 configure one or more addresses for each SPVC terminating endpoint 118 interface. 120 In order to configure the terminating endpoint PVC parameters (e.g., 121 terminating endpoint DLCI), an entry in the PVC End-Point table (see 122 the PVC End-Point Group in RFC 1604 [1]) may be defined prior to the 123 arrival of the Setup request. 125 4.3. Asymmetric and Symmetric SPVC Establishment 127 The configuration of an originating SPVC endpoint and a terminating 128 SPVC endpoint defines an "asymmetric" SPVC: only one of the two SPVC 129 endpoints has the capability to originate the SPVC. FRF.10 also 130 requires the capability to originate the SPVC from both of the SPVC 131 endpoints ("symmetric" SPVC establishment). 133 Configuration of the symmetric SPVC establishment case is 134 accomplished by provisioning two asymmetric configurations (with the 135 roles of originating endpoint and terminating endpoint reversed for 136 one of the configurations). The MIB defined herein will highlight 137 differences between the asymmetric and symmetric cases where 138 necessary. 140 See FRF.10 for symmetric establishment procedures including handling 141 of "call collisions". For instance, FRF.10 indicates that only the 142 "specificDlci" or "specificSpvcCorrelator" target select type may be 143 used for symmetric establishment. (This is because the call 144 collision would not be detectable for the "anyDlci" target select 145 type.) 147 4.4. FR/ATM SPVC Interworking 149 This SPVC MIB also includes objects for performing FR/ATM service 150 interworking. The originating network "ingress" FR endpoint defined 151 in this MIB can select an ATM VPI/VCI for the target destination. 152 The originating endpoint can also select whether multiprotocol 153 encapsulation translation between RFC 1490 and RFC 1483 is required. 155 5. Definitions 157 FR-SWITCHED-PVC-MIB DEFINITIONS ::= BEGIN 159 IMPORTS 160 MODULE-IDENTITY, OBJECT-TYPE, Gauge32, 161 Integer32 FROM SNMPv2-SMI 162 TEXTUAL-CONVENTION, NOTIFICATION-TYPE, 163 TruthValue, TimeStamp, RowStatus FROM SNMPv2-TC 164 OBJECT-GROUP FROM SNMPv2-CONF 165 ifIndex FROM RFC-1213 167 frSwitchedPvcMIB MODULE-IDENTITY 168 LAST-UPDATED "9003010000Z" 169 ORGANIZATION "IETF TBD Working Group" 170 CONTACT-INFO 171 "Bill Coutts 172 Ascend Communications Inc. 173 1 Robbins Road 174 Westford, MA 01886 USA 176 Tel: 1-978-952-1516 177 Fax: 1-978-392-2075 178 E-mail: bill.coutts@ascend.com." 180 frSwitchedPvcMIBObjects OBJECT IDENTIFIER ::= { frSwitchedPvcMIB 1 } 181 frSwitchedPvcMIBTraps OBJECT IDENTIFIER ::= { frSwitchedPvcMIB 2 } 183 FrSwitchedPvcAddrPlan ::= TEXTUAL-CONVENTION 184 STATUS current 185 DESCRIPTION 186 "The number plan for an SPVC address." 187 SYNTAX INTEGER { 188 other(1), 189 e164(2), 190 x121(3), 191 none(4), 192 nsap(5) -- NSAP format 193 } 195 FrSwitchedPvcAddr ::= TEXTUAL-CONVENTION 196 STATUS current 197 DESCRIPTION 198 "The FR SPVC address used by the network entity. 199 The number of octets are dependent on the address plan: 200 none (0 octets), 201 other, E.164, and X.121 (8 octets) - these are 202 BCD encoded; leading 0 semi-octets and a single 203 trailing semi-octet of 'F' are used. 204 NSAP (20 octets) - binary encoded." 205 SYNTAX OCTET STRING (SIZE(0|8|20)) 207 -- 208 -- Switched PVC 209 -- 210 -- 211 -- A Switched PVC (SPVC) is a virtual circuit that appears to the user to be a 212 -- PVC but spans multiple networks as an SVC. 213 -- The PVC End-Point table entry (see the PVC End-Point Group in RFC 1604) 214 -- identifies the bi-directional traffic parameters for the originating endpoint 215 -- of the SPVC; and the Switched PVC table entry (of this Switched PVC MIB) 216 -- identifies the target (destination) address information (e.g., E.164 address) 217 -- of the SPVC. Together these two entries provide the information required 218 -- (by the network originating the SPVC) to signal an SVC across the NNI. 219 -- 220 -- To create and activate an SPVC at the originating endpoint, the following 221 -- procedures shall be followed: 222 -- 1). Create an entry in the frPVCEndptTable (see RFC 1604). 223 -- 2). Create an entry in the frSwitchedPvcTable (in this MIB). 224 -- 3). Activate the frPVCEndptTable entry. 225 -- 4). When the corresponding row in the frSwitchedPvcTable (i.e., the rows with 226 -- matching UNI/NNI logical port and matching DLCI index values) is set to 227 -- 'active', an attempt is made to set up a switched connection to an 228 -- interface at the destination switch. 230 -- The Switched PVC Address table (frSwitchedPvcAddressTable defined in this 231 -- MIB) identifies the addresses assigned to the SPVC destination UNI/NNIs (the 232 -- terminating endpoints). Prior to creating and activating an SPVC at the 233 -- originating endpoint (in the originating network), an entry must be created 234 -- in the Switched PVC Address table in the network that terminates the SPVC. 235 -- This terminating address corresponds to the target address configured in the 236 -- Switched PVC table of the originating network. At the destination, a PVC 237 -- End-Point table entry may be defined. As a result, the PVC's inactive 238 -- status can be signaled across the UNI/NNI prior to the arrival of the Setup 239 -- request. 241 -- 242 -- The Frame Relay Switched PVC Table (Originating Endpoint) 243 -- 245 frSwitchedPvcTable OBJECT-TYPE 246 SYNTAX SEQUENCE OF FrSwitchedPvcEntry 247 MAX-ACCESS not-accessible 248 STATUS current 249 DESCRIPTION 250 "The (conceptual) table used to manage Switched Permanent 251 Virtual Connections (SPVCs). The SPVC table is applicable 252 only to switches." 253 ::= { frSwitchedPvcMIBObjects 1 } 255 frSwitchedPvcEntry OBJECT-TYPE 256 SYNTAX FrSwitchedPvcEntry 257 MAX-ACCESS not-accessible 258 STATUS current 259 DESCRIPTION 260 "Each entry in this table represents a Switched Permanent 261 Virtual Connection (SPVC) originating at a switch interface. 262 An SPVC is a VC that is : 263 - provisioned at the originating (source) interface of the 264 connection. 265 - established by signalling procedures across a network to a 266 destination interface. 268 A row in the frPVCEndptTable must be created, defining a PVC 269 endpoint on the source interface, prior to creating an 270 frSwitchedPvcEntry row. The row in the frPVCEndptTable must 271 be active prior to activating the frSwitchedPvcEntry row. The 272 contents of this table reflect only the characteristics unique 273 to a Switched PVC. The traffic and signalling parameters are 274 defined in the PVC endpoint row for the source interface. 275 Since the Low Layer Compatibility, Called Party Subaddress, 276 and Calling Party Subaddress information elements are used to 277 carry end-to-end information, they are not used in the 278 configuration of Switched PVC. Note that the User-User 279 Information information element is used to contain the 280 frSwitchedPvcTargetIdentifier if 'specificSpvcCorrelator' is 281 selected in the frSwitchedPvcTargetSelectType. 283 When a row is made active, an attempt is made to set up a 284 switched connection to an interface at the destination switch. 285 No objects (other that frSwitchedPvcAdminStatus and 286 frSwitchedPvcRowStatus) can be set while the row is active. 288 The combination of the frSwitchedPvcIfIndex and 289 frSwitchedPvcDlciIndex specified in the index clause of this entry 290 serves to identify the PVC endpoint on the source interface. 292 In accordance with ITU-T X.76 Annex A, if the 293 frSwitchedPvcTargetSelectType is provisioned for either 294 'specificDlci' or 'specificSpvcCorrelator', SPVC 295 establishment can be attempted from either one or both 296 endpoints. Otherwise, SPVC establishment must be 297 attempted from a single endpoint chosen through bilateral 298 agreement - that is, the SPVC need only be provisioned at a 299 single endpoint" 300 INDEX { frSwitchedPvcIfIndex, frSwitchedPvcDlciIndex } 301 ::= { frSwitchedPvcTable 1 } 303 FrSwitchedPvcEntry ::= 304 SEQUENCE { 305 frSwitchedPvcIfIndex 306 ifIndex, 307 frSwitchedPvcDlciIndex 308 Integer32, 309 frSwitchedPvcTargetAddress 310 FrSwitchedPvcAddr, 311 frSwitchedPvcTargetAddressPlan 312 FrSwitchedPvcAddrPlan, 313 frSwitchedPvcTargetSelectType 314 INTEGER, 315 frSwitchedPvcFrTargetIdentifier 316 Integer32, 317 frSwitchedPvcAtmTargetVpi 318 INTEGER, 319 frSwitchedPvcAtmTargetVci 320 INTEGER, 321 frSwitchedPvcAtmTranslation 322 INTEGER, 323 frSwitchedPvcLastReleaseCause 324 INTEGER, 325 frSwitchedPvcLastReleaseDiagnostic 326 OCTET STRING, 327 frSwitchedPvcOperStatus 328 INTEGER, 329 frSwitchedPvcAdminStatus 330 INTEGER, 331 frSwitchedPvcRestart 332 INTEGER, 333 frSwitchedPvcRetryInterval 334 INTEGER, 335 frSwitchedPvcRetryTimer 336 INTEGER, 337 frSwitchedPvcRetryFailures 338 INTEGER, 339 frSwitchedPvcRetryLimit 340 INTEGER, 341 frSwitchedPvcLastChange 342 TimeStamp, 343 frSwitchedPvcRowStatus 344 RowStatus 345 } 347 frSwitchedPvcIfIndex OBJECT-TYPE 348 SYNTAX IfIndex 349 MAX-ACCESS not-accessible 350 STATUS current 351 DESCRIPTION 352 "The value of this object is equal to MIB II's ifIndex value of 353 the UNI/NNI logical port for this PVC endpoint." 354 ::= { frSwitchedPvcEntry 1 } 356 frSwitchedPvcDlciIndex OBJECT-TYPE 357 SYNTAX Integer32 358 MAX-ACCESS not-accessible 359 STATUS current 360 DESCRIPTION 361 "The value of this object is equal to the DLCI value for this 362 PVC endpoint." 363 ::= { frSwitchedPvcEntry 2 } 365 frSwitchedPvcTargetAddress OBJECT-TYPE 366 SYNTAX FrSwitchedPvcAddr 367 MAX-ACCESS read-create 368 STATUS current 369 DESCRIPTION 370 "The target address of this SPVC." 371 ::= { frSwitchedPvcEntry 3 } 373 frSwitchedPvcTargetAddressPlan OBJECT-TYPE 374 SYNTAX FrSwitchedPvcAddrPlan 375 MAX-ACCESS read-create 376 STATUS current 377 DESCRIPTION 378 "The target address plan of this SPVC." 379 ::= { frSwitchedPvcEntry 4 } 381 frSwitchedPvcTargetSelectType OBJECT-TYPE 382 SYNTAX INTEGER { 383 anyDlci(1), 384 specificDlci(2), 385 specificSpvcCorrelator(3), 386 anyVpiVci(4), 387 specificVpiVci(5) 388 } 389 MAX-ACCESS read-create 390 STATUS current 391 DESCRIPTION 392 "The 'anyDlci', 'specificDlci', and 'specificSpvcCorrelator' 393 values are used to indicate an FR target. These values 394 indicate whether the target DLCI value or SPVC correlator is 395 to be used at the destination. If the value 'anyDlci' is 396 specified, the destination switch will choose the DLCI value. 397 In such a case, once the SPVC frSwitchedPvcOperStatus value is 398 'connected', the value of this object changes to 'specificDlci' 399 such that the same DLCI value will be used even if the 400 connection is subsequently torn-down and re-established. 401 The DLCI value chosen will be available for reading in 402 frSwitchedPvcTargetIdentifier. If the value 'specificDlci' or 403 'specificSpvcCorrelator' is specified, then a value must be 404 supplied for object frSwitchedPvcTargetIdentifier 405 prior to activation of the row. This value is then to be used 406 at the destination. 408 The 'anyVpiVci' and 'specificVpiVci' values are used to indicate 409 an ATM target (and FR/ATM interworking). If the value 410 'anyVpiVci' is specified, the destination switch will choose the 411 VPI/VCI values. In such a case, once the the SPVC 412 frSwitchedPvcOperStatus value is 'connected', the value of this 413 object changes to 'specificVpiVci' such that the same VPI/VCI 414 value will be used even if the connection is subsequently 415 torn-down and re-established. The VPI/VCI value chosen will be 416 available for reading in frSwitchedPvcAtmTargetVpi and 417 frSwitchedPvcAtmTargetVci. If the value 'specificVpiVci' is 418 specified, then a value must be supplied for objects 419 frSwitchedPvcAtmTargetVpi and frSwitchedPvcAtmTargetVci 420 prior to activation of the row. These values are then to be used 421 at the destination." 422 DEFVAL { specificDlci } 423 ::= { frSwitchedPvcEntry 5 } 425 frSwitchedPvcTargetIdentifier OBJECT-TYPE 426 SYNTAX Integer32 (0..8388607) 427 MAX-ACCESS read-create 428 STATUS current 429 DESCRIPTION 430 "This object can represent either the target DLCI value or the 431 SPVC correlator value. When the frSwitchedPvcTargetSelectType 432 is set to 'specificDlci', this object represents the DLCI value 433 of the SPVC and has a range of 16 to 8388607. It is passed in 434 the SETUP message Frame Relay Called Party SPVC information 435 element. When the frSwitchedPvcTargetSelectType is set to 436 'specificSpvcCorrelator', this object represents the value of the 437 specific SPVC correlator to be passed in the SETUP message 438 User-User information element." 439 ::= { frSwitchedPvcEntry 6 } 441 frSwitchedPvcAtmTargetVpi OBJECT-TYPE 442 SYNTAX INTEGER (0..4095) 443 MAX-ACCESS read-create 444 STATUS current 445 DESCRIPTION 446 "When the frSwitchedPvcTargetSelectType is set to 447 'specificVpiVci', this object represents the VPI value 448 of the SPVC target destination. It is passed in the SETUP 449 message Frame Relay Called Party SPVC information element." 450 ::= { frSwitchedPvcEntry 7 } 452 frSwitchedPvcAtmTargetVci OBJECT-TYPE 453 SYNTAX INTEGER (0..65535) 454 MAX-ACCESS read-create 455 STATUS current 456 DESCRIPTION 457 "When the frSwitchedPvcTargetSelectType is set to 458 'specificVpiVci', this object represents the VCI value 459 of the SPVC target destination. It is passed in the SETUP 460 message Frame Relay Called Party SPVC information element." 461 ::= { frSwitchedPvcEntry 8 } 463 frSwitchedPvcAtmTranslation OBJECT-TYPE 464 SYNTAX INTEGER { 465 none(1), 466 rfc1490-rfc1483(2) 467 } 468 MAX-ACCESS read-create 469 STATUS current 470 DESCRIPTION 471 "When the frSwitchedPvcTargetSelectType is 'anyVpiVci' or 472 'specificVpiVci', FR/ATM interworking is indicated. For 473 FR/ATM service interworking, the value 'rfc1490-rfc1483' 474 selects multiprotocol encapsulation translation from FR 475 RFC 1490 to ATM RFC 1483." 476 ::= { frSwitchedPvcEntry 9 } 478 frSwitchedPvcLastReleaseCause OBJECT-TYPE 479 SYNTAX INTEGER(1..127) 480 MAX-ACCESS read-only 481 STATUS current 482 DESCRIPTION 483 "Value of the Cause field of the Cause Information Element in 484 the last Release Signalling message received for this SPVC. 485 Indicates the reason for the Disconnect." 486 ::= { frSwitchedPvcEntry 10 } 488 frSwitchedPvcLastReleaseDiagnostic OBJECT-TYPE 489 SYNTAX OCTET STRING (SIZE(0..8)) 490 MAX-ACCESS read-only 491 STATUS current 492 DESCRIPTION 493 "Value of the first 8 bytes of diagnostic information from the 494 Cause field of the Cause Information Element in the last 495 Release Signalling message received for this SPVC." 496 ::= { frSwitchedPvcEntry 11 } 498 frSwitchedPvcOperStatus OBJECT-TYPE 499 SYNTAX INTEGER { 500 other(1), 501 setupInProgress(2), 502 connectedAsOriginator(3), 503 connectedAsTerminator(4), 504 failed(5) 505 } 506 MAX-ACCESS read-only 507 STATUS current 508 DESCRIPTION 509 "Describes the status of the SPVC. The value 510 'connectedAsOriginator' is set if this endpoint initiated 511 establishment of the connected SPVC. The value is set to 512 'connectedAsTerminator' if the other endpoint initiated 513 establishment of the connect SPVC. If the row is not active, 514 the value of this object is 'other'." 515 ::= { frSwitchedPvcEntry 12 } 517 frSwitchedPvcAdminStatus OBJECT-TYPE 518 SYNTAX INTEGER { 519 up(1), 520 down(2) 521 } 522 MAX-ACCESS read-write 523 STATUS current 524 DESCRIPTION 525 "Used to select the administrative state of this SPVC. When 526 changed to 'down', the PVC is released and the 527 frSwitchedPvcOperStatus object transitions to 'failed'. When 528 changed to 'up', the setup procedure is begun and the 529 frSwitchedPvcOperStatus object transitions to 'setupInProgress'." 530 ::= { frSwitchedPvcEntry 13 } 532 frSwitchedPvcRestart OBJECT-TYPE 533 SYNTAX INTEGER { 534 restart(1), 535 noop(2) 536 } 537 MAX-ACCESS read-create 538 STATUS current 539 DESCRIPTION 540 "When the value is set to 'noop' then no action is taken; 541 otherwise, when the value is set to 'restart', the PVC is 542 released if necessary and a new setup procedure is begun. As a 543 result of this action, the frSwitchedPvcOperStatus object 544 transitions to 'setupInProgress' (either from the 'connected' 545 or 'failed' state). When read, the value 'noop' is returned." 546 ::= { frSwitchedPvcEntry 14 } 548 frSwitchedPvcRetryInterval OBJECT-TYPE 549 SYNTAX INTEGER (0..3600) 550 UNITS "seconds" 551 MAX-ACCESS read-create 552 STATUS current 553 DESCRIPTION 554 "Defines the period to wait (in seconds) before attempting to 555 establish the SPVC connection after the first failed call 556 attempt. Zero represents an infinite interval indicating no 557 retries." 558 DEFVAL { 0 } 559 ::= { frSwitchedPvcEntry 15 } 561 frSwitchedPvcRetryTimer OBJECT-TYPE 562 SYNTAX INTEGER 563 UNITS "seconds" 564 MAX-ACCESS read-only 565 STATUS current 566 DESCRIPTION 567 "Indicates the current value of the retry timer (in seconds) 568 for this connection. When the value reaches zero, an attempt 569 will be made to establish the SPVC connection" 570 ::= { frSwitchedPvcEntry 16 } 572 frSwitchedPvcRetryFailures OBJECT-TYPE 573 SYNTAX INTEGER 574 MAX-ACCESS read-only 575 STATUS current 576 DESCRIPTION 577 "Indicates how many attempts to establish the connection have 578 failed. This counter is reset whenever a connection is 579 successfully established or the SPVC is restarted." 580 ::= { frSwitchedPvcEntry 17 } 582 frSwitchedPvcRetryLimit OBJECT-TYPE 583 SYNTAX INTEGER 584 MAX-ACCESS read-create 585 STATUS current 586 DESCRIPTION 587 "Sets a maximum limit on how many consecutive unsuccessful call 588 setup attempts can be made before stopping the attempt to set 589 up the connection. If this limit is reached then management 590 action will be required to initiate a new attempt to establish 591 the connection. A value of zero indicates no limit - the 592 attempt will continue until successful." 593 DEFVAL { 0 } 594 ::= { frSwitchedPvcEntry 18 } 596 frSwitchedPvcLastChange OBJECT-TYPE 597 SYNTAX TimeStamp 598 MAX-ACCESS read-create 599 STATUS current 600 DESCRIPTION 601 "Used to indicate time of last status change." 602 ::= { frSwitchedPvcEntry 19 } 604 frSwitchedPvcRowStatus OBJECT-TYPE 605 SYNTAX RowStatus 606 MAX-ACCESS read-create 607 STATUS current 608 DESCRIPTION 609 "Used to create and delete an SPVC. When this object is set to 610 'active' an attempt is made to set up the SPVC. When this 611 object has the value 'active' and is set to another value, any 612 set-up or connection in-progress is released." 613 ::= { frSwitchedPvcEntry 20 } 615 -- 616 -- The Frame Relay Switched PVC Address Table (Terminating Endpoint) 617 -- 618 -- 619 -- This table is used to configure one or more addresses prior to 620 -- setting up Switched PVCs at an interface. In addition, prior 621 -- to setting up a Switched PVC at the originating interface, this 622 -- table can be consulted to determine available addresses at the 623 -- destination interface. 624 -- 626 frSwitchedPvcAddressTable OBJECT-TYPE 627 SYNTAX SEQUENCE OF FrSwitchedPvcAddressEntry 628 MAX-ACCESS not-accessible 629 STATUS current 630 DESCRIPTION 631 "This table is used to configure addresses at an 632 interface on this node prior to accepting 633 Switched PVCs at that same interface." 635 ::= { frSwitchedPvcMIBObjects 2 } 637 frSwitchedPvcAddressEntry OBJECT-TYPE 638 SYNTAX FrSwitchedPvcAddressEntry 639 MAX-ACCESS not-accessible 640 STATUS current 641 DESCRIPTION 642 "Address entry for configuring the destination 643 endpoint for a Switched PVC at an interface" 644 INDEX { frSwitchedPvcAddressIfIndex, frSwitchedPvcAddressPlan, 645 frSwitchedPvcAddressAddress } 646 ::= { frSwitchedPvcAddressTable 1 } 648 FrSwitchedPvcAddressEntry ::= 649 SEQUENCE { 650 frSwitchedPvcAddressIfIndex ifIndex, 651 frSwitchedPvcAddressPlan FrSwitchedPvcAddrPlan, 652 frSwitchedPvcAddressAddress FrSwitchedPvcAddr, 653 frSwitchedPvcAddressRowStatus RowStatus 654 } 656 frSwitchedPvcIfIndex OBJECT-TYPE 657 SYNTAX IfIndex 658 MAX-ACCESS not-accessible 659 STATUS current 660 DESCRIPTION 661 "The value of this object is equal to MIB II's ifIndex value of 662 the UNI/NNI logical port for this PVC endpoint." 663 ::= { frSwitchedPvcAddressEntry 1 } 665 frSwitchedPvcAddressPlan OBJECT-TYPE 666 SYNTAX FrSwitchedPvcAddrPlan 667 MAX-ACCESS not-accessible 668 STATUS current 669 DESCRIPTION 670 "The number plan for this SPVC destination address." 671 ::= { frSwitchedPvcAddressEntry 2 } 673 frSwitchedPvcAddressAddress OBJECT-TYPE 674 SYNTAX FrSwitchedPvcAddr 675 MAX-ACCESS not-accessible 676 STATUS current 677 DESCRIPTION 678 "The destination address for an SPVC." 679 ::= { frSwitchedPvcAddressEntry 3 } 681 frSwitchedPvcAddressRowStatus OBJECT-TYPE 682 SYNTAX RowStatus 683 MAX-ACCESS read-create 684 STATUS current 685 DESCRIPTION 686 "Used to create and delete an SPVC address entry." 687 ::= { frSwitchedPvcAddressEntry 4 } 689 -- 690 -- Currently Failing Switched PVC table. 691 -- 693 frCurrentlyFailingSwitchedPvcTable OBJECT-TYPE 694 SYNTAX SEQUENCE OF FrCurrentlyFailingSwitchedPvcEntry 695 MAX-ACCESS not-accessible 696 STATUS current 697 DESCRIPTION 698 "A table indicating all Switched Permanent Virtual Connections 699 (Switched PVCs) for which the frSwitchedPvcRowStatus is 700 'active' and the frSwitchedPvcOperStatus is other than 701 'connected'." 702 ::= { frSwitchedPvcMIBObjects 3 } 704 frCurrentlyFailingSwitchedPvcEntry OBJECT-TYPE 705 SYNTAX FrCurrentlyFailingSwitchedPvcEntry 706 MAX-ACCESS not-accessible 707 STATUS current 708 DESCRIPTION 709 "Each entry in this table represents a Switched Permanent 710 Virtual Connection (Switched PVC) for which the 711 frSwitchedPvcRowStatus is 'active' and the 712 frSwitchedPvcOperStatus is other than 'connected'." 713 INDEX { ifIndex, frDlci } 714 ::= { frCurrentlyFailingSwitchedPvcTable 1 } 716 FrCurrentlyFailingSwitchedPvcEntry ::= 717 SEQUENCE { 718 frCurrentlyFailingSwitchedPvcTimeStamp 719 TimeStamp 720 } 722 frCurrentlyFailingSwitchedPvcTimeStamp OBJECT-TYPE 723 SYNTAX TimeStamp 724 MAX-ACCESS read-only 725 STATUS current 726 DESCRIPTION 727 "The time at which this Switched PVC began to fail." 728 ::= { frCurrentlyFailingSwitchedPvcEntry 1 } 730 -- 731 -- Switched PVC MIB Definitions 732 -- 734 frSwitchedPvcBaseGroup OBJECT IDENTIFIER ::= { frSwitchedPvcMIBObjects 4 } 736 frSwitchedPvcCallFailuresTrapEnable OBJECT-TYPE 737 SYNTAX TruthValue 738 MAX-ACCESS read-write 739 STATUS current 740 DESCRIPTION 741 "Allows the generation of traps in response to call failures." 742 ::= { frSwitchedPvcBaseGroup 1 } 744 frSwitchedPvcCallFailures OBJECT-TYPE 745 SYNTAX TruthValue 746 MAX-ACCESS read-only 747 STATUS current 748 DESCRIPTION 749 "The number of times a series of call attempts has failed to 750 establish a Switched PVC." 751 ::= { frSwitchedPvcBaseGroup 2 } 753 frSwitchedPvcCurrentlyFailingSwitchedPvcs OBJECT-TYPE 754 SYNTAX Gauge32 755 MAX-ACCESS read-only 756 STATUS current 757 DESCRIPTION 758 "The current number of Switched-PVC connections for which the 759 frSwitchedPvcOperStatus does not have the value 'connected'." 760 ::= { frSwitchedPvcBaseGroup 3 } 762 frSwitchedPvcNotificationInterval OBJECT-TYPE 763 SYNTAX Integer32 (0..3600) 764 UNITS "seconds" 765 MAX-ACCESS read-write 766 DESCRIPTION 767 "The minimum interval in seconds between the sending of 768 frSwitchedPvcCallFailuresTrap notifications." 769 ::= { frSwitchedPvcBaseGroup 4 } 771 -- 772 -- Switched PVC Traps 773 -- 775 frSwitchedPvcTraps OBJECT IDENTIFIER ::= { frSwitchedPvcMIBTraps 1 } 776 frSwitchedPvcTrapsPrefix OBJECT IDENTIFIER ::= { frSwitchedPvcTraps 0 } 778 frSwitchedPvcCallFailuresTrap NOTIFICATION-TYPE 779 OBJECTS { 780 frSwitchedPvcCallFailures, 781 frSwitchedPvcCurrentlyFailingSwitchedPvcs } 782 STATUS current 783 DESCRIPTION 784 "A notification indicating that one or more series of 785 call attempts in trying to establish a Switched PVC 786 have failed since the last frSwitchedPvcCallFailuresTrap 787 was sent. If this trap has not been sent for the last 788 frSwitchedPvcNotificationInterval, then it will be sent 789 on the next increment of frSwitchedPvcCallFailures." 790 ::= { frSwitchedPvcTrapsPrefix 1 } 792 END 794 6. Acknowledgments 796 Special thanks to Andy Malis and Ron Parker of Ascend 797 Communications and Dave Sinicrope of IBM for their 798 valuable comments. 800 7. References 802 [1] Brown, T., "Definitions of Managed Objects for Frame 803 Relay Service", RFC 1604, Bell Communications Research, 804 March 1994. 806 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 807 and S. Waldbusser, "Structure of Management Information 808 for Version 2 of the Simple Network Management Protocol 809 (SNMPv2)", RFC 1902, January 1996. 811 [3] McCloghrie, K., and M. Rose, Editors, "Management 812 Information Base for Network Management of TCP/IP-based 813 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 814 Performance Systems International, March 1991. 816 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 817 and S. Waldbusser, "Protocol Operations for Version 2 of 818 the Simple Network Management Protocol (SNMPv2)", RFC 819 1905, January 1996. 821 [5] ATM Forum Technical Committee, "Private Network-Network 822 Specification Version 1.0 Addendum (Soft PVC MIB)", 823 af-pnni-0066.000, July 1996. 825 8. Author's Address 827 Bill Coutts 828 Ascend Communications Inc. 829 1 Robbins Road 830 Westford, MA 01886 831 USA 833 Phone: +1 978 952 1516 834 Email: bill.coutts@ascend.com