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

Closed with Code Change in Fabric OS v7.2.1
Fabric OS v7.2.1a Release Notes v1.0 Page 41 of 55
Defect ID:
DEFECT000467051
Technical Severity:
Medium
Probability:
High
Product:
FOS
Technology:
Monitoring/RAS
Reported In Release:
FOS7.0.2
Technology Area:
Fabric Watch
Closed In Release(s):
FOS7.2.1(Fixed)
Symptom:
switchstatuspolicy shows incorrect port count which may impact the accuracy of switch status
Condition:
switchstatuspolicy incorrectly accounts for logical ports into the total physical port count.
Defect ID:
DEFECT000467204
Technical Severity:
Medium
Probability:
Low
Product:
FOS
Technology:
Management
Reported In Release:
FOS7.0.0_pha
Technology Area:
SNMPv2, SNMPv3 & MIBs
Closed In Release(s):
FOS7.2.1(Fixed)
Symptom:
SNMPV3 user entries are not cleared when CMM executes restore default.
Condition:
Applicable only for embedded BR6547 platform
Workaround:
Default to snmpv3 configuration with "snmpconfig --default snmpv3" command.
Defect ID:
DEFECT000467965
Technical Severity:
Medium
Probability:
Medium
Product:
FOS
Technology:
Management
Reported In Release:
FOS7.2.0
Technology Area:
Web Tools
Closed In Release(s):
FOS7.2.1(Fixed)
Symptom:
Seed switch with lower versions (pre-v7.2.0) of Webtools, will incorrectly display switches running
MAPS as "blue" and unknown.
Condition:
A fabric having seed switch running FOS version lower than V7.2.0 and checking for Switch Health
in Webtools
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.