HP Surestore 64 FW 05.01.00 and SW 07.01.00 HP StorageWorks SAN High Availabil - Page 165

Task 15: Plan a Multi-Switch Fabric (Optional), Fabric topology limits, Bandwidth, Load balancing

Page 165 highlights

Configuration Planning Tasks Task 15: Plan a Multi-Switch Fabric (Optional) If a multi-switch fabric topology is to be implemented, carefully plan the physical characteristics and performance objectives of the topology. Include the proposed number of fabric elements, characteristics of attached devices, cost, nondisruptive growth requirements, and service requirements. When two or more fabric elements are connected through ISLs to form a fabric, the elements must have compatible operating parameters, compatible name server zoning configurations, and unique domain identifications (IDs). Planning for a fabric must be carefully coordinated with planning for zoned configurations. Consider the following factors when planning for a multi-switch fabric: ■ Fabric topology limits - Consider the practical number of fabric elements (theoretical maximum of 31, practical limit of 24), number of ISLs per element, hop count (maximum of 3), and distance limitations (limited by port type and cable availability). ■ Bandwidth - Consider using multiple ISLs to increase the total bandwidth available between two fabric elements. ■ Load balancing - If heavy traffic between devices is expected, consider installing multiple ISLs to create multiple minimum-hop paths for load balancing ■ Principal switch selection - If required, plan which fabric element is to be assigned principal switch duties for the fabric. ■ Critical operations - Consider routing paths that transfer data for critical operations directly through one director or switch and not through the fabric. Planning and implementing a multi-switch fabric is a complex and difficult task. HP recommends you obtain planning assistance from our professional services organization before implementing a fabric topology. SAN High Availability Planning Guide 165

  • 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

Configuration Planning Tasks
165
SAN High Availability Planning Guide
Task 15: Plan a Multi-Switch Fabric (Optional)
If a multi-switch fabric topology is to be implemented, carefully plan the physical
characteristics and performance objectives of the topology. Include the proposed
number of fabric elements, characteristics of attached devices, cost, nondisruptive
growth requirements, and service requirements.
When two or more fabric elements are connected through ISLs to form a fabric,
the elements must have compatible operating parameters, compatible name server
zoning configurations, and unique domain identifications (IDs). Planning for a
fabric must be carefully coordinated with planning for zoned configurations.
Consider the following factors when planning for a multi-switch fabric:
Fabric topology limits
— Consider the practical number of fabric elements
(theoretical maximum of 31, practical limit of 24), number of ISLs per
element, hop count (maximum of 3), and distance limitations (limited by port
type and cable availability).
Bandwidth
— Consider using multiple ISLs to increase the total bandwidth
available between two fabric elements.
Load balancing
— If heavy traffic between devices is expected, consider
installing multiple ISLs to create multiple minimum-hop paths for load
balancing
Principal switch selection
— If required, plan which fabric element is to be
assigned principal switch duties for the fabric.
Critical operations
— Consider routing paths that transfer data for critical
operations directly through one director or switch and not through the fabric.
Planning and implementing a multi-switch fabric is a complex and difficult task.
HP recommends you obtain planning assistance from our professional services
organization before implementing a fabric topology.