Brocade Fabric OS v7.2.1 Release Notes v1.0

Closed with Code Change in Fabric OS v7.2.1
Fabric OS v7.2.1 Release Notes v1.0 Page 36 of 49
Defect ID:
DEFECT000468458
Technical Severity:
High
Probability:
Low
Product:
FOS
Technology:
Traffic Management
Reported In Release:
FOS7.2.0
Technology Area:
FC-FC routing
Closed In Release(s):
FOS7.2.1(Fixed)
Symptom:
FCR may indicate the error message "switch not ready for ex-ports" in switchshow.
Condition:
Repeated disruptive operation in blade/slot which is having E-Port and EX-Port in the FCR core
switch may result in the error message "switch not ready for ex-ports" in switchshow output.
Recovery:
Toggle the affected Ex-ports.
Defect ID:
DEFECT000468549
Technical Severity:
High
Probability:
Medium
Product:
FOS
Technology:
Traffic Management
Reported In Release:
FOS7.0.2
Technology Area:
FC-FC routing
Closed In Release(s):
FOS7.2.1(Fixed)
Symptom:
Hyperswap fails after device gets name server query rejected with reason
NSRJT_EXPL_NO_PORTID
Condition:
This is a timing issue that occurs rarely for a node device that sends back to back FLOGI within short
span of time on the same port.
Workaround:
Disable and enable ports manually to complete site swap
Recovery:
Toggle affected ports.
Defect ID:
DEFECT000469507
Technical Severity:
High
Probability:
Low
Product:
FOS
Technology:
Security
Reported In Release:
FOS7.0.1
Technology Area:
Encryption
Closed In Release(s):
FOS7.2.1(Fixed)
Symptom:
Tape backup jobs on encrypted tape may fail.
Condition:
Issue will be seen on Brocade Encryption Switch or FS8-18 blade with hosts and targets that doesn’t
support SRR/FCP_CONF and tape pipelining is enabled for the tape LUN.
Workaround:
Disable tape pipelining for tape LUNs corresponding to targets/CTC which don’t support
SRR/FCP_CONF.
Defect ID:
DEFECT000473144
Technical Severity:
Medium
Probability:
Low
Product:
FOS
Technology:
Monitoring/RAS
Reported In Release:
FOS7.1.1
Technology Area:
Fabric Watch
Closed In Release(s):
FOS7.2.1(Fixed)
Symptom:
The "fmmonitor" CLI command is able to change the time base on each filters. However, "thconfig"
CLI command is unable to change the time base of each filters and displays "Timebase not supported
by this class".
Condition:
Always seen while configuring time base for filters using "thconfig".
Workaround:
fmmonitor can be used in place of thconfig for timebase configuration for filter class.
Recovery:
fmmonitor can be used in place of thconfig for timebase configuration for filter class.