HP NetServer AA 4000 HP Netserver AA Solution Administrator's Guide v - Page 26

Endurance Server Hardware Configuration, IL IOP Link cable connects IOP1 and IOP2.

Page 26 highlights

Endurance Server Hardware Configuration With four systems integrated into a single Windows fault tolerant server, as shown in Figure 1-1, the Endurance server provides complete hardware redundancy. Because the Endurance server uses redundant hardware, its hardware availability far surpasses that of a standard Windows server. Using redundant hardware also allows online service and replacement of Endurance hardware. The Endurance server supports multiple network connections to provide additional network redundancy and network traffic control. Each system in the Endurance server (Figure 1-2) performs specific tasks, functioning as either a CE or IOP: • CE (Compute Element) contains the server CPU(s) and memory that supports a standard Windows operating system and applications. Because there are two CEs, the CEs provide the redundant CPU(s) and memory for the Endurance server. • IOPs (I/O Processors) contain the keyboard and mouse, mirrored SCSI devices, redundant network adapters, and other I/O devices. Because there are two IOPs, the mirrored SCSI devices (one on each IOP) provide fault tolerant data storage, and the redundant network adapters (one on each IOP) provide redundant network connectivity. The IOPs handle all Endurance server I/O requests. The Endurance server uses MICs and the IL to interconnect four standard systems into the server configuration. This enables these systems to function as one server: • MIC (Marathon Interface Card) is an adapter that provides a high speed interconnect path for the Endurance server. There are four MICs in an Endurance server: one in each IOP, and one in each CE. • IL (IOP Link) cable connects IOP1 and IOP2. By using redundant hardware, HP is also able to implement SplitSite technology in your server. SplitSite enables you to locate each tuple of an Endurance server residing in different locations. This provides a method of offsite data protection while also providing protection from potential site disasters. 1-8 HP Netserver AA Solution Administrator's 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
  • 271
  • 272

1-8
HP Netserver AA Solution Administrator°s Guide
Endurance Server Hardware Configuration
With four systems integrated into a single Windows fault tolerant server, as shown in
Figure 1-1
, the Endurance server provides complete hardware redundancy. Because the
Endurance server uses redundant hardware, its hardware availability far surpasses that of a
standard Windows server. Using redundant hardware also allows online service and
replacement of Endurance hardware. The Endurance server supports multiple network
connections to provide additional network redundancy and network traffic control.
Each system in the Endurance server (
Figure 1-2
) performs specific tasks, functioning as either
a CE or IOP:
°
CE (Compute Element) contains the server CPU(s) and memory that supports a standard
Windows operating system and applications. Because there are two CEs, the CEs provide
the redundant CPU(s) and memory for the Endurance server.
°
IOPs (I/O Processors) contain the keyboard and mouse, mirrored SCSI devices, redundant
network adapters, and other I/O devices. Because there are two IOPs, the mirrored SCSI
devices (one on each IOP) provide fault tolerant data storage, and the redundant network
adapters (one on each IOP) provide redundant network connectivity. The IOPs handle all
Endurance server I/O requests.
The Endurance server uses MICs
and the IL to interconnect four standard systems into the
server configuration. This enables these systems to function as one server:
°
MIC (Marathon Interface Card) is an adapter that provides a high speed interconnect path
for the Endurance server. There are four MICs in an Endurance server: one in each IOP,
and one in each CE.
°
IL (IOP Link) cable connects IOP1 and IOP2.
By using redundant hardware, HP is also able to implement SplitSite technology in your server.
SplitSite enables you to locate each tuple of an Endurance server residing in different locations.
This provides a method of offsite data protection while also providing protection from potential
site disasters.