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,
Содержание N2000 Series
Страница 50: ...50 Contents ...
Страница 54: ...54 Introduction ...
Страница 134: ...134 Using Dell OpenManage Switch Administrator ...
Страница 168: ...168 Setting Basic Network Information ...
Страница 206: ...206 Managing a Switch Stack ...
Страница 242: ...242 Configuring Authentication Authorization and Accounting ...
Страница 318: ...318 Managing General System Settings Figure 12 24 Verify MOTD ...
Страница 322: ...322 Managing General System Settings ...
Страница 344: ...344 Configuring SNMP Figure 13 18 Trap Logs Click Clear to delete all entries from the trap log ...
Страница 358: ...358 Configuring SNMP ...
Страница 388: ...388 Managing Images and Files ...
Страница 415: ...Monitoring Switch Traffic 415 Figure 16 2 sFlow Agent Summary ...
Страница 451: ...Monitoring Switch Traffic 451 5 On the Capture Options dialog click Manage Interfaces ...
Страница 458: ...458 Monitoring Switch Traffic ...
Страница 488: ...488 Configuring Port Characteristics Figure 18 3 Copy Port Settings 8 Click Apply ...
Страница 502: ...502 Configuring Port Characteristics ...
Страница 541: ...Configuring Port and System Security 541 Figure 19 12 Configure Port Security Settings 5 Click Apply ...
Страница 567: ...Configuring Port and System Security 567 Figure 19 38 Captive Portal Client Status ...
Страница 666: ...666 Configuring VLANs Figure 21 6 Add Ports to VLAN 4 Click Apply 5 Verify that the ports have been added to the VLAN ...
Страница 674: ...674 Configuring VLANs Figure 21 17 GVRP Port Parameters Table ...
Страница 680: ...680 Configuring VLANs Figure 21 24 Double VLAN Port Parameter Table ...
Страница 714: ...714 Configuring VLANs ...
Страница 737: ...Configuring the Spanning Tree Protocol 737 Figure 22 9 Spanning Tree Global Settings ...
Страница 760: ...760 Configuring the Spanning Tree Protocol ...
Страница 786: ...786 Discovering Network Devices ...
Страница 793: ...Configuring Port Based Traffic Control 793 Figure 24 3 Storm Control 5 Click Apply ...
Страница 878: ...878 Configuring Connectivity Fault Management ...
Страница 899: ...Snooping and Inspecting Traffic 899 Figure 27 17 DAI Interface Configuration Summary ...
Страница 903: ...Snooping and Inspecting Traffic 903 Figure 27 24 Dynamic ARP Inspection Statistics ...
Страница 924: ...924 Configuring Link Aggregation Figure 28 7 LAG Hash Summary ...
Страница 982: ...982 Configuring Link Aggregation ...
Страница 1062: ...1062 Configuring DHCP Server and Relay Settings ...
Страница 1096: ...1096 Configuring L2 and L3 Relay Features Figure 34 3 DHCP Relay Interface Summary ...
Страница 1200: ...1200 Configuring OSPF and OSPFv3 ...
Страница 1216: ...1216 Configuring RIP ...
Страница 1240: ...1240 Configuring VRRP ...
Страница 1284: ...1284 Configuring DHCPv6 Server and Relay Settings Relay Interface Number Vl100 Relay Remote ID Option Flags ...
Страница 1291: ...Configuring Differentiated Services 1291 Figure 40 5 DiffServ Class Criteria ...
Страница 1336: ...1336 Configuring Auto VoIP ...
Страница 1367: ...Managing IPv4 and IPv6 Multicast 1367 Figure 43 20 IGMP Cache Information ...
Страница 1422: ...1422 Managing IPv4 and IPv6 Multicast ...
Страница 1440: ...1440 System Process Definitions ...
Страница 1460: ...Index 1460 ...