Adaptec 412R User Guide - Page 110

should not change these ID settings., SCSI Initiator IDs 6 and 7 on each of the disk channels.

Page 110 highlights

DuraStor 412R/6320SS/7320SS Installation and User's Guide Arrays can only be accessed by the controller that currently owns them. One controller will have no visibility to the others' arrays. If one controller fails, the surviving controller will take ownership of all arrays. Pool spares and unassigned disks are visible to both controllers. The two controllers communicate via the back-end disk buses. Although many different message types are sent between the two controllers, the majority of the data is write cache data. In the default write-back caching mode, any data that the host writes to one controller is copied to the other controller before a good status is returned to the host. By mirroring the data, if a controller fails, the surviving controller will have a copy of all data that has not been written to the disk. Warning: The controllers communicate with each other using SCSI Initiator IDs 6 and 7 on each of the disk channels. You should not change these ID settings. Each controller sends heartbeat messages to its partner controller. If a controller does not receive a heartbeat message within a set time period, it will kill the other controller assuming that it has malfunctioned. After killing the other controller, it will take ownership of the arrays and will activate its passive host port to assume the defunct controller's identity. A-8

  • 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

A-8
DuraStor 412R/6320SS/7320SS Installation and User’s Guide
Arrays can only be accessed by the controller that currently owns
them. One controller will have no visibility to the others’ arrays. If
one controller fails, the surviving controller will take ownership of
all arrays. Pool spares and unassigned disks are visible to both
controllers.
The two controllers communicate via the back-end disk buses.
Although many different message types are sent between the two
controllers, the majority of the data is write cache data. In the
default write-back caching mode, any data that the host writes to
one controller is copied to the other controller before a good status
is returned to the host. By mirroring the data, if a controller fails,
the surviving controller will have a copy of all data that has not
been written to the disk.
Warning:
The controllers communicate with each other using
SCSI Initiator IDs 6 and 7 on each of the disk channels. You
should not change these ID settings.
Each controller sends heartbeat messages to its partner controller.
If a controller does not receive a heartbeat message within a set
time period, it will kill the other controller assuming that it has
malfunctioned.
After killing the other controller, it will take ownership of the
arrays and will activate its passive host port to assume the defunct
controller’s identity.