Configuring Data Center Bridging Features
995
the willing parameter is disabled on auto-downstream. By default, auto-
downstream ports have the recommendation TLV parameter enabled. Auto-
downstream ports that receive internally propagated information ignore their
local configuration and utilize the internally propagated information. Auto-
downstream ports propagate PFC, ETS, and application priority information
received from the configuration source.
In the Configuration Source role, the port has been manually selected to be
the configuration source. Configuration received over this port is propagated
to the other auto configuration ports, however, no automatic election of a
new configuration source port is allowed. Events that cause selection of a new
configuration source are ignored. The configuration received over the
configuration source port is maintained until cleared by the operator (set the
port to the manual role).
Since it is not possible to configure the port role for a port-channel, it is
recommended that the individual links have an identical port role configured
on all links in the port-channel (auto-up or auto-down). Since only one port
in the system can be configured as the configuration source, configuring
interfaces as auto-up is a preferable alternative to a config-source setting.
Configuration Source Port Selection Process
When an auto-upstream or auto-downstream port receives a configuration
from a peer, the DCBx client first checks if there is an active configuration
source. If there is a configuration source already selected, the received
configuration is checked against the local port operational values as received
from the configuration source, and if compatible, the client marks the port as
operationally enabled. If the configuration received from the peer is
determined to not be compatible, a message is logged, an error counter is
incremented and the DCBx clients become operationally disabled on the
port. Operationally disabled means that PFC will not operate over the port.
The port continues to keep link up and exchanges DCBx packets. If a
compatible configuration is later received, the DCBx clients will become
operationally enabled.
If there is no configuration source, a port may elect itself as the configuration
source on a first-come, first-serve basis from the set of eligible ports. A port is
eligible to become the configuration source if the following conditions are
true:
• No other port is the configuration source.
Summary of Contents for N2000 Series
Page 50: ...50 Contents ...
Page 54: ...54 Introduction ...
Page 134: ...134 Using Dell OpenManage Switch Administrator ...
Page 168: ...168 Setting Basic Network Information ...
Page 206: ...206 Managing a Switch Stack ...
Page 242: ...242 Configuring Authentication Authorization and Accounting ...
Page 318: ...318 Managing General System Settings Figure 12 24 Verify MOTD ...
Page 322: ...322 Managing General System Settings ...
Page 358: ...358 Configuring SNMP ...
Page 388: ...388 Managing Images and Files ...
Page 415: ...Monitoring Switch Traffic 415 Figure 16 2 sFlow Agent Summary ...
Page 451: ...Monitoring Switch Traffic 451 5 On the Capture Options dialog click Manage Interfaces ...
Page 458: ...458 Monitoring Switch Traffic ...
Page 488: ...488 Configuring Port Characteristics Figure 18 3 Copy Port Settings 8 Click Apply ...
Page 502: ...502 Configuring Port Characteristics ...
Page 567: ...Configuring Port and System Security 567 Figure 19 38 Captive Portal Client Status ...
Page 674: ...674 Configuring VLANs Figure 21 17 GVRP Port Parameters Table ...
Page 680: ...680 Configuring VLANs Figure 21 24 Double VLAN Port Parameter Table ...
Page 714: ...714 Configuring VLANs ...
Page 737: ...Configuring the Spanning Tree Protocol 737 Figure 22 9 Spanning Tree Global Settings ...
Page 760: ...760 Configuring the Spanning Tree Protocol ...
Page 786: ...786 Discovering Network Devices ...
Page 793: ...Configuring Port Based Traffic Control 793 Figure 24 3 Storm Control 5 Click Apply ...
Page 878: ...878 Configuring Connectivity Fault Management ...
Page 899: ...Snooping and Inspecting Traffic 899 Figure 27 17 DAI Interface Configuration Summary ...
Page 903: ...Snooping and Inspecting Traffic 903 Figure 27 24 Dynamic ARP Inspection Statistics ...
Page 924: ...924 Configuring Link Aggregation Figure 28 7 LAG Hash Summary ...
Page 982: ...982 Configuring Link Aggregation ...
Page 1062: ...1062 Configuring DHCP Server and Relay Settings ...
Page 1096: ...1096 Configuring L2 and L3 Relay Features Figure 34 3 DHCP Relay Interface Summary ...
Page 1200: ...1200 Configuring OSPF and OSPFv3 ...
Page 1216: ...1216 Configuring RIP ...
Page 1240: ...1240 Configuring VRRP ...
Page 1291: ...Configuring Differentiated Services 1291 Figure 40 5 DiffServ Class Criteria ...
Page 1336: ...1336 Configuring Auto VoIP ...
Page 1367: ...Managing IPv4 and IPv6 Multicast 1367 Figure 43 20 IGMP Cache Information ...
Page 1422: ...1422 Managing IPv4 and IPv6 Multicast ...
Page 1440: ...1440 System Process Definitions ...
Page 1460: ...Index 1460 ...