IBM SAS RAID controllers, Руководство пользователя

Страница: 36 / 82

Storage IOA configuration marked as Yes. The IBM i software levels that are required for multi-initiator
support are identified in the Controller software verification topic.
Controllers connected in a dual storage IOA configuration must have the same write cache size (assuming
that they support write cache). A configuration error is logged if the write caches for the controllers are
not the same size.
When you configure a controller for a dual storage IOA configuration, no mode jumpers or special
configuration settings are needed.
For all dual storage IOA configurations, one controller functions as the primary controller. Primary
controllers perform management of the physical devices, such as creating a disk array. The other
controller functions as the secondary controller and is not capable of physical device management.
If the secondary controller detects that the primary controller is going offline, it switches roles to become
the primary controller. When the original primary controller comes back online, it becomes the secondary
controller.
Both controllers are capable of performing direct I/O accesses (read and write operations) to the disk
arrays. At any given time, only one controller in the pair is optimized for the disk array. The controller
optimized for a disk array is the one that directly accesses the physical devices for I/O operations. The
controller that is not optimized for a disk array forwards read and write requests, through the SAS fabric,
to the optimized controller.
The primary controller logs most errors that are related to problems with a disk array. Disk array errors
might also be logged on the secondary controller if a disk array is optimized on the secondary controller
at the time the error occurred.
Typical reasons for the primary and secondary controllers to switch roles from what was expected are as
follows:
v
Controllers switch roles for asymmetric reasons. For example, one controller detects more disk drives
than the other. If the secondary controller is able to find devices that are not found by the primary
controller, an automatic transition (failover) occurs. The controllers communicate with each other,
compare device information, and switch roles.
v Powering off the primary controller causes an automatic transition (failover) to occur.
v
Failure of the primary controller causes an automatic transition (failover) to occur.
v
If the primary controller loses contact with the disks that are also accessible by the secondary
controller, an automatic transition (failover) occurs.
v
Downloading controller microcode might cause an automatic transition (failover) to occur.
Related concepts :
“Verifying the controller software” on page 19
Verify the minimum software support that is required for your specific controller.
“PCI-X SAS RAID card comparison” on page 2
Use the table in this topic to compare the features of the various PCI-X SAS RAID cards for IBM i. There
are also images of adapters for you to view.
“PCIe SAS RAID card comparison” on page 5
Use the tables in this topic to compare the features of the various PCI Express (PCIe) SAS RAID cards for
IBM i. There are also images of adapters for you to view.
“Dual storage IOA access optimization” on page 28
View the active or passive path of your disk units and controller.
24
SAS RAID controllers for IBM i