Dell Brocade 5100 Fabric OS v7.0.2 Release Notes v1.0 - Page 61

Fabric Services

Get Dell Brocade 5100 PDF manuals and user guides View all Dell Brocade 5100 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 61 highlights

Close with Code Change in Fabric OS v7.0.1a Defect ID: DEFECT000381334 Technical Severity: Medium Summary: Portloopbacktest clean up for 16G blades Symptom: Cleanup portloopbacktest issues: portloopbacktest -nframes option does not work properly on 16G platforms Portloopbacktest actually gets skipped on 16G in slot3 and above Default number of frames for portloopbacktest on 16G in man page is incorrect Mode 1 portloopbacktest fails on FC16 blades in either slot 7 or 8 of 8510-4 Incorrect diagstatus outputs "dummytest" and not "portloopbacktest Feature: Field Escalation Function: Diagnostics Probability: High Found in Release: FOS7.0.0 Service Request ID: 679251 Defect ID: DEFECT000381459 Technical Severity: Medium Summary: FCIP FastWrite: SRDF cannot handle busy response to commands Symptom: Customer getting data corruption on SRDF replication with FCIP FastWrite enabled. Finisar traces show busy status being returned after SCSI command, SRDF does not understand busy status and thinks busy = good status. Workaround: Disable emulation Feature: Field Escalation Function: FCIP Probability: Medium Found in Release: FOS6.4.1 Service Request ID: 694909 Defect ID: DEFECT000382643 Technical Severity: Medium Summary: CP panicked during core blade reseat Symptom: During core blade replacement, race condition caused a removed blade object being access by routing module. Customer observed unintended Hafailover. Feature: Field Escalation Function: Fabric Services Probability: Medium Found in Release: FOS6.4.1 Service Request ID: 695027 Defect ID: DEFECT000385058 Technical Severity: Medium Summary: POST failure with FOS 16G blade with misleading test name Symptom: 16G blade fails turboramtest as "fcbistest", when chassis is power cycled due to not properly initialized data structure. FOS turboramtest command line does not fail, reboot does not fail, slot power on/off does not fail. Misleading error message and test name is cleaned up Feature: Diagnostics Function: Post Diags Probability: Low Found in Release: FOS7.0.0 Service Request ID: NA Fabric OS v7.0.2 Release Notes v1.0 Page 61 of 99

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
Close with Code Change in Fabric OS v7.0.1a
Fabric OS v7.0.2 Release Notes v1.0
Page 61 of 99
Defect ID:
DEFECT000381334
Technical Severity:
Medium
Summary:
Portloopbacktest clean up for 16G blades
Symptom:
Cleanup portloopbacktest issues:
portloopbacktest -nframes option does not work properly on 16G platforms
Portloopbacktest actually gets skipped on 16G in slot3 and above
Default number of frames for portloopbacktest on 16G in man page is incorrect
Mode 1 portloopbacktest fails on FC16 blades in either slot 7 or 8 of 8510-4
Incorrect diagstatus outputs "dummytest" and not "portloopbacktest
Feature:
Field Escalation
Function:
Diagnostics
Probability:
High
Found in Release:
FOS7.0.0
Service Request ID:
679251
Defect ID:
DEFECT000381459
Technical Severity:
Medium
Summary:
FCIP FastWrite: SRDF cannot handle busy response to commands
Symptom:
Customer getting data corruption on SRDF replication with FCIP FastWrite enabled.
Finisar
traces show busy status being returned after SCSI command, SRDF does not understand
busy status and thinks busy = good status.
Workaround:
Disable emulation
Feature:
Field Escalation
Function:
FCIP
Probability:
Medium
Found in Release:
FOS6.4.1
Service Request ID:
694909
Defect ID:
DEFECT000382643
Technical Severity:
Medium
Summary:
CP panicked during core blade reseat
Symptom:
During core blade replacement,
race condition caused a removed blade object being
access by routing module.
Customer observed unintended Hafailover.
Feature:
Field Escalation
Function:
Fabric Services
Probability:
Medium
Found in Release:
FOS6.4.1
Service Request ID:
695027
Defect ID:
DEFECT000385058
Technical Severity:
Medium
Summary:
POST failure with FOS 16G blade with misleading test name
Symptom:
16G blade fails turboramtest as “fcbistest”, when chassis is power cycled due to not
properly initialized data structure. FOS turboramtest command line does not fail, reboot
does not fail, slot power on/off does not fail. Misleading error message and test name is
cleaned up
Feature:
Diagnostics
Function:
Post Diags
Probability:
Low
Found in Release:
FOS7.0.0
Service Request ID:
NA