Adaptec 1966600 User Guide - Page 71

be done with the Disk Array Administrator Other Controller

Get Adaptec 1966600 - DuraStor 7220SS Hard Drive Array PDF manuals and user guides
UPC - 760884139202
View all Adaptec 1966600 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 71 highlights

Installing the DuraStor Storage Subsystem ! Caution: When in active-active mode, the two controllers communicate with each other using SCSI initiator IDs 6 and 7 on the disk channels. The values of 6 and 7 are mandatory defaults to guarantee good communication between the two controllers, and you cannot change them. Do not configure any other devices to IDs 6 and 7 on the disk channels, or the active-active configuration will fail to operate. Each controller also sends heartbeat messages to its partner controller. If a controller does not receive a heartbeat message within a set timeout 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. In this failed-over configuration, the controller will present its native identity on one host port, and the failed-over controller's identity on its other host port. The controller's host interface impersonates the other's World Wide Name (WWN) Identifier and other identifiers as appropriate to the current Fibre Channel topology. The arrays native to the controller are presented on the controller's native host port, and the arrays for the failed-over controller are presented on the other host port. This is different from the dual-port configuration where each array is presented on both host ports. After the controller has failed over, you can replace the failed controller with a new controller, assuming the enclosure allows hot plugging. The arrays will fail back to the new controller without intervention. If you want to retry the failed controller, it is necessary to release the kill line that the survivor asserts. This can be done with the Disk Array Administrator (Other Controller Menu, Unkill Other menu option). You can kill the other controller with the Kill Other menu option. 3-37

  • 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
3-37
Installing the DuraStor Storage Subsystem
Caution:
When in active-active mode, the two controllers
communicate with each other using SCSI initiator IDs 6
and 7 on the disk channels. The values of 6 and 7 are
mandatory defaults to guarantee good communication
between the two controllers, and you cannot change them.
Do not configure any other devices to IDs 6 and 7 on the
disk channels, or the active-active configuration will fail to
operate.
Each controller also sends heartbeat messages to its partner
controller. If a controller does not receive a heartbeat message
within a set timeout 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.
In this failed-over configuration, the controller will present its
native identity on one host port, and the failed-over controller’s
identity on its other host port. The controller’s host interface
impersonates the other’s World Wide Name (WWN) Identifier and
other identifiers as appropriate to the current Fibre Channel
topology. The arrays native to the controller are presented on the
controller’s native host port, and the arrays for the failed-over
controller are presented on the other host port. This is different
from the dual-port configuration where each array is presented on
both host ports.
After the controller has failed over, you can replace the failed
controller with a new controller, assuming the enclosure allows hot
plugging. The arrays will fail back to the new controller without
intervention. If you want to retry the failed controller, it is
necessary to release the kill line that the survivor asserts. This can
be done with the Disk Array Administrator (Other Controller
Menu, Unkill Other menu option). You can kill the other controller
with the Kill Other menu option.
!