beautypg.com

Configuring fcoe over lag, Configuring fcoe provisioning on lags – Brocade Network OS Administrator’s Guide v4.1.1 User Manual

Page 352

background image

6. Confirm the changes to the interface with the show running-config command.

switch# show running-config interface tengigabitethernet 3/0/19

interface TenGigabitEthernet 3/0/19

fabric isl enable

fabric trunk enable

channel-group 10 mode active type standard

lacp timeout long

fcoeport default

no shutdown

7. Use the show fcoe interface brief command to confirm the current status of the FCoE logins.

switch# show fcoe interface brief

8. Repeat this procedure for any additional interfaces.

Configuring FCoE over LAG

Network OS 4.0.0 and later supports FCoE over LAGs. These are LAGs between the FCoE Forwarder
(FCF) and a DCB capable switch. The entire LAG is provisioned for FCoE, so that all member ports
are used for FCoE traffic. FCoE traffic is broadcast on all the member links of the LAG.

NOTE
FCoE over LAG supports standard LAGs only. vLAGs are not supported.

Additionally, Network OS 4.0.0 and later supports multiple logins per port. This feature allows multiple
ENodes to login to a single 10-gigabit Ethernet port or a LAG.

Guidelines and restrictions for configuring FCoE over LAG

Follow these configuration guidelines and restrictions when configuring FCoE over LAG:

1. The intermediate switches may or may not be an FSB. However, FSB is recommended for security.
2. All ACLs and FCoE forwarding entries will continue to be on the FCF’s ingress ports.
3. It is assumed that the intermediate switch works in "Willing" mode towards the FCF in the DCBX

exchange, and accepts the configuration from the FCF and propagates it downstream.

4. The CEE/DCBX configuration is expected to identical on both FCF and the intermediate switch.
5. Irrespective of item 3 or item 4, the PFC/No-drop behavior from the FCF perspective will be

guaranteed only on the links between the FCF and first hop switch. There is no provision in the
standard to guarantee this requirement on all paths leading to the Enode.

6. FSBs may or may not be able to forward the FCoE LLS TLV to the Enodes. Hence this TLV may

not be present in the LLDP packets sent to the Enodes. The FCF continues to send this TLV in its
LLDP packets destined to the intermediate switch.

Configuring FCoE provisioning on LAGs

The existing fcoeport default command is extended to the LAG interfaces to support the new feature,
as shown in the example below.

switch# configure

Entering configuration mode terminal

switch(config)# interface Port-channel 10

switch(config-Port-channel-10)# fcoeport default

switch(config-Port-channel-10)#

This provisions all the member ports of Port-channel 10 for FCoE.

Configuring FCoE over LAG

352

Network OS Administrator’s Guide

53-1003225-04