![Brocade Communications Systems Fabric OS v7.0.2 Release Note Download Page 64](http://html1.mh-extra.com/html/brocade-communications-systems/fabric-os-v7-0-2/fabric-os-v7-0-2_release-note_2817373064.webp)
Open Defects in Fabric OS v7.0.1
Fabric OS v7.0.2 Release Notes v1.0
Page 64 of 99
Defect ID:
DEFECT000342944
Technical Severity:
Medium
Summary:
WebTools dialog does not include FID in the error message resulting from Config Download
failure on DCX with multiple logical switches.
Symptom:
If configdownload fails for a particular fid while being performed through WebTools , the
displayed error message does not include the logical switch FID.
Feature:
FOS-Infrastructure
Function:
Config Download
Probability:
Low
Found in Release:
FOS7.0.0
Defect ID:
DEFECT000348045
Technical Severity:
Medium
Summary:
Fabric Watch is not properly triggering E-Port state change events.
Symptom:
Fabric Watch logs will not include E-Port state changes events.
Workaround:
Use Fabric Watch Port Class to monitor state changes.
Feature:
Field Escalation
Function:
Fabric Services
Probability:
Medium
Found in Release:
FOS6.3.2
Service Request ID:
SR 586189
Defect ID:
DEFECT000367062
Technical Severity:
Medium
Summary:
Manually stopping D-Port tests may result in software verify error.
Symptom:
User sees the following software verify error message after manually stopping D-Port tests.
"VERIFY - Failed expression: (SM_SUCCESS == dp_return)"
Workaround:
Workaround is to leave D-Port tests running to completion and not stop them.
Feature:
FC Services
Function:
D-port
Probability:
Medium
Found in Release:
FOS7.0.1
Defect ID:
DEFECT000367436
Technical Severity:
Medium
Summary:
Fabric Watch email alerts use the default switch name instead of current switch name in
the "Sent From" field.
Symptom:
The 'sent from' field name in a Fabric watch email alert is the default switch name instead
of current switch name for the FID.
Feature:
FABRIC WATCH
Function:
Other
Probability:
High
Found in Release:
FOS7.0.1
Defect ID:
DEFECT000367477
Technical Severity:
Medium
Summary:
SSH "Allowed User" usernames are converted to all lower case when saved to the
configuration file.
Symptom:
Sshutil command will fail for the usernames containing upper case letters.
Workaround:
Run sshutil command with username converted to all lower case letters, or avoid
configuring usernames with upper case letters.
Feature:
FOS Security
Function:
SSH
Probability:
Medium
Found in Release:
FOS7.0.1