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.
Configuration
source
The port is configured to serve as a source of configuration information on the switch.
Peer DCB configurations received on the port are propagated to other DCBx auto-
configured ports. If the peer configuration is compatible with a port configuration,
DCBx is enabled on the port.
On a configuration-source port, the link with a DCBx peer is enabled when the port
receives a DCB configuration that can be internally propagated to other auto-
configured ports. The configuration received from a DCBx peer is not stored in the
switch’s running configuration. On a DCBx port that is the configuration source, all PFC
and application priority TLVs are enabled. ETS recommend TLVs are disabled and ETS
configuration TLVs are enabled.
Manual
The port is configured to operate only with administrator-configured settings and does
not auto-configure with DCB settings received from a DCBx peer or from an internally
propagated configuration from the configuration source. If you enable DCBx, ports in
Manual mode advertise their configurations to peer devices but do not accept or
Data Center Bridging (DCB)
319
Summary of Contents for S4048T
Page 1: ...Dell Configuration Guide for the S4048T ON System 9 10 0 1 ...
Page 98: ... saveenv 7 Reload the system uBoot mode reset Management 98 ...
Page 113: ...Total CFM Pkts 10303 CCM Pkts 0 LBM Pkts 0 LTM Pkts 3 LBR Pkts 0 LTR Pkts 0 802 1ag 113 ...
Page 411: ...mode transit no disable Force10 Resilient Ring Protocol FRRP 411 ...
Page 590: ...Figure 67 Inspecting the LAG Configuration Link Aggregation Control Protocol LACP 590 ...
Page 646: ...Figure 87 Configuring Interfaces for MSDP Multicast Source Discovery Protocol MSDP 646 ...
Page 647: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 647 ...
Page 653: ...Figure 91 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 653 ...
Page 654: ...Figure 92 MSDP Default Peer Scenario 3 Multicast Source Discovery Protocol MSDP 654 ...
Page 955: ...Figure 119 Single and Double Tag First byte TPID Match Service Provider Bridging 955 ...