congestion-notification-profile
Syntax
congestion-notification-profile profile-name {
input {
(dscp | ieee-802.1) {
code-point [code-point-bits] {
pfc {
mru mru-value;
}
xon value;
}
}
cable-length cable-length-value;
}
output {
ieee-802.1 {
code-point [code-point-bits] {
flow-control-queue [queue | list-of-queues];
}
}
}
pfc-watchdog {
detection number of polling intervals;
poll-interval time;
recovery time;
watchdog-action {
drop;
}
}
}
EX4550 Switches
congestion-notification-profile profile-name {
input {
ieee-802.1 {
code-point up-bits pfc;
Hierarchy Level
[edit class-of-service], [edit class-of-service interfaces interface-name]
Description
Configure a congestion notification profile (CNP) to enable priority-based flow control (PFC) on traffic and apply the profile to an interface. You can apply a CNP to most interfaces, including aggregated ethernet (AE) interfaces and their individual members.
A congestion notification profile can be configured to enable
PFC on incoming traffic (input stanza) that matches the
following:
A Differentiated Services code point (DSCP) value in the Layer 3 IP header (for traffic that is not VLAN-tagged).
An IEEE 802.1 code point at Layer 2 in the VLAN header (for VLAN-tagged traffic).
A congestion notification profile can be configured to enable
PFC on outgoing traffic (output stanza) specified only
by an IEEE 802.1 code point at Layer 2 in the VLAN header.
You must configure PFC for FCoE traffic. Each interface
that carries FCoE traffic should be configured for PFC on the FCoE
code point (usually 011).
There is no limit to the total number of congestion notification profiles you can create. However:
You can attach a maximum of one congestion notification profile to an interface.
DSCP-based PFC and IEEE 802.1p PFC cannot be configured under the same congestion notification profile.
Configuring or changing PFC on an interface blocks the entire port until the PFC change is completed. After a PFC change is completed, the port is unblocked and traffic resumes. Blocking the port stops ingress and egress traffic, and causes packet loss on all queues on the port until the port is unblocked.
Options
| profile-name | Name of the congestion notification profile. |
| pfc-watchdog | Enable the Priority Flow Control (PFC) watchdog. If you do not configure any options, the default values are used.
|
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details.
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 Release 10.4.
Support for DSCP values introduced in Junos OS Release 17.4R1 for the QFX Series.
pfc-watchdog option introduced in Junos OS Evolved Release 20.4R1.