Loading...
Loading...
Different rule-set Names are displayed between clusters in the CLI on a VPLEX Metro Configuration. In this scenario, "Cluster-1-detaches" is the rule-set name on Cluster-1. On Cluster-2, "ruleset_recreate5" and "Cluster-1 detaches" are the rule-set Names for the same volumes. Under normal condition, the rule-set names should be identical on both Cluster. Cluster-1 rule-set output: VPlexcli:/distributed-storage/rule-sets> ll Name PotentialConflict UsedBy ------------------ ----------------- -------------------------------------------- cluster-1-detaches false <<<< Rule-Set Name device_XXXXXXXXXXXXXXXXXXXXXXXXXXXX, XXXXXXXXXXXXXXXXXXXXXX_1362_04, XXXXXXXXXXXXXXXXXXXXXX_1362_05, XXXXXXXXXXXXXXXXXXXXXX_1362_08, XXXXXXXXXXXXXXXXXXXXXX_1362_09, XXXXXXXXXXXXXXXXXXXXXX_1362_10, XXXXXXXXXXXXXXXXXXXXXX_1362_12, XXXXXXXXXXXXXXXXXXXXXX_1362_14, XXXXXXXXXXXXXXXXXXXXXX_1362_15, XXXXXXXXXXXXXXXXXXXXXX_1362_16, ... (667 total) Cluster-2 rule-set output: VPlexcli:/distributed-storage/rule-sets> ll Name PotentialConflict UsedBy ------------------ ----------------- -------------------------------------------- cluster-1-detaches false ruleset_recreate5 false XXXXXXXXXXXXXXXXXXXXXX_1362_01, XXXXXXXXXXXXXXXXXXXXXX_1362_04, XXXXXXXXXXXXXXXXXXXXXX_1362_05, XXXXXXXXXXXXXXXXXXXXXX_1362_08, XXXXXXXXXXXXXXXXXXXXXX_1362_09, XXXXXXXXXXXXXXXXXXXXXX_1362_10, XXXXXXXXXXXXXXXXXXXXXX_1362_12, XXXXXXXXXXXXXXXXXXXXXX_1362_14, XXXXXXXXXXXXXXXXXXXXXX_1362_15, XXXXXXXXXXXXXXXXXXXXXX_1362_16, ... (667 total)
This is a minor display issue. Both rule-set names have the correct settings for Disaster.
Permanent Fix: Dell VPLEX Engineering is currently investigating this problem. This article will be updated when a fix is available. Workaround: Note: Each step below must be performed on both VPLEX Management Servers before proceeding with the next step. Stop the VPLEX Management Console on both Clusters. service@ManagementServer:/var/log/VPlex/cli> sudo /etc/init.d/VPlexManagementConsole stop Stopping EMC VPlex Management Console... On Cluster-1, rename the persistentstore.xml file to persistentstore.xml.bk to create a backup copy. service@ManagementServer:/var/log/VPlex/cli> mv persistentstore.xml persistentstore.xml.bk service@ManagementServer:/var/log/VPlex/cli> ll persistentstore.xml* -rw-r--r-- 1 service users 79858 Apr 22 14:58 persistentstore.xml.bk Repeat Step 2 on Cluster-2. Start the VPLEX Management Console on both clusters. service@ManagementServer:/var/log/VPlex/cli> sudo /etc/init.d/VPlexManagementConsole start Starting EMC VPlex Management Console... done After completing Steps 1 through 4, verify the "/distributed-storage/rule-sets" context on both clusters from the VPlexcli level to confirm that the rule-set Names match on both sides. If the rule-set Names do not match after performing this procedure, contact Dell Technical Support for further investigation.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.