idnits 2.17.1 draft-ietf-pce-pcep-mib-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (April 2, 2014) is 3670 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) ** Downref: Normative reference to an Informational RFC: RFC 4655 ** Downref: Normative reference to an Informational RFC: RFC 3410 Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 PCE Working Group A. Koushik 3 Internet-Draft Cisco Systems, Inc. 4 Intended status: Standards Track E. Stephan 5 Expires: October 4, 2014 France Telecom 6 Q. Zhao 7 Huawei Technology 8 D. King 9 Old Dog Consulting 10 J. Hardwick 11 Metaswitch 12 April 2, 2014 14 Path Computation Element Protocol (PCEP) Management Information Base 15 draft-ietf-pce-pcep-mib-08 17 Abstract 19 This memo defines a portion of the Management Information Base for 20 use with network management protocols in the Internet community. In 21 particular, it describes managed objects for modeling of Path 22 Computation Element communication Protocol (PCEP) for communications 23 between a Path Computation Client (PCC) and a Path Computation 24 Element (PCE), or between two PCEs. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on October 4, 2014. 43 Copyright Notice 45 Copyright (c) 2014 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 2. The Internet-Standard Management Framework . . . . . . . . . . 3 62 3. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 63 4. PCEP MIB Module Architecture . . . . . . . . . . . . . . . . . 4 64 4.1. pcePcepEntityTable . . . . . . . . . . . . . . . . . . . . 4 65 4.2. pcePcepPeerTable . . . . . . . . . . . . . . . . . . . . . 4 66 4.3. pcePcepSessTable . . . . . . . . . . . . . . . . . . . . . 4 67 4.4. PCEP Notifications . . . . . . . . . . . . . . . . . . . . 5 68 4.5. Relationship to other MIB modules . . . . . . . . . . . . 5 69 5. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 5 70 5.1. PCE-PCEP-MIB . . . . . . . . . . . . . . . . . . . . . . . 5 71 6. Security Considerations . . . . . . . . . . . . . . . . . . . 45 72 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 45 73 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 46 74 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 46 75 9.1. Normative References . . . . . . . . . . . . . . . . . . . 46 76 9.2. Normative References . . . . . . . . . . . . . . . . . . . 46 77 Appendix A. Acknowledgement . . . . . . . . . . . . . . . . . . . 46 79 1. Introduction 81 The Path Computation Element (PCE) defined in [RFC4655] is an entity 82 that is capable of computing a network path or route based on a 83 network graph, and applying computational constraints. A Path 84 Computation Client (PCC) may make requests to a PCE for paths to be 85 computed. 87 The PCE communication protocol (PCEP) is the communication protocol 88 between a PCC and PCE for point-to-point (P2P) path computations and 89 is defined in [RFC5440]. Such PCEP communication interactions 90 include path computation requests and path computation replies as 91 well as notifications of specific states related to the use of a PCE 92 in the context of Multiprotocol Label Switching (MPLS) and 93 Generalized MPLS (GMPLS) Traffic Engineering. 95 This memo defines a portion of the Management Information Base (MIB) 96 for use with network management protocols in the Internet community. 97 In particular, it defines a MIB module that can be used to monitor 98 PCEP communications between a PCC and a PCE, or between two PCEs. 100 This document uses the terminology defined in [RFC4655] and 101 [RFC5440]. 103 2. The Internet-Standard Management Framework 105 For a detailed overview of the documents that describe the current 106 Internet-Standard Management Framework, please refer to section 7 of 107 RFC 3410 [RFC3410]. 109 Managed objects are accessed via a virtual information store, termed 110 the Management Information Base or MIB. MIB objects are generally 111 accessed through the Simple Network Management Protocol (SNMP). 112 Objects in the MIB are defined using the mechanisms defined in the 113 Structure of Management Information (SMI). This memo specifies a MIB 114 module that is compliant to the SMIv2, which is described in STD 58, 115 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579], and STD 58, RFC 2580 116 [RFC2580]. 118 3. Requirements Language 120 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 121 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 122 document are to be interpreted as described in BCP 14, RFC 2119 123 [RFC2119]. 125 4. PCEP MIB Module Architecture 127 The PCEP MIB contains the following information: 129 a. PCE and PCC entity status (see pcePcepEntityTable). 131 b. PCEP peer information (see pcePcepPeerTable). 133 c. PCEP session information (see pcePcepSessTable). 135 d. Notifications to indicate PCEP session changes. 137 4.1. pcePcepEntityTable 139 The pcePcepEntityTable contains one row for each PCEP-speaking entity 140 (PCC or PCE). Each row is read-only and contains current status 141 information plus the running configuration of the PCEP-speaking 142 entity. 144 4.2. pcePcepPeerTable 146 The pcePcepPeerTable contains one row for each PCEP peer that the 147 PCEP entity (PCE or PCC) knows about. Each row is read-only and 148 contains information to identify the peer, the running configuration 149 relating to that peer and statistics that track the messages 150 exchanged with that peer and its response times. 152 Since PCEP sessions can be ephemeral, the pcePcepPeerTable tracks a 153 peer even when no PCEP session currently exists to that peer. The 154 statistics contained in pcePcepPeerTable are an aggregate of the 155 statistics for all successive sessions to that peer. 157 To limit the quantity of information that is stored, an 158 implementation MAY choose to discard a row from the pcePcepPeerTable 159 if and only if no PCEP session exists to the corresponding peer. 161 4.3. pcePcepSessTable 163 The pcePcepSessTable contains one row for each PCEP session that the 164 PCEP entity (PCE or PCC) is currently participating in. Each row is 165 read-only and contains the running configuration that is applied to 166 the session, plus identifiers and statistics for the session. 168 The statistics in pcePcepSessTable are semantically different from 169 those in pcePcepPeerTable since the former apply to the current 170 session only, whereas the latter are the aggregate for all sessions 171 that have existed to that peer. 173 Although [RFC5440] forbids there from being more than one active PCEP 174 session between a given pair of PCEP entities at any one time, there 175 is a window during session establishment where the pcePcepSessTable 176 may contain two rows for a given peer, one representing a session 177 initiated by the local PCEP speaker and one representing a session 178 initiated by the remote PCEP speaker. If either of these sessions 179 reaches active state, then the other is discarded. 181 4.4. PCEP Notifications 183 The PCEP MIB contains notifications for the following conditions. 185 a. pcePcepSessUp: PCEP Session has gone up. 187 b. pcePcepSessDown: PCEP Session has gone down. 189 c. pcePcepSessLocalOverload: Local PCEP entity has sent an overload 190 PCNtf on this session. 192 d. pcePcepSessLocalOverloadClear: Local PCEP entity has sent an 193 overload-cleared PCNtf on this session. 195 e. pcePcepSessPeerOverload: Remote PCEP entity has sent an overload 196 PCNtf on this session. 198 f. pcePcepSessPeerOverloadClear: Remote PCEP entity has sent an 199 overload-cleared PCNtf on this session. 201 4.5. Relationship to other MIB modules 203 The PCEP MIB imports the following textual conventions from the INET- 204 ADDRESS-MIB defined in RFC 4001 [RFC4001]: 206 o InetAddressType 208 o InetAddress 210 PCEP relies on existing protocols which have specialized MIB objects 211 to monitor their own activities. Consequently this document 212 considers that the monitoring of underlying protocols is out of scope 213 of the PCEP MIB module. 215 5. Object Definitions 217 5.1. PCE-PCEP-MIB 219 PCE-PCEP-MIB DEFINITIONS ::= BEGIN 220 IMPORTS 221 MODULE-IDENTITY, 222 OBJECT-TYPE, 223 mib-2, 224 NOTIFICATION-TYPE, 225 Unsigned32, 226 Counter32 227 FROM SNMPv2-SMI -- RFC 2578 228 TruthValue, 229 TimeStamp 230 FROM SNMPv2-TC -- RFC 2579 231 MODULE-COMPLIANCE, 232 OBJECT-GROUP, 233 NOTIFICATION-GROUP 234 FROM SNMPv2-CONF -- RFC 2580 235 InetAddressType, 236 InetAddress 237 FROM INET-ADDRESS-MIB; -- RFC 4001 239 pcePcepMIB MODULE-IDENTITY 240 LAST-UPDATED 241 "201404021200Z" -- 2 April 2014 242 ORGANIZATION 243 "IETF Path Computation Element (PCE) Working Group" 244 CONTACT-INFO 245 "Email: pce@ietf.org 246 WG charter: 247 http://www.ietf.org/html.charters/pce-charter.html" 249 DESCRIPTION 250 "This MIB module defines a collection of objects for managing 251 PCE communication protocol (PCEP). 253 Copyright (C) The IETF Trust (2014). This version of this 254 MIB module is part of RFC YYYY; see the RFC itself for full 255 legal notices." 256 -- RFC Ed,: replace YYYY with actual RFC number & remove this note 257 REVISION 258 "201404021200Z" -- 2 April 2014 259 DESCRIPTION 260 "Initial version, published as RFC YYYY." 261 -- RFC Ed.: replace YYYY with actual RFC number & remove this note 262 ::= { mib-2 XXX } 263 -- RFC Ed.: replace XXX with IANA-assigned number & remove this note 265 pcePcepNotifications OBJECT IDENTIFIER ::= { pcePcepMIB 0 } 266 pcePcepObjects OBJECT IDENTIFIER ::= { pcePcepMIB 1 } 267 pcePcepConformance OBJECT IDENTIFIER ::= { pcePcepMIB 2 } 268 pcePcepEntityObjects OBJECT IDENTIFIER ::= { pcePcepObjects 1 } 270 -- 271 -- PCE Entity Objects 272 -- 274 pcePcepEntityTable OBJECT-TYPE 275 SYNTAX SEQUENCE OF PcePcepEntityEntry 276 MAX-ACCESS not-accessible 277 STATUS current 278 DESCRIPTION 279 "This table contains information about PCEP Entities." 280 ::= { pcePcepEntityObjects 1 } 282 pcePcepEntityEntry OBJECT-TYPE 283 SYNTAX PcePcepEntityEntry 284 MAX-ACCESS not-accessible 285 STATUS current 286 DESCRIPTION 287 "An entry in this table represents a PCEP entity." 288 INDEX { pcePcepEntityIndex } 289 ::= { pcePcepEntityTable 1 } 291 PcePcepEntityEntry ::= SEQUENCE { 292 pcePcepEntityIndex Unsigned32, 293 pcePcepEntityAdminStatus INTEGER, 294 pcePcepEntityOperStatus INTEGER, 295 pcePcepEntityAddrType InetAddressType, 296 pcePcepEntityAddr InetAddress, 297 pcePcepEntityConnectTimer Unsigned32, 298 pcePcepEntityConnectMaxRetry Unsigned32, 299 pcePcepEntityOpenWaitTimer Unsigned32, 300 pcePcepEntityKeepWaitTimer Unsigned32, 301 pcePcepEntityKeepAliveTimer Unsigned32, 302 pcePcepEntityDeadTimer Unsigned32, 303 pcePcepEntityMaxKeepAliveTimer Unsigned32, 304 pcePcepEntityMaxDeadTimer Unsigned32, 305 pcePcepEntityAllowNegotiation TruthValue, 306 pcePcepEntityMinKeepAliveTimer Unsigned32, 307 pcePcepEntityMinDeadTimer Unsigned32, 308 pcePcepEntitySyncTimer Unsigned32, 309 pcePcepEntityRequestTimer Unsigned32, 310 pcePcepEntityInitBackoffTimer Unsigned32, 311 pcePcepEntityMaxBackoffTimer Unsigned32, 312 pcePcepEntityMaxSessions Unsigned32, 313 pcePcepEntityMaxUnknownReqs Unsigned32, 314 pcePcepEntityMaxUnknownMsgs Unsigned32 315 } 316 pcePcepEntityIndex OBJECT-TYPE 317 SYNTAX Unsigned32 (1..2147483647) 318 MAX-ACCESS not-accessible 319 STATUS current 320 DESCRIPTION 321 "This index is used to uniquely identify the PCEP entity." 322 ::= { pcePcepEntityEntry 1 } 324 pcePcepEntityAdminStatus OBJECT-TYPE 325 SYNTAX INTEGER { 326 adminStatusUp(1), 327 adminStatusDown(2) 328 } 329 MAX-ACCESS read-only 330 STATUS current 331 DESCRIPTION 332 "The administrative status of this PCEP Entity." 333 ::= { pcePcepEntityEntry 2 } 335 pcePcepEntityOperStatus OBJECT-TYPE 336 SYNTAX INTEGER { 337 operStatusUp(1), 338 operStatusDown(2), 339 operStatusGoingUp(3), 340 operStatusGoingDown(4), 341 operStatusFailed(5), 342 operStatusFailedPerm(6) 343 } 344 MAX-ACCESS read-only 345 STATUS current 346 DESCRIPTION 347 "The operational status of the PCEP entity. Takes one of the 348 following values. 349 - operStatusUp(1): the PCEP entity is active. 350 - operStatusDown(2): the PCEP entity is inactive. 351 - operStatusGoingUp(3): the PCEP entity is activating. 352 - operStatusGoingDown(4): the PCEP entity is deactivating. 353 - operStatusFailed(5): the PCEP entity has failed and will 354 recover when possible. 355 - operStatusFailedPerm(6): the PCEP entity has failed and 356 will not recover without operator intervention." 357 ::= { pcePcepEntityEntry 3 } 359 pcePcepEntityAddrType OBJECT-TYPE 360 SYNTAX InetAddressType 361 MAX-ACCESS read-only 362 STATUS current 363 DESCRIPTION 364 "The type of the PCEP entity's Internet address. This object 365 specifies how the value of the pcePcepEntityAddr object 366 should be interpreted." 367 ::= { pcePcepEntityEntry 4 } 369 pcePcepEntityAddr OBJECT-TYPE 370 SYNTAX InetAddress 371 MAX-ACCESS read-only 372 STATUS current 373 DESCRIPTION 374 "The local Internet address of this PCEP entity. The type is 375 given by pcePcepEntityAddrType. 377 If operating as a PCE server, the PCEP entity listens on 378 this address. If operating as a PCC, the PCEP entity binds 379 outgoing TCP connections to this address. 381 It is possible for the PCEP entity to operate both as a PCC 382 and a PCE Server, in which case it uses this address both to 383 listen for incoming TCP connections and to bind outgoing 384 TCP connections." 385 ::= { pcePcepEntityEntry 5 } 387 pcePcepEntityConnectTimer OBJECT-TYPE 388 SYNTAX Unsigned32 (1..65535) 389 UNITS "seconds" 390 MAX-ACCESS read-only 391 STATUS current 392 DESCRIPTION 393 "The time that the PCEP entity will wait to establish a TCP 394 connection with a PCEP peer. If a TCP connection is not 395 established within this time then PCEP aborts the session 396 setup attempt." 397 ::= { pcePcepEntityEntry 6 } 399 pcePcepEntityConnectMaxRetry OBJECT-TYPE 400 SYNTAX Unsigned32 401 MAX-ACCESS read-only 402 STATUS current 403 DESCRIPTION 404 "The maximum number of times the system tries to establish 405 a TCP connection to a peer before going back to the Idle 406 state." 407 ::= { pcePcepEntityEntry 7 } 409 pcePcepEntityOpenWaitTimer OBJECT-TYPE 410 SYNTAX Unsigned32 (1..65535) 411 UNITS "seconds" 412 MAX-ACCESS read-only 413 STATUS current 414 DESCRIPTION 415 "The time that the PCEP entity will wait to receive an Open 416 message from a PCEP peer. If no Open message is received 417 within this time then PCEP aborts the session setup 418 attempt." 419 ::= { pcePcepEntityEntry 8 } 421 pcePcepEntityKeepWaitTimer OBJECT-TYPE 422 SYNTAX Unsigned32 (1..65535) 423 UNITS "seconds" 424 MAX-ACCESS read-only 425 STATUS current 426 DESCRIPTION 427 "The time that the PCEP entity will wait to receive a 428 Keepalive or PCErr message from a PCEP peer during session 429 initialization. If no Keepalive or PCErr message is 430 received within this time then PCEP aborts the session setup 431 attempt." 432 ::= { pcePcepEntityEntry 9 } 434 pcePcepEntityKeepAliveTimer OBJECT-TYPE 435 SYNTAX Unsigned32 (0..255) 436 UNITS "seconds" 437 MAX-ACCESS read-only 438 STATUS current 439 DESCRIPTION 440 "The keep alive transmission timer that this PCEP entity will 441 propose in the initial OPEN message of each session it is 442 involved in. This is the maximum time between two 443 consecutive messages sent to a PCEP peer. Zero means that 444 the PCEP entity prefers not to send Keepalives at all. 446 Note that the actual Keepalive transmission intervals, in 447 either direction of an active PCEP session, are determined 448 by negotiation between the PCEP peers as specified by RFC 449 5440, and so may differ from this configured value. For 450 the actually negotiated values (per-session), see 451 pcePcepSessKeepaliveTimer and 452 pcePcepSessPeerKeepaliveTimer." 453 ::= { pcePcepEntityEntry 10 } 455 pcePcepEntityDeadTimer OBJECT-TYPE 456 SYNTAX Unsigned32 (0..255) 457 UNITS "seconds" 458 MAX-ACCESS read-only 459 STATUS current 460 DESCRIPTION 461 "The dead timer that this PCEP entity will propose in the 462 initial OPEN message of each session it is involved in. 463 This is the time after which a PCEP peer should declare a 464 session down if it does not receive any PCEP messages. 466 pcePcepEntityDeadTimer is recommended to be 4 times the 467 pcePcepEntityKeepAliveTimer value. Zero means suggesting 468 that the peer does not run a dead timer at all; it is only 469 allowed when pcePcepEntityKeepAliveTimer is also zero." 470 ::= { pcePcepEntityEntry 11 } 472 pcePcepEntityMaxKeepAliveTimer OBJECT-TYPE 473 SYNTAX Unsigned32 (0..255) 474 UNITS "seconds" 475 MAX-ACCESS read-only 476 STATUS current 477 DESCRIPTION 478 "The maximum value that this PCEP entity will accept from a 479 peer for the interval between Keepalive transmissions. Zero 480 means that the PCEP entity will allow no Keepalive 481 transmission at all." 482 ::= { pcePcepEntityEntry 12 } 484 pcePcepEntityMaxDeadTimer OBJECT-TYPE 485 SYNTAX Unsigned32 (0..255) 486 UNITS "seconds" 487 MAX-ACCESS read-only 488 STATUS current 489 DESCRIPTION 490 "The maximum value that this PCEP entity will accept from a 491 peer for the Dead timer. Zero means that the PCEP entity 492 will allow not running a Dead timer. 494 A Dead timer will not be accepted unless it is both greater 495 than the session Keepalive timer and less than this field." 496 ::= { pcePcepEntityEntry 13 } 498 pcePcepEntityAllowNegotiation OBJECT-TYPE 499 SYNTAX TruthValue 500 MAX-ACCESS read-only 501 STATUS current 502 DESCRIPTION 503 "Whether the PCEP entity will permit negotiation of session 504 parameters." 505 ::= { pcePcepEntityEntry 14 } 507 pcePcepEntityMinKeepAliveTimer OBJECT-TYPE 508 SYNTAX Unsigned32 (0..255) 509 UNITS "seconds" 510 MAX-ACCESS read-only 511 STATUS current 512 DESCRIPTION 513 "In PCEP session parameter negotiation, the minimum value 514 that this PCEP entity will accept for the interval between 515 Keepalive transmissions. Zero means that the PCEP entity 516 insists on no Keepalive transmission at all." 517 ::= { pcePcepEntityEntry 15 } 519 pcePcepEntityMinDeadTimer OBJECT-TYPE 520 SYNTAX Unsigned32 (0..255) 521 UNITS "seconds" 522 MAX-ACCESS read-only 523 STATUS current 524 DESCRIPTION 525 "In PCEP session parameter negotiation, the minimum value 526 that this PCEP entity will accept for the Dead timer. Zero 527 means that the PCEP entity insists on not running a Dead 528 timer. 530 A Dead timer will not be accepted unless it is both greater 531 than the session Keepalive timer and greater than this 532 field." 533 ::= { pcePcepEntityEntry 16 } 535 pcePcepEntitySyncTimer OBJECT-TYPE 536 SYNTAX Unsigned32 (1..65535) 537 UNITS "seconds" 538 MAX-ACCESS read-only 539 STATUS current 540 DESCRIPTION 541 "The value of SYNC timer is used in the case of synchronized 542 path computation request using the SVEC object. 544 Consider the case where a PCReq message is received by a PCE 545 that contains the SVEC object referring to M synchronized 546 path computation requests. If after the expiration of the 547 SYNC timer all the M path computation requests have not been 548 received, a protocol error is triggered and the PCE MUST 549 cancel the whole set of path computation requests. 551 The aim of the SyncTimer is to avoid the storage of unused 552 synchronized requests should one of them get lost for some 553 reasons (for example, a misbehaving PCC)." 554 ::= { pcePcepEntityEntry 17 } 556 pcePcepEntityRequestTimer OBJECT-TYPE 557 SYNTAX Unsigned32 (1..65535) 558 UNITS "seconds" 559 MAX-ACCESS read-only 560 STATUS current 561 DESCRIPTION 562 "The maximum time that the PCEP entity will wait for a 563 response to a PCReq message." 564 ::= { pcePcepEntityEntry 18 } 566 pcePcepEntityInitBackoffTimer OBJECT-TYPE 567 SYNTAX Unsigned32 (1..65535) 568 UNITS "seconds" 569 MAX-ACCESS read-only 570 STATUS current 571 DESCRIPTION 572 "The initial back-off time for retrying a failed session 573 setup attempt to a peer. 575 The back-off time increases for each failed session setup 576 attempt, until a maximum back-off time is reached. The 577 maximum back-off time is pcePcepEntityMaxBackoffTimer." 578 ::= { pcePcepEntityEntry 19 } 580 pcePcepEntityMaxBackoffTimer OBJECT-TYPE 581 SYNTAX Unsigned32 582 UNITS "seconds" 583 MAX-ACCESS read-only 584 STATUS current 585 DESCRIPTION 586 "The maximum back-off time for retrying a failed session 587 setup attempt to a peer. 589 The back-off time increases for each failed session setup 590 attempt, until this maximum value is reached. Session 591 setup attempts then repeat periodically without any 592 further increase in back-off time." 593 ::= { pcePcepEntityEntry 20 } 595 pcePcepEntityMaxSessions OBJECT-TYPE 596 SYNTAX Unsigned32 597 MAX-ACCESS read-only 598 STATUS current 599 DESCRIPTION 600 "Maximum number of sessions involving this PCEP entity 601 that can exist at any time." 602 ::= { pcePcepEntityEntry 21 } 604 pcePcepEntityMaxUnknownReqs OBJECT-TYPE 605 SYNTAX Unsigned32 606 MAX-ACCESS read-only 607 STATUS current 608 DESCRIPTION 609 "The maximum number of unrecognized requests and replies that 610 any session on this PCEP entity is willing to accept per 611 minute. 613 A PCRep message contains an unrecognized reply if it 614 contains an RP object whose request ID does not correspond 615 to any in-progress request sent by this PCEP entity. 617 A PCReq message contains an unrecognized request if it 618 contains an RP object whose request ID is zero." 619 ::= { pcePcepEntityEntry 22 } 621 pcePcepEntityMaxUnknownMsgs OBJECT-TYPE 622 SYNTAX Unsigned32 623 MAX-ACCESS read-only 624 STATUS current 625 DESCRIPTION 626 "The maximum number of unknown messages that any session 627 on this PCEP entity is willing to accept per minute." 628 ::= { pcePcepEntityEntry 23 } 630 -- 631 -- The PCEP Peer Table 632 -- 634 pcePcepPeerObjects OBJECT IDENTIFIER ::= { pcePcepObjects 2 } 636 pcePcepPeerTable OBJECT-TYPE 637 SYNTAX SEQUENCE OF PcePcepPeerEntry 638 MAX-ACCESS not-accessible 639 STATUS current 640 DESCRIPTION 641 "Information about PCEP peers known by the local PCEP 642 speaker. 644 This MIB table gives PCEP peer information that spans PCEP 645 sessions. Information about current PCEP sessions can be 646 found in the pcePcepSessTable MIB table." 647 ::= { pcePcepPeerObjects 1 } 649 pcePcepPeerEntry OBJECT-TYPE 650 SYNTAX PcePcepPeerEntry 651 MAX-ACCESS not-accessible 652 STATUS current 653 DESCRIPTION 654 "Information about a single PCEP peer which spans all PCEP 655 sessions to that peer. The information contained in a row 656 is read-only." 657 INDEX { pcePcepEntityIndex, 658 pcePcepPeerAddrType, 659 pcePcepPeerAddr } 660 ::= { pcePcepPeerTable 1 } 662 PcePcepPeerEntry ::= SEQUENCE { 663 pcePcepPeerAddrType InetAddressType, 664 pcePcepPeerAddr InetAddress, 665 pcePcepPeerRole INTEGER, 666 pcePcepPeerDiscontinuityTime TimeStamp, 667 pcePcepPeerInitiateSession TruthValue, 668 pcePcepPeerSessionExists TruthValue, 669 pcePcepPeerNumSessSetupOK Counter32, 670 pcePcepPeerNumSessSetupFail Counter32, 671 pcePcepPeerSessionUpTime TimeStamp, 672 pcePcepPeerSessionFailTime TimeStamp, 673 pcePcepPeerAvgRspTime Unsigned32, 674 pcePcepPeerLWMRspTime Unsigned32, 675 pcePcepPeerHWMRspTime Unsigned32, 676 pcePcepPeerNumPCReqSent Counter32, 677 pcePcepPeerNumPCReqRcvd Counter32, 678 pcePcepPeerNumPCRepSent Counter32, 679 pcePcepPeerNumPCRepRcvd Counter32, 680 pcePcepPeerNumPCErrSent Counter32, 681 pcePcepPeerNumPCErrRcvd Counter32, 682 pcePcepPeerNumPCNtfSent Counter32, 683 pcePcepPeerNumPCNtfRcvd Counter32, 684 pcePcepPeerNumKeepaliveSent Counter32, 685 pcePcepPeerNumKeepaliveRcvd Counter32, 686 pcePcepPeerNumUnknownRcvd Counter32, 687 pcePcepPeerNumReqSent Counter32, 688 pcePcepPeerNumSvecSent Counter32, 689 pcePcepPeerNumSvecReqSent Counter32, 690 pcePcepPeerNumReqSentPendRep Counter32, 691 pcePcepPeerNumReqSentEroRcvd Counter32, 692 pcePcepPeerNumReqSentNoPathRcvd Counter32, 693 pcePcepPeerNumReqSentCancelRcvd Counter32, 694 pcePcepPeerNumReqSentErrorRcvd Counter32, 695 pcePcepPeerNumReqSentTimeout Counter32, 696 pcePcepPeerNumReqSentCancelSent Counter32, 697 pcePcepPeerNumReqSentClosed Counter32, 698 pcePcepPeerNumReqRcvd Counter32, 699 pcePcepPeerNumSvecRcvd Counter32, 700 pcePcepPeerNumSvecReqRcvd Counter32, 701 pcePcepPeerNumReqRcvdPendRep Counter32, 702 pcePcepPeerNumReqRcvdEroSent Counter32, 703 pcePcepPeerNumReqRcvdNoPathSent Counter32, 704 pcePcepPeerNumReqRcvdCancelSent Counter32, 705 pcePcepPeerNumReqRcvdErrorSent Counter32, 706 pcePcepPeerNumReqRcvdCancelRcvd Counter32, 707 pcePcepPeerNumReqRcvdClosed Counter32, 708 pcePcepPeerNumRepRcvdUnknown Counter32, 709 pcePcepPeerNumReqRcvdUnknown Counter32 710 } 712 pcePcepPeerAddrType OBJECT-TYPE 713 SYNTAX InetAddressType 714 MAX-ACCESS not-accessible 715 STATUS current 716 DESCRIPTION 717 "The type of the peer's Internet address. This object 718 specifies how the value of the pcePcepPeerAddr object should 719 be interpreted." 720 ::= { pcePcepPeerEntry 1 } 722 pcePcepPeerAddr OBJECT-TYPE 723 SYNTAX InetAddress 724 MAX-ACCESS not-accessible 725 STATUS current 726 DESCRIPTION 727 "The Internet address of the peer. The type is given by 728 pcePcepPeerAddrType. " 729 ::= { pcePcepPeerEntry 2 } 731 pcePcepPeerRole OBJECT-TYPE 732 SYNTAX INTEGER { 733 pcc(1), 734 pce(2), 735 pccAndPce(3), 736 unknown(4) 737 } 738 MAX-ACCESS read-only 739 STATUS current 740 DESCRIPTION 741 "The role that this peer took the last time a session was 742 established. Takes one of the following values. 743 - pcc(1): this peer is a Path Computation Client (PCC). 744 - pce(2): this peer is a Path Computation Server (PCE). 745 - pccAndPce(3): this peer is both a PCC and a PCE. 746 - unknown(4): this peer's role is not known." 747 ::= { pcePcepPeerEntry 3 } 749 pcePcepPeerDiscontinuityTime OBJECT-TYPE 750 SYNTAX TimeStamp 751 MAX-ACCESS read-only 752 STATUS current 753 DESCRIPTION 754 "The value of sysUpTime at the time that the information and 755 statistics in this row were last reset." 756 ::= { pcePcepPeerEntry 4 } 758 pcePcepPeerInitiateSession OBJECT-TYPE 759 SYNTAX TruthValue 760 MAX-ACCESS read-only 761 STATUS current 762 DESCRIPTION 763 "Indicates whether the PCEP Entity initiates sessions to this 764 peer, or waits for the peer to initiate a session." 765 ::= { pcePcepPeerEntry 5 } 767 pcePcepPeerSessionExists OBJECT-TYPE 768 SYNTAX TruthValue 769 MAX-ACCESS read-only 770 STATUS current 771 DESCRIPTION 772 "Indicates whether a session with this peer currently 773 exists." 774 ::= { pcePcepPeerEntry 6 } 776 pcePcepPeerNumSessSetupOK OBJECT-TYPE 777 SYNTAX Counter32 778 MAX-ACCESS read-only 779 STATUS current 780 DESCRIPTION 781 "The number of PCEP sessions successfully established with 782 the peer, including any current session. This counter is 783 incremented each time a session with this peer is 784 successfully established." 785 ::= { pcePcepPeerEntry 7 } 787 pcePcepPeerNumSessSetupFail OBJECT-TYPE 788 SYNTAX Counter32 789 MAX-ACCESS read-only 790 STATUS current 791 DESCRIPTION 792 "The number of PCEP sessions with the peer that have been 793 attempted but failed before being fully estbalished. 794 This counter is incremented each time a session with this 795 peer fails before reaching session state pceSessionUp." 796 ::= { pcePcepPeerEntry 8 } 798 pcePcepPeerSessionUpTime OBJECT-TYPE 799 SYNTAX TimeStamp 800 MAX-ACCESS read-only 801 STATUS current 802 DESCRIPTION 803 "The value of sysUpTime the last time a session with this 804 peer was successfully established. 806 If pcePcepPeerNumSessSetupOK is zero, then this object 807 contains zero." 808 ::= { pcePcepPeerEntry 9 } 810 pcePcepPeerSessionFailTime OBJECT-TYPE 811 SYNTAX TimeStamp 812 MAX-ACCESS read-only 813 STATUS current 814 DESCRIPTION 815 "The value of sysUpTime the last time a session with this 816 peer failed to be established. 818 If pcePcepPeerNumSessSetupFail is zero, then this object 819 contains zero." 820 ::= { pcePcepPeerEntry 10 } 822 pcePcepPeerAvgRspTime OBJECT-TYPE 823 SYNTAX Unsigned32 824 UNITS "milliseconds" 825 MAX-ACCESS read-only 826 STATUS current 827 DESCRIPTION 828 "The average response time for this peer. 830 If an average response time has not been calculated for this 831 peer then this object has the value zero. 833 If pcePcepPeerRole is pcc then this field is meaningless and 834 is set to zero." 835 ::= { pcePcepPeerEntry 11 } 837 pcePcepPeerLWMRspTime OBJECT-TYPE 838 SYNTAX Unsigned32 839 UNITS "milliseconds" 840 MAX-ACCESS read-only 841 STATUS current 842 DESCRIPTION 843 "The smallest (low-water mark) response time seen from this 844 peer. 846 If no responses have been received from this peer then this 847 object has the value zero. 849 If pcePcepPeerRole is pcc then this field is meaningless and 850 is set to zero." 851 ::= { pcePcepPeerEntry 12 } 853 pcePcepPeerHWMRspTime OBJECT-TYPE 854 SYNTAX Unsigned32 855 UNITS "milliseconds" 856 MAX-ACCESS read-only 857 STATUS current 858 DESCRIPTION 859 "The greatest (high-water mark) response time seen from this 860 peer. 862 If no responses have been received from this peer then this 863 object has the value zero. 865 If pcePcepPeerRole is pcc then this field is meaningless and 866 is set to zero." 867 ::= { pcePcepPeerEntry 13 } 869 pcePcepPeerNumPCReqSent OBJECT-TYPE 870 SYNTAX Counter32 871 MAX-ACCESS read-only 872 STATUS current 873 DESCRIPTION 874 "The number of PCReq messages sent to this peer." 875 ::= { pcePcepPeerEntry 14 } 877 pcePcepPeerNumPCReqRcvd OBJECT-TYPE 878 SYNTAX Counter32 879 MAX-ACCESS read-only 880 STATUS current 881 DESCRIPTION 882 "The number of PCReq messages received from this peer." 883 ::= { pcePcepPeerEntry 15 } 885 pcePcepPeerNumPCRepSent OBJECT-TYPE 886 SYNTAX Counter32 887 MAX-ACCESS read-only 888 STATUS current 889 DESCRIPTION 890 "The number of PCRep messages sent to this peer." 891 ::= { pcePcepPeerEntry 16 } 893 pcePcepPeerNumPCRepRcvd OBJECT-TYPE 894 SYNTAX Counter32 895 MAX-ACCESS read-only 896 STATUS current 897 DESCRIPTION 898 "The number of PCRep messages received from this peer." 899 ::= { pcePcepPeerEntry 17 } 901 pcePcepPeerNumPCErrSent OBJECT-TYPE 902 SYNTAX Counter32 903 MAX-ACCESS read-only 904 STATUS current 905 DESCRIPTION 906 "The number of PCErr messages sent to this peer." 907 ::= { pcePcepPeerEntry 18 } 909 pcePcepPeerNumPCErrRcvd OBJECT-TYPE 910 SYNTAX Counter32 911 MAX-ACCESS read-only 912 STATUS current 913 DESCRIPTION 914 "The number of PCErr messages received from this peer." 915 ::= { pcePcepPeerEntry 19 } 917 pcePcepPeerNumPCNtfSent OBJECT-TYPE 918 SYNTAX Counter32 919 MAX-ACCESS read-only 920 STATUS current 921 DESCRIPTION 922 "The number of PCNtf messages sent to this peer." 923 ::= { pcePcepPeerEntry 20 } 925 pcePcepPeerNumPCNtfRcvd OBJECT-TYPE 926 SYNTAX Counter32 927 MAX-ACCESS read-only 928 STATUS current 929 DESCRIPTION 930 "The number of PCNtf messages received from this peer." 931 ::= { pcePcepPeerEntry 21 } 933 pcePcepPeerNumKeepaliveSent OBJECT-TYPE 934 SYNTAX Counter32 935 MAX-ACCESS read-only 936 STATUS current 937 DESCRIPTION 938 "The number of Keepalive messages sent to this peer." 939 ::= { pcePcepPeerEntry 22 } 941 pcePcepPeerNumKeepaliveRcvd OBJECT-TYPE 942 SYNTAX Counter32 943 MAX-ACCESS read-only 944 STATUS current 945 DESCRIPTION 946 "The number of Keepalive messages received from this peer." 947 ::= { pcePcepPeerEntry 23 } 949 pcePcepPeerNumUnknownRcvd OBJECT-TYPE 950 SYNTAX Counter32 951 MAX-ACCESS read-only 952 STATUS current 953 DESCRIPTION 954 "The number of unknown messages received from this peer." 955 ::= { pcePcepPeerEntry 24 } 957 pcePcepPeerNumReqSent OBJECT-TYPE 958 SYNTAX Counter32 959 MAX-ACCESS read-only 960 STATUS current 961 DESCRIPTION 962 "The number of requests sent to this peer. A request 963 corresponds 1:1 with an RP object in a PCReq message. 965 This might be greater than pcePcepPeerNumPCReqSent because 966 multiple requests can be batched into a single PCReq 967 message." 968 ::= { pcePcepPeerEntry 25 } 970 pcePcepPeerNumSvecSent OBJECT-TYPE 971 SYNTAX Counter32 972 MAX-ACCESS read-only 973 STATUS current 974 DESCRIPTION 975 "The number of SVEC objects sent to this peer in PCReq 976 messages. An SVEC object represents a set of synchronized 977 requests." 978 ::= { pcePcepPeerEntry 26 } 980 pcePcepPeerNumSvecReqSent OBJECT-TYPE 981 SYNTAX Counter32 982 MAX-ACCESS read-only 983 STATUS current 984 DESCRIPTION 985 "The number of requests sent to this peer that appeared in 986 one or more SVEC objects." 987 ::= { pcePcepPeerEntry 27 } 989 pcePcepPeerNumReqSentPendRep OBJECT-TYPE 990 SYNTAX Counter32 991 MAX-ACCESS read-only 992 STATUS current 993 DESCRIPTION 994 "The number of requests that have been sent to this peer for 995 which a response is still pending." 996 ::= { pcePcepPeerEntry 28 } 998 pcePcepPeerNumReqSentEroRcvd OBJECT-TYPE 999 SYNTAX Counter32 1000 MAX-ACCESS read-only 1001 STATUS current 1002 DESCRIPTION 1003 "The number of requests that have been sent to this peer for 1004 which a response with an ERO object was received. Such 1005 responses indicate that a path was successfully computed by 1006 the peer." 1007 ::= { pcePcepPeerEntry 29 } 1009 pcePcepPeerNumReqSentNoPathRcvd OBJECT-TYPE 1010 SYNTAX Counter32 1011 MAX-ACCESS read-only 1012 STATUS current 1013 DESCRIPTION 1014 "The number of requests that have been sent to this peer for 1015 which a response with a NO-PATH object was received. Such 1016 responses indicate that the peer could not find a path to 1017 satisfy the request." 1018 ::= { pcePcepPeerEntry 30 } 1020 pcePcepPeerNumReqSentCancelRcvd OBJECT-TYPE 1021 SYNTAX Counter32 1022 MAX-ACCESS read-only 1023 STATUS current 1024 DESCRIPTION 1025 "The number of requests that were cancelled by the peer with 1026 a PCNtf message. 1028 This might be different than pcePcepPeerNumPCNtfRcvd because 1029 not all PCNtf messages are used to cancel requests, and a 1030 single PCNtf message can cancel multiple requests." 1031 ::= { pcePcepPeerEntry 31 } 1033 pcePcepPeerNumReqSentErrorRcvd OBJECT-TYPE 1034 SYNTAX Counter32 1035 MAX-ACCESS read-only 1036 STATUS current 1037 DESCRIPTION 1038 "The number of requests that were rejected by the peer with a 1039 PCErr message. 1041 This might be different than pcePcepPeerNumPCErrRcvd because 1042 not all PCErr messages are used to reject requests, and a 1043 single PCErr message can reject multiple requests." 1044 ::= { pcePcepPeerEntry 32 } 1046 pcePcepPeerNumReqSentTimeout OBJECT-TYPE 1047 SYNTAX Counter32 1048 MAX-ACCESS read-only 1049 STATUS current 1050 DESCRIPTION 1051 "The number of requests that have been sent to a peer and 1052 have been abandoned because the peer has taken too long to 1053 respond to them." 1054 ::= { pcePcepPeerEntry 33 } 1056 pcePcepPeerNumReqSentCancelSent OBJECT-TYPE 1057 SYNTAX Counter32 1058 MAX-ACCESS read-only 1059 STATUS current 1060 DESCRIPTION 1061 "The number of requests that were sent to the peer and 1062 explicitly canceled by the local PCEP speaker sending a 1063 PCNtf." 1064 ::= { pcePcepPeerEntry 34 } 1066 pcePcepPeerNumReqSentClosed OBJECT-TYPE 1067 SYNTAX Counter32 1068 MAX-ACCESS read-only 1069 STATUS current 1070 DESCRIPTION 1071 "The number of requests that were sent to the peer and 1072 implicitly canceled when the session they were sent over was 1073 closed." 1074 ::= { pcePcepPeerEntry 35 } 1076 pcePcepPeerNumReqRcvd OBJECT-TYPE 1077 SYNTAX Counter32 1078 MAX-ACCESS read-only 1079 STATUS current 1080 DESCRIPTION 1081 "The number of requests received from this peer. A request 1082 corresponds 1:1 with an RP object in a PCReq message. 1084 This might be greater than pcePcepPeerNumPCReqRcvd because 1085 multiple requests can be batched into a single PCReq 1086 message." 1087 ::= { pcePcepPeerEntry 36 } 1089 pcePcepPeerNumSvecRcvd OBJECT-TYPE 1090 SYNTAX Counter32 1091 MAX-ACCESS read-only 1092 STATUS current 1093 DESCRIPTION 1094 "The number of SVEC objects received from this peer in PCReq 1095 messages. An SVEC object represents a set of synchronized 1096 requests." 1097 ::= { pcePcepPeerEntry 37 } 1099 pcePcepPeerNumSvecReqRcvd OBJECT-TYPE 1100 SYNTAX Counter32 1101 MAX-ACCESS read-only 1102 STATUS current 1103 DESCRIPTION 1104 "The number of requests received from this peer that appeared 1105 in one or more SVEC objects." 1106 ::= { pcePcepPeerEntry 38 } 1108 pcePcepPeerNumReqRcvdPendRep OBJECT-TYPE 1109 SYNTAX Counter32 1110 MAX-ACCESS read-only 1111 STATUS current 1112 DESCRIPTION 1113 "The number of requests that have been received from this 1114 peer for which a response is still pending." 1115 ::= { pcePcepPeerEntry 39 } 1117 pcePcepPeerNumReqRcvdEroSent OBJECT-TYPE 1118 SYNTAX Counter32 1119 MAX-ACCESS read-only 1120 STATUS current 1121 DESCRIPTION 1122 "The number of requests that have been received from this 1123 peer for which a response with an ERO object was sent. Such 1124 responses indicate that a path was successfully computed by 1125 the local PCEP speaker." 1126 ::= { pcePcepPeerEntry 40 } 1128 pcePcepPeerNumReqRcvdNoPathSent OBJECT-TYPE 1129 SYNTAX Counter32 1130 MAX-ACCESS read-only 1131 STATUS current 1132 DESCRIPTION 1133 "The number of requests that have been received from this 1134 peer for which a response with a NO-PATH object was sent. 1135 Such responses indicate that the local PCEP speaker could 1136 not find a path to satisfy the request." 1137 ::= { pcePcepPeerEntry 41 } 1139 pcePcepPeerNumReqRcvdCancelSent OBJECT-TYPE 1140 SYNTAX Counter32 1141 MAX-ACCESS read-only 1142 STATUS current 1143 DESCRIPTION 1144 "The number of requests received from this peer that were 1145 cancelled by the local PCEP speaker sending a PCNtf message. 1147 This might be different than pcePcepPeerNumPCNtfSent because 1148 not all PCNtf messages are used to cancel requests, and a 1149 single PCNtf message can cancel multiple requests." 1150 ::= { pcePcepPeerEntry 42 } 1152 pcePcepPeerNumReqRcvdErrorSent OBJECT-TYPE 1153 SYNTAX Counter32 1154 MAX-ACCESS read-only 1155 STATUS current 1156 DESCRIPTION 1157 "The number of requests received from this peer that were 1158 rejected by the local PCEP speaker sending a PCErr message. 1160 This might be different than pcePcepPeerNumPCErrSent because 1161 not all PCErr messages are used to reject requests, and a 1162 single PCErr message can reject multiple requests." 1163 ::= { pcePcepPeerEntry 43 } 1165 pcePcepPeerNumReqRcvdCancelRcvd OBJECT-TYPE 1166 SYNTAX Counter32 1167 MAX-ACCESS read-only 1168 STATUS current 1169 DESCRIPTION 1170 "The number of requests that were received from the peer and 1171 explicitly canceled by the peer sending a PCNtf." 1172 ::= { pcePcepPeerEntry 44 } 1174 pcePcepPeerNumReqRcvdClosed OBJECT-TYPE 1175 SYNTAX Counter32 1176 MAX-ACCESS read-only 1177 STATUS current 1178 DESCRIPTION 1179 "The number of requests that were received from the peer and 1180 implicitly canceled when the session they were received over 1181 was closed." 1183 ::= { pcePcepPeerEntry 45 } 1185 pcePcepPeerNumRepRcvdUnknown OBJECT-TYPE 1186 SYNTAX Counter32 1187 MAX-ACCESS read-only 1188 STATUS current 1189 DESCRIPTION 1190 "The number of responses to unknown requests received from 1191 this peer. A response to an unknown request is a response 1192 whose RP object does not contain the request ID of any 1193 request that is currently outstanding on the session." 1194 ::= { pcePcepPeerEntry 46 } 1196 pcePcepPeerNumReqRcvdUnknown OBJECT-TYPE 1197 SYNTAX Counter32 1198 MAX-ACCESS read-only 1199 STATUS current 1200 DESCRIPTION 1201 "The number of unknown requests that have been received from 1202 a peer. An unknown request is a request whose RP object 1203 contains a request ID of zero." 1204 ::= { pcePcepPeerEntry 47 } 1206 -- 1207 -- The PCEP Sessions Table 1208 -- 1210 pcePcepSessObjects OBJECT IDENTIFIER ::= { pcePcepObjects 3 } 1212 pcePcepSessTable OBJECT-TYPE 1213 SYNTAX SEQUENCE OF PcePcepSessEntry 1214 MAX-ACCESS not-accessible 1215 STATUS current 1216 DESCRIPTION 1217 "A table of PCEP sessions that involve the local PCEP 1218 speaker. Each row in this table represents a single 1219 session." 1220 ::= { pcePcepSessObjects 1 } 1222 pcePcepSessEntry OBJECT-TYPE 1223 SYNTAX PcePcepSessEntry 1224 MAX-ACCESS not-accessible 1225 STATUS current 1226 DESCRIPTION 1227 "An entry in this table represents a single PCEP session in 1228 which the local PCEP speaker participates. 1230 An entry in this table exists only if the corresponding PCEP 1231 session has been initialized by some event, such as manual 1232 user configuration, autodiscovery of a peer, or an incoming 1233 TCP connection. 1235 An entry appears in this table when the corresponding PCEP 1236 session transitions out of idle state. If the PCEP session 1237 transitions back into idle state then the corresponding 1238 entry in this table is removed." 1239 INDEX { pcePcepEntityIndex, 1240 pcePcepPeerAddrType, 1241 pcePcepPeerAddr, 1242 pcePcepSessInitiator } 1243 ::= { pcePcepSessTable 1 } 1245 PcePcepSessEntry ::= SEQUENCE { 1246 pcePcepSessInitiator INTEGER, 1247 pcePcepSessStateLastChange TimeStamp, 1248 pcePcepSessState INTEGER, 1249 pcePcepSessConnectRetry Counter32, 1250 pcePcepSessLocalID Unsigned32, 1251 pcePcepSessRemoteID Unsigned32, 1252 pcePcepSessKeepaliveTimer Unsigned32, 1253 pcePcepSessPeerKeepaliveTimer Unsigned32, 1254 pcePcepSessDeadTimer Unsigned32, 1255 pcePcepSessPeerDeadTimer Unsigned32, 1256 pcePcepSessKAHoldTimeRem Unsigned32, 1257 pcePcepSessOverloaded TruthValue, 1258 pcePcepSessOverloadTime Unsigned32, 1259 pcePcepSessPeerOverloaded TruthValue, 1260 pcePcepSessPeerOverloadTime Unsigned32, 1261 pcePcepSessDiscontinuityTime TimeStamp, 1262 pcePcepSessAvgRspTime Unsigned32, 1263 pcePcepSessLWMRspTime Unsigned32, 1264 pcePcepSessHWMRspTime Unsigned32, 1265 pcePcepSessNumPCReqSent Counter32, 1266 pcePcepSessNumPCReqRcvd Counter32, 1267 pcePcepSessNumPCRepSent Counter32, 1268 pcePcepSessNumPCRepRcvd Counter32, 1269 pcePcepSessNumPCErrSent Counter32, 1270 pcePcepSessNumPCErrRcvd Counter32, 1271 pcePcepSessNumPCNtfSent Counter32, 1272 pcePcepSessNumPCNtfRcvd Counter32, 1273 pcePcepSessNumKeepaliveSent Counter32, 1274 pcePcepSessNumKeepaliveRcvd Counter32, 1275 pcePcepSessNumUnknownRcvd Counter32, 1276 pcePcepSessNumReqSent Counter32, 1277 pcePcepSessNumSvecSent Counter32, 1278 pcePcepSessNumSvecReqSent Counter32, 1279 pcePcepSessNumReqSentPendRep Counter32, 1280 pcePcepSessNumReqSentEroRcvd Counter32, 1281 pcePcepSessNumReqSentNoPathRcvd Counter32, 1282 pcePcepSessNumReqSentCancelRcvd Counter32, 1283 pcePcepSessNumReqSentErrorRcvd Counter32, 1284 pcePcepSessNumReqSentTimeout Counter32, 1285 pcePcepSessNumReqSentCancelSent Counter32, 1286 pcePcepSessNumReqRcvd Counter32, 1287 pcePcepSessNumSvecRcvd Counter32, 1288 pcePcepSessNumSvecReqRcvd Counter32, 1289 pcePcepSessNumReqRcvdPendRep Counter32, 1290 pcePcepSessNumReqRcvdEroSent Counter32, 1291 pcePcepSessNumReqRcvdNoPathSent Counter32, 1292 pcePcepSessNumReqRcvdCancelSent Counter32, 1293 pcePcepSessNumReqRcvdErrorSent Counter32, 1294 pcePcepSessNumReqRcvdCancelRcvd Counter32, 1295 pcePcepSessNumRepRcvdUnknown Counter32, 1296 pcePcepSessNumReqRcvdUnknown Counter32 1297 } 1299 pcePcepSessInitiator OBJECT-TYPE 1300 SYNTAX INTEGER { 1301 local(1), 1302 remote(2) 1303 } 1304 MAX-ACCESS not-accessible 1305 STATUS current 1306 DESCRIPTION 1307 "The initiator of the session, that is, whether the TCP 1308 connection was initiated by the local PCEP speaker or the 1309 remote PCEP speaker. 1311 There is a window during session initialization where two 1312 sessions can exist between a pair of PCEP speakers, each 1313 initiated by one of the speakers. One of these sessions is 1314 always discarded before it leaves OpenWait state. However, 1315 before it is discarded, two sessions to the given peer 1316 appear transiently in the MIB. The sessions are 1317 distinguished by who initiated them, and so this field is an 1318 index for the pcePcepSessTable." 1319 ::= { pcePcepSessEntry 1 } 1321 pcePcepSessStateLastChange OBJECT-TYPE 1322 SYNTAX TimeStamp 1323 MAX-ACCESS read-only 1324 STATUS current 1325 DESCRIPTION 1326 "The value of sysUpTime at the time this session entered its 1327 current state as denoted by the pcePcepSessState object." 1328 ::= { pcePcepSessEntry 2 } 1330 pcePcepSessState OBJECT-TYPE 1331 SYNTAX INTEGER { 1332 tcpPending(1), 1333 openWait(2), 1334 keepWait(3), 1335 sessionUp(4) 1336 } 1337 MAX-ACCESS read-only 1338 STATUS current 1339 DESCRIPTION 1340 "The current state of the session. 1342 The set of possible states excludes the idle state since 1343 entries do not exist in this table in the idle state." 1344 ::= { pcePcepSessEntry 3 } 1346 pcePcepSessConnectRetry OBJECT-TYPE 1347 SYNTAX Counter32 1348 MAX-ACCESS read-only 1349 STATUS current 1350 DESCRIPTION 1351 "The number of times that the local PCEP speaker has 1352 attempted to establish a TCP connection for this session 1353 without success. The PCEP speaker gives up when this 1354 reaches pcePcepEntityConnectMaxRetry." 1355 ::= { pcePcepSessEntry 4 } 1357 pcePcepSessLocalID OBJECT-TYPE 1358 SYNTAX Unsigned32 (0..255) 1359 MAX-ACCESS read-only 1360 STATUS current 1361 DESCRIPTION 1362 "The value of the PCEP session ID used by the local PCEP 1363 speaker in the Open message for this session. 1365 If pcePcepSessState is tcpPending then this is the session 1366 ID that will be used in the Open message. Otherwise, this 1367 is the session ID that was sent in the Open message." 1368 ::= { pcePcepSessEntry 5 } 1370 pcePcepSessRemoteID OBJECT-TYPE 1371 SYNTAX Unsigned32 (0..255) 1372 MAX-ACCESS read-only 1373 STATUS current 1374 DESCRIPTION 1375 "The value of the PCEP session ID used by the peer in its 1376 Open message for this session. 1378 If pcePcepSessState is tcpPending or openWait then this 1379 field is not used and MUST be set to zero." 1380 ::= { pcePcepSessEntry 6 } 1382 pcePcepSessKeepaliveTimer OBJECT-TYPE 1383 SYNTAX Unsigned32 (0..255) 1384 UNITS "seconds" 1385 MAX-ACCESS read-only 1386 STATUS current 1387 DESCRIPTION 1388 "The agreed maximum interval at which the local PCEP speaker 1389 transmits PCEP messages on this PCEP session. Zero means 1390 that the local PCEP speaker never sends Keepalives on this 1391 session. 1393 This field is used if and only if pcePcepSessState is 1394 sessionUp. Otherwise, it is not used and MUST be set to 1395 zero." 1396 ::= { pcePcepSessEntry 7 } 1398 pcePcepSessPeerKeepaliveTimer OBJECT-TYPE 1399 SYNTAX Unsigned32 (0..255) 1400 UNITS "seconds" 1401 MAX-ACCESS read-only 1402 STATUS current 1403 DESCRIPTION 1404 "The agreed maximum interval at which the peer transmits PCEP 1405 messages on this PCEP session. Zero means that the peer 1406 never sends Keepalives on this session. 1408 This field is used if and only if pcePcepSessState is 1409 sessionUp. Otherwise, it is not used and MUST be set to 1410 zero." 1411 ::= { pcePcepSessEntry 8 } 1413 pcePcepSessDeadTimer OBJECT-TYPE 1414 SYNTAX Unsigned32 (0..255) 1415 UNITS "seconds" 1416 MAX-ACCESS read-only 1417 STATUS current 1418 DESCRIPTION 1419 "The DeadTimer interval for this PCEP session." 1420 ::= { pcePcepSessEntry 9 } 1422 pcePcepSessPeerDeadTimer OBJECT-TYPE 1423 SYNTAX Unsigned32 (0..255) 1424 UNITS "seconds" 1425 MAX-ACCESS read-only 1426 STATUS current 1427 DESCRIPTION 1428 "The peer's DeadTimer interval for this PCEP session. 1430 If pcePcepSessState is tcpPending or openWait then this 1431 field is not used and MUST be set to zero." 1432 ::= { pcePcepSessEntry 10 } 1434 pcePcepSessKAHoldTimeRem OBJECT-TYPE 1435 SYNTAX Unsigned32 (0..255) 1436 UNITS "seconds" 1437 MAX-ACCESS read-only 1438 STATUS current 1439 DESCRIPTION 1440 "The keep alive hold time remaining for this session. 1442 If pcePcepSessState is tcpPending or openWait then this 1443 field is not used and MUST be set to zero." 1444 ::= { pcePcepSessEntry 11 } 1446 pcePcepSessOverloaded OBJECT-TYPE 1447 SYNTAX TruthValue 1448 MAX-ACCESS read-only 1449 STATUS current 1450 DESCRIPTION 1451 "If the local PCEP speaker has informed the peer that it is 1452 currently overloaded, then this is set to true. Otherwise, 1453 it is set to false." 1454 ::= { pcePcepSessEntry 12 } 1456 pcePcepSessOverloadTime OBJECT-TYPE 1457 SYNTAX Unsigned32 1458 UNITS "seconds" 1459 MAX-ACCESS read-only 1460 STATUS current 1461 DESCRIPTION 1462 "The interval of time until the local PCEP speaker will cease 1463 to be overloaded on this session. 1465 This field is only used if pcePcepSessOverloaded is set to 1466 true. Otherwise, it is not used and MUST be set to zero." 1467 ::= { pcePcepSessEntry 13 } 1469 pcePcepSessPeerOverloaded OBJECT-TYPE 1470 SYNTAX TruthValue 1471 MAX-ACCESS read-only 1472 STATUS current 1473 DESCRIPTION 1474 "If the peer has informed the local PCEP speaker that it is 1475 currently overloaded, then this is set to true. Otherwise, 1476 it is set to false." 1477 ::= { pcePcepSessEntry 14 } 1479 pcePcepSessPeerOverloadTime OBJECT-TYPE 1480 SYNTAX Unsigned32 1481 UNITS "seconds" 1482 MAX-ACCESS read-only 1483 STATUS current 1484 DESCRIPTION 1485 "The interval of time until the peer will cease to be 1486 overloaded. If it is not known how long the peer will stay 1487 in overloaded state, this field is set to zero. 1489 This field is only used if pcePcepSessPeerOverloaded is set 1490 to true. Otherwise, it is not used and MUST be set to 1491 zero." 1492 ::= { pcePcepSessEntry 15 } 1494 pcePcepSessDiscontinuityTime OBJECT-TYPE 1495 SYNTAX TimeStamp 1496 MAX-ACCESS read-only 1497 STATUS current 1498 DESCRIPTION 1499 "The value of sysUpTime at the time that the statistics in 1500 this row were last reset." 1501 ::= { pcePcepSessEntry 16 } 1503 pcePcepSessAvgRspTime OBJECT-TYPE 1504 SYNTAX Unsigned32 1505 UNITS "milliseconds" 1506 MAX-ACCESS read-only 1507 STATUS current 1508 DESCRIPTION 1509 "The average response time for this peer on this session. 1511 If an average response time has not been calculated for this 1512 peer then this object has the value zero." 1513 ::= { pcePcepSessEntry 17 } 1515 pcePcepSessLWMRspTime OBJECT-TYPE 1516 SYNTAX Unsigned32 1517 UNITS "milliseconds" 1518 MAX-ACCESS read-only 1519 STATUS current 1520 DESCRIPTION 1521 "The smallest (low-water mark) response time seen from this 1522 peer on this session. 1524 If no responses have been received from this peer then this 1525 object has the value zero." 1526 ::= { pcePcepSessEntry 18 } 1528 pcePcepSessHWMRspTime OBJECT-TYPE 1529 SYNTAX Unsigned32 1530 UNITS "milliseconds" 1531 MAX-ACCESS read-only 1532 STATUS current 1533 DESCRIPTION 1534 "The greatest (high-water mark) response time seen from this 1535 peer on this session. 1537 If no responses have been received from this peer then this 1538 object has the value zero." 1539 ::= { pcePcepSessEntry 19 } 1541 pcePcepSessNumPCReqSent OBJECT-TYPE 1542 SYNTAX Counter32 1543 MAX-ACCESS read-only 1544 STATUS current 1545 DESCRIPTION 1546 "The number of PCReq messages sent on this session." 1547 ::= { pcePcepSessEntry 20 } 1549 pcePcepSessNumPCReqRcvd OBJECT-TYPE 1550 SYNTAX Counter32 1551 MAX-ACCESS read-only 1552 STATUS current 1553 DESCRIPTION 1554 "The number of PCReq messages received on this session." 1555 ::= { pcePcepSessEntry 21 } 1557 pcePcepSessNumPCRepSent OBJECT-TYPE 1558 SYNTAX Counter32 1559 MAX-ACCESS read-only 1560 STATUS current 1561 DESCRIPTION 1562 "The number of PCRep messages sent on this session." 1563 ::= { pcePcepSessEntry 22 } 1565 pcePcepSessNumPCRepRcvd OBJECT-TYPE 1566 SYNTAX Counter32 1567 MAX-ACCESS read-only 1568 STATUS current 1569 DESCRIPTION 1570 "The number of PCRep messages received on this session." 1571 ::= { pcePcepSessEntry 23 } 1573 pcePcepSessNumPCErrSent OBJECT-TYPE 1574 SYNTAX Counter32 1575 MAX-ACCESS read-only 1576 STATUS current 1577 DESCRIPTION 1578 "The number of PCErr messages sent on this session." 1579 ::= { pcePcepSessEntry 24 } 1581 pcePcepSessNumPCErrRcvd OBJECT-TYPE 1582 SYNTAX Counter32 1583 MAX-ACCESS read-only 1584 STATUS current 1585 DESCRIPTION 1586 "The number of PCErr messages received on this session." 1587 ::= { pcePcepSessEntry 25 } 1589 pcePcepSessNumPCNtfSent OBJECT-TYPE 1590 SYNTAX Counter32 1591 MAX-ACCESS read-only 1592 STATUS current 1593 DESCRIPTION 1594 "The number of PCNtf messages sent on this session." 1595 ::= { pcePcepSessEntry 26 } 1597 pcePcepSessNumPCNtfRcvd OBJECT-TYPE 1598 SYNTAX Counter32 1599 MAX-ACCESS read-only 1600 STATUS current 1601 DESCRIPTION 1602 "The number of PCNtf messages received on this session." 1603 ::= { pcePcepSessEntry 27 } 1605 pcePcepSessNumKeepaliveSent OBJECT-TYPE 1606 SYNTAX Counter32 1607 MAX-ACCESS read-only 1608 STATUS current 1609 DESCRIPTION 1610 "The number of Keepalive messages sent on this session." 1611 ::= { pcePcepSessEntry 28 } 1613 pcePcepSessNumKeepaliveRcvd OBJECT-TYPE 1614 SYNTAX Counter32 1615 MAX-ACCESS read-only 1616 STATUS current 1617 DESCRIPTION 1618 "The number of Keepalive messages received on this session." 1619 ::= { pcePcepSessEntry 29 } 1621 pcePcepSessNumUnknownRcvd OBJECT-TYPE 1622 SYNTAX Counter32 1623 MAX-ACCESS read-only 1624 STATUS current 1625 DESCRIPTION 1626 "The number of unknown messages received on this session." 1627 ::= { pcePcepSessEntry 30 } 1629 pcePcepSessNumReqSent OBJECT-TYPE 1630 SYNTAX Counter32 1631 MAX-ACCESS read-only 1632 STATUS current 1633 DESCRIPTION 1634 "The number of requests sent on this session. A request 1635 corresponds 1:1 with an RP object in a PCReq message. 1637 This might be greater than pcePcepSessNumPCReqSent because 1638 multiple requests can be batched into a single PCReq 1639 message." 1640 ::= { pcePcepSessEntry 31 } 1642 pcePcepSessNumSvecSent OBJECT-TYPE 1643 SYNTAX Counter32 1644 MAX-ACCESS read-only 1645 STATUS current 1646 DESCRIPTION 1647 "The number of SVEC objects sent on this session in PCReq 1648 messages. An SVEC object represents a set of synchronized 1649 requests." 1650 ::= { pcePcepSessEntry 32 } 1652 pcePcepSessNumSvecReqSent OBJECT-TYPE 1653 SYNTAX Counter32 1654 MAX-ACCESS read-only 1655 STATUS current 1656 DESCRIPTION 1657 "The number of requests sent on this session that appeared in 1658 one or more SVEC objects." 1659 ::= { pcePcepSessEntry 33 } 1661 pcePcepSessNumReqSentPendRep OBJECT-TYPE 1662 SYNTAX Counter32 1663 MAX-ACCESS read-only 1664 STATUS current 1665 DESCRIPTION 1666 "The number of requests that have been sent on this session 1667 for which a response is still pending." 1668 ::= { pcePcepSessEntry 34 } 1670 pcePcepSessNumReqSentEroRcvd OBJECT-TYPE 1671 SYNTAX Counter32 1672 MAX-ACCESS read-only 1673 STATUS current 1674 DESCRIPTION 1675 "The number of successful responses received on this session. 1676 A response corresponds 1:1 with an RP object in a PCRep 1677 message. A successful response is a response for which an 1678 ERO was successfully computed." 1679 ::= { pcePcepSessEntry 35 } 1681 pcePcepSessNumReqSentNoPathRcvd OBJECT-TYPE 1682 SYNTAX Counter32 1683 MAX-ACCESS read-only 1684 STATUS current 1685 DESCRIPTION 1686 "The number of unsuccessful responses received on this 1687 session. A response corresponds 1:1 with an RP object in a 1688 PCRep message. An unsuccessful response is a response with 1689 a NO-PATH object." 1690 ::= { pcePcepSessEntry 36 } 1692 pcePcepSessNumReqSentCancelRcvd OBJECT-TYPE 1693 SYNTAX Counter32 1694 MAX-ACCESS read-only 1695 STATUS current 1696 DESCRIPTION 1697 "The number of requests sent on this session that were 1698 cancelled by the peer with a PCNtf message. 1700 This might be different than pcePcepSessNumPCNtfRcvd because 1701 not all PCNtf messages are used to cancel requests, and a 1702 single PCNtf message can cancel multiple requests." 1703 ::= { pcePcepSessEntry 37 } 1705 pcePcepSessNumReqSentErrorRcvd OBJECT-TYPE 1706 SYNTAX Counter32 1707 MAX-ACCESS read-only 1708 STATUS current 1709 DESCRIPTION 1710 "The number of requests sent on this session that were 1711 rejected by the peer with a PCErr message. 1713 This might be different than pcePcepSessNumPCErrRcvd because 1714 not all PCErr messages are used to reject requests, and a 1715 single PCErr message can reject multiple requests." 1716 ::= { pcePcepSessEntry 38 } 1718 pcePcepSessNumReqSentTimeout OBJECT-TYPE 1719 SYNTAX Counter32 1720 MAX-ACCESS read-only 1721 STATUS current 1722 DESCRIPTION 1723 "The number of requests sent on this session that have been 1724 sent to a peer and have been abandoned because the peer has 1725 taken too long to respond to them." 1726 ::= { pcePcepSessEntry 39 } 1728 pcePcepSessNumReqSentCancelSent OBJECT-TYPE 1729 SYNTAX Counter32 1730 MAX-ACCESS read-only 1731 STATUS current 1732 DESCRIPTION 1733 "The number of requests sent on this session that were sent 1734 to the peer and explicitly canceled by the local PCEP 1735 speaker sending a PCNtf." 1736 ::= { pcePcepSessEntry 40 } 1738 pcePcepSessNumReqRcvd OBJECT-TYPE 1739 SYNTAX Counter32 1740 MAX-ACCESS read-only 1741 STATUS current 1742 DESCRIPTION 1743 "The number of requests received on this session. A request 1744 corresponds 1:1 with an RP object in a PCReq message. 1746 This might be greater than pcePcepSessNumPCReqRcvd because 1747 multiple requests can be batched into a single PCReq 1748 message." 1749 ::= { pcePcepSessEntry 41 } 1751 pcePcepSessNumSvecRcvd OBJECT-TYPE 1752 SYNTAX Counter32 1753 MAX-ACCESS read-only 1754 STATUS current 1755 DESCRIPTION 1756 "The number of SVEC objects received on this session in PCReq 1757 messages. An SVEC object represents a set of synchronized 1758 requests." 1760 ::= { pcePcepSessEntry 42 } 1762 pcePcepSessNumSvecReqRcvd OBJECT-TYPE 1763 SYNTAX Counter32 1764 MAX-ACCESS read-only 1765 STATUS current 1766 DESCRIPTION 1767 "The number of requests received on this session that 1768 appeared in one or more SVEC objects." 1769 ::= { pcePcepSessEntry 43 } 1771 pcePcepSessNumReqRcvdPendRep OBJECT-TYPE 1772 SYNTAX Counter32 1773 MAX-ACCESS read-only 1774 STATUS current 1775 DESCRIPTION 1776 "The number of requests that have been received on this 1777 session for which a response is still pending." 1778 ::= { pcePcepSessEntry 44 } 1780 pcePcepSessNumReqRcvdEroSent OBJECT-TYPE 1781 SYNTAX Counter32 1782 MAX-ACCESS read-only 1783 STATUS current 1784 DESCRIPTION 1785 "The number of successful responses sent on this session. A 1786 response corresponds 1:1 with an RP object in a PCRep 1787 message. A successful response is a response for which an 1788 ERO was successfully computed." 1789 ::= { pcePcepSessEntry 45 } 1791 pcePcepSessNumReqRcvdNoPathSent OBJECT-TYPE 1792 SYNTAX Counter32 1793 MAX-ACCESS read-only 1794 STATUS current 1795 DESCRIPTION 1796 "The number of unsuccessful responses sent on this session. 1797 A response corresponds 1:1 with an RP object in a PCRep 1798 message. An unsuccessful response is a response with a 1799 NO-PATH object." 1800 ::= { pcePcepSessEntry 46 } 1802 pcePcepSessNumReqRcvdCancelSent OBJECT-TYPE 1803 SYNTAX Counter32 1804 MAX-ACCESS read-only 1805 STATUS current 1806 DESCRIPTION 1807 "The number of requests received on this session that were 1808 cancelled by the local PCEP speaker sending a PCNtf message. 1810 This might be different than pcePcepSessNumPCNtfSent because 1811 not all PCNtf messages are used to cancel requests, and a 1812 single PCNtf message can cancel multiple requests." 1813 ::= { pcePcepSessEntry 47 } 1815 pcePcepSessNumReqRcvdErrorSent OBJECT-TYPE 1816 SYNTAX Counter32 1817 MAX-ACCESS read-only 1818 STATUS current 1819 DESCRIPTION 1820 "The number of requests received on this session that were 1821 rejected by the local PCEP speaker sending a PCErr message. 1823 This might be different than pcePcepSessNumPCErrSent because 1824 not all PCErr messages are used to reject requests, and a 1825 single PCErr message can reject multiple requests." 1826 ::= { pcePcepSessEntry 48 } 1828 pcePcepSessNumReqRcvdCancelRcvd OBJECT-TYPE 1829 SYNTAX Counter32 1830 MAX-ACCESS read-only 1831 STATUS current 1832 DESCRIPTION 1833 "The number of requests that were received on this session 1834 and explicitly canceled by the peer sending a PCNtf." 1835 ::= { pcePcepSessEntry 49 } 1837 pcePcepSessNumRepRcvdUnknown OBJECT-TYPE 1838 SYNTAX Counter32 1839 MAX-ACCESS read-only 1840 STATUS current 1841 DESCRIPTION 1842 "The number of responses to unknown requests received on this 1843 session. A response to an unknown request is a response 1844 whose RP object does not contain the request ID of any 1845 request that is currently outstanding on the session." 1846 ::= { pcePcepSessEntry 50 } 1848 pcePcepSessNumReqRcvdUnknown OBJECT-TYPE 1849 SYNTAX Counter32 1850 MAX-ACCESS read-only 1851 STATUS current 1852 DESCRIPTION 1853 "The number of unknown requests that have been received on 1854 this session. An unknown request is a request whose RP 1855 object contains a request ID of zero." 1857 ::= { pcePcepSessEntry 51 } 1859 --- 1860 --- Notifications 1861 --- 1863 pcePcepSessUp NOTIFICATION-TYPE 1864 OBJECTS { 1865 pcePcepSessState, 1866 pcePcepSessStateLastChange 1867 } 1868 STATUS current 1869 DESCRIPTION 1870 "This notification is sent when the value of 1871 'pcePcepSessState' enters the 'sessionUp' state." 1872 ::= { pcePcepNotifications 1 } 1874 pcePcepSessDown NOTIFICATION-TYPE 1875 OBJECTS { 1876 pcePcepSessState, 1877 pcePcepSessStateLastChange 1878 } 1879 STATUS current 1880 DESCRIPTION 1881 "This notification is sent when the value of 1882 'pcePcepSessState' leaves the 'sessionUp' state." 1883 ::= { pcePcepNotifications 2 } 1885 pcePcepSessLocalOverload NOTIFICATION-TYPE 1886 OBJECTS { 1887 pcePcepSessOverloaded, 1888 pcePcepSessOverloadTime 1889 } 1890 STATUS current 1891 DESCRIPTION 1892 "This notification is sent when the local PCEP speaker enters 1893 overload state for a peer." 1894 ::= { pcePcepNotifications 3 } 1896 pcePcepSessLocalOverloadClear NOTIFICATION-TYPE 1897 OBJECTS { 1898 pcePcepSessOverloaded 1899 } 1900 STATUS current 1901 DESCRIPTION 1902 "This notification is sent when the local PCEP speaker leaves 1903 overload state for a peer." 1904 ::= { pcePcepNotifications 4 } 1906 pcePcepSessPeerOverload NOTIFICATION-TYPE 1907 OBJECTS { 1908 pcePcepSessPeerOverloaded, 1909 pcePcepSessPeerOverloadTime 1910 } 1911 STATUS current 1912 DESCRIPTION 1913 "This notification is sent when a peer enters overload 1914 state." 1915 ::= { pcePcepNotifications 5 } 1917 pcePcepSessPeerOverloadClear NOTIFICATION-TYPE 1918 OBJECTS { 1919 pcePcepSessPeerOverloaded 1920 } 1921 STATUS current 1922 DESCRIPTION 1923 "This notification is sent when a peer leaves overload 1924 state." 1925 ::= { pcePcepNotifications 6 } 1927 -- 1928 -- Module Conformance Statement 1929 -- 1931 pcePcepCompliances 1932 OBJECT IDENTIFIER ::= { pcePcepConformance 1 } 1934 pcePcepGroups 1935 OBJECT IDENTIFIER ::= { pcePcepConformance 2 } 1937 -- 1938 -- Read-Only Compliance 1939 -- 1941 pcePcepModuleReadOnlyCompliance MODULE-COMPLIANCE 1942 STATUS current 1943 DESCRIPTION 1944 "The Module is implemented with support for read-only. In 1945 other words, only monitoring is available by implementing 1946 this MODULE-COMPLIANCE." 1948 MODULE -- this module 1949 MANDATORY-GROUPS { 1950 pcePcepGeneralGroup, 1951 pcePcepNotificationsGroup 1952 } 1953 ::= { pcePcepCompliances 1 } 1955 -- units of conformance 1957 pcePcepGeneralGroup OBJECT-GROUP 1958 OBJECTS { pcePcepEntityAdminStatus, 1959 pcePcepEntityOperStatus, 1960 pcePcepEntityAddrType, 1961 pcePcepEntityAddr, 1962 pcePcepEntityConnectTimer, 1963 pcePcepEntityConnectMaxRetry, 1964 pcePcepEntityOpenWaitTimer, 1965 pcePcepEntityKeepWaitTimer, 1966 pcePcepEntityKeepAliveTimer, 1967 pcePcepEntityDeadTimer, 1968 pcePcepEntityMaxKeepAliveTimer, 1969 pcePcepEntityMaxDeadTimer, 1970 pcePcepEntityAllowNegotiation, 1971 pcePcepEntityMinKeepAliveTimer, 1972 pcePcepEntityMinDeadTimer, 1973 pcePcepEntitySyncTimer, 1974 pcePcepEntityRequestTimer, 1975 pcePcepEntityInitBackoffTimer, 1976 pcePcepEntityMaxBackoffTimer, 1977 pcePcepEntityMaxSessions, 1978 pcePcepEntityMaxUnknownReqs, 1979 pcePcepEntityMaxUnknownMsgs, 1980 pcePcepPeerRole, 1981 pcePcepPeerDiscontinuityTime, 1982 pcePcepPeerInitiateSession, 1983 pcePcepPeerSessionExists, 1984 pcePcepPeerNumSessSetupOK, 1985 pcePcepPeerNumSessSetupFail, 1986 pcePcepPeerSessionUpTime, 1987 pcePcepPeerSessionFailTime, 1988 pcePcepPeerAvgRspTime, 1989 pcePcepPeerLWMRspTime, 1990 pcePcepPeerHWMRspTime, 1991 pcePcepPeerNumPCReqSent, 1992 pcePcepPeerNumPCReqRcvd, 1993 pcePcepPeerNumPCRepSent, 1994 pcePcepPeerNumPCRepRcvd, 1995 pcePcepPeerNumPCErrSent, 1996 pcePcepPeerNumPCErrRcvd, 1997 pcePcepPeerNumPCNtfSent, 1998 pcePcepPeerNumPCNtfRcvd, 1999 pcePcepPeerNumKeepaliveSent, 2000 pcePcepPeerNumKeepaliveRcvd, 2001 pcePcepPeerNumUnknownRcvd, 2002 pcePcepPeerNumReqSent, 2003 pcePcepPeerNumSvecSent, 2004 pcePcepPeerNumSvecReqSent, 2005 pcePcepPeerNumReqSentPendRep, 2006 pcePcepPeerNumReqSentEroRcvd, 2007 pcePcepPeerNumReqSentNoPathRcvd, 2008 pcePcepPeerNumReqSentCancelRcvd, 2009 pcePcepPeerNumReqSentErrorRcvd, 2010 pcePcepPeerNumReqSentTimeout, 2011 pcePcepPeerNumReqSentCancelSent, 2012 pcePcepPeerNumReqSentClosed, 2013 pcePcepPeerNumReqRcvd, 2014 pcePcepPeerNumSvecRcvd, 2015 pcePcepPeerNumSvecReqRcvd, 2016 pcePcepPeerNumReqRcvdPendRep, 2017 pcePcepPeerNumReqRcvdEroSent, 2018 pcePcepPeerNumReqRcvdNoPathSent, 2019 pcePcepPeerNumReqRcvdCancelSent, 2020 pcePcepPeerNumReqRcvdErrorSent, 2021 pcePcepPeerNumReqRcvdCancelRcvd, 2022 pcePcepPeerNumReqRcvdClosed, 2023 pcePcepPeerNumRepRcvdUnknown, 2024 pcePcepPeerNumReqRcvdUnknown, 2025 pcePcepSessStateLastChange, 2026 pcePcepSessState, 2027 pcePcepSessConnectRetry, 2028 pcePcepSessLocalID, 2029 pcePcepSessRemoteID, 2030 pcePcepSessKeepaliveTimer, 2031 pcePcepSessPeerKeepaliveTimer, 2032 pcePcepSessDeadTimer, 2033 pcePcepSessPeerDeadTimer, 2034 pcePcepSessKAHoldTimeRem, 2035 pcePcepSessOverloaded, 2036 pcePcepSessOverloadTime, 2037 pcePcepSessPeerOverloaded, 2038 pcePcepSessPeerOverloadTime, 2039 pcePcepSessDiscontinuityTime, 2040 pcePcepSessAvgRspTime, 2041 pcePcepSessLWMRspTime, 2042 pcePcepSessHWMRspTime, 2043 pcePcepSessNumPCReqSent, 2044 pcePcepSessNumPCReqRcvd, 2045 pcePcepSessNumPCRepSent, 2046 pcePcepSessNumPCRepRcvd, 2047 pcePcepSessNumPCErrSent, 2048 pcePcepSessNumPCErrRcvd, 2049 pcePcepSessNumPCNtfSent, 2050 pcePcepSessNumPCNtfRcvd, 2051 pcePcepSessNumKeepaliveSent, 2052 pcePcepSessNumKeepaliveRcvd, 2053 pcePcepSessNumUnknownRcvd, 2054 pcePcepSessNumReqSent, 2055 pcePcepSessNumSvecSent, 2056 pcePcepSessNumSvecReqSent, 2057 pcePcepSessNumReqSentPendRep, 2058 pcePcepSessNumReqSentEroRcvd, 2059 pcePcepSessNumReqSentNoPathRcvd, 2060 pcePcepSessNumReqSentCancelRcvd, 2061 pcePcepSessNumReqSentErrorRcvd, 2062 pcePcepSessNumReqSentTimeout, 2063 pcePcepSessNumReqSentCancelSent, 2064 pcePcepSessNumReqRcvd, 2065 pcePcepSessNumSvecRcvd, 2066 pcePcepSessNumSvecReqRcvd, 2067 pcePcepSessNumReqRcvdPendRep, 2068 pcePcepSessNumReqRcvdEroSent, 2069 pcePcepSessNumReqRcvdNoPathSent, 2070 pcePcepSessNumReqRcvdCancelSent, 2071 pcePcepSessNumReqRcvdErrorSent, 2072 pcePcepSessNumReqRcvdCancelRcvd, 2073 pcePcepSessNumRepRcvdUnknown, 2074 pcePcepSessNumReqRcvdUnknown 2075 } 2076 STATUS current 2077 DESCRIPTION 2078 "Objects that apply to all PCEP MIB implementations." 2079 ::= { pcePcepGroups 1 } 2081 pcePcepNotificationsGroup NOTIFICATION-GROUP 2082 NOTIFICATIONS { pcePcepSessUp, 2083 pcePcepSessDown, 2084 pcePcepSessLocalOverload, 2085 pcePcepSessLocalOverloadClear, 2086 pcePcepSessPeerOverload, 2087 pcePcepSessPeerOverloadClear 2088 } 2089 STATUS current 2090 DESCRIPTION 2091 "The notifications for a PCEP MIB implementation." 2092 ::= { pcePcepGroups 2 } 2094 END 2096 6. Security Considerations 2098 The readable objects in the PCE-PCEP-MIB module (i.e., those with 2099 MAX-ACCESS other than not-accessible) may be considered sensitive in 2100 some environments since, collectively, they provide information about 2101 the amount and frequency of path computation requests and responses 2102 within the network and can reveal some aspects of their 2103 configuration. 2105 In such environments it is important to control also GET and NOTIFY 2106 access to these objects and possibly even to encrypt their values 2107 when sending them over the network via SNMP. 2109 SNMP versions prior to SNMPv3 did not include adequate security. 2110 Even if the network itself is secure (for example by using IPsec), 2111 even then, there is no control as to who on the secure network is 2112 allowed to access and GET/SET (read/change/create/delete) the objects 2113 in this MIB module. 2115 It is RECOMMENDED that implementers consider the security features as 2116 provided by the SNMPv3 framework (see [RFC3410], section 8), 2117 including full support for the SNMPv3 cryptographic mechanisms (for 2118 authentication and privacy). 2120 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2121 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2122 enable cryptographic security. It is then a customer/operator 2123 responsibility to ensure that the SNMP entity giving access to an 2124 instance of this MIB module is properly configured to give access to 2125 the objects only to those principals (users) that have legitimate 2126 rights to indeed GET or SET (change/create/delete) them. 2128 7. IANA Considerations 2130 The MIB module in this document uses the following IANA-assigned 2131 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 2133 Descriptor OBJECT IDENTIFIER value 2134 ---------- ----------------------- 2135 pcePcepMIB { mib-2 XXX } 2137 Editor's Note (to be removed prior to publication): the IANA is 2138 requested to assign a value for "XXX" under the 'mib-2' subtree and 2139 to record the assignment in the SMI Numbers registry. When the 2140 assignment has been made, the RFC Editor is asked to replace "XXX" 2141 (here and in the MIB module) with the assigned value and to remove 2142 this note. 2144 8. Contributors 2146 Thanks to Dhruv Dhody for his contribution and detailed review. 2148 9. References 2150 9.1. Normative References 2152 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2153 Requirement Levels", BCP 14, RFC 2119, March 1997. 2155 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2156 Schoenwaelder, Ed., "Structure of Management Information 2157 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2159 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2160 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2161 STD 58, RFC 2579, April 1999. 2163 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2164 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2165 April 1999. 2167 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2168 Schoenwaelder, "Textual Conventions for Internet Network 2169 Addresses", RFC 4001, February 2005. 2171 [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation 2172 Element (PCE)-Based Architecture", RFC 4655, August 2006. 2174 [RFC5440] Vasseur, JP. and JL. Le Roux, "Path Computation Element 2175 (PCE) Communication Protocol (PCEP)", RFC 5440, 2176 March 2009. 2178 9.2. Normative References 2180 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2181 "Introduction and Applicability Statements for Internet- 2182 Standard Management Framework", RFC 3410, December 2002. 2184 Appendix A. Acknowledgement 2186 The authors would like to thank Santanu Mazumder and Meral 2187 Shirazipour for their valuable input. 2189 Funding for the RFC Editor function is currently provided by the 2190 Internet Society. 2192 Authors' Addresses 2194 A S Kiran Koushik 2195 Cisco Systems, Inc. 2197 EMail: kkoushik@cisco.com 2199 Emile Stephan 2200 France Telecom 2201 2 avenue Pierre Marzin 2202 Lannion F-22307 2203 France 2205 EMail: emile.stephan@orange.com 2207 Quintin Zhao 2208 Huawei Technology 2209 125 Nagog Technology Park 2210 Acton, MA 01719 2211 US 2213 EMail: qzhao@huawei.com 2215 Daniel King 2216 Old Dog Consulting 2217 UK 2219 EMail: daniel@olddog.co.uk 2221 Jonathan Hardwick 2222 Metaswitch 2223 100 Church Street 2224 Enfield EN2 6BQ 2225 UK 2227 EMail: jonathan.hardwick@metaswitch.com