Wireless Controller
Dedicated Wi-Fi control and management for high density and mobility
nsamuel
Staff
Staff
Article Id 189849
Description

QoS Rule to throttle the data traffic on particular port


Scope

KB ARTICLE TYPE: Troubleshooting

RELATED PRODUCTS: N/A

RELATED SOFTWARE VERSIONS: N/A

KEYWORDS: data traffic, bucket rate box, QOS


Solution

STEPS TAKEN FOR TROUBLESHOOTING:

STEP 1: Create a QoS rule by adding the information given below. Add 2 QoS rules; one in each direction of traffic.

STEP 2: Create a unique numeric identifier for the rule. If the data traffic has to be throttled for all the clients then you can leave the Destination and the Source IP as 0’s. Make sure that you turn ON the Destination Portmatch, Source Portmatch and the Network Protocol match.

STEP 3: Type the TCP or UDP port to be used as criteria for matching the rule on which the data traffic has to be throttled. (if necessary)

STEP 4: Give the protocol number depending upon the data traffic. For TCP protocol number is 6 and the protocol number for UDP is 17. (if necessary)

STEP 5: Set the QoS Protocol to other and set the Action list to Forward and the Drop policy as Head.

STEP 6: In the Token Bucket Rate box, specify the rate or maximum number of bytes allowed for a flow; bytes exceeding this rate will be dropped.

1000: 8Kbps.
5000: 40Kbps
12500: 100Kbps
125000: 1Mbps
625000: 5Mbps
1000000 : 8 Mpbs

STEP 7: Leave the priority to 0.

For E.g: the rule could be like the following:

QoS and Firewall Rules

ID : 20
Id Class flow class : on
Destination IP : 0.0.0.0
Destination IP match : none
Destination IP flow class : none
Destination Netmask : 0.0.0.0
Destination Port : 139
Destination Port match : on
Destination Port flow class : none
Source IP : 0.0.0.0
Source IP match : none
Source IP flow class : none
Source Netmask : 0.0.0.0
Source Port : 0
Source Port match : on
Source Port flow class : none
Network Protocol : 6
Network Protocol match : on
Network Protocol flow class : none
Firewall Filter ID:
Filter Id match : none
Filter Id Flow Class : none
Packet minimum length : 0
Packet Length match : none
Packet Length flow class : none
Packet maximum length : 0
QoS Protocol : other
Average Packet Rate : 0
Action : forward
Drop Policy : head
Token Bucket Rate : 1000
Priority : 0
Traffic Control : off
DiffServ Codepoint : disabled
Qos Rule Logging : on
Qos Rule Logging Frequency : 60

ID : 21
Id Class flow class : on
Destination IP : 0.0.0.0
Destination IP match : none
Destination IP flow class : none
Destination Netmask : 0.0.0.0
Destination Port : 0
Destination Port match : on
Destination Port flow class : none
Source IP : 0.0.0.0
Source IP match : none
Source IP flow class : none
Source Netmask : 0.0.0.0
Source Port : 139
Source Port match : on
Source Port flow class : none
Network Protocol : 6
Network Protocol match : on
Network Protocol flow class : none
Firewall Filter ID :
Filter Id match : none
Filter Id Flow Class : none
Packet minimum length : 0
Packet Length match : none
Packet Length flow class : none
Packet maximum length : 0
QoS Protocol : other
Average Packet Rate : 0
Action : forward
Drop Policy : head
Token Bucket Rate : 1000
Priority : 0
Traffic Control : off
DiffServ Codepoint : disabled
Qos Rule Logging : on
Qos Rule Logging Frequency : 60

RESOLUTION: The data traffic can be throttled down by defining QOS rule by giving the token bucket rate according to the requirement.


Contributors