Fip Snooping For Specific Ports; Fips Lag Support On Server Ports - Lenovo ThinkSystem NE2552E Application Manual

FIP Snooping for Specific Ports

FIPS LAG Support on Server Ports

© Copyright Lenovo 2018
When FIP snooping is globally turned on (see above), ports may be individually
configured for participation in FIP snooping and automatic ACL generation. By
default, FIP snooping is enabled for each port. To change the setting for any
specific port, use the following CLI commands:
NE2552E(config)# [no] fcoe fips port <port number, alias, list, or range> enable
When FIP snooping is enabled on a port, FCoE‐related ACLs will be automatically
configured.
When FIP snooping is disabled on a port, all FCoE‐related ACLs on the port are
removed, and the switch will enforce no FCoE‐related rules for traffic on the port.
Note: FIP Snooping and IPv6 ACLs are not supported simultaneously on the same
ports. To use FIP snooping, remove IPv6 ACLs from the port.
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.
Chapter 15: Fibre Channel over Ethernet
251