Administrator Guide

Table Of Contents
When failover is initiated for a specific logical unit on an array to a specific target controller as active, metro node firmware
event apf/3 is observed. When failover succeeds or fails for a specific logical unit on an array to a specific target controller as
active, a metro node firmware event apf/4 is generated.
For Example:
apf/3 Failover initiated for logical unit VPD83T3:6006016015a0320061d7f2b300d3e211 on
array EMC~CLARiiON~FNM00124500474 to target controller FNM00124500474.SPA as active.
apf/4 Failover succeeded for logical unit VPD83T3:6006016015a0320061d7f2b300d3e211 on
array EMC~CLARiiON~FNM00124500474 to target controller FNM00124500474.SPA as active.
apf/4 Failover failed for logical unit VPD83T3:600601606bb72200f01fb4fa1e22e311 on array
EMC~CLARiiON~FCNCH072602809 to target controller FCNCH072602809.SPA as active. reason:
Scsi mode select command failed
Similar entries can be found in the metro node firmware event log /var/log/VPlex/cli/firmware.log* on a running
management server.
Logical Unit failback
When the status of the logical unit becomes nominal, metro node automatically attempts to fail back the logical unit to its
default controller. This is usually defined as the owner of the logical unit as determined by the array. The logical unit failover
execution process is started again in order to optimize the performance on the storage array side. This failback occurs only if
the array has the autoswitch property enabled and the logical unit is visible through the controller.
NOTE:
The Simple Support Matrix for metro node provides more information on the supported Dell EMC storage systems
and third-party arrays.
Metro node with active-passive storage arrays 109