Enum Class PCEPErrors
- All Implemented Interfaces:
Serializable
,Comparable<PCEPErrors>
,Constable
Possible errors listed in various PCE RFC.
- See Also:
-
Nested Class Summary
Nested classes/interfaces inherited from class java.lang.Enum
Enum.EnumDesc<E extends Enum<E>>
-
Enum Constant Summary
Enum ConstantsEnum ConstantDescriptionAssociation group mismatch.Association ID not in range.Association information mismatch.Attempt to establish a second PCEP session: Error-Type = 9.Segment Routing error: Bad label format.Segment Routing error: ERO subobject with invalid SID value.Bidirectional LSP co-routed mismatch.Bidirectional LSP direction mismatch.BRPC procedure not supported by one or more PCEs along the domain path.C bit of the METRIC object set (request rejected).Attempt to add another working/protection LSP for Path Protection Association.Unable to allocate a new binding label/SID.Unable to allocate the specified binding value.A PCC indicates to a PCE that it can not complete the state synchronization.Cannot join the association group.A PCE indicates to a PCC that it can not process (an otherwise valid) LSP State Report.Unable to remove the binding value.The PCE cannot satisfy the request due to insufficient memory.Capability not supported: Error-Type = 2.CCI object missing.Class-Type and setup priority do not form a configured TE-class.The LSP-DB-VERSION TLV Missing when State Synchronization Avoidance enabled.Delegation for PCE-initiated LSP cannot be revoked.DISJOINTNESS-CONFIGURATION TLV missing.END-POINTS object missing.Endpoint mismatch in the association group.ERO Object missing for a path in an LSP Update Request where TE-LSP setup is requested.Global concurrent optimization not allowed (GCO extension).Global concurrent optimization not supported (GCO extension).Inconsistent binding types.Insufficient memory (GCO extension).Invalid Class-Type.Received an invalid LSP DB Version Number.Invalid SID.LABEL-REQUEST TLV missing.LSP Database version mismatch.LSP-DB-VERSION TLV missing.LSP-IDENTIFIERS TLV missing for a path in an LSP Update Request where TE-LSP setup is requested.LSP instantiation error: Internal error.PCE-initiated LSP limit reached.LSP Object missing.LSP is not PCE-initiated.LSP instantiation error: RSVP signaling error.LSP instantiation error: Unacceptable instantiation parameters.Invalid traffic engineering path setup type: Mismatched path setup type.MONITORING object missing.Monitoring message supported but rejected due to policy violation.Native IP object missing.No Keepalive or PCErr message received before the expiration of the KeepWait timer.No Open message received before the expiration of the OpenWait timer.No sufficient LSP change information for incremental LSP state synchronization.Unacceptable but negotiable session characteristics.Unacceptable and non-negotiable session characteristics.Segment Routing error: Non-identical ERO subobjects.Reception of an invalid Open message or a non Open message.Reception of any other message apart from StartTLS, Open, or PCErr.Non-zero PLSP-ID in LSP initiation request.The PCE is not capable of P2MP computation.Not expecting policy parameters.Failure, connection without TLS not possible.Not supported object class.Not supported object Type.O bit of the RP object cleared (request rejected).OF bit of the RP object set (request rejected).Objective function not allowed (request rejected).Operator-configured association information mismatch.Reception of an object with P flag not set although the P flag must be set according to this specification.P2MP Path computation is not allowed.Fragmented Instantiation failure.Fragmented Report failure.P2MP Fragmented request failure.Fragmented Update failure.P2MP-LSP-IDENTIFIERS TLV missing.The PCE is not capable to satisfy the request due to inconsistent END-POINTS.The PCE is not capable to satisfy the request due to no END-POINTS with leaf type 2.The PCE is not capable to satisfy the request due to no END-POINTS with leaf type 3.The PCE is not capable to satisfy the request due to no END-POINTS with leaf type 4.Tunnel ID or End points mismatch for Path Protection Association.PCEP version not supported.Reception of a PCErr message proposing unacceptable session characteristics.Not allowed network performance constraint.Failure, connection without TLS possible.A PCE indicates to a PCC that it has exceeded the resource limit allocated for its state, and thus it cannot accept and process its LSP State Report message.RP object missing.RRO missing for a re-optimization request (R bit of the RP object set).Scheduled TLV missing.Reception of a second Open message with still unacceptable session characteristics.Segment Routing error: Both SID and NAI are absent in ERO subobject.Segment Routing error: Both SID and NAI are absent in RRO subobject.Segment Routing error: Non-identical RRO subobjects.SLS Object missing.Speaker identity included for an LSP that is not PCE initiated.SR Policy Candidate Path Identifier Mismatch.SR Policy Identifers Mismatch.Missing SR Policy Mandatory TLV.Srp Object missing for a path in an LSP Update Request where TE-LSP setup is requested.Reception of StartTLS after any PCEP exchange.No StartTLS message (nor PCErr/Open) before StartTLSWait timer expiry.Synchronized path computation request missing: Error-Type = 7.Too many association groups.Too many LSPs in the association group.Tunnel mismatch in the association group.Unacceptable policy parameters.Attempt to trigger a synchronization when the PCE triggered synchronization capability has not been advertised.Association unknown.Attempted LSP Update Request for an LSP identified by an unknown PLSP-ID.Unknown request reference: Error-Type = 8.Unrecognized EXRS SubObject: Error-Type = 11.Unrecognized object class.Unrecognized object Type.Association Type is not supported.BANDWIDTH object type 3 or 4 not supported.Unsupported Class-Type.Unsupported TLV present in END-POINTS Generalized Endpoint object type.Unsupported endpoint type in END-POINTS Generalized Endpoint object type.Segment Routing error: Unsupported number of Segment ERO subobjects.Unsupported Parameter.Path Setup Type not supported.Unsupported network performance constraint.Protection type is not supported.Invalid traffic engineering path setup type: Unsupported path setup type.Unsupported granularity in the RP object flags.Attempted LSP Update Request if active stateful PCE capability was not negotiated active PCE.Attempted LSP Update Request for a non- delegated LSP.SYMBOLIC-PATH-NAME in use.VIRTUAL-NETWORK-TLV missing. -
Method Summary
Modifier and TypeMethodDescriptionstatic PCEPErrors
forValue
(org.opendaylight.yangtools.yang.common.Uint8 errorType, org.opendaylight.yangtools.yang.common.Uint8 errorValue) org.opendaylight.yangtools.yang.common.Uint8
org.opendaylight.yangtools.yang.common.Uint8
static PCEPErrors
Returns the enum constant of this class with the specified name.static PCEPErrors[]
values()
Returns an array containing the constants of this enum class, in the order they are declared.
-
Enum Constant Details
-
NON_OR_INVALID_OPEN_MSG
Reception of an invalid Open message or a non Open message. -
NO_OPEN_BEFORE_EXP_OPENWAIT
No Open message received before the expiration of the OpenWait timer. -
NON_ACC_NON_NEG_SESSION_CHAR
Unacceptable and non-negotiable session characteristics. -
NON_ACC_NEG_SESSION_CHAR
Unacceptable but negotiable session characteristics. -
SECOND_OPEN_MSG
Reception of a second Open message with still unacceptable session characteristics. -
PCERR_NON_ACC_SESSION_CHAR
Reception of a PCErr message proposing unacceptable session characteristics. -
NO_MSG_BEFORE_EXP_KEEPWAIT
No Keepalive or PCErr message received before the expiration of the KeepWait timer. -
PCEP_VERSION_NOT_SUPPORTED
PCEP version not supported. -
CAPABILITY_NOT_SUPPORTED
Capability not supported: Error-Type = 2. -
UNRECOGNIZED_OBJ_CLASS
Unrecognized object class. -
UNRECOGNIZED_OBJ_TYPE
Unrecognized object Type. -
NOT_SUPPORTED_OBJ_CLASS
Not supported object class. -
NOT_SUPPORTED_OBJ_TYPE
Not supported object Type. -
UNSUPPORTED_PARAMETER
Unsupported Parameter. -
UNSUPPORTED_PERFORMANCE
Unsupported network performance constraint. -
UNSUPPORTED_BANDWIDTH
BANDWIDTH object type 3 or 4 not supported. -
UNSUPPORTED_ENSPOINT_TYPE
Unsupported endpoint type in END-POINTS Generalized Endpoint object type. -
UNSUPPORTED_ENDPOINT_TLV
Unsupported TLV present in END-POINTS Generalized Endpoint object type. -
UNSUPPORTED_RP_FLAGS
Unsupported granularity in the RP object flags. -
C_BIT_SET
C bit of the METRIC object set (request rejected). -
O_BIT_SET
O bit of the RP object cleared (request rejected). -
OF_NOT_ALLOWED
Objective function not allowed (request rejected). -
OF_BIT_SET
OF bit of the RP object set (request rejected). -
GCO_NOT_ALLOWED
Global concurrent optimization not allowed (GCO extension). -
MONITORING_POLICY_VIOLATION
Monitoring message supported but rejected due to policy violation. -
P2MP_COMPUTATION_NOT_ALLOWED
P2MP Path computation is not allowed. -
PERFORMANCE_CONSTRAINT_NOT_ALLOWED
Not allowed network performance constraint. -
RP_MISSING
RP object missing. -
RRO_MISSING
RRO missing for a re-optimization request (R bit of the RP object set). -
END_POINTS_MISSING
END-POINTS object missing. -
MONITORING_OBJECT_MISSING
MONITORING object missing. -
LSP_MISSING
LSP Object missing. -
ERO_MISSING
ERO Object missing for a path in an LSP Update Request where TE-LSP setup is requested. -
SRP_MISSING
Srp Object missing for a path in an LSP Update Request where TE-LSP setup is requested. -
LSP_IDENTIFIERS_TLV_MISSING
LSP-IDENTIFIERS TLV missing for a path in an LSP Update Request where TE-LSP setup is requested. -
LSP_DB_VERSION_MISSING
LSP-DB-VERSION TLV missing. -
SLS_OBJECT_MISSING
SLS Object missing. -
P2MP_LSP_ID_TLV_MISSING
P2MP-LSP-IDENTIFIERS TLV missing. -
DISJOINT_CONFIG_TLV_MISSING
DISJOINTNESS-CONFIGURATION TLV missing. -
SCHEDULED_TLV_MISSING
Scheduled TLV missing. -
CCI_OBJECT_MISSING
CCI object missing. -
VIRTUEL_NET_TLV_MISSING
VIRTUAL-NETWORK-TLV missing. -
NATIVE_IP_OBJ_MISSING
Native IP object missing. -
LABEL_REQUEST_TLV_MISSING
LABEL-REQUEST TLV missing. -
SR_POLICY_TLV_MISSING
Missing SR Policy Mandatory TLV. -
SYNC_PATH_COMP_REQ_MISSING
Synchronized path computation request missing: Error-Type = 7. -
UNKNOWN_REQ_REF
Unknown request reference: Error-Type = 8. -
ATTEMPT_2ND_SESSION
Attempt to establish a second PCEP session: Error-Type = 9. -
P_FLAG_NOT_SET
Reception of an object with P flag not set although the P flag must be set according to this specification. -
BAD_LABEL_VALUE
Segment Routing error: ERO subobject with invalid SID value. -
UNSUPPORTED_NUMBER_OF_SR_ERO_SUBOBJECTS
Segment Routing error: Unsupported number of Segment ERO subobjects. -
BAD_LABEL_FORMAT
Segment Routing error: Bad label format. -
NON_IDENTICAL_ERO_SUBOBJECTS
Segment Routing error: Non-identical ERO subobjects. -
SID_AND_NAI_ABSENT_IN_ERO
Segment Routing error: Both SID and NAI are absent in ERO subobject. -
SID_AND_NAI_ABSENT_IN_RRO
Segment Routing error: Both SID and NAI are absent in RRO subobject. -
SID_NON_IDENTICAL_RRO_SUBOBJECTS
Segment Routing error: Non-identical RRO subobjects. -
UNRECOGNIZED_EXRS_SUB_OBJ
Unrecognized EXRS SubObject: Error-Type = 11. -
UNSUPPORTED_CT
Unsupported Class-Type. -
INVALID_CT
Invalid Class-Type. -
CT_AND_SETUP_PRIORITY_DO_NOT_FORM_TE_CLASS
Class-Type and setup priority do not form a configured TE-class. -
BRPC_NOT_SUPORTED_BY_PCE
BRPC procedure not supported by one or more PCEs along the domain path. -
INSUFFICIENT_MEMORY
Insufficient memory (GCO extension). -
GCO_NOT_SUPPORTED
Global concurrent optimization not supported (GCO extension). -
CANNOT_SATISFY_P2MP_REQUEST_DUE_TO_INSUFFISIENT_MEMMORY
The PCE cannot satisfy the request due to insufficient memory. -
NOT_CAPPABLE_P2MP_COMPUTATION
The PCE is not capable of P2MP computation. -
P2MP_NOT_CAPPABLE_SATISFY_REQ_DUE_LT2
The PCE is not capable to satisfy the request due to no END-POINTS with leaf type 2. -
P2MP_NOT_CAPPABLE_SATISFY_REQ_DUE_LT3
The PCE is not capable to satisfy the request due to no END-POINTS with leaf type 3. -
P2MP_NOT_CAPPABLE_SATISFY_REQ_DUE_LT4
The PCE is not capable to satisfy the request due to no END-POINTS with leaf type 4. -
P2MP_NOT_CAPPABLE_SATISFY_REQ_DUE_INCONSISTENT_EP
The PCE is not capable to satisfy the request due to inconsistent END-POINTS. -
P2MP_FRAGMENTATION_REQ_FAILURE
P2MP Fragmented request failure. -
P2MP_FRAGMENTATION_REP_FAILURE
Fragmented Report failure. -
P2MP_FRAGMENTATION_UPD_FAILURE
Fragmented Update failure. -
P2MP_FRAGMENTATION_INIT_FAILURE
Fragmented Instantiation failure. -
UPDATE_REQ_FOR_NON_LSP
Attempted LSP Update Request for a non- delegated LSP. The PCEP-ERROR Object is followed by the LSP Object that identifies the LSP. -
UPDATE_REQ_FOR_NO_STATEFUL
Attempted LSP Update Request if active stateful PCE capability was not negotiated active PCE. -
UNKNOWN_PLSP_ID
Attempted LSP Update Request for an LSP identified by an unknown PLSP-ID. -
RESOURCE_LIMIT_EXCEEDED
A PCE indicates to a PCC that it has exceeded the resource limit allocated for its state, and thus it cannot accept and process its LSP State Report message. -
LSP_LIMIT_EXCEEDED
PCE-initiated LSP limit reached. -
DELEGATION_NON_REVOKABLE
Delegation for PCE-initiated LSP cannot be revoked. -
NON_ZERO_PLSPID
Non-zero PLSP-ID in LSP initiation request. -
LSP_NOT_PCE_INITIATED
LSP is not PCE-initiated. -
CANNOT_PROCESS_STATE_REPORT
A PCE indicates to a PCC that it can not process (an otherwise valid) LSP State Report. The PCEP-ERROR Object is followed by the LSP Object that identifies the LSP. -
LSP_DB_VERSION_MISMATCH
LSP Database version mismatch. -
DB_VERSION_TLV_MISSING_WHEN_SYNC_ALLOWED
The LSP-DB-VERSION TLV Missing when State Synchronization Avoidance enabled. -
UNEXPECTED_SYNCHRONIZATION_ATTEMPT
Attempt to trigger a synchronization when the PCE triggered synchronization capability has not been advertised. -
CANNOT_COMPLETE_STATE_SYNC
A PCC indicates to a PCE that it can not complete the state synchronization. -
NO_SUFFICIENT_LSP_CHANGE
No sufficient LSP change information for incremental LSP state synchronization. -
INVALID_LSP_DB_VERSION
Received an invalid LSP DB Version Number. -
UNSUPPORTED_PST
Invalid traffic engineering path setup type: Unsupported path setup type. -
MISMATCHED_PST
Invalid traffic engineering path setup type: Mismatched path setup type. -
USED_SYMBOLIC_PATH_NAME
SYMBOLIC-PATH-NAME in use. -
SPEAKER_ID_FOR_LSP_NOT_PCE_INIT
Speaker identity included for an LSP that is not PCE initiated. -
LSP_UNACC_INST_PARAMS
LSP instantiation error: Unacceptable instantiation parameters. -
LSP_INTERNAL_ERROR
LSP instantiation error: Internal error. -
LSP_RSVP_ERROR
LSP instantiation error: RSVP signaling error. -
STARTTLS_RCVD_INCORRECTLY
Reception of StartTLS after any PCEP exchange. -
NON_STARTTLS_MSG_RCVD
Reception of any other message apart from StartTLS, Open, or PCErr. -
NOT_POSSIBLE_WITHOUT_TLS
Failure, connection without TLS not possible. -
POSSIBLE_WITHOUT_TLS
Failure, connection without TLS possible. -
STARTTLS_TIMER_EXP
No StartTLS message (nor PCErr/Open) before StartTLSWait timer expiry. -
UNSUPPORTED_ASSOCIATION_TYPE
Association Type is not supported. -
TOO_MANY_LSP_IN_ASSOCIATION_GROUP
Too many LSPs in the association group. -
TOO_MANY_ASSOCIATION_GROUPS
Too many association groups. -
UNKNOWN_ASSOCIATION
Association unknown. -
OPER_CONFIG_ASSOCIATION_MISMATCH
Operator-configured association information mismatch. -
ASSOCIATION_INFO_MISMATCH
Association information mismatch. -
CANNOT_JOIN_ASSOCIATION_GROUP
Cannot join the association group. -
ASSOCIATION_ID_NOT_IN_RANGE
Association ID not in range. -
PATH_PROTECTION_ID_MISMATCH
Tunnel ID or End points mismatch for Path Protection Association. -
CANNOT_ADD_ANOTHER_PATH_PROTECTION
Attempt to add another working/protection LSP for Path Protection Association. -
UNSUPPORTED_PROTECTION_TYPE
Protection type is not supported. -
NOT_EXPECTING_POLICY_PARAMETERS
Not expecting policy parameters. -
UNACCEPTABLE_POLICY_PARAMETERS
Unacceptable policy parameters. -
ASSOCIATION_GROUP_MISMATCH
Association group mismatch. -
TUNNEL_MISMATCH_IN_ASSOCIATION
Tunnel mismatch in the association group. -
UNSUPPORTED_PATH_SETUP_TYPE
Path Setup Type not supported. -
BIDIRECTIONAL_DIRECTION_MISMATCH
Bidirectional LSP direction mismatch. -
BIDIRECTIONAL_COROUTED_MISMATCH
Bidirectional LSP co-routed mismatch. -
ENDPOINT_MISMATCH_IN_ASSOCIATION
Endpoint mismatch in the association group. -
SR_POLICY_ID_MISMATCH
SR Policy Identifers Mismatch. -
SR_POLICY_CANDIDATE_MISMATCH
SR Policy Candidate Path Identifier Mismatch. -
INVALID_SID
Invalid SID. -
CANNOT_ALLOCATE_SPECIFIED_BINDING
Unable to allocate the specified binding value. -
CANNOT_ALLOCATE_BINDING
Unable to allocate a new binding label/SID. -
CANNOT_REMOVE_BINDING
Unable to remove the binding value. -
INCONSISTENT_BINDING_TYPES
Inconsistent binding types. -
LAST_ERROR
-
-
Method Details
-
values
Returns an array containing the constants of this enum class, in the order they are declared.- Returns:
- an array containing the constants of this enum class, in the order they are declared
-
valueOf
Returns the enum constant of this class with the specified name. The string must match exactly an identifier used to declare an enum constant in this class. (Extraneous whitespace characters are not permitted.)- Parameters:
name
- the name of the enum constant to be returned.- Returns:
- the enum constant with the specified name
- Throws:
IllegalArgumentException
- if this enum class has no constant with the specified nameNullPointerException
- if the argument is null
-
forValue
public static PCEPErrors forValue(org.opendaylight.yangtools.yang.common.Uint8 errorType, org.opendaylight.yangtools.yang.common.Uint8 errorValue) -
getErrorType
public org.opendaylight.yangtools.yang.common.Uint8 getErrorType() -
getErrorValue
public org.opendaylight.yangtools.yang.common.Uint8 getErrorValue()
-