Brocade Fabric OS v7.2.1a Release Notes v1.0

Closed with Code Change in Fabric OS v7.2.1a
Fabric OS v7.2.1a Release Notes v1.0 Page 34 of 55
Defect ID:
DEFECT000484327
Technical Severity:
High
Probability:
Low
Product:
FOS
Technology:
Traffic Management
Reported In Release:
FOS7.1.0
Technology Area:
FC-FC routing
Closed In Release(s):
FOS7.2.1a(Fixed)
Symptom:
Switch panic after name server detected duplicated WWPN with raslog:
2013/10/22-02:26:59, [NS-1012], 147485, SLOT 6 | FID 128, WARNING, , Detected duplicate
WWPN [] - devices removed with PID 0x3ce701 and 0x3ce80
Condition:
This may occur when
1. There is physically duplicated WWPN in the environment, or
2. An interleaved offline and online sequence between two different NPIV ports may trigger a false
duplicate WWPN detection.
Workaround:
Remove physically duplicate WWPN devices if any exist.
Recovery:
If there is no physically duplicate WWPN devices, switch recovers itself after panic.
Defect ID:
DEFECT000487235
Technical Severity:
High
Probability:
High
Product:
FOS
Technology:
Virtualization
Reported In Release:
FOS7.1.1
Technology Area:
Access Gateway
Closed In Release(s):
FOS7.2.1a(Fixed)
Symptom:
Hosts are not able to login to the Access Gateway after the Access Gateway is rebooted.
Condition:
The problem occurs under these conditions:
- No Access Gateway policies are enabled -- i.e. neither Port Group policy nor Auto Policy
- Access Gateway is rebooted
- One or more N-ports do not come online after reboot
Workaround:
Insure all N-ports come online after an Access Gateway reboot.
Recovery:
Either bring all required N-ports online or re-map the currently offline F-ports to the online N-port(s).
Defect ID:
DEFECT000487250
Technical Severity:
High
Probability:
Low
Product:
FOS
Technology:
Management
Reported In Release:
FOS7.1.1
Technology Area:
Platform Services
Closed In Release(s):
FOS7.2.1a(Fixed)
Symptom:
Host cannot connect to storage and CLI nsshow for a FC4 type device is missing FC4 type:
“FC4s:fcp”
Condition:
A timing condition is observed when a device sends 2 consecutive FLOGIs without an explicit logout
in between.
Recovery:
Reboot device or issue portdisable and portenable on the switch port
Defect ID:
DEFECT000487271
Technical Severity:
High
Probability:
Medium
Product:
FOS
Technology:
Management
Reported In Release:
FOS7.2.1
Technology Area:
Brocade Network Advisor
Closed In Release(s):
FOS7.2.1a(Fixed)
Symptom:
Unable to create flow with Flow Mirror feature through BNA with FOS v7.2.0x
Condition:
This happens in a race condition when the non-default switch goes to active prior to the default switch
in an VF environment after a cold boot or hafailover.
Workaround:
The FOS CLI can be used to successfully create the flow.
Recovery:
User can attempt to restart the flow. If it still fails and user has to use BNA to create flow, upgrade to a
FOS code revision with the fix.