PCE-PCEP-MIB
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).
Main OID:
pcePcepMIB.1.3.6.1.2.1.227
146
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
146 total| Object Name |
|---|
pcePcepMIBThis 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). MODULE-IDENTITY .1.3.6.1.2.1.227 |
pcePcepNotifications OBJECT IDENTIFIER .1.3.6.1.2.1.227.0 |
pcePcepSessUpThis notification is sent when the value of pcePcepSessState enters the sessionUp state. NOTIFICATION-TYPE .1.3.6.1.2.1.227.0.1 |
pcePcepSessDownThis notification is sent when the value of pcePcepSessState leaves the sessionUp state. NOTIFICATION-TYPE .1.3.6.1.2.1.227.0.2 |
pcePcepSessLocalOverloadThis notification is sent when the local PCEP entity enters overload state for a peer. NOTIFICATION-TYPE .1.3.6.1.2.1.227.0.3 |
pcePcepSessLocalOverloadClearThis notification is sent when the local PCEP entity leaves overload state for a peer. NOTIFICATION-TYPE .1.3.6.1.2.1.227.0.4 |
pcePcepSessPeerOverloadThis notification is sent when a peer enters overload state. NOTIFICATION-TYPE .1.3.6.1.2.1.227.0.5 |
pcePcepSessPeerOverloadClearThis notification is sent when a peer leaves overload state. NOTIFICATION-TYPE .1.3.6.1.2.1.227.0.6 |
pcePcepObjects OBJECT IDENTIFIER .1.3.6.1.2.1.227.1 |
pcePcepEntityTableThis table contains information about local PCEP entities. The entries in this table are read-only. SEQUENCE OF PcePcepEntityEntry .1.3.6.1.2.1.227.1.1 |
pcePcepEntityEntryThis entry represents a local PCEP entity. PcePcepEntityEntry .1.3.6.1.2.1.227.1.1.1 |
pcePcepEntityIndexThis index is used to uniquely identify the PCEP entity. Unsigned32 .1.3.6.1.2.1.227.1.1.1.1 |
pcePcepEntityAdminStatusThe 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.ro Enumeration .1.3.6.1.2.1.227.1.1.1.2 |
pcePcepEntityOperStatusThe 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.ro Enumeration .1.3.6.1.2.1.227.1.1.1.3 |
pcePcepEntityAddrTypeThe 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.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.227.1.1.1.4 |
pcePcepEntityAddrThe 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.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.2.1.227.1.1.1.5 |
pcePcepEntityConnectTimerThe 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.ro Unsigned32 .1.3.6.1.2.1.227.1.1.1.6 |
pcePcepEntityConnectMaxRetryThe 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.ro Unsigned32 .1.3.6.1.2.1.227.1.1.1.7 |
pcePcepEntityInitBackoffTimerThe 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.ro Unsigned32 .1.3.6.1.2.1.227.1.1.1.8 |
pcePcepEntityMaxBackoffTimerThe 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.ro Unsigned32 UNITS "seconds" .1.3.6.1.2.1.227.1.1.1.9 |
pcePcepEntityOpenWaitTimerThe 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.ro Unsigned32 .1.3.6.1.2.1.227.1.1.1.10 |
pcePcepEntityKeepWaitTimerThe 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.ro Unsigned32 .1.3.6.1.2.1.227.1.1.1.11 |
pcePcepEntityKeepAliveTimerThe 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.ro Unsigned32 .1.3.6.1.2.1.227.1.1.1.12 |
pcePcepEntityDeadTimerThe 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.ro Unsigned32 .1.3.6.1.2.1.227.1.1.1.13 |
pcePcepEntityAllowNegotiationWhether the PCEP entity will permit negotiation of session parameters.ro TruthValue (SNMPv2-TC) .1.3.6.1.2.1.227.1.1.1.14 |
pcePcepEntityMaxKeepAliveTimerIn 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.ro Unsigned32 .1.3.6.1.2.1.227.1.1.1.15 |
pcePcepEntityMaxDeadTimerIn 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.ro Unsigned32 .1.3.6.1.2.1.227.1.1.1.16 |
pcePcepEntityMinKeepAliveTimerIn 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.ro Unsigned32 .1.3.6.1.2.1.227.1.1.1.17 |
pcePcepEntityMinDeadTimerIn 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.ro Unsigned32 .1.3.6.1.2.1.227.1.1.1.18 |
pcePcepEntitySyncTimerThe 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.ro Unsigned32 .1.3.6.1.2.1.227.1.1.1.19 |
pcePcepEntityRequestTimerThe maximum time that the PCEP entity will wait for a response to a PCReq message.ro Unsigned32 .1.3.6.1.2.1.227.1.1.1.20 |
pcePcepEntityMaxSessionsThe maximum number of sessions involving this PCEP entity that can exist at any time.ro Unsigned32 .1.3.6.1.2.1.227.1.1.1.21 |
pcePcepEntityMaxUnknownReqsThe 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.ro Unsigned32 .1.3.6.1.2.1.227.1.1.1.22 |
pcePcepEntityMaxUnknownMsgsThe maximum number of unknown messages that any session on this PCEP entity is willing to accept per minute before terminating the session.ro Unsigned32 .1.3.6.1.2.1.227.1.1.1.23 |
pcePcepPeerTableThis 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. SEQUENCE OF PcePcepPeerEntry .1.3.6.1.2.1.227.1.2 |
pcePcepPeerEntryInformation about a single peer that spans all PCEP sessions to that peer. PcePcepPeerEntry .1.3.6.1.2.1.227.1.2.1 |
pcePcepPeerAddrTypeThe 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. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.2.1.227.1.2.1.1 |
pcePcepPeerAddrThe Internet address of the peer. The type is given by pcePcepPeerAddrType. InetAddress (INET-ADDRESS-MIB) .1.3.6.1.2.1.227.1.2.1.2 |
pcePcepPeerRoleThe 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.ro Enumeration .1.3.6.1.2.1.227.1.2.1.3 |
pcePcepPeerDiscontinuityTimeThe value of sysUpTime at the time that the information and statistics in this row were last reset.ro TimeStamp (SNMPv2-TC) .1.3.6.1.2.1.227.1.2.1.4 |
pcePcepPeerInitiateSessionIndicates whether the local PCEP entity initiates sessions to this peer or waits for the peer to initiate a session.ro TruthValue (SNMPv2-TC) .1.3.6.1.2.1.227.1.2.1.5 |
pcePcepPeerSessionExistsIndicates whether a session with this peer currently exists.ro TruthValue (SNMPv2-TC) .1.3.6.1.2.1.227.1.2.1.6 |
pcePcepPeerNumSessSetupOKThe 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.ro Counter32 .1.3.6.1.2.1.227.1.2.1.7 |
pcePcepPeerNumSessSetupFailThe 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.ro Counter32 .1.3.6.1.2.1.227.1.2.1.8 |
pcePcepPeerSessionUpTimeThe value of sysUpTime the last time a session with this peer was successfully established. If pcePcepPeerNumSessSetupOK is zero, then this object contains zero.ro TimeStamp (SNMPv2-TC) .1.3.6.1.2.1.227.1.2.1.9 |
pcePcepPeerSessionFailTimeThe value of sysUpTime the last time a session with this peer failed to be established. If pcePcepPeerNumSessSetupFail is zero, then this object contains zero.ro TimeStamp (SNMPv2-TC) .1.3.6.1.2.1.227.1.2.1.10 |
pcePcepPeerSessionFailUpTimeThe value of sysUpTime the last time a session with this peer failed from active. If pcePcepPeerNumSessSetupOK is zero, then this object contains zero.ro TimeStamp (SNMPv2-TC) .1.3.6.1.2.1.227.1.2.1.11 |
pcePcepPeerAvgRspTimeThe 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.ro Unsigned32 UNITS "milliseconds" .1.3.6.1.2.1.227.1.2.1.12 |
pcePcepPeerLWMRspTimeThe 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.ro Unsigned32 UNITS "milliseconds" .1.3.6.1.2.1.227.1.2.1.13 |
pcePcepPeerHWMRspTimeThe 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.ro Unsigned32 UNITS "milliseconds" .1.3.6.1.2.1.227.1.2.1.14 |
pcePcepPeerNumPCReqSentThe number of PCReq messages sent to this peer.ro Counter32 .1.3.6.1.2.1.227.1.2.1.15 |
pcePcepPeerNumPCReqRcvdThe number of PCReq messages received from this peer.ro Counter32 .1.3.6.1.2.1.227.1.2.1.16 |
pcePcepPeerNumPCRepSentThe number of PCRep messages sent to this peer.ro Counter32 .1.3.6.1.2.1.227.1.2.1.17 |
pcePcepPeerNumPCRepRcvdThe number of PCRep messages received from this peer.ro Counter32 .1.3.6.1.2.1.227.1.2.1.18 |
pcePcepPeerNumPCErrSentThe number of PCErr messages sent to this peer.ro Counter32 .1.3.6.1.2.1.227.1.2.1.19 |
pcePcepPeerNumPCErrRcvdThe number of PCErr messages received from this peer.ro Counter32 .1.3.6.1.2.1.227.1.2.1.20 |
pcePcepPeerNumPCNtfSentThe number of PCNtf messages sent to this peer.ro Counter32 .1.3.6.1.2.1.227.1.2.1.21 |
pcePcepPeerNumPCNtfRcvdThe number of PCNtf messages received from this peer.ro Counter32 .1.3.6.1.2.1.227.1.2.1.22 |
pcePcepPeerNumKeepaliveSentThe number of Keepalive messages sent to this peer.ro Counter32 .1.3.6.1.2.1.227.1.2.1.23 |
pcePcepPeerNumKeepaliveRcvdThe number of Keepalive messages received from this peer.ro Counter32 .1.3.6.1.2.1.227.1.2.1.24 |
pcePcepPeerNumUnknownRcvdThe number of unknown messages received from this peer.ro Counter32 .1.3.6.1.2.1.227.1.2.1.25 |
pcePcepPeerNumCorruptRcvdThe number of corrupted PCEP messages received from this peer.ro Counter32 .1.3.6.1.2.1.227.1.2.1.26 |
pcePcepPeerNumReqSentThe 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.ro Counter32 .1.3.6.1.2.1.227.1.2.1.27 |
pcePcepPeerNumSvecSentThe number of SVEC objects sent to this peer in PCReq messages. An SVEC object represents a set of synchronized requests.ro Counter32 .1.3.6.1.2.1.227.1.2.1.28 |
pcePcepPeerNumSvecReqSentThe number of requests sent to this peer that appeared in one or more SVEC objects.ro Counter32 .1.3.6.1.2.1.227.1.2.1.29 |
pcePcepPeerNumReqSentPendRepThe number of requests that have been sent to this peer for which a response is still pending.ro Counter32 .1.3.6.1.2.1.227.1.2.1.30 |
pcePcepPeerNumReqSentEroRcvdThe 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.ro Counter32 .1.3.6.1.2.1.227.1.2.1.31 |
pcePcepPeerNumReqSentNoPathRcvdThe 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.ro Counter32 .1.3.6.1.2.1.227.1.2.1.32 |
pcePcepPeerNumReqSentCancelRcvdThe 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.ro Counter32 .1.3.6.1.2.1.227.1.2.1.33 |
pcePcepPeerNumReqSentErrorRcvdThe 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.ro Counter32 .1.3.6.1.2.1.227.1.2.1.34 |
pcePcepPeerNumReqSentTimeoutThe 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.ro Counter32 .1.3.6.1.2.1.227.1.2.1.35 |
pcePcepPeerNumReqSentCancelSentThe number of requests that were sent to the peer and explicitly canceled by the local PCEP entity sending a PCNtf.ro Counter32 .1.3.6.1.2.1.227.1.2.1.36 |
pcePcepPeerNumReqSentClosedThe number of requests that were sent to the peer and implicitly canceled when the session they were sent over was closed.ro Counter32 .1.3.6.1.2.1.227.1.2.1.37 |
pcePcepPeerNumReqRcvdThe 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.ro Counter32 .1.3.6.1.2.1.227.1.2.1.38 |
pcePcepPeerNumSvecRcvdThe number of SVEC objects received from this peer in PCReq messages. An SVEC object represents a set of synchronized requests.ro Counter32 .1.3.6.1.2.1.227.1.2.1.39 |
pcePcepPeerNumSvecReqRcvdThe number of requests received from this peer that appeared in one or more SVEC objects.ro Counter32 .1.3.6.1.2.1.227.1.2.1.40 |
pcePcepPeerNumReqRcvdPendRepThe number of requests that have been received from this peer for which a response is still pending.ro Counter32 .1.3.6.1.2.1.227.1.2.1.41 |
pcePcepPeerNumReqRcvdEroSentThe 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.ro Counter32 .1.3.6.1.2.1.227.1.2.1.42 |
pcePcepPeerNumReqRcvdNoPathSentThe 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.ro Counter32 .1.3.6.1.2.1.227.1.2.1.43 |
pcePcepPeerNumReqRcvdCancelSentThe 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.ro Counter32 .1.3.6.1.2.1.227.1.2.1.44 |
pcePcepPeerNumReqRcvdErrorSentThe 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.ro Counter32 .1.3.6.1.2.1.227.1.2.1.45 |
pcePcepPeerNumReqRcvdCancelRcvdThe number of requests that were received from the peer and explicitly canceled by the peer sending a PCNtf.ro Counter32 .1.3.6.1.2.1.227.1.2.1.46 |
pcePcepPeerNumReqRcvdClosedThe number of requests that were received from the peer and implicitly canceled when the session they were received over was closed.ro Counter32 .1.3.6.1.2.1.227.1.2.1.47 |
pcePcepPeerNumRepRcvdUnknownThe 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.ro Counter32 .1.3.6.1.2.1.227.1.2.1.48 |
pcePcepPeerNumReqRcvdUnknownThe 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.ro Counter32 .1.3.6.1.2.1.227.1.2.1.49 |
pcePcepSessTableA 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. SEQUENCE OF PcePcepSessEntry .1.3.6.1.2.1.227.1.3 |
pcePcepSessEntryThis entry represents a single PCEP session in which the local PCEP entity participates. This entry exists only if the corresponding PCEP session has been initialized by some event, such as manual user configuration, auto-discovery of a peer, or an incoming TCP connection. PcePcepSessEntry .1.3.6.1.2.1.227.1.3.1 |
pcePcepSessInitiatorThe 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. Enumeration .1.3.6.1.2.1.227.1.3.1.1 |
pcePcepSessStateLastChangeThe value of sysUpTime at the time this session entered its current state as denoted by the pcePcepSessState object.ro TimeStamp (SNMPv2-TC) .1.3.6.1.2.1.227.1.3.1.2 |
pcePcepSessStateThe 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.ro Enumeration .1.3.6.1.2.1.227.1.3.1.3 |
pcePcepSessConnectRetryThe 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.ro Counter32 .1.3.6.1.2.1.227.1.3.1.4 |
pcePcepSessLocalIDThe 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.ro Unsigned32 .1.3.6.1.2.1.227.1.3.1.5 |
pcePcepSessRemoteIDThe 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.ro Unsigned32 .1.3.6.1.2.1.227.1.3.1.6 |
pcePcepSessKeepaliveTimerThe 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.ro Unsigned32 .1.3.6.1.2.1.227.1.3.1.7 |
pcePcepSessPeerKeepaliveTimerThe 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.ro Unsigned32 .1.3.6.1.2.1.227.1.3.1.8 |
pcePcepSessDeadTimerThe DeadTimer interval for this PCEP session.ro Unsigned32 .1.3.6.1.2.1.227.1.3.1.9 |
pcePcepSessPeerDeadTimerThe 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.ro Unsigned32 .1.3.6.1.2.1.227.1.3.1.10 |
pcePcepSessKAHoldTimeRemThe 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.ro Unsigned32 .1.3.6.1.2.1.227.1.3.1.11 |
pcePcepSessOverloadedIf 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.ro TruthValue (SNMPv2-TC) .1.3.6.1.2.1.227.1.3.1.12 |
pcePcepSessOverloadTimeThe 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.ro Unsigned32 UNITS "seconds" .1.3.6.1.2.1.227.1.3.1.13 |
pcePcepSessPeerOverloadedIf 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.ro TruthValue (SNMPv2-TC) .1.3.6.1.2.1.227.1.3.1.14 |
pcePcepSessPeerOverloadTimeThe 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.ro Unsigned32 UNITS "seconds" .1.3.6.1.2.1.227.1.3.1.15 |
pcePcepSessDiscontinuityTimeThe value of sysUpTime at the time that the statistics in this row were last reset.ro TimeStamp (SNMPv2-TC) .1.3.6.1.2.1.227.1.3.1.16 |
pcePcepSessAvgRspTimeThe 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.ro Unsigned32 UNITS "milliseconds" .1.3.6.1.2.1.227.1.3.1.17 |
pcePcepSessLWMRspTimeThe 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.ro Unsigned32 UNITS "milliseconds" .1.3.6.1.2.1.227.1.3.1.18 |
pcePcepSessHWMRspTimeThe 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.ro Unsigned32 UNITS "milliseconds" .1.3.6.1.2.1.227.1.3.1.19 |
pcePcepSessNumPCReqSentThe number of PCReq messages sent on this session.ro Counter32 .1.3.6.1.2.1.227.1.3.1.20 |
pcePcepSessNumPCReqRcvdThe number of PCReq messages received on this session.ro Counter32 .1.3.6.1.2.1.227.1.3.1.21 |
pcePcepSessNumPCRepSentThe number of PCRep messages sent on this session.ro Counter32 .1.3.6.1.2.1.227.1.3.1.22 |
pcePcepSessNumPCRepRcvdThe number of PCRep messages received on this session.ro Counter32 .1.3.6.1.2.1.227.1.3.1.23 |
pcePcepSessNumPCErrSentThe number of PCErr messages sent on this session.ro Counter32 .1.3.6.1.2.1.227.1.3.1.24 |
pcePcepSessNumPCErrRcvdThe number of PCErr messages received on this session.ro Counter32 .1.3.6.1.2.1.227.1.3.1.25 |
pcePcepSessNumPCNtfSentThe number of PCNtf messages sent on this session.ro Counter32 .1.3.6.1.2.1.227.1.3.1.26 |
pcePcepSessNumPCNtfRcvdThe number of PCNtf messages received on this session.ro Counter32 .1.3.6.1.2.1.227.1.3.1.27 |
pcePcepSessNumKeepaliveSentThe number of Keepalive messages sent on this session.ro Counter32 .1.3.6.1.2.1.227.1.3.1.28 |
pcePcepSessNumKeepaliveRcvdThe number of Keepalive messages received on this session.ro Counter32 .1.3.6.1.2.1.227.1.3.1.29 |
pcePcepSessNumUnknownRcvdThe number of unknown messages received on this session.ro Counter32 .1.3.6.1.2.1.227.1.3.1.30 |
pcePcepSessNumCorruptRcvdThe number of corrupted PCEP messages received on this session.ro Counter32 .1.3.6.1.2.1.227.1.3.1.31 |
pcePcepSessNumReqSentThe 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.ro Counter32 .1.3.6.1.2.1.227.1.3.1.32 |
pcePcepSessNumSvecSentThe number of SVEC objects sent on this session in PCReq messages. An SVEC object represents a set of synchronized requests.ro Counter32 .1.3.6.1.2.1.227.1.3.1.33 |
pcePcepSessNumSvecReqSentThe number of requests sent on this session that appeared in one or more SVEC objects.ro Counter32 .1.3.6.1.2.1.227.1.3.1.34 |
pcePcepSessNumReqSentPendRepThe number of requests that have been sent on this session for which a response is still pending.ro Counter32 .1.3.6.1.2.1.227.1.3.1.35 |
pcePcepSessNumReqSentEroRcvdThe 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.ro Counter32 .1.3.6.1.2.1.227.1.3.1.36 |
pcePcepSessNumReqSentNoPathRcvdThe 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.ro Counter32 .1.3.6.1.2.1.227.1.3.1.37 |
pcePcepSessNumReqSentCancelRcvdThe 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.ro Counter32 .1.3.6.1.2.1.227.1.3.1.38 |
pcePcepSessNumReqSentErrorRcvdThe 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.ro Counter32 .1.3.6.1.2.1.227.1.3.1.39 |
pcePcepSessNumReqSentTimeoutThe 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.ro Counter32 .1.3.6.1.2.1.227.1.3.1.40 |
pcePcepSessNumReqSentCancelSentThe number of requests sent on this session that were sent to the peer and explicitly canceled by the local PCEP entity sending a PCNtf.ro Counter32 .1.3.6.1.2.1.227.1.3.1.41 |
pcePcepSessNumReqRcvdThe 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.ro Counter32 .1.3.6.1.2.1.227.1.3.1.42 |
pcePcepSessNumSvecRcvdThe number of SVEC objects received on this session in PCReq messages. An SVEC object represents a set of synchronized requests.ro Counter32 .1.3.6.1.2.1.227.1.3.1.43 |
pcePcepSessNumSvecReqRcvdThe number of requests received on this session that appeared in one or more SVEC objects.ro Counter32 .1.3.6.1.2.1.227.1.3.1.44 |
pcePcepSessNumReqRcvdPendRepThe number of requests that have been received on this session for which a response is still pending.ro Counter32 .1.3.6.1.2.1.227.1.3.1.45 |
pcePcepSessNumReqRcvdEroSentThe 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.ro Counter32 .1.3.6.1.2.1.227.1.3.1.46 |
pcePcepSessNumReqRcvdNoPathSentThe 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.ro Counter32 .1.3.6.1.2.1.227.1.3.1.47 |
pcePcepSessNumReqRcvdCancelSentThe 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.ro Counter32 .1.3.6.1.2.1.227.1.3.1.48 |
pcePcepSessNumReqRcvdErrorSentThe 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.ro Counter32 .1.3.6.1.2.1.227.1.3.1.49 |
pcePcepSessNumReqRcvdCancelRcvdThe number of requests that were received on this session and explicitly canceled by the peer sending a PCNtf.ro Counter32 .1.3.6.1.2.1.227.1.3.1.50 |
pcePcepSessNumRepRcvdUnknownThe 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.ro Counter32 .1.3.6.1.2.1.227.1.3.1.51 |
pcePcepSessNumReqRcvdUnknownThe 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.ro Counter32 .1.3.6.1.2.1.227.1.3.1.52 |
pcePcepNotificationsMaxRateThis 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).rw Unsigned32 .1.3.6.1.2.1.227.1.4 |
pcePcepConformance OBJECT IDENTIFIER .1.3.6.1.2.1.227.2 |
pcePcepCompliances OBJECT IDENTIFIER .1.3.6.1.2.1.227.2.1 |
pcePcepModuleReadOnlyComplianceThe module is implemented with support for read-only. In other words, only monitoring is available by implementing this MODULE-COMPLIANCE. Unknown .1.3.6.1.2.1.227.2.1.1 |
pcePcepGroups OBJECT IDENTIFIER .1.3.6.1.2.1.227.2.2 |
pcePcepGeneralGroupObjects that apply to all PCEP MIB module implementations. Unknown .1.3.6.1.2.1.227.2.2.1 |
pcePcepNotificationsGroupThe notifications for a PCEP MIB module implementation. Unknown .1.3.6.1.2.1.227.2.2.2 |