Brocade Communications Systems 53-1001761-01 Benutzerhandbuch

FCoE Initialization Protocol

1

Logincfg

The Brocade FCoE hardware logincfg mechanism operates as follows:

•

The logincfg is the mechanism for controlling ENode logins per Brocade FCoE hardware. Each 
unit of Brocade FCoE hardware maintains its own logincfg. 

•

Login configuration management is optional—when login management is disabled, the default 
behavior is to accept logins from any ENode.

•

Logingroup creation and deletion—The Brocade FCoE hardware accepts valid logingroup 
names and member WWNs. The Brocade FCoE hardware rejects invalid entries. The Brocade 
FCoE hardware allows the deletion of logingroups that are defined and committed. You can 
display defined and committed logingroups. The logingroup capability is disabled by default.

•

Member add and remove—You can add valid member WWNs. Invalid WWNs are rejected. 
Duplicate WWNs are uniquely resolved. You can display the current view of defined logingroups 
when changes are made to the configuration.

•

Commit and abort—Defined logingroup changes can be aborted with no effect on existing 
sessions. The Brocade FCoE hardware does not apply the configurations to new sessions until 
the changes are committed. Once defined, logingroups are committed. The Brocade FCoE 
hardware immediately uses the new configuration.

•

No traffic disruption—Changing the logingroup without committing the changes does not affect 
existing sessions. After committing the changes, Enodes that were already logged in continue 
to function even when that member is removed from the logingroup. New logins from the 
former member are rejected.

Name server

The Brocade FCoE hardware name server function operates as follows:

•

ENode login and logout to and from the Brocade FCoE hardware updates the name server in 
the FC fabric. The Brocade FCoE hardware maintains the MAC address to WWN/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 FCoE 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/PID 
mappings on the FC side. You can display the VN_port table with the fcoe -loginshow port 
command.

FC zoning

The Brocade FCoE hardware FC zoning operates as follows:

•

The virtual devices created by the Brocade FCoE hardware on behalf of the ENodes are subject 
to FC zoning. An ENode is only allowed to access devices in the same zones. Administrative 
Domains (ADs) are not supported in the Fabric OS v6.4.0 release.

•

ENodes can access FC devices in the same zones— FC devices that are not in the same zones 
cannot be accessed. Zone members can overlap in multiple zones (that is, overlapping zones). 
Zoning changes are immediately enabled by hardware enforced zoning.