Users Guide

Configure Deep Buffer mode
You must disable all the network QoS configurations; for example, PFC and LLFC, before configuring the Deep Buffer mode. Deep Buffer
mode is disabled by default.
1. Enable Deep Buffer mode in CONFIGURATION mode.
OS10# configure terminal
OS10(config)# hardware deep-buffer-mode
NOTE: To disable Deep Buffer mode, use the no form of the command. Disabling Deep Buffer mode takes effect only
after saving it in the startup configuration and reloading the switch.
After you configure Deep Buffer mode, the system displays a warning stating that the configuration takes effect only after saving it in
the startup configuration and reloading the switch.
% Warning: Deep buffer mode configuration will be applied only after a save and reload.
2. Save Deep Buffer mode in the startup configuration in CONFIGURATION mode.
OS10(config)# do write memory
3. Reload the switch in CONFIGURATION mode.
OS10(config)# do reload
Proceed to reboot the system? [confirm yes/no]:yes
To view Deep Buffer mode status, use the show hardware deep-buffer-mode command. The show command output displays the
status of Deep Buffer mode in the current boot and the next boot.
The following is Deep Buffer mode status before enabling it, the default setting:
OS10# show hardware deep-buffer-mode
Deep Buffer Mode Configuration Status
-------------------------------------------
Current-boot Settings : Disabled
Next-boot Settings : Disabled
The following is Deep Buffer mode status after saving the configuration in the startup configuration:
OS10# show hardware deep-buffer-mode
Deep Buffer Mode Configuration Status
-------------------------------------------
Current-boot Settings : Disabled
Next-boot Settings : Enabled
The following is Deep Buffer mode status after the switch reloads:
OS10# show hardware deep-buffer-mode
Deep Buffer Mode Configuration Status
-------------------------------------------
Current-boot Settings : Enabled
Next-boot Settings : Enabled
Congestion avoidance
Congestion avoidance anticipates and takes necessary actions to avoid congestion. The following mechanisms avoid congestion:
• Tail drop—Packets are buffered at traffic queues. When the buffers are exhausted or reach the configured threshold, excess
packets drop. By default, OS10 uses tail drop for congestion avoidance.
• Random early detection (RED)—In tail drop, different flows are not considered in buffer utilization. When multiple hosts start
retransmission, tail drop causes TCP global re-synchronization. Instead of waiting for the queue to get filled up completely, RED starts
1110
Quality of service