qos ingress-buffer-profile
qos ingress-buffer-profileuser-profile-namepriority-grouppriority-group-numberxoffshared-level no qos ingress-buffer-profileuser-profile-namepriority-grouppriority-group-numberxoffshared-levelAn ingress buffer profile is not configured.
Global configuration mode
This command is not supported on RUCKUS ICX 8200 or ICX 7650 devices.
You can attach an ingress buffer profile to a port.
You must configure the
no ingress-buffer-profile command to detach a profile from any ports that are using it before you can configure
the
no qos ingress-buffer-profile command to delete it.
The higher the sharing level, the better the port absorbs micro-bursts before reaching the XOFF threshold limit.
If PFC is enabled on a PG, and per-port with a user-defined ingress buffer profile attached to a port, the port maximum XOFF threshold level is 50 percent of service pool 1. The port maximum is used as a cap to prevent a port from using too many buffers. Under normal conditions, the PG XOFF limit is reached first.
If a PG is not enabled to send globally, any XOFF value configured has no effect.
The default ingress buffer profiles are as follows:
- For PFC disabled ports, the default PG XOFF limit is level7-1/2.
- For PFC enabled ports, the default PG XOFF limit is level2-1/32.
The following six PG XOFF limits are supported:
Supported PG XOFF Limits
The
no form of the command deletes the ingress buffer profile.
| Release version | Command history |
|---|---|
| 08.0.20 | This command was introduced. |