HP AM866A Brocade Troubleshooting and Diagnostics Guide v6.1.0 (53-1000853-01, - Page 98

Fabric OS Administrator's Guide, TABLE 16

Get HP AM866A - StorageWorks 8/8 Base SAN Switch PDF manuals and user guides
UPC - 884420064602
View all HP AM866A manuals
Add to My Manuals
Save this manual to your list of manuals

Page 98 highlights

10 Troubleshooting FICON CUP Symptom Mainframe RMF utility fails to capture performance data Probable cause and recommended action On Fabric OS v6.0.0, Brocade SilkWorm switches do not fully implement all of CUP commands needed to collect all of performance data on switch. Upgrade your switch to Fabric OS v6.1.0, where the performance data is captured. Symptom Switch panic when a firmware upgrade from v5.0.1d to v5.1.0c occurred. Probable cause and recommended action Switches may have the following settings: route.delayReroute:0==> iodReset route.stickyRoutes:0==> dlsSet Aptpolicy:1 ==> port-based routing Fabric OS v5.1.x introduced a new flag during route calculation. After an upgrade from Fabric OS v5.0.x to v5.1.x, a new active CP running Fabric OS v5.1.x uses the old method of calculating the route rather than using the new flag. This causes a route miscalculation and the switch panics. This issues is fixed in Fabric OS v5.2.1 and v5.3.0 The following will appear in the message logs: MSR: 00029030 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 1/1 TASK = c0f28000[658] 'RTEK_TH' Last syscall: -1 ASSERT - Failed expression: !old_path, file = rte_path.c, line = 1366, kernel mode Follow the routing guidelines in Table 16 to avoid this issue. Avoid the combination of port-based routing (external = 1, internal = 2) with DLS on in a FICON fsmode enabled setup. DLS off is recommended for a FICON environment. TABLE 16 Tested scenarios for panic or no panic Routing type IOD setting DLS setting Port-based Off On (external = 1, internal = 2) Port-based On On (external = 1, internal = 2) Port-based On Off (external = 1, internal = 2) Port-based Off Off (external = 1, internal = 2) Device-based Off n/a (external = 3, internal = 3) Device-based On n/a (external = 3, internal = 3) Result Panic Panic No panic No panic No panic No panic NOTE You have to configure the switches according to the Fabric OS Administrator's Guide. 84 Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-01

  • 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
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
84
Fabric OS Troubleshooting and Diagnostics Guide
53-1000853-01
Troubleshooting FICON CUP
10
Symptom
Mainframe RMF utility fails to capture performance data
Probable cause and recommended action
On Fabric OS v6.0.0, Brocade SilkWorm switches do not fully implement all of CUP commands
needed to collect all of performance data on switch. Upgrade your switch to Fabric OS v6.1.0,
where the performance data is captured.
Symptom
Switch panic when a firmware upgrade from v5.0.1d to v5.1.0c occurred.
Probable cause and recommended action
Switches may have the following settings:
route.delayReroute:0==> iodReset
route.stickyRoutes:0==> dlsSet
Aptpolicy:1
==> port-based routing
Fabric OS v5.1.x introduced a new flag during route calculation. After an upgrade from Fabric OS
v5.0.x to v5.1.x, a new active CP running Fabric OS v5.1.x uses the old method of calculating the
route rather than using the new flag. This causes a route miscalculation and the switch panics. This
issues is fixed in Fabric OS v5.2.1 and v5.3.0
The following will appear in the message logs:
MSR: 00029030 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 1/1
TASK = c0f28000[658] 'RTEK_TH' Last syscall: -1
ASSERT - Failed expression: !old_path,
file = rte_path.c, line = 1366, kernel mode
Follow the routing guidelines in
Table 16
to avoid this issue. Avoid the combination of port-based
routing (external = 1, internal = 2) with DLS on in a FICON fsmode enabled setup. DLS off is
recommended for a FICON environment.
NOTE
You have to configure the switches according to the
Fabric OS Administrator’s Guide
.
TABLE 16
Tested scenarios for panic or no panic
Routing type
IOD setting
DLS setting
Result
Port-based
(external = 1, internal = 2)
Off
On
Panic
Port-based
(external = 1, internal = 2)
On
On
Panic
Port-based
(external = 1, internal = 2)
On
Off
No panic
Port-based
(external = 1, internal = 2)
Off
Off
No panic
Device-based
(external = 3, internal = 3)
Off
n/a
No panic
Device-based
(external = 3, internal = 3)
On
n/a
No panic