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