This section provides an example for setting overall maximum bandwidth to restrict non-key service traffic on an enterprise network and setting overall guaranteed bandwidth to ensure proper forwarding of key service traffic during peak hours.
As shown in Figure 1, an enterprise purchases 100 Mbit/s bandwidth from an ISP. On office networks, email and ERP traffic is key service traffic, and P2P and online video traffic is non-key service traffic. However, P2P and online video traffic exhausts the limited bandwidth resources on the enterprise network, and key service traffic, such as email and ERP traffic, is not properly forwarded. As a result, emails fail to be sent, and web pages fail to be displayed, which greatly affects the daily operation of the enterprise.
To prevent the preceding symptoms, the enterprise requires to enable the bandwidth management function on the FW to meet the following requirements:
This section provides only the script related to the example.
# sysname FW # time-range work_time period-range 09:00:00 to 18:00:00 working-day # interface GigabitEthernet0/0/2 undo shutdown ip address 1.1.1.1 255.255.255.0 # interface GigabitEthernet0/0/3 undo shutdown ip address 10.3.0.1 255.255.255.0 # firewall zone trust set priority 85 add interface GigabitEthernet0/0/3 # firewall zone untrust set priority 5 add interface GigabitEthernet0/0/2 # traffic-policy profile profile_p2p bandwidth maximum-bandwidth whole both 30000 bandwidth connection-limit whole both 10000 profile profile_email bandwidth guaranteed-bandwidth whole both 60000 rule name policy_p2p source-zone trust destination-zone untrust application app BT application app YouKu action qos profile profile_p2p rule name policy_email source-zone trust destination-zone untrust application app LotusNotes application app OWA time-range work_time action qos profile profile_email