When an error is detected synchronously, a RAPI error code
is returned via the
Errnop
argument of
When an error is detected asynchronously, it is indicated by a RAPI_PATH_ERROR or RAPI_RESV_ERROR event. An RSVP error code and error value are then contained in the ErrorCode and ErrorValue arguments of the event upcall function. In case of an API error (RSVP error code 20), a RAPI error code is contained in the ErrorValue argument.
A description of RSVP error codes and values can be found in Appendix B of the referenced RFC 2205.
Note that [RAPI_ERR_BADSEND], [RAPI_ERR_BADRECV] and [RAPI_ERR_BADSPORT] occur only asynchronously, as the ErrorValue when the ErrorCode is 20 (API error).
Symbol | Value | Meaning |
---|---|---|
RSVP_Err_NONE | 0 | No error (confirmation) |
RSVP_Err_ADMISSION | 1 | Admission control failure |
RSVP_Err_POLICY | 2 | Policy control failure |
RSVP_Err_NO_PATH | 3 | No path information |
RSVP_Err_NO_SENDER | 4 | No sender information |
RSVP_Err_BAD_STYLE | 5 | Conflicting style |
RSVP_Err_UNKNOWN_STYLE | 6 | Unknown style |
RSVP_Err_BAD_DSTPORT | 7 | Conflicting destination port in session |
RSVP_Err_BAD_SNDPORT | 8 | Conflicting source port |
9 | reserved | |
10 | reserved | |
11 | reserved | |
RSVP_Err_PREEMPTED | 12 | Service preempted |
RSVP_Err_UNKN_OBJ_CLASS | 13 | Unknown object class |
RSVP_Err_UNKNOWN_CTYPE | 14 | Unknown object C-Type |
15 | reserved | |
16 | reserved | |
17 | reserved | |
18 | reserved | |
19 | reserved | |
RSVP_Err_API_ERROR | 20 | API error |
RSVP_Err_TC_ERROR | 21 | Traffic control error |
RSVP_Err_TC_SYS_ERROR | 22 | Traffic control system error |
RSVP_Err_RSVP_SYS_ERROR | 23 | RSVP system error |
Contents | Next section | Index |