The submodel number associated with this RAID controller module was not set at the factory or it is not supported by the RAID controller module 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 RAID controller module that has the same replacement part number as the RAID controller module that is operating.
Note: Select the remaining RAID controller module 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 RAID controller module. |
| You DO NOT have a replacement RAID controller module that has the same replacement part number as the RAID controller module that is still operating. |
You need to obtain a replacement RAID controller module.
Select the Advanced >> Troubleshooting >> Support Data >> Collect menu option from the Array 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 "RAID Controller Module 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 RAID controller module. The incompatible RAID controller module (A or B) is listed in the Details area. Note that there is nothing wrong with the incompatible RAID controller module and that it may be compatible with another storage array. It can be used as a replacement for a RAID controller module that has the same replacement part number. |
|
b |
| If... |
Then... |
| You are using In-Band management of the storage array
(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 array
(refer to the Network Management Type column in the Enterprise Management Window)
|
Before you insert a new RAID controller module module into the storage array, you must update the DHCP/BOOTP server so that it will associate the new RAID controller module's hardware Ethernet (MAC) address with the DNS/network name and IP address previously assigned to the removed RAID controller module.
To update the DHCP/BOOTP server, find the entry associated with the removed RAID controller module and replace its Ethernet (MAC) address with the new RAID controller module's Ethernet (MAC) address. The RAID controller module's Ethernet (MAC) address is located on an Ethernet ID label on the RAID controller module module 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 RAID controller module and ensure that the new RAID controller module has the same replacement part number. Select the remaining RAID controller module in the physical view and then select the RAID Controller Module >> Properties menu option to view the replacement part number.
Depending on the model of your RAID controller module, the battery may be integrated inside the RAID controller module module, rather than residing in a separate module. If the RAID controller module you are replacing contains a battery, you may have to insert the battery from the old RAID controller module module into the new replacement RAID controller module module. Consult your hardware documentation for details.
If you do not have a RAID controller module 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) RAID controller module module firmly into place. |
| 5 |
Check the status of the RAID controller module in the Array Management Window. The RAID controller module should have an optimal status.
|
| 6 |
If you have virtual disks mapped to hosts that have Automatic Virtual Disk Transfer (AVT) disabled, it may be necessary to redistribute the virtual disks to their preferred RAID controller module. Use the following steps to determine the AVT status of the hosts connected to your storage array:
| a |
Open the Storage Array Profile by selecting the Storage Array >> View >> Profile menu option from the Array 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 virtual disks on this storage array that have an AVT status of disabled
OR
There are hosts mapped to virtual disks on this storage array that are not running a host-based, multi-path failover driver
|
It may be necessary to redistribute the virtual disks to their preferred RAID controller module. If the Array Management Window's Advanced >> Recovery >> Redistribute Virtual Disks menu option is available, select the option.
Note: If you have a mix of hosts with AVT enabled and AVT disabled, all virtual disks 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 virtual disks mapped to the AVT-enabled hosts may get temporarily returned back to the non-preferred path.
If the menu option is not available (grayed out), the virtual disks are already associated with their preferred RAID controller modules and no action is needed.
Go to step 7.
|
| There are NO hosts mapped to virtual disks on this storage array with an AVT status of disabled
AND
All hosts mapped to virtual disks on this storage array are running a host-based, multi-path failover driver
|
No action is required.
If virtual disks need to be redistributed to their preferred RAID controller module, 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. |