VPLEX: How to Restart VPlexManagementConsole to Refresh VPLEX CLI or UI

• VPLEX UI or CLI does not display up-to-date information.
• VPLEX UI or CLI has conflicting information
• VPLEX UI or CLI has been slowing down
• Unable to log in to VPLEX CLI or UI

Follow the steps below to restart the VPlexManagementConsole service. The VPlexcli and UI are refreshed by restarting this service.

Note: If the VPLEX is running GeoSynchrony 6.2 SP1 or higher, you must use the alternate steps in the section below titled, "Restarting VPlexManagementConsole on GeoSynchrony 6.2 SP1 and later code levels." Otherwise, if VPLEX is running GeoSynchrony 6.2 P7 or lower, use the below steps to restart the console service.

Restarting VPlexManagementConsole on GeoSynchrony 6.2 P7 and lower code levels

1. Log in to the management server using PuTTY and the service account credentials.
2. Once on the management server, run the following command.

service@ManagementServer:~> sudo /etc/init.d/VPlexManagementConsole restart
Restarting EMC VPlex Management Console...

3. When the service has restarted, check the status of the service to ensure it is running using the command below.

service@ManagementServer:/etc/init.d/> sudo /etc/init.d/VPlexManagementConsole status
VPlexManagementConsole is running (pid 12345)

4. After restarting the management console, allow approximately five minutes for the system to stabilize before attempting a new login. The wait time varies depending on the size of the VPLEX environment.
5. Access the UI by opening a browser and typing in the management server IP address or access the VPlexcli level from the management server. Check to see if the changes that you were not able to see before, as noted in the Symptoms section, now show.
6. Access the VPLEX UI:

https:// <mgmt server ip address>

Or
Access the VPlexcli from the management server:

service@ManagementServer:~> vplexcli

Restarting VPlexManagementConsole on GeoSynchrony 6.2 SP1 and later code levels

1. To restart the VPlexManagementConsole service, run the following command: 

service@ManagementServer:~> sudo systemctl restart VPlexManagementConsole

2. To check status on the VPlexManagementConsole service, run the following command:

service@ManagementServer:~> sudo systemctl status VPlexManagementConsole

3. After restarting the management console, allow approximately five minutes for the system to stabilize before attempting a new login. The wait time varies depending on the size of the VPLEX environment.

           Example of the output seen when the status of the VPlexMaanagementConsole service is checked..

service@ManagementServer:~> sudo systemctl status VPlexManagementConsole
● VPlexManagementConsole.service - VPlexManagementConsole
     Loaded: loaded (/etc/systemd/system/VPlexManagementConsole.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2024-06-17 10:23:51 UTC; 3 weeks 4 days ago
    Process: 18961 ExecCondition=/bin/bash -c [ "$(cat /proc/platform)" == "snowhill" ] || [ "$(cat /proc/spid)" == "0" ] (code=exited, status=0>
    Process: 18964 ExecStartPre=/bin/bash -l -c echo /usr/bin/java $JAVA_OPTS -cp $CLASSPATH com.emc.vplex.smsv2.cli.Main $CLI_OPTS (code=exited>
   Main PID: 18985 (java)
      Tasks: 422
     CGroup: /system.slice/VPlexManagementConsole.service
             ├─18985 /usr/bin/java -Xmx2048m -XX:+UseMembar -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/VPlex/cli//vplex-oome-heap>
             ├─19408 ssh -p 22 -t -oBatchMode=yes -oControlMaster=auto -oControlPersist=yes -oControlPath=/tmp/ssh-ctrl-%r@%h:%p -oServerAliveIn>
             ├─19414 ssh: /tmp/ssh-ctrl-service@128.221.252.35:22 [mux]
             ├─19415 ssh -p 22 -t -oBatchMode=yes -oControlMaster=auto -oControlPersist=yes -oControlPath=/tmp/ssh-ctrl-%r@%h:%p -oServerAliveIn>
             ├─19418 ssh: /tmp/ssh-ctrl-service@128.221.252.36:22 [mux]
             ├─19430 ssh -p 22 -t -oBatchMode=yes -oControlMaster=auto -oControlPersist=yes -oControlPath=/tmp/ssh-ctrl-%r@%h:%p -oServerAliveIn>
             ├─19436 ssh: /tmp/ssh-ctrl-service@128.221.252.67:22 [mux]
             ├─19437 ssh -p 22 -t -oBatchMode=yes -oControlMaster=auto -oControlPersist=yes -oControlPath=/tmp/ssh-ctrl-%r@%h:%p -oServerAliveIn>
             ├─19440 ssh: /tmp/ssh-ctrl-service@128.221.252.68:22 [mux]
             ├─21115 ssh -p 22 -t -oBatchMode=yes -oControlMaster=auto -oControlPersist=yes -oControlPath=/tmp/ssh-ctrl-%r@%h:%p -oServerAliveIn>
             ├─21118 ssh: /tmp/ssh-ctrl-service@128.221.253.35:22 [mux]
             ├─21122 ssh -p 22 -t -oBatchMode=yes -oControlMaster=auto -oControlPersist=yes -oControlPath=/tmp/ssh-ctrl-%r@%h:%p -oServerAliveIn>
             ├─21125 ssh: /tmp/ssh-ctrl-service@128.221.253.36:22 [mux]
             ├─21130 ssh -p 22 -t -oBatchMode=yes -oControlMaster=auto -oControlPersist=yes -oControlPath=/tmp/ssh-ctrl-%r@%h:%p -oServerAliveIn>
             ├─21133 ssh: /tmp/ssh-ctrl-service@128.221.253.67:22 [mux]
             ├─21142 ssh -p 22 -t -oBatchMode=yes -oControlMaster=auto -oControlPersist=yes -oControlPath=/tmp/ssh-ctrl-%r@%h:%p -oServerAliveIn>
             └─21145 ssh: /tmp/ssh-ctrl-service@128.221.253.68:22 [mux]

Jul 12 13:20:06 ManagementServer sudo[30096]:  service : PWD=/var/log/VPlex/cli ; USER=root ; COMMAND=/usr/sbin/ipsec status
Jul 12 13:20:06 ManagementServer sudo[30121]:  service : PWD=/var/log/VPlex/cli ; USER=root ; COMMAND=/usr/sbin/ipsec status
Jul 12 13:20:06 ManagementServer sudo[30119]:  service : PWD=/var/log/VPlex/cli ; USER=root ; COMMAND=/usr/sbin/ipsec status
Jul 12 13:20:06 ManagementServer sudo[30147]:  service : PWD=/var/log/VPlex/cli ; USER=root ; COMMAND=/usr/sbin/ipsec status
Jul 12 13:20:06 ManagementServer sudo[30156]:  service : PWD=/var/log/VPlex/cli ; USER=root ; COMMAND=/usr/sbin/ipsec status
Jul 12 13:20:07 ManagementServer sudo[30183]:  service : PWD=/var/log/VPlex/cli ; USER=root ; COMMAND=/usr/sbin/ipsec status
Jul 12 13:20:07 ManagementServer sudo[30195]:  service : PWD=/var/log/VPlex/cli ; USER=root ; COMMAND=/usr/sbin/ipsec status
Jul 12 13:20:25 ManagementServer sudo[30298]:  service : PWD=/var/log/VPlex/cli ; USER=root ; COMMAND=/usr/sbin/ipsec status
Jul 12 13:23:46 ManagementServer sudo[32697]:  service : PWD=/var/log/VPlex/cli ; USER=root ; COMMAND=/usr/sbin/ipsec status
Jul 12 13:23:46 ManagementServer sudo[32709]:  service : PWD=/var/log/VPlex/cli ; USER=root ; COMMAND=/usr/sbin/ipsec status
lines 1-36/36 (END)

Note: To get back to the management server prompt after the above output is displayed press Ctrl-c.

4. Access the UI by opening a browser and typing in the management server IP address or access the VPlexcli level from the management server. Check to see if the changes that you were not able to see before, as noted in the Symptoms section, now show.

Access the VPLEX UI:

https:// <mgmt server ip address>

Or

Access the VPlexcli from the management server:

service@ManagementServer:~> vplexcli

• If you attempt to log in to the VPlexcli immediately after restarting the VPlexManagementConsole, the login attempts fail and can possibly have false-positives while the information is refreshed in the CLI and UI.
• If a message is displayed stating that the process could not be gracefully stopped, run the command to restart the VPlexManagementConsole again.