Solstice Bandwidth Reservation Protocol 1.0 Administration Guide
- Introducing Solstice Bandwidth Reservation Protocol
-
- Sending and Receiving RSVP Messages
-
- The Solstice Bandwidth Reservation Protocol Daemon
-
- Admission Control Module
-
- API Interface
-
- Network Interface
-
- Routing Interface
-
- Log Interface
-
- Configuring Solstice Bandwidth Reservation Protocol
-
- Modifying the Default Configuration File
-
- Configuration Parameters
-
- interface
-
- log
-
- version
-
- syslog
-
- router
-
- inact_to
-
- Example rsvpd.conf Configuration File
-
- Locating the Daemon Configuration File
-
- Locating the Daemon
-
- Starting and Stopping the Daemon Manually
-
- Shared Path Installation
-
- Solstice Bandwidth Reservation Protocol Management Tools
-
- RSVP Logging Facility
-
- Recommended Logging Levels
-
- Errors
-
- Setting the Logging Levels and Trace Output
-
- Command Interpreter Options
-
- Decoding and Displaying the rsvpd Log Files
-
- Example Log Traces
-
- The rsvpd daemon on jamima is started.
-
- The RSVP application on jamima calls the rapi_session() function.
-
- The RSVP application on jamima calls the rapi_sender() function.
-
- The rsvpd daemon on jamima generates a PATH refresh message.
-
- The RSVP application on riemann calls the rapi_reserve() function.
-
- The RSVP application on riemann calls the rapi_release() function.
-
- The RSVP application on jamima calls the rapi_release() function
-
- Packet Error Code and Values
-
- Displaying the Resource Reservation Status
-
- Localizing Message Output
-
Solstice Bandwidth Reservation Protocol 1.0 Administration Guide - 29 JAN 97
Copyright 1997 Sun Microsystems, Inc. 2550 Garcia Ave., Mt. View, CA 94043-1100 USA.
Copyright in French
Generated with CERN WebMaker