HP StorageWorks 2/140 fw 05.01.00 and sw 07.01.00 ha-fabric manager user guide - Page 189

Insistent Domain Identification (ID), Open Trunking

Page 189 highlights

Optional Features Insistent Domain Identification (ID) This is a parameter in the Configure Switch Parameters dialog box, available from Configure menu in the Product Manager application. Enabling this option sets the domain ID configured in the Preferred Domain ID field in the Configure Switch Parameters dialog box as the active domain identification when the fabric initializes. A static and unique domain identification is required by the Fabric Binding feature because the feature's Fabric Membership list identifies switches by WWN and Domain ID. If a duplicate preferred domain ID is used, then insisted, warnings occur when directors and switches are added to a Fabric Membership List. If Fabric Binding or Enterprise Fabric Mode is enabled, this option is automatically enabled and cannot be disabled unless these options are disabled when the director or switch is offline. If the director or switch is online, disabling Insistent Domain ID will disable Enterprise Fabric Mode and Fabric Binding. Open Trunking Interswitch links (ISLs) connect ports between E_Ports on Fibre Channel switches and link these switches into a multiswitch fabric. Multiple ISLs may be connected between the switches in the fabric. Data from an attached end device (server or storage) flows through these ISLs to a target end-device connected to a switch somewhere in the fabric. A data flow is data received from a specified receive port that is destined for a port in a specified target domain (switch). The list of ISLs that are candidates for being rerouted (to or from) is derived from the fibre shortest path first (FSPF) algorithm. The Open Trunking feature monitors the average data rates of all traffic flows on ISLs (from a receive port to a target domain) and periodically adjusts routing tables to reroute data flows from congested links to lightly loaded links and optimize bandwidth use. The objective of Open Trunking is to make the most efficient possible use of redundant ISLs between neighboring switches, even if these ISLs have different bandwidths. Load-balancing among the ISLs does not require user configuration, other than enabling Open Trunking. However, you can modify or "tweak" default settings for congestion thresholds (per port) and low BB_credit threshold if desired,. High Availability Fabric Manager User Guide 189

  • 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

Optional Features
189
High Availability Fabric Manager User Guide
Insistent Domain Identification (ID)
This is a parameter in the
Configure Switch Parameters
dialog box, available
from
Configure
menu in the
Product Manager
application. Enabling this option
sets the domain ID configured in the
Preferred Domain ID
field in the
Configure
Switch Parameters
dialog box as the active domain identification when the fabric
initializes. A static and unique domain identification is required by the Fabric
Binding feature because the feature's Fabric Membership list identifies switches
by WWN and Domain ID. If a duplicate preferred domain ID is used, then
insisted, warnings occur when directors and switches are added to a Fabric
Membership List.
If Fabric Binding or Enterprise Fabric Mode is enabled, this option is
automatically enabled and cannot be disabled unless these options are disabled
when the director or switch is offline. If the director or switch is online, disabling
Insistent Domain ID will disable Enterprise Fabric Mode and Fabric Binding.
Open Trunking
Interswitch links (ISLs) connect ports between E_Ports on Fibre Channel switches
and link these switches into a multiswitch fabric. Multiple ISLs may be connected
between the switches in the fabric. Data from an attached end device (server or
storage) flows through these ISLs to a target end-device connected to a switch
somewhere in the fabric. A data flow is data received from a specified receive port
that is destined for a port in a specified target domain (switch). The list of ISLs
that are candidates for being rerouted (to or from) is derived from the fibre
shortest path first (FSPF) algorithm.
The Open Trunking feature monitors the average data rates of all traffic flows on
ISLs (from a receive port to a target domain) and periodically adjusts routing
tables to reroute data flows from congested links to lightly loaded links and
optimize bandwidth use. The objective of Open Trunking is to make the most
efficient possible use of redundant ISLs between neighboring switches, even if
these ISLs have different bandwidths.
Load-balancing among the ISLs does not require user configuration, other than
enabling Open Trunking. However, you can modify or “tweak” default settings for
congestion thresholds (per port) and low BB_credit threshold if desired,.