The application you select for an integrated service policy must be written to use the Resource Reservation Setup Protocol (RAPI) API or the qtoq sockets APIs. Along with the ReSerVation Protocol (RSVP), these APIs perform the integrated service reservation through the network. If you do not use these APIs, the application will not receive any priority or guarantee.
It is also important to note that this policy enables your applications to receive priority through a network, but cannot guarantee it. All routers and systems along the traffic's path must also use the RSVP to guarantee a reservation.
An end-to-end reservation is dependent on participation throughout the network.
On the Local IP address page, accept the default value and click Next.
On the Integrated Services Type page, select Controlled load and click Next.
On the Integrated Services Marking page, select No,
do not assign a per-hop behavior and click Next.
On the Integrated Services Performance Limits page, enter the following information and click Next:
- Maximum number of flows: 5
- Token rate limit (R): Do not limit
- Token bucket size: 100 Kilobits
- Token rate limit (R): 25 Megabits per second
On the Schedule page, select Active during selected schedule and click New.
On the New Schedule page, enter the following information and click OK:
- Name: primetime
- Time of day: Active at the specific times and add 10:00 a.m. to 4:00 p.m..
- Day of week: Active on the specific days and select Monday through Friday.
On the Schedules page, click Next.
Review the summary information. If accurate, click Finish to create the policy. The main QoS interface lists all the policies that are created on the system. After you complete the wizard, the policy is listed in the right pane.
You have finished configuring the integrated service policy on your system. The next step is to start or update the server.
Parent topic:
Scenario: Predictable B2B traffic