Fortinet Document Library

Version:


Table of Contents

Related Videos

Scheduling for Traffic Shaping Policies

  • 389 views
  • 7 months ago

New Features

6.2.0
Download PDF
Copy Link

Traffic Shaping Schedules

In a shaping policy, there are many matching criteria available for administrators to match a specific traffic and apply a traffic shaper or shaping group to the traffic. This version adds a new matching criterion: Schedule. This feature gives shaping policy the ability to apply different shaping profiles at different times. Administrators can select a one-time schedule, recurring schedule, or schedule group.

Schedule is not a mandatory setting. If it is not set, then the current date and time are not used to match the traffic.

To configure Traffic Shaping Policy in GUI:
  1. Navigate to Policy & Objects > Traffic Shaping Policy.
  2. Create or edit a Traffic Shaping Policy.
  3. Enable Schedule and select a schedule option.

  4. Configure other options and click OK.
To configure Traffic Shaping Policy in CLI:
config firewall schedule recurring
    edit "work-hours"
        set start 07:00
        set end 20:00
        set day monday tuesday wednesday thursday friday
    next
end

config firewall shaping-policy
    edit 1
        set name "demo"
        set service "ALL"
        set schedule "work-hours"  <<< Can select schedule from one-time schedule, recurring schedule or schedule group
        set dstintf "port1"
        set traffic-shaper "high-priority"
        set traffic-shaper-reverse "high-priority"
        set srcaddr "all"
        set dstaddr "all"
    next
end
To troubleshoot Traffic Shaping Policy in CLI:

The selected schedule is listed in the iprope.

dia firewall iprope list 100015
 
policy index=1 uuid_idx=0 action=accept
flag (0): 
schedule(work-hours)
shapers: orig=high-priority(2/0/134217728) reply=high-priority(2/0/134217728)
cos_fwd=0  cos_rev=0 
group=00100015 av=00000000 au=00000000 split=00000000
host=1 chk_client_info=0x0 app_list=0 ips_view=0
misc=0 dd_type=0 dd_mode=0
zone(1): 0 -> zone(1): 9 
source(1): 0.0.0.0-255.255.255.255, uuid_idx=28, 
dest(1): 0.0.0.0-255.255.255.255, uuid_idx=28, 
service(1): 
    [0:0x0:0/(0,65535)->(0,65535)] helper:auto

Related Videos

Scheduling for Traffic Shaping Policies

  • 389 views
  • 7 months ago

Traffic Shaping Schedules

In a shaping policy, there are many matching criteria available for administrators to match a specific traffic and apply a traffic shaper or shaping group to the traffic. This version adds a new matching criterion: Schedule. This feature gives shaping policy the ability to apply different shaping profiles at different times. Administrators can select a one-time schedule, recurring schedule, or schedule group.

Schedule is not a mandatory setting. If it is not set, then the current date and time are not used to match the traffic.

To configure Traffic Shaping Policy in GUI:
  1. Navigate to Policy & Objects > Traffic Shaping Policy.
  2. Create or edit a Traffic Shaping Policy.
  3. Enable Schedule and select a schedule option.

  4. Configure other options and click OK.
To configure Traffic Shaping Policy in CLI:
config firewall schedule recurring
    edit "work-hours"
        set start 07:00
        set end 20:00
        set day monday tuesday wednesday thursday friday
    next
end

config firewall shaping-policy
    edit 1
        set name "demo"
        set service "ALL"
        set schedule "work-hours"  <<< Can select schedule from one-time schedule, recurring schedule or schedule group
        set dstintf "port1"
        set traffic-shaper "high-priority"
        set traffic-shaper-reverse "high-priority"
        set srcaddr "all"
        set dstaddr "all"
    next
end
To troubleshoot Traffic Shaping Policy in CLI:

The selected schedule is listed in the iprope.

dia firewall iprope list 100015
 
policy index=1 uuid_idx=0 action=accept
flag (0): 
schedule(work-hours)
shapers: orig=high-priority(2/0/134217728) reply=high-priority(2/0/134217728)
cos_fwd=0  cos_rev=0 
group=00100015 av=00000000 au=00000000 split=00000000
host=1 chk_client_info=0x0 app_list=0 ips_view=0
misc=0 dd_type=0 dd_mode=0
zone(1): 0 -> zone(1): 9 
source(1): 0.0.0.0-255.255.255.255, uuid_idx=28, 
dest(1): 0.0.0.0-255.255.255.255, uuid_idx=28, 
service(1): 
    [0:0x0:0/(0,65535)->(0,65535)] helper:auto