00
|
Confirmation
|
Value=00
|
ResvConf
|
01
|
Admission Control Failure
Subcode:
- 1 Delay bound cannot be met
- 2 Requested bandwidth unavailable
- 3 MTU in flowspec larger than interface MTU
|
Reservation request was rejected by admission control
due to unavailable resources.
The 16 bits of the Error Value field are: ssur
cccc cccc cccc. If ssur=0, the low order bits contain
a subcode.
|
ResvErr
|
02
|
Policy Control Failure
|
Path or Resv message rejected for administrative reason;
for example, preemption.
|
PathErr, ResvErr
|
03
|
No Path Information
|
No Path state exists for this session; Resv message cannot
be forwarded.
|
ResvErr
|
04
|
No Sender Information
|
Path state does not include sender information that matches
the flow descriptor; Resv message cannot be forwarded.
|
ResvErr
|
05
|
Conflicting
|
Reservation style conflicts with existing reservation
style; Resv message cannot be forwarded.
|
ResvErr
|
06
|
Unknown Reservation Style
|
Reservation style unknown; Resv message cannot be forwarded.
|
ResvErr
|
07
|
Conflicting Destination Port
|
RSVP sessions with identical destination address and
protocol values have zero and non-zero destination port values.
|
PathErr, ResvErr
|
08
|
Conflicting Sender Ports
|
RSVP sessions with identical destination address and
protocol values have zero and non-zero sender ports.
|
PathErr
|
09 to 11
|
Reserved
|
|
|
12
|
Service Preempted
Subcode:
Reserved for future definition
|
The service request defined by the style object and the
flow descriptor has been administratively preempted.
Value=ssur cccc cccc cccc. If ssur=0, low order bits contain subcode.
|
ResvErr
|
13
|
Unknown Object Class
|
Contains a 16-bit value composed of Class-Num and C-Type of the unknown object. This error is sent only
if RSVP will reject the message, as determined by the high-order bits
of the Class-Num.
|
PathErr, ResvErr
|
14
|
Unknown Object C-Type
|
Comprised of Class_Num, C-Type of object.
|
ResvErr
|
15-19
|
Reserved
|
|
|
20
|
Reserved for API
|
Contains an API error code that was detected asynchronously
and must be reported by upcall.
|
ResvErr
|
21
|
Traffic Control Error
Subcode:
- 01 Service Conflict—Trying to merge two incompatible
service requests.
- 02 Service Unsupported—Traffic control can't provide
requested service or acceptable replacement.
- 03 Bad Flowspec—Malformed or unreasonable request.
- 04 Bad Tspec— Malformed or unreasonable request.
- 05 Bad Adspec—Malformed or unreasonable request.
|
Traffic control failed due to format or parameters.
Path or Resv message cannot be forwarded. Value=ss00
cccc cccc cccc; ss bits=00.
|
ResvErr
|
22
|
Traffic Control System Error
|
System error detected; RSVP is not expected to interpret
this value.
|
ResvErr
|
23
|
RSVP System Error
|
Implementation-dependent value; RSVP is not expected
to interpret this value.
|
ResvErr
|
24
|
Routing Problem
Subcode:
- 01Bad Explicit Route Object
- 02 Bad Strict node
- 03 Bad loose node
- 04 Bad initial sub-object
- 05 No route available toward destination
- 06 Unacceptable label value
- 07 RRO indicated routing loops
- 08 MPLS being negotiated, but non-RSVP capable router
stands in the path
- 09 MPLS label allocation failure
- 10 Unsupported L3PID
|
For information on this error code, see RFC 3209, RSVP-TE: Extensions to RSVP
for LSP Tunnels.
|
PathErr
ResvErr
|
25
|
Notify Error
subcode:
- 01 RRO too large for MTU
- 02 RRO notification
- 03 Tunnel locally required
|
For information on this error code, see RFC 3209, RSVP-TE: Extensions to RSVP
for LSP Tunnels.
|
ResvErr
|
