How it Works
Dell
Loading...
53-1002116-01
User Manual
168 pgs1.03 Mb0
Table of contents
Loading...

Dell 53-1002116-01 User Manual

53-1002116-01 07 December 2010
Dell Converged Enhanced Ethernet
Administrator’s Guide
Information in this document is subject to change without notice. © 2010 Dell Inc. All rights reserved.
Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own.
Regulatory Model Code: M8428-k

Contents

About This Document
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Document conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Command syntax conventions . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Notes, cautions, and warnings . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Getting technical help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Contacting Dell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Chapter 1 Introducing FCoE
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
FCoE terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
FCoE overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
FCoE hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Layer 2 Ethernet overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Layer 2 forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
VLAN tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Loop-free network environment . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Frame classification (incoming) . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Congestion control and queuing. . . . . . . . . . . . . . . . . . . . . . . . . . 6
Access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Access Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
FCoE Initialization Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
FIP discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
FIP login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
FIP logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
FCoE login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
FCoE logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Logincfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Name server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
FC zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Registered State Change Notification (RSCN) . . . . . . . . . . . . . .12
FCoE queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Dell Converged Enhanced Ethernet Administrator’s Guide iii 53-1002116-01
Chapter 2 Using the CEE CLI
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Management Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
CEE Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Saving your configuration changes. . . . . . . . . . . . . . . . . . . . . . . 14
CEE CLI RBAC permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Accessing the CEE CLI through the console or Telnet . . . . . . . 15
Accessing the CEE CLI from the Fabric OS shell . . . . . . . . . . . .15
CEE CLI command modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
CEE CLI keyboard shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Using the do command as a shortcut . . . . . . . . . . . . . . . . . . . .18
Displaying CEE CLI commands and command syntax . . . . . . . 18
CEE CLI command completion . . . . . . . . . . . . . . . . . . . . . . . . . .19
CEE CLI command output modifiers. . . . . . . . . . . . . . . . . . . . . .19
Internal and external 10 Gbps Ethernet interfaces syntax . . . . . . .20
Chapter 3 Initial FCoE and CEE Configuration
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Configuring the FCoE interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Configuring FCoE VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Assigning FCoE map on to an interface . . . . . . . . . . . . . . . . . . . 23
Configuring the CEE interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Configuring DCBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Configuring Spanning Tree Protocol. . . . . . . . . . . . . . . . . . . . . . . . . .25
Configuring VLAN membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Configuring protect mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Chapter 4 Configuring IP static routes
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
IP static routes overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Configuring IP static routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Recursive IP static routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Floating IP static routes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Displaying and clearing IP static routes . . . . . . . . . . . . . . . . . . .29
Chapter 5 Configuring VLANs Using the CEE CLI
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
VLAN overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Ingress VLAN filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
VLAN configuration guidelines and restrictions . . . . . . . . . . . . . . . .33
Default VLAN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
iv Dell Converged Enhanced Ethernet Administrator’s Guide
53-1002116-01
VLAN configuration and management. . . . . . . . . . . . . . . . . . . . . . . . 34
Enabling and disabling an interface port . . . . . . . . . . . . . . . . . .34
Configuring the MTU on an interface port . . . . . . . . . . . . . . . . .34
Creating a VLAN interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Enabling STP on a VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Disabling STP on a VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Configuring a VLAN interface to forward FCoE traffic . . . . . . . .36
Configuring an interface port as a Layer 2 switch port . . . . . . .36
Configuring an interface port as an access interface . . . . . . . .36
Configuring an interface port as a trunk interface . . . . . . . . . .37
Disabling a VLAN on a trunk interface . . . . . . . . . . . . . . . . . . . . 37
Configuring an interface port as a converged interface . . . . . . 37
Disabling a VLAN on a converged interface . . . . . . . . . . . . . . . .38
Configuring protocol-based VLAN classifier rules . . . . . . . . . . . . . . .38
Configuring a VLAN classifier rule. . . . . . . . . . . . . . . . . . . . . . . .39
Configuring MAC address-based VLAN classifier rules . . . . . . .39
Deleting a VLAN classifier rule . . . . . . . . . . . . . . . . . . . . . . . . . .39
Creating a VLAN classifier group and adding rules . . . . . . . . . .39
Activating a VLAN classifier group with an interface port . . . . .40
Clearing VLAN counter statistics. . . . . . . . . . . . . . . . . . . . . . . . .40
Displaying VLAN information. . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Configuring the MAC address table . . . . . . . . . . . . . . . . . . . . . . . . . .40
Specifying or disabling the aging time for MAC addresses. . . . 41
Adding static addresses to the MAC address table. . . . . . . . . . 41
Chapter 6 Configuring STP, RSTP, and MSTP using the CEE CLI
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
STP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Configuring STP on Dell FCoE hardware. . . . . . . . . . . . . . . . . . .44
RSTP overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
MSTP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Configuring MSTP on Dell FCoE hardware . . . . . . . . . . . . . . . . .48
STP, RSTP, and MSTP configuration guidelines and restrictions . . .49
Default STP, RSTP, and MSTP configuration . . . . . . . . . . . . . . . . . . .50
Dell Converged Enhanced Ethernet Administrator’s Guide v 53-1002116-01
STP, RSTP, and MSTP configuration and management . . . . . . . . . . 51
Enabling STP, RSTP, or MSTP . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Disabling STP, RSTP, or MSTP . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Shutting down STP, RSTP, or MSTP globally . . . . . . . . . . . . . . . . 51
Specifying the bridge priority. . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Specifying the bridge forward delay . . . . . . . . . . . . . . . . . . . . . .52
Specifying the bridge maximum aging time. . . . . . . . . . . . . . . .53
Enabling the error disable timeout timer . . . . . . . . . . . . . . . . . .53
Specifying the error disable timeout interval. . . . . . . . . . . . . . .53
Specifying the port-channel path cost . . . . . . . . . . . . . . . . . . . .54
Specifying the bridge hello time (STP and RSTP). . . . . . . . . . . .54
Specifying the transmit hold count (RSTP and MSTP). . . . . . . .54
Enabling Cisco interoperability (MSTP). . . . . . . . . . . . . . . . . . . .55
Disabling Cisco interoperability (MSTP) . . . . . . . . . . . . . . . . . . . 55
Mapping a VLAN to an MSTP instance . . . . . . . . . . . . . . . . . . . .55
Specifying the maximum number of hops
for a BPDU (MSTP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Specifying a name for an MSTP region. . . . . . . . . . . . . . . . . . . .56
Specifying a revision number for an MSTP configuration . . . . .56
Flushing MAC addresses (RSTP and MSTP). . . . . . . . . . . . . . . . 57
Clearing spanning tree counters. . . . . . . . . . . . . . . . . . . . . . . . . 57
Clearing spanning tree-detected protocols . . . . . . . . . . . . . . . .57
Displaying STP, RSTP, and MSTP-related information . . . . . . . . 58
Configuring STP, RSTP, or MSTP on CEE interface ports . . . . . . . . .58
Enabling automatic edge detection . . . . . . . . . . . . . . . . . . . . . .58
Configuring the path cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
Enabling a port (interface) as an edge port . . . . . . . . . . . . . . . .59
Enabling the guard root. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Specifying the MSTP hello time. . . . . . . . . . . . . . . . . . . . . . . . . .60
Specifying restrictions for an MSTP instance . . . . . . . . . . . . . .60
Specifying a link type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Enabling port fast (STP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Specifying the port priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Restricting the port from becoming a root port . . . . . . . . . . . . .62
Restricting the topology change notification . . . . . . . . . . . . . . . 62
Enabling spanning tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
Disabling spanning tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Chapter 7 Configuring Link Aggregation using the CEE CLI
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Link aggregation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Link Aggregation Group configuration . . . . . . . . . . . . . . . . . . . .65
Link Aggregation Control Protocol. . . . . . . . . . . . . . . . . . . . . . . .68
Dynamic link aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Static link aggregation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Dell-proprietary aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
LAG distribution process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
LACP configuration guidelines and restrictions . . . . . . . . . . . . . . . .69
Default LACP configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
vi Dell Converged Enhanced Ethernet Administrator’s Guide
53-1002116-01
LACP configuration and management. . . . . . . . . . . . . . . . . . . . . . . .69
Enabling LACP on a CEE interface . . . . . . . . . . . . . . . . . . . . . . .69
Configuring the LACP system priority . . . . . . . . . . . . . . . . . . . . .70
Configuring the LACP timeout period on a CEE interface . . . . . 70
Configuring minimum links feature . . . . . . . . . . . . . . . . . . . . . .70
Configuring interface tracking. . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Clearing LACP counter statistics on a LAG . . . . . . . . . . . . . . . . . 71
Clearing LACP counter statistics on all LAG groups . . . . . . . . . . 72
Displaying LACP information . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
LACP troubleshooting tips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Chapter 8 Configuring LLDP using the CEE CLI
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
LLDP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
Layer 2 topology mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
DCBX overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Enhanced Transmission Selection (ETS) . . . . . . . . . . . . . . . . . .78
Priority Flow Control (PFC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
DCBX interaction with other vendor devices . . . . . . . . . . . . . . . . . . . 79
LLDP configuration guidelines and restrictions . . . . . . . . . . . . . . . .79
Default LLDP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
LLDP configuration and management. . . . . . . . . . . . . . . . . . . . . . . .80
Enabling LLDP globally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Disabling and resetting LLDP globally . . . . . . . . . . . . . . . . . . . .80
Configuring LLDP global command options. . . . . . . . . . . . . . . . 81
Configuring LLDP interface-level command options . . . . . . . . .84
Clearing LLDP-related information . . . . . . . . . . . . . . . . . . . . . . .85
Displaying LLDP-related information . . . . . . . . . . . . . . . . . . . . .85
Chapter 9 Configuring ACLs using the CEE CLI
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
ACL overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Default ACL configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
ACL configuration guidelines and restrictions. . . . . . . . . . . . . . . . . .88
ACL configuration and management . . . . . . . . . . . . . . . . . . . . . . . . . 88
Creating a standard MAC ACL and adding rules . . . . . . . . . . . .88
Creating an extended MAC ACL and adding rules . . . . . . . . . . . 89
Modifying MAC ACL rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
Removing a MAC ACL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Reordering the sequence numbers in a MAC ACL. . . . . . . . . . . 90
Applying a MAC ACL to a CEE interface . . . . . . . . . . . . . . . . . . .91
Applying a MAC ACL to a VLAN interface . . . . . . . . . . . . . . . . . . 91
Dell Converged Enhanced Ethernet Administrator’s Guide vii 53-1002116-01
Chapter 10 Configuring QoS using the CEE CLI
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
QoS overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Rewriting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Queueing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
User-priority mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
Traffic class mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Congestion control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100
Tail drop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100
Ethernet pause. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
Ethernet Priority Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . .102
Multicast rate limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
Strict priority scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
Deficit weighted round robin scheduling . . . . . . . . . . . . . . . . .104
Traffic class scheduling policy. . . . . . . . . . . . . . . . . . . . . . . . . .105
Multicast queue scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . .106
Converged Enhanced Ethernet map configuration. . . . . . . . . . . . .107
Chapter 11 Configuring 802.1x Port Authentication
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
802.1x protocol overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
802.1x configuration guidelines and restrictions. . . . . . . . . . . . . .111
802.1x authentication configuration tasks. . . . . . . . . . . . . . . . . . .112
Configure authentication
between the switch and CNA or NIC. . . . . . . . . . . . . . . . . . . . .112
Interface-specific administrative tasks for 802.1x . . . . . . . . . . . . .112
Configuring 802.1x on specific interface ports . . . . . . . . . . . .113
Configuring 802.1x timeouts
on specific interface ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
Configuring 802.1x re-authentication
on specific interface ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
Disabling 802.1x on specific interface ports . . . . . . . . . . . . . .114
Chapter 12 Configuring sFlow using the CEE CLI
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
sFlow protocol overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
Interface flow samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
Packet counter samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
Configuring the sFlow protocol globally . . . . . . . . . . . . . . . . . . . . . .116
Interface-specific administrative tasks for sFlow . . . . . . . . . . . . . .116
Disabling sFlow on specific interfaces . . . . . . . . . . . . . . . . . . .116
Configuring sFlow on specific interfaces . . . . . . . . . . . . . . . . . 117
viii Dell Converged Enhanced Ethernet Administrator’s Guide
53-1002116-01
Chapter 13 Configuring Port Mirroring using the CEE CLI
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
Port Mirroring protocol overview . . . . . . . . . . . . . . . . . . . . . . . . . . .119
Port Mirroring limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
Configuring ingress Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . .120
Configuring egress Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . .120
Configuring bidirectional Port Mirroring . . . . . . . . . . . . . . . . . . . . .120
Deleting a Port Mirroring connection from a session . . . . . . . . . . .121
Deleting a Port Mirroring session. . . . . . . . . . . . . . . . . . . . . . . . . . .121
Chapter 14 Configuring RMON using the CEE CLI
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
RMON overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
RMON configuration and management. . . . . . . . . . . . . . . . . . . . . .123
Default RMON configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .123
Configuring RMON settings . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
Configuring RMON events . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
Configuring RMON group statistics collection . . . . . . . . . . . . .124
Configuring RMON history collection . . . . . . . . . . . . . . . . . . . .125
Chapter 15 Configuring IGMP
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
About IGMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
Active IGMP snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
Multicast routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
Configuring IGMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
Configuring IGMP snooping querier. . . . . . . . . . . . . . . . . . . . . . . . .128
Monitoring IGMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129
Chapter 16 FCoE configuration using the Fabric OS CLI
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131
FCoE configuration guidelines and restrictions . . . . . . . . . . . . . . .131
Managing and displaying the FCoE configuration. . . . . . . . . . . . . .132
Enabling or disabling an FCoE port . . . . . . . . . . . . . . . . . . . . .132
Configuring FCMAP values for a VLAN . . . . . . . . . . . . . . . . . . .132
Configuring FIP multicast advertisement intervals . . . . . . . . .132
Clearing logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133
Displaying FCoE configuration-related information . . . . . . . . .133
Dell Converged Enhanced Ethernet Administrator’s Guide ix 53-1002116-01
Managing and displaying the FCoE login configuration . . . . . . . . .133
Enabling or disabling FCoE login
configuration management. . . . . . . . . . . . . . . . . . . . . . . . . . . .133
Displaying or aborting the current
configuration transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134
Cleaning up login groups and VN_port mappings . . . . . . . . . .134
Displaying the FCoE login configuration. . . . . . . . . . . . . . . . . .135
Saving the current FCoE configuration. . . . . . . . . . . . . . . . . . .135
Creating and managing the FCoE login group configuration . . . . .135
Creating an FCoE login group . . . . . . . . . . . . . . . . . . . . . . . . . .135
Modifying the FCoE login group device list. . . . . . . . . . . . . . . .136
Deleting an FCoE login group . . . . . . . . . . . . . . . . . . . . . . . . . .136
Renaming an FCoE login group. . . . . . . . . . . . . . . . . . . . . . . . .137
Chapter 17 CEE configuration management
In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
CEE configuration management guidelines and restrictions. . . . .139
CEE configuration management tasks . . . . . . . . . . . . . . . . . . . . . .139
Display the running configuration file. . . . . . . . . . . . . . . . . . . .140
Saving the running configuration file . . . . . . . . . . . . . . . . . . . .140
Loading the startup configuration file . . . . . . . . . . . . . . . . . . .140
Erasing the startup configuration file. . . . . . . . . . . . . . . . . . . .140
Archiving the running configuration file . . . . . . . . . . . . . . . . . .141
Restore an archived running configuration file . . . . . . . . . . . . 141
Archiving the startup configuration file . . . . . . . . . . . . . . . . . .141
Restore an archived startup configuration file . . . . . . . . . . . .141
Archive a startup configuration from Flash . . . . . . . . . . . . . . . 141
Restore a startup configuration file from Flash. . . . . . . . . . . .142
CEE configuration management commands . . . . . . . . . . . . . .142
Flash file management commands . . . . . . . . . . . . . . . . . . . . . . . . .142
Debugging and logging commands . . . . . . . . . . . . . . . . . . . . . . . . .143
Index
x Dell Converged Enhanced Ethernet Administrator’s Guide
53-1002116-01

Figures

Figure 1 Multiple switch fabric configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Figure 2 CEE CLI command mode hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Figure 3 Ingress VLAN filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 4 Configuring LAGs for a top-of-the-rack CEE switch—Example 1 . . . . . . . . . . . . . 67
Figure 5 Configuring LAGs for a top-of-the-rack CEE switch—Example 2 . . . . . . . . . . . . . 67
Figure 6 Queue depth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Figure 7 Strict priority schedule — two queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 8 WRR schedule — two queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 9 Strict priority and Weighted Round Robin scheduler . . . . . . . . . . . . . . . . . . . . 106
Dell Converged Enhanced Ethernet Administrator’s Guide xi 53-1002116-01
xii Dell Converged Enhanced Ethernet Administrator’s Guide
53-1002116-01

Tables

Tab le 1 FCoE terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Tab le 2 CEE RBAC permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Tab le 3 CEE CLI command modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Tab le 4 CEE CLI keyboard shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Tab le 5 CEE CLI command output modifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Tab le 6 IP static route features and capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Tab le 7 Default VLAN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Tab le 8 STP versus RSTP state comparison. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Tab le 9 Default STP, RSTP, and MSTP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Tab le 10 Default MSTP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Tab le 11 Default 10-Gigabit Ethernet CEE interface-specific configuration . . . . . . . . . . . 50
Tab le 1 2 Default LACP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Tab le 13 ETS priority grouping of IPC, LAN, and SAN traffic . . . . . . . . . . . . . . . . . . . . . . . . 78
Tab le 14 Default LLDP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Tab le 15 Default MAC ACL configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Tab le 16 Default priority value of untrusted interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Table 17 IEEE 802.1Q default priority mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Tab le 18 Default user priority for unicast traffic class mapping. . . . . . . . . . . . . . . . . . . . . 97
Tab le 19 Default user priority for multicast traffic class mapping . . . . . . . . . . . . . . . . . . . 98
Tab le 2 0 Supported scheduling configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Tab le 21 Multicast traffic class equivalence mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Tab le 2 2 Default CEE Priority Group Table configuration . . . . . . . . . . . . . . . . . . . . . . . . . 108
Tab le 2 3 Default CEE priority table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Tab le 24 CEE configuration management commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Tab le 2 5 CEE Flash memory file management commands. . . . . . . . . . . . . . . . . . . . . . . . 143
Tab le 2 6 Debugging and logging commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Dell Converged Enhanced Ethernet Administrator’s Guide xiii 53-1002116-01
xiv Dell Converged Enhanced Ethernet Administrator’s Guide
53-1002116-01

About This Document

In this chapter

•How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
•Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
•Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
•Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
•Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

How this document is organized

This document is organized to help you find the information that you want as quickly and easily as possible.
The document contains the following components:
• Chapter 1, “Introducing FCoE,” provides an overview of Fibre Channel over Ethernet (FCoE) on
the Dell FCoE hardware.
• Chapter 2, “Using the CEE CLI,” describes the Converged Enhanced Ethernet (CEE) CLI.
• Chapter 3, “Initial FCoE and CEE Configuration,” describes some basic switch configurations
for command SAN and LAN environments.
• Chapter 4, “Configuring IP static routes,” describes how to configure IP static routes.
• Chapter 5, “Configuring VLANs Using the CEE CLI,” describes how to configure VLANs.
• Chapter 6, “Configuring STP, RSTP, and MSTP using the CEE CLI,” describes how to configure
the Spanning Tree Protocol (STP), Rapid STP (RSTP), and Multiple STP (MSTP).
• Chapter 7, “Configuring Link Aggregation using the CEE CLI,” describes how to configure Link
Aggregation and Link Aggregation Control Protocol (LACP).
• Chapter 8, “Configuring LLDP using the CEE CLI,” describes how to configure the Link Layer
Discovery Protocol (LLDP) and the Data Center Bridging (DCB) Capability Exchange Protocol (DCBX).
• Chapter 9, “Configuring ACLs using the CEE CLI,” describes how to configure Access Control
Lists (ACLs).
• Chapter 10, “Configuring QoS using the CEE CLI,” describes how to configure Quality of Service
(QoS).
• Chapter 11, “Configuring 802.1x Port Authentication,”describes how to configure the 802.1x
Port Authentication protocol.
• Chapter 12, “Configuring sFlow using the CEE CLI,”describes how to configure sFlow.
Dell Converged Enhanced Ethernet Administrator’s Guide xv 53-1002116-01
• Chapter 13, “Configuring Port Mirroring using the CEE CLI,”describes how to configure Port
Mirroring.
• Chapter 14, “Configuring RMON using the CEE CLI,” describes how to configure remote
monitoring (RMON).
• Chapter 15, “Configuring IGMP,” describes how to configure IGMP snooping on the Dell FCoE
hardware.
• Chapter 16, “FCoE configuration using the Fabric OS CLI,” describes how to configure FCoE
using the Fabric OS CLI.
• Chapter 17, “CEE configuration management,” describes how to perform the administrative
tasks required by the Dell FCoE hardware.

Supported hardware and software

The following hardware platforms are supported in this release:
• Dell M8428-k
Within this manual, any appearance of the term “Dell FCoE hardware” is referring to:
• Dell M8428-k
• Dell FCOE10-24 port blade
• Dell Converged 10GbE Switch Module for IBM BladeCenter
• Dell 2 port 10GbE Converged Network Adapter for IBM BladeCenter

Document conventions

This section describes text formatting conventions and important notice formats used in this document.

Text formatting

The narrative-text formatting conventions that are used are as follows:
bold text Identifies command names
italic text Provides emphasis
code text Identifies CLI output
Identifies the names of user-manipulated GUI elements Identifies keywords and operands Identifies text to enter at the GUI or CLI
Identifies variables Identifies paths and Internet addresses Identifies document titles
Identifies command syntax examples
xvi Dell Converged Enhanced Ethernet Administrator’s Guide
53-1002116-01
For readability, command names in the narrative portions of this guide are presented in mixed
NOTE
ATTENTION
CAUTION
DANGER
lettercase: for example, switchShow. In actual examples, command lettercase is often all lowercase. Otherwise, this manual specifically notes those cases in which a command is case sensitive.

Command syntax conventions

Command syntax in this manual follows these conventions:
command Commands are printed in bold.
--option, option Command options are printed in bold.
-argument, arg Arguments.
[ ] Optional element.
variable Variables are printed in italics. In the help pages, values are underlined
enclosed in angled brackets < >.
... Repeat the previous element, for example “member[;member...]”
value Fixed values following arguments are printed in plain font. For example,
--show WWN
| Boolean. Elements are exclusive. Example:
--show -mode egress | ingress
or

Notes, cautions, and warnings

The following notices and statements are used in this manual. They are listed below in order of increasing severity of potential hazards.
A note provides a tip, guidance, or advice, emphasizes important information, or provides a reference to related information.
An Attention statement indicates potential damage to hardware or data.
A Caution statement alerts you to situations that can be potentially hazardous to you or cause damage to hardware, firmware, software, or data.
A Danger statement indicates conditions or situations that can be potentially lethal or extremely hazardous to you. Safety labels are also attached directly to products to warn of these conditions or situations.
Dell Converged Enhanced Ethernet Administrator’s Guide xvii 53-1002116-01

Notice to the reader

NOTE
This document may contain references to the trademarks of the following corporations. These trademarks are the properties of their respective companies and corporations.
These references are made for informational purposes only.
Corporation Referenced Trademarks and Products
IBM BladeCenter Advanced Management Module Protect Mode

Getting technical help

Dell is committed to ensuring that your investment in our products remains cost-effective. If you need assistance, or find errors in the manuals, contact Dell Technical Support.

Contacting Dell

For customers in the United States, call 800-WWW.DELL (800.999.3355).
If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip, bill, or Dell product catalog.
Dell provides several online and telephone-based support and service options. Availability varies by country and product, and some services may not be available in your area. To contact Dell for sales, technical support, or customer service issues:
1. Visit http://www.support.dell.com.
2. Click your country or region at the bottom of the page. For a full listing of countries and regions, click All.
3. In the Support menu, click All Support.
Choose the method of contacting Dell that is convenient for you.
xviii Dell Converged Enhanced Ethernet Administrator’s Guide
53-1002116-01
Chapter

Introducing FCoE

In this chapter

•FCoE terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
•FCoE overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
•Layer 2 Ethernet overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
•FCoE Initialization Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
•FCoE queuing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

FCoE terminology

Tab le 1 lists and describes the FCoE terminology used in this document.
TABLE 1 FCoE terminology
Term Description
1
FCoE Fibre Channel over Ethernet
CEE Converged Enhanced Ethernet
VN_port FCoE equivalent of an FC N_port
VF_port FCoE equivalent of an FC F_port
ENode An FCoE device that supports FCoE VN_ports
FCoE Forwarder (FCF) An FCoE link end point that provides FC fabric

FCoE overview

Fibre Channel over Ethernet (FCoE) enables you to transport FC protocols and frames over Converged Enhanced Ethernet (CEE) networks. CEE is an enhanced Ethernet that enables the convergence of various applications in data centers (LAN, SAN, and HPC) onto a single interconnect technology.
FCoE provides a method of encapsulating the Fibre Channel (FC) traffic over a physical Ethernet link. FCoE frames use a unique EtherType that enables FCoE traffic and standard Ethernet traffic to be carried on the same link. FC frames are encapsulated in an Ethernet frame and sent from one FCoE-aware device across an Ethernet network to a second FCoE-aware device. The FCoE-aware devices may be FCoE end nodes (ENodes) such as servers, storage arrays, or tape drives on one end and FCoE Forwarders on the other end. FCoE Forwarders (FCFs) are switches providing FC fabric services and FCoE-to-FC bridging.
(servers and target devices)
services
Dell Converged Enhanced Ethernet Administrator’s Guide 1 53-1002116-01
1
NOTE
NOTE
FCoE overview
The motivation behind using CEE networks as a transport mechanism for FC arises from the desire to simplify host protocol stacks and consolidate network interfaces in data center environments. FC standards allow for building highly reliable, high-performance fabrics for shared storage, and these characteristics are what CEE brings to data centers. Therefore, it is logical to consider transporting FC protocols over a reliable CEE network in such a way that it is completely transparent to the applications. The underlying CEE fabric is highly reliable and high performing, the same as the FC SAN.
In FCoE, ENodes discover FCFs and initialize the FCoE connection through the FCoE Initialization Protocol (FIP). The FIP has a separate EtherType from FCoE. The FIP includes a discovery phase in which ENodes solicit FCFs, and FCFs respond to the solicitations with advertisements of their own. At this point, the ENodes know enough about the FCFs to log into them. The fabric login and fabric discovery (FLOGI/FDISC) for VN-to-VF port connections is also part of the FIP.
With pre-FIP implementations, as an alternative to FIP, directly connected devices can send an FCoE-encapsulated FLOGI to the connected FCF.

FCoE hardware

At a fundamental level, FCoE is designed to enable the transport of storage and networking traffic over the same physical link. Utilizing this technology, Dell FCoE hardware provides a unique platform that connects servers to both LAN and SAN environments.
Within this manual, any appearance of the term “Dell FCoE hardware” refers to any of Dell’s FCoE products.
The intermediate switching devices in the CEE network do not have to be FCoE-aware. They simply route the FCoE traffic to the FCoE device based on the Ethernet destination address in the FCoE frame.
2 Dell Converged Enhanced Ethernet Administrator’s Guide
53-1002116-01

Layer 2 Ethernet overview

Classic Layer 2 Ethernet switch
FC switch
FC switch
Storage
Host 1 Host 2
Host 3
Dell M8428-k
Switch
CNA or
classic NIC
CNA or
classic NIC
Classic NIC
The Dell FCoE hardware contain CEE ports that support FCoE forwarding. The CEE ports are also backwards compatible and support classic Layer 2 Ethernet networks (see Figure 1). In Layer 2 Ethernet operation, a host with a Converged Network Adapter (CNA) can be directly attached to a CEE port on the Dell FCoE hardware. Another host with a classic 10-Gigabit Ethernet NIC can be either directly attached to a CEE port, or attached to a classic Layer 2 Ethernet network which is attached to the Dell FCoE hardware.
FIGURE 1 Multiple switch fabric configuration
Layer 2 Ethernet overview
1

Layer 2 forwarding

Layer 2 Ethernet frames are forwarded on the CEE ports. 802.1Q VLAN support is used to tag incoming frames to specific VLANs, and 802.3ac VLAN tagging support is used to accept VLAN tagged frames from external devices. The 802.1D Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), and Multiple Spanning Tree Protocol (MSTP) are used as the bridging
Dell Converged Enhanced Ethernet Administrator’s Guide 3 53-1002116-01
protocols between Layer 2 switches.
Layer 2 Ethernet overview
NOTE
NOTE
1
The Dell FCoE hardware handles Ethernet frames as follows:
• When the destination MAC address is not in the lookup table, the frame is flooded on all ports
except the ingress port.
• When the destination MAC address is present in the lookup table, the frame is switched only to
the correct egress port.
• When the destination MAC address is present in the lookup table, and the egress port is the
same as the ingress port, the frame is dropped.
• If the Ethernet Frame Check Sequence (FCS) is incorrect, because the switch is in cut-through
mode, a correctly formatted Ethernet frame is sent out with an incorrect FCS.
• If the Ethernet frame is too short, the frame is discarded and the error counter is incremented.
• If the Ethernet frame is too long, the frame is discarded and the error counter is incremented.
• Frames sent to a broadcast destination MAC address are flooded on all ports except the
ingress port.
• When MAC address entries in the lookup table time out, they are removed. In this event, frame
forwarding changes from unicast to flood.
• An existing MAC address entry in the lookup table is discarded when a device is moved to a
new location. When a device is moved, the ingress frame from the new port causes the old lookup table entry to be discarded and the new entry inserted into the lookup table. Frame forwarding remains unicast to the new port.
• When the lookup table is full, new entries replace the oldest MAC addresses after the oldest
MAC addresses age and time out. MAC addresses that still have traffic running are not timed out.
New entries start replacing older entries when the lookup table reaches 90 percent of its 32k capacity.

VLAN tagging

The Dell FCoE hardware handles VLAN tagging as follows:
• If the CEE port is configured to tag incoming frames with a single VLAN ID, then incoming
frames that are untagged are tagged with the VLAN ID.
• If the CEE port is configured to tag incoming frames with multiple VLAN IDs, then incoming
frames that are untagged are tagged with the correct VLAN ID based on the port setting.
• If the CEE port is configured to accept externally tagged frames, then incoming frames that are
tagged with a VLAN ID are passed through unchanged.
Only a single switch-wide VLAN is capable of forwarding FCoE traffic.
For detailed information on configuring VLANs, see “Configuring VLANs Using the CEE CLI” on page 31.
4 Dell Converged Enhanced Ethernet Administrator’s Guide
53-1002116-01
Layer 2 Ethernet overview
1

Loop-free network environment

The Dell FCoE hardware uses the following protocols to maintain a loop-free network environment:
• 802.1D Spanning Tree Protocol (STP)—STP is required to create a loop-free topology in the LAN.
• Rapid Spanning Tree Protocol (RSTP)—RSTP evolved from the 802.1D STP standard. RSTP
provides for a faster spanning tree convergence after a topology change.
• Multiple Spanning Tree Protocol (MSTP)—MSTP defines an extension to RSTP to further develop
the usefulness of VLANs. With per-VLAN MSTP, you can configure a separate spanning tree for each VLAN group. The protocol automatically blocks the links that are redundant in each spanning tree.
Using MSTP, you can create multiple loop-free active topologies on a single physical topology. These loop-free topologies are mapped to a set of configurable VLANs. This enables you to better utilize the physical resources present in the network and achieve better load balancing of VLAN traffic.
For detailed information on configuring these protocols, see “Configuring STP, RSTP, and MSTP
using the CEE CLI” on page 43.

Frame classification (incoming)

The Dell FCoE hardware is capable of classifying incoming Ethernet frames based on the following criteria:
• Port number
• Protocol
• MAC address
The classified frames can be tagged with a VLAN ID or with 802.1p Ethernet priority. The 802.1p Ethernet priority tagging is done using the Layer 2 Class of Service (CoS). The 802.1p Ethernet priority is used to tag frames in a VLAN with a Layer 2 CoS to prioritize traffic in the VLAN. The Dell FCoE hardware also accepts frames that have been tagged by an external device.
Frame classification options are as follows:
• VLAN ID and Layer 2 CoS by physical port number—With this option, the port is set to classify
incoming frames to a preset VLAN ID and the Layer 2 CoS by the physical port number on the Dell FCoE hardware.
• VLAN ID and Layer 2 CoS by LAG virtual port number—With this option, the port is set to classify
incoming frames to a preset VLAN ID and Layer 2 CoS by the Link Aggregation Group (LAG) virtual port number.
• Layer 2 CoS mutation—With this option, the port is set to change the Layer 2 CoS setting by
enabling the QoS mutation feature.
• Layer 2 CoS trust—With this option, the port is set to accept the Layer 2 CoS of incoming
frames by enabling the QoS trust feature.
For detailed information on configuring QoS, see “Configuring QoS using the CEE CLI” on page 93.
Dell Converged Enhanced Ethernet Administrator’s Guide 5 53-1002116-01
Layer 2 Ethernet overview
1

Congestion control and queuing

The Dell FCoE hardware supports several congestion control and queuing strategies. As an output queue approaches congestion, Random Early Detection (RED) is used to selectively and proactively drop frames to maintain maximum link utilization. Incoming frames are classified into priority queues based on the Layer 2 CoS setting of the incoming frame, or the possible rewriting of the Layer 2 CoS field based on the settings of the CEE port or VLAN.
The Dell FCoE hardware supports a combination of two scheduling strategies to queue frames to the egress ports; Priority queuing, which is also referred to as strict priority, and Deficit Weighted Round Robin (DWRR) queuing.
The scheduling algorithms work on the eight traffic classes as specified in 802.1Qaz Enhanced Transmission Selection (ETS).
Queuing features are described as follows:
• RED—RED increases link utilization. When multiple inbound TCP traffic streams are switched to
the same outbound port, and some traffic streams send small frames while other traffic streams send large frames, link utilization will not be able to reach 100 percent. When RED is enabled, link utilization approaches 100 percent.
• Classification—Setting user priority.
- Inbound frames are tagged with the user priority set for the inbound port. The tag is visible
when examining the frames on the outbound port. By default, all frames are tagged to priority zero.
- Externally tagged Layer 2 frames—When the port is set to accept externally tagged Layer 2
frames, the user priority is set to the Layer 2 CoS of the inbound frames.
• Queuing
- Input queuing—Input queuing optimizes the traffic flow in the following way. Suppose a CEE
port has inbound traffic that is tagged with several priority values, and traffic from different priority settings is switched to different outbound ports. Some outbound ports are already congested with background traffic while others are uncongested. With input queuing, the traffic rate of the traffic streams switched to uncongested ports should remain high.
- Output queuing—Output queuing optimizes the traffic flow in the following way. Suppose
that several ports carry inbound traffic with different priority settings. Traffic from all ports is switched to the same outbound port. If the inbound ports have different traffic rates, some outbound priority groups will be congested while others can remain uncongested. With output queuing, the traffic rate of the traffic streams that are uncongested should remain high.
- Multicast rate limit—A typical multicast rate limiting example is where several ports carry
multicast inbound traffic that is tagged with several priority values. Traffic with different priority settings is switched to different outbound ports. The multicast rate limit is set so that the total multicast traffic rate on output ports is less than the specified set rate limit.
- Multicast input queuing—A typical multicast input queuing example is where several ports
carry multicast inbound traffic that is tagged with several priority values. Traffic with different priority settings is switched to different outbound ports. Some outbound ports are already congested with background traffic while others are uncongested. The traffic rate of the traffic streams switched to the uncongested ports should remain high. All outbound ports should carry some multicast frames from all inbound ports. This enables multicast traffic distribution relative to the set threshold values.
6 Dell Converged Enhanced Ethernet Administrator’s Guide
53-1002116-01
Layer 2 Ethernet overview
1
- Multicast output queuing—A typical multicast output queuing example is where several
ports carry multicast inbound traffic. Each port has a different priority setting. Traffic from all ports is switched to the same outbound port. If the inbound ports have varying traffic rates, some outbound priority groups will be congested while others remain uncongested. The traffic rate of the traffic streams that are uncongested remains high. The outbound ports should carry some multicast frames from all the inbound ports.
• Scheduling—A typical example of scheduling policy (using SP0 and SP1 modes) is where ports
0 through 7 carry inbound traffic, each port has a unique priority level, port 0 has priority 0, port 1 has priority 1, and so on. All traffic is switched to the same outbound port. In SP0 mode, all ports have DWRR scheduling; therefore, the frames-per-second (FPS) on all ports should correspond to the DWRR settings. In SP1 mode, priority 7 traffic uses SP; therefore, priority 7 can achieve a higher FPS. Frames from input ports with the same priority level should be scheduled in a round robin manner to the output port.
When setting the scheduling policy, each priority group that is using DWRR scheduling can be set to use a percentage of the total bandwidth by setting the PG_Percentage parameter.
For detailed information on configuring QoS, see “Configuring QoS using the CEE CLI” on page 93.

Access control

Access Control Lists (ACLs) are used for Layer 2 switching security. Standard ACLs inspect the source address for the inbound ports. Extended ACLs provide filtering by source and destination addresses and protocol. ACLs can be applied to the CEE ports or to VLANs.
ACLs function as follows:
• A standard Ethernet ACL configured on a physical port is used to permit or deny frames based
on the source MAC address. The default is to permit all frames.
• An extended Ethernet ACL configured on a physical port is used to permit or deny frames
based on the source MAC address, destination MAC address, and EtherType. The default is to permit all frames.
• A standard Ethernet ACL configured on a LAG virtual port is used to permit or deny frames
based on the source MAC address. The default is to permit all frames. LAG ACLs apply to all ports in the LAG.
• An extended Ethernet ACL configured on a LAG virtual port is used to permit or deny frames
based on the source MAC address, destination MAC address, and EtherType. The default is to permit all frames. LAG ACLs apply to all ports in the LAG.
• A standard Ethernet ACL configured on a VLAN is used to permit or deny frames based on the
source MAC address. The default is to permit all frames. VLAN ACLs apply to the Switch Vertical Interface (SVI) for the VLAN.
• An extended Ethernet ACL configured on a VLAN is used to permit or deny frames based on the
source MAC address, destination MAC address, and EtherType. The default is to permit all frames. VLAN ACLs apply to the Switch Vertical Interface (SVI) for the VLAN.
For detailed information on configuring ACLs, see “Configuring ACLs using the CEE CLI” on page 87.

Access Gateway

All ports on the switch come from the factory set to Access Gateway mode, with the default Access Gateway mapping. See the “Access Gateway Administrator’s Guide” for full details.
Dell Converged Enhanced Ethernet Administrator’s Guide 7 53-1002116-01

FCoE Initialization Protocol

NOTE
NOTE
NOTE
1

Trunking

The term “trunking” in an Ethernet network refers to the use of multiple network links (ports) in parallel to increase the link speed beyond the limits of any one single link or port, and to increase the redundancy for higher availability.
802.1ab Link Layer Discovery Protocol (LLDP) is used to detect links to connected switches or
hosts. Trunks can then be configured between an adjacent switch or host and the Dell FCoE hardware using the VLAN classifier commands. See “Configuring an interface port as a trunk
interface” on page 37.
The Data Center Bridging (DCB) Capability Exchange Protocol (DCBX) extension is used to identify a CEE-capable port on an adjacent switch or host. For detailed information on configuring LLDP and DCBX, see “Configuring LLDP using the CEE CLI” on page 75.
The 802.3ad Link Aggregation Control Protocol (LACP) is used to combine multiple links to create a trunk with the combined bandwidth of all the individual links. For detailed information on configuring LACP, see “Configuring Link Aggregation using the CEE CLI” on page 65.
The Dell software supports a maximum 24 LAG interfaces.

Flow Control

802.3x Ethernet pause and Ethernet Priority-based Flow Control (PFC) are used to prevent dropped
frames by slowing traffic at the source end of a link. When a port on a switch or host is not ready to receive more traffic from the source, perhaps due to congestion, it sends pause frames to the source to pause the traffic flow. When the congestion has been cleared, it stops requesting the source to pause traffic flow, and traffic resumes without any frame drop.
When Ethernet pause is enabled, pause frames are sent to the traffic source. Similarly, when PFC is enabled, there is no frame drop; pause frames are sent to the source switch.
For detailed information on configuring Ethernet pause and PFC, see “Configuring QoS using the
CEE CLI” on page 93.
FCoE Initialization Protocol
The FCoE Initialization Protocol (FIP) discovers and initializes FCoE capable entities connected to an Ethernet cloud through a dedicated Ethertype, 0x8914, in the Ethernet frame.

FIP discovery

This software version supports the October 8, 2008 (REV 1.03) of the ANSI FC Backbone Specification with priority-tagged FIP VLAN discovery protocol and FIP version 0. This release does not support FIP Keep Alive.
8 Dell Converged Enhanced Ethernet Administrator’s Guide
53-1002116-01
FCoE Initialization Protocol
NOTE
The Dell FCoE hardware FIP discovery phase operates as follows:
1
• The Dell FCoE hardware uses the FCoE Initialization Protocol (FIP). Enodes discover FCFs and
initialize the FCoE connection through the FIP.
• Solicited advertisements—A typical scenario is where a Dell FCoE hardware receives a FIP
solicitation from an ENode. Replies to the original FIP solicitation are sent to the MAC address embedded in the original FIP solicitation. After being accepted, the ENode is added to the VN_port table.
• Login group—When enabled, replies to solicitations are sent only by Dell FCoE hardware that
have the ENode in the login group.
• VLAN 1—The Dell FCoE hardware should not forward FIP frames on VLAN 1 because it is
reserved for management traffic only.
• A fabric-provided MAC address is supported. A server-provided MAC-address is not supported
in the Fabric OS v6.3.1_cee release.
In the fabric-provided MAC address format, VN_port MAC addresses are based on a 24-bit fabric-supplied value. The first three bytes of this value is referred to as the FCMAP. The next three bytes are the FC ID, which is assigned by the switch when the ENode logs in to the switch.

FIP login

FIP login operates as follows:
• ENodes can log in to the Dell FCoE hardware using FIP. Fabric login (FLOGI) and fabric
discovery (FDISC) are accepted. Dell FCoE hardware in the fabric maintain the MAC address, World Wide Name (WWN), and PID mappings per login. Each ENode port should have a unique MAC address and WWN.
• FIP FLOGI—The Dell FCoE hardware accepts the FIP FLOGI from the ENode. The FIP FLOGI
acceptance (ACC) is sent to the ENode if the ENode MAC address or WWN matches the VN_port table on the Dell FCoE hardware. The FIP FLOGI request is rejected if the ENode MAC address or WWN does not match. The ENode login is added to the VN_port table. Fabric Provided MAC addressing (FPMA) is supported.
• FIP FDISC—The Dell FCoE hardware accepts FIP FDISC from the ENode. FIP FDISC acceptance
(ACC) is sent to the ENode if the ENode MAC address or WWN matches the VN_port table on the Dell FCoE hardware. The FIP FDISC request is rejected if the ENode MAC address or WWN does not match. The ENode login is added to the VN_port table. FPMA is supported.
• Maximum logins per VF_port—The Dell FCoE hardware supports a maximum of 255 logins per
VF_port. The VF_port rejects further logins after the maximum is reached.
• Maximum logins per switch—The Dell FCoE hardware accepts a maximum of 1024 logins per
switch. Note that the Dell FCoE hardware does not reject further logins after the maximum is reached.
Dell Converged Enhanced Ethernet Administrator’s Guide 9 53-1002116-01
FCoE Initialization Protocol
NOTE
1

FIP logout

FIP logout operates as follows:
• ENodes can log out from the Dell FCoE hardware using FIP. The Dell FCoE hardware in the
fabric updates the MAC address, WWN, and PID mappings upon logout. The Dell FCoE hardware also handles scenarios of implicit logout where the ENode has left the fabric without explicitly logging out.
• FIP logout (LOGO)—The Dell FCoE hardware accepts a FIP LOGO from the ENode. The FIP LOGO
ACC should be sent to the ENode if the ENode MAC address matches the VN_port table on the Dell FCoE hardware. The LOGO is ignored (not rejected) if the ENode MAC address does not match. The ENode logout is updated in the VN_port table. FPMA is supported.
• Implicit logout—With the ENode directly connected to a CEE port, if the port that the ENode is
attached to goes offline, the Dell FCoE hardware implicitly logs out that ENode. ENode logout is updated in the VN_port table. The Dell FCoE hardware sends FCoE LOGO on behalf of the ENode.

FCoE login

The Dell FCoE hardware FCoE login operates as follows:
• ENodes can log in to the Dell FCoE hardware using FCoE encapsulated, FC Extended Link
Service (ELS) frames. FLOGI and FDISC are accepted. Dell FCoE hardware in the fabric maintains the MAC address to WWN/PID mappings per login. Class 2 FLOGI is not supported.
• FCoE FLOGI—The Dell FCoE hardware accepts FCoE FLOGI from the ENode. FCoE FLOGI ACC is
sent to the ENode if the FCMAP matches the VN_port table on the Dell FCoE hardware. Requests are ignored if the FCMAP does not match. The ENode login is added to the VN_port table.
• FCoE FDISC—The Dell FCoE hardware accepts FCoE FDISC from the ENode. FCoE FDISC ACC is
sent to the ENode if the FCMAP matches the VN_port table on the Dell FCoE hardware. The FCoE FDISC request is ignored if the FCMAP does not match. The ENode login is added to the VN_port table.
• FCMAP—The Dell FCoE hardware accepts FCoE FLOGI from the ENode. The FCMAP determines
which FCoE VLAN is accepted for the FCoE session.
Only one FCoE VLAN is supported in the Fabric OS v6.3.1_cee release.

FCoE logout

The Dell FCoE hardware FCoE logout operates as follows:
• ENodes can log out from the Dell FCoE hardware using the FCoE encapsulated, FC ELS frame.
Dell FCoE hardware in the fabric updates the MAC address to WWN/PID mappings upon logout. The Dell FCoE hardware also handles scenarios of implicit logout where the ENode has left the fabric without explicitly logging out.
• FCoE LOGO—The Dell FCoE hardware accepts the FCoE LOGO from the ENode. The FCoE LOGO
ACC is sent to the ENode if the ENode MAC address matches the VN_port table on the Dell FCoE hardware. The LOGO is ignored (not rejected) if the ENode MAC address does not match. The ENode logout is updated in the VN_port table.
10 Dell Converged Enhanced Ethernet Admin istrator’s Guide
53-1002116-01
FCoE Initialization Protocol
1

Logincfg

The Dell FCoE hardware logincfg mechanism operates as follows:
• The logincfg is the mechanism for controlling ENode logins per Dell FCoE hardware. Each unit
of Dell FCoE hardware maintains its own logincfg.
• Login configuration management is optional—when login management is disabled, the default
behavior is to accept logins from any ENode.
• Logingroup creation and deletion—The Dell FCoE hardware accepts valid logingroup names
and member WWNs. The Dell FCoE hardware rejects invalid entries. The Dell FCoE hardware allows the deletion of logingroups that are defined and committed. You can display defined and committed logingroups. The logingroup capability is disabled by default.
• Member add and remove—You can add valid member WWNs. Invalid WWNs are rejected.
Duplicate WWNs are uniquely resolved. You can display the current view of defined logingroups when changes are made to the configuration.
• Commit and abort—Defined logingroup changes can be aborted with no effect on existing
sessions. The Dell FCoE hardware does not apply the configurations to new sessions until the changes are committed. Once defined, logingroups are committed. The Dell FCoE hardware immediately uses the new configuration.
• No traffic disruption—Changing the logingroup without committing the changes does not affect
existing sessions. After committing the changes, ENodes that were already logged in continue to function even when that member is removed from the logingroup. New logins from the former member are rejected.

Name server

The Dell FCoE hardware name server function operates as follows:
• ENode login and logout to and from the Dell FCoE hardware updates the name server in the FC
fabric. The Dell FCoE hardware maintains the MAC address to WWN/PID mappings.
• ENode login and logout—When an ENode login occurs through any means (FIP FLOGI, FIP
FDISC, FCoE FLOGI, or FCoE FDISC), an entry is added to the name server. When an ENode logout occurs through any means (FIP LOGO, FCoE LOGO, or implicit logout), the entry is removed from the name server.
• ENode data—The Dell FCoE hardware maintains a VN_port table. The table tracks the ENode
MAC address, FIP login parameters for each login from the same ENode, and WWN/PID mappings on the FC side. You can display the VN_port table with the fcoe -loginshow port command.

FC zoning

The Dell FCoE hardware FC zoning operates as follows:
• The virtual devices created by the Dell FCoE hardware on behalf of the ENodes are subject to
FC zoning. An ENode is only allowed to access devices in the same zones. Administrative Domains (ADs) are not supported in the Fabric OS v6.3.1_cee release.
• ENodes can access FC devices in the same zones— FC devices that are not in the same zones
cannot be accessed. Zone members can overlap in multiple zones (that is, overlapping zones). Zoning changes are immediately enabled by hardware enforced zoning.
Dell Converged Enhanced Ethernet Administrator’s Guide 11 53-1002116-01
1
NOTE
NOTE

FCoE queuing

• ENodes can access all FC devices with no zoning—ENodes can access all FC devices in the
fabric when cfgdisable is issued and Default Zone is set to All Access Mode.
• Field replacement—When a Dell FCoE hardware is replaced in the field, you can perform a
configdownload on a previously saved configuration. No zoning change is required.

Registered State Change Notification (RSCN)

The Dell FCoE hardware RSCN function operates as follows:
• RSCN events generated in the FC fabric are forwarded to the ENodes. RSCN events generated
on the FCoE side are forwarded to the FC devices. CEE is not aware of RSCN events.
• Device RSCN—An RSCN is generated to all registered and affected members when an ENode
either logs in or logs out of an FCF through any means. An RSCN is generated when an FC N_port device either logs in or logs out of the FC fabric.
When transmitting an RSCN, zoning rules still apply for FCoE devices as the devices are treated as regular FC N_ports.
• VF_port RSCN—An RSCN is generated to all registered members when a VF_port goes online or
offline, causing ENode or FC devices to be added or removed.
• Domain RSCN—An RSCN is generated to all registered and affected members when an FC
switch port goes online or offline, causing ENode or FC devices to be added or removed. An RSCN is generated when two FC switches merge or segment, causing ENode or FC devices to be added or removed. When FC switches merge or segment, an RSCN is propagated to ENodes.
• Zoning RSCN—An RSCN is generated to all registered and affected members when a zoning
exchange occurs in the FC fabric.
FCoE queuing
The QOS configuration controls the FCoE traffic distribution. Note that changing these settings requires changes on both the Dell FCoE hardware and the CNA; therefore, the link must be taken offline and back online after a change is made. Traffic scheduler configuration changes affect FCoE traffic distribution as follows:
• Changing the priority group for a port causes the FCoE traffic distribution to update. The priority
group and bandwidth are updated.
• Changing the priority table for a port causes the FCoE traffic distribution to be updated. The
COS-to-priority group mapping is updated.
• Changing the class map for a port causes the FCoE traffic distribution to be updated.
• Changing the policy map for a port causes FCoE traffic distribution to be updated.
• Changing the CEE map for a port causes the FCoE traffic distribution to be updated.
• The FCMAP to VLAN mapping determines the FCoE VLAN allowed for the FCoE session.
Modifying this mapping causes the existing sessions to terminate.
Only one FCoE VLAN is supported in the Fabric OS v6.3.1_cee release.
12 Dell Converged Enhanced Ethernet Admin istrator’s Guide
53-1002116-01
Loading...
+ 138 hidden pages
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use