Users Guide
propagates the configuration to other auto-upstream and auto-downstream ports.
A port that receives an internally propagated configuration overwrites its local
configuration with the new parameter values.
When an auto-upstream port (besides the configuration source) receives and
overwrites its configuration with internally propagated information, one of the
following actions is taken:
• If the peer configuration received is compatible with the internally propagated
port configuration, the link with the DCBx peer is enabled.
• If the received peer configuration is not compatible with the currently
configured port configuration, the link with the DCBx peer port is disabled and
a syslog message for an incompatible configuration is generated. The network
administrator must then reconfigure the peer device so that it advertises a
compatible DCB configuration.
The configuration received from a DCBx peer or from an internally propagated
configuration is not stored in the switch’s running configuration.
On a DCBx port in an auto-upstream role, the PFC and application priority TLVs are
enabled. ETS recommend TLVs are disabled and ETS configuration TLVs are
enabled.
Auto-
downstream
The port advertises its own configuration to DCBx peers but is not willing to
receive remote peer configuration. The port always accepts internally propagated
configurations from a configuration source. An auto-downstream port that
receives an internally propagated configuration overwrites its local configuration
with the new parameter values.
When an auto-downstream port receives and overwrites its configuration with
internally propagated information, one of the following actions is taken:
• If the peer configuration received is compatible with the internally propagated
port configuration, the link with the DCBx peer is enabled.
• If the received peer configuration is not compatible with the currently
configured port configuration, the link with the DCBx peer port is disabled and
a syslog message for an incompatible configuration is generated. The network
administrator must then reconfigure the peer device so that it advertises a
compatible DCB configuration.
The internally propagated configuration is not stored in the switch’s running
configuration. On a DCBx port in an auto-downstream role, all PFC, application
priority, ETS recommend, and ETS configuration TLVs are enabled.
Default DCBx port role: Uplink ports are auto-configured in an auto-upstream role. Server-facing ports
are auto-configured in an auto-downstream role.
NOTE: You can change the port roles only in the PMUX mode. Use the following command to
change the port roles:
dcbx port-role {auto-downstream | auto-upstream | config-source | manual}
manual is the default port role.
Data Center Bridging (DCB)
49