Error-Type,Meaning,Error-value,Reference
0,Reserved,0-255: Reserved,[RFC5440]
1,PCEP session establishment failure,0: Unassigned,[RFC5440]
,,"1: reception of an invalid Open message or
a non Open message.",[RFC5440]
,,2: no Open message received before the expiration of the OpenWait timer,[RFC5440]
,,3: unacceptable and non negotiable session characteristics,[RFC5440]
,,4: unacceptable but negotiable session characteristics,[RFC5440]
,,5: reception of a second Open message with still unacceptable session characteristics,[RFC5440]
,,6: reception of a PCErr message proposing unacceptable session characteristics,[RFC5440]
,,7: No Keepalive or PCErr message received before the expiration of the KeepWait timer,[RFC5440]
,,8: PCEP version not supported,[RFC5440]
,,9-255: Unassigned,
2,Capability not supported,0-255: Unassigned,[RFC5440]
3,Unknown Object,0: Unassigned,[RFC5440]
,,1: Unrecognized object class,[RFC5440]
,,2: Unrecognized object Type,[RFC5440]
,,3-255: Unassigned,
4,Not supported object,0: Unassigned,[RFC5440]
,,1: Not supported object class,[RFC5440]
,,2: Not supported object Type,[RFC5440]
,,3: Unassigned,
,,4: Unsupported parameter,[RFC5441]
,,5: Unsupported network performance constraint,[RFC8233]
,,6: BANDWIDTH object type 3 or 4 not supported,[RFC8779]
,,7: Unsupported endpoint type in END-POINTS Generalized Endpoint object type,[RFC8779]
,,8: Unsupported TLV present in END-POINTS Generalized Endpoint object type,[RFC8779]
,,9: Unsupported granularity in the RP object flags,[RFC8779]
,,10-255: Unassigned,
5,Policy violation,0: Unassigned,[RFC5440]
,,1: C bit of the METRIC object set (request rejected),[RFC5440]
,,2: O bit of the RP object cleared (request rejected),[RFC5440]
,,3: objective function not allowed (request rejected),[RFC5541]
,,4: OF bit of the RP object set (request rejected),[RFC5541]
,,5: Global concurrent optimization not allowed,[RFC5557]
,,6: Monitoring message supported but rejected due to policy violation,[RFC5886]
,,7: P2MP Path computation is not allowed,[RFC8306]
,,8: Not allowed network performance constraint,[RFC8233]
,,9-255: Unassigned,
6,Mandatory Object missing,0: Unassigned,[RFC5440]
,,1: RP object missing,[RFC5440]
,,2: RRO missing for a reoptimization request (R bit of the RP object set),[RFC5440]
,,3: END-POINTS object missing,[RFC5440]
,,4: MONITORING object missing,[RFC5886]
,,5-7: Unassigned,
,,8: LSP object missing,[RFC8231]
,,9: ERO object missing,[RFC8231]
,,10: SRP object missing,[RFC8231]
,,11: LSP-IDENTIFIERS TLV missing,[RFC8231]
,,12: LSP-DB-VERSION TLV missing,[RFC8232]
,,13: S2LS object missing,[RFC8623]
,,14: P2MP-LSP-IDENTIFIERS TLV missing,[RFC8623]
,,15: DISJOINTNESS-CONFIGURATION TLV missing,[RFC8800]
,,16: Scheduled TLV missing,[RFC8934]
,,17: CCI object missing,[RFC9050]
,,18: VIRTUAL-NETWORK-TLV missing,[RFC9358]
,,19: Native IP object missing,[RFC9757]
,,20: LABEL-REQUEST TLV missing,[RFC9504]
,,21: Missing SR Policy Mandatory TLV,[RFC-ietf-pce-segment-routing-policy-cp-27]
,,22: Missing SR Policy Association,[RFC-ietf-pce-segment-routing-policy-cp-27]
,,23-255: Unassigned,
7,Synchronized path computation request missing,0-255: Unassigned,[RFC5440]
8,Unknown request reference,0-255: Unassigned,[RFC5440]
9,Attempt to establish a second PCEP session,0-255: Unassigned,[RFC5440]
10,Reception of an invalid object,0: Unassigned,[RFC5440]
,,1: Reception of an object with P flag not set although the P-flag must be set according to this specification.,[RFC5440]
,,2: Bad label value,[RFC8664]
,,3: Unsupported number of SR-ERO subobjects,[RFC8664]
,,4: Bad label format,[RFC8664]
,,5: ERO mixes SR-ERO subobjects with other subobject types,[RFC8664]
,,6: Both SID and NAI are absent in the SR-ERO subobject,[RFC8664]
,,7: Both SID and NAI are absent in the SR-RRO subobject,[RFC8664]
,,8: SYMBOLIC-PATH-NAME TLV missing,[RFC8281]
,,"9: MSD exceeds the
default for the PCEP session",[RFC8664]
,,"10: RRO mixes SR-RRO
subobjects with other subobject types",[RFC8664]
,,11: Malformed object,[RFC8408]
,,12: Missing PCE-SR-CAPABILITY sub-TLV,[RFC8664]
,,13: Unsupported NAI Type in the SR-ERO/SR-RRO subobject,[RFC8664]
,,14: Unknown SID,[RFC8664]
,,15: NAI cannot be resolved to a SID,[RFC8664]
,,16: Could not find SRGB,[RFC8664]
,,17: SID index exceeds SRGB size,[RFC8664]
,,18: Could not find SRLB,[RFC8664]
,,19: SID index exceeds SRLB size,[RFC8664]
,,20: Inconsistent SIDs in SR-ERO / SR-RRO subobjects,[RFC8664]
,,21: MSD must be nonzero,[RFC8664]
,,22: Mismatch of O field in S2LS and LSP object,[RFC8623]
,,23: Incompatible OF codes in H-PCE,[RFC8685]
,,24: Bad BANDWIDTH object type 3 or 4,[RFC8779]
,,25: Unsupported LSP Protection Flags in PROTECTION-ATTRIBUTE TLV,[RFC8779]
,,26: Unsupported Secondary LSP Protection Flags in PROTECTION-ATTRIBUTE TLV,[RFC8779]
,,27: Unsupported Link Protection Type in PROTECTION-ATTRIBUTE TLV,[RFC8779]
,,28: LABEL-SET TLV present with O bit set but without R bit set in RP,[RFC8779]
,,29: Wrong LABEL-SET TLV present with O and L bits set,[RFC8779]
,,30: Wrong LABEL-SET TLV present with O bit set and wrong format,[RFC8779]
,,31: Missing GMPLS-CAPABILITY TLV,[RFC8779]
,,32: Incompatible OF code,[RFC8800]
,,33: Missing PCECC Capability sub-TLV,[RFC9050]
,,34: Missing PCE-SRv6-CAPABILITY sub-TLV,[RFC9603]
,,35: Both SID and NAI are absent in SRv6-RRO subobject,[RFC9603]
,,36: RRO mixes SRv6-RRO subobjects with other subobject types,[RFC9603]
,,37: Invalid SRv6 SID Structure,[RFC9603]
,,"38: Conflicting Path ID
(TEMPORARY - registered 2022-05-09, extension registered 2025-04-04, expires 2026-05-09)",[draft-ietf-pce-multipath-07]
,,39: PCECC NATIVE-IP-TE-CAPABILITY bit is not set,[RFC9757]
,,40: Unsupported number of SRv6-ERO subobjects,[RFC9603]
,,41: Unsupported NAI Type in the SRv6-ERO/SRv6-RRO subobject,[RFC9603]
,,42: Both SID and NAI are absent in the SRv6-ERO subobject,[RFC9603]
,,43: ERO mixes SRv6-ERO subobjects with other subobject types,[RFC9603]
,,44: Missing SRPOLICY-CAPABILITY,[RFC-ietf-pce-segment-routing-policy-cp-27]
,,45-255: Unassigned,
11,Unrecognized EXRS subobject,0-255: Unassigned,[RFC5521]
12,Diffserv-aware TE error,0: Unassigned,[RFC5455]
,,1: Unsupported class-type,[RFC5455]
,,2: Invalid class-type,[RFC5455]
,,3: Class-Type and setup priority do not form a configured TE-class,[RFC5455]
,,4-255: Unassigned,
13,BRPC procedure completion failure,0: Unassigned,[RFC5441]
,,1: BRPC procedure not supported by one or more PCEs along the domain path,[RFC5441]
,,2-255: Unassigned,
14,Unassigned,0-255: Unassigned,
15,Global Concurrent Optimization Error,0: Unassigned,[RFC5557]
,,1: Insufficient memory,[RFC5557]
,,2: Global concurrent optimization not supported,[RFC5557]
,,3-255: Unassigned,
16,P2MP Capability Error,0: Unassigned,[RFC8306]
,,1: The PCE cannot satisfy the request due to insufficient memory,[RFC8306]
,,2: The PCE is not capable of P2MP computation,[RFC8306]
,,3-255: Unassigned,
17,P2MP END-POINTS Error,0: Unassigned,[RFC8306]
,,1: The PCE cannot satisfy the request due to no END-POINTS with leaf type 2,[RFC8306]
,,2: The PCE cannot satisfy the request due to no END-POINTS with leaf type 3,[RFC8306]
,,3: The PCE cannot satisfy the request due to no END-POINTS with leaf type 4,[RFC8306]
,,4: The PCE cannot satisfy the request due to inconsistent END-POINTS,[RFC8306]
,,5-255: Unassigned,
18,P2MP Fragmentation Error,0: Unassigned,[RFC8306]
,,1: Fragmented request failure,[RFC8306]
,,2: Fragmented Report failure,[RFC8623]
,,3: Fragmented Update failure,[RFC8623]
,,4: Fragmented Instantiation failure,[RFC8623]
,,5-255: Unassigned,
19,Invalid Operation,0: Unassigned,[RFC8231]
,,"1: Attempted LSP Update Request for a non-delegated
LSP. The PCEP-ERROR object is followed by the LSP
object that identifies the LSP.",[RFC8231]
,,2: Attempted LSP Update Request if the stateful PCE capability was not advertised.,[RFC8231]
,,3: Attempted LSP Update Request for an LSP identified by an unknown PLSP-ID.,[RFC8231]
,,4: Unassigned,
,,5: Attempted LSP State Report if active stateful PCE capability was not advertised.,[RFC8231]
,,6: PCE-initiated LSP limit reached,[RFC8281]
,,7: Delegation for PCE-initiated LSP cannot be revoked,[RFC8281]
,,8: Non-zero PLSP-ID in LSP Initiate Request,[RFC8281]
,,9: LSP is not PCE initiated,[RFC8281]
,,10: PCE-initiated operation-frequency limit reached,[RFC8281]
,,"11: Attempted LSP State Report
for P2MP if stateful PCE capability for P2MP was not advertised",[RFC8623]
,,"12: Attempted LSP Update Request
for P2MP if active stateful PCE capability for P2MP was not advertised",[RFC8623]
,,"13: Attempted LSP Instantiation
Request for P2MP if stateful PCE
instantiation capability for P2MP was not advertised",[RFC8623]
,,14: Auto-Bandwidth capability was not advertised,[RFC8733]
,,15: Attempted LSP scheduling while the scheduling capability was not advertised,[RFC8934]
,,16: Attempted PCECC operations when PCECC capability was not advertised,[RFC9050]
,,17: Stateful PCE capability was not advertised,[RFC9050]
,,18: Unknown Label,[RFC9050]
,,19: Attempted SRv6 when the capability was not advertised,[RFC9603]
,,"20: Not supported path backup
(TEMPORARY - registered 2022-05-09, extension registered 2025-04-04, expires 2026-05-09)",[draft-ietf-pce-multipath-07]
,,"21: Non-empty path
(TEMPORARY - registered 2022-05-09, extension registered 2025-04-04, expires 2026-05-09)",[draft-ietf-pce-multipath-07]
,,"22: Only one BPI, EPR, or PPA object can be included in this message",[RFC9757]
,,23: LSP state info unavailable for reoptimization,[RFC9504]
,,24: LSP state info for route exclusion not found,[RFC9504]
,,25: Attempted LSP update request for GMPLS if stateful PCE capability not advertised,[RFC9504]
,,26: Attempted LSP State Report for GMPLS if stateful PCE capability not advertised,[RFC9504]
,,27: Attempted LSP instantiation request for GMPLS if stateful PCE instantiation capability not advertised,[RFC9504]
,,28: Use of the Generalized Endpoint object type for non-GMPLS LSPs,[RFC9504]
,,29: Attempted Native IP operations when the capability was not advertised,[RFC9757]
,,30: Unknown Native IP Info,[RFC9757]
,,31: Invalid Color,[RFC-ietf-pce-pcep-color-12]
,,32: Inconsistent Color,[RFC-ietf-pce-pcep-color-12]
,,33-255: Unassigned,
20,LSP State Synchronization Error,0: Unassigned,[RFC8231]
,,"1: A PCE indicates to a PCC that it cannot process
(an otherwise valid) LSP State Report. The PCEP-
ERROR object is followed by the LSP object
that identifies the LSP.",[RFC8231]
,,2: LSP-DB version mismatch.,[RFC8232]
,,"3: Attempt to trigger
synchronization before PCE
trigger.",[RFC8232]
,,"4: Attempt to trigger a
synchronization when the
PCE triggered synchronization
capability has not been
advertised.",[RFC8232]
,,"5: A PCC indicates to a PCE that it cannot complete
the State Synchronization.",[RFC8231]
,,6: Received an invalid LSP-DB Version Number.,[RFC8232]
,,7: Received an invalid Speaker Entity Identifier.,[RFC8232]
,,8-255: Unassigned,
21,Invalid traffic engineering path setup type,0: Unassigned,[RFC8408]
,,1: Unsupported path setup type,[RFC8408]
,,2: Mismatched path setup type,[RFC8408]
,,3-255: Unassigned,
22,Unassigned,0-255: Unassigned,
23,Bad parameter value,0: Unassigned,[RFC8281]
,,1: SYMBOLIC-PATH-NAME in use,[RFC8281]
,,2: Speaker identity included for an LSP that is not PCE initiated,[RFC8281]
,,3-255: Unassigned,
24,LSP instantiation error,0: Unassigned,[RFC8281]
,,1: Unacceptable instantiation parameters,[RFC8281]
,,2: Internal error,[RFC8281]
,,3: Signaling error,[RFC8281]
,,4-255: Unassigned,
25,PCEP StartTLS failure,0: Unassigned,[RFC8253]
,,1: Reception of StartTLS after any PCEP exchange,[RFC8253]
,,"2: Reception of any other message apart from StartTLS, Open, or PCErr",[RFC8253]
,,"3: Failure, connection without TLS is not possible",[RFC8253]
,,"4: Failure, connection without TLS is possible",[RFC8253]
,,5: No StartTLS message (nor PCErr/Open) before StartTLSWait timer expiry,[RFC8253]
,,6-255: Unassigned,
26,Association Error,0: Unassigned,[RFC8697]
,,1: Association Type is not supported,[RFC8697]
,,2: Too many LSPs in the association group,[RFC8697]
,,3: Too many association groups,[RFC8697]
,,4: Association unknown,[RFC8697]
,,5: Operator-configured association information mismatch,[RFC8697]
,,6: Association information mismatch,[RFC8697]
,,7: Cannot join the association group,[RFC8697]
,,8: Association ID not in range,[RFC8697]
,,"9: Tunnel ID or End points mismatch for
Path Protection Association",[RFC8745]
,,10: Attempt to add another working/protection LSP for Path Protection Association,[RFC8745]
,,11: Protection type is not supported,[RFC8745]
,,12: Not expecting policy parameters,[RFC9005]
,,13: Unacceptable policy parameters,[RFC9005]
,,14: Association group mismatch,[RFC9059]
,,15: Tunnel mismatch in the association group,[RFC9059]
,,16: Path Setup Type not supported,[RFC9059]
,,17: Bidirectional LSP direction mismatch,[RFC9059]
,,18: Bidirectional LSP co-routed mismatch,[RFC9059]
,,19: Endpoint mismatch in the association group,[RFC9059]
,,20: SR Policy Identifers Mismatch,[RFC-ietf-pce-segment-routing-policy-cp-27]
,,21: SR Policy Candidate Path Identifier Mismatch,[RFC-ietf-pce-segment-routing-policy-cp-27]
,,22-255: Unassigned,
27,WSON RWA error,0: Unassigned,[RFC8780]
,,1: Insufficient memory,[RFC8780]
,,2: RWA computation not supported,[RFC8780]
,,3: Syntactical encoding error,[RFC8780]
,,4-255: Unassigned,
28,H-PCE Error,0: Unassigned,[RFC8685]
,,1: H-PCE Capability not advertised,[RFC8685]
,,2: Parent PCE Capability cannot be provided,[RFC8685]
,,3-255: Unassigned,
29,Path computation failure,0: Unassigned,[RFC8779]
,,1: Unacceptable request message,[RFC8779]
,,2: Generalized bandwidth value not supported,[RFC8779]
,,3: Label set constraint could not be met,[RFC8779]
,,4: Label constraint could not be met,[RFC8779]
,,5: Constraints could not be met for some intervals,[RFC8934]
,,6-255: Unassigned,
30,FlowSpec error,0: Unassigned,[RFC9168]
,,1: Unsupported FlowSpec,[RFC9168]
,,2: Malformed FlowSpec,[RFC9168]
,,3: Unresolvable Conflict,[RFC9168]
,,4: Unknown FlowSpec,[RFC9168]
,,5: Unsupported LPM Route,[RFC9168]
,,6-255: Unassigned,
31,PCECC failure,0: Unassigned,[RFC9050]
,,1: Label out of range,[RFC9050]
,,2: Instruction failed,[RFC9050]
,,3: Invalid CCI,[RFC9050]
,,4: Unable to allocate the specified CCI,[RFC9050]
,,5: Invalid next-hop information,[RFC9050]
,,6-255: Unassigned,
32,Binding label/SID failure,0: Unassigned,[RFC9604]
,,1: Invalid SID,[RFC9604]
,,2: Unable to allocate the specified binding value,[RFC9604]
,,3: Unable to allocate a new binding label/SID,[RFC9604]
,,4: Unable to remove the binding value,[RFC9604]
,,5: Inconsistent binding types,[RFC9604]
,,6-255: Unassigned,
33,Native IP TE failure,0: Unassigned,[RFC9757]
,,1: Local IP is in use,[RFC9757]
,,2: Remote IP is in use,[RFC9757]
,,3: Explicit Peer Route Error,[RFC9757]
,,4: EPR/BPI Peer Info mismatch,[RFC9757]
,,5: BPI/PPA Address Family mismatch,[RFC9757]
,,6: PPA/BPI Peer Info mismatch,[RFC9757]
,,7-255: Unassigned,
34-251,Unassigned,0-255: Unassigned,
252-255,Reserved for Experimental Use,0-255: Reserved for Experimental Use,[RFC9756]
Presently we were in a very dark road, and at a point where it dropped suddenly between steep sides we halted in black shadow. A gleam of pale sand, a whisper of deep flowing waters, and a farther glimmer of more sands beyond them challenged our advance. We had come to a "grapevine ferry." The scow was on the other side, the water too shoal for the horses to swim, and the bottom, most likely, quicksand. Out of the blackness of the opposite shore came a soft, high-pitched, quavering, long-drawn, smothered moan of woe, the call of that snivelling little sinner the screech-owl. Ferry murmured to me to answer it and I sent the same faint horror-stricken tremolo back. Again it came to us, from not farther than one might toss his cap, and I followed Ferry down to the water's edge. The grapevine guy swayed at our side, we heard the scow slide from the sands, and in a few moments, moved by two videttes, it touched our shore. Soon we were across, the two videttes riding with us, and beyond a sharp rise, in an old opening made by the swoop of a hurricane, we entered the silent unlighted bivouac of Ferry's scouts. Ferry got down and sat on the earth talking with Quinn, while the sergeants quietly roused the sleepers to horse. Plotinus is driven by this perplexity to reconsider the whole theory of Matter.477 He takes Aristotle¡¯s doctrine as the groundwork of his investigation. According to this, all existence is divided into Matter and Form. What we know of things¡ªin other words, the sum of their differential characteristics¡ªis their Form. Take away this, and the unknowable residuum is their Matter. Again, Matter is the vague indeterminate something out of which particular Forms are developed. The two are related as Possibility to Actuality, as the more generic to the more specific substance through every grade of classification and composition. Thus there are two Matters, the one sensible and the other intelligible. The former constitutes the common substratum of bodies, the other the common element of ideas.478 The general distinction between Matter and Form was originally suggested to Aristotle by Plato¡¯s remarks on the same subject; but he differs325 from his master in two important particulars. Plato, in his Timaeus, seems to identify Matter with space.479 So far, it is a much more positive conception than the ?λη of the Metaphysics. On the other hand, he constantly opposes it to reality as something non-existent; and he at least implies that it is opposed to absolute good as a principle of absolute evil.480 Thus while the Aristotelian world is formed by the development of Power into Actuality, the Platonic world is composed by the union of Being and not-Being, of the Same and the Different, of the One and the Many, of the Limit and the Unlimited, of Good and Evil, in varying proportions with each other. The Lawton woman had heard of an officer's family at Grant, which was in need of a cook, and had gone there. [See larger version] On the 8th of July an extraordinary Privy Council was summoned. All the members, of whatever party, were desired to attend, and many were the speculations as to the object of their meeting. The general notion was that it involved the continuing or the ending of the war. It turned out to be for the announcement of the king's intended marriage. The lady selected was Charlotte, the second sister of the Duke of Mecklenburg-Strelitz. Apart from the narrowness of her education, the young princess had a considerable amount of amiability, good sense, and domestic taste. These she shared with her intended husband, and whilst they made the royal couple always retiring, at the same time they caused them to give, during their lives, a moral air to their court. On the 8th of September Charlotte arrived at St. James's, and that afternoon the marriage took place, the ceremony being performed by the Archbishop of Canterbury. On the 22nd the coronation took place with the greatest splendour. Mother and girls were inconsolable, for each had something that they were sure "Si would like," and would "do him good," but they knew Josiah Klegg, Sr., well enough to understand what was the condition when he had once made up his mind. CHAPTER V. THE YOUNG RECRUITS Si proceeded to deftly construct a litter out of the two guns, with some sticks that he cut with a knife, and bound with pawpaw strips. His voice had sunk very low, almost to sweetness. A soft flurry of pink went over her face, and her eyelids drooped. Then suddenly she braced herself, pulled herself taut, grew combative again, though her voice shook. HoME²Ô¾®Ïè̫ʲôÐÇ×ù
ENTER NUMBET 0016www.hbstkjyxgs.com.cn
www.maxview.net.cn
www.gmchain.com.cn
www.kcchain.com.cn
www.hnmjcx.com.cn
lfchain.com.cn
www.fmlpjs.com.cn
www.nbhongyuan.com.cn
noeixr.com.cn
woooyoo.com.cn