986 Configuring Data Center Bridging FeaturesOperator configuration of PFC is used only when the port is configured in amanual role. When interoperating with other equipment in a manual role,the peer equipment must be configured with identical PFC priorities andVLAN assignments. Interfaces not enabled for PFC ignore received PFCframes. Ports configured in auto-upstream or auto-downstream roles receivetheir PFC configuration from the configuration source and ignore anymanually configured information.When using links in a port-channel, PFC must be configured on all of theindividual links in the port-channel, as it operates on a link-local basis.When PFC is disabled, the interface defaults to the IEEE 802.3 Annex 31Bflow control setting for the interface. PFC is disabled by default.If you enable priority-based flow control for a particular priority value on aninterface, ensure that VLAN tagging is enabled on the interface so that the802.1p priority values are carried through the network (see "VLAN Tagging"on page 649). Additionally, make sure that 802.1p priority values are mappedto CoS values (see "Configuring Class-of-Service" on page 1313). If DCBX isenabled, the manually configured PFC parameters (no-drop priorities) mustmatch the peers PFC parameters. If they do not match, PFC will not beoperationally enabled and the port will continue to operate in the configuredlegacy flow control mode (IEEE 802.3 Annex 31B mode or none).PFC can be configured using the web interface and the command lineinterface.Configuring PFC Using the Web InterfaceThis section provides information about the OpenManage SwitchAdministrator pages to use to view and configure PFC on N4000 seriesswitches. For details about the fields on a page, click at the top of thepage.NOTE: This feature is configurable on physical full duplex interfaces only. Toenable PFC on a LAG interface, the member interfaces must have the sameconfiguration.
