
DCBx Port Roles
To enable the auto-configuration of DCBx-enabled ports and propagate DCB configurations learned from peer DCBx devices
internally to other switch ports, use the following DCBx port roles.
Auto-upstream
The port advertises its own configuration to DCBx peers and is
willing
to receive peer configuration. The
port also propagates its configuration to other ports on the switch.
The first auto-upstream that is capable of receiving a peer configuration is elected as the configuration
source. The elected configuration source then internally 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.
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
260
Data Center Bridging (DCB)
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...