After congestion management is configured on an S series switch, why is the delay increased when the switch is fully loaded

If some services are interrupted after IPSG is configured on an S series switch (except the S1700), possible causes include the following: 1. DHCP snooping is not enabled on a DHCP terminal or the DHCP terminal does not obtain an IP address again after DHCP snooping is enabled. As a result, the dynamic binding table does not contain correct information about the terminal. IP packets sent by the terminal are discarded, and the terminal cannot communicate with the network. Solution: Enable DHCP snooping on the terminal and make the terminal obtain an IP address again to generate a dynamic binding entry in the binding table. 2. No static binding entry corresponding to a static user is generated. As a result, the user cannot go online. Solution: Create a static binding entry for each authorized user connected to the switch. Note: After the ip source check user-bind enable command is configured on an interface or in a VLAN. The interface or VLAN matches all received IP packets against a binding table and discards those not matching the binding table.

For S series switches (except the S1700), congestion avoidance prevents a network from being overloaded using a packet discarding policy. Congestion management ensures that high-priority services are preferentially processed based on the specified packet scheduling sequence. On a traditional network, quality of services (QoS) is affected by network congestion. Congestion means the low data forwarding rate and delay resulting from insufficient network resources. Congestion results in delay of packet transmission, low throughput rate, and high resource consumption. Congestion often occurs in a complex networking environment where packet transmission and provision of various services are both required. Congestion avoidance and congestion management are two flow control mechanisms for resolving congestion on a network. For the configuration of congestion management on S series fixed switches, see "Example for Configuring Congestion Management (Schedule Template Mode)" in the Typical QoS Configuration. For the comprehensive configuration example of S series fixed and modular switches, see "Example for Configuring Congestion Avoidance and Congestion Management (Using WRR Scheduling and an SRED Policy)" or "Example for Configuring Congestion Avoidance and Congestion Management (Using PQ+DRR Scheduling and a WERD Profile)" in the Typical QoS Configuration.

On S series switches (except S1700), each physical port has eight sending queues numbered from 7 to 0 in descending order of priority. Queue 7 has the highest priority and queue 0 has the lowest priority. Sending ports support the following queue scheduling modes: PQ, WRR, DRR, PQ+WRR, and PQ+DRR. When PQ+WRR or PQ+DRR is used, packets in PQ queues are scheduled first. The PQ queue with the highest priority is scheduled preferentially and then PQ queues with lower priorities are scheduled in succession. After all PQ queues are scheduled, WRR or DRR queues are then scheduled. For WRR and DRR queues, the queues are scheduled to ensure bandwidth first and then scheduled based on weights. The S5720HI fixed switch and X series cards of S series modular switches do not support WRR and PQ+WRR scheduling.

S series switch observation port specifications will not increase after stack or cluster