Brocade Network OS Administrator’s Guide v4.1.1 - Manual (Page 348)

If FKA timeouts are enabled on the switch, the VN_Port will be implicitly logged out in the event of a
VN_Port FKA timeout.
Name server operation
The Brocade VDX hardware name server function operates as follows:
• ENode login and logout to and from the Brocade VDX hardware updates the name server in the FC
fabric. The Brocade VDX hardware maintains the MAC address to WWN and 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 Brocade VDX 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 and PID
mappings on the FC side. You can display the VN_Port table with the show fcoe login command.
Registered State Change Notification
The Brocade VDX hardware Registered State Change Notification (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. DCB 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.
NOTE
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.
Local ENode configuration
Prior to the current release, the configuration of the number of FCoE interfaces to be created per
switch was done through a max-enodes attribute in the FCoE default fabric map. This was a global
configuration, and the same number of Virtual Fabric ports was configured on all the switches in the
VCS cluster in logical chassis cluster mode.
Beginning with the current release, the number of interfaces to be created is configured per switch by
means of the fcoe-enodes command, executed in RBridge ID configuration mode. This is known as
the local ENode configuration model. The number of ENodes that can be configured ranges from 0
through 1000, with a default of 64.
An FCoE license is required to enable FCoE interfaces. If this license is not present, no FCoE
interfaces are created. To upgrade from the previous release, the user executes the enode-config
Name server operation
348 Network OS Administrator’s Guide
53-1003225-04