dedicated-buffer-profile
Syntax
dedicated-buffer-profile name {
egress {
buffer-size {
( cells | none);
}
}
ingress {
buffer-size {
( cells | none);
}
}
}Hierarchy Level
[edit class-of-service]
Description
Dedicated buffer profile configuration.
By default, the operating system calculates port level dedicated buffers internally.
Therefore, even ports that are down or unused also get an equal amount of dedicated
buffer space that is then unavailable to any traffic burst.
dedicated-buffer-profile provides the ability to increase or
decrease the default dedicated buffer at a physical interface level.
Once you define a dedicated-buffer-profile, you can attach it directly
to a physical interface. For example:
[edit class-of-service interfaces interface-name] user@host# set dedicated-buffer-profile name
Remaining dedicated buffers that you do not allocate to any ports by a
dedicated-buffer-profile are equally shared among ports (based on
speed) that don't have a dedicated-buffer-profile assigned to them.
You cannot assign a dedicated-buffer-profile to aggregated Ethernet
(ae-) interfaces. You can only assign a
dedicated-buffer-profile to a physical interface.
If the buffer-size of all dedicated buffer profiles combined exceeds
the total available dedicated buffer pool, the system logs a syslog error and does
not implement the new configuration even though the commit succeeds.
Options
| name |
Name the buffer profile. You apply a dedicated buffer profile to a physical interface by this name. |
egress buffer-size cells |
Set the egress dedicated buffer size for a port as a number of cells or
Range: 20-100,000 (Each cell is 254 bytes.) |
ingress buffer-size cells |
Set the ingress dedicated buffer size for a port as a number of cells or
Range: 20-50,000 (Each cell is 254 bytes.) |
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Evolved Release 23.2R1.