Hi,  Okay, then here's what I suggest:  First, if you haven't done this in a while, restart the VPlexCLI process.  From the mgmt station prompt (not the VPlexCLI prompt):       sudo /etc/init.d/VPlexManagementConsole restart  Note:  This will terminate the sessions for any users connected to the CLI or GUI.  After issuing that restart, wait about a minute or so, then re-login into the Unisphere GUI.  Also check the monitors from the CLI if they've changed.  If that doesn't do anything, try issuing this command in the VPlexCLI to restart (kick) the monitors:      emc-internal configuration restart-perpetual-monitors  For the GUI to pick-up the change, I believe you have to restart the process again.(sudo restart above).  If even after that you have issues and 1-1-A's not updating, then more drastic steps may be required:  1. From the VPlexCLI, enable engineering-mode. 2. From the VPlexCLI, destroy the perpetual monitors for the director (1-1-A in your case): 3. Restart the CLI:  The monitor will get automatically recreated when the CLI starts up.  I'd also suggest upgrading to a 5.3 version of VPLEX code.  Hope that works! Gary 
Hi,  I've found that only one director is handling data transactions on one of VPLEX cluster. I figured this is not normal as other Clusters in Customer's environment have both directors handling data transactions.  I have checked the ports (FA and BE ) all of them are UP and also I can ping Director 1-1-A which we are facing this problem with.  Please suggest any workaround to omit this issue. Attached are the snips for both directors.[IMAGE][IMAGE]  -Nitss
Only one VPLEX director is handling all data transactions.