Symptoms

Ndu pre-check error: Verify management network redundancy.. ERROR VPlexcli:/> ndu pre-check Verify management network redundancy.. ERROR VPlexcli:/>ndu pre-check --verbose (***run on Cluster-2) No management connectivity to /engines/engine-1-1/directors/director-1-1-A at IP 128.221.253.35 [ERROR]: No management connectivity to /engines/engine-1-1/directors/director-1-1-B at IP 128.221.253.36 [ERROR]: No management connectivity to /engines/engine-1-2/directors/director-1-2-A at IP 128.221.253.37 [ERROR]: No management connectivity to /engines/engine-1-2/directors/director-1-2-B at IP 128.221.253.38 [ERROR]: No management connectivity to /engines/engine-1-3/directors/director-1-3-A at IP 128.221.253.39 [ERROR]: No management connectivity to /engines/engine-1-3/directors/director-1-3-B at IP 128.221.253.40 [ERROR]: No management connectivity to /engines/engine-1-4/directors/director-1-4-A at IP 128.221.253.41 [ERROR]: No management connectivity to /engines/engine-1-4/directors/director-1-4-B at IP 128.221.253.42 [ERROR]:

Cause

On further investigation the following behavior can be seen:Each MMCS (MMCS-A and MMCS-B) could ping all Directors across both VPlex Clusters on the 128.221.252 (MMCS-A) and 128.221.253 (MMCS-B) networks.In this case, MMCS-B on both (Cluster-1 and Cluster-2) is not able to ping the Remote Directors on the 128.221.253 network however the Local Directors are pinging OK from both MMCS-B's on the 128.221.253 network. It was not possible to SSH into MMCS-B on Cluster-2….MMCS-B on Cluster2 was replaced to resolve the issue.

Resolution

MMCS-B on Cluster2 was replaced to resolve the issue.ndu-pre-checks are now clean and error free.

Support Cases