HP Surestore 64 Planning Guide - Page 121

Task 15: Plan a Multiswitch Fabric (Optional), If heavy traffic between devices is expected

Page 121 highlights

Configuration Planning Tasks Task 15: Plan a Multiswitch Fabric (Optional) If a multiswitch fabric topology is to be implemented, carefully plan the physical characteristics and performance objectives of the topology, including the proposed number of directors (or other elements) in the fabric, characteristics of attached devices, cost, nondisruptive growth requirements, and service requirements. When two or more directors are connected through ISLs to form a fabric, the directors 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. The following factors should be considered when planning for a multiswitch fabric: • Fabric topology limits Consider the practical number of director fabric elements (maximum of 31), number of ISLs per element (maximum of 32), hop count (two), and distance limitations (limited by port type and cable availability). • Bandwidth Consider using multiple ISLs to increase the total bandwidth available between two directors. • 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 director 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 and not a fabric. Planning and implementing a multiswitch fabric is a complex and difficult task. Consult your local HP sales office for the latest configuration information. Task 15: Plan a Multiswitch Fabric (Optional) 107

  • 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

Task 15: Plan a Multiswitch Fabric (Optional)
107
Configuration Planning
Tasks
Task 15: Plan a Multiswitch Fabric (Optional)
If a multiswitch fabric topology is to be implemented, carefully plan the physical
characteristics and performance objectives of the topology, including the proposed
number of directors (or other elements) in the fabric, characteristics of attached devices,
cost, nondisruptive growth requirements, and service requirements.
When two or more directors are connected through ISLs to form a fabric, the directors
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. The following factors should
be considered when planning for a multiswitch fabric:
Fabric topology limits
Consider the practical number of director fabric elements (maximum of 31), number of
ISLs per element (maximum of 32), hop count (two), and distance limitations (limited
by port type and cable availability).
Bandwidth
Consider using multiple ISLs to increase the total bandwidth available between two
directors.
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 director 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 and not a fabric.
Planning and implementing a multiswitch fabric is a complex and difficult task. Consult
your local HP sales office for the latest configuration information.