P55A接FastT200，换电池后报错（高手指点）

FastT200 B控制器电池失效，更换电池后，将控制器online，然后手动将array移回控制器b，报错；将电池日期清零，也报同样的错，具体报错那图我不方便截图。

整个fastT的听诊器的报错是：Logical Drive Not On Preferred Path
What Caused the Problem?
There is a problem accessing the controller listed in the Recovery Guru Details Area. Any logical drives that have this controller assigned as their preferred path will be moved to the non-preferred path (alternate controller). This procedure will help you pinpoint the problem along the data path. Because the logical drives will be moved to the alternate controller, they should still be accessible. Therefore, no action is required on the individual logical drives.
Possible causes include:
The controller failed a manually initiated diagnostic test and was placed Offline.
The controller was manually placed Offline using the Controller>>Place>>Offline menu option.
There are disconnected or faulty cables.
A Hub or Fabric switch is not functioning properly.
A host adapter has failed.
The storage subsystem contains a defective RAID controller.
The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Caution Do not replace the controller until you are instructed to do so. This procedure will instruct you to check the components along the connection, check the host adapters, and eventually instruct you to replace the controller, if necessary.
Caution  Electrostatic discharge can damage sensitive components. Use a grounding wrist strap or other anti-static precautions before removing or handling components.
Important Notes
When Auto Logical Drive Transfer (ADT) is enabled, it can take several minutes for the host-based, multi-path failover driver to recognize a restored or modified preferred path (use the Storage Subsystem Profile to determine whether you have ADT?enabled on a mapped host; see Step 9 below). A Logical Drive Not On Preferred Path error will be reported during this time. If you have recently modified the preferred path using the Array>>Change>>Ownership/Preferred Path or Logical Drive>>Change>>Ownership/Preferred Path menu options or performed a recovery procedure that has restored a preferred path, wait at least 10 minutes and run the Recovery Guru again using the Recheck button. If this error is reported again, perform the recovery procedures listed below.
If the controllers for this storage subsystem are located in an enclosure containing both controllers and drives, you may have to insert the battery from the old controller canister into the new replacement controller canister. Consult the following steps and your hardware documentation for details.
Recovery Steps
1
If...
Then...
The controller was manually placed Offline
Place the controller back Online by highlighting the controller in the Physical View of the Subsystem Management Window and selecting Controller>>Place>>Online.
Go to Step 9.
The controller was NOT manually placed Offline
Go to Step 2.
2
Check the following components on both ends of the connection for loose connections or visible damage:
External cables
Hubs and switches
If...
Then...
The connection components are OK
Go to Step 3.
There is a problem with the connection
Fix the connection problem. Then, go to Step 8.
3
Use the information in the following table to determine the action to take.
If...
Then...
The host connected to this storage subsystem is NOT connected to any other storage subsystems
Verify that its host adapter is operational.
If the host adapter is operational, the controller in the storage subsystem is probably defective. Go to Step 4.
If the host adapter is defective, correct the problem, then go to Step 8.
The host connected to this storage subsystem is connected to other storage subsystems
Check the Enterprise Management Window for storage subsystems showing a Needs Attention status.
If one or more storage subsystems connected to this host/host adapter does not have a Needs Attention status, then the controller in the storage subsystem is probably defective. Go to Step 4.
If every storage subsystem connected to this host/host adapter has a Needs Attention status, then the associated host adapter is probably defective. Fix the host adapter problem, then go to Step 8.
4
Remove the defective controller. The defective controller (A or B) is listed in the Recovery Guru Details area.
Note: Before you insert a new controller canister into a Directly Managed Storage Subsystem (refer to the Network Management Type column in the Enterprise Management Window), you must update the DHCP/BOOTP server so that it will associate the new controller's hardware Ethernet address with the host name and IP address previously assigned to the removed controller.
To update the DHCP/BOOTP server, find the entry associated with the removed controller and replace its Ethernet address with the new controller's Ethernet address. The controller's Ethernet address is located on an Ethernet ID label on the controller canister in the form xx.xx.xx.xx.xx.xx. If you need more details, consult the Storage System Planning Guide.
5
If...
Then...
The controllers for this storage subsystem are located in an enclosure containing both controllers and drives
Check to see if the new controller canister contains a battery.
If there is not a battery installed, then install the battery from the old canister and go to Step 6.
If there is a battery installed, then go to Step 6.
The controllers for this storage subsystem are located in an enclosure containing only controllers
Go to Step 6.
6
Make sure at least 1 minute has elapsed. Then, insert the new controller canister firmly into place.
Note the controller slot (A or B) of the affected controller listed in the Recovery Guru Details area. Highlight this controller slot in the Physical View of the Subsystem Management Window.
If...
Then...
The controller indicates that it is Active/Optimal
Go to Step 7.
The controller indicates that is Offline
Select Controller>>Place>>Online and then go to Step 7.
7
If...
Then...
The controllers for this storage subsystem are located in an enclosure containing both controllers and drives
Determine whether you need to reset the battery age.
If you installed the battery from the old canister, then you don't need to reset the battery age. Go to Step 9.
If there was already a battery in the new replacement controller canister, then you must reset the battery age using the following procedure:
Select the Components button  on the enclosure containing the controllers in the Physical View of the Subsystem Management Window. Highlight the Batteries option and select the Reset button associated with the new controller canister (A or B). Then, go to Step 9.
The controllers for this storage subsystem are located in an enclosure containing only controllers
Go to Step 9.
8
Note the controller slot (A or B) of the affected controller listed in the Recovery Guru Details area. Highlight this controller slot in the Physical View of the Subsystem Management Window.
If...
Then...
The controller indicates that it is Active/Optimal
Go to Step 9.
The controller indicates that is Offline
Select Controller>>Place>>Online and then go to step 9.
9
If you have logical drives mapped to hosts that have Automatic Logical Drive Transfer (ADT) disabled, it may be necessary to redistribute the logical drives to their preferred controller. Use the following steps to determine the ADT status of the hosts connected to your storage subsystem:
a
Open the Storage Subsystem Profile by selecting the View>>Storage Subsystem Profile menu option from the Subsystem Management Window. Then, select the profile's Mappings tab.
b
Scroll to the NVSRAM Host Type Internal Definitions section.
c
If...
Then...
There are hosts mapped to logical drives on this storage subsystem that have an ADT status of disabled
OR
There are hosts mapped to logical drives on this storage subsystem that are not running a host-based, multi-path failover driver
It may be necessary to redistribute the logical drives to their preferred controller. If the Subsystem Management Window's Storage Subsystem>>Redistribute Logical Drives menu option is visible, select the option.
Note: If you have a mix of hosts with ADT enabled and ADT disabled, all logical drives will be immediately assigned back to their preferred path. However, until the host-based, multi-path failover driver detects the valid preferred path (may take several minutes), the logical drives mapped to the ADT-enabled hosts may get temporarily returned back to the non-preferred path.
If the menu option is not visible, the logical drives are already associated with their preferred controllers and no action is needed.
Go to Step 10.
There are NO hosts mapped to logical drives on this storage subsystem with an ADT status of disabled
AND
All hosts mapped to logical drives on this storage subsystem are running a host-based, multi-path failover driver
No action is required.
If logical drives need to be redistributed to their preferred controller, the host-based, multi-path failover driver will automatically initiate the transfer.
Note that detection of a restored preferred path by the multi-path failover driver can take several minutes.
Go to Step 10.
10
Select Recheck to rerun the Recovery Guru to ensure that the failure has been fixed.
If...
Then...
Another type of failure is reported
Follow the recovery procedures given for that failure.
No failures are reported
You are finished with the recovery procedure.
Note: If you replaced the controller and the file systems/logical drives do not respond, reboot your

******************************************************************************************

sm里看，控制器B是online的，状态也是active的，其他电源风扇状态都是好的，换过的电池状态也正常了，连线也没动过，就是切不回去
array只有1个，里面有两个logic disk，其中disk1从一台主机可以看到，应用也启动了，还有个logic disk没被主机识别到，应用也启动不了，由于是双机，另一台机器倒是能能看到logic disk2，于是从另一台机器启动了应用。
我点了redistribute logical dirves也没用。

FastT200
Firmware version: PkgInfo 04.01.02.30
NVSRAM version: NV3542R710NT012m
ADT状态是 enable的，prefer 的控制器是B，是不是要等控制器插回去，电池充电完成，然后将其online，要等一会儿，让系统自动将array移回控制器B，才能启动业务？！？！

我的SM装的是 V09.23.G5.01，连上FastT200后，看不到mappings view那一栏，这是怎么回事？！

顺便问一下，是不是要停了HA以后，array会自动回到prefer的控制器（B）上？如果想关闭ADT的话，如何关闭？

[[i] 本帖最后由 stevestifler 于 2008-6-12 10:19 编辑 [/i]]

看不到mappings view，是因为SM的版本太高了，控制器的微码太低了，你要不找个低版本的sm，或者升级微码试试

200也太老了，微码够老。
PATH有问题，仔细检查吧。
怀疑你的拓扑设计本身就有问题

PATH与初设置时的PATH不一致引起的