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