QOS configuration of the S9300 Switch

QOS configuration of the S9300 port of the S9300 switch the queue scheduling mechanism. Each physical port has eight sending queues. The queue 7 has the highest priority, and the queue 0 has the lowest priority. The sending port supports PQ, WRR, and DRR scheduling methods, and hybrid scheduling of PQ + WRR and PQ + DRR. When www.2cto.com is used for hybrid scheduling, packets in the PQ queue are first scheduled. The highest priority queue is first scheduled during the PQ scheduling, and then the queue with lower scheduling priority is later. After the PQ queue is scheduled, The WRR or DRR queue will be scheduled again. For WRR and DRR queues, the scheduling queue guarantees the bandwidth and then performs WRR and DRR scheduling based on the weight. How to support port speed limit support the speed limit of the inbound port configure the qos car under the Port, In addition, you can configure the stream policy, the classifier configures ACL rules to limit the flow. Qos car does not support outbound port speed limiting, but outbound port speed limiting and traffic limiting can be achieved through the outbound traffic forwarding policy or port traffic integer. Whether www.2cto.com S9300 supports outbound access control, redirection, speed limit, and port image Access Control in both outbound and inbound directions. Supports inbound traffic redirection, but does not support outbound traffic redirection. Supports outbound and inbound speed limits. Supports both inbound and outbound images. How to perform Traffic Shaping and configure traffic shaping is to control the output packet rate so that the packet is sent at a uniform rate. You can use the Traffic Shaping function to limit the outbound port speed. Traffic Shaping can be performed on ports or priority queues. Go to the port view and generate traffic shaping: [Quidway] interface gigabitethernet 3/0/1 [Quidway-GigabitEthernet3/0/1] qos lr cir 100000 [Quidway-GigabitEthernet3/0/1] qos queue 0 shaping cir 50000 pir 100000 port Max rate setting must be greater than or equal to 64 K. On S9300V1R1 and S9300V1R2C00 devices, queue shaping can be configured only for non-PQ queues. Whether cross-board redirection is supported how to configure S9300 to support cross-board redirection in the INBOUND direction, and redirection can be performed based on a specific stream to redirect the output direction of the message, it can be output to the CPU, other ports, or other IP addresses. The redirection configuration is as follows: Configure ACL rules: [Quidway] acl number 3000 [S9300-acl-adv-3000] rule 0 permit ip source 192.168.1.1 0 configure classifier: [Quidway] traffic classifier 3000 [QUIDWAY-classifier-3000] if-match acl 3000 configure stream Action: [Quidway] traffic behavior 3000 [Quidway-behavior-3000] redirect interface GigabitEthernet 4/0/0 configure stream policy: [Quidway] traffic policy 3000 [Quidway-trafficpolicy-3000] classifier 3000 behavior 3000 port streaming policy: [Quidway-GigabitE Thernet3/0/0] When traffic-policy 3000 inbound S9300's traffic-policy references the effective mechanism of acl actions and uses traffic-policy to reference acl scenarios, the permit/deny in the acl rule takes effect, combined with permit/deny in behavior, if either of them has a deny, the deny action is actually executed. The default action is permit. What is the difference between the port-based CAR and the global-based CAR-based port-based CAR? The speed of this port is separately enjoyed, while the global-based CAR-based port is equivalent to sharing all ports. For example, CAR 5000 kbit/s. If the application is under the port, the port speed is limited. The maximum rate of sent or received packets is 5000 kbit/s. If the application is under the global conditions, it is equivalent to the sum of the packets forwarded by all ports and can only reach 5000 kbit/s at most. In S9300 or byte-based S9300, The eseries and F series boards support byte-based and packet-based traffic statistics, the S Series boards only support packet-based traffic statistics. After configuring link aggregation, S9300 can configure the port speed limit and how to apply it. S9300 supports configuring the inbound port speed limit function (using the qos car command) in Eth-Trunk. After Configuration: if each member port is on a different board, each port has an exclusive speed limit value. If the member ports are on the same board, the ports share the speed limit value. The shared bandwidth is randomly allocated. If the S9300 port is used as the CAR port and the global CAR port is used as the CAR port, the port enjoys this rate separately, and all ports share this rate when the global CAR is used. For example, for CAR 5000 kbit/s: if the application is on a port, the port speed is limited. The maximum rate of sent or received packets is 5000 kbit/s. If the application is global, the sum of the packets forwarded by all ports can only reach 5000 kbit/s. S9300 V100R003 G24SA Board whether remark 8021pS9300V100R001 supports inbound remark 8021 p and outbound remark. Eseries and F series boards support both the inbound and outbound directions. The G24SA board is a series of S boards, so the inbound remark 8021 p is not supported. How to configure S9300 to support cross-board redirection in the Inbound direction? The redirection can be performed based on a specific stream, the redirection packet can be output to the CPU, other ports, or other IP addresses. The method for configuring Layer 2 redirection to an interface is as follows: configure ACL rules [S9300] acl number 3000 [S9300-acl-adv-3000] rule 0 permit ip source 1.1.1.1 0 2 [S9300-acl-adv-3000] quit configure stream classification [S9300] traffic classifier 3000 [S9300-classifier-3000] if-match acl 3000 [S9300-classifier-3000] quit configuration popular for [S9300] traffic behavior 3000 [S9300-behavior-3000] redirect interface gigabitethernet 3/0/0 [S9300-behavior-3000] quit configure stream policy [S9300] traffic policy 3000 [S9300-trafficp Olicy-3000] classifier 3000 behavior 3000 [S9300-trafficpolicy-3000] quit interface application flow policy [S9300] interface gigabitethernet3/0/0 [S9300-GigabitEthernet3/0/0] traffic-policy 3000 inbound S9300 classification statistics in what units the S Series board does not support Statistics in bytes, other boards support traffic classification statistics in packets or bytes. How does the second-level shared CAR of S9300 take effect? The second-level shared CAR can be configured on S9300. The following configuration is used as an example. The principle of the second-level shared CAR is as follows: [S9300] qos car car1 cir 16000 [S9300] traffic classifier 1 [S9300-classifier-1] if-match vlan-id 100 [S9300-classifier-1] quit [S9300] traffic classifier 2 [S9300-classifier-2] if-match vlan-id 101 [S9300-classifier-2] quit [S9300] traffic behavior 1 [S9300-behavior-1] car cir 6000 pir 8000 [S9300-behavior-1] car car1 share [S9300-behavior-1] quit [S9300] traffic behavior 2 [S9300-behavior-2] car cir 8000 pir 10000 [S9300-behavior-2] car car1 share [S9300-behavior-2] quit [S9300] traffic policy 1 [S9300-trafficpolicy-1] classifier 1 behavior 1 [S9300-trafficpolicy-1] classifier 2 behavior 2 [S9300-trafficpolicy-1] quit apply stream policy 1 under the port, test the traffic of VLAN 100 and VLAN 101 respectively. When the traffic speed of VLAN 100 is below 6 m and that of VLAN 101 is below 8 m, the two flows can be effectively guaranteed without packet loss; when the VLAN 100 flow rate exceeds 6 M and the VLAN 101 flow rate exceeds 8 M, both traffic will be lost. The total bandwidth of the two streams is 16 MB, that is, the shared CAR value. The above results show that the second-level shared CAR has no limit on the flow rate of the first-level CAR which is less than that of the CIR, but only on the flow rate between the CIR and PIR. Therefore, when the second-level shared CAR is configured, the shared CAR value must be between the sum of CIR and PIR. Otherwise, the second-level shared CAR is meaningless. In S9300, how to configure the speed limit S9300 to support port speed limit and flow speed limit is as follows: configure the Port Speed Limit # configure the inbound port speed limit with the speed limit of 10 MB. [Quidway] qos car car1 cir 10240 cbs 1024000 [Quidway-GigabitEthernet1/0/0] qos car inbound car1 # configure the outbound port speed limit, with a speed limit of 10 M. [Quidway] interface gigabitethernet1/0/0 [Quidway-GigabitEthernet1/0/0] qos lr cir 10240 pir 10240 configure the flow speed limit # configure the flow speed limit, any flow speed limit on the inbound and outbound ports is 10 M. [Quidway] traffic classifier c1 operator and [Quidway-classifier-c1] if-match any [Quidway-classifier-c1] quit [Quidway] traffic behavior b1 [Quidway-behavior-b1] car cir 10240 pir 10240 green pass yellow pass red discard [quidway-behavior-b1] quit [Quidway] traffic policy p1 [Quidway-trafficpolicy-p1] classifier c1 behavior b1 [Quidway-trafficpolicy-p1] quit [Quidway] interface gigabitethernet1/0/1 [Quidway -GigabitEthernet1/0/1] traffic-policy p1 inbound [Quidway-GigabitEthernet1/0/1] traffic-policy p1 outbound stream policies can be applied in the inbound and outbound directions of the global, interface, and VLAN view. In S9300, how do I configure traffic statistics? Suppose we need to count the Ping packets whose source IP address on port GigabitEthernet1/0/1 is 10.1.1.0/24. The configuration is as follows: [Quidway] acl number 3333 [Quidway-acl-adv-3333] rule 5 permit icmp source 10.1.1.0 0.0.255 [Quidway-acl-adv-3333] quit [Quidway] traffic classifier test [Quidway-classifier-test] if-match acl 3333 [Quidway -classifier-test] quit [Quidway] traffic behavior test [Quidway-behavior-test] statistic enable [Quidway-behavior-test] qui T [Quidway] traffic policy test [Quidway-trafficpolicy-test] classifier test behavior test [Quidway-trafficpolicy-test] quit [Quidway] interface gigabitethernet1/0/1 [Quidway-GigabitEthernet1/0/1] traffic- after policy test inbound is configured, you can run the display traffic policy statistics interface-type interface-number command to view traffic statistics. To perform traffic statistics again, run the reset traffic policy statisticsinterface interface-type interface-number command to clear the original traffic statistics. S9300 supports inbound and outbound traffic statistics, and collects packets sent from the S9300 device's CPU.