The submodel number associated with this controller was not set at the factory or it is not supported by the controller firmware. The Recovery Guru Details area provides specific information you will need as you follow the Recovery Steps.
1
|
Use the table below and the information in the Recovery Guru Details area to determine what actions to take.
If... |
Then... |
You have a replacement controller that has the same replacement part number as the controller that is operating.
Note: Select the remaining controller in the physical view and right click, and then select the properties menu item to view the replacement part number. |
Go to step 2 to replace the incompatible controller. |
You DO NOT have a replacement controller that has the same replacement part number as the controller that is still operating. |
You need to obtain a replacement controller.
Select the Advanced >> Troubleshooting >> Support Data >> Collect menu option from the Subsystem Management Window (AMW),
and take the appropriate steps to save the support
data to a .zip file.
Contact your technical support representative and indicate that a "Controller Submodel Not Supported" problem is being reported. Send the file you saved in the previous step to your representative and wait for further instruction.
|
|
2 |
a
|
Remove the incompatible controller. The incompatible controller (A or B) is listed in the Details area. Note that there is nothing wrong with the incompatible controller and that it may be compatible with another storage subsystem. It can be used as a replacement for a controller that has the same replacement part number. |
b |
If... |
Then... |
You are using In-Band management of the storage subsystem
(refer to the Network Management Type column in the Enterprise Management Window)
|
Go to step 3. |
You are using Out-of-Band management of the storage subsystem
(refer to the Network Management Type column in the Enterprise Management Window)
|
Before you insert a new controller canister into the storage subsystem, you must update the DHCP/BOOTP server so that it will associate the new controller's hardware Ethernet (MAC) address with the DNS/network 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 (MAC) address with the new controller's Ethernet (MAC) address. The controller's Ethernet (MAC) address is located on an Ethernet ID label on the controller canister in the form xx.xx.xx.xx.xx.xx.
When you are finished, go to step 3.
|
|
|
3 |
Check the replacement part number of the remaining controller and ensure that the new controller has the same replacement part number. Select the remaining controller in the physical view and then select the Controller >> Properties menu option to view the replacement part number.
Depending on the model of your controller, the battery may be integrated inside the controller canister, rather than residing in a separate module. If the controller you are replacing contains a battery, you may have to insert the battery from the old controller canister into the new replacement controller canister. Consult your hardware documentation for details.
If you do not have a controller with the appropriate replacement part number, contact your technical support representative.
|
4 |
Make sure at least 1 minute has elapsed. Then, insert the new (compatible) controller canister firmly into place. |
5 |
Check the status of the controller in the Subsystem Management Window. The controller should have an optimal status.
|
6 |
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 Storage Subsystem >> View >> Profile menu option from the Subsystem Management Window. Then, select the 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 Advanced >> Recovery >> Redistribute Logical Drives menu option is available, 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 available (grayed out), the logical drives are already associated with their preferred controllers and no action is needed.
Go to step 7.
|
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 7.
|
|
|
|
7 |
Click the Recheck button to
rerun the Recovery Guru. The failure should no longer appear in
the Summary area. If the failure appears again, contact your
technical support representative. |