Creating A Top-Level Service Policy Profile - Patton electronics SmartNode Series Software Configuration Manual

SmartWare Software Configuration Guide
voice has absolute priority and is therefore effectively bypassing the link arbiter, as shown in
class gets at least 30%, the Web class gets at least 40%, and the Low_Priority policy gets 30% of the overall band-
width. Moreover there is defined that a maximum of 50 packets are queued for the source class Web.
profile service-policy Level_1
rate-limit 512
mode wfq
source class local-voice
priority
source class VPN
share 30
source class Web
share 40
source policy Low_Priority
share 30
Parts of the configuration used for arbiter Low_Priority are listed below. The arbitration uses shaping to share
the bandwidth between the two classes Mail and Default. Therefore each class gets just as much bandwidth as
assigned, but never more. The source class Mail gets 40% and Default gets 60% of the remaining bandwidth as
defined for arbiter Level_1.
profile service-policy Low_Priority
mode shaper
source class mail
rate 40
source class default
rate 60
At last the Level_1 service policy profile has to be used on the outbound IP interface. As shown in the example
in figure 35 a possible related IP interface could be named as "wan".
context ip
interface wan
use profile service-policy Level_1 out
Creating a top-level service policy profile
Each service policy profile defines how the link arbiter has to act as. The link scheduler allows building up hier-
archical scheduling. The uppermost service policy profile, also referred to as top-level service policy profile, is
that service policy profile with which the link arbiter starts performing.
The top-level service policy profile is made up of following components:
• Arbitration schema definition, like weighted fair queuing or shaping
Link scheduler configuration task list
Figure 33. Service policy for level_1 arbiter
Figure 34. Service policy for low_priority arbiter
Figure 35. IP Interface "wan" uses service policy profile
13 • Link scheduler configuration
figure 33. The VPN
147