draft-ietf-pce-pcep-mib-11.txt   rfc7420.txt 
PCE Working Group A. Koushik Internet Engineering Task Force (IETF) A. Koushik
Internet-Draft Brocade Communications Inc. Request for Comments: 7420 Brocade Communications, Inc.
Intended status: Standards Track E. Stephan Category: Standards Track E. Stephan
Expires: April 27, 2015 Orange ISSN: 2070-1721 Orange
Q. Zhao Q. Zhao
Huawei Technology Huawei Technology
D. King D. King
Old Dog Consulting Old Dog Consulting
J. Hardwick J. Hardwick
Metaswitch Metaswitch
October 24, 2014 December 2014
Path Computation Element Communications Protocol (PCEP) Management Path Computation Element Communication Protocol (PCEP)
Information Base (MIB) Module Management Information Base (MIB) Module
draft-ietf-pce-pcep-mib-11
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling of Path In particular, it describes managed objects for modeling of the Path
Computation Element communications Protocol (PCEP) for communications Computation Element Communication Protocol (PCEP) for communications
between a Path Computation Client (PCC) and a Path Computation between a Path Computation Client (PCC) and a Path Computation
Element (PCE), or between two PCEs. Element (PCE), or between two PCEs.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on April 27, 2015. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7420.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . 4
3. PCEP MIB Module Architecture . . . . . . . . . . . . . . . . 4 3. PCEP MIB Module Architecture . . . . . . . . . . . . . . . . 4
3.1. pcePcepEntityTable . . . . . . . . . . . . . . . . . . . 4 3.1. pcePcepEntityTable . . . . . . . . . . . . . . . . . . . 4
3.2. pcePcepPeerTable . . . . . . . . . . . . . . . . . . . . 5 3.2. pcePcepPeerTable . . . . . . . . . . . . . . . . . . . . 5
3.3. pcePcepSessTable . . . . . . . . . . . . . . . . . . . . 5 3.3. pcePcepSessTable . . . . . . . . . . . . . . . . . . . . 5
3.4. PCEP Notifications . . . . . . . . . . . . . . . . . . . 6 3.4. PCEP Notifications . . . . . . . . . . . . . . . . . . . 6
3.5. Relationship to other MIB modules . . . . . . . . . . . . 6 3.5. Relationship to Other MIB Modules . . . . . . . . . . . . 6
3.6. Illustrative example . . . . . . . . . . . . . . . . . . 6 3.6. Illustrative Example . . . . . . . . . . . . . . . . . . 7
4. Object Definitions . . . . . . . . . . . . . . . . . . . . . 7 4. Object Definitions . . . . . . . . . . . . . . . . . . . . . 8
4.1. PCE-PCEP-MIB . . . . . . . . . . . . . . . . . . . . . . 7 4.1. PCE-PCEP-MIB . . . . . . . . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 48 5. Security Considerations . . . . . . . . . . . . . . . . . . . 49
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 49 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50
7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 49 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 50
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 49 7.1. Normative References . . . . . . . . . . . . . . . . . . 50
8.1. Normative References . . . . . . . . . . . . . . . . . . 49 7.2. Informative References . . . . . . . . . . . . . . . . . 51
8.2. Informative References . . . . . . . . . . . . . . . . . 50 Appendix A. PCEP MIB Module Example . . . . . . . . . . . . . . 52
Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 51 A.1. Contents of PCEP MIB Module at PCE2 . . . . . . . . . . . 53
Appendix B. PCEP MIB Module Example . . . . . . . . . . . . . . 51 A.2. Contents of PCEP MIB Module at PCCb . . . . . . . . . . . 60
B.1. Contents of PCEP MIB module at PCE2 . . . . . . . . . . . 51 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 64
B.2. Contents of PCEP MIB module at PCCb . . . . . . . . . . . 59 Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 65
1. Introduction 1. Introduction
The Path Computation Element (PCE) defined in [RFC4655] is an entity The PCE defined in [RFC4655] is an entity that is capable of
that is capable of computing a network path or route based on a computing a network path or route based on a network graph and
network graph, and applying computational constraints. A Path applying computational constraints. A PCC may make requests to a PCE
Computation Client (PCC) may make requests to a PCE for paths to be for paths to be computed.
computed.
PCEP is the communication protocol between a PCC and PCE and is PCEP is the communication protocol between a PCC and PCE and is
defined in [RFC5440]. PCEP interactions include path computation defined in [RFC5440]. PCEP interactions include path computation
requests and path computation replies as well as notifications of requests and path computation replies as well as notifications of
specific states related to the use of a PCE in the context of specific states related to the use of a PCE in the context of
Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS)
Traffic Engineering (TE). Traffic Engineering (TE).
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the MIB for use with network
for use with network management protocols in the Internet community. management protocols in the Internet community. In particular, it
In particular, it defines a MIB module that can be used to monitor defines a MIB module that can be used to monitor PCEP interactions
PCEP interactions between a PCC and a PCE, or between two PCEs. between a PCC and a PCE, or between two PCEs.
The scope of this document is to provide a MIB module for the PCEP The scope of this document is to provide a MIB module for the PCEP
base protocol defined in [RFC5440]. Extensions to the PCEP base base protocol defined in [RFC5440]. Extensions to the PCEP base
protocol are beyond the scope for this document. protocol are beyond the scope for this document.
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119 document are to be interpreted as described in BCP 14 [RFC2119].
[RFC2119].
1.2. Terminology 1.2. Terminology
This document uses the terminology defined in [RFC4655] and This document uses the terminology defined in [RFC4655] and
[RFC5440]. In particular, it uses the following acronyms. [RFC5440]. In particular, it uses the following acronyms.
o Path Computation Request message (PCReq). o Path Computation Request (PCReq) message.
o Path Computation Reply message (PCRep). o Path Computation Reply (PCRep) message.
o Notification message (PCNtf). o Notification (PCNtf) message.
o Error message (PCErr). o Error (PCErr) message.
o Request Parameters object (RP). o Request Parameter (RP) object.
o Synchronization Vector object (SVEC). o Synchronization Vector (SVEC) object.
o Explicit Route object (ERO). o Explicit Route Object (ERO).
This document uses the term "PCEP entity" to refer to a local PCEP This document uses the term "PCEP entity" to refer to a local PCEP
speaker, "peer" to refer to a remote PCEP speaker and "PCEP speaker" speaker, "peer" to refer to a remote PCEP speaker, and "PCEP speaker"
where it is not necessary to distinguish between local and remote. where it is not necessary to distinguish between local and remote.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
skipping to change at page 4, line 43 skipping to change at page 4, line 50
3.1. pcePcepEntityTable 3.1. pcePcepEntityTable
The PCEP MIB module may contain status information for multiple The PCEP MIB module may contain status information for multiple
logical local PCEP entities. There are several scenarios in which logical local PCEP entities. There are several scenarios in which
there may be more than one local PCEP entity, including the there may be more than one local PCEP entity, including the
following. following.
o A physical router, which is partitioned into multiple virtual o A physical router, which is partitioned into multiple virtual
routers, each with its own PCC. routers, each with its own PCC.
o A PCE device which front-ends a cluster of compute resources, each o A PCE device that front ends a cluster of compute resources, each
with a different set of capabilities that are accessed via with a different set of capabilities that are accessed via
different IP addresses. different IP addresses.
The pcePcepEntityTable contains one row for each local PCEP entity. The pcePcepEntityTable contains one row for each local PCEP entity.
Each row is read-only and contains current status information plus Each row is read-only and contains current status information, plus
the PCEP entity's running configuration. the PCEP entity's running configuration.
The pcePcepEntityTable is indexed by pcePcepEntityIndex, which also The pcePcepEntityTable is indexed by pcePcepEntityIndex, which also
acts as the primary index for the other tables in this MIB module. acts as the primary index for the other tables in this MIB module.
3.2. pcePcepPeerTable 3.2. pcePcepPeerTable
The pcePcepPeerTable contains one row for each peer that the local The pcePcepPeerTable contains one row for each peer that the local
PCEP entity knows about. Each row is read-only and contains PCEP entity knows about. Each row is read-only and contains
information to identify the peer, the running configuration relating information to identify the peer, the running configuration relating
to that peer and statistics that track the messages exchanged with to that peer, and statistics that track the messages exchanged with
that peer and its response times. that peer and its response times.
A PCEP speaker is identified by its IP address. If there is a PCEP A PCEP speaker is identified by its IP address. If there is a PCEP
speaker in the network that uses multiple IP addresses then it looks speaker in the network that uses multiple IP addresses, then it looks
like multiple distinct peers to the other PCEP speakers in the like multiple distinct peers to the other PCEP speakers in the
network. network.
The pcePcepPeerTable is indexed first by pcePcepEntityIndex, then by The pcePcepPeerTable is indexed first by pcePcepEntityIndex, then by
pcePcepPeerAddrType and pcePcepPeerAddr. This indexing structure pcePcepPeerAddrType and pcePcepPeerAddr. This indexing structure
allows each local PCEP entity to report its own set of peers. allows each local PCEP entity to report its own set of peers.
Since PCEP sessions can be ephemeral, the pcePcepPeerTable tracks a Since PCEP sessions can be ephemeral, pcePcepPeerTable tracks a peer
peer even when no PCEP session currently exists to that peer. The even when no PCEP session currently exists to that peer. The
statistics contained in pcePcepPeerTable are an aggregate of the statistics contained in pcePcepPeerTable are an aggregate of the
statistics for all successive sessions to that peer. statistics for all successive sessions to that peer.
To limit the quantity of information that is stored, an To limit the quantity of information that is stored, an
implementation MAY choose to discard a row from the pcePcepPeerTable implementation MAY choose to discard a row from pcePcepPeerTable if
if and only if no PCEP session exists to the corresponding peer. and only if no PCEP session exists to the corresponding peer.
3.3. pcePcepSessTable 3.3. pcePcepSessTable
The pcePcepSessTable contains one row for each PCEP session that the The pcePcepSessTable contains one row for each PCEP session that the
PCEP entity (PCE or PCC) is currently participating in. Each row is PCEP entity (PCE or PCC) is currently participating in. Each row is
read-only and contains the running configuration that is applied to read-only and contains the running configuration that is applied to
the session, plus identifiers and statistics for the session. the session, plus identifiers and statistics for the session.
The statistics in pcePcepSessTable are semantically different from The statistics in pcePcepSessTable are semantically different from
those in pcePcepPeerTable since the former apply to the current those in pcePcepPeerTable since the former applies to the current
session only, whereas the latter are the aggregate for all sessions session only, whereas the latter is the aggregate for all sessions
that have existed to that peer. that have existed to that peer.
Although [RFC5440] forbids there from being more than one active PCEP Although it is forbidden per [RFC5440] to have more than one active
session between a given pair of PCEP entities at any one time, there PCEP session between a given pair of PCEP entities at any one time,
is a window during session establishment where the pcePcepSessTable there is a window during session establishment where the
may contain two rows for a given peer, one representing a session pcePcepSessTable may contain two rows for a given peer, one
initiated by the local PCEP entity and one representing a session representing a session initiated by the local PCEP entity and one
initiated by the peer. If either of these sessions reaches active representing a session initiated by the peer. If either of these
state, then the other is discarded. sessions reaches an active state, then the other is discarded.
The pcePcepSessTable is indexed first by pcePcepEntityIndex, then by The pcePcepSessTable is indexed first by pcePcepEntityIndex, then by
pcePcepPeerAddrType and pcePcepPeerAddr, and finally by pcePcepPeerAddrType and pcePcepPeerAddr, and finally by
pcePcepSessInitiator. This indexing structure allows each local PCEP pcePcepSessInitiator. This indexing structure allows each local PCEP
entity to report its own set of active sessions. The entity to report its own set of active sessions. The
pcePcepSessInitiator index allows two rows to exist transiently for a pcePcepSessInitiator index allows two rows to exist transiently for a
given peer, as discussed above. given peer, as discussed above.
3.4. PCEP Notifications 3.4. PCEP Notifications
The PCEP MIB module contains notifications for the following The PCEP MIB module contains notifications for the following
conditions. conditions.
a. pcePcepSessUp: PCEP Session has gone up. a. pcePcepSessUp: PCEP session has gone up.
b. pcePcepSessDown: PCEP Session has gone down. b. pcePcepSessDown: PCEP session has gone down.
c. pcePcepSessLocalOverload: Local PCEP entity has sent an overload c. pcePcepSessLocalOverload: Local PCEP entity has sent an overload
PCNtf on this session. PCNtf on this session.
d. pcePcepSessLocalOverloadClear: Local PCEP entity has sent an d. pcePcepSessLocalOverloadClear: Local PCEP entity has sent an
overload-cleared PCNtf on this session. overload-cleared PCNtf on this session.
e. pcePcepSessPeerOverload: Peer has sent an overload PCNtf on this e. pcePcepSessPeerOverload: Peer has sent an overload PCNtf on this
session. session.
f. pcePcepSessPeerOverloadClear: Peer has sent an overload-cleared f. pcePcepSessPeerOverloadClear: Peer has sent an overload-cleared
PCNtf on this session. PCNtf on this session.
3.5. Relationship to other MIB modules 3.5. Relationship to Other MIB Modules
The PCEP MIB module imports the following textual conventions from The PCEP MIB module imports the following textual conventions from
the INET-ADDRESS-MIB defined in RFC 4001 [RFC4001]: the INET-ADDRESS-MIB defined in RFC 4001 [RFC4001]:
o InetAddressType o InetAddressType
o InetAddress o InetAddress
PCEP relies on existing protocols which have specialized MIB objects PCEP relies on existing protocols that have specialized MIB objects
to monitor their own activities. Consequently this document to monitor their own activities. Consequently, this document
considers that the monitoring of underlying protocols is out of scope considers that the monitoring of underlying protocols is out of scope
of the PCEP MIB module. of the PCEP MIB module.
3.6. Illustrative example 3.6. Illustrative Example
The following diagram illustrates the relationships between the The following diagram illustrates the relationships between
pcePcepEntityTable, pcePcepPeerTable and pcePcepSessTable. pcePcepEntityTable, pcePcepPeerTable, and pcePcepSessTable.
Index by: Index by:
pcePcepEntityIndex pcePcepEntityIndex
+--------------+ Index by: +--------------+ Index by:
|pcePcepEntity | pcePcepEntityIndex, |pcePcepEntity | pcePcepEntityIndex,
|Table | pcePcepPeerAddrType, |Table | pcePcepPeerAddrType,
+--------------+ pcePcepPeerAddr +--------------+ pcePcepPeerAddr
|pcePcepEntity | |pcePcepEntity |
|Entry |<----* |Entry |<----*
skipping to change at page 7, line 37 skipping to change at page 7, line 42
*-----| | | *--| | *-----| | | *--| |
| [1] | | | | | [1] | | | |
+------------+ | +------------+ +------------+ | +------------+
*----| | *----| |
| | | | | |
| +------------+ | +------------+
*----| [2] | *----| [2] |
| | | |
+------------+ +------------+
[1]: A peer entry with no current session [1]: A peer entry with no current session.
[2]: Two sessions exist during a window in session [2]: Two sessions exist during a window in session
initialization. initialization.
4. Object Definitions 4. Object Definitions
4.1. PCE-PCEP-MIB 4.1. PCE-PCEP-MIB
PCE-PCEP-MIB DEFINITIONS ::= BEGIN PCE-PCEP-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY,
OBJECT-TYPE,
mib-2,
NOTIFICATION-TYPE,
Unsigned32,
Counter32
FROM SNMPv2-SMI -- RFC 2578
TruthValue,
TimeStamp
FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE,
OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580
InetAddressType,
InetAddress
FROM INET-ADDRESS-MIB; -- RFC 4001
pcePcepMIB MODULE-IDENTITY
LAST-UPDATED
"201410241200Z" -- 24 October 2014
ORGANIZATION
"IETF Path Computation Element (PCE) Working Group"
CONTACT-INFO
"Email: pce@ietf.org
WG charter:
http://www.ietf.org/html.charters/pce-charter.html"
DESCRIPTION
"This MIB module defines a collection of objects for managing
Path Computation Element communications Protocol (PCEP).
Copyright (C) The IETF Trust (2014). This version of this
MIB module is part of RFC YYYY; see the RFC itself for full
legal notices."
-- RFC Ed,: replace YYYY with actual RFC number & remove this note
REVISION
"201410241200Z" -- 24 October 2014
DESCRIPTION
"Initial version, published as RFC YYYY."
-- RFC Ed.: replace YYYY with actual RFC number & remove this note
::= { mib-2 XXX }
-- RFC Ed.: replace XXX with IANA-assigned number & remove this note
pcePcepNotifications OBJECT IDENTIFIER ::= { pcePcepMIB 0 } IMPORTS
pcePcepObjects OBJECT IDENTIFIER ::= { pcePcepMIB 1 } MODULE-IDENTITY,
pcePcepConformance OBJECT IDENTIFIER ::= { pcePcepMIB 2 } OBJECT-TYPE,
mib-2,
NOTIFICATION-TYPE,
Unsigned32,
Counter32
FROM SNMPv2-SMI -- RFC 2578
TruthValue,
TimeStamp
FROM SNMPv2-TC -- RFC 2579
MODULE-COMPLIANCE,
OBJECT-GROUP,
NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580
InetAddressType,
InetAddress
FROM INET-ADDRESS-MIB; -- RFC 4001
-- pcePcepMIB MODULE-IDENTITY
-- PCEP Entity Objects LAST-UPDATED
-- "201412171200Z" -- 17 December 2014
ORGANIZATION
"IETF Path Computation Element (PCE) Working Group"
CONTACT-INFO
"Email: pce@ietf.org
WG charter:
http://datatracker.ietf.org/wg/pce/charter/"
pcePcepEntityTable OBJECT-TYPE DESCRIPTION
SYNTAX SEQUENCE OF PcePcepEntityEntry "This MIB module defines a collection of objects for managing
MAX-ACCESS not-accessible the Path Computation Element Communication Protocol (PCEP).
STATUS current
DESCRIPTION
"This table contains information about local PCEP entities.
The entries in this table are read-only."
::= { pcePcepObjects 1 }
pcePcepEntityEntry OBJECT-TYPE Copyright (c) 2014 IETF Trust and the persons identified as
SYNTAX PcePcepEntityEntry authors of the code. All rights reserved.
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This entry represents a local PCEP entity."
INDEX { pcePcepEntityIndex }
::= { pcePcepEntityTable 1 }
PcePcepEntityEntry ::= SEQUENCE { Redistribution and use in source and binary forms, with or
pcePcepEntityIndex Unsigned32, without modification, is permitted pursuant to, and subject
pcePcepEntityAdminStatus INTEGER, to the license terms contained in, the Simplified BSD License
pcePcepEntityOperStatus INTEGER, set forth in Section 4.c of the IETF Trust's Legal Provisions
pcePcepEntityAddrType InetAddressType, Relating to IETF Documents
pcePcepEntityAddr InetAddress, (http://trustee.ietf.org/license-info)."
pcePcepEntityConnectTimer Unsigned32,
pcePcepEntityConnectMaxRetry Unsigned32,
pcePcepEntityInitBackoffTimer Unsigned32,
pcePcepEntityMaxBackoffTimer Unsigned32,
pcePcepEntityOpenWaitTimer Unsigned32,
pcePcepEntityKeepWaitTimer Unsigned32,
pcePcepEntityKeepAliveTimer Unsigned32,
pcePcepEntityDeadTimer Unsigned32,
pcePcepEntityAllowNegotiation TruthValue,
pcePcepEntityMaxKeepAliveTimer Unsigned32,
pcePcepEntityMaxDeadTimer Unsigned32,
pcePcepEntityMinKeepAliveTimer Unsigned32,
pcePcepEntityMinDeadTimer Unsigned32,
pcePcepEntitySyncTimer Unsigned32,
pcePcepEntityRequestTimer Unsigned32,
pcePcepEntityMaxSessions Unsigned32,
pcePcepEntityMaxUnknownReqs Unsigned32,
pcePcepEntityMaxUnknownMsgs Unsigned32
}
pcePcepEntityIndex OBJECT-TYPE REVISION
SYNTAX Unsigned32 "201412171200Z" -- 17 December 2014
MAX-ACCESS not-accessible DESCRIPTION
STATUS current "Initial version, published as RFC 7420."
DESCRIPTION ::= { mib-2 227 }
"This index is used to uniquely identify the PCEP entity."
::= { pcePcepEntityEntry 1 }
pcePcepEntityAdminStatus OBJECT-TYPE pcePcepNotifications OBJECT IDENTIFIER ::= { pcePcepMIB 0 }
SYNTAX INTEGER { pcePcepObjects OBJECT IDENTIFIER ::= { pcePcepMIB 1 }
adminStatusUp(1), pcePcepConformance OBJECT IDENTIFIER ::= { pcePcepMIB 2 }
adminStatusDown(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The administrative status of this PCEP Entity.
This is the desired operational status as currently set by --
an operator or by default in the implementation. The value -- PCEP Entity Objects
of pcePcepEntityOperStatus represents the current status of --
an attempt to reach this desired status."
::= { pcePcepEntityEntry 2 }
pcePcepEntityOperStatus OBJECT-TYPE pcePcepEntityTable OBJECT-TYPE
SYNTAX INTEGER { SYNTAX SEQUENCE OF PcePcepEntityEntry
operStatusUp(1), MAX-ACCESS not-accessible
operStatusDown(2), STATUS current
operStatusGoingUp(3), DESCRIPTION
operStatusGoingDown(4), "This table contains information about local PCEP entities.
operStatusFailed(5), The entries in this table are read-only."
operStatusFailedPerm(6) ::= { pcePcepObjects 1 }
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The operational status of the PCEP entity. Takes one of the
following values.
- operStatusUp(1): the PCEP entity is active.
- operStatusDown(2): the PCEP entity is inactive.
- operStatusGoingUp(3): the PCEP entity is activating.
- operStatusGoingDown(4): the PCEP entity is deactivating.
- operStatusFailed(5): the PCEP entity has failed and will
recover when possible.
- operStatusFailedPerm(6): the PCEP entity has failed and
will not recover without operator intervention."
::= { pcePcepEntityEntry 3 }
pcePcepEntityAddrType OBJECT-TYPE pcePcepEntityEntry OBJECT-TYPE
SYNTAX InetAddressType SYNTAX PcePcepEntityEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the PCEP entity's Internet address. This object "This entry represents a local PCEP entity."
specifies how the value of the pcePcepEntityAddr object INDEX { pcePcepEntityIndex }
should be interpreted. Only values unknown(0), ipv4(1), or ::= { pcePcepEntityTable 1 }
ipv6(2) are supported."
::= { pcePcepEntityEntry 4 }
pcePcepEntityAddr OBJECT-TYPE PcePcepEntityEntry ::= SEQUENCE {
SYNTAX InetAddress pcePcepEntityIndex Unsigned32,
MAX-ACCESS read-only pcePcepEntityAdminStatus INTEGER,
STATUS current pcePcepEntityOperStatus INTEGER,
DESCRIPTION pcePcepEntityAddrType InetAddressType,
"The local Internet address of this PCEP entity. The type is pcePcepEntityAddr InetAddress,
given by pcePcepEntityAddrType. pcePcepEntityConnectTimer Unsigned32,
pcePcepEntityConnectMaxRetry Unsigned32,
pcePcepEntityInitBackoffTimer Unsigned32,
pcePcepEntityMaxBackoffTimer Unsigned32,
pcePcepEntityOpenWaitTimer Unsigned32,
pcePcepEntityKeepWaitTimer Unsigned32,
pcePcepEntityKeepAliveTimer Unsigned32,
pcePcepEntityDeadTimer Unsigned32,
pcePcepEntityAllowNegotiation TruthValue,
pcePcepEntityMaxKeepAliveTimer Unsigned32,
pcePcepEntityMaxDeadTimer Unsigned32,
pcePcepEntityMinKeepAliveTimer Unsigned32,
pcePcepEntityMinDeadTimer Unsigned32,
pcePcepEntitySyncTimer Unsigned32,
pcePcepEntityRequestTimer Unsigned32,
pcePcepEntityMaxSessions Unsigned32,
pcePcepEntityMaxUnknownReqs Unsigned32,
pcePcepEntityMaxUnknownMsgs Unsigned32
}
If operating as a PCE server, the PCEP entity listens on pcePcepEntityIndex OBJECT-TYPE
this address. If operating as a PCC, the PCEP entity binds SYNTAX Unsigned32
outgoing TCP connections to this address. MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This index is used to uniquely identify the PCEP entity."
::= { pcePcepEntityEntry 1 }
It is possible for the PCEP entity to operate both as a PCC pcePcepEntityAdminStatus OBJECT-TYPE
and a PCE Server, in which case it uses this address both to SYNTAX INTEGER {
listen for incoming TCP connections and to bind outgoing adminStatusUp(1),
TCP connections." adminStatusDown(2)
::= { pcePcepEntityEntry 5 } }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The administrative status of this PCEP entity.
pcePcepEntityConnectTimer OBJECT-TYPE This is the desired operational status as currently set by
SYNTAX Unsigned32 (1..65535) an operator or by default in the implementation. The value
UNITS "seconds" of pcePcepEntityOperStatus represents the current status of
MAX-ACCESS read-only an attempt to reach this desired status."
STATUS current ::= { pcePcepEntityEntry 2 }
DESCRIPTION
"The time that the PCEP entity will wait to establish a TCP
connection with a peer. If a TCP connection is not
established within this time then PCEP aborts the session
setup attempt."
::= { pcePcepEntityEntry 6 }
pcePcepEntityConnectMaxRetry OBJECT-TYPE pcePcepEntityOperStatus OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX INTEGER {
MAX-ACCESS read-only operStatusUp(1),
STATUS current operStatusDown(2),
DESCRIPTION operStatusGoingUp(3),
"The maximum number of times the system tries to establish operStatusGoingDown(4),
a TCP connection to a peer before the session with the peer operStatusFailed(5),
transitions to the idle state. operStatusFailedPerm(6)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The operational status of the PCEP entity. It takes one of
the following values.
When the session transitions to the idle state: - operStatusUp(1): the PCEP entity is active.
- pcePcepPeerSessionExists transitions to false(2) - operStatusDown(2): the PCEP entity is inactive.
- the associated PcePcepSessEntry is deleted - operStatusGoingUp(3): the PCEP entity is activating.
- a backoff timer runs before the session is tried again." - operStatusGoingDown(4): the PCEP entity is deactivating.
::= { pcePcepEntityEntry 7 } - operStatusFailed(5): the PCEP entity has failed and will
recover when possible.
- operStatusFailedPerm(6): the PCEP entity has failed and
will not recover without operator intervention."
::= { pcePcepEntityEntry 3 }
pcePcepEntityInitBackoffTimer OBJECT-TYPE pcePcepEntityAddrType OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX InetAddressType
UNITS "seconds" MAX-ACCESS read-only
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The type of the PCEP entity's Internet address. This object
"The initial back-off time for retrying a failed session specifies how the value of the pcePcepEntityAddr object
setup attempt to a peer. should be interpreted. Only values unknown(0), ipv4(1), or
ipv6(2) are supported."
::= { pcePcepEntityEntry 4 }
The back-off time increases for each failed session setup pcePcepEntityAddr OBJECT-TYPE
attempt, until a maximum back-off time is reached. The SYNTAX InetAddress
maximum back-off time is pcePcepEntityMaxBackoffTimer." MAX-ACCESS read-only
::= { pcePcepEntityEntry 8 } STATUS current
DESCRIPTION
"The local Internet address of this PCEP entity. The type is
given by pcePcepEntityAddrType.
pcePcepEntityMaxBackoffTimer OBJECT-TYPE If operating as a PCE server, the PCEP entity listens on
SYNTAX Unsigned32 this address. If operating as a PCC, the PCEP entity binds
UNITS "seconds" outgoing TCP connections to this address.
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum back-off time for retrying a failed session
setup attempt to a peer.
The back-off time increases for each failed session setup It is possible for the PCEP entity to operate both as a PCC
attempt, until this maximum value is reached. Session and a PCE server, in which case it uses this address both to
setup attempts then repeat periodically without any listen for incoming TCP connections and to bind outgoing
further increase in back-off time." TCP connections."
::= { pcePcepEntityEntry 9 } ::= { pcePcepEntityEntry 5 }
pcePcepEntityOpenWaitTimer OBJECT-TYPE pcePcepEntityConnectTimer OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time that the PCEP entity will wait to receive an Open "The time that the PCEP entity will wait to establish a TCP
message from a peer after the TCP connection has come up. connection with a peer. If a TCP connection is not
If no Open message is received within this time then PCEP established within this time, then PCEP aborts the session
terminates the TCP connection and deletes the associated setup attempt."
PcePcepSessEntry." ::= { pcePcepEntityEntry 6 }
::= { pcePcepEntityEntry 10 }
pcePcepEntityKeepWaitTimer OBJECT-TYPE pcePcepEntityConnectMaxRetry OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32
UNITS "seconds" MAX-ACCESS read-only
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The maximum number of times the system tries to establish
"The time that the PCEP entity will wait to receive a a TCP connection to a peer before the session with the peer
Keepalive or PCErr message from a peer during session transitions to the idle state.
initialization after receiving an Open message. If no
Keepalive or PCErr message is received within this time then
PCEP terminates the TCP connection and deletes the
associated PcePcepSessEntry."
::= { pcePcepEntityEntry 11 }
pcePcepEntityKeepAliveTimer OBJECT-TYPE When the session transitions to the idle state:
SYNTAX Unsigned32 (0..255) - pcePcepPeerSessionExists transitions to false(2).
UNITS "seconds" - the associated PcePcepSessEntry is deleted.
MAX-ACCESS read-only - a backoff timer runs before the session is tried again."
STATUS current ::= { pcePcepEntityEntry 7 }
DESCRIPTION
"The keep alive transmission timer that this PCEP entity will
propose in the initial OPEN message of each session it is
involved in. This is the maximum time between two
consecutive messages sent to a peer. Zero means that
the PCEP entity prefers not to send Keepalives at all.
Note that the actual Keepalive transmission intervals, in pcePcepEntityInitBackoffTimer OBJECT-TYPE
either direction of an active PCEP session, are determined SYNTAX Unsigned32 (1..65535)
by negotiation between the peers as specified by RFC UNITS "seconds"
5440, and so may differ from this configured value. For MAX-ACCESS read-only
the actually negotiated values (per-session), see STATUS current
pcePcepSessKeepaliveTimer and DESCRIPTION
pcePcepSessPeerKeepaliveTimer." "The initial backoff time for retrying a failed session
::= { pcePcepEntityEntry 12 } setup attempt to a peer.
pcePcepEntityDeadTimer OBJECT-TYPE The backoff time increases for each failed session setup
SYNTAX Unsigned32 (0..255) attempt, until a maximum backoff time is reached. The
UNITS "seconds" maximum backoff time is pcePcepEntityMaxBackoffTimer."
MAX-ACCESS read-only ::= { pcePcepEntityEntry 8 }
STATUS current
DESCRIPTION
"The dead timer that this PCEP entity will propose in the
initial OPEN message of each session it is involved in.
This is the time after which a peer should declare a
session down if it does not receive any PCEP messages.
Zero suggests that the peer does not run a dead timer at
all."
::= { pcePcepEntityEntry 13 }
pcePcepEntityAllowNegotiation OBJECT-TYPE pcePcepEntityMaxBackoffTimer OBJECT-TYPE
SYNTAX TruthValue SYNTAX Unsigned32
MAX-ACCESS read-only UNITS "seconds"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"Whether the PCEP entity will permit negotiation of session DESCRIPTION
parameters." "The maximum backoff time for retrying a failed session
::= { pcePcepEntityEntry 14 } setup attempt to a peer.
pcePcepEntityMaxKeepAliveTimer OBJECT-TYPE The backoff time increases for each failed session setup
SYNTAX Unsigned32 (0..255) attempt, until this maximum value is reached. Session
UNITS "seconds" setup attempts then repeats periodically without any
MAX-ACCESS read-only further increase in backoff time."
STATUS current ::= { pcePcepEntityEntry 9 }
DESCRIPTION
"In PCEP session parameter negotiation, the maximum value
that this PCEP entity will accept from a peer for the
interval between Keepalive transmissions. Zero means that
the PCEP entity will allow no Keepalive transmission at
all."
::= { pcePcepEntityEntry 15 }
pcePcepEntityMaxDeadTimer OBJECT-TYPE pcePcepEntityOpenWaitTimer OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (1..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"In PCEP session parameter negotiation, the maximum value "The time that the PCEP entity will wait to receive an Open
that this PCEP entity will accept from a peer for the Dead message from a peer after the TCP connection has come up.
timer. Zero means that the PCEP entity will allow not If no Open message is received within this time, then PCEP
running a Dead timer." terminates the TCP connection and deletes the associated
::= { pcePcepEntityEntry 16 } PcePcepSessEntry."
::= { pcePcepEntityEntry 10 }
pcePcepEntityMinKeepAliveTimer OBJECT-TYPE pcePcepEntityKeepWaitTimer OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (1..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"In PCEP session parameter negotiation, the minimum value "The time that the PCEP entity will wait to receive a
that this PCEP entity will accept for the interval between Keepalive or PCErr message from a peer during session
Keepalive transmissions. Zero means that the PCEP entity initialization after receiving an Open message. If no
insists on no Keepalive transmission at all." Keepalive or PCErr message is received within this time,
::= { pcePcepEntityEntry 17 } then PCEP terminates the TCP connection and deletes the
associated PcePcepSessEntry."
::= { pcePcepEntityEntry 11 }
pcePcepEntityMinDeadTimer OBJECT-TYPE pcePcepEntityKeepAliveTimer OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"In PCEP session parameter negotiation, the minimum value "The Keepalive transmission timer that this PCEP entity will
that this PCEP entity will accept for the Dead timer. Zero propose in the initial OPEN message of each session it is
means that the PCEP entity insists on not running a Dead involved in. This is the maximum time between two
timer." consecutive messages sent to a peer. Zero means that
::= { pcePcepEntityEntry 18 } the PCEP entity prefers not to send Keepalives at all.
pcePcepEntitySyncTimer OBJECT-TYPE Note that the actual Keepalive transmission intervals, in
SYNTAX Unsigned32 (0..65535) either direction of an active PCEP session, are determined
UNITS "seconds" by negotiation between the peers as specified by RFC
MAX-ACCESS read-only 5440, and so may differ from this configured value. For
STATUS current the actually negotiated values (per session), see
DESCRIPTION pcePcepSessKeepaliveTimer and
"The value of SyncTimer is used in the case of synchronized pcePcepSessPeerKeepaliveTimer."
path computation request using the SVEC object. ::= { pcePcepEntityEntry 12 }
Consider the case where a PCReq message is received by a PCE pcePcepEntityDeadTimer OBJECT-TYPE
that contains the SVEC object referring to M synchronized SYNTAX Unsigned32 (0..255)
path computation requests. If after the expiration of the UNITS "seconds"
SyncTimer all the M path computation requests have not been MAX-ACCESS read-only
received, a protocol error is triggered and the PCE MUST STATUS current
cancel the whole set of path computation requests. DESCRIPTION
"The DeadTimer that this PCEP entity will propose in the
initial OPEN message of each session it is involved in.
This is the time after which a peer should declare a
session down if it does not receive any PCEP messages.
Zero suggests that the peer does not run a DeadTimer at
all."
::= { pcePcepEntityEntry 13 }
The aim of the SyncTimer is to avoid the storage of unused pcePcepEntityAllowNegotiation OBJECT-TYPE
synchronized requests should one of them get lost for some SYNTAX TruthValue
reasons (for example, a misbehaving PCC). MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Whether the PCEP entity will permit negotiation of session
parameters."
::= { pcePcepEntityEntry 14 }
A value of zero is returned if and only if the entity does pcePcepEntityMaxKeepAliveTimer OBJECT-TYPE
not use the SyncTimer." SYNTAX Unsigned32 (0..255)
::= { pcePcepEntityEntry 19 } UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"In PCEP session parameter negotiation, the maximum value
that this PCEP entity will accept from a peer for the
interval between Keepalive transmissions. Zero means that
the PCEP entity will allow no Keepalive transmission at
all."
::= { pcePcepEntityEntry 15 }
pcePcepEntityRequestTimer OBJECT-TYPE pcePcepEntityMaxDeadTimer OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (0..255)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum time that the PCEP entity will wait for a "In PCEP session parameter negotiation, the maximum value
response to a PCReq message." that this PCEP entity will accept from a peer for the
::= { pcePcepEntityEntry 20 } DeadTimer. Zero means that the PCEP entity will allow not
running a DeadTimer."
::= { pcePcepEntityEntry 16 }
pcePcepEntityMaxSessions OBJECT-TYPE pcePcepEntityMinKeepAliveTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only UNITS "seconds"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"Maximum number of sessions involving this PCEP entity DESCRIPTION
that can exist at any time." "In PCEP session parameter negotiation, the minimum value
::= { pcePcepEntityEntry 21 } that this PCEP entity will accept for the interval between
Keepalive transmissions. Zero means that the PCEP entity
insists on no Keepalive transmission at all."
::= { pcePcepEntityEntry 17 }
pcePcepEntityMaxUnknownReqs OBJECT-TYPE pcePcepEntityMinDeadTimer OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only UNITS "seconds"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"The maximum number of unrecognized requests and replies that DESCRIPTION
any session on this PCEP entity is willing to accept per "In PCEP session parameter negotiation, the minimum value
minute before terminating the session. that this PCEP entity will accept for the DeadTimer. Zero
means that the PCEP entity insists on not running a
DeadTimer."
::= { pcePcepEntityEntry 18 }
A PCRep message contains an unrecognized reply if it pcePcepEntitySyncTimer OBJECT-TYPE
contains an RP object whose request ID does not correspond SYNTAX Unsigned32 (0..65535)
to any in-progress request sent by this PCEP entity. UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of SyncTimer is used in the case of a synchronized
path computation request using the SVEC object.
A PCReq message contains an unrecognized request if it Consider the case where a PCReq message is received by a PCE
contains an RP object whose request ID is zero." that contains the SVEC object referring to M synchronized
::= { pcePcepEntityEntry 22 } path computation requests. If after the expiration of the
SyncTimer all the M path computation requests have not been
received, a protocol error is triggered and the PCE MUST
cancel the whole set of path computation requests.
pcePcepEntityMaxUnknownMsgs OBJECT-TYPE The aim of the SyncTimer is to avoid the storage of unused
SYNTAX Unsigned32 synchronized requests should one of them get lost for some
MAX-ACCESS read-only reason (for example, a misbehaving PCC).
STATUS current
DESCRIPTION
"The maximum number of unknown messages that any session
on this PCEP entity is willing to accept per minute before
terminating the session."
::= { pcePcepEntityEntry 23 }
-- A value of zero is returned if and only if the entity does
-- The PCEP Peer Table not use the SyncTimer."
-- ::= { pcePcepEntityEntry 19 }
pcePcepPeerTable OBJECT-TYPE pcePcepEntityRequestTimer OBJECT-TYPE
SYNTAX SEQUENCE OF PcePcepPeerEntry SYNTAX Unsigned32 (1..65535)
MAX-ACCESS not-accessible UNITS "seconds"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"This table contains information about peers known by DESCRIPTION
the local PCEP entity. The entries in this table are "The maximum time that the PCEP entity will wait for a
read-only. response to a PCReq message."
::= { pcePcepEntityEntry 20 }
This table gives peer information that spans PCEP pcePcepEntityMaxSessions OBJECT-TYPE
sessions. Information about current PCEP sessions can be SYNTAX Unsigned32
found in the pcePcepSessTable table." MAX-ACCESS read-only
::= { pcePcepObjects 2 } STATUS current
DESCRIPTION
"The maximum number of sessions involving this PCEP entity
that can exist at any time."
::= { pcePcepEntityEntry 21 }
pcePcepPeerEntry OBJECT-TYPE pcePcepEntityMaxUnknownReqs OBJECT-TYPE
SYNTAX PcePcepPeerEntry SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a single peer which spans all PCEP "The maximum number of unrecognized requests and replies that
sessions to that peer." any session on this PCEP entity is willing to accept per
INDEX { pcePcepEntityIndex, minute before terminating the session.
pcePcepPeerAddrType,
pcePcepPeerAddr }
::= { pcePcepPeerTable 1 }
PcePcepPeerEntry ::= SEQUENCE { A PCRep message contains an unrecognized reply if it
pcePcepPeerAddrType InetAddressType, contains an RP object whose request ID does not correspond
pcePcepPeerAddr InetAddress, to any in-progress request sent by this PCEP entity.
pcePcepPeerRole INTEGER,
pcePcepPeerDiscontinuityTime TimeStamp,
pcePcepPeerInitiateSession TruthValue,
pcePcepPeerSessionExists TruthValue,
pcePcepPeerNumSessSetupOK Counter32,
pcePcepPeerNumSessSetupFail Counter32,
pcePcepPeerSessionUpTime TimeStamp,
pcePcepPeerSessionFailTime TimeStamp,
pcePcepPeerSessionFailUpTime TimeStamp,
pcePcepPeerAvgRspTime Unsigned32,
pcePcepPeerLWMRspTime Unsigned32,
pcePcepPeerHWMRspTime Unsigned32,
pcePcepPeerNumPCReqSent Counter32,
pcePcepPeerNumPCReqRcvd Counter32,
pcePcepPeerNumPCRepSent Counter32,
pcePcepPeerNumPCRepRcvd Counter32,
pcePcepPeerNumPCErrSent Counter32,
pcePcepPeerNumPCErrRcvd Counter32,
pcePcepPeerNumPCNtfSent Counter32,
pcePcepPeerNumPCNtfRcvd Counter32,
pcePcepPeerNumKeepaliveSent Counter32,
pcePcepPeerNumKeepaliveRcvd Counter32,
pcePcepPeerNumUnknownRcvd Counter32,
pcePcepPeerNumCorruptRcvd Counter32,
pcePcepPeerNumReqSent Counter32,
pcePcepPeerNumSvecSent Counter32,
pcePcepPeerNumSvecReqSent Counter32,
pcePcepPeerNumReqSentPendRep Counter32,
pcePcepPeerNumReqSentEroRcvd Counter32,
pcePcepPeerNumReqSentNoPathRcvd Counter32,
pcePcepPeerNumReqSentCancelRcvd Counter32,
pcePcepPeerNumReqSentErrorRcvd Counter32,
pcePcepPeerNumReqSentTimeout Counter32,
pcePcepPeerNumReqSentCancelSent Counter32,
pcePcepPeerNumReqSentClosed Counter32,
pcePcepPeerNumReqRcvd Counter32,
pcePcepPeerNumSvecRcvd Counter32,
pcePcepPeerNumSvecReqRcvd Counter32,
pcePcepPeerNumReqRcvdPendRep Counter32,
pcePcepPeerNumReqRcvdEroSent Counter32,
pcePcepPeerNumReqRcvdNoPathSent Counter32,
pcePcepPeerNumReqRcvdCancelSent Counter32,
pcePcepPeerNumReqRcvdErrorSent Counter32,
pcePcepPeerNumReqRcvdCancelRcvd Counter32,
pcePcepPeerNumReqRcvdClosed Counter32,
pcePcepPeerNumRepRcvdUnknown Counter32,
pcePcepPeerNumReqRcvdUnknown Counter32
}
pcePcepPeerAddrType OBJECT-TYPE A PCReq message contains an unrecognized request if it
SYNTAX InetAddressType contains an RP object whose request ID is zero."
MAX-ACCESS not-accessible ::= { pcePcepEntityEntry 22 }
STATUS current
DESCRIPTION
"The type of the peer's Internet address. This object
specifies how the value of the pcePcepPeerAddr object should
be interpreted. Only values unknown(0), ipv4(1), or
ipv6(2) are supported."
::= { pcePcepPeerEntry 1 }
pcePcepPeerAddr OBJECT-TYPE pcePcepEntityMaxUnknownMsgs OBJECT-TYPE
SYNTAX InetAddress SYNTAX Unsigned32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Internet address of the peer. The type is given by "The maximum number of unknown messages that any session
pcePcepPeerAddrType." on this PCEP entity is willing to accept per minute before
::= { pcePcepPeerEntry 2 } terminating the session."
::= { pcePcepEntityEntry 23 }
pcePcepPeerRole OBJECT-TYPE --
SYNTAX INTEGER { -- The PCEP Peer Table
unknown(0), --
pcc(1),
pce(2),
pccAndPce(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The role that this peer took the last time a session was
established. Takes one of the following values.
- unknown(0): this peer's role is not known. pcePcepPeerTable OBJECT-TYPE
- pcc(1): this peer is a Path Computation Client (PCC). SYNTAX SEQUENCE OF PcePcepPeerEntry
- pce(2): this peer is a Path Computation Server (PCE). MAX-ACCESS not-accessible
- pccAndPce(3): this peer is both a PCC and a PCE." STATUS current
::= { pcePcepPeerEntry 3 } DESCRIPTION
"This table contains information about peers known by
the local PCEP entity. The entries in this table are
read-only.
pcePcepPeerDiscontinuityTime OBJECT-TYPE This table gives peer information that spans PCEP
SYNTAX TimeStamp sessions. Information about current PCEP sessions can be
MAX-ACCESS read-only found in the pcePcepSessTable table."
STATUS current ::= { pcePcepObjects 2 }
DESCRIPTION
"The value of sysUpTime at the time that the information and
statistics in this row were last reset."
::= { pcePcepPeerEntry 4 }
pcePcepPeerInitiateSession OBJECT-TYPE pcePcepPeerEntry OBJECT-TYPE
SYNTAX TruthValue SYNTAX PcePcepPeerEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether the local PCEP entity initiates sessions "Information about a single peer that spans all PCEP
to this peer, or waits for the peer to initiate a session." sessions to that peer."
::= { pcePcepPeerEntry 5 } INDEX { pcePcepEntityIndex,
pcePcepPeerAddrType,
pcePcepPeerAddr }
::= { pcePcepPeerTable 1 }
pcePcepPeerSessionExists OBJECT-TYPE PcePcepPeerEntry ::= SEQUENCE {
SYNTAX TruthValue pcePcepPeerAddrType InetAddressType,
MAX-ACCESS read-only pcePcepPeerAddr InetAddress,
STATUS current pcePcepPeerRole INTEGER,
DESCRIPTION pcePcepPeerDiscontinuityTime TimeStamp,
"Indicates whether a session with this peer currently pcePcepPeerInitiateSession TruthValue,
exists." pcePcepPeerSessionExists TruthValue,
::= { pcePcepPeerEntry 6 } pcePcepPeerNumSessSetupOK Counter32,
pcePcepPeerNumSessSetupFail Counter32,
pcePcepPeerSessionUpTime TimeStamp,
pcePcepPeerSessionFailTime TimeStamp,
pcePcepPeerSessionFailUpTime TimeStamp,
pcePcepPeerAvgRspTime Unsigned32,
pcePcepPeerLWMRspTime Unsigned32,
pcePcepPeerHWMRspTime Unsigned32,
pcePcepPeerNumPCReqSent Counter32,
pcePcepPeerNumPCReqRcvd Counter32,
pcePcepPeerNumPCRepSent Counter32,
pcePcepPeerNumPCRepRcvd Counter32,
pcePcepPeerNumPCErrSent Counter32,
pcePcepPeerNumPCErrRcvd Counter32,
pcePcepPeerNumPCNtfSent Counter32,
pcePcepPeerNumPCNtfRcvd Counter32,
pcePcepPeerNumKeepaliveSent Counter32,
pcePcepPeerNumKeepaliveRcvd Counter32,
pcePcepPeerNumUnknownRcvd Counter32,
pcePcepPeerNumCorruptRcvd Counter32,
pcePcepPeerNumReqSent Counter32,
pcePcepPeerNumSvecSent Counter32,
pcePcepPeerNumSvecReqSent Counter32,
pcePcepPeerNumReqSentPendRep Counter32,
pcePcepPeerNumReqSentEroRcvd Counter32,
pcePcepPeerNumReqSentNoPathRcvd Counter32,
pcePcepPeerNumReqSentCancelRcvd Counter32,
pcePcepPeerNumReqSentErrorRcvd Counter32,
pcePcepPeerNumReqSentTimeout Counter32,
pcePcepPeerNumReqSentCancelSent Counter32,
pcePcepPeerNumReqSentClosed Counter32,
pcePcepPeerNumReqRcvd Counter32,
pcePcepPeerNumSvecRcvd Counter32,
pcePcepPeerNumSvecReqRcvd Counter32,
pcePcepPeerNumReqRcvdPendRep Counter32,
pcePcepPeerNumReqRcvdEroSent Counter32,
pcePcepPeerNumReqRcvdNoPathSent Counter32,
pcePcepPeerNumReqRcvdCancelSent Counter32,
pcePcepPeerNumReqRcvdErrorSent Counter32,
pcePcepPeerNumReqRcvdCancelRcvd Counter32,
pcePcepPeerNumReqRcvdClosed Counter32,
pcePcepPeerNumRepRcvdUnknown Counter32,
pcePcepPeerNumReqRcvdUnknown Counter32
}
pcePcepPeerNumSessSetupOK OBJECT-TYPE pcePcepPeerAddrType OBJECT-TYPE
SYNTAX Counter32 SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of PCEP sessions successfully established with "The type of the peer's Internet address. This object
the peer, including any current session. This counter is specifies how the value of the pcePcepPeerAddr object should
incremented each time a session with this peer is be interpreted. Only values unknown(0), ipv4(1), or
successfully established." ipv6(2) are supported."
::= { pcePcepPeerEntry 7 } ::= { pcePcepPeerEntry 1 }
pcePcepPeerNumSessSetupFail OBJECT-TYPE pcePcepPeerAddr OBJECT-TYPE
SYNTAX Counter32 SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of PCEP sessions with the peer that have been "The Internet address of the peer. The type is given by
attempted but failed before being fully established. pcePcepPeerAddrType."
This counter is incremented each time a session retry to ::= { pcePcepPeerEntry 2 }
this peer fails."
::= { pcePcepPeerEntry 8 }
pcePcepPeerSessionUpTime OBJECT-TYPE pcePcepPeerRole OBJECT-TYPE
SYNTAX TimeStamp SYNTAX INTEGER {
MAX-ACCESS read-only unknown(0),
STATUS current pcc(1),
DESCRIPTION pce(2),
"The value of sysUpTime the last time a session with this pccAndPce(3)
peer was successfully established. }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The role that this peer took the last time a session was
established. It takes one of the following values.
- unknown(0): this peer's role is not known.
- pcc(1): this peer is a Path Computation Client (PCC).
- pce(2): this peer is a Path Computation Element (PCE).
- pccAndPce(3): this peer is both a PCC and a PCE."
::= { pcePcepPeerEntry 3 }
If pcePcepPeerNumSessSetupOK is zero, then this object pcePcepPeerDiscontinuityTime OBJECT-TYPE
contains zero." SYNTAX TimeStamp
::= { pcePcepPeerEntry 9 } MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time that the information and
statistics in this row were last reset."
::= { pcePcepPeerEntry 4 }
pcePcepPeerSessionFailTime OBJECT-TYPE pcePcepPeerInitiateSession OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime the last time a session with this "Indicates whether the local PCEP entity initiates sessions
peer failed to be established. to this peer or waits for the peer to initiate a session."
::= { pcePcepPeerEntry 5 }
If pcePcepPeerNumSessSetupFail is zero, then this object pcePcepPeerSessionExists OBJECT-TYPE
contains zero." SYNTAX TruthValue
::= { pcePcepPeerEntry 10 } MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether a session with this peer currently
exists."
::= { pcePcepPeerEntry 6 }
pcePcepPeerSessionFailUpTime OBJECT-TYPE pcePcepPeerNumSessSetupOK OBJECT-TYPE
SYNTAX TimeStamp SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime the last time a session with this "The number of PCEP sessions successfully established with
peer failed from active. the peer, including any current session. This counter is
incremented each time a session with this peer is
successfully established."
::= { pcePcepPeerEntry 7 }
If pcePcepPeerNumSessSetupOK is zero, then this object pcePcepPeerNumSessSetupFail OBJECT-TYPE
contains zero." SYNTAX Counter32
::= { pcePcepPeerEntry 11 } MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of PCEP sessions with the peer that have been
attempted but failed before being fully established.
This counter is incremented each time a session retry to
this peer fails."
::= { pcePcepPeerEntry 8 }
pcePcepPeerAvgRspTime OBJECT-TYPE pcePcepPeerSessionUpTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX TimeStamp
UNITS "milliseconds" MAX-ACCESS read-only
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The value of sysUpTime the last time a session with this
"The average response time for this peer. peer was successfully established.
If an average response time has not been calculated for this If pcePcepPeerNumSessSetupOK is zero, then this object
peer then this object has the value zero. contains zero."
::= { pcePcepPeerEntry 9 }
If pcePcepPeerRole is pcc then this field is meaningless and pcePcepPeerSessionFailTime OBJECT-TYPE
is set to zero." SYNTAX TimeStamp
::= { pcePcepPeerEntry 12 } MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime the last time a session with this
peer failed to be established.
pcePcepPeerLWMRspTime OBJECT-TYPE If pcePcepPeerNumSessSetupFail is zero, then this object
SYNTAX Unsigned32 contains zero."
UNITS "milliseconds" ::= { pcePcepPeerEntry 10 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The smallest (low-water mark) response time seen from this
peer.
If no responses have been received from this peer then this pcePcepPeerSessionFailUpTime OBJECT-TYPE
object has the value zero. SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime the last time a session with this
peer failed from active.
If pcePcepPeerRole is pcc then this field is meaningless and If pcePcepPeerNumSessSetupOK is zero, then this object
is set to zero." contains zero."
::= { pcePcepPeerEntry 13 } ::= { pcePcepPeerEntry 11 }
pcePcepPeerHWMRspTime OBJECT-TYPE pcePcepPeerAvgRspTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "milliseconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The greatest (high-water mark) response time seen from this "The average response time for this peer.
peer.
If no responses have been received from this peer then this If an average response time has not been calculated for this
object has the value zero. peer, then this object has the value zero.
If pcePcepPeerRole is pcc then this field is meaningless and If pcePcepPeerRole is pcc, then this field is meaningless
is set to zero." and is set to zero."
::= { pcePcepPeerEntry 14 } ::= { pcePcepPeerEntry 12 }
pcePcepPeerNumPCReqSent OBJECT-TYPE pcePcepPeerLWMRspTime OBJECT-TYPE
SYNTAX Counter32 SYNTAX Unsigned32
MAX-ACCESS read-only UNITS "milliseconds"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"The number of PCReq messages sent to this peer." DESCRIPTION
"The smallest (low-water mark) response time seen from this
peer.
::= { pcePcepPeerEntry 15 } If no responses have been received from this peer, then this
object has the value zero.
pcePcepPeerNumPCReqRcvd OBJECT-TYPE If pcePcepPeerRole is pcc, then this field is meaningless
SYNTAX Counter32 and is set to zero."
MAX-ACCESS read-only ::= { pcePcepPeerEntry 13 }
STATUS current
DESCRIPTION
"The number of PCReq messages received from this peer."
::= { pcePcepPeerEntry 16 }
pcePcepPeerNumPCRepSent OBJECT-TYPE pcePcepPeerHWMRspTime OBJECT-TYPE
SYNTAX Counter32 SYNTAX Unsigned32
MAX-ACCESS read-only UNITS "milliseconds"
STATUS current MAX-ACCESS read-only
DESCRIPTION STATUS current
"The number of PCRep messages sent to this peer." DESCRIPTION
::= { pcePcepPeerEntry 17 } "The greatest (high-water mark) response time seen from this
peer.
pcePcepPeerNumPCRepRcvd OBJECT-TYPE If no responses have been received from this peer, then this
SYNTAX Counter32 object has the value zero.
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of PCRep messages received from this peer."
::= { pcePcepPeerEntry 18 }
pcePcepPeerNumPCErrSent OBJECT-TYPE If pcePcepPeerRole is pcc, then this field is meaningless
SYNTAX Counter32 and is set to zero."
MAX-ACCESS read-only ::= { pcePcepPeerEntry 14 }
STATUS current
DESCRIPTION
"The number of PCErr messages sent to this peer."
::= { pcePcepPeerEntry 19 }
pcePcepPeerNumPCErrRcvd OBJECT-TYPE pcePcepPeerNumPCReqSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of PCErr messages received from this peer." "The number of PCReq messages sent to this peer."
::= { pcePcepPeerEntry 20 } ::= { pcePcepPeerEntry 15 }
pcePcepPeerNumPCNtfSent OBJECT-TYPE pcePcepPeerNumPCReqRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of PCNtf messages sent to this peer." "The number of PCReq messages received from this peer."
::= { pcePcepPeerEntry 16 }
::= { pcePcepPeerEntry 21 } pcePcepPeerNumPCRepSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of PCRep messages sent to this peer."
::= { pcePcepPeerEntry 17 }
pcePcepPeerNumPCNtfRcvd OBJECT-TYPE pcePcepPeerNumPCRepRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of PCNtf messages received from this peer." "The number of PCRep messages received from this peer."
::= { pcePcepPeerEntry 22 } ::= { pcePcepPeerEntry 18 }
pcePcepPeerNumKeepaliveSent OBJECT-TYPE pcePcepPeerNumPCErrSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Keepalive messages sent to this peer." "The number of PCErr messages sent to this peer."
::= { pcePcepPeerEntry 23 } ::= { pcePcepPeerEntry 19 }
pcePcepPeerNumKeepaliveRcvd OBJECT-TYPE pcePcepPeerNumPCErrRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Keepalive messages received from this peer." "The number of PCErr messages received from this peer."
::= { pcePcepPeerEntry 24 } ::= { pcePcepPeerEntry 20 }
pcePcepPeerNumUnknownRcvd OBJECT-TYPE pcePcepPeerNumPCNtfSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of unknown messages received from this peer." "The number of PCNtf messages sent to this peer."
::= { pcePcepPeerEntry 25 } ::= { pcePcepPeerEntry 21 }
pcePcepPeerNumCorruptRcvd OBJECT-TYPE pcePcepPeerNumPCNtfRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of corrupted PCEP message received from this "The number of PCNtf messages received from this peer."
peer." ::= { pcePcepPeerEntry 22 }
::= { pcePcepPeerEntry 26 }
pcePcepPeerNumReqSent OBJECT-TYPE pcePcepPeerNumKeepaliveSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests sent to this peer. A request "The number of Keepalive messages sent to this peer."
corresponds 1:1 with an RP object in a PCReq message. ::= { pcePcepPeerEntry 23 }
This might be greater than pcePcepPeerNumPCReqSent because pcePcepPeerNumKeepaliveRcvd OBJECT-TYPE
multiple requests can be batched into a single PCReq SYNTAX Counter32
message." MAX-ACCESS read-only
::= { pcePcepPeerEntry 27 } STATUS current
DESCRIPTION
"The number of Keepalive messages received from this peer."
::= { pcePcepPeerEntry 24 }
pcePcepPeerNumSvecSent OBJECT-TYPE pcePcepPeerNumUnknownRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of SVEC objects sent to this peer in PCReq "The number of unknown messages received from this peer."
messages. An SVEC object represents a set of synchronized ::= { pcePcepPeerEntry 25 }
requests."
::= { pcePcepPeerEntry 28 }
pcePcepPeerNumSvecReqSent OBJECT-TYPE pcePcepPeerNumCorruptRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests sent to this peer that appeared in "The number of corrupted PCEP messages received from this
one or more SVEC objects." peer."
::= { pcePcepPeerEntry 29 } ::= { pcePcepPeerEntry 26 }
pcePcepPeerNumReqSentPendRep OBJECT-TYPE pcePcepPeerNumReqSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests that have been sent to this peer for "The number of requests sent to this peer. A request
which a response is still pending." corresponds 1:1 with an RP object in a PCReq message.
::= { pcePcepPeerEntry 30 }
pcePcepPeerNumReqSentEroRcvd OBJECT-TYPE This might be greater than pcePcepPeerNumPCReqSent because
SYNTAX Counter32 multiple requests can be batched into a single PCReq
MAX-ACCESS read-only message."
STATUS current ::= { pcePcepPeerEntry 27 }
DESCRIPTION
"The number of requests that have been sent to this peer for
which a response with an ERO object was received. Such
responses indicate that a path was successfully computed by
the peer."
::= { pcePcepPeerEntry 31 }
pcePcepPeerNumReqSentNoPathRcvd OBJECT-TYPE pcePcepPeerNumSvecSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests that have been sent to this peer for "The number of SVEC objects sent to this peer in PCReq
which a response with a NO-PATH object was received. Such messages. An SVEC object represents a set of synchronized
responses indicate that the peer could not find a path to requests."
satisfy the request." ::= { pcePcepPeerEntry 28 }
::= { pcePcepPeerEntry 32 }
pcePcepPeerNumReqSentCancelRcvd OBJECT-TYPE pcePcepPeerNumSvecReqSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests that were cancelled by the peer with "The number of requests sent to this peer that appeared in
a PCNtf message. one or more SVEC objects."
::= { pcePcepPeerEntry 29 }
This might be different than pcePcepPeerNumPCNtfRcvd because pcePcepPeerNumReqSentPendRep OBJECT-TYPE
not all PCNtf messages are used to cancel requests, and a SYNTAX Counter32
single PCNtf message can cancel multiple requests." MAX-ACCESS read-only
::= { pcePcepPeerEntry 33 } STATUS current
DESCRIPTION
"The number of requests that have been sent to this peer for
which a response is still pending."
::= { pcePcepPeerEntry 30 }
pcePcepPeerNumReqSentErrorRcvd OBJECT-TYPE pcePcepPeerNumReqSentEroRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests that were rejected by the peer with a "The number of requests that have been sent to this peer for
PCErr message. which a response with an ERO was
received. Such responses indicate that a path was
successfully computed by the peer."
::= { pcePcepPeerEntry 31 }
This might be different than pcePcepPeerNumPCErrRcvd because pcePcepPeerNumReqSentNoPathRcvd OBJECT-TYPE
not all PCErr messages are used to reject requests, and a SYNTAX Counter32
single PCErr message can reject multiple requests." MAX-ACCESS read-only
::= { pcePcepPeerEntry 34 } STATUS current
DESCRIPTION
"The number of requests that have been sent to this peer for
which a response with a NO-PATH object was received. Such
responses indicate that the peer could not find a path to
satisfy the request."
::= { pcePcepPeerEntry 32 }
pcePcepPeerNumReqSentTimeout OBJECT-TYPE pcePcepPeerNumReqSentCancelRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests that have been sent to a peer and "The number of requests that were canceled by the peer with
have been abandoned because the peer has taken too long to a PCNtf message.
respond to them."
::= { pcePcepPeerEntry 35 }
pcePcepPeerNumReqSentCancelSent OBJECT-TYPE This might be different than pcePcepPeerNumPCNtfRcvd because
SYNTAX Counter32 not all PCNtf messages are used to cancel requests, and a
MAX-ACCESS read-only single PCNtf message can cancel multiple requests."
STATUS current ::= { pcePcepPeerEntry 33 }
DESCRIPTION
"The number of requests that were sent to the peer and
explicitly canceled by the local PCEP entity sending a
PCNtf."
::= { pcePcepPeerEntry 36 }
pcePcepPeerNumReqSentClosed OBJECT-TYPE pcePcepPeerNumReqSentErrorRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests that were sent to the peer and "The number of requests that were rejected by the peer with a
implicitly canceled when the session they were sent over was PCErr message.
closed."
::= { pcePcepPeerEntry 37 }
pcePcepPeerNumReqRcvd OBJECT-TYPE This might be different than pcePcepPeerNumPCErrRcvd because
SYNTAX Counter32 not all PCErr messages are used to reject requests, and a
MAX-ACCESS read-only single PCErr message can reject multiple requests."
STATUS current ::= { pcePcepPeerEntry 34 }
DESCRIPTION
"The number of requests received from this peer. A request
corresponds 1:1 with an RP object in a PCReq message.
This might be greater than pcePcepPeerNumPCReqRcvd because pcePcepPeerNumReqSentTimeout OBJECT-TYPE
multiple requests can be batched into a single PCReq SYNTAX Counter32
message." MAX-ACCESS read-only
::= { pcePcepPeerEntry 38 } STATUS current
DESCRIPTION
"The number of requests that have been sent to a peer and
have been abandoned because the peer has taken too long to
respond to them."
::= { pcePcepPeerEntry 35 }
pcePcepPeerNumSvecRcvd OBJECT-TYPE pcePcepPeerNumReqSentCancelSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of SVEC objects received from this peer in PCReq "The number of requests that were sent to the peer and
messages. An SVEC object represents a set of synchronized explicitly canceled by the local PCEP entity sending a
requests." PCNtf."
::= { pcePcepPeerEntry 39 } ::= { pcePcepPeerEntry 36 }
pcePcepPeerNumSvecReqRcvd OBJECT-TYPE pcePcepPeerNumReqSentClosed OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests received from this peer that appeared "The number of requests that were sent to the peer and
in one or more SVEC objects." implicitly canceled when the session they were sent over was
closed."
::= { pcePcepPeerEntry 37 }
::= { pcePcepPeerEntry 40 } pcePcepPeerNumReqRcvd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of requests received from this peer. A request
corresponds 1:1 with an RP object in a PCReq message.
pcePcepPeerNumReqRcvdPendRep OBJECT-TYPE This might be greater than pcePcepPeerNumPCReqRcvd because
SYNTAX Counter32 multiple requests can be batched into a single PCReq
MAX-ACCESS read-only message."
STATUS current ::= { pcePcepPeerEntry 38 }
DESCRIPTION
"The number of requests that have been received from this
peer for which a response is still pending."
::= { pcePcepPeerEntry 41 }
pcePcepPeerNumReqRcvdEroSent OBJECT-TYPE pcePcepPeerNumSvecRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests that have been received from this "The number of SVEC objects received from this peer in PCReq
peer for which a response with an ERO object was sent. Such messages. An SVEC object represents a set of synchronized
responses indicate that a path was successfully computed by requests."
the local PCEP entity." ::= { pcePcepPeerEntry 39 }
::= { pcePcepPeerEntry 42 }
pcePcepPeerNumReqRcvdNoPathSent OBJECT-TYPE pcePcepPeerNumSvecReqRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests that have been received from this "The number of requests received from this peer that appeared
peer for which a response with a NO-PATH object was sent. in one or more SVEC objects."
Such responses indicate that the local PCEP entity could ::= { pcePcepPeerEntry 40 }
not find a path to satisfy the request."
::= { pcePcepPeerEntry 43 }
pcePcepPeerNumReqRcvdCancelSent OBJECT-TYPE pcePcepPeerNumReqRcvdPendRep OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests received from this peer that were "The number of requests that have been received from this
cancelled by the local PCEP entity sending a PCNtf message. peer for which a response is still pending."
::= { pcePcepPeerEntry 41 }
This might be different than pcePcepPeerNumPCNtfSent because pcePcepPeerNumReqRcvdEroSent OBJECT-TYPE
not all PCNtf messages are used to cancel requests, and a SYNTAX Counter32
single PCNtf message can cancel multiple requests." MAX-ACCESS read-only
::= { pcePcepPeerEntry 44 } STATUS current
DESCRIPTION
"The number of requests that have been received from this
peer for which a response with an ERO was sent. Such
responses indicate that a path was successfully computed by
the local PCEP entity."
::= { pcePcepPeerEntry 42 }
pcePcepPeerNumReqRcvdErrorSent OBJECT-TYPE pcePcepPeerNumReqRcvdNoPathSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests received from this peer that were "The number of requests that have been received from this
rejected by the local PCEP entity sending a PCErr message. peer for which a response with a NO-PATH object was sent.
Such responses indicate that the local PCEP entity could
not find a path to satisfy the request."
::= { pcePcepPeerEntry 43 }
This might be different than pcePcepPeerNumPCErrSent because pcePcepPeerNumReqRcvdCancelSent OBJECT-TYPE
not all PCErr messages are used to reject requests, and a SYNTAX Counter32
single PCErr message can reject multiple requests." MAX-ACCESS read-only
::= { pcePcepPeerEntry 45 } STATUS current
DESCRIPTION
"The number of requests received from this peer that were
canceled by the local PCEP entity sending a PCNtf message.
pcePcepPeerNumReqRcvdCancelRcvd OBJECT-TYPE This might be different than pcePcepPeerNumPCNtfSent because
SYNTAX Counter32 not all PCNtf messages are used to cancel requests, and a
MAX-ACCESS read-only single PCNtf message can cancel multiple requests."
STATUS current ::= { pcePcepPeerEntry 44 }
DESCRIPTION
"The number of requests that were received from the peer and
explicitly canceled by the peer sending a PCNtf."
::= { pcePcepPeerEntry 46 }
pcePcepPeerNumReqRcvdClosed OBJECT-TYPE pcePcepPeerNumReqRcvdErrorSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests that were received from the peer and "The number of requests received from this peer that were
implicitly canceled when the session they were received over rejected by the local PCEP entity sending a PCErr message.
was closed."
::= { pcePcepPeerEntry 47 }
pcePcepPeerNumRepRcvdUnknown OBJECT-TYPE This might be different than pcePcepPeerNumPCErrSent because
SYNTAX Counter32 not all PCErr messages are used to reject requests, and a
MAX-ACCESS read-only single PCErr message can reject multiple requests."
STATUS current ::= { pcePcepPeerEntry 45 }
DESCRIPTION
"The number of responses to unknown requests received from
this peer. A response to an unknown request is a response
whose RP object does not contain the request ID of any
request that is currently outstanding on the session."
::= { pcePcepPeerEntry 48 }
pcePcepPeerNumReqRcvdUnknown OBJECT-TYPE pcePcepPeerNumReqRcvdCancelRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of unknown requests that have been received from "The number of requests that were received from the peer and
a peer. An unknown request is a request whose RP object explicitly canceled by the peer sending a PCNtf."
contains a request ID of zero." ::= { pcePcepPeerEntry 46 }
::= { pcePcepPeerEntry 49 }
-- pcePcepPeerNumReqRcvdClosed OBJECT-TYPE
-- The PCEP Sessions Table SYNTAX Counter32
-- MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of requests that were received from the peer and
implicitly canceled when the session they were received over
was closed."
::= { pcePcepPeerEntry 47 }
pcePcepSessTable OBJECT-TYPE pcePcepPeerNumRepRcvdUnknown OBJECT-TYPE
SYNTAX SEQUENCE OF PcePcepSessEntry SYNTAX Counter32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of PCEP sessions that involve the local PCEP "The number of responses to unknown requests received from
entity. Each entry in this table represents a single this peer. A response to an unknown request is a response
session. The entries in this table are read-only. whose RP object does not contain the request ID of any
request that is currently outstanding on the session."
::= { pcePcepPeerEntry 48 }
An entry appears in this table when the corresponding PCEP pcePcepPeerNumReqRcvdUnknown OBJECT-TYPE
session transitions out of idle state. If the PCEP session SYNTAX Counter32
transitions back into idle state then the corresponding MAX-ACCESS read-only
entry in this table is removed." STATUS current
::= { pcePcepObjects 3 } DESCRIPTION
"The number of unknown requests that have been received from
a peer. An unknown request is a request whose RP object
contains a request ID of zero."
::= { pcePcepPeerEntry 49 }
pcePcepSessEntry OBJECT-TYPE --
SYNTAX PcePcepSessEntry -- The PCEP Sessions Table
MAX-ACCESS not-accessible --
STATUS current
DESCRIPTION
"This entry represents a single PCEP session in which the
local PCEP entity participates.
This entry exists only if the corresponding PCEP session has pcePcepSessTable OBJECT-TYPE
been initialized by some event, such as manual user SYNTAX SEQUENCE OF PcePcepSessEntry
configuration, autodiscovery of a peer, or an incoming TCP MAX-ACCESS not-accessible
connection." STATUS current
INDEX { pcePcepEntityIndex, DESCRIPTION
pcePcepPeerAddrType, "A table of PCEP sessions that involve the local PCEP
pcePcepPeerAddr, entity. Each entry in this table represents a single
pcePcepSessInitiator } session. The entries in this table are read-only.
::= { pcePcepSessTable 1 }
PcePcepSessEntry ::= SEQUENCE { An entry appears in this table when the corresponding PCEP
pcePcepSessInitiator INTEGER, session transitions out of idle state. If the PCEP session
pcePcepSessStateLastChange TimeStamp, transitions back into an idle state, then the corresponding
pcePcepSessState INTEGER, entry in this table is removed."
pcePcepSessConnectRetry Counter32, ::= { pcePcepObjects 3 }
pcePcepSessLocalID Unsigned32,
pcePcepSessRemoteID Unsigned32,
pcePcepSessKeepaliveTimer Unsigned32,
pcePcepSessPeerKeepaliveTimer Unsigned32,
pcePcepSessDeadTimer Unsigned32,
pcePcepSessPeerDeadTimer Unsigned32,
pcePcepSessKAHoldTimeRem Unsigned32,
pcePcepSessOverloaded TruthValue,
pcePcepSessOverloadTime Unsigned32,
pcePcepSessPeerOverloaded TruthValue,
pcePcepSessPeerOverloadTime Unsigned32,
pcePcepSessDiscontinuityTime TimeStamp,
pcePcepSessAvgRspTime Unsigned32,
pcePcepSessLWMRspTime Unsigned32,
pcePcepSessHWMRspTime Unsigned32,
pcePcepSessNumPCReqSent Counter32,
pcePcepSessNumPCReqRcvd Counter32,
pcePcepSessNumPCRepSent Counter32,
pcePcepSessNumPCRepRcvd Counter32,
pcePcepSessNumPCErrSent Counter32,
pcePcepSessNumPCErrRcvd Counter32,
pcePcepSessNumPCNtfSent Counter32,
pcePcepSessNumPCNtfRcvd Counter32,
pcePcepSessNumKeepaliveSent Counter32,
pcePcepSessNumKeepaliveRcvd Counter32,
pcePcepSessNumUnknownRcvd Counter32,
pcePcepSessNumCorruptRcvd Counter32,
pcePcepSessNumReqSent Counter32,
pcePcepSessNumSvecSent Counter32,
pcePcepSessNumSvecReqSent Counter32,
pcePcepSessNumReqSentPendRep Counter32,
pcePcepSessNumReqSentEroRcvd Counter32,
pcePcepSessNumReqSentNoPathRcvd Counter32,
pcePcepSessNumReqSentCancelRcvd Counter32,
pcePcepSessNumReqSentErrorRcvd Counter32,
pcePcepSessNumReqSentTimeout Counter32,
pcePcepSessNumReqSentCancelSent Counter32,
pcePcepSessNumReqRcvd Counter32,
pcePcepSessNumSvecRcvd Counter32,
pcePcepSessNumSvecReqRcvd Counter32,
pcePcepSessNumReqRcvdPendRep Counter32,
pcePcepSessNumReqRcvdEroSent Counter32,
pcePcepSessNumReqRcvdNoPathSent Counter32,
pcePcepSessNumReqRcvdCancelSent Counter32,
pcePcepSessNumReqRcvdErrorSent Counter32,
pcePcepSessNumReqRcvdCancelRcvd Counter32,
pcePcepSessNumRepRcvdUnknown Counter32,
pcePcepSessNumReqRcvdUnknown Counter32
}
pcePcepSessInitiator OBJECT-TYPE pcePcepSessEntry OBJECT-TYPE
SYNTAX INTEGER { SYNTAX PcePcepSessEntry
local(1), MAX-ACCESS not-accessible
remote(2) STATUS current
} DESCRIPTION
MAX-ACCESS not-accessible "This entry represents a single PCEP session in which the
STATUS current local PCEP entity participates.
DESCRIPTION
"The initiator of the session, that is, whether the TCP
connection was initiated by the local PCEP entity or the
peer.
There is a window during session initialization where two This entry exists only if the corresponding PCEP session has
sessions can exist between a pair of PCEP speakers, each been initialized by some event, such as manual user
initiated by one of the speakers. One of these sessions is configuration, auto-discovery of a peer, or an incoming TCP
always discarded before it leaves OpenWait state. However, connection."
before it is discarded, two sessions to the given peer INDEX { pcePcepEntityIndex,
appear transiently in this MIB module. The sessions are pcePcepPeerAddrType,
distinguished by who initiated them, and so this field is an pcePcepPeerAddr,
index for the pcePcepSessTable." pcePcepSessInitiator }
::= { pcePcepSessEntry 1 } ::= { pcePcepSessTable 1 }
pcePcepSessStateLastChange OBJECT-TYPE PcePcepSessEntry ::= SEQUENCE {
SYNTAX TimeStamp pcePcepSessInitiator INTEGER,
MAX-ACCESS read-only pcePcepSessStateLastChange TimeStamp,
STATUS current pcePcepSessState INTEGER,
DESCRIPTION pcePcepSessConnectRetry Counter32,
"The value of sysUpTime at the time this session entered its pcePcepSessLocalID Unsigned32,
current state as denoted by the pcePcepSessState object." pcePcepSessRemoteID Unsigned32,
::= { pcePcepSessEntry 2 } pcePcepSessKeepaliveTimer Unsigned32,
pcePcepSessPeerKeepaliveTimer Unsigned32,
pcePcepSessDeadTimer Unsigned32,
pcePcepSessPeerDeadTimer Unsigned32,
pcePcepSessKAHoldTimeRem Unsigned32,
pcePcepSessOverloaded TruthValue,
pcePcepSessOverloadTime Unsigned32,
pcePcepSessPeerOverloaded TruthValue,
pcePcepSessPeerOverloadTime Unsigned32,
pcePcepSessDiscontinuityTime TimeStamp,
pcePcepSessAvgRspTime Unsigned32,
pcePcepSessLWMRspTime Unsigned32,
pcePcepSessHWMRspTime Unsigned32,
pcePcepSessNumPCReqSent Counter32,
pcePcepSessNumPCReqRcvd Counter32,
pcePcepSessNumPCRepSent Counter32,
pcePcepSessNumPCRepRcvd Counter32,
pcePcepSessNumPCErrSent Counter32,
pcePcepSessNumPCErrRcvd Counter32,
pcePcepSessNumPCNtfSent Counter32,
pcePcepSessNumPCNtfRcvd Counter32,
pcePcepSessNumKeepaliveSent Counter32,
pcePcepSessNumKeepaliveRcvd Counter32,
pcePcepSessNumUnknownRcvd Counter32,
pcePcepSessNumCorruptRcvd Counter32,
pcePcepSessNumReqSent Counter32,
pcePcepSessNumSvecSent Counter32,
pcePcepSessNumSvecReqSent Counter32,
pcePcepSessNumReqSentPendRep Counter32,
pcePcepSessNumReqSentEroRcvd Counter32,
pcePcepSessNumReqSentNoPathRcvd Counter32,
pcePcepSessNumReqSentCancelRcvd Counter32,
pcePcepSessNumReqSentErrorRcvd Counter32,
pcePcepSessNumReqSentTimeout Counter32,
pcePcepSessNumReqSentCancelSent Counter32,
pcePcepSessNumReqRcvd Counter32,
pcePcepSessNumSvecRcvd Counter32,
pcePcepSessNumSvecReqRcvd Counter32,
pcePcepSessNumReqRcvdPendRep Counter32,
pcePcepSessNumReqRcvdEroSent Counter32,
pcePcepSessNumReqRcvdNoPathSent Counter32,
pcePcepSessNumReqRcvdCancelSent Counter32,
pcePcepSessNumReqRcvdErrorSent Counter32,
pcePcepSessNumReqRcvdCancelRcvd Counter32,
pcePcepSessNumRepRcvdUnknown Counter32,
pcePcepSessNumReqRcvdUnknown Counter32
}
pcePcepSessState OBJECT-TYPE pcePcepSessInitiator OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
tcpPending(1), local(1),
openWait(2), remote(2)
keepWait(3), }
sessionUp(4) MAX-ACCESS not-accessible
} STATUS current
MAX-ACCESS read-only DESCRIPTION
STATUS current "The initiator of the session; that is, whether the TCP
DESCRIPTION connection was initiated by the local PCEP entity or the
"The current state of the session. peer.
The set of possible states excludes the idle state since There is a window during session initialization where two
entries do not exist in this table in the idle state." sessions can exist between a pair of PCEP speakers, each
::= { pcePcepSessEntry 3 } initiated by one of the speakers. One of these sessions is
always discarded before it leaves OpenWait state. However,
before it is discarded, two sessions to the given peer
appear transiently in this MIB module. The sessions are
distinguished by who initiated them, and so this field is an
index for pcePcepSessTable."
::= { pcePcepSessEntry 1 }
pcePcepSessConnectRetry OBJECT-TYPE pcePcepSessStateLastChange OBJECT-TYPE
SYNTAX Counter32 SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of times that the local PCEP entity has "The value of sysUpTime at the time this session entered its
attempted to establish a TCP connection for this session current state as denoted by the pcePcepSessState object."
without success. The PCEP entity gives up when this ::= { pcePcepSessEntry 2 }
reaches pcePcepEntityConnectMaxRetry."
::= { pcePcepSessEntry 4 }
pcePcepSessLocalID OBJECT-TYPE pcePcepSessState OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX INTEGER {
MAX-ACCESS read-only tcpPending(1),
STATUS current openWait(2),
DESCRIPTION keepWait(3),
"The value of the PCEP session ID used by the local PCEP sessionUp(4)
entity in the Open message for this session. }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The current state of the session.
If pcePcepSessState is tcpPending then this is the session The set of possible states excludes the idle state since
ID that will be used in the Open message. Otherwise, this entries do not exist in this table in the idle state."
is the session ID that was sent in the Open message." ::= { pcePcepSessEntry 3 }
::= { pcePcepSessEntry 5 }
pcePcepSessRemoteID OBJECT-TYPE pcePcepSessConnectRetry OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the PCEP session ID used by the peer in its "The number of times that the local PCEP entity has
Open message for this session. attempted to establish a TCP connection for this session
without success. The PCEP entity gives up when this
reaches pcePcepEntityConnectMaxRetry."
::= { pcePcepSessEntry 4 }
If pcePcepSessState is tcpPending or openWait then this pcePcepSessLocalID OBJECT-TYPE
field is not used and MUST be set to zero." SYNTAX Unsigned32 (0..255)
::= { pcePcepSessEntry 6 } MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of the PCEP session ID used by the local PCEP
entity in the Open message for this session.
pcePcepSessKeepaliveTimer OBJECT-TYPE If pcePcepSessState is tcpPending, then this is the session
SYNTAX Unsigned32 (0..255) ID that will be used in the Open message. Otherwise, this
UNITS "seconds" is the session ID that was sent in the Open message."
MAX-ACCESS read-only ::= { pcePcepSessEntry 5 }
STATUS current
DESCRIPTION
"The agreed maximum interval at which the local PCEP entity
transmits PCEP messages on this PCEP session. Zero means
that the local PCEP entity never sends Keepalives on this
session.
This field is used if and only if pcePcepSessState is pcePcepSessRemoteID OBJECT-TYPE
sessionUp. Otherwise, it is not used and MUST be set to SYNTAX Unsigned32 (0..255)
zero." MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of the PCEP session ID used by the peer in its
Open message for this session.
::= { pcePcepSessEntry 7 } If pcePcepSessState is tcpPending or openWait, then this
field is not used and MUST be set to zero."
::= { pcePcepSessEntry 6 }
pcePcepSessPeerKeepaliveTimer OBJECT-TYPE pcePcepSessKeepaliveTimer OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The agreed maximum interval at which the peer transmits PCEP "The agreed maximum interval at which the local PCEP entity
messages on this PCEP session. Zero means that the peer transmits PCEP messages on this PCEP session. Zero means
never sends Keepalives on this session. that the local PCEP entity never sends Keepalives on this
session.
This field is used if and only if pcePcepSessState is This field is used if and only if pcePcepSessState is
sessionUp. Otherwise, it is not used and MUST be set to sessionUp. Otherwise, it is not used and MUST be set to
zero." zero."
::= { pcePcepSessEntry 8 } ::= { pcePcepSessEntry 7 }
pcePcepSessDeadTimer OBJECT-TYPE pcePcepSessPeerKeepaliveTimer OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The DeadTimer interval for this PCEP session." "The agreed maximum interval at which the peer transmits PCEP
::= { pcePcepSessEntry 9 } messages on this PCEP session. Zero means that the peer
never sends Keepalives on this session.
pcePcepSessPeerDeadTimer OBJECT-TYPE This field is used if and only if pcePcepSessState is
SYNTAX Unsigned32 (0..255) sessionUp. Otherwise, it is not used and MUST be set to
UNITS "seconds" zero."
MAX-ACCESS read-only ::= { pcePcepSessEntry 8 }
STATUS current
DESCRIPTION
"The peer's DeadTimer interval for this PCEP session.
If pcePcepSessState is tcpPending or openWait then this pcePcepSessDeadTimer OBJECT-TYPE
field is not used and MUST be set to zero." SYNTAX Unsigned32 (0..255)
::= { pcePcepSessEntry 10 } UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The DeadTimer interval for this PCEP session."
::= { pcePcepSessEntry 9 }
pcePcepSessKAHoldTimeRem OBJECT-TYPE pcePcepSessPeerDeadTimer OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The keep alive hold time remaining for this session. "The peer's DeadTimer interval for this PCEP session.
If pcePcepSessState is tcpPending or openWait then this If pcePcepSessState is tcpPending or openWait, then this
field is not used and MUST be set to zero." field is not used and MUST be set to zero."
::= { pcePcepSessEntry 10 }
::= { pcePcepSessEntry 11 } pcePcepSessKAHoldTimeRem OBJECT-TYPE
SYNTAX Unsigned32 (0..255)
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Keepalive hold time remaining for this session.
pcePcepSessOverloaded OBJECT-TYPE If pcePcepSessState is tcpPending or openWait, then this
SYNTAX TruthValue field is not used and MUST be set to zero."
MAX-ACCESS read-only ::= { pcePcepSessEntry 11 }
STATUS current
DESCRIPTION
"If the local PCEP entity has informed the peer that it is
currently overloaded, then this is set to true. Otherwise,
it is set to false."
::= { pcePcepSessEntry 12 }
pcePcepSessOverloadTime OBJECT-TYPE pcePcepSessOverloaded OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX TruthValue
UNITS "seconds" MAX-ACCESS read-only
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "If the local PCEP entity has informed the peer that it is
"The interval of time that is remaining until the local PCEP currently overloaded, then this is set to true. Otherwise,
entity will cease to be overloaded on this session. it is set to false."
::= { pcePcepSessEntry 12 }
This field is only used if pcePcepSessOverloaded is set to pcePcepSessOverloadTime OBJECT-TYPE
true. Otherwise, it is not used and MUST be set to zero." SYNTAX Unsigned32
::= { pcePcepSessEntry 13 } UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The interval of time that is remaining until the local PCEP
entity will cease to be overloaded on this session.
pcePcepSessPeerOverloaded OBJECT-TYPE This field is only used if pcePcepSessOverloaded is set to
SYNTAX TruthValue true. Otherwise, it is not used and MUST be set to zero."
MAX-ACCESS read-only ::= { pcePcepSessEntry 13 }
STATUS current
DESCRIPTION
"If the peer has informed the local PCEP entity that it is
currently overloaded, then this is set to true. Otherwise,
it is set to false."
::= { pcePcepSessEntry 14 }
pcePcepSessPeerOverloadTime OBJECT-TYPE pcePcepSessPeerOverloaded OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX TruthValue
UNITS "seconds" MAX-ACCESS read-only
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "If the peer has informed the local PCEP entity that it is
"The interval of time that is remaining until the peer will currently overloaded, then this is set to true. Otherwise,
cease to be overloaded. If it is not known how long the it is set to false."
peer will stay in overloaded state, this field is set to ::= { pcePcepSessEntry 14 }
zero.
This field is only used if pcePcepSessPeerOverloaded is set pcePcepSessPeerOverloadTime OBJECT-TYPE
to true. Otherwise, it is not used and MUST be set to SYNTAX Unsigned32
zero." UNITS "seconds"
::= { pcePcepSessEntry 15 } MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The interval of time that is remaining until the peer will
cease to be overloaded. If it is not known how long the
peer will stay in overloaded state, this field is set to
zero.
pcePcepSessDiscontinuityTime OBJECT-TYPE This field is only used if pcePcepSessPeerOverloaded is set
SYNTAX TimeStamp to true. Otherwise, it is not used and MUST be set to
MAX-ACCESS read-only zero."
STATUS current ::= { pcePcepSessEntry 15 }
DESCRIPTION
"The value of sysUpTime at the time that the statistics in
this row were last reset."
::= { pcePcepSessEntry 16 }
pcePcepSessAvgRspTime OBJECT-TYPE pcePcepSessDiscontinuityTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX TimeStamp
UNITS "milliseconds" MAX-ACCESS read-only
MAX-ACCESS read-only STATUS current
STATUS current DESCRIPTION
DESCRIPTION "The value of sysUpTime at the time that the statistics in
"The average response time for this peer on this session. this row were last reset."
::= { pcePcepSessEntry 16 }
If an average response time has not been calculated for this pcePcepSessAvgRspTime OBJECT-TYPE
peer then this object has the value zero." SYNTAX Unsigned32
::= { pcePcepSessEntry 17 } UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The average response time for this peer on this session.
pcePcepSessLWMRspTime OBJECT-TYPE If an average response time has not been calculated for this
SYNTAX Unsigned32 peer, then this object has the value zero."
UNITS "milliseconds" ::= { pcePcepSessEntry 17 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The smallest (low-water mark) response time seen from this
peer on this session.
If no responses have been received from this peer then this pcePcepSessLWMRspTime OBJECT-TYPE
object has the value zero." SYNTAX Unsigned32
::= { pcePcepSessEntry 18 } UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The smallest (low-water mark) response time seen from this
peer on this session.
pcePcepSessHWMRspTime OBJECT-TYPE If no responses have been received from this peer, then this
SYNTAX Unsigned32 object has the value zero."
UNITS "milliseconds" ::= { pcePcepSessEntry 18 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The greatest (high-water mark) response time seen from this
peer on this session.
If no responses have been received from this peer then this pcePcepSessHWMRspTime OBJECT-TYPE
object has the value zero." SYNTAX Unsigned32
UNITS "milliseconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The greatest (high-water mark) response time seen from this
peer on this session.
::= { pcePcepSessEntry 19 } If no responses have been received from this peer, then this
object has the value zero."
::= { pcePcepSessEntry 19 }
pcePcepSessNumPCReqSent OBJECT-TYPE pcePcepSessNumPCReqSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of PCReq messages sent on this session." "The number of PCReq messages sent on this session."
::= { pcePcepSessEntry 20 } ::= { pcePcepSessEntry 20 }
pcePcepSessNumPCReqRcvd OBJECT-TYPE pcePcepSessNumPCReqRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of PCReq messages received on this session." "The number of PCReq messages received on this session."
::= { pcePcepSessEntry 21 } ::= { pcePcepSessEntry 21 }
pcePcepSessNumPCRepSent OBJECT-TYPE pcePcepSessNumPCRepSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of PCRep messages sent on this session." "The number of PCRep messages sent on this session."
::= { pcePcepSessEntry 22 } ::= { pcePcepSessEntry 22 }
pcePcepSessNumPCRepRcvd OBJECT-TYPE pcePcepSessNumPCRepRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of PCRep messages received on this session." "The number of PCRep messages received on this session."
::= { pcePcepSessEntry 23 } ::= { pcePcepSessEntry 23 }
pcePcepSessNumPCErrSent OBJECT-TYPE pcePcepSessNumPCErrSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of PCErr messages sent on this session." "The number of PCErr messages sent on this session."
::= { pcePcepSessEntry 24 } ::= { pcePcepSessEntry 24 }
pcePcepSessNumPCErrRcvd OBJECT-TYPE pcePcepSessNumPCErrRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of PCErr messages received on this session." "The number of PCErr messages received on this session."
::= { pcePcepSessEntry 25 }
::= { pcePcepSessEntry 25 } pcePcepSessNumPCNtfSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of PCNtf messages sent on this session."
::= { pcePcepSessEntry 26 }
pcePcepSessNumPCNtfSent OBJECT-TYPE pcePcepSessNumPCNtfRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of PCNtf messages sent on this session." "The number of PCNtf messages received on this session."
::= { pcePcepSessEntry 26 } ::= { pcePcepSessEntry 27 }
pcePcepSessNumPCNtfRcvd OBJECT-TYPE pcePcepSessNumKeepaliveSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of PCNtf messages received on this session." "The number of Keepalive messages sent on this session."
::= { pcePcepSessEntry 27 } ::= { pcePcepSessEntry 28 }
pcePcepSessNumKeepaliveSent OBJECT-TYPE pcePcepSessNumKeepaliveRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Keepalive messages sent on this session." "The number of Keepalive messages received on this session."
::= { pcePcepSessEntry 28 } ::= { pcePcepSessEntry 29 }
pcePcepSessNumKeepaliveRcvd OBJECT-TYPE pcePcepSessNumUnknownRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Keepalive messages received on this session." "The number of unknown messages received on this session."
::= { pcePcepSessEntry 29 } ::= { pcePcepSessEntry 30 }
pcePcepSessNumUnknownRcvd OBJECT-TYPE pcePcepSessNumCorruptRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of unknown messages received on this session." "The number of corrupted PCEP messages received on this
::= { pcePcepSessEntry 30 } session."
::= { pcePcepSessEntry 31 }
pcePcepSessNumCorruptRcvd OBJECT-TYPE pcePcepSessNumReqSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of corrupted PCEP message received on this "The number of requests sent on this session. A request
session." corresponds 1:1 with an RP object in a PCReq message.
::= { pcePcepSessEntry 31 }
pcePcepSessNumReqSent OBJECT-TYPE This might be greater than pcePcepSessNumPCReqSent because
SYNTAX Counter32 multiple requests can be batched into a single PCReq
MAX-ACCESS read-only message."
STATUS current ::= { pcePcepSessEntry 32 }
DESCRIPTION
"The number of requests sent on this session. A request
corresponds 1:1 with an RP object in a PCReq message.
This might be greater than pcePcepSessNumPCReqSent because pcePcepSessNumSvecSent OBJECT-TYPE
multiple requests can be batched into a single PCReq SYNTAX Counter32
message." MAX-ACCESS read-only
::= { pcePcepSessEntry 32 } STATUS current
DESCRIPTION
"The number of SVEC objects sent on this session in PCReq
messages. An SVEC object represents a set of synchronized
requests."
::= { pcePcepSessEntry 33 }
pcePcepSessNumSvecSent OBJECT-TYPE pcePcepSessNumSvecReqSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of SVEC objects sent on this session in PCReq "The number of requests sent on this session that appeared in
messages. An SVEC object represents a set of synchronized one or more SVEC objects."
requests." ::= { pcePcepSessEntry 34 }
::= { pcePcepSessEntry 33 }
pcePcepSessNumSvecReqSent OBJECT-TYPE pcePcepSessNumReqSentPendRep OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests sent on this session that appeared in "The number of requests that have been sent on this session
one or more SVEC objects." for which a response is still pending."
::= { pcePcepSessEntry 34 } ::= { pcePcepSessEntry 35 }
pcePcepSessNumReqSentPendRep OBJECT-TYPE pcePcepSessNumReqSentEroRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests that have been sent on this session "The number of successful responses received on this session.
for which a response is still pending." A response corresponds 1:1 with an RP object in a PCRep
::= { pcePcepSessEntry 35 } message. A successful response is a response for which an
ERO was successfully computed."
::= { pcePcepSessEntry 36 }
pcePcepSessNumReqSentEroRcvd OBJECT-TYPE pcePcepSessNumReqSentNoPathRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of successful responses received on this session. "The number of unsuccessful responses received on this
A response corresponds 1:1 with an RP object in a PCRep session. A response corresponds 1:1 with an RP object in a
message. A successful response is a response for which an PCRep message. An unsuccessful response is a response with
ERO was successfully computed." a NO-PATH object."
::= { pcePcepSessEntry 36 }
pcePcepSessNumReqSentNoPathRcvd OBJECT-TYPE ::= { pcePcepSessEntry 37 }
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of unsuccessful responses received on this
session. A response corresponds 1:1 with an RP object in a
PCRep message. An unsuccessful response is a response with
a NO-PATH object."
::= { pcePcepSessEntry 37 }
pcePcepSessNumReqSentCancelRcvd OBJECT-TYPE pcePcepSessNumReqSentCancelRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests sent on this session that were "The number of requests sent on this session that were
cancelled by the peer with a PCNtf message. canceled by the peer with a PCNtf message.
This might be different than pcePcepSessNumPCNtfRcvd because This might be different than pcePcepSessNumPCNtfRcvd because
not all PCNtf messages are used to cancel requests, and a not all PCNtf messages are used to cancel requests, and a
single PCNtf message can cancel multiple requests." single PCNtf message can cancel multiple requests."
::= { pcePcepSessEntry 38 } ::= { pcePcepSessEntry 38 }
pcePcepSessNumReqSentErrorRcvd OBJECT-TYPE pcePcepSessNumReqSentErrorRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests sent on this session that were "The number of requests sent on this session that were
rejected by the peer with a PCErr message. rejected by the peer with a PCErr message.
This might be different than pcePcepSessNumPCErrRcvd because This might be different than pcePcepSessNumPCErrRcvd because
not all PCErr messages are used to reject requests, and a not all PCErr messages are used to reject requests, and a
single PCErr message can reject multiple requests." single PCErr message can reject multiple requests."
::= { pcePcepSessEntry 39 } ::= { pcePcepSessEntry 39 }
pcePcepSessNumReqSentTimeout OBJECT-TYPE pcePcepSessNumReqSentTimeout OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests sent on this session that have been "The number of requests sent on this session that have been
sent to a peer and have been abandoned because the peer has sent to a peer and have been abandoned because the peer has
taken too long to respond to them." taken too long to respond to them."
::= { pcePcepSessEntry 40 } ::= { pcePcepSessEntry 40 }
pcePcepSessNumReqSentCancelSent OBJECT-TYPE pcePcepSessNumReqSentCancelSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests sent on this session that were sent "The number of requests sent on this session that were sent
to the peer and explicitly canceled by the local PCEP to the peer and explicitly canceled by the local PCEP
entity sending a PCNtf." entity sending a PCNtf."
::= { pcePcepSessEntry 41 } ::= { pcePcepSessEntry 41 }
pcePcepSessNumReqRcvd OBJECT-TYPE pcePcepSessNumReqRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests received on this session. A request "The number of requests received on this session. A request
corresponds 1:1 with an RP object in a PCReq message. corresponds 1:1 with an RP object in a PCReq message.
This might be greater than pcePcepSessNumPCReqRcvd because This might be greater than pcePcepSessNumPCReqRcvd because
multiple requests can be batched into a single PCReq multiple requests can be batched into a single PCReq
message." message."
::= { pcePcepSessEntry 42 } ::= { pcePcepSessEntry 42 }
pcePcepSessNumSvecRcvd OBJECT-TYPE pcePcepSessNumSvecRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of SVEC objects received on this session in PCReq "The number of SVEC objects received on this session in PCReq
messages. An SVEC object represents a set of synchronized messages. An SVEC object represents a set of synchronized
requests." requests."
::= { pcePcepSessEntry 43 } ::= { pcePcepSessEntry 43 }
pcePcepSessNumSvecReqRcvd OBJECT-TYPE pcePcepSessNumSvecReqRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests received on this session that "The number of requests received on this session that
appeared in one or more SVEC objects." appeared in one or more SVEC objects."
::= { pcePcepSessEntry 44 } ::= { pcePcepSessEntry 44 }
pcePcepSessNumReqRcvdPendRep OBJECT-TYPE pcePcepSessNumReqRcvdPendRep OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests that have been received on this "The number of requests that have been received on this
session for which a response is still pending." session for which a response is still pending."
::= { pcePcepSessEntry 45 } ::= { pcePcepSessEntry 45 }
pcePcepSessNumReqRcvdEroSent OBJECT-TYPE pcePcepSessNumReqRcvdEroSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of successful responses sent on this session. A "The number of successful responses sent on this session. A
response corresponds 1:1 with an RP object in a PCRep response corresponds 1:1 with an RP object in a PCRep
message. A successful response is a response for which an message. A successful response is a response for which an
ERO was successfully computed." ERO was successfully computed."
::= { pcePcepSessEntry 46 } ::= { pcePcepSessEntry 46 }
pcePcepSessNumReqRcvdNoPathSent OBJECT-TYPE pcePcepSessNumReqRcvdNoPathSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of unsuccessful responses sent on this session. "The number of unsuccessful responses sent on this session.
A response corresponds 1:1 with an RP object in a PCRep A response corresponds 1:1 with an RP object in a PCRep
message. An unsuccessful response is a response with a message. An unsuccessful response is a response with a
NO-PATH object." NO-PATH object."
::= { pcePcepSessEntry 47 } ::= { pcePcepSessEntry 47 }
pcePcepSessNumReqRcvdCancelSent OBJECT-TYPE pcePcepSessNumReqRcvdCancelSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests received on this session that were "The number of requests received on this session that were
cancelled by the local PCEP entity sending a PCNtf message. canceled by the local PCEP entity sending a PCNtf message.
This might be different than pcePcepSessNumPCNtfSent because This might be different than pcePcepSessNumPCNtfSent because
not all PCNtf messages are used to cancel requests, and a not all PCNtf messages are used to cancel requests, and a
single PCNtf message can cancel multiple requests." single PCNtf message can cancel multiple requests."
::= { pcePcepSessEntry 48 } ::= { pcePcepSessEntry 48 }
pcePcepSessNumReqRcvdErrorSent OBJECT-TYPE pcePcepSessNumReqRcvdErrorSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests received on this session that were "The number of requests received on this session that were
rejected by the local PCEP entity sending a PCErr message. rejected by the local PCEP entity sending a PCErr message.
This might be different than pcePcepSessNumPCErrSent because This might be different than pcePcepSessNumPCErrSent because
not all PCErr messages are used to reject requests, and a not all PCErr messages are used to reject requests, and a
single PCErr message can reject multiple requests." single PCErr message can reject multiple requests."
::= { pcePcepSessEntry 49 } ::= { pcePcepSessEntry 49 }
pcePcepSessNumReqRcvdCancelRcvd OBJECT-TYPE pcePcepSessNumReqRcvdCancelRcvd OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests that were received on this session "The number of requests that were received on this session
and explicitly canceled by the peer sending a PCNtf." and explicitly canceled by the peer sending a PCNtf."
::= { pcePcepSessEntry 50 }
pcePcepSessNumRepRcvdUnknown OBJECT-TYPE ::= { pcePcepSessEntry 50 }
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of responses to unknown requests received on this
session. A response to an unknown request is a response
whose RP object does not contain the request ID of any
request that is currently outstanding on the session."
::= { pcePcepSessEntry 51 }
pcePcepSessNumReqRcvdUnknown OBJECT-TYPE pcePcepSessNumRepRcvdUnknown OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of unknown requests that have been received on "The number of responses to unknown requests received on this
this session. An unknown request is a request whose RP session. A response to an unknown request is a response
object contains a request ID of zero." whose RP object does not contain the request ID of any
::= { pcePcepSessEntry 52 } request that is currently outstanding on the session."
::= { pcePcepSessEntry 51 }
--- pcePcepSessNumReqRcvdUnknown OBJECT-TYPE
--- Notifications Configuration SYNTAX Counter32
--- MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of unknown requests that have been received on
this session. An unknown request is a request whose RP
object contains a request ID of zero."
::= { pcePcepSessEntry 52 }
pcePcepNotificationsMaxRate OBJECT-TYPE ---
SYNTAX Unsigned32 --- Notifications Configuration
MAX-ACCESS read-write ---
STATUS current
DESCRIPTION
"This variable indicates the maximum number of
notifications issued per second. If events occur
more rapidly, the implementation may simply fail to
emit these notifications during that period, or may
queue them until an appropriate time. A value of 0
means no notifications are emitted and all should be
discarded (that is, not queued)."
::= { pcePcepObjects 4 }
--- pcePcepNotificationsMaxRate OBJECT-TYPE
--- Notifications SYNTAX Unsigned32
--- MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This variable indicates the maximum number of
notifications issued per second. If events occur
more rapidly, the implementation may simply fail to
emit these notifications during that period or may
queue them until an appropriate time. A value of zero
means no notifications are emitted and all should be
discarded (that is, not queued)."
::= { pcePcepObjects 4 }
pcePcepSessUp NOTIFICATION-TYPE ---
OBJECTS { --- Notifications
pcePcepSessState, ---
pcePcepSessStateLastChange
}
STATUS current
DESCRIPTION
"This notification is sent when the value of
'pcePcepSessState' enters the 'sessionUp' state."
::= { pcePcepNotifications 1 }
pcePcepSessDown NOTIFICATION-TYPE pcePcepSessUp NOTIFICATION-TYPE
OBJECTS { OBJECTS {
pcePcepSessState, pcePcepSessState,
pcePcepSessStateLastChange pcePcepSessStateLastChange
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is sent when the value of "This notification is sent when the value of
'pcePcepSessState' leaves the 'sessionUp' state." pcePcepSessState enters the sessionUp state."
::= { pcePcepNotifications 2 } ::= { pcePcepNotifications 1 }
pcePcepSessLocalOverload NOTIFICATION-TYPE pcePcepSessDown NOTIFICATION-TYPE
OBJECTS { OBJECTS {
pcePcepSessOverloaded, pcePcepSessState,
pcePcepSessOverloadTime pcePcepSessStateLastChange
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is sent when the local PCEP entity enters "This notification is sent when the value of
overload state for a peer." pcePcepSessState leaves the sessionUp state."
::= { pcePcepNotifications 3 } ::= { pcePcepNotifications 2 }
pcePcepSessLocalOverloadClear NOTIFICATION-TYPE pcePcepSessLocalOverload NOTIFICATION-TYPE
OBJECTS { OBJECTS {
pcePcepSessOverloaded pcePcepSessOverloaded,
} pcePcepSessOverloadTime
STATUS current }
DESCRIPTION STATUS current
"This notification is sent when the local PCEP entity leaves DESCRIPTION
overload state for a peer." "This notification is sent when the local PCEP entity enters
::= { pcePcepNotifications 4 } overload state for a peer."
::= { pcePcepNotifications 3 }
pcePcepSessPeerOverload NOTIFICATION-TYPE pcePcepSessLocalOverloadClear NOTIFICATION-TYPE
OBJECTS { OBJECTS {
pcePcepSessPeerOverloaded, pcePcepSessOverloaded
pcePcepSessPeerOverloadTime }
} STATUS current
STATUS current DESCRIPTION
DESCRIPTION "This notification is sent when the local PCEP entity leaves
"This notification is sent when a peer enters overload overload state for a peer."
state." ::= { pcePcepNotifications 4 }
::= { pcePcepNotifications 5 }
pcePcepSessPeerOverloadClear NOTIFICATION-TYPE pcePcepSessPeerOverload NOTIFICATION-TYPE
OBJECTS { OBJECTS {
pcePcepSessPeerOverloaded pcePcepSessPeerOverloaded,
} pcePcepSessPeerOverloadTime
STATUS current }
DESCRIPTION STATUS current
"This notification is sent when a peer leaves overload DESCRIPTION
state." "This notification is sent when a peer enters overload
::= { pcePcepNotifications 6 } state."
::= { pcePcepNotifications 5 }
-- pcePcepSessPeerOverloadClear NOTIFICATION-TYPE
-- Module Conformance Statement OBJECTS {
-- pcePcepSessPeerOverloaded
}
STATUS current
DESCRIPTION
"This notification is sent when a peer leaves overload
state."
::= { pcePcepNotifications 6 }
pcePcepCompliances --
OBJECT IDENTIFIER ::= { pcePcepConformance 1 } -- Module Conformance Statement
--
pcePcepGroups pcePcepCompliances
OBJECT IDENTIFIER ::= { pcePcepConformance 2 } OBJECT IDENTIFIER ::= { pcePcepConformance 1 }
-- pcePcepGroups
-- Read-Only Compliance OBJECT IDENTIFIER ::= { pcePcepConformance 2 }
--
pcePcepModuleReadOnlyCompliance MODULE-COMPLIANCE --
STATUS current -- Read-Only Compliance
DESCRIPTION --
"The Module is implemented with support for read-only. In
other words, only monitoring is available by implementing
this MODULE-COMPLIANCE."
MODULE -- this module pcePcepModuleReadOnlyCompliance MODULE-COMPLIANCE
MANDATORY-GROUPS { STATUS current
pcePcepGeneralGroup, DESCRIPTION
pcePcepNotificationsGroup "The module is implemented with support for read-only. In
} other words, only monitoring is available by implementing
this MODULE-COMPLIANCE."
OBJECT pcePcepEntityAddrType MODULE -- this module
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } MANDATORY-GROUPS {
DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support pcePcepGeneralGroup,
is required." pcePcepNotificationsGroup
}
OBJECT pcePcepPeerAddrType OBJECT pcePcepEntityAddrType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support DESCRIPTION "Only unknown(0), ipv4(1), and ipv6(2) support
is required." is required."
::= { pcePcepCompliances 1 } -- The following restriction is commented out because of a limitation
-- in SMIv2 which does not allow index objects to be restricted in
-- scope. Nevertheless, this object is intended to be restricted in
-- scope, as follows.
--
-- OBJECT pcePcepPeerAddrType
-- SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
-- DESCRIPTION "Only unknown(0), ipv4(1), and ipv6(2) support
-- is required."
-- units of conformance ::= { pcePcepCompliances 1 }
pcePcepGeneralGroup OBJECT-GROUP -- units of conformance
OBJECTS { pcePcepEntityAdminStatus,
pcePcepEntityOperStatus,
pcePcepEntityAddrType,
pcePcepEntityAddr,
pcePcepEntityConnectTimer,
pcePcepEntityConnectMaxRetry,
pcePcepEntityInitBackoffTimer,
pcePcepEntityMaxBackoffTimer,
pcePcepEntityOpenWaitTimer,
pcePcepEntityKeepWaitTimer,
pcePcepEntityKeepAliveTimer,
pcePcepEntityDeadTimer,
pcePcepEntityAllowNegotiation,
pcePcepEntityMaxKeepAliveTimer,
pcePcepEntityMaxDeadTimer,
pcePcepEntityMinKeepAliveTimer,
pcePcepEntityMinDeadTimer,
pcePcepEntitySyncTimer,
pcePcepEntityRequestTimer,
pcePcepEntityMaxSessions,
pcePcepEntityMaxUnknownReqs,
pcePcepEntityMaxUnknownMsgs,
pcePcepPeerRole,
pcePcepPeerDiscontinuityTime,
pcePcepPeerInitiateSession,
pcePcepPeerSessionExists,
pcePcepPeerNumSessSetupOK,
pcePcepPeerNumSessSetupFail,
pcePcepPeerSessionUpTime,
pcePcepPeerSessionFailTime,
pcePcepPeerSessionFailUpTime,
pcePcepPeerAvgRspTime,
pcePcepPeerLWMRspTime,
pcePcepPeerHWMRspTime,
pcePcepPeerNumPCReqSent,
pcePcepPeerNumPCReqRcvd,
pcePcepPeerNumPCRepSent,
pcePcepPeerNumPCRepRcvd,
pcePcepPeerNumPCErrSent,
pcePcepPeerNumPCErrRcvd,
pcePcepPeerNumPCNtfSent,
pcePcepPeerNumPCNtfRcvd,
pcePcepPeerNumKeepaliveSent,
pcePcepPeerNumKeepaliveRcvd,
pcePcepPeerNumUnknownRcvd,
pcePcepPeerNumCorruptRcvd,
pcePcepPeerNumReqSent,
pcePcepPeerNumSvecSent,
pcePcepPeerNumSvecReqSent,
pcePcepPeerNumReqSentPendRep,
pcePcepPeerNumReqSentEroRcvd,
pcePcepPeerNumReqSentNoPathRcvd,
pcePcepPeerNumReqSentCancelRcvd,
pcePcepPeerNumReqSentErrorRcvd,
pcePcepPeerNumReqSentTimeout,
pcePcepPeerNumReqSentCancelSent,
pcePcepPeerNumReqSentClosed,
pcePcepPeerNumReqRcvd,
pcePcepPeerNumSvecRcvd,
pcePcepPeerNumSvecReqRcvd,
pcePcepPeerNumReqRcvdPendRep,
pcePcepPeerNumReqRcvdEroSent,
pcePcepPeerNumReqRcvdNoPathSent,
pcePcepPeerNumReqRcvdCancelSent,
pcePcepPeerNumReqRcvdErrorSent,
pcePcepPeerNumReqRcvdCancelRcvd,
pcePcepPeerNumReqRcvdClosed,
pcePcepPeerNumRepRcvdUnknown,
pcePcepPeerNumReqRcvdUnknown,
pcePcepSessStateLastChange,
pcePcepSessState,
pcePcepSessConnectRetry,
pcePcepSessLocalID,
pcePcepSessRemoteID,
pcePcepSessKeepaliveTimer,
pcePcepSessPeerKeepaliveTimer,
pcePcepSessDeadTimer,
pcePcepSessPeerDeadTimer,
pcePcepSessKAHoldTimeRem,
pcePcepSessOverloaded,
pcePcepSessOverloadTime,
pcePcepSessPeerOverloaded,
pcePcepSessPeerOverloadTime,
pcePcepSessDiscontinuityTime,
pcePcepSessAvgRspTime,
pcePcepSessLWMRspTime,
pcePcepSessHWMRspTime,
pcePcepSessNumPCReqSent,
pcePcepSessNumPCReqRcvd,
pcePcepSessNumPCRepSent,
pcePcepSessNumPCRepRcvd,
pcePcepSessNumPCErrSent,
pcePcepSessNumPCErrRcvd,
pcePcepSessNumPCNtfSent,
pcePcepSessNumPCNtfRcvd,
pcePcepSessNumKeepaliveSent,
pcePcepSessNumKeepaliveRcvd,
pcePcepSessNumUnknownRcvd,
pcePcepSessNumCorruptRcvd,
pcePcepSessNumReqSent,
pcePcepSessNumSvecSent,
pcePcepSessNumSvecReqSent,
pcePcepSessNumReqSentPendRep,
pcePcepSessNumReqSentEroRcvd,
pcePcepSessNumReqSentNoPathRcvd,
pcePcepSessNumReqSentCancelRcvd,
pcePcepSessNumReqSentErrorRcvd,
pcePcepSessNumReqSentTimeout,
pcePcepSessNumReqSentCancelSent,
pcePcepSessNumReqRcvd,
pcePcepSessNumSvecRcvd,
pcePcepSessNumSvecReqRcvd,
pcePcepSessNumReqRcvdPendRep,
pcePcepSessNumReqRcvdEroSent,
pcePcepSessNumReqRcvdNoPathSent,
pcePcepSessNumReqRcvdCancelSent,
pcePcepSessNumReqRcvdErrorSent,
pcePcepSessNumReqRcvdCancelRcvd,
pcePcepSessNumRepRcvdUnknown,
pcePcepSessNumReqRcvdUnknown,
pcePcepNotificationsMaxRate
} pcePcepGeneralGroup OBJECT-GROUP
STATUS current OBJECTS { pcePcepEntityAdminStatus,
DESCRIPTION pcePcepEntityOperStatus,
"Objects that apply to all PCEP MIB module implementations." pcePcepEntityAddrType,
::= { pcePcepGroups 1 } pcePcepEntityAddr,
pcePcepEntityConnectTimer,
pcePcepEntityConnectMaxRetry,
pcePcepEntityInitBackoffTimer,
pcePcepEntityMaxBackoffTimer,
pcePcepEntityOpenWaitTimer,
pcePcepEntityKeepWaitTimer,
pcePcepEntityKeepAliveTimer,
pcePcepEntityDeadTimer,
pcePcepEntityAllowNegotiation,
pcePcepEntityMaxKeepAliveTimer,
pcePcepEntityMaxDeadTimer,
pcePcepEntityMinKeepAliveTimer,
pcePcepEntityMinDeadTimer,
pcePcepEntitySyncTimer,
pcePcepEntityRequestTimer,
pcePcepEntityMaxSessions,
pcePcepEntityMaxUnknownReqs,
pcePcepEntityMaxUnknownMsgs,
pcePcepPeerRole,
pcePcepPeerDiscontinuityTime,
pcePcepPeerInitiateSession,
pcePcepPeerSessionExists,
pcePcepPeerNumSessSetupOK,
pcePcepPeerNumSessSetupFail,
pcePcepPeerSessionUpTime,
pcePcepPeerSessionFailTime,
pcePcepPeerSessionFailUpTime,
pcePcepPeerAvgRspTime,
pcePcepPeerLWMRspTime,
pcePcepPeerHWMRspTime,
pcePcepPeerNumPCReqSent,
pcePcepPeerNumPCReqRcvd,
pcePcepPeerNumPCRepSent,
pcePcepPeerNumPCRepRcvd,
pcePcepPeerNumPCErrSent,
pcePcepPeerNumPCErrRcvd,
pcePcepPeerNumPCNtfSent,
pcePcepPeerNumPCNtfRcvd,
pcePcepPeerNumKeepaliveSent,
pcePcepPeerNumKeepaliveRcvd,
pcePcepPeerNumUnknownRcvd,
pcePcepPeerNumCorruptRcvd,
pcePcepPeerNumReqSent,
pcePcepPeerNumSvecSent,
pcePcepPeerNumSvecReqSent,
pcePcepPeerNumReqSentPendRep,
pcePcepPeerNumReqSentEroRcvd,
pcePcepPeerNumReqSentNoPathRcvd,
pcePcepPeerNumReqSentCancelRcvd,
pcePcepPeerNumReqSentErrorRcvd,
pcePcepPeerNumReqSentTimeout,
pcePcepPeerNumReqSentCancelSent,
pcePcepPeerNumReqSentClosed,
pcePcepPeerNumReqRcvd,
pcePcepPeerNumSvecRcvd,
pcePcepPeerNumSvecReqRcvd,
pcePcepPeerNumReqRcvdPendRep,
pcePcepPeerNumReqRcvdEroSent,
pcePcepPeerNumReqRcvdNoPathSent,
pcePcepPeerNumReqRcvdCancelSent,
pcePcepPeerNumReqRcvdErrorSent,
pcePcepPeerNumReqRcvdCancelRcvd,
pcePcepPeerNumReqRcvdClosed,
pcePcepPeerNumRepRcvdUnknown,
pcePcepPeerNumReqRcvdUnknown,
pcePcepSessStateLastChange,
pcePcepSessState,
pcePcepSessConnectRetry,
pcePcepSessLocalID,
pcePcepSessRemoteID,
pcePcepSessKeepaliveTimer,
pcePcepSessPeerKeepaliveTimer,
pcePcepSessDeadTimer,
pcePcepSessPeerDeadTimer,
pcePcepSessKAHoldTimeRem,
pcePcepSessOverloaded,
pcePcepSessOverloadTime,
pcePcepSessPeerOverloaded,
pcePcepSessPeerOverloadTime,
pcePcepSessDiscontinuityTime,
pcePcepSessAvgRspTime,
pcePcepSessLWMRspTime,
pcePcepSessHWMRspTime,
pcePcepSessNumPCReqSent,
pcePcepSessNumPCReqRcvd,
pcePcepSessNumPCRepSent,
pcePcepSessNumPCRepRcvd,
pcePcepSessNumPCErrSent,
pcePcepSessNumPCErrRcvd,
pcePcepSessNumPCNtfSent,
pcePcepSessNumPCNtfRcvd,
pcePcepSessNumKeepaliveSent,
pcePcepSessNumKeepaliveRcvd,
pcePcepSessNumUnknownRcvd,
pcePcepSessNumCorruptRcvd,
pcePcepSessNumReqSent,
pcePcepSessNumSvecSent,
pcePcepSessNumSvecReqSent,
pcePcepSessNumReqSentPendRep,
pcePcepSessNumReqSentEroRcvd,
pcePcepSessNumReqSentNoPathRcvd,
pcePcepSessNumReqSentCancelRcvd,
pcePcepSessNumReqSentErrorRcvd,
pcePcepSessNumReqSentTimeout,
pcePcepSessNumReqSentCancelSent,
pcePcepSessNumReqRcvd,
pcePcepSessNumSvecRcvd,
pcePcepSessNumSvecReqRcvd,
pcePcepSessNumReqRcvdPendRep,
pcePcepSessNumReqRcvdEroSent,
pcePcepSessNumReqRcvdNoPathSent,
pcePcepSessNumReqRcvdCancelSent,
pcePcepSessNumReqRcvdErrorSent,
pcePcepSessNumReqRcvdCancelRcvd,
pcePcepSessNumRepRcvdUnknown,
pcePcepSessNumReqRcvdUnknown,
pcePcepNotificationsMaxRate
}
STATUS current
DESCRIPTION
"Objects that apply to all PCEP MIB module implementations."
::= { pcePcepGroups 1 }
pcePcepNotificationsGroup NOTIFICATION-GROUP pcePcepNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { pcePcepSessUp, NOTIFICATIONS { pcePcepSessUp,
pcePcepSessDown, pcePcepSessDown,
pcePcepSessLocalOverload, pcePcepSessLocalOverload,
pcePcepSessLocalOverloadClear, pcePcepSessLocalOverloadClear,
pcePcepSessPeerOverload, pcePcepSessPeerOverload,
pcePcepSessPeerOverloadClear pcePcepSessPeerOverloadClear
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notifications for a PCEP MIB module implementation." "The notifications for a PCEP MIB module implementation."
::= { pcePcepGroups 2 } ::= { pcePcepGroups 2 }
END END
5. Security Considerations 5. Security Considerations
The pcePcepNotificationsMaxRate object defined in this MIB module has The pcePcepNotificationsMaxRate object defined in this MIB module has
a MAX-ACCESS clause of read-write. Such objects may be considered a MAX-ACCESS clause of read-write. Such objects may be considered
sensitive or vulnerable in some network environments. The support sensitive or vulnerable in some network environments. The support
for SET operations in a non-secure environment without proper for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations. In protection opens devices to attack. In particular,
particular, pcePcepNotificationsMaxRate may be used improperly to pcePcepNotificationsMaxRate may be used improperly to stop
stop notifications being issued, or to permit a flood of notifications being issued or to permit a flood of notifications to
notifications to be sent to the management agent at a high rate. be sent to the management agent at a high rate.
The readable objects in this MIB module (i.e., objects with a MAX- All the readable objects in this MIB module (i.e., objects with a
ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments since, collectively, they vulnerable in some network environments. It is thus important to
provide information about the amount and frequency of path control even GET and/or NOTIFY access to these objects and possibly
computation requests and responses within the network and can reveal to even encrypt the values of these objects when sending them over
some aspects of its configuration. It is thus important to control the network via SNMP. The sensitivity/vulnerability arises because,
even GET and/or NOTIFY access to these objects and possibly to even collectively, these objects provide information about the amount and
encrypt the values of these objects when sending them over the frequency of path computation requests and responses within the
network via SNMP. network and can reveal some aspects of its configuration.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPsec), Even if the network itself is secure (for example by using IPsec),
there is no control as to who on the secure network is allowed to there is no control as to who on the secure network is allowed to
access and GET/SET (read/change/create/delete) the objects in this access and GET/SET (read/change/create/delete) the objects in this
MIB module. MIB module.
Implementations SHOULD provide the security features described by the Implementations SHOULD provide the security features described by the
SNMPv3 framework (see [RFC3410]), and implementations claiming SNMPv3 framework (see [RFC3410]), and implementations claiming
compliance to the SNMPv3 standard MUST include full support for compliance to the SNMPv3 standard MUST include full support for
skipping to change at page 49, line 29 skipping to change at page 50, line 23
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
6. IANA Considerations 6. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
pcePcepMIB { mib-2 XXX } pcePcepMIB { mib-2 227 }
Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX"
(here and in the MIB module) with the assigned value and to remove
this note.
7. Acknowledgement
The authors would like to thank Santanu Mazumder, Meral Shirazipour
and Adrian Farrel for their valuable input.
Funding for the RFC Editor function is currently provided by the
Internet Society.
8. References 7. References
8.1. Normative References 7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999,
<http://www.rfc-editor.org/info/rfc2578>.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD
58, RFC 2579, April 1999. 58, RFC 2579, April 1999,
<http://www.rfc-editor.org/info/rfc2579>.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999, <http://www.rfc-editor.org/info/rfc2580>.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005.
[RFC5440] Vasseur, JP. and JL. Le Roux, "Path Computation Element
(PCE) Communication Protocol (PCEP)", RFC 5440, March
2009.
8.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, December 2002. Protocol (SNMPv3)", STD 62, RFC 3414, December 2002,
<http://www.rfc-editor.org/info/rfc3414>.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
Advanced Encryption Standard (AES) Cipher Algorithm in the Advanced Encryption Standard (AES) Cipher Algorithm in the
SNMP User-based Security Model", RFC 3826, June 2004. SNMP User-based Security Model", RFC 3826, June 2004,
<http://www.rfc-editor.org/info/rfc3826>.
[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Element (PCE)-Based Architecture", RFC 4655, August 2006. Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005,
<http://www.rfc-editor.org/info/rfc4001>.
[RFC5440] Vasseur, JP. and JL. Le Roux, "Path Computation Element
(PCE) Communication Protocol (PCEP)", RFC 5440, March
2009, <http://www.rfc-editor.org/info/rfc5440>.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
for the Simple Network Management Protocol (SNMP)", STD for the Simple Network Management Protocol (SNMP)", STD
78, RFC 5591, June 2009. 78, RFC 5591, June 2009,
<http://www.rfc-editor.org/info/rfc5591>.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
Shell Transport Model for the Simple Network Management Shell Transport Model for the Simple Network Management
Protocol (SNMP)", RFC 5592, June 2009. Protocol (SNMP)", RFC 5592, June 2009,
<http://www.rfc-editor.org/info/rfc5592>.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Model for the Simple Network Management Protocol (SNMP)", Model for the Simple Network Management Protocol (SNMP)",
STD 78, RFC 6353, July 2011. STD 78, RFC 6353, July 2011,
<http://www.rfc-editor.org/info/rfc6353>.
Appendix A. Contributors 7.2. Informative References
Dhruv Dhody [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
Huawei Technologies "Introduction and Applicability Statements for Internet-
Leela Palace Standard Management Framework", RFC 3410, December 2002,
Bangalore, Karnataka 560008 <http://www.rfc-editor.org/info/rfc3410>.
India
EMail: dhruv.ietf@gmail.com [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation
Element (PCE)-Based Architecture", RFC 4655, August 2006,
<http://www.rfc-editor.org/info/rfc4655>.
Appendix B. PCEP MIB Module Example Appendix A. PCEP MIB Module Example
This example considers the set of PCC / PCE relationships shown in This example considers the set of PCC/PCE relationships shown in the
the following figure. The example shows the contents of the PCEP MIB following figure. The example shows the contents of the PCEP MIB
module as read at PCE2 and PCCb. module as read at PCE2 and PCCb.
PCE1---PCE2 PCE3 PCE1---PCE2 PCE3
| / | / | | / | / |
| / | / | | / | / |
PCCa/ PCCb PCCc PCCa/ PCCb PCCc
The IP addresses of the PCE speakers in this diagram are given in the The IP addresses of the PCE speakers in this diagram are given in the
following table. following table.
+------+-------------+ +------+-------------+
| PCE1 | 1.1.1.1 | | PCE1 | 1.1.1.1 |
+------+-------------+ +------+-------------+
| PCE2 | 2.2.2.2 | | PCE2 | 2.2.2.2 |
+------+-------------+ +------+-------------+
| PCE3 | 3.3.3.3 | | PCE3 | 3.3.3.3 |
+------+-------------+ +------+-------------+
| PCCa | 11.11.11.11 | | PCCa | 11.11.11.11 |
+------+-------------+ +------+-------------+
| PCCb | 22.22.22.22 | | PCCb | 22.22.22.22 |
+------+-------------+ +------+-------------+
| PCCc | 33.33.33.33 | | PCCc | 33.33.33.33 |
+------+-------------+ +------+-------------+
In this example, the PCEP session between PCCb and PCE3 is currently In this example, the PCEP session between PCCb and PCE3 is currently
down. down.
B.1. Contents of PCEP MIB module at PCE2 A.1. Contents of PCEP MIB Module at PCE2
At PCE2, there is a single local PCEP entity which has three peers At PCE2, there is a single local PCEP entity that has three peers
(PCCa, PCCb and PCE1). There is a session active to all of these (PCCa, PCCb, and PCE1). There is a session active to all of these
peers. peers.
The contents of the PCEP MIB module as read at PCE2 are as follows. The contents of the PCEP MIB module as read at PCE2 are as follows.
In pcePcepEntityTable { In pcePcepEntityTable {
pcePcepEntityIndex 1, pcePcepEntityIndex 1,
pcePcepEntityAdminStatus adminStatusUp(1), pcePcepEntityAdminStatus adminStatusUp(1),
pcePcepEntityOperStatus operStatusUp(1), pcePcepEntityOperStatus operStatusUp(1),
pcePcepEntityAddrType ipv4(1), pcePcepEntityAddrType ipv4(1),
pcePcepEntityAddr 2.2.2.2, -- PCE2 pcePcepEntityAddr 2.2.2.2, -- PCE2
skipping to change at page 59, line 13 skipping to change at page 60, line 19
pcePcepSessNumReqRcvdPendRep 0, pcePcepSessNumReqRcvdPendRep 0,
pcePcepSessNumReqRcvdEroSent 3, pcePcepSessNumReqRcvdEroSent 3,
pcePcepSessNumReqRcvdNoPathSent 1, pcePcepSessNumReqRcvdNoPathSent 1,
pcePcepSessNumReqRcvdCancelSent 0, pcePcepSessNumReqRcvdCancelSent 0,
pcePcepSessNumReqRcvdErrorSent 0, pcePcepSessNumReqRcvdErrorSent 0,
pcePcepSessNumReqRcvdCancelRcvd 0, pcePcepSessNumReqRcvdCancelRcvd 0,
pcePcepSessNumRepRcvdUnknown 0, pcePcepSessNumRepRcvdUnknown 0,
pcePcepSessNumReqRcvdUnknown 0 pcePcepSessNumReqRcvdUnknown 0
} }
B.2. Contents of PCEP MIB module at PCCb A.2. Contents of PCEP MIB Module at PCCb
At PCCb, there is a single local PCEP entity which has two peers At PCCb, there is a single local PCEP entity that has two peers (PCE2
(PCE2 and PCE3). There is a session active to PCE2, but the session and PCE3). There is a session active to PCE2, but the session to
to PCE3 is currently down. PCE3 is currently down.
The contents of the PCEP MIB module as read at PCCb are as follows. The contents of the PCEP MIB module as read at PCCb are as follows.
In pcePcepEntityTable { In pcePcepEntityTable {
pcePcepEntityIndex 1, pcePcepEntityIndex 1,
pcePcepEntityAdminStatus adminStatusUp(1), pcePcepEntityAdminStatus adminStatusUp(1),
pcePcepEntityOperStatus operStatusUp(1), pcePcepEntityOperStatus operStatusUp(1),
pcePcepEntityAddrType ipv4(1), pcePcepEntityAddrType ipv4(1),
pcePcepEntityAddr 22.22.22.22, -- PCCb pcePcepEntityAddr 22.22.22.22, -- PCCb
pcePcepEntityConnectTimer 60, pcePcepEntityConnectTimer 60,
skipping to change at page 63, line 15 skipping to change at page 64, line 20
pcePcepSessNumReqRcvdNoPathSent 0, pcePcepSessNumReqRcvdNoPathSent 0,
pcePcepSessNumReqRcvdCancelSent 0, pcePcepSessNumReqRcvdCancelSent 0,
pcePcepSessNumReqRcvdErrorSent 0, pcePcepSessNumReqRcvdErrorSent 0,
pcePcepSessNumReqRcvdCancelRcvd 0, pcePcepSessNumReqRcvdCancelRcvd 0,
pcePcepSessNumRepRcvdUnknown 0, pcePcepSessNumRepRcvdUnknown 0,
pcePcepSessNumReqRcvdUnknown 0 pcePcepSessNumReqRcvdUnknown 0
} }
-- no session to PCE3 -- no session to PCE3
Acknowledgements
The authors would like to thank Santanu Mazumder, Meral Shirazipour,
and Adrian Farrel for their valuable input.
Contributors
Dhruv Dhody
Huawei Technologies
Leela Palace
Bangalore, Karnataka 560008
India
EMail: dhruv.ietf@gmail.com
Authors' Addresses Authors' Addresses
Agrahara Kiran Koushik Agrahara Kiran Koushik
Brocade Communications Inc. Brocade Communications, Inc.
EMail: kkoushik@brocade.com EMail: kkoushik@brocade.com
Emile Stephan Emile Stephan
Orange Orange
2 avenue Pierre Marzin 2 Avenue Pierre Marzin
Lannion F-22307 Lannion F-22307
France France
EMail: emile.stephan@orange.com EMail: emile.stephan@orange.com
Quintin Zhao Quintin Zhao
Huawei Technology Huawei Technology
125 Nagog Technology Park 125 Nagog Technology Park
Acton, MA 01719 Acton, MA 01719
US United States
EMail: qzhao@huawei.com EMail: qzhao@huawei.com
Daniel King Daniel King
Old Dog Consulting Old Dog Consulting
EMail: daniel@olddog.co.uk EMail: daniel@olddog.co.uk
Jonathan Hardwick Jonathan Hardwick
Metaswitch Metaswitch
100 Church Street 100 Church Street
Enfield EN2 6BQ Enfield EN2 6BQ
UK United Kingdom
EMail: jonathan.hardwick@metaswitch.com EMail: jonathan.hardwick@metaswitch.com
 End of changes. 286 change blocks. 
1913 lines changed or deleted 1914 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/