Symptoms

Data mover is in Configured state with no Failover to standby Slot_3 and no impact: [nasadmin@Mea ~]$ /nas/sbin/getreason 10 - slot_0 primary control station 4 - slot_2 configured <<<<<<<< 5 - slot_3 contacted [nasadmin@Mea ~]$ nas_server -l id type acl slot groupID state name 1 1 0 2 0 server_2 2 1 0 3 0 server_3 Verify that the data mover is actually faulted or online: [nasadmin@Mea ~]$ /nas/bin/nas_server -info -all id = 1 name = server_2 acl = 0 type = nas slot = 2 member_of = standby = status : defined = enabled <<<<<<< If actually faulted : defined = out_of_service actual = online, active <<<<<<< If actually faulted : actual = out_of_service If DM is actually faulted, do not follow this KB.

Cause

Inconsistency in the CS database leads to display incorrect DM state in command output.

Resolution

Control Station reboot updates the CS database: Reboot CS.Wait for 10 minutes and verify that the DM state shows as contacted.

Support Cases