| Event Id | 870 |
| Event Source | Dell PowerVault |
| Description | Killed partner. |
| More Information | According to dell: Cause: The controller is waiting for the Enable Partner command before completing the startup process. If the controller option Auto Restore is set, the Enable Partner command is not needed. If the Auto Restore option is not set, the partner controller will wait for the Enable Partner command. Couldn't allocate chunk of memory. SCSI communication failed. Mismatch in the number of array disk channels present. Mismatch in the number of host channels present. Mismatch in the firmware version. Mismatch in the firmware header type. Memory read of partner controller failed. Mismatch in cache memory size. Received Disable Partner controller command. Negotiation finished, but nexus not entered in time. Write-back sync to partner controller, channels 0-5. Mismatch in firmware build. Device cables are crossed. Partner controller removal detected while nexus active. Partner controller missing at negotiation time. BBU powerfailed before failover finished. BBU powerfailed before relinquish finished. Lock time-out. Lock SCSI failed. General ctoc (controller to controller) message failure. Failed for some unknown reason. Resolution: Go to the Array Manager console and click to expand the Arrays storage object, right-click the PV660F Subsystem storage object, and select Rescan from the context menu that comes up. This action will update the partner controller. If the situation does not improve, try one of the following (Rescan as before when necessary after troubleshooting the partner controller): The controller is shipped with Auto Restore set. To see whether the partner is enabled, right-click the controller. If Enable Partner is on the menu, then the partner controller is disabled: click Enable Partner to enable the partner controller. If Disable Partner is on the menu, then the partner controller is enabled; use the following troubleshooting solutions to fix the event. Unless a firmware or memory mismatch is suspected, reboot the disabled partner controller. If a firmware or memory mismatch is the issue, see below. If memory problems exist, replace the memory module if necessary. See the Dell PowerVault 660F and 224F Storage Systems Service Manual. Check the firmware version of the good controller: in the Array Manager tree view right-click the Controller and click the Properties command on the context menu that appears. Replace the failed controller; see the Dell PowerVault 660F and 224F Storage Systems Service Manual. Go to the Array Manager console and click to expand the Arrays storage object, right-click the PV660F Subsystem storage object, and select Rescan from the context menu that comes up. This action will update the controller status. Check the firmware version of the new controller; if there is a mismatch, update both controllers with the latest firmware. See "Firmware version mismatch" in this chapter for instructions. Check the memory size of the good controller: right-click the Controller in the tree view and click the Properties command on the context menu that appears. Replace the failed controller with a controller of the same memory size; see the Dell PowerVault 660F and 224F Storage Systems Service Manual. Go to the Array Manager console and click to expand the Arrays storage object, right-click the PV660F Subsystem storage object, and select Rescan from the context menu that comes up. This action will update the controller status. Check that the partner controller is present. If it is not, reinstall the partner controller. See the Dell PowerVault 660F and 224F Storage Systems Installation and Troubleshooting Guide for slot module installation instructions. If the user gave the Disable Partner command, continue per user's intent. |
| Reference Links | event id:870 and source: Dell PowerVault |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.