2014-12-17
This MIB module defines a collection of objects for managing the Path Computation Element Communication Protocol (PCEP). Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
Download PCE-PCEP-MIB.txt Open PCE-PCEP-MIB.txt in a new tab
SCALARS (1) · TABLES (3) · TRAPS (6)
| Name | OID |
|---|---|
| pcePcepNotificationsMaxRate | 1.3.6.1.2.1.227.1.4 |
| Name | OID |
|---|---|
| pcePcepEntityTable | 1.3.6.1.2.1.227.1.1 |
| pcePcepPeerTable | 1.3.6.1.2.1.227.1.2 |
| pcePcepSessTable | 1.3.6.1.2.1.227.1.3 |
END OF TOC
1.3.6.1.2.1.227.1.4
Unsigned32
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).
1.3.6.1.2.1.227.1.1
Index: pcePcepEntityIndex
This table contains information about local PCEP entities. The entries in this table are read-only.
1.3.6.1.2.1.227.1.1.1.1
Unsigned32
This index is used to uniquely identify the PCEP entity.
1.3.6.1.2.1.227.1.1.1.2
INTEGER1 = adminStatusUp2 = adminStatusDown · Integer32
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 of pcePcepEntityOperStatus represents the current status of an attempt to reach this desired status.
1.3.6.1.2.1.227.1.1.1.3
INTEGER1 = operStatusUp2 = operStatusDown3 = operStatusGoingUp4 = operStatusGoingDown5 = operStatusFailed6 = operStatusFailedPerm · Integer32
The operational status of the PCEP entity. It 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.
1.3.6.1.2.1.227.1.1.1.4
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
The type of the PCEP entity's Internet address. This object specifies how the value of the pcePcepEntityAddr object should be interpreted. Only values unknown(0), ipv4(1), or ipv6(2) are supported.
1.3.6.1.2.1.227.1.1.1.5
InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
The local Internet address of this PCEP entity. The type is given by pcePcepEntityAddrType. If operating as a PCE server, the PCEP entity listens on this address. If operating as a PCC, the PCEP entity binds outgoing TCP connections to this address. It is possible for the PCEP entity to operate both as a PCC and a PCE server, in which case it uses this address both to listen for incoming TCP connections and to bind outgoing TCP connections.
1.3.6.1.2.1.227.1.1.1.6
Unsigned32 (1..65535) · seconds
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.
1.3.6.1.2.1.227.1.1.1.7
Unsigned32
The maximum number of times the system tries to establish a TCP connection to a peer before the session with the peer transitions to the idle state. When the session transitions to the idle state: - pcePcepPeerSessionExists transitions to false(2). - the associated PcePcepSessEntry is deleted. - a backoff timer runs before the session is tried again.
1.3.6.1.2.1.227.1.1.1.8
Unsigned32 (1..65535) · seconds
The initial backoff time for retrying a failed session setup attempt to a peer. The backoff time increases for each failed session setup attempt, until a maximum backoff time is reached. The maximum backoff time is pcePcepEntityMaxBackoffTimer.
1.3.6.1.2.1.227.1.1.1.9
Unsigned32 · seconds
The maximum backoff time for retrying a failed session setup attempt to a peer. The backoff time increases for each failed session setup attempt, until this maximum value is reached. Session setup attempts then repeats periodically without any further increase in backoff time.
1.3.6.1.2.1.227.1.1.1.10
Unsigned32 (1..65535) · seconds
The time that the PCEP entity will wait to receive an Open message from a peer after the TCP connection has come up. If no Open message is received within this time, then PCEP terminates the TCP connection and deletes the associated PcePcepSessEntry.
1.3.6.1.2.1.227.1.1.1.11
Unsigned32 (1..65535) · seconds
The time that the PCEP entity will wait to receive a Keepalive or PCErr message from a peer during session 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.
1.3.6.1.2.1.227.1.1.1.12
Unsigned32 (0..255) · seconds
The Keepalive 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 either direction of an active PCEP session, are determined by negotiation between the peers as specified by RFC 5440, and so may differ from this configured value. For the actually negotiated values (per session), see pcePcepSessKeepaliveTimer and pcePcepSessPeerKeepaliveTimer.
1.3.6.1.2.1.227.1.1.1.13
Unsigned32 (0..255) · seconds
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.
1.3.6.1.2.1.227.1.1.1.14
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
Whether the PCEP entity will permit negotiation of session parameters.
1.3.6.1.2.1.227.1.1.1.15
Unsigned32 (0..255) · seconds
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.
1.3.6.1.2.1.227.1.1.1.16
Unsigned32 (0..255) · seconds
In PCEP session parameter negotiation, the maximum value that this PCEP entity will accept from a peer for the DeadTimer. Zero means that the PCEP entity will allow not running a DeadTimer.
1.3.6.1.2.1.227.1.1.1.17
Unsigned32 (0..255) · seconds
In PCEP session parameter negotiation, the minimum value 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.
1.3.6.1.2.1.227.1.1.1.18
Unsigned32 (0..255) · seconds
In PCEP session parameter negotiation, the minimum value that this PCEP entity will accept for the DeadTimer. Zero means that the PCEP entity insists on not running a DeadTimer.
1.3.6.1.2.1.227.1.1.1.19
Unsigned32 (0..65535) · seconds
The value of SyncTimer is used in the case of a synchronized path computation request using the SVEC object. Consider the case where a PCReq message is received by a PCE that contains the SVEC object referring to M synchronized 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. The aim of the SyncTimer is to avoid the storage of unused synchronized requests should one of them get lost for some reason (for example, a misbehaving PCC). A value of zero is returned if and only if the entity does not use the SyncTimer.
1.3.6.1.2.1.227.1.1.1.20
Unsigned32 (1..65535) · seconds
The maximum time that the PCEP entity will wait for a response to a PCReq message.
1.3.6.1.2.1.227.1.1.1.21
Unsigned32
The maximum number of sessions involving this PCEP entity that can exist at any time.
1.3.6.1.2.1.227.1.1.1.22
Unsigned32
The maximum number of unrecognized requests and replies that any session on this PCEP entity is willing to accept per minute before terminating the session. A PCRep message contains an unrecognized reply if it contains an RP object whose request ID does not correspond to any in-progress request sent by this PCEP entity. A PCReq message contains an unrecognized request if it contains an RP object whose request ID is zero.
1.3.6.1.2.1.227.1.1.1.23
Unsigned32
The maximum number of unknown messages that any session on this PCEP entity is willing to accept per minute before terminating the session.
1.3.6.1.2.1.227.1.2
Index: pcePcepEntityIndex · pcePcepPeerAddrType · pcePcepPeerAddr
This table contains information about peers known by the local PCEP entity. The entries in this table are read-only. This table gives peer information that spans PCEP sessions. Information about current PCEP sessions can be found in the pcePcepSessTable table.
1.3.6.1.2.1.227.1.2.1.1
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
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.
1.3.6.1.2.1.227.1.2.1.2
InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
The Internet address of the peer. The type is given by pcePcepPeerAddrType.
1.3.6.1.2.1.227.1.2.1.3
INTEGER0 = unknown1 = pcc2 = pce3 = pccAndPce · Integer32
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.
1.3.6.1.2.1.227.1.2.1.4
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The value of sysUpTime at the time that the information and statistics in this row were last reset.
1.3.6.1.2.1.227.1.2.1.5
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
Indicates whether the local PCEP entity initiates sessions to this peer or waits for the peer to initiate a session.
1.3.6.1.2.1.227.1.2.1.6
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
Indicates whether a session with this peer currently exists.
1.3.6.1.2.1.227.1.2.1.7
Counter32
The number of PCEP sessions successfully established with the peer, including any current session. This counter is incremented each time a session with this peer is successfully established.
1.3.6.1.2.1.227.1.2.1.8
Counter32
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.
1.3.6.1.2.1.227.1.2.1.9
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The value of sysUpTime the last time a session with this peer was successfully established. If pcePcepPeerNumSessSetupOK is zero, then this object contains zero.
1.3.6.1.2.1.227.1.2.1.10
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The value of sysUpTime the last time a session with this peer failed to be established. If pcePcepPeerNumSessSetupFail is zero, then this object contains zero.
1.3.6.1.2.1.227.1.2.1.11
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The value of sysUpTime the last time a session with this peer failed from active. If pcePcepPeerNumSessSetupOK is zero, then this object contains zero.
1.3.6.1.2.1.227.1.2.1.12
Unsigned32 · milliseconds
The average response time for this peer. If an average response time has not been calculated for this peer, then this object has the value zero. If pcePcepPeerRole is pcc, then this field is meaningless and is set to zero.
1.3.6.1.2.1.227.1.2.1.13
Unsigned32 · milliseconds
The smallest (low-water mark) response time seen from this peer. If no responses have been received from this peer, then this object has the value zero. If pcePcepPeerRole is pcc, then this field is meaningless and is set to zero.
1.3.6.1.2.1.227.1.2.1.14
Unsigned32 · milliseconds
The greatest (high-water mark) response time seen from this peer. If no responses have been received from this peer, then this object has the value zero. If pcePcepPeerRole is pcc, then this field is meaningless and is set to zero.
1.3.6.1.2.1.227.1.2.1.15
Counter32
The number of PCReq messages sent to this peer.
1.3.6.1.2.1.227.1.2.1.16
Counter32
The number of PCReq messages received from this peer.
1.3.6.1.2.1.227.1.2.1.17
Counter32
The number of PCRep messages sent to this peer.
1.3.6.1.2.1.227.1.2.1.18
Counter32
The number of PCRep messages received from this peer.
1.3.6.1.2.1.227.1.2.1.19
Counter32
The number of PCErr messages sent to this peer.
1.3.6.1.2.1.227.1.2.1.20
Counter32
The number of PCErr messages received from this peer.
1.3.6.1.2.1.227.1.2.1.21
Counter32
The number of PCNtf messages sent to this peer.
1.3.6.1.2.1.227.1.2.1.22
Counter32
The number of PCNtf messages received from this peer.
1.3.6.1.2.1.227.1.2.1.23
Counter32
The number of Keepalive messages sent to this peer.
1.3.6.1.2.1.227.1.2.1.24
Counter32
The number of Keepalive messages received from this peer.
1.3.6.1.2.1.227.1.2.1.25
Counter32
The number of unknown messages received from this peer.
1.3.6.1.2.1.227.1.2.1.26
Counter32
The number of corrupted PCEP messages received from this peer.
1.3.6.1.2.1.227.1.2.1.27
Counter32
The number of requests sent to this peer. A request corresponds 1:1 with an RP object in a PCReq message. This might be greater than pcePcepPeerNumPCReqSent because multiple requests can be batched into a single PCReq message.
1.3.6.1.2.1.227.1.2.1.28
Counter32
The number of SVEC objects sent to this peer in PCReq messages. An SVEC object represents a set of synchronized requests.
1.3.6.1.2.1.227.1.2.1.29
Counter32
The number of requests sent to this peer that appeared in one or more SVEC objects.
1.3.6.1.2.1.227.1.2.1.30
Counter32
The number of requests that have been sent to this peer for which a response is still pending.
1.3.6.1.2.1.227.1.2.1.31
Counter32
The number of requests that have been sent to this peer for which a response with an ERO was received. Such responses indicate that a path was successfully computed by the peer.
1.3.6.1.2.1.227.1.2.1.32
Counter32
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.
1.3.6.1.2.1.227.1.2.1.33
Counter32
The number of requests that were canceled by the peer with a PCNtf message. This might be different than pcePcepPeerNumPCNtfRcvd because not all PCNtf messages are used to cancel requests, and a single PCNtf message can cancel multiple requests.
1.3.6.1.2.1.227.1.2.1.34
Counter32
The number of requests that were rejected by the peer with a PCErr message. This might be different than pcePcepPeerNumPCErrRcvd because not all PCErr messages are used to reject requests, and a single PCErr message can reject multiple requests.
1.3.6.1.2.1.227.1.2.1.35
Counter32
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.
1.3.6.1.2.1.227.1.2.1.36
Counter32
The number of requests that were sent to the peer and explicitly canceled by the local PCEP entity sending a PCNtf.
1.3.6.1.2.1.227.1.2.1.37
Counter32
The number of requests that were sent to the peer and implicitly canceled when the session they were sent over was closed.
1.3.6.1.2.1.227.1.2.1.38
Counter32
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 multiple requests can be batched into a single PCReq message.
1.3.6.1.2.1.227.1.2.1.39
Counter32
The number of SVEC objects received from this peer in PCReq messages. An SVEC object represents a set of synchronized requests.
1.3.6.1.2.1.227.1.2.1.40
Counter32
The number of requests received from this peer that appeared in one or more SVEC objects.
1.3.6.1.2.1.227.1.2.1.41
Counter32
The number of requests that have been received from this peer for which a response is still pending.
1.3.6.1.2.1.227.1.2.1.42
Counter32
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.
1.3.6.1.2.1.227.1.2.1.43
Counter32
The number of requests that have been received from this 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.
1.3.6.1.2.1.227.1.2.1.44
Counter32
The number of requests received from this peer that were canceled by the local PCEP entity sending a PCNtf message. This might be different than pcePcepPeerNumPCNtfSent because not all PCNtf messages are used to cancel requests, and a single PCNtf message can cancel multiple requests.
1.3.6.1.2.1.227.1.2.1.45
Counter32
The number of requests received from this peer that were rejected by the local PCEP entity sending a PCErr message. This might be different than pcePcepPeerNumPCErrSent because not all PCErr messages are used to reject requests, and a single PCErr message can reject multiple requests.
1.3.6.1.2.1.227.1.2.1.46
Counter32
The number of requests that were received from the peer and explicitly canceled by the peer sending a PCNtf.
1.3.6.1.2.1.227.1.2.1.47
Counter32
The number of requests that were received from the peer and implicitly canceled when the session they were received over was closed.
1.3.6.1.2.1.227.1.2.1.48
Counter32
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.
1.3.6.1.2.1.227.1.2.1.49
Counter32
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.
1.3.6.1.2.1.227.1.3
Index: pcePcepEntityIndex · pcePcepPeerAddrType · pcePcepPeerAddr · pcePcepSessInitiator
A table of PCEP sessions that involve the local PCEP entity. Each entry in this table represents a single session. The entries in this table are read-only. An entry appears in this table when the corresponding PCEP session transitions out of idle state. If the PCEP session transitions back into an idle state, then the corresponding entry in this table is removed.
1.3.6.1.2.1.227.1.3.1.1
INTEGER1 = local2 = remote · Integer32
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 sessions can exist between a pair of PCEP speakers, each 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.
1.3.6.1.2.1.227.1.3.1.2
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The value of sysUpTime at the time this session entered its current state as denoted by the pcePcepSessState object.
1.3.6.1.2.1.227.1.3.1.3
INTEGER1 = tcpPending2 = openWait3 = keepWait4 = sessionUp · Integer32
The current state of the session. The set of possible states excludes the idle state since entries do not exist in this table in the idle state.
1.3.6.1.2.1.227.1.3.1.4
Counter32
The number of times that the local PCEP entity has attempted to establish a TCP connection for this session without success. The PCEP entity gives up when this reaches pcePcepEntityConnectMaxRetry.
1.3.6.1.2.1.227.1.3.1.5
Unsigned32 (0..255)
The value of the PCEP session ID used by the local PCEP entity in the Open message for this session. If pcePcepSessState is tcpPending, then this is the session ID that will be used in the Open message. Otherwise, this is the session ID that was sent in the Open message.
1.3.6.1.2.1.227.1.3.1.6
Unsigned32 (0..255)
The value of the PCEP session ID used by the peer in its Open message for this session. If pcePcepSessState is tcpPending or openWait, then this field is not used and MUST be set to zero.
1.3.6.1.2.1.227.1.3.1.7
Unsigned32 (0..255) · seconds
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 sessionUp. Otherwise, it is not used and MUST be set to zero.
1.3.6.1.2.1.227.1.3.1.8
Unsigned32 (0..255) · seconds
The agreed maximum interval at which the peer transmits PCEP messages on this PCEP session. Zero means that the peer never sends Keepalives on this session. This field is used if and only if pcePcepSessState is sessionUp. Otherwise, it is not used and MUST be set to zero.
1.3.6.1.2.1.227.1.3.1.9
Unsigned32 (0..255) · seconds
The DeadTimer interval for this PCEP session.
1.3.6.1.2.1.227.1.3.1.10
Unsigned32 (0..255) · seconds
The peer's DeadTimer interval for this PCEP session. If pcePcepSessState is tcpPending or openWait, then this field is not used and MUST be set to zero.
1.3.6.1.2.1.227.1.3.1.11
Unsigned32 (0..255) · seconds
The Keepalive hold time remaining for this session. If pcePcepSessState is tcpPending or openWait, then this field is not used and MUST be set to zero.
1.3.6.1.2.1.227.1.3.1.12
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
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.
1.3.6.1.2.1.227.1.3.1.13
Unsigned32 · seconds
The interval of time that is remaining until the local PCEP entity will cease to be overloaded on this session. This field is only used if pcePcepSessOverloaded is set to true. Otherwise, it is not used and MUST be set to zero.
1.3.6.1.2.1.227.1.3.1.14
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
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.
1.3.6.1.2.1.227.1.3.1.15
Unsigned32 · seconds
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. This field is only used if pcePcepSessPeerOverloaded is set to true. Otherwise, it is not used and MUST be set to zero.
1.3.6.1.2.1.227.1.3.1.16
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The value of sysUpTime at the time that the statistics in this row were last reset.
1.3.6.1.2.1.227.1.3.1.17
Unsigned32 · milliseconds
The average response time for this peer on this session. If an average response time has not been calculated for this peer, then this object has the value zero.
1.3.6.1.2.1.227.1.3.1.18
Unsigned32 · milliseconds
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 object has the value zero.
1.3.6.1.2.1.227.1.3.1.19
Unsigned32 · milliseconds
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 object has the value zero.
1.3.6.1.2.1.227.1.3.1.20
Counter32
The number of PCReq messages sent on this session.
1.3.6.1.2.1.227.1.3.1.21
Counter32
The number of PCReq messages received on this session.
1.3.6.1.2.1.227.1.3.1.22
Counter32
The number of PCRep messages sent on this session.
1.3.6.1.2.1.227.1.3.1.23
Counter32
The number of PCRep messages received on this session.
1.3.6.1.2.1.227.1.3.1.24
Counter32
The number of PCErr messages sent on this session.
1.3.6.1.2.1.227.1.3.1.25
Counter32
The number of PCErr messages received on this session.
1.3.6.1.2.1.227.1.3.1.26
Counter32
The number of PCNtf messages sent on this session.
1.3.6.1.2.1.227.1.3.1.27
Counter32
The number of PCNtf messages received on this session.
1.3.6.1.2.1.227.1.3.1.28
Counter32
The number of Keepalive messages sent on this session.
1.3.6.1.2.1.227.1.3.1.29
Counter32
The number of Keepalive messages received on this session.
1.3.6.1.2.1.227.1.3.1.30
Counter32
The number of unknown messages received on this session.
1.3.6.1.2.1.227.1.3.1.31
Counter32
The number of corrupted PCEP messages received on this session.
1.3.6.1.2.1.227.1.3.1.32
Counter32
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 multiple requests can be batched into a single PCReq message.
1.3.6.1.2.1.227.1.3.1.33
Counter32
The number of SVEC objects sent on this session in PCReq messages. An SVEC object represents a set of synchronized requests.
1.3.6.1.2.1.227.1.3.1.34
Counter32
The number of requests sent on this session that appeared in one or more SVEC objects.
1.3.6.1.2.1.227.1.3.1.35
Counter32
The number of requests that have been sent on this session for which a response is still pending.
1.3.6.1.2.1.227.1.3.1.36
Counter32
The number of successful responses received on this session. A response corresponds 1:1 with an RP object in a PCRep message. A successful response is a response for which an ERO was successfully computed.
1.3.6.1.2.1.227.1.3.1.37
Counter32
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.
1.3.6.1.2.1.227.1.3.1.38
Counter32
The number of requests sent on this session that were canceled by the peer with a PCNtf message. This might be different than pcePcepSessNumPCNtfRcvd because not all PCNtf messages are used to cancel requests, and a single PCNtf message can cancel multiple requests.
1.3.6.1.2.1.227.1.3.1.39
Counter32
The number of requests sent on this session that were rejected by the peer with a PCErr message. This might be different than pcePcepSessNumPCErrRcvd because not all PCErr messages are used to reject requests, and a single PCErr message can reject multiple requests.
1.3.6.1.2.1.227.1.3.1.40
Counter32
The number of requests sent on this session that have been sent to a peer and have been abandoned because the peer has taken too long to respond to them.
1.3.6.1.2.1.227.1.3.1.41
Counter32
The number of requests sent on this session that were sent to the peer and explicitly canceled by the local PCEP entity sending a PCNtf.
1.3.6.1.2.1.227.1.3.1.42
Counter32
The number of requests received on this session. A request corresponds 1:1 with an RP object in a PCReq message. This might be greater than pcePcepSessNumPCReqRcvd because multiple requests can be batched into a single PCReq message.
1.3.6.1.2.1.227.1.3.1.43
Counter32
The number of SVEC objects received on this session in PCReq messages. An SVEC object represents a set of synchronized requests.
1.3.6.1.2.1.227.1.3.1.44
Counter32
The number of requests received on this session that appeared in one or more SVEC objects.
1.3.6.1.2.1.227.1.3.1.45
Counter32
The number of requests that have been received on this session for which a response is still pending.
1.3.6.1.2.1.227.1.3.1.46
Counter32
The number of successful responses sent on this session. A response corresponds 1:1 with an RP object in a PCRep message. A successful response is a response for which an ERO was successfully computed.
1.3.6.1.2.1.227.1.3.1.47
Counter32
The number of unsuccessful responses sent 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.
1.3.6.1.2.1.227.1.3.1.48
Counter32
The number of requests received on this session that were canceled by the local PCEP entity sending a PCNtf message. This might be different than pcePcepSessNumPCNtfSent because not all PCNtf messages are used to cancel requests, and a single PCNtf message can cancel multiple requests.
1.3.6.1.2.1.227.1.3.1.49
Counter32
The number of requests received on this session that were rejected by the local PCEP entity sending a PCErr message. This might be different than pcePcepSessNumPCErrSent because not all PCErr messages are used to reject requests, and a single PCErr message can reject multiple requests.
1.3.6.1.2.1.227.1.3.1.50
Counter32
The number of requests that were received on this session and explicitly canceled by the peer sending a PCNtf.
1.3.6.1.2.1.227.1.3.1.51
Counter32
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.
1.3.6.1.2.1.227.1.3.1.52
Counter32
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.
1.3.6.1.2.1.227.0.1
This notification is sent when the value of pcePcepSessState enters the sessionUp state.
1.3.6.1.2.1.227.1.3.1.3
INTEGER1 = tcpPending2 = openWait3 = keepWait4 = sessionUp · Integer32
The current state of the session. The set of possible states excludes the idle state since entries do not exist in this table in the idle state.
1.3.6.1.2.1.227.1.3.1.2
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The value of sysUpTime at the time this session entered its current state as denoted by the pcePcepSessState object.
1.3.6.1.2.1.227.0.2
This notification is sent when the value of pcePcepSessState leaves the sessionUp state.
1.3.6.1.2.1.227.1.3.1.3
INTEGER1 = tcpPending2 = openWait3 = keepWait4 = sessionUp · Integer32
The current state of the session. The set of possible states excludes the idle state since entries do not exist in this table in the idle state.
1.3.6.1.2.1.227.1.3.1.2
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The value of sysUpTime at the time this session entered its current state as denoted by the pcePcepSessState object.
1.3.6.1.2.1.227.0.3
This notification is sent when the local PCEP entity enters overload state for a peer.
1.3.6.1.2.1.227.1.3.1.12
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
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.
1.3.6.1.2.1.227.1.3.1.13
Unsigned32 · seconds
The interval of time that is remaining until the local PCEP entity will cease to be overloaded on this session. This field is only used if pcePcepSessOverloaded is set to true. Otherwise, it is not used and MUST be set to zero.
1.3.6.1.2.1.227.0.4
This notification is sent when the local PCEP entity leaves overload state for a peer.
1.3.6.1.2.1.227.1.3.1.12
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
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.
1.3.6.1.2.1.227.0.5
This notification is sent when a peer enters overload state.
1.3.6.1.2.1.227.1.3.1.14
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
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.
1.3.6.1.2.1.227.1.3.1.15
Unsigned32 · seconds
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. This field is only used if pcePcepSessPeerOverloaded is set to true. Otherwise, it is not used and MUST be set to zero.
1.3.6.1.2.1.227.0.6
This notification is sent when a peer leaves overload state.
1.3.6.1.2.1.227.1.3.1.14
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
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.