Release Notes

Closed with Code Change in Fabric OS v7.2.1b
Fabric OS v7.2.1e Release Notes v1.0 Page 56 of 82
Defect ID:
DEFECT000500532
Technical Severity:
High
Probability:
High
Product:
FOS
Technology:
Other
Reported In Release:
FOS7.2.0
Technology Area:
Other
Symptom:
On BR6547, Firmware status is shown incorrectly in firmwareImageinfo object.
Condition:
FirmwareStatus is shown as "inACtive", even though firmware is active.
Defect ID:
DEFECT000500759
Technical Severity:
Medium
Probability:
High
Product:
FOS
Technology:
Other
Reported In Release:
FOS7.2.1
Technology Area:
Other
Symptom:
CRC with Good EOF errors observed on FC8-64 in BR8150.
Condition:
Port blade FC8-64 is installed in BR8150 slot 2
Workaround:
Manually tune S2/P34 to 0x195DA1DD
Recovery:
Manually tune serdes value for S2/P34 to 0x195DA1DD
Defect ID:
DEFECT000501917
Technical Severity:
Medium
Probability:
Low
Product:
FOS
Technology:
Security
Reported In Release:
FOS7.2.1
Technology Area:
Encryption
Symptom:
In encryption environment with BES/FS8-18, switch or blade became faulty during initial discovery
of target.
Condition:
It may happen after EE became online and during initial discovery of targets, if the target returns error
for slow path commands(REPORT_LUN/INQUIRY).
.
Defect ID:
DEFECT000501919
Technical Severity:
Medium
Probability:
High
Product:
FOS
Technology:
Monitoring/RAS
Reported In Release:
FOS7.3.0
Technology Area:
Diagnostic Port (D_Port)
Symptom:
D-Port test PASSED with errors on D-Port Responder side.
Condition:
After electrical or optical loopback test, stats are not cleared in responder.
Defect ID:
DEFECT000502591
Technical Severity:
High
Probability:
Low
Product:
FOS
Technology:
Traffic Management
Reported In Release:
FOS7.2.0
Technology Area:
Routing
Symptom:
On a switch that had pre-FOS v7.1 installed before, upgrade the switch to FOS v7.1 or later, host lost
access to storage with missing route.
Condition:
If there is a port bounces during hareboot/hafailover (or as part of firmwaredownload), switches
could see this problem.
Workaround:
Upgrade to a release containing defect 459831 fix (FOS v7.1.1a, v7.1.2, v7.2.0). If a later release
is needed, then upgrade must be done to a release with the fix to this defect in it.
Recovery:
Port bounce alone may not fully recover. Need a slotpoweroff/on on impacted port blade or cold boot
on a switch.