Status in source: current.
Names: mplsTunnelErrorCode
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"mplsTunnelErrorCode",
"OBJECT-TYPE",
"SYNTAX",
"Unsigned32",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"The primary error code associated with the last error. The interpretation of this error code depends on the value of mplsTunnelErrorLastErrorType. If the value of mplsTunnelErrorLastErrorType is noError (0) the value of this object should be 0 and should be ignored. If the value of mplsTunnelErrorLastErrorType is protocol (2) the error should be interpreted in the context of the signling protocol identified by the mplsTunnelSignallingProto object. Values in excess 32767 of are not used by signaling protocols and may safely be used as implementation-specific error codes.\"",
"REFERENCE",
"\"1. Braden, R. (Ed.) et al., Resource ReserVation Protocol -- Version 1 Functional Specification, RFC 2205, September 1997. 2. RSVP-TE: Extensions to RSVP for LSP Tunnels, Awduche et al., RFC 3209, December 2001. 3. Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. (Editor), RFC 3473, January 2003.\"",
"::=",
"{",
"mplsTunnelErrorEntry",
"5",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Unsigned32"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The primary error code associated with the last error. The interpretation of this error code depends on the value of mplsTunnelErrorLastErrorType. If the value of mplsTunnelErrorLastErrorType is noError (0) the value of this object should be 0 and should be ignored. If the value of mplsTunnelErrorLastErrorType is protocol (2) the error should be interpreted in the context of the signling protocol identified by the mplsTunnelSignallingProto object. Values in excess 32767 of are not used by signaling protocols and may safely be used as implementation-specific error codes."
],
[
"REFERENCE",
"1. Braden, R. (Ed.) et al., Resource ReserVation Protocol -- Version 1 Functional Specification, RFC 2205, September 1997. 2. RSVP-TE: Extensions to RSVP for LSP Tunnels, Awduche et al., RFC 3209, December 2001. 3. Generalized MPLS Signaling - RSVP-TE Extensions, Berger, L. (Editor), RFC 3473, January 2003."
],
null,
null,
null
]
}