Fabric OS v6.4.1 Release Notes v1.0 Page 33 of 62
• It is recommended that for directors with more than 300 E_Ports, the switch be disabled
prior to executing the “switchCfgTrunk” command (used to disable or enable trunking on
the switch).
• During non-disruptive firmware upgrades, E_Ports in R-RDY mode may cause some frame
drops on the E-port links.
• The portCfgFillWord
portCfgFillWordportCfgFillWord
portCfgFillWord command, applicable to 8G-capable ports, has been enhanced with
FOS v6.3.1 and v6.4 to provide two new configuration options (Modes 2 and 3). The
available settings include:
Mode
ModeMode
Mode
-
--
-
Link Init/Fill Word
Link Init/Fill WordLink Init/Fill Word
Link Init/Fill Word
Mode 0 – IDLE/IDLE
Mode 1 – ARBF/ARBF
Mode 2 – IDLE/ARBF
Mode 3 – If ARBF/ARBF fails use IDLE/ARBF
Although this setting only affects devices logged in at 8G, changing the mode is disruptive
regardless of the speed the port is operating at. The setting is retained and applied any
time an 8G device logs in. Upgrades to FOS v6.3.1 or v6.4 from prior releases supporting
only modes 0 and 1 will not change the existing setting, but switches or ports reset to
factory defaults with FOS v6.3.1 or v6.4 will be configured to Mode 0 by default. The
default setting on new units may vary by vendor. Please use portcfgshow CLI to view the
current portcfgfillword status for that port.
Modes 2 and 3 are compliant with FC-FS-3 specifications (standards specify the
IDLE/ARBF behavior of Mode 2 which is used by Mode 3 if ARBF/ARBF fails after 3
attempts). For most environments, Brocade recommends using Mode 3, as it provides
more flexibility and compatibility with a wide range of devices. In the event that the
default setting or Mode 3 does not work with a particular device, contact your switch
vendor for further assistance.
• For the configure command, in FOS v6.4, the default value that displays for Maximum Logins per
switch is different than the value that displays in FOS v6.3.x. The default value has not changed; it
was displayed incorrectly in FOS v6.3.x, and is now corrected.
