HP StorageWorks MSA 2/8 HP StorageWorks Fabric OS Procedures V3.1.x/4.1.x User - Page 28

Con Fabric Parameters, Understanding the Core PID Requirements, Mixed Fabric Requirements

Page 28 highlights

Initial Configuration Configure Fabric Parameters Fabric Parameters include all the items listed in the configure command. Fabric Parameters (displayed using the configshow command) must be identical for each switch across a fabric. To save time when configuring the fabric parameters: 1. Configure one switch first (using the configure command) 2. Use the configUpload command to save the configuration information. See "Saving the Switch Configuration File to a Host" on page 37. 3. Use the configdownload command to download it onto each of the remaining switches. See "Restoring the System Configuration Settings" on page 55. Understanding the Core PID Requirements Core Port Identifier (PID) addressing is an option of the configure command for 2.6.0c + and 3.0.2.g+ firmware, but not 4.x firmware. However, even if you are configuring a Core Switch 2/64 or SAN Switch 2/32 switch, it is important to note this requirement if you have a fabric that mixes 4.x switches with other switches. Failing to update the Core PID addressing in non-4.x switches will result in segmentation in a mixed fabric. For detailed information regarding Core PID and related procedures, see "Procedures for Updating the Core PID Format" on page 154. For fabrics that consist of only 4.x.x firmware (Core Switch 2/64 or SAN Switch 2/32 switches), no action is required to configure the Core PID. The Core PID is enabled by default, and this parameter cannot be changed. However, other switches in your fabric will need to be Core PID-enabled if you mixing 2.x.x or 3.x.x. firmware with your 4.x.x firmware in a single fabric. Mixed Fabric Requirements To mix 2.x.x or 3.x.x switches into a fabric that contains one or more 4.x.x switches, the following is required: Minimum Firmware ■ 2.x.x firmware must be 2.6.0c or later (though 2.6.1 is strongly recommended for full functionality) ■ 3.x.x firmware must be 3.0.2g or later 28 Fabric OS Procedures Version 3.1.x/4.1.x User Guide

  • 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
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270

Initial Configuration
28
Fabric OS Procedures Version 3.1.x/4.1.x User Guide
Configure Fabric Parameters
Fabric Parameters include all the items listed in the
configure
command.
Fabric Parameters (displayed using the
configshow
command) must be
identical for each switch across a fabric.
To save time when configuring the fabric parameters:
1.
Configure one switch first (using the
configure
command)
2.
Use the
configUpload
command to save the configuration information.
See “
Saving the Switch Configuration File to a Host
” on page 37.
3.
Use the
configdownload
command to download it onto each of the
remaining switches. See “
Restoring the System Configuration Settings
” on
page 55.
Understanding the Core PID Requirements
Core Port Identifier (PID) addressing is an option of the
configure
command
for 2.6.0c + and 3.0.2.g+ firmware, but not 4.x firmware. However, even if you are
configuring a Core Switch 2/64 or SAN Switch 2/32 switch, it is important to note
this requirement if you have a fabric that mixes 4.x switches with other switches.
Failing to update the Core PID addressing in non-4.x switches will result in
segmentation in a mixed fabric.
For detailed information regarding Core PID and related procedures, see
Procedures for Updating the Core PID Format
” on page 154.
For fabrics that consist of only 4.x.x firmware (Core Switch 2/64 or SAN Switch
2/32 switches), no action is required to configure the Core PID. The Core PID is
enabled by default, and this parameter cannot be changed. However, other
switches in your fabric will need to be Core PID-enabled if you mixing 2.x.x or
3.x.x. firmware with your 4.x.x firmware in a single fabric.
Mixed Fabric Requirements
To mix 2.x.x or 3.x.x switches into a fabric that contains one or more 4.x.x
switches, the following is required:
Minimum Firmware
2.x.x firmware must be 2.6.0c or later (though 2.6.1 is strongly recommended
for full functionality)
3.x.x firmware must be 3.0.2g or later