Fips Lag Support On Server Ports; Port Fcf And Enode Detection - Lenovo Flex System Fabric CN4093 Application Manual

FIPS LAG Support on Server Ports

Port FCF and ENode Detection

© Copyright Lenovo 2017
FIPS LAG Support allows FCoE and Ethernet traffic to co‐exist within the same
LAGs (ports). By default, FCoE servers (CNA/HBA) do not support aggregation,
while Ethernet (NIC/CNA) are aggregation capable. Due to this incompatibility on
FCoE capable servers, the FCoE traffic is generated on separate (exclusive) ports
whenever Ethernet adapters need to be consolidated into a LAG.
FIPS LAG Support allows FCoE traffic and traditional Ethernet traffic to use the
same ports for traffic by pinning each destination FCoE Enode‐MAC to a static
switch port within the LAG. This is due to each server port within a LAG expecting
FCoE traffic with a destination ‐ MAC as its Enode‐MAC to arrive on the same port
within the LAG from the switch (i.e. FCoE traffic with a destination Enode‐MAC is
always expected to traverse the link with that Enode‐MAC). Initially, any incoming
FIP packets are snooped by the switch and if the Enode‐MAC is new (previously
undiscovered) and source port is part of a LAG, then a static Enode‐MAC entry is
installed within the switch. Any unicast (FIP) response then onward is transmitted
using the assigned port within the LAG and not any other port. Thus, FCoE traffic
then strictly transmits across only the assigned port (within the LAG) for each
Enode. Similarly, any VN‐Port MACs are pinned on a port by port basis within a
LAG. Regular (non‐FCoE) Ethernet traffic will continue to operate across the LAG
normally (using any of the links based on balancing algorithm).
This feature is automatically activated upon server‐port LAG mode detection by
FIPS.
Note: FCoE Fips must be enabled on FSB/FCF switch.
When FIP snooping is enabled on a port, the port is placed in FCF auto‐detect
mode by default. In this mode, the port assumes connection to an ENode unless
FIP packets show the port is connected to an external FCF.
Ports can also be specifically configured as to whether automatic FCF detection
should be used, or whether the port is connected to an external FCF or ENode:
CN 4093(config)# fcoe fips port <port alias, number, list, or range> fcf-mode
{auto|on|off}
When FCF mode is on, the port is assumed to be connected to a trusted external
FCF, and only ACLs appropriate to FCFs will be installed on the port. When off,
the port is assumed to be connected to an ENode, and only ACLs appropriate to
ENodes will be installed. When the mode is changed (either through manual
configuration or as a result of automatic detection), the appropriate ACLs are
automatically added, removed, or changed to reflect the new FCF or ENode
connection.
Chapter 17: FCoE and CEE
307