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

Closed with Code Change in Fabric OS v7.0.0a - GA June 2, 2011

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 95 highlights

Closed with Code Change in Fabric OS v7.0.0a - GA June 2, 2011 This section lists the defects with Critical, High and Medium Technical Severity closed with a code change as of June 2, 2011 in Fabric OS v7.0.0a. Defect ID: DEFECT000321855 Technical Severity: High Summary: CRC and/or CDR-5021 errors seen on DCX, DCX-4S, or 5100 switch platforms Symptom: CRC or other errors as described below: 1. Port 7/0 detected CRC error with good EOF when FC8-16 is placed in DCX-4s Slot7. For the solution to be effective, one must execute: serdestunemode --set; 2. Port 7/0, 7/10 detected CRC error when FX8-24 is placed in DCX4s slot7. May also see CRC error on corresponding core blade backend port 3/10 6/30. Solution is effective upon upgrade, hafailover or re-init of blade. 3. 5100 experience CRC error with 3rd party tape device. 4. FC10-6 in DCX detects backend port with stuck VC after link level error (CDR-5021) Feature: FC10-6 Platform Services Function: ASIC Driver Probability: Low Found in Release: FOS6.3.1 Service Request ID: 451697 Where Else Fixed: FOS7.0.0 GA Defect ID: DEFECT000345259 Technical Severity: High Summary: FC8-64 blade set to FAULTY 51 after removal/insertion of that blade in DCX 8510 chassis with diagpost on Symptom: May see a faulted blade upon insertion due to diagnostics failure. Feature: 16G Platform Services Function: FOS Kernel Drivers Probability: Medium Found in Release: FOS7.0.0 Defect ID: DEFECT000345858 Technical Severity: High Summary: FIPS firmware integrity check has gaps in coverage Symptom: None Feature: FOS-Infrastructure Function: Firmware Download Probability: Low Found in Release: FOS7.0.0 Defect ID: DEFECT000346532 Technical Severity: High Summary: Disable or shutdown BES causes the SVC nodes to go offline and service mode. Symptom: Disable or poweroff BES switch causes the SVC nodes to go offline. The SVC nodes reboot several times before it toggled between offline and services mode. Workaround: Issue affects SVC storage with BES going offline. Restart storage with VI/VT members (BES) online. Feature: FC Services Function: Name Server Probability: High Found in Release: FOS7.0.0 Fabric OS v7.0.1b Release Notes v1.0 Page 95 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
Fabric OS v7.0.1b Release Notes v1.0
Page 95 of 99
Closed with Code Change in Fabric OS v7.0.0a – GA June 2, 2011
This section lists the defects with Critical, High and Medium Technical Severity closed with a code change as of
June 2, 2011 in Fabric OS v7.0.0a.
Defect ID:
DEFECT000321855
Technical Severity:
High
Summary:
CRC and/or CDR-5021 errors seen on DCX, DCX-4S, or 5100 switch platforms
Symptom:
CRC or other errors as described below: 1. Port 7/0 detected CRC error with good EOF
when FC8-16 is placed in DCX-4s Slot7. For the solution to be effective, one must execute:
serdestunemode --set; 2. Port 7/0, 7/10 detected CRC error when FX8-24 is placed in DCX-
4s slot7. May also see CRC error on corresponding core blade backend port 3/10 6/30.
Solution is effective upon upgrade, hafailover or re-init of blade. 3. 5100 experience CRC
error with 3rd party tape device. 4. FC10-6 in DCX detects backend port with stuck VC after
link level error (CDR-5021)
Feature:
FC10-6 Platform Services
Function:
ASIC Driver
Probability:
Low
Found in Release:
FOS6.3.1
Service Request ID:
451697
Where Else Fixed:
FOS7.0.0 GA
Defect ID:
DEFECT000345259
Technical Severity:
High
Summary:
FC8-64 blade set to FAULTY 51 after removal/insertion of that blade in DCX 8510 chassis
with diagpost on
Symptom:
May see a faulted blade upon insertion due to diagnostics failure.
Feature:
16G Platform Services
Function:
FOS Kernel Drivers
Probability:
Medium
Found in Release:
FOS7.0.0
Defect ID:
DEFECT000345858
Technical Severity:
High
Summary:
FIPS firmware integrity check has gaps in coverage
Symptom:
None
Feature:
FOS-Infrastructure
Function:
Firmware Download
Probability:
Low
Found in Release:
FOS7.0.0
Defect ID:
DEFECT000346532
Technical Severity:
High
Summary:
Disable or shutdown BES causes the SVC nodes to go offline and service mode.
Symptom:
Disable or poweroff BES switch causes the SVC nodes to go offline. The SVC nodes reboot
several times before it toggled between offline and services mode.
Workaround:
Issue affects SVC storage with BES going offline. Restart storage with VI/VT members
(BES) online.
Feature:
FC Services
Function:
Name Server
Probability:
High
Found in Release:
FOS7.0.0