Port Fcf And Enode Detection; Fcoe Connection Timeout - Lenovo RackSwitch G8264 Application Manual

Port FCF and ENode Detection

FCoE Connection Timeout

372
G8264 Application Guide for ENOS 8.4
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.
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 FCF.
Ports can also be specifically configured as to whether automatic FCF detection
will be used, or whether the port is connected to an FCF or ENode:
RS G8264(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 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.
FCoE‐related ACLs are added, changed, and removed as FCoE device connection
and disconnection are discovered. In addition, the administrator can enable or
disable automatic removal of ACLs for FCFs and other FCoE connections that
timeout (fail or are disconnected) without FIP notification.
By default, automatic removal of ACLs upon timeout is enabled. To change this
function, use the following CLI command:
RS G8264(config)# [no] fcoe fips timeout­acl