994
Configuring Data Center Bridging Features
explicitly by the operator. These ports advertise their configuration to their
peer if DCBx is enabled on that port. Incompatible peer configurations are
logged and counted with an error counter.
The default operating mode for each port is manual. A port that is set to
manual mode sets the willing bit for DCBx client TLVs to false. Manually-
configured ports never internally propagate or accept internal or external
configuration from other ports; in other words, a manual configuration
discards any automatic configuration. Manually-configured ports may notify
the operator of incompatible configurations if client configuration exchange
over DCBx is enabled. Manually configured ports are always operationally
enabled for DCBx clients, regardless of whether DCBx is enabled.
Operationally enabled means that the port reports that it is able to operate
using the current configuration.
A port operating in the auto-upstream role advertises a configuration, but is
also willing to accept a configuration from the link-partner and propagate it
internally to the auto-downstream ports, as well as receive configuration
propagated internally by other auto-upstream ports. Specifically, the willing
parameter is enabled on the port and the recommendation TLV is sent to the
peer and processed if received locally. The first auto-upstream port to
successfully accept a compatible configuration becomes the configuration
source. The configuration source propagates its configuration to other auto-
upstream and auto-downstream ports. Only the configuration source may
propagate configuration to other ports internally. Auto-upstream ports that
receive internally propagated information ignore their local configuration and
utilize the internally propagated information.
Peer configurations received on auto-upstream ports other than the
configuration source result in one of two possibilities. If the configuration is
compatible with the configuration source, then the DCBx client becomes
operationally active on the upstream port. If the configuration is not
compatible with the configuration source, then a message is logged indicating
an incompatible configuration, an error counter is incremented, and the
DCBx client is operationally disabled on the port. The expectation is that the
network administrator configures the upstream devices appropriately so that
all such devices advertise a compatible configuration.
A port operating in the auto-downstream role advertises a configuration but is
not willing to accept one from the link partner. However, the port will accept a
configuration propagated internally by the configuration source. Specifically,
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 ...