idnits 2.17.1 draft-ietf-pce-pcep-mib-09.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 lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (July 25, 2014) is 3563 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) No issues found here. Summary: 0 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: January 26, 2015 Orange 6 Q. Zhao 7 Huawei Technology 8 D. King 9 Old Dog Consulting 10 J. Hardwick 11 Metaswitch 12 July 25, 2014 14 Path Computation Element Protocol (PCEP) Management Information Base 15 draft-ietf-pce-pcep-mib-09 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 January 26, 2015. 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 . . . . . . . . . . . . . . . . . . . . . . . . 2 61 2. The Internet-Standard Management Framework . . . . . . . . . 3 62 3. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 63 4. PCEP MIB Module Architecture . . . . . . . . . . . . . . . . 3 64 4.1. pcePcepEntityTable . . . . . . . . . . . . . . . . . . . 3 65 4.2. pcePcepPeerTable . . . . . . . . . . . . . . . . . . . . 4 66 4.3. pcePcepSessTable . . . . . . . . . . . . . . . . . . . . 4 67 4.4. PCEP Notifications . . . . . . . . . . . . . . . . . . . 4 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 . . . . . . . . . . . . . . . . . . . 44 72 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 45 73 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 45 74 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 45 75 9.1. Normative References . . . . . . . . . . . . . . . . . . 45 76 9.2. Informative References . . . . . . . . . . . . . . . . . 46 77 Appendix A. Acknowledgement . . . . . . . . . . . . . . . . . . 47 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", "NOT RECOMMENDED", "MAY" and 122 "OPTIONAL" in this document are to be interpreted as described in BCP 123 14, RFC 2119 [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 159 pcePcepPeerTable if and only if no PCEP session exists to the 160 corresponding peer. 162 4.3. pcePcepSessTable 164 The pcePcepSessTable contains one row for each PCEP session that the 165 PCEP entity (PCE or PCC) is currently participating in. Each row is 166 read-only and contains the running configuration that is applied to 167 the session, plus identifiers and statistics for the session. 169 The statistics in pcePcepSessTable are semantically different from 170 those in pcePcepPeerTable since the former apply to the current 171 session only, whereas the latter are the aggregate for all sessions 172 that have existed to that peer. 174 Although [RFC5440] forbids there from being more than one active PCEP 175 session between a given pair of PCEP entities at any one time, there 176 is a window during session establishment where the 177 pcePcepSessTable may contain two rows for a given peer, one 178 representing a session initiated by the local PCEP speaker and one 179 representing a session initiated by the remote PCEP speaker. If 180 either of these sessions reaches active state, then the other is 181 discarded. 183 4.4. PCEP Notifications 185 The PCEP MIB contains notifications for the following conditions. 187 a. pcePcepSessUp: PCEP Session has gone up. 189 b. pcePcepSessDown: PCEP Session has gone down. 191 c. pcePcepSessLocalOverload: Local PCEP entity has sent an overload 192 PCNtf on this session. 194 d. pcePcepSessLocalOverloadClear: Local PCEP entity has sent an 195 overload-cleared PCNtf on this session. 197 e. pcePcepSessPeerOverload: Remote PCEP entity has sent an overload 198 PCNtf on this session. 200 f. pcePcepSessPeerOverloadClear: Remote PCEP entity has sent an 201 overload-cleared PCNtf on this session. 203 4.5. Relationship to other MIB modules 205 The PCEP MIB imports the following textual conventions from the INET- 206 ADDRESS-MIB defined in RFC 4001 [RFC4001]: 208 o InetAddressType 210 o InetAddress 212 PCEP relies on existing protocols which have specialized MIB objects 213 to monitor their own activities. Consequently this document 214 considers that the monitoring of underlying protocols is out of scope 215 of the PCEP MIB module. 217 5. Object Definitions 219 5.1. PCE-PCEP-MIB 221 PCE-PCEP-MIB DEFINITIONS ::= BEGIN 223 IMPORTS 224 MODULE-IDENTITY, 225 OBJECT-TYPE, 226 mib-2, 227 NOTIFICATION-TYPE, 228 Unsigned32, 229 Counter32 230 FROM SNMPv2-SMI -- RFC 2578 231 TruthValue, 232 TimeStamp 233 FROM SNMPv2-TC -- RFC 2579 234 MODULE-COMPLIANCE, 235 OBJECT-GROUP, 236 NOTIFICATION-GROUP 237 FROM SNMPv2-CONF -- RFC 2580 238 InetAddressType, 239 InetAddress 240 FROM INET-ADDRESS-MIB; -- RFC 4001 242 pcePcepMIB MODULE-IDENTITY 243 LAST-UPDATED 244 "201407251200Z" -- 25 July 2014 245 ORGANIZATION 246 "IETF Path Computation Element (PCE) Working Group" 247 CONTACT-INFO 248 "Email: pce@ietf.org 249 WG charter: 250 http://www.ietf.org/html.charters/pce-charter.html" 252 DESCRIPTION 253 "This MIB module defines a collection of objects for managing 254 PCE communication protocol (PCEP). 256 Copyright (C) The IETF Trust (2014). This version of this 257 MIB module is part of RFC YYYY; see the RFC itself for full 258 legal notices." 259 -- RFC Ed,: replace YYYY with actual RFC number & remove this note 260 REVISION 261 "201407251200Z" -- 25 July 2014 262 DESCRIPTION 263 "Initial version, published as RFC YYYY." 264 -- RFC Ed.: replace YYYY with actual RFC number & remove this note 265 ::= { mib-2 XXX } 266 -- RFC Ed.: replace XXX with IANA-assigned number & remove this note 268 pcePcepNotifications OBJECT IDENTIFIER ::= { pcePcepMIB 0 } 269 pcePcepObjects OBJECT IDENTIFIER ::= { pcePcepMIB 1 } 270 pcePcepConformance OBJECT IDENTIFIER ::= { pcePcepMIB 2 } 271 pcePcepEntityObjects OBJECT IDENTIFIER ::= { pcePcepObjects 1 } 273 -- 274 -- PCE Entity Objects 275 -- 277 pcePcepEntityTable OBJECT-TYPE 278 SYNTAX SEQUENCE OF PcePcepEntityEntry 279 MAX-ACCESS not-accessible 280 STATUS current 281 DESCRIPTION 282 "This table contains information about PCEP Entities." 283 ::= { pcePcepEntityObjects 1 } 285 pcePcepEntityEntry OBJECT-TYPE 286 SYNTAX PcePcepEntityEntry 287 MAX-ACCESS not-accessible 288 STATUS current 289 DESCRIPTION 290 "An entry in this table represents a PCEP entity." 291 INDEX { pcePcepEntityIndex } 292 ::= { pcePcepEntityTable 1 } 294 PcePcepEntityEntry ::= SEQUENCE { 295 pcePcepEntityIndex Unsigned32, 296 pcePcepEntityAdminStatus INTEGER, 297 pcePcepEntityOperStatus INTEGER, 298 pcePcepEntityAddrType InetAddressType, 299 pcePcepEntityAddr InetAddress, 300 pcePcepEntityConnectTimer Unsigned32, 301 pcePcepEntityConnectMaxRetry Unsigned32, 302 pcePcepEntityOpenWaitTimer Unsigned32, 303 pcePcepEntityKeepWaitTimer Unsigned32, 304 pcePcepEntityKeepAliveTimer Unsigned32, 305 pcePcepEntityDeadTimer Unsigned32, 306 pcePcepEntityMaxKeepAliveTimer Unsigned32, 307 pcePcepEntityMaxDeadTimer Unsigned32, 308 pcePcepEntityAllowNegotiation TruthValue, 309 pcePcepEntityMinKeepAliveTimer Unsigned32, 310 pcePcepEntityMinDeadTimer Unsigned32, 311 pcePcepEntitySyncTimer Unsigned32, 312 pcePcepEntityRequestTimer Unsigned32, 313 pcePcepEntityInitBackoffTimer Unsigned32, 314 pcePcepEntityMaxBackoffTimer Unsigned32, 315 pcePcepEntityMaxSessions Unsigned32, 316 pcePcepEntityMaxUnknownReqs Unsigned32, 317 pcePcepEntityMaxUnknownMsgs Unsigned32 318 } 320 pcePcepEntityIndex OBJECT-TYPE 321 SYNTAX Unsigned32 (1..2147483647) 322 MAX-ACCESS not-accessible 323 STATUS current 324 DESCRIPTION 325 "This index is used to uniquely identify the PCEP entity." 326 ::= { pcePcepEntityEntry 1 } 328 pcePcepEntityAdminStatus OBJECT-TYPE 329 SYNTAX INTEGER { 330 adminStatusUp(1), 331 adminStatusDown(2) 332 } 333 MAX-ACCESS read-only 334 STATUS current 335 DESCRIPTION 336 "The administrative status of this PCEP Entity." 337 ::= { pcePcepEntityEntry 2 } 339 pcePcepEntityOperStatus OBJECT-TYPE 340 SYNTAX INTEGER { 341 operStatusUp(1), 342 operStatusDown(2), 343 operStatusGoingUp(3), 344 operStatusGoingDown(4), 345 operStatusFailed(5), 346 operStatusFailedPerm(6) 347 } 348 MAX-ACCESS read-only 349 STATUS current 350 DESCRIPTION 351 "The operational status of the PCEP entity. Takes one of the 352 following values. 353 - operStatusUp(1): the PCEP entity is active. 354 - operStatusDown(2): the PCEP entity is inactive. 355 - operStatusGoingUp(3): the PCEP entity is activating. 356 - operStatusGoingDown(4): the PCEP entity is deactivating. 357 - operStatusFailed(5): the PCEP entity has failed and will 358 recover when possible. 359 - operStatusFailedPerm(6): the PCEP entity has failed and 360 will not recover without operator intervention." 361 ::= { pcePcepEntityEntry 3 } 363 pcePcepEntityAddrType OBJECT-TYPE 364 SYNTAX InetAddressType 365 MAX-ACCESS read-only 366 STATUS current 367 DESCRIPTION 368 "The type of the PCEP entity's Internet address. This object 369 specifies how the value of the pcePcepEntityAddr object 370 should be interpreted." 371 ::= { pcePcepEntityEntry 4 } 373 pcePcepEntityAddr OBJECT-TYPE 374 SYNTAX InetAddress 375 MAX-ACCESS read-only 376 STATUS current 377 DESCRIPTION 378 "The local Internet address of this PCEP entity. The type is 379 given by pcePcepEntityAddrType. 381 If operating as a PCE server, the PCEP entity listens on 382 this address. If operating as a PCC, the PCEP entity binds 383 outgoing TCP connections to this address. 385 It is possible for the PCEP entity to operate both as a PCC 386 and a PCE Server, in which case it uses this address both to 387 listen for incoming TCP connections and to bind outgoing 388 TCP connections." 389 ::= { pcePcepEntityEntry 5 } 391 pcePcepEntityConnectTimer OBJECT-TYPE 392 SYNTAX Unsigned32 (1..65535) 393 UNITS "seconds" 394 MAX-ACCESS read-only 395 STATUS current 396 DESCRIPTION 397 "The time that the PCEP entity will wait to establish a TCP 398 connection with a PCEP peer. If a TCP connection is not 399 established within this time then PCEP aborts the session 400 setup attempt." 401 ::= { pcePcepEntityEntry 6 } 403 pcePcepEntityConnectMaxRetry OBJECT-TYPE 404 SYNTAX Unsigned32 405 MAX-ACCESS read-only 406 STATUS current 407 DESCRIPTION 408 "The maximum number of times the system tries to establish 409 a TCP connection to a peer before going back to the Idle 410 state." 411 ::= { pcePcepEntityEntry 7 } 413 pcePcepEntityOpenWaitTimer OBJECT-TYPE 414 SYNTAX Unsigned32 (1..65535) 415 UNITS "seconds" 416 MAX-ACCESS read-only 417 STATUS current 418 DESCRIPTION 419 "The time that the PCEP entity will wait to receive an Open 420 message from a PCEP peer. If no Open message is received 421 within this time then PCEP aborts the session setup 422 attempt." 423 ::= { pcePcepEntityEntry 8 } 425 pcePcepEntityKeepWaitTimer OBJECT-TYPE 426 SYNTAX Unsigned32 (1..65535) 427 UNITS "seconds" 428 MAX-ACCESS read-only 429 STATUS current 430 DESCRIPTION 431 "The time that the PCEP entity will wait to receive a 432 Keepalive or PCErr message from a PCEP peer during session 433 initialization. If no Keepalive or PCErr message is 434 received within this time then PCEP aborts the session setup 435 attempt." 436 ::= { pcePcepEntityEntry 9 } 438 pcePcepEntityKeepAliveTimer OBJECT-TYPE 439 SYNTAX Unsigned32 (0..255) 440 UNITS "seconds" 441 MAX-ACCESS read-only 442 STATUS current 443 DESCRIPTION 444 "The keep alive transmission timer that this PCEP entity will 445 propose in the initial OPEN message of each session it is 446 involved in. This is the maximum time between two 447 consecutive messages sent to a PCEP peer. Zero means that 448 the PCEP entity prefers not to send Keepalives at all. 450 Note that the actual Keepalive transmission intervals, in 451 either direction of an active PCEP session, are determined 452 by negotiation between the PCEP peers as specified by RFC 453 5440, and so may differ from this configured value. For 454 the actually negotiated values (per-session), see 455 pcePcepSessKeepaliveTimer and 456 pcePcepSessPeerKeepaliveTimer." 457 ::= { pcePcepEntityEntry 10 } 459 pcePcepEntityDeadTimer OBJECT-TYPE 460 SYNTAX Unsigned32 (0..255) 461 UNITS "seconds" 462 MAX-ACCESS read-only 463 STATUS current 464 DESCRIPTION 465 "The dead timer that this PCEP entity will propose in the 466 initial OPEN message of each session it is involved in. 467 This is the time after which a PCEP peer should declare a 468 session down if it does not receive any PCEP messages. 470 pcePcepEntityDeadTimer is recommended to be 4 times the 471 pcePcepEntityKeepAliveTimer value. Zero means suggesting 472 that the peer does not run a dead timer at all; it is only 473 allowed when pcePcepEntityKeepAliveTimer is also zero." 474 ::= { pcePcepEntityEntry 11 } 476 pcePcepEntityMaxKeepAliveTimer OBJECT-TYPE 477 SYNTAX Unsigned32 (0..255) 478 UNITS "seconds" 479 MAX-ACCESS read-only 480 STATUS current 481 DESCRIPTION 482 "The maximum value that this PCEP entity will accept from a 483 peer for the interval between Keepalive transmissions. Zero 484 means that the PCEP entity will allow no Keepalive 485 transmission at all." 486 ::= { pcePcepEntityEntry 12 } 488 pcePcepEntityMaxDeadTimer OBJECT-TYPE 489 SYNTAX Unsigned32 (0..255) 490 UNITS "seconds" 491 MAX-ACCESS read-only 492 STATUS current 493 DESCRIPTION 494 "The maximum value that this PCEP entity will accept from a 495 peer for the Dead timer. Zero means that the PCEP entity 496 will allow not running a Dead timer. 498 A Dead timer will not be accepted unless it is both greater 499 than the session Keepalive timer and less than this field." 500 ::= { pcePcepEntityEntry 13 } 502 pcePcepEntityAllowNegotiation OBJECT-TYPE 503 SYNTAX TruthValue 504 MAX-ACCESS read-only 505 STATUS current 506 DESCRIPTION 507 "Whether the PCEP entity will permit negotiation of session 508 parameters." 509 ::= { pcePcepEntityEntry 14 } 511 pcePcepEntityMinKeepAliveTimer OBJECT-TYPE 512 SYNTAX Unsigned32 (0..255) 513 UNITS "seconds" 514 MAX-ACCESS read-only 515 STATUS current 516 DESCRIPTION 517 "In PCEP session parameter negotiation, the minimum value 518 that this PCEP entity will accept for the interval between 519 Keepalive transmissions. Zero means that the PCEP entity 520 insists on no Keepalive transmission at all." 521 ::= { pcePcepEntityEntry 15 } 523 pcePcepEntityMinDeadTimer OBJECT-TYPE 524 SYNTAX Unsigned32 (0..255) 525 UNITS "seconds" 526 MAX-ACCESS read-only 527 STATUS current 528 DESCRIPTION 529 "In PCEP session parameter negotiation, the minimum value 530 that this PCEP entity will accept for the Dead timer. Zero 531 means that the PCEP entity insists on not running a Dead 532 timer. 534 A Dead timer will not be accepted unless it is both greater 535 than the session Keepalive timer and greater than this 536 field." 537 ::= { pcePcepEntityEntry 16 } 539 pcePcepEntitySyncTimer OBJECT-TYPE 540 SYNTAX Unsigned32 (1..65535) 541 UNITS "seconds" 542 MAX-ACCESS read-only 543 STATUS current 544 DESCRIPTION 545 "The value of SYNC timer is used in the case of synchronized 546 path computation request using the SVEC object. 548 Consider the case where a PCReq message is received by a PCE 549 that contains the SVEC object referring to M synchronized 550 path computation requests. If after the expiration of the 551 SYNC timer all the M path computation requests have not been 552 received, a protocol error is triggered and the PCE MUST 553 cancel the whole set of path computation requests. 555 The aim of the SyncTimer is to avoid the storage of unused 556 synchronized requests should one of them get lost for some 557 reasons (for example, a misbehaving PCC)." 558 ::= { pcePcepEntityEntry 17 } 560 pcePcepEntityRequestTimer OBJECT-TYPE 561 SYNTAX Unsigned32 (1..65535) 562 UNITS "seconds" 563 MAX-ACCESS read-only 564 STATUS current 565 DESCRIPTION 566 "The maximum time that the PCEP entity will wait for a 567 response to a PCReq message." 568 ::= { pcePcepEntityEntry 18 } 570 pcePcepEntityInitBackoffTimer OBJECT-TYPE 571 SYNTAX Unsigned32 (1..65535) 572 UNITS "seconds" 573 MAX-ACCESS read-only 574 STATUS current 575 DESCRIPTION 576 "The initial back-off time for retrying a failed session 577 setup attempt to a peer. 579 The back-off time increases for each failed session setup 580 attempt, until a maximum back-off time is reached. The 581 maximum back-off time is pcePcepEntityMaxBackoffTimer." 582 ::= { pcePcepEntityEntry 19 } 584 pcePcepEntityMaxBackoffTimer OBJECT-TYPE 585 SYNTAX Unsigned32 586 UNITS "seconds" 587 MAX-ACCESS read-only 588 STATUS current 589 DESCRIPTION 590 "The maximum back-off time for retrying a failed session 591 setup attempt to a peer. 593 The back-off time increases for each failed session setup 594 attempt, until this maximum value is reached. Session 595 setup attempts then repeat periodically without any 596 further increase in back-off time." 597 ::= { pcePcepEntityEntry 20 } 599 pcePcepEntityMaxSessions OBJECT-TYPE 600 SYNTAX Unsigned32 601 MAX-ACCESS read-only 602 STATUS current 603 DESCRIPTION 604 "Maximum number of sessions involving this PCEP entity 605 that can exist at any time." 606 ::= { pcePcepEntityEntry 21 } 608 pcePcepEntityMaxUnknownReqs OBJECT-TYPE 609 SYNTAX Unsigned32 610 MAX-ACCESS read-only 611 STATUS current 612 DESCRIPTION 613 "The maximum number of unrecognized requests and replies that 614 any session on this PCEP entity is willing to accept per 615 minute. 617 A PCRep message contains an unrecognized reply if it 618 contains an RP object whose request ID does not correspond 619 to any in-progress request sent by this PCEP entity. 621 A PCReq message contains an unrecognized request if it 622 contains an RP object whose request ID is zero." 624 ::= { pcePcepEntityEntry 22 } 626 pcePcepEntityMaxUnknownMsgs OBJECT-TYPE 627 SYNTAX Unsigned32 628 MAX-ACCESS read-only 629 STATUS current 630 DESCRIPTION 631 "The maximum number of unknown messages that any session 632 on this PCEP entity is willing to accept per minute." 633 ::= { pcePcepEntityEntry 23 } 635 -- 636 -- The PCEP Peer Table 637 -- 639 pcePcepPeerObjects OBJECT IDENTIFIER ::= { pcePcepObjects 2 } 641 pcePcepPeerTable OBJECT-TYPE 642 SYNTAX SEQUENCE OF PcePcepPeerEntry 643 MAX-ACCESS not-accessible 644 STATUS current 645 DESCRIPTION 646 "Information about PCEP peers known by the local PCEP 647 speaker. 649 This MIB table gives PCEP peer information that spans PCEP 650 sessions. Information about current PCEP sessions can be 651 found in the pcePcepSessTable MIB table." 652 ::= { pcePcepPeerObjects 1 } 654 pcePcepPeerEntry OBJECT-TYPE 655 SYNTAX PcePcepPeerEntry 656 MAX-ACCESS not-accessible 657 STATUS current 658 DESCRIPTION 659 "Information about a single PCEP peer which spans all PCEP 660 sessions to that peer. The information contained in a row 661 is read-only." 662 INDEX { pcePcepEntityIndex, 663 pcePcepPeerAddrType, 664 pcePcepPeerAddr } 665 ::= { pcePcepPeerTable 1 } 667 PcePcepPeerEntry ::= SEQUENCE { 668 pcePcepPeerAddrType InetAddressType, 669 pcePcepPeerAddr InetAddress, 670 pcePcepPeerRole INTEGER, 671 pcePcepPeerDiscontinuityTime TimeStamp, 672 pcePcepPeerInitiateSession TruthValue, 673 pcePcepPeerSessionExists TruthValue, 674 pcePcepPeerNumSessSetupOK Counter32, 675 pcePcepPeerNumSessSetupFail Counter32, 676 pcePcepPeerSessionUpTime TimeStamp, 677 pcePcepPeerSessionFailTime TimeStamp, 678 pcePcepPeerAvgRspTime Unsigned32, 679 pcePcepPeerLWMRspTime Unsigned32, 680 pcePcepPeerHWMRspTime Unsigned32, 681 pcePcepPeerNumPCReqSent Counter32, 682 pcePcepPeerNumPCReqRcvd Counter32, 683 pcePcepPeerNumPCRepSent Counter32, 684 pcePcepPeerNumPCRepRcvd Counter32, 685 pcePcepPeerNumPCErrSent Counter32, 686 pcePcepPeerNumPCErrRcvd Counter32, 687 pcePcepPeerNumPCNtfSent Counter32, 688 pcePcepPeerNumPCNtfRcvd Counter32, 689 pcePcepPeerNumKeepaliveSent Counter32, 690 pcePcepPeerNumKeepaliveRcvd Counter32, 691 pcePcepPeerNumUnknownRcvd Counter32, 692 pcePcepPeerNumReqSent Counter32, 693 pcePcepPeerNumSvecSent Counter32, 694 pcePcepPeerNumSvecReqSent Counter32, 695 pcePcepPeerNumReqSentPendRep Counter32, 696 pcePcepPeerNumReqSentEroRcvd Counter32, 697 pcePcepPeerNumReqSentNoPathRcvd Counter32, 698 pcePcepPeerNumReqSentCancelRcvd Counter32, 699 pcePcepPeerNumReqSentErrorRcvd Counter32, 700 pcePcepPeerNumReqSentTimeout Counter32, 701 pcePcepPeerNumReqSentCancelSent Counter32, 702 pcePcepPeerNumReqSentClosed Counter32, 703 pcePcepPeerNumReqRcvd Counter32, 704 pcePcepPeerNumSvecRcvd Counter32, 705 pcePcepPeerNumSvecReqRcvd Counter32, 706 pcePcepPeerNumReqRcvdPendRep Counter32, 707 pcePcepPeerNumReqRcvdEroSent Counter32, 708 pcePcepPeerNumReqRcvdNoPathSent Counter32, 709 pcePcepPeerNumReqRcvdCancelSent Counter32, 710 pcePcepPeerNumReqRcvdErrorSent Counter32, 711 pcePcepPeerNumReqRcvdCancelRcvd Counter32, 712 pcePcepPeerNumReqRcvdClosed Counter32, 713 pcePcepPeerNumRepRcvdUnknown Counter32, 714 pcePcepPeerNumReqRcvdUnknown Counter32 715 } 717 pcePcepPeerAddrType OBJECT-TYPE 718 SYNTAX InetAddressType 719 MAX-ACCESS not-accessible 720 STATUS current 721 DESCRIPTION 722 "The type of the peer's Internet address. This object 723 specifies how the value of the pcePcepPeerAddr object should 724 be interpreted." 725 ::= { pcePcepPeerEntry 1 } 727 pcePcepPeerAddr OBJECT-TYPE 728 SYNTAX InetAddress 729 MAX-ACCESS not-accessible 730 STATUS current 731 DESCRIPTION 732 "The Internet address of the peer. The type is given by 733 pcePcepPeerAddrType. " 734 ::= { pcePcepPeerEntry 2 } 736 pcePcepPeerRole OBJECT-TYPE 737 SYNTAX INTEGER { 738 pcc(1), 739 pce(2), 740 pccAndPce(3), 741 unknown(4) 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. Takes one of the following values. 748 - pcc(1): this peer is a Path Computation Client (PCC). 749 - pce(2): this peer is a Path Computation Server (PCE). 750 - pccAndPce(3): this peer is both a PCC and a PCE. 751 - unknown(4): this peer's role is not known." 752 ::= { pcePcepPeerEntry 3 } 754 pcePcepPeerDiscontinuityTime OBJECT-TYPE 755 SYNTAX TimeStamp 756 MAX-ACCESS read-only 757 STATUS current 758 DESCRIPTION 759 "The value of sysUpTime at the time that the information and 760 statistics in this row were last reset." 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." 801 ::= { pcePcepPeerEntry 8 } 803 pcePcepPeerSessionUpTime OBJECT-TYPE 804 SYNTAX TimeStamp 805 MAX-ACCESS read-only 806 STATUS current 807 DESCRIPTION 808 "The value of sysUpTime the last time a session with this 809 peer was successfully established. 811 If pcePcepPeerNumSessSetupOK is zero, then this object 812 contains zero." 813 ::= { pcePcepPeerEntry 9 } 815 pcePcepPeerSessionFailTime OBJECT-TYPE 816 SYNTAX TimeStamp 817 MAX-ACCESS read-only 818 STATUS current 819 DESCRIPTION 820 "The value of sysUpTime the last time a session with this 821 peer failed to be established. 823 If pcePcepPeerNumSessSetupFail is zero, then this object 824 contains zero." 825 ::= { pcePcepPeerEntry 10 } 827 pcePcepPeerAvgRspTime OBJECT-TYPE 828 SYNTAX Unsigned32 829 UNITS "milliseconds" 830 MAX-ACCESS read-only 831 STATUS current 832 DESCRIPTION 833 "The average response time for this peer. 835 If an average response time has not been calculated for this 836 peer then this object has the value zero. 838 If pcePcepPeerRole is pcc then this field is meaningless and 839 is set to zero." 840 ::= { pcePcepPeerEntry 11 } 842 pcePcepPeerLWMRspTime OBJECT-TYPE 843 SYNTAX Unsigned32 844 UNITS "milliseconds" 845 MAX-ACCESS read-only 846 STATUS current 847 DESCRIPTION 848 "The smallest (low-water mark) response time seen from this 849 peer. 851 If no responses have been received from this peer then this 852 object has the value zero. 854 If pcePcepPeerRole is pcc then this field is meaningless and 855 is set to zero." 856 ::= { pcePcepPeerEntry 12 } 858 pcePcepPeerHWMRspTime OBJECT-TYPE 859 SYNTAX Unsigned32 860 UNITS "milliseconds" 861 MAX-ACCESS read-only 862 STATUS current 863 DESCRIPTION 864 "The greatest (high-water mark) response time seen from this 865 peer. 867 If no responses have been received from this peer then this 868 object has the value zero. 870 If pcePcepPeerRole is pcc then this field is meaningless and 871 is set to zero." 872 ::= { pcePcepPeerEntry 13 } 874 pcePcepPeerNumPCReqSent OBJECT-TYPE 875 SYNTAX Counter32 876 MAX-ACCESS read-only 877 STATUS current 878 DESCRIPTION 879 "The number of PCReq messages sent to this peer." 880 ::= { pcePcepPeerEntry 14 } 882 pcePcepPeerNumPCReqRcvd OBJECT-TYPE 883 SYNTAX Counter32 884 MAX-ACCESS read-only 885 STATUS current 886 DESCRIPTION 887 "The number of PCReq messages received from this peer." 888 ::= { pcePcepPeerEntry 15 } 890 pcePcepPeerNumPCRepSent OBJECT-TYPE 891 SYNTAX Counter32 892 MAX-ACCESS read-only 893 STATUS current 894 DESCRIPTION 895 "The number of PCRep messages sent to this peer." 896 ::= { pcePcepPeerEntry 16 } 898 pcePcepPeerNumPCRepRcvd OBJECT-TYPE 899 SYNTAX Counter32 900 MAX-ACCESS read-only 901 STATUS current 902 DESCRIPTION 903 "The number of PCRep messages received from this peer." 904 ::= { pcePcepPeerEntry 17 } 906 pcePcepPeerNumPCErrSent OBJECT-TYPE 907 SYNTAX Counter32 908 MAX-ACCESS read-only 909 STATUS current 910 DESCRIPTION 911 "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." 962 ::= { pcePcepPeerEntry 24 } 964 pcePcepPeerNumReqSent OBJECT-TYPE 965 SYNTAX Counter32 966 MAX-ACCESS read-only 967 STATUS current 968 DESCRIPTION 969 "The number of requests sent to this peer. A request 970 corresponds 1:1 with an RP object in a PCReq message. 972 This might be greater than pcePcepPeerNumPCReqSent because 973 multiple requests can be batched into a single PCReq 974 message." 975 ::= { pcePcepPeerEntry 25 } 977 pcePcepPeerNumSvecSent OBJECT-TYPE 978 SYNTAX Counter32 979 MAX-ACCESS read-only 980 STATUS current 981 DESCRIPTION 982 "The number of SVEC objects sent to this peer in PCReq 983 messages. An SVEC object represents a set of synchronized 984 requests." 985 ::= { pcePcepPeerEntry 26 } 987 pcePcepPeerNumSvecReqSent OBJECT-TYPE 988 SYNTAX Counter32 989 MAX-ACCESS read-only 990 STATUS current 991 DESCRIPTION 992 "The number of requests sent to this peer that appeared in 993 one or more SVEC objects." 994 ::= { pcePcepPeerEntry 27 } 996 pcePcepPeerNumReqSentPendRep OBJECT-TYPE 997 SYNTAX Counter32 998 MAX-ACCESS read-only 999 STATUS current 1000 DESCRIPTION 1001 "The number of requests that have been sent to this peer for 1002 which a response is still pending." 1003 ::= { pcePcepPeerEntry 28 } 1005 pcePcepPeerNumReqSentEroRcvd OBJECT-TYPE 1006 SYNTAX Counter32 1007 MAX-ACCESS read-only 1008 STATUS current 1009 DESCRIPTION 1010 "The number of requests that have been sent to this peer for 1011 which a response with an ERO object was received. Such 1012 responses indicate that a path was successfully computed by 1013 the peer." 1014 ::= { pcePcepPeerEntry 29 } 1016 pcePcepPeerNumReqSentNoPathRcvd OBJECT-TYPE 1017 SYNTAX Counter32 1018 MAX-ACCESS read-only 1019 STATUS current 1020 DESCRIPTION 1021 "The number of requests that have been sent to this peer for 1022 which a response with a NO-PATH object was received. Such 1023 responses indicate that the peer could not find a path to 1024 satisfy the request." 1025 ::= { pcePcepPeerEntry 30 } 1027 pcePcepPeerNumReqSentCancelRcvd OBJECT-TYPE 1028 SYNTAX Counter32 1029 MAX-ACCESS read-only 1030 STATUS current 1031 DESCRIPTION 1032 "The number of requests that were cancelled by the peer with 1033 a PCNtf message. 1035 This might be different than pcePcepPeerNumPCNtfRcvd because 1036 not all PCNtf messages are used to cancel requests, and a 1037 single PCNtf message can cancel multiple requests." 1038 ::= { pcePcepPeerEntry 31 } 1040 pcePcepPeerNumReqSentErrorRcvd OBJECT-TYPE 1041 SYNTAX Counter32 1042 MAX-ACCESS read-only 1043 STATUS current 1044 DESCRIPTION 1045 "The number of requests that were rejected by the peer with a 1046 PCErr message. 1048 This might be different than pcePcepPeerNumPCErrRcvd because 1049 not all PCErr messages are used to reject requests, and a 1050 single PCErr message can reject multiple requests." 1051 ::= { pcePcepPeerEntry 32 } 1053 pcePcepPeerNumReqSentTimeout OBJECT-TYPE 1054 SYNTAX Counter32 1055 MAX-ACCESS read-only 1056 STATUS current 1057 DESCRIPTION 1058 "The number of requests that have been sent to a peer and 1059 have been abandoned because the peer has taken too long to 1060 respond to them." 1061 ::= { pcePcepPeerEntry 33 } 1063 pcePcepPeerNumReqSentCancelSent OBJECT-TYPE 1064 SYNTAX Counter32 1065 MAX-ACCESS read-only 1066 STATUS current 1067 DESCRIPTION 1068 "The number of requests that were sent to the peer and 1069 explicitly canceled by the local PCEP speaker sending a 1070 PCNtf." 1071 ::= { pcePcepPeerEntry 34 } 1073 pcePcepPeerNumReqSentClosed OBJECT-TYPE 1074 SYNTAX Counter32 1075 MAX-ACCESS read-only 1076 STATUS current 1077 DESCRIPTION 1078 "The number of requests that were sent to the peer and 1079 implicitly canceled when the session they were sent over was 1080 closed." 1081 ::= { pcePcepPeerEntry 35 } 1083 pcePcepPeerNumReqRcvd OBJECT-TYPE 1084 SYNTAX Counter32 1085 MAX-ACCESS read-only 1086 STATUS current 1087 DESCRIPTION 1088 "The number of requests received from this peer. A request 1089 corresponds 1:1 with an RP object in a PCReq message. 1091 This might be greater than pcePcepPeerNumPCReqRcvd because 1092 multiple requests can be batched into a single PCReq 1093 message." 1094 ::= { pcePcepPeerEntry 36 } 1096 pcePcepPeerNumSvecRcvd OBJECT-TYPE 1097 SYNTAX Counter32 1098 MAX-ACCESS read-only 1099 STATUS current 1100 DESCRIPTION 1101 "The number of SVEC objects received from this peer in PCReq 1102 messages. An SVEC object represents a set of synchronized 1103 requests." 1104 ::= { pcePcepPeerEntry 37 } 1106 pcePcepPeerNumSvecReqRcvd OBJECT-TYPE 1107 SYNTAX Counter32 1108 MAX-ACCESS read-only 1109 STATUS current 1110 DESCRIPTION 1111 "The number of requests received from this peer that appeared 1112 in one or more SVEC objects." 1113 ::= { pcePcepPeerEntry 38 } 1115 pcePcepPeerNumReqRcvdPendRep OBJECT-TYPE 1116 SYNTAX Counter32 1117 MAX-ACCESS read-only 1118 STATUS current 1119 DESCRIPTION 1120 "The number of requests that have been received from this 1121 peer for which a response is still pending." 1122 ::= { pcePcepPeerEntry 39 } 1124 pcePcepPeerNumReqRcvdEroSent OBJECT-TYPE 1125 SYNTAX Counter32 1126 MAX-ACCESS read-only 1127 STATUS current 1128 DESCRIPTION 1129 "The number of requests that have been received from this 1130 peer for which a response with an ERO object was sent. Such 1131 responses indicate that a path was successfully computed by 1132 the local PCEP speaker." 1133 ::= { pcePcepPeerEntry 40 } 1135 pcePcepPeerNumReqRcvdNoPathSent OBJECT-TYPE 1136 SYNTAX Counter32 1137 MAX-ACCESS read-only 1138 STATUS current 1139 DESCRIPTION 1140 "The number of requests that have been received from this 1141 peer for which a response with a NO-PATH object was sent. 1142 Such responses indicate that the local PCEP speaker could 1143 not find a path to satisfy the request." 1144 ::= { pcePcepPeerEntry 41 } 1146 pcePcepPeerNumReqRcvdCancelSent OBJECT-TYPE 1147 SYNTAX Counter32 1148 MAX-ACCESS read-only 1149 STATUS current 1150 DESCRIPTION 1151 "The number of requests received from this peer that were 1152 cancelled by the local PCEP speaker sending a PCNtf message. 1154 This might be different than pcePcepPeerNumPCNtfSent because 1155 not all PCNtf messages are used to cancel requests, and a 1156 single PCNtf message can cancel multiple requests." 1157 ::= { pcePcepPeerEntry 42 } 1159 pcePcepPeerNumReqRcvdErrorSent OBJECT-TYPE 1160 SYNTAX Counter32 1161 MAX-ACCESS read-only 1162 STATUS current 1163 DESCRIPTION 1164 "The number of requests received from this peer that were 1165 rejected by the local PCEP speaker sending a PCErr message. 1167 This might be different than pcePcepPeerNumPCErrSent because 1168 not all PCErr messages are used to reject requests, and a 1169 single PCErr message can reject multiple requests." 1170 ::= { pcePcepPeerEntry 43 } 1172 pcePcepPeerNumReqRcvdCancelRcvd OBJECT-TYPE 1173 SYNTAX Counter32 1174 MAX-ACCESS read-only 1175 STATUS current 1176 DESCRIPTION 1177 "The number of requests that were received from the peer and 1178 explicitly canceled by the peer sending a PCNtf." 1179 ::= { pcePcepPeerEntry 44 } 1181 pcePcepPeerNumReqRcvdClosed OBJECT-TYPE 1182 SYNTAX Counter32 1183 MAX-ACCESS read-only 1184 STATUS current 1185 DESCRIPTION 1186 "The number of requests that were received from the peer and 1187 implicitly canceled when the session they were received over 1188 was closed." 1189 ::= { pcePcepPeerEntry 45 } 1191 pcePcepPeerNumRepRcvdUnknown OBJECT-TYPE 1192 SYNTAX Counter32 1193 MAX-ACCESS read-only 1194 STATUS current 1195 DESCRIPTION 1196 "The number of responses to unknown requests received from 1197 this peer. A response to an unknown request is a response 1198 whose RP object does not contain the request ID of any 1199 request that is currently outstanding on the session." 1200 ::= { pcePcepPeerEntry 46 } 1202 pcePcepPeerNumReqRcvdUnknown OBJECT-TYPE 1203 SYNTAX Counter32 1204 MAX-ACCESS read-only 1205 STATUS current 1206 DESCRIPTION 1207 "The number of unknown requests that have been received from 1208 a peer. An unknown request is a request whose RP object 1209 contains a request ID of zero." 1210 ::= { pcePcepPeerEntry 47 } 1212 -- 1213 -- The PCEP Sessions Table 1214 -- 1216 pcePcepSessObjects OBJECT IDENTIFIER ::= { pcePcepObjects 3 } 1218 pcePcepSessTable OBJECT-TYPE 1219 SYNTAX SEQUENCE OF PcePcepSessEntry 1220 MAX-ACCESS not-accessible 1221 STATUS current 1222 DESCRIPTION 1223 "A table of PCEP sessions that involve the local PCEP 1224 speaker. Each row in this table represents a single 1225 session." 1226 ::= { pcePcepSessObjects 1 } 1228 pcePcepSessEntry OBJECT-TYPE 1229 SYNTAX PcePcepSessEntry 1230 MAX-ACCESS not-accessible 1231 STATUS current 1232 DESCRIPTION 1233 "An entry in this table represents a single PCEP session in 1234 which the local PCEP speaker participates. 1236 An entry in this table exists only if the corresponding PCEP 1237 session has been initialized by some event, such as manual 1238 user configuration, autodiscovery of a peer, or an incoming 1239 TCP connection. 1241 An entry appears in this table when the corresponding PCEP 1242 session transitions out of idle state. If the PCEP session 1243 transitions back into idle state then the corresponding 1244 entry in this table is removed." 1245 INDEX { pcePcepEntityIndex, 1246 pcePcepPeerAddrType, 1247 pcePcepPeerAddr, 1248 pcePcepSessInitiator } 1249 ::= { pcePcepSessTable 1 } 1251 PcePcepSessEntry ::= SEQUENCE { 1252 pcePcepSessInitiator INTEGER, 1253 pcePcepSessStateLastChange TimeStamp, 1254 pcePcepSessState INTEGER, 1255 pcePcepSessConnectRetry Counter32, 1256 pcePcepSessLocalID Unsigned32, 1257 pcePcepSessRemoteID Unsigned32, 1258 pcePcepSessKeepaliveTimer Unsigned32, 1259 pcePcepSessPeerKeepaliveTimer Unsigned32, 1260 pcePcepSessDeadTimer Unsigned32, 1261 pcePcepSessPeerDeadTimer Unsigned32, 1262 pcePcepSessKAHoldTimeRem Unsigned32, 1263 pcePcepSessOverloaded TruthValue, 1264 pcePcepSessOverloadTime Unsigned32, 1265 pcePcepSessPeerOverloaded TruthValue, 1266 pcePcepSessPeerOverloadTime Unsigned32, 1267 pcePcepSessDiscontinuityTime TimeStamp, 1268 pcePcepSessAvgRspTime Unsigned32, 1269 pcePcepSessLWMRspTime Unsigned32, 1270 pcePcepSessHWMRspTime Unsigned32, 1271 pcePcepSessNumPCReqSent Counter32, 1272 pcePcepSessNumPCReqRcvd Counter32, 1273 pcePcepSessNumPCRepSent Counter32, 1274 pcePcepSessNumPCRepRcvd Counter32, 1275 pcePcepSessNumPCErrSent Counter32, 1276 pcePcepSessNumPCErrRcvd Counter32, 1277 pcePcepSessNumPCNtfSent Counter32, 1278 pcePcepSessNumPCNtfRcvd Counter32, 1279 pcePcepSessNumKeepaliveSent Counter32, 1280 pcePcepSessNumKeepaliveRcvd Counter32, 1281 pcePcepSessNumUnknownRcvd Counter32, 1282 pcePcepSessNumReqSent Counter32, 1283 pcePcepSessNumSvecSent Counter32, 1284 pcePcepSessNumSvecReqSent Counter32, 1285 pcePcepSessNumReqSentPendRep Counter32, 1286 pcePcepSessNumReqSentEroRcvd Counter32, 1287 pcePcepSessNumReqSentNoPathRcvd Counter32, 1288 pcePcepSessNumReqSentCancelRcvd Counter32, 1289 pcePcepSessNumReqSentErrorRcvd Counter32, 1290 pcePcepSessNumReqSentTimeout Counter32, 1291 pcePcepSessNumReqSentCancelSent Counter32, 1292 pcePcepSessNumReqRcvd Counter32, 1293 pcePcepSessNumSvecRcvd Counter32, 1294 pcePcepSessNumSvecReqRcvd Counter32, 1295 pcePcepSessNumReqRcvdPendRep Counter32, 1296 pcePcepSessNumReqRcvdEroSent Counter32, 1297 pcePcepSessNumReqRcvdNoPathSent Counter32, 1298 pcePcepSessNumReqRcvdCancelSent Counter32, 1299 pcePcepSessNumReqRcvdErrorSent Counter32, 1300 pcePcepSessNumReqRcvdCancelRcvd Counter32, 1301 pcePcepSessNumRepRcvdUnknown Counter32, 1302 pcePcepSessNumReqRcvdUnknown Counter32 1303 } 1305 pcePcepSessInitiator OBJECT-TYPE 1306 SYNTAX INTEGER { 1307 local(1), 1308 remote(2) 1309 } 1310 MAX-ACCESS not-accessible 1311 STATUS current 1312 DESCRIPTION 1313 "The initiator of the session, that is, whether the TCP 1314 connection was initiated by the local PCEP speaker or the 1315 remote PCEP speaker. 1317 There is a window during session initialization where two 1318 sessions can exist between a pair of PCEP speakers, each 1319 initiated by one of the speakers. One of these sessions is 1320 always discarded before it leaves OpenWait state. However, 1321 before it is discarded, two sessions to the given peer 1322 appear transiently in the MIB. The sessions are 1323 distinguished by who initiated them, and so this field is an 1324 index for the pcePcepSessTable." 1325 ::= { pcePcepSessEntry 1 } 1327 pcePcepSessStateLastChange OBJECT-TYPE 1328 SYNTAX TimeStamp 1329 MAX-ACCESS read-only 1330 STATUS current 1331 DESCRIPTION 1332 "The value of sysUpTime at the time this session entered its 1333 current state as denoted by the pcePcepSessState object." 1334 ::= { pcePcepSessEntry 2 } 1336 pcePcepSessState OBJECT-TYPE 1337 SYNTAX INTEGER { 1338 tcpPending(1), 1339 openWait(2), 1340 keepWait(3), 1341 sessionUp(4) 1342 } 1343 MAX-ACCESS read-only 1344 STATUS current 1345 DESCRIPTION 1346 "The current state of the session. 1348 The set of possible states excludes the idle state since 1349 entries do not exist in this table in the idle state." 1350 ::= { pcePcepSessEntry 3 } 1352 pcePcepSessConnectRetry OBJECT-TYPE 1353 SYNTAX Counter32 1354 MAX-ACCESS read-only 1355 STATUS current 1356 DESCRIPTION 1357 "The number of times that the local PCEP speaker has 1358 attempted to establish a TCP connection for this session 1359 without success. The PCEP speaker gives up when this 1360 reaches pcePcepEntityConnectMaxRetry." 1361 ::= { pcePcepSessEntry 4 } 1363 pcePcepSessLocalID OBJECT-TYPE 1364 SYNTAX Unsigned32 (0..255) 1365 MAX-ACCESS read-only 1366 STATUS current 1367 DESCRIPTION 1368 "The value of the PCEP session ID used by the local PCEP 1369 speaker in the Open message for this session. 1371 If pcePcepSessState is tcpPending then this is the session 1372 ID that will be used in the Open message. Otherwise, this 1373 is the session ID that was sent in the Open message." 1374 ::= { pcePcepSessEntry 5 } 1376 pcePcepSessRemoteID OBJECT-TYPE 1377 SYNTAX Unsigned32 (0..255) 1378 MAX-ACCESS read-only 1379 STATUS current 1380 DESCRIPTION 1381 "The value of the PCEP session ID used by the peer in its 1382 Open message for this session. 1384 If pcePcepSessState is tcpPending or openWait then this 1385 field is not used and MUST be set to zero." 1386 ::= { pcePcepSessEntry 6 } 1388 pcePcepSessKeepaliveTimer OBJECT-TYPE 1389 SYNTAX Unsigned32 (0..255) 1390 UNITS "seconds" 1391 MAX-ACCESS read-only 1392 STATUS current 1393 DESCRIPTION 1394 "The agreed maximum interval at which the local PCEP speaker 1395 transmits PCEP messages on this PCEP session. Zero means 1396 that the local PCEP speaker never sends Keepalives on this 1397 session. 1399 This field is used if and only if pcePcepSessState is 1400 sessionUp. Otherwise, it is not used and MUST be set to 1401 zero." 1402 ::= { pcePcepSessEntry 7 } 1404 pcePcepSessPeerKeepaliveTimer OBJECT-TYPE 1405 SYNTAX Unsigned32 (0..255) 1406 UNITS "seconds" 1407 MAX-ACCESS read-only 1408 STATUS current 1409 DESCRIPTION 1410 "The agreed maximum interval at which the peer transmits PCEP 1411 messages on this PCEP session. Zero means that the peer 1412 never sends Keepalives on this session. 1414 This field is used if and only if pcePcepSessState is 1415 sessionUp. Otherwise, it is not used and MUST be set to 1416 zero." 1417 ::= { pcePcepSessEntry 8 } 1419 pcePcepSessDeadTimer OBJECT-TYPE 1420 SYNTAX Unsigned32 (0..255) 1421 UNITS "seconds" 1422 MAX-ACCESS read-only 1423 STATUS current 1424 DESCRIPTION 1425 "The DeadTimer interval for this PCEP session." 1426 ::= { pcePcepSessEntry 9 } 1428 pcePcepSessPeerDeadTimer OBJECT-TYPE 1429 SYNTAX Unsigned32 (0..255) 1430 UNITS "seconds" 1431 MAX-ACCESS read-only 1432 STATUS current 1433 DESCRIPTION 1434 "The peer's DeadTimer interval for this PCEP session. 1436 If pcePcepSessState is tcpPending or openWait then this 1437 field is not used and MUST be set to zero." 1438 ::= { pcePcepSessEntry 10 } 1440 pcePcepSessKAHoldTimeRem OBJECT-TYPE 1441 SYNTAX Unsigned32 (0..255) 1442 UNITS "seconds" 1443 MAX-ACCESS read-only 1444 STATUS current 1445 DESCRIPTION 1446 "The keep alive hold time remaining for this session. 1448 If pcePcepSessState is tcpPending or openWait then this 1449 field is not used and MUST be set to zero." 1450 ::= { pcePcepSessEntry 11 } 1452 pcePcepSessOverloaded OBJECT-TYPE 1453 SYNTAX TruthValue 1454 MAX-ACCESS read-only 1455 STATUS current 1456 DESCRIPTION 1457 "If the local PCEP speaker has informed the peer that it is 1458 currently overloaded, then this is set to true. Otherwise, 1459 it is set to false." 1460 ::= { pcePcepSessEntry 12 } 1462 pcePcepSessOverloadTime OBJECT-TYPE 1463 SYNTAX Unsigned32 1464 UNITS "seconds" 1465 MAX-ACCESS read-only 1466 STATUS current 1467 DESCRIPTION 1468 "The interval of time until the local PCEP speaker will cease 1469 to be overloaded on this session. 1471 This field is only used if pcePcepSessOverloaded is set to 1472 true. Otherwise, it is not used and MUST be set to zero." 1473 ::= { pcePcepSessEntry 13 } 1475 pcePcepSessPeerOverloaded OBJECT-TYPE 1476 SYNTAX TruthValue 1477 MAX-ACCESS read-only 1478 STATUS current 1479 DESCRIPTION 1480 "If the peer has informed the local PCEP speaker that it is 1481 currently overloaded, then this is set to true. Otherwise, 1482 it is set to false." 1483 ::= { pcePcepSessEntry 14 } 1485 pcePcepSessPeerOverloadTime OBJECT-TYPE 1486 SYNTAX Unsigned32 1487 UNITS "seconds" 1488 MAX-ACCESS read-only 1489 STATUS current 1490 DESCRIPTION 1491 "The interval of time until the peer will cease to be 1492 overloaded. If it is not known how long the peer will stay 1493 in overloaded state, this field is set to zero. 1495 This field is only used if pcePcepSessPeerOverloaded is set 1496 to true. Otherwise, it is not used and MUST be set to 1497 zero." 1498 ::= { pcePcepSessEntry 15 } 1500 pcePcepSessDiscontinuityTime OBJECT-TYPE 1501 SYNTAX TimeStamp 1502 MAX-ACCESS read-only 1503 STATUS current 1504 DESCRIPTION 1505 "The value of sysUpTime at the time that the statistics in 1506 this row were last reset." 1507 ::= { pcePcepSessEntry 16 } 1509 pcePcepSessAvgRspTime OBJECT-TYPE 1510 SYNTAX Unsigned32 1511 UNITS "milliseconds" 1512 MAX-ACCESS read-only 1513 STATUS current 1514 DESCRIPTION 1515 "The average response time for this peer on this session. 1517 If an average response time has not been calculated for this 1518 peer then this object has the value zero." 1519 ::= { pcePcepSessEntry 17 } 1521 pcePcepSessLWMRspTime OBJECT-TYPE 1522 SYNTAX Unsigned32 1523 UNITS "milliseconds" 1524 MAX-ACCESS read-only 1525 STATUS current 1526 DESCRIPTION 1527 "The smallest (low-water mark) response time seen from this 1528 peer on this session. 1530 If no responses have been received from this peer then this 1531 object has the value zero." 1532 ::= { pcePcepSessEntry 18 } 1534 pcePcepSessHWMRspTime OBJECT-TYPE 1535 SYNTAX Unsigned32 1536 UNITS "milliseconds" 1537 MAX-ACCESS read-only 1538 STATUS current 1539 DESCRIPTION 1540 "The greatest (high-water mark) response time seen from this 1541 peer on this session. 1543 If no responses have been received from this peer then this 1544 object has the value zero." 1545 ::= { pcePcepSessEntry 19 } 1547 pcePcepSessNumPCReqSent OBJECT-TYPE 1548 SYNTAX Counter32 1549 MAX-ACCESS read-only 1550 STATUS current 1551 DESCRIPTION 1552 "The number of PCReq messages sent on this session." 1553 ::= { pcePcepSessEntry 20 } 1555 pcePcepSessNumPCReqRcvd OBJECT-TYPE 1556 SYNTAX Counter32 1557 MAX-ACCESS read-only 1558 STATUS current 1559 DESCRIPTION 1560 "The number of PCReq messages received on this session." 1561 ::= { pcePcepSessEntry 21 } 1563 pcePcepSessNumPCRepSent OBJECT-TYPE 1564 SYNTAX Counter32 1565 MAX-ACCESS read-only 1566 STATUS current 1567 DESCRIPTION 1568 "The number of PCRep messages sent on this session." 1569 ::= { pcePcepSessEntry 22 } 1571 pcePcepSessNumPCRepRcvd OBJECT-TYPE 1572 SYNTAX Counter32 1573 MAX-ACCESS read-only 1574 STATUS current 1575 DESCRIPTION 1576 "The number of PCRep messages received on this session." 1577 ::= { pcePcepSessEntry 23 } 1579 pcePcepSessNumPCErrSent OBJECT-TYPE 1580 SYNTAX Counter32 1581 MAX-ACCESS read-only 1582 STATUS current 1583 DESCRIPTION 1584 "The number of PCErr messages sent on this session." 1585 ::= { pcePcepSessEntry 24 } 1587 pcePcepSessNumPCErrRcvd OBJECT-TYPE 1588 SYNTAX Counter32 1589 MAX-ACCESS read-only 1590 STATUS current 1591 DESCRIPTION 1592 "The number of PCErr messages received on this session." 1593 ::= { pcePcepSessEntry 25 } 1595 pcePcepSessNumPCNtfSent OBJECT-TYPE 1596 SYNTAX Counter32 1597 MAX-ACCESS read-only 1598 STATUS current 1599 DESCRIPTION 1600 "The number of PCNtf messages sent on this session." 1601 ::= { pcePcepSessEntry 26 } 1603 pcePcepSessNumPCNtfRcvd OBJECT-TYPE 1604 SYNTAX Counter32 1605 MAX-ACCESS read-only 1606 STATUS current 1607 DESCRIPTION 1608 "The number of PCNtf messages received on this session." 1609 ::= { pcePcepSessEntry 27 } 1611 pcePcepSessNumKeepaliveSent OBJECT-TYPE 1612 SYNTAX Counter32 1613 MAX-ACCESS read-only 1614 STATUS current 1615 DESCRIPTION 1616 "The number of Keepalive messages sent on this session." 1617 ::= { pcePcepSessEntry 28 } 1619 pcePcepSessNumKeepaliveRcvd OBJECT-TYPE 1620 SYNTAX Counter32 1621 MAX-ACCESS read-only 1622 STATUS current 1623 DESCRIPTION 1624 "The number of Keepalive messages received on this session." 1625 ::= { pcePcepSessEntry 29 } 1627 pcePcepSessNumUnknownRcvd OBJECT-TYPE 1628 SYNTAX Counter32 1629 MAX-ACCESS read-only 1630 STATUS current 1631 DESCRIPTION 1632 "The number of unknown messages received on this session." 1633 ::= { pcePcepSessEntry 30 } 1635 pcePcepSessNumReqSent OBJECT-TYPE 1636 SYNTAX Counter32 1637 MAX-ACCESS read-only 1638 STATUS current 1639 DESCRIPTION 1640 "The number of requests sent on this session. A request 1641 corresponds 1:1 with an RP object in a PCReq message. 1643 This might be greater than pcePcepSessNumPCReqSent because 1644 multiple requests can be batched into a single PCReq 1645 message." 1646 ::= { pcePcepSessEntry 31 } 1648 pcePcepSessNumSvecSent OBJECT-TYPE 1649 SYNTAX Counter32 1650 MAX-ACCESS read-only 1651 STATUS current 1652 DESCRIPTION 1653 "The number of SVEC objects sent on this session in PCReq 1654 messages. An SVEC object represents a set of synchronized 1655 requests." 1656 ::= { pcePcepSessEntry 32 } 1658 pcePcepSessNumSvecReqSent OBJECT-TYPE 1659 SYNTAX Counter32 1660 MAX-ACCESS read-only 1661 STATUS current 1662 DESCRIPTION 1663 "The number of requests sent on this session that appeared in 1664 one or more SVEC objects." 1665 ::= { pcePcepSessEntry 33 } 1667 pcePcepSessNumReqSentPendRep OBJECT-TYPE 1668 SYNTAX Counter32 1669 MAX-ACCESS read-only 1670 STATUS current 1671 DESCRIPTION 1672 "The number of requests that have been sent on this session 1673 for which a response is still pending." 1674 ::= { pcePcepSessEntry 34 } 1676 pcePcepSessNumReqSentEroRcvd OBJECT-TYPE 1677 SYNTAX Counter32 1678 MAX-ACCESS read-only 1679 STATUS current 1680 DESCRIPTION 1681 "The number of successful responses received on this session. 1682 A response corresponds 1:1 with an RP object in a PCRep 1683 message. A successful response is a response for which an 1684 ERO was successfully computed." 1685 ::= { pcePcepSessEntry 35 } 1687 pcePcepSessNumReqSentNoPathRcvd OBJECT-TYPE 1688 SYNTAX Counter32 1689 MAX-ACCESS read-only 1690 STATUS current 1691 DESCRIPTION 1692 "The number of unsuccessful responses received on this 1693 session. A response corresponds 1:1 with an RP object in a 1694 PCRep message. An unsuccessful response is a response with 1695 a NO-PATH object." 1696 ::= { pcePcepSessEntry 36 } 1698 pcePcepSessNumReqSentCancelRcvd OBJECT-TYPE 1699 SYNTAX Counter32 1700 MAX-ACCESS read-only 1701 STATUS current 1702 DESCRIPTION 1703 "The number of requests sent on this session that were 1704 cancelled by the peer with a PCNtf message. 1706 This might be different than pcePcepSessNumPCNtfRcvd because 1707 not all PCNtf messages are used to cancel requests, and a 1708 single PCNtf message can cancel multiple requests." 1709 ::= { pcePcepSessEntry 37 } 1711 pcePcepSessNumReqSentErrorRcvd OBJECT-TYPE 1712 SYNTAX Counter32 1713 MAX-ACCESS read-only 1714 STATUS current 1715 DESCRIPTION 1716 "The number of requests sent on this session that were 1717 rejected by the peer with a PCErr message. 1719 This might be different than pcePcepSessNumPCErrRcvd because 1720 not all PCErr messages are used to reject requests, and a 1721 single PCErr message can reject multiple requests." 1722 ::= { pcePcepSessEntry 38 } 1724 pcePcepSessNumReqSentTimeout OBJECT-TYPE 1725 SYNTAX Counter32 1726 MAX-ACCESS read-only 1727 STATUS current 1728 DESCRIPTION 1729 "The number of requests sent on this session that have been 1730 sent to a peer and have been abandoned because the peer has 1731 taken too long to respond to them." 1733 ::= { pcePcepSessEntry 39 } 1735 pcePcepSessNumReqSentCancelSent OBJECT-TYPE 1736 SYNTAX Counter32 1737 MAX-ACCESS read-only 1738 STATUS current 1739 DESCRIPTION 1740 "The number of requests sent on this session that were sent 1741 to the peer and explicitly canceled by the local PCEP 1742 speaker sending a PCNtf." 1743 ::= { pcePcepSessEntry 40 } 1745 pcePcepSessNumReqRcvd OBJECT-TYPE 1746 SYNTAX Counter32 1747 MAX-ACCESS read-only 1748 STATUS current 1749 DESCRIPTION 1750 "The number of requests received on this session. A request 1751 corresponds 1:1 with an RP object in a PCReq message. 1753 This might be greater than pcePcepSessNumPCReqRcvd because 1754 multiple requests can be batched into a single PCReq 1755 message." 1756 ::= { pcePcepSessEntry 41 } 1758 pcePcepSessNumSvecRcvd OBJECT-TYPE 1759 SYNTAX Counter32 1760 MAX-ACCESS read-only 1761 STATUS current 1762 DESCRIPTION 1763 "The number of SVEC objects received on this session in PCReq 1764 messages. An SVEC object represents a set of synchronized 1765 requests." 1766 ::= { pcePcepSessEntry 42 } 1768 pcePcepSessNumSvecReqRcvd OBJECT-TYPE 1769 SYNTAX Counter32 1770 MAX-ACCESS read-only 1771 STATUS current 1772 DESCRIPTION 1773 "The number of requests received on this session that 1774 appeared in one or more SVEC objects." 1775 ::= { pcePcepSessEntry 43 } 1777 pcePcepSessNumReqRcvdPendRep OBJECT-TYPE 1778 SYNTAX Counter32 1779 MAX-ACCESS read-only 1780 STATUS current 1781 DESCRIPTION 1782 "The number of requests that have been received on this 1783 session for which a response is still pending." 1784 ::= { pcePcepSessEntry 44 } 1786 pcePcepSessNumReqRcvdEroSent OBJECT-TYPE 1787 SYNTAX Counter32 1788 MAX-ACCESS read-only 1789 STATUS current 1790 DESCRIPTION 1791 "The number of successful responses sent on this session. A 1792 response corresponds 1:1 with an RP object in a PCRep 1793 message. A successful response is a response for which an 1794 ERO was successfully computed." 1795 ::= { pcePcepSessEntry 45 } 1797 pcePcepSessNumReqRcvdNoPathSent OBJECT-TYPE 1798 SYNTAX Counter32 1799 MAX-ACCESS read-only 1800 STATUS current 1801 DESCRIPTION 1802 "The number of unsuccessful responses sent on this session. 1803 A response corresponds 1:1 with an RP object in a PCRep 1804 message. An unsuccessful response is a response with a 1805 NO-PATH object." 1806 ::= { pcePcepSessEntry 46 } 1808 pcePcepSessNumReqRcvdCancelSent OBJECT-TYPE 1809 SYNTAX Counter32 1810 MAX-ACCESS read-only 1811 STATUS current 1812 DESCRIPTION 1813 "The number of requests received on this session that were 1814 cancelled by the local PCEP speaker sending a PCNtf message. 1816 This might be different than pcePcepSessNumPCNtfSent because 1817 not all PCNtf messages are used to cancel requests, and a 1818 single PCNtf message can cancel multiple requests." 1819 ::= { pcePcepSessEntry 47 } 1821 pcePcepSessNumReqRcvdErrorSent OBJECT-TYPE 1822 SYNTAX Counter32 1823 MAX-ACCESS read-only 1824 STATUS current 1825 DESCRIPTION 1826 "The number of requests received on this session that were 1827 rejected by the local PCEP speaker sending a PCErr message. 1829 This might be different than pcePcepSessNumPCErrSent because 1830 not all PCErr messages are used to reject requests, and a 1831 single PCErr message can reject multiple requests." 1832 ::= { pcePcepSessEntry 48 } 1834 pcePcepSessNumReqRcvdCancelRcvd OBJECT-TYPE 1835 SYNTAX Counter32 1836 MAX-ACCESS read-only 1837 STATUS current 1838 DESCRIPTION 1839 "The number of requests that were received on this session 1840 and explicitly canceled by the peer sending a PCNtf." 1841 ::= { pcePcepSessEntry 49 } 1843 pcePcepSessNumRepRcvdUnknown OBJECT-TYPE 1844 SYNTAX Counter32 1845 MAX-ACCESS read-only 1846 STATUS current 1847 DESCRIPTION 1848 "The number of responses to unknown requests received on this 1849 session. A response to an unknown request is a response 1850 whose RP object does not contain the request ID of any 1851 request that is currently outstanding on the session." 1852 ::= { pcePcepSessEntry 50 } 1854 pcePcepSessNumReqRcvdUnknown OBJECT-TYPE 1855 SYNTAX Counter32 1856 MAX-ACCESS read-only 1857 STATUS current 1858 DESCRIPTION 1859 "The number of unknown requests that have been received on 1860 this session. An unknown request is a request whose RP 1861 object contains a request ID of zero." 1862 ::= { pcePcepSessEntry 51 } 1864 --- 1865 --- Notifications 1866 --- 1868 pcePcepSessUp NOTIFICATION-TYPE 1869 OBJECTS { 1870 pcePcepSessState, 1871 pcePcepSessStateLastChange 1872 } 1873 STATUS current 1874 DESCRIPTION 1875 "This notification is sent when the value of 1876 'pcePcepSessState' enters the 'sessionUp' state." 1878 ::= { pcePcepNotifications 1 } 1880 pcePcepSessDown NOTIFICATION-TYPE 1881 OBJECTS { 1882 pcePcepSessState, 1883 pcePcepSessStateLastChange 1884 } 1885 STATUS current 1886 DESCRIPTION 1887 "This notification is sent when the value of 1888 'pcePcepSessState' leaves the 'sessionUp' state." 1889 ::= { pcePcepNotifications 2 } 1891 pcePcepSessLocalOverload NOTIFICATION-TYPE 1892 OBJECTS { 1893 pcePcepSessOverloaded, 1894 pcePcepSessOverloadTime 1895 } 1896 STATUS current 1897 DESCRIPTION 1898 "This notification is sent when the local PCEP speaker enters 1899 overload state for a peer." 1900 ::= { pcePcepNotifications 3 } 1902 pcePcepSessLocalOverloadClear NOTIFICATION-TYPE 1903 OBJECTS { 1904 pcePcepSessOverloaded 1905 } 1906 STATUS current 1907 DESCRIPTION 1908 "This notification is sent when the local PCEP speaker leaves 1909 overload state for a peer." 1910 ::= { pcePcepNotifications 4 } 1912 pcePcepSessPeerOverload NOTIFICATION-TYPE 1913 OBJECTS { 1914 pcePcepSessPeerOverloaded, 1915 pcePcepSessPeerOverloadTime 1916 } 1917 STATUS current 1918 DESCRIPTION 1919 "This notification is sent when a peer enters overload 1920 state." 1921 ::= { pcePcepNotifications 5 } 1923 pcePcepSessPeerOverloadClear NOTIFICATION-TYPE 1924 OBJECTS { 1925 pcePcepSessPeerOverloaded 1927 } 1928 STATUS current 1929 DESCRIPTION 1930 "This notification is sent when a peer leaves overload 1931 state." 1932 ::= { pcePcepNotifications 6 } 1934 -- 1935 -- Module Conformance Statement 1936 -- 1938 pcePcepCompliances 1939 OBJECT IDENTIFIER ::= { pcePcepConformance 1 } 1941 pcePcepGroups 1942 OBJECT IDENTIFIER ::= { pcePcepConformance 2 } 1944 -- 1945 -- Read-Only Compliance 1946 -- 1948 pcePcepModuleReadOnlyCompliance MODULE-COMPLIANCE 1949 STATUS current 1950 DESCRIPTION 1951 "The Module is implemented with support for read-only. In 1952 other words, only monitoring is available by implementing 1953 this MODULE-COMPLIANCE." 1955 MODULE -- this module 1956 MANDATORY-GROUPS { 1957 pcePcepGeneralGroup, 1958 pcePcepNotificationsGroup 1959 } 1960 ::= { pcePcepCompliances 1 } 1962 -- units of conformance 1964 pcePcepGeneralGroup OBJECT-GROUP 1965 OBJECTS { pcePcepEntityAdminStatus, 1966 pcePcepEntityOperStatus, 1967 pcePcepEntityAddrType, 1968 pcePcepEntityAddr, 1969 pcePcepEntityConnectTimer, 1970 pcePcepEntityConnectMaxRetry, 1971 pcePcepEntityOpenWaitTimer, 1972 pcePcepEntityKeepWaitTimer, 1973 pcePcepEntityKeepAliveTimer, 1974 pcePcepEntityDeadTimer, 1975 pcePcepEntityMaxKeepAliveTimer, 1976 pcePcepEntityMaxDeadTimer, 1977 pcePcepEntityAllowNegotiation, 1978 pcePcepEntityMinKeepAliveTimer, 1979 pcePcepEntityMinDeadTimer, 1980 pcePcepEntitySyncTimer, 1981 pcePcepEntityRequestTimer, 1982 pcePcepEntityInitBackoffTimer, 1983 pcePcepEntityMaxBackoffTimer, 1984 pcePcepEntityMaxSessions, 1985 pcePcepEntityMaxUnknownReqs, 1986 pcePcepEntityMaxUnknownMsgs, 1987 pcePcepPeerRole, 1988 pcePcepPeerDiscontinuityTime, 1989 pcePcepPeerInitiateSession, 1990 pcePcepPeerSessionExists, 1991 pcePcepPeerNumSessSetupOK, 1992 pcePcepPeerNumSessSetupFail, 1993 pcePcepPeerSessionUpTime, 1994 pcePcepPeerSessionFailTime, 1995 pcePcepPeerAvgRspTime, 1996 pcePcepPeerLWMRspTime, 1997 pcePcepPeerHWMRspTime, 1998 pcePcepPeerNumPCReqSent, 1999 pcePcepPeerNumPCReqRcvd, 2000 pcePcepPeerNumPCRepSent, 2001 pcePcepPeerNumPCRepRcvd, 2002 pcePcepPeerNumPCErrSent, 2003 pcePcepPeerNumPCErrRcvd, 2004 pcePcepPeerNumPCNtfSent, 2005 pcePcepPeerNumPCNtfRcvd, 2006 pcePcepPeerNumKeepaliveSent, 2007 pcePcepPeerNumKeepaliveRcvd, 2008 pcePcepPeerNumUnknownRcvd, 2009 pcePcepPeerNumReqSent, 2010 pcePcepPeerNumSvecSent, 2011 pcePcepPeerNumSvecReqSent, 2012 pcePcepPeerNumReqSentPendRep, 2013 pcePcepPeerNumReqSentEroRcvd, 2014 pcePcepPeerNumReqSentNoPathRcvd, 2015 pcePcepPeerNumReqSentCancelRcvd, 2016 pcePcepPeerNumReqSentErrorRcvd, 2017 pcePcepPeerNumReqSentTimeout, 2018 pcePcepPeerNumReqSentCancelSent, 2019 pcePcepPeerNumReqSentClosed, 2020 pcePcepPeerNumReqRcvd, 2021 pcePcepPeerNumSvecRcvd, 2022 pcePcepPeerNumSvecReqRcvd, 2023 pcePcepPeerNumReqRcvdPendRep, 2024 pcePcepPeerNumReqRcvdEroSent, 2025 pcePcepPeerNumReqRcvdNoPathSent, 2026 pcePcepPeerNumReqRcvdCancelSent, 2027 pcePcepPeerNumReqRcvdErrorSent, 2028 pcePcepPeerNumReqRcvdCancelRcvd, 2029 pcePcepPeerNumReqRcvdClosed, 2030 pcePcepPeerNumRepRcvdUnknown, 2031 pcePcepPeerNumReqRcvdUnknown, 2032 pcePcepSessStateLastChange, 2033 pcePcepSessState, 2034 pcePcepSessConnectRetry, 2035 pcePcepSessLocalID, 2036 pcePcepSessRemoteID, 2037 pcePcepSessKeepaliveTimer, 2038 pcePcepSessPeerKeepaliveTimer, 2039 pcePcepSessDeadTimer, 2040 pcePcepSessPeerDeadTimer, 2041 pcePcepSessKAHoldTimeRem, 2042 pcePcepSessOverloaded, 2043 pcePcepSessOverloadTime, 2044 pcePcepSessPeerOverloaded, 2045 pcePcepSessPeerOverloadTime, 2046 pcePcepSessDiscontinuityTime, 2047 pcePcepSessAvgRspTime, 2048 pcePcepSessLWMRspTime, 2049 pcePcepSessHWMRspTime, 2050 pcePcepSessNumPCReqSent, 2051 pcePcepSessNumPCReqRcvd, 2052 pcePcepSessNumPCRepSent, 2053 pcePcepSessNumPCRepRcvd, 2054 pcePcepSessNumPCErrSent, 2055 pcePcepSessNumPCErrRcvd, 2056 pcePcepSessNumPCNtfSent, 2057 pcePcepSessNumPCNtfRcvd, 2058 pcePcepSessNumKeepaliveSent, 2059 pcePcepSessNumKeepaliveRcvd, 2060 pcePcepSessNumUnknownRcvd, 2061 pcePcepSessNumReqSent, 2062 pcePcepSessNumSvecSent, 2063 pcePcepSessNumSvecReqSent, 2064 pcePcepSessNumReqSentPendRep, 2065 pcePcepSessNumReqSentEroRcvd, 2066 pcePcepSessNumReqSentNoPathRcvd, 2067 pcePcepSessNumReqSentCancelRcvd, 2068 pcePcepSessNumReqSentErrorRcvd, 2069 pcePcepSessNumReqSentTimeout, 2070 pcePcepSessNumReqSentCancelSent, 2071 pcePcepSessNumReqRcvd, 2072 pcePcepSessNumSvecRcvd, 2073 pcePcepSessNumSvecReqRcvd, 2074 pcePcepSessNumReqRcvdPendRep, 2075 pcePcepSessNumReqRcvdEroSent, 2076 pcePcepSessNumReqRcvdNoPathSent, 2077 pcePcepSessNumReqRcvdCancelSent, 2078 pcePcepSessNumReqRcvdErrorSent, 2079 pcePcepSessNumReqRcvdCancelRcvd, 2080 pcePcepSessNumRepRcvdUnknown, 2081 pcePcepSessNumReqRcvdUnknown 2082 } 2083 STATUS current 2084 DESCRIPTION 2085 "Objects that apply to all PCEP MIB implementations." 2086 ::= { pcePcepGroups 1 } 2088 pcePcepNotificationsGroup NOTIFICATION-GROUP 2089 NOTIFICATIONS { pcePcepSessUp, 2090 pcePcepSessDown, 2091 pcePcepSessLocalOverload, 2092 pcePcepSessLocalOverloadClear, 2093 pcePcepSessPeerOverload, 2094 pcePcepSessPeerOverloadClear 2095 } 2096 STATUS current 2097 DESCRIPTION 2098 "The notifications for a PCEP MIB implementation." 2099 ::= { pcePcepGroups 2 } 2101 END 2103 6. Security Considerations 2105 The readable objects in the PCE-PCEP-MIB module (i.e., those with 2106 MAX-ACCESS other than not-accessible) may be considered sensitive in 2107 some environments since, collectively, they provide information about 2108 the amount and frequency of path computation requests and responses 2109 within the network and can reveal some aspects of their 2110 configuration. 2112 In such environments it is important to control also GET and NOTIFY 2113 access to these objects and possibly even to encrypt their values 2114 when sending them over the network via SNMP. 2116 SNMP versions prior to SNMPv3 did not include adequate security. 2117 Even if the network itself is secure (for example by using IPsec), 2118 even then, there is no control as to who on the secure network is 2119 allowed to access and GET/SET (read/change/create/delete) the objects 2120 in this MIB module. 2122 It is RECOMMENDED that implementers consider the security features as 2123 provided by the SNMPv3 framework (see [RFC3410], section 8), 2124 including full support for the SNMPv3 cryptographic mechanisms (for 2125 authentication and privacy). 2127 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2128 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2129 enable cryptographic security. It is then a customer/operator 2130 responsibility to ensure that the SNMP entity giving access to an 2131 instance of this MIB module is properly configured to give access to 2132 the objects only to those principals (users) that have legitimate 2133 rights to indeed GET or SET (change/create/delete) them. 2135 7. IANA Considerations 2137 The MIB module in this document uses the following IANA-assigned 2138 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 2140 Descriptor OBJECT IDENTIFIER value 2141 ---------- ----------------------- 2142 pcePcepMIB { mib-2 XXX } 2144 Editor's Note (to be removed prior to publication): the IANA is 2145 requested to assign a value for "XXX" under the 'mib-2' subtree and 2146 to record the assignment in the SMI Numbers registry. When the 2147 assignment has been made, the RFC Editor is asked to replace "XXX" 2148 (here and in the MIB module) with the assigned value and to remove 2149 this note. 2151 8. Contributors 2153 Thanks to Dhruv Dhody for his contribution and detailed review. 2155 9. References 2157 9.1. Normative References 2159 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2160 Requirement Levels", BCP 14, RFC 2119, March 1997. 2162 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2163 Schoenwaelder, Ed., "Structure of Management Information 2164 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2166 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2167 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 2168 58, RFC 2579, April 1999. 2170 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2171 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2172 April 1999. 2174 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2175 Schoenwaelder, "Textual Conventions for Internet Network 2176 Addresses", RFC 4001, February 2005. 2178 [RFC5440] Vasseur, JP. and JL. Le Roux, "Path Computation Element 2179 (PCE) Communication Protocol (PCEP)", RFC 5440, March 2180 2009. 2182 9.2. Informative References 2184 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2185 "Introduction and Applicability Statements for Internet- 2186 Standard Management Framework", RFC 3410, December 2002. 2188 [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation 2189 Element (PCE)-Based Architecture", RFC 4655, August 2006. 2191 Appendix A. Acknowledgement 2193 The authors would like to thank Santanu Mazumder and Meral 2194 Shirazipour for their valuable input. 2196 Funding for the RFC Editor function is currently provided by the 2197 Internet Society. 2199 Authors' Addresses 2201 A S Kiran Koushik 2202 Cisco Systems, Inc. 2204 EMail: kkoushik@cisco.com 2206 Emile Stephan 2207 Orange 2208 2 avenue Pierre Marzin 2209 Lannion F-22307 2210 France 2212 EMail: emile.stephan@orange.com 2214 Quintin Zhao 2215 Huawei Technology 2216 125 Nagog Technology Park 2217 Acton, MA 01719 2218 US 2220 EMail: qzhao@huawei.com 2222 Daniel King 2223 Old Dog Consulting 2225 EMail: daniel@olddog.co.uk 2227 Jonathan Hardwick 2228 Metaswitch 2229 100 Church Street 2230 Enfield EN2 6BQ 2231 UK 2233 EMail: jonathan.hardwick@metaswitch.com