Troubleshooting Guide RP4VM Plug-in

Revised May 31, 2017

RP4VMs Plug-In Does Not Appear

KB: 500514
Let’s start with initial basic steps
Environment: RecoverPoint for Virtual
Machine

Start

Check if the vCenter is Registered

in RecoverPoint

Registered No Register vCenter in RP

Yes

Clear browser history/cookies/

cache

Restart the vSphere Web Client

Plugin visible? No
services

Yes
Note: If plugin is still not visible follow steps 2A to
6A based on the findings.
Plug-in works

Page 1 of 9 © Copyright EMC Corporation. All rights reserved.

 Troubleshooting Guide RP4VM Plug-in
Revised May 31, 2017

2A

Steps 1: To check if plugin extension is

installed

Use vCenter Managed object browser

https://vCenterIP/mob?moid=ExtensionManager

It should contain
"extensionList["com.emc.recoverpoint.vwc"]"

Positive? Yes Plugin extension is installed

No

Note: If Procedure 2 didn’t help (suspecting only partial

Follow Procedure 2 plugin information has been deployed in the system), try
both Procedure 1 and Procedure 2 in sequence.

Page 2 of 9 © Copyright EMC Corporation. All rights reserved.

 Troubleshooting Guide RP4VM Plug-in
Revised May 31, 2017

3A

Note: Plugin path in vCenter Server:

Windows VC:
C:\ProgramData\VMware\vSphere Web Client\vc-packages\vsphere-
client-serenity\com.emc.recoverpoint.vwc-x.x.x
Check if the plug-in files was deployed
to the vCenter server: Linux VC:
/var/lib/vmware/vsphere-client/vc-packages/vsphere-client-serenity/
com.emc.recoverpoint.vwc-x.x.x
Or
/etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/
com.emc.recoverpoint.vwc-x.x.x

Contains the plug-in files

Yes Plugin files deployed to vCenter Server

No

Note: If Procedure 2 didn’t help (suspecting only partial

plugin information has been deployed in the system), try
Follow Procedure 2
both Procedure 2 and Procedure 1 in sequence.

Page 3 of 9 © Copyright EMC Corporation. All rights reserved.

 Troubleshooting Guide RP4VM Plug-in
Revised May 31, 2017

4A

Verify communications

Ping VC from vRPAs

Pingable No

Yes Fix the communication

Can VC
No
communicate with vRPAs

Yes

Communication is OK

Page 4 of 9 © Copyright EMC Corporation. All rights reserved.

 Troubleshooting Guide RP4VM Plug-in
Revised May 31, 2017

5A

Verify FAPI communication:

You should see as below:

From the vCenter server, navigate to the

following address:
https://RPA-IP/fapi/rest/4_1

Output is as
No Need to fix FAPI communication
shown in the above Note section

Yes

No issues with FAPI communication

Page 5 of 9 © Copyright EMC Corporation. All rights reserved.

 Troubleshooting Guide RP4VM Plug-in
Revised May 31, 2017

6A

You should see something as below:

From the vCenter server, navigate to the following
address:
https://RPA-IP/amffapi/fapi/amf/4_1

Output is as shown in the above

No Need to fix FAPI communication
Note section

Yes
Note: If you don’t see result as shown above for both
1 and 2, there is a possibility of FAPI communication
issue and needs to be fixed.
No issues with FAPI communication
Also, check port 7225 for FAPI communication by
running telnet RPA_IP from VC.

Page 6 of 9 © Copyright EMC Corporation. All rights reserved.

 Troubleshooting Guide RP4VM Plug-in
Revised May 31, 2017

RP4VMs Plug-in is Visible but doesn't show Information or Actions

7A
Note: RP4VMs Plug-In is visible but does not show Information or
Actions

If above didn’t help, verify if customer has linked vCenters:

As per the design all linked vCenters must be registered whether
Initial Steps to check RP4VMs they contain RP4VMs or not.
plug-in is visible Use register_storage admin command and follow the prompts.

Note: Prior to vCenter version 6 user had to configure the linked

vCenters. From version 6, vCenters that are in the same domain
are automatically linked. Follow the condition above- all vCenter
Clear browser history/cookies/ servers must be registered with RP.
cache

Is plug-in the right version?

To check the installed RP4VM-Plugin version use the vCenter
Managed Object Browser (mob)
https://vCenterIP/mob/
?moid=ExtensionManager&doPath=extensionList%5b%22com%2e
Restart the vSphere Web
Plugin Works? No emc%2erecoverpoint%2evwc%22%5d
Client services
In the scenarios where the above aspects holds good but still the
plugin doesn’t show information, and if you have tried removal and
Yes installation of plugin already, you may want to review multiple old
bugs with similar situation as EE have provided hotfix/modified
plugins for certain environment (Example: For VC 6.0 U3, stock
RP4VM plugin doesn’t work). To install the modified version of
Plugin information is visible plugin, you need root access.

Page 7 of 9 © Copyright EMC Corporation. All rights reserved.

 Troubleshooting Guide RP4VM Plug-in
Revised May 31, 2017

Manual Removal of the RP4VMs Plug-In

8A

Manual Removal of the RP4VMs Plug-In

Unregister vCenter from the cluster. Note: Using admin command "unregister_storage" and follow the
prompt.

Navigate to https://vCenterIP/mob/?moid=ExtensionManager.
Unregister "com.emc.recoverpoint.vwc" · Click "UnregisterExtension" and enter
extension from the mob. "com.emc.recoverpoint.vwc".
· Click "Invoke Method".

Remove all tokens (labeled Navigate to https://vCenterIP/mob/?moid=CustomFieldsManager.

"config.RecoverPoint_TOKEN;xxxxxxxxxxxxxxxxxxx") · Click fields to find TOKENs.
from the mob. · Click "RemoveCustomFieldDef" and enter the field number of the
TOKEN.
· Click "Invoke Method".

Delete the plug-in folders from the vCenter.

Path to the plugin folder in vCenter Server:
Windows VC:
C:\Program Files\VMware\Infrastructure\vSphereWebClient\plugin-
packages\com.emc.recoverpoint.vwc-x.x.x
C:\ProgramData\VMware\vSphere Web Client\vc-packages\vsphere-
client-serenity\com.emc.recoverpoint.vwc-x.x.x
End
Linux VC:
/var/lib/vmware/vsphere-client/vc-packages/vsphere-client-serenity/
com.emc.recoverpoint.vwc-x.x.x
Or
/etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/
com.emc.recoverpoint.vwc-x.x.x

Page 8 of 9 © Copyright EMC Corporation. All rights reserved.

 Troubleshooting Guide RP4VM Plug-in
Revised May 31, 2017

Manual Installation of the RP4VMs Plug-In

9A

Manual Installation of the RP4VMs Plug-In

Register vCenter server using admin

command "register_storage".
>If above command didn’t work with Admin
user, run register_vcenter_server with SE
user.

Reboot RPAs 1 and 2 one at a time

Once site control is back up, restart the

vCenter Web Client Services

When Web Client Services are back up, log

in to the vCenter Web Client and check that
the plug-in is available.

End

Page 9 of 9 © Copyright EMC Corporation. All rights reserved.