Site Recovery Manager OR vSphere Replication plugin is Not accessible in vCenter
Article ID: 388910
Updated On:
Products
Issue/Introduction
1. vCenter displays the SRM/VRMS plugin as 'Not accessible'
2. You cannot launch the plugin from vCenter as its grayed out
3. There is no indication of errors in the logs
4. If anything has changed in the configuration (like IP address, DNS, etc.), the plugin may become not accessible
Environment
VMware vCenter Server
VMware Live Site Recovery
VMware Site Recovery Manager
VMware vSphere Replication
Cause
Site Recovery Manager (SRM) or vSphere Replication (VRMS) Appliance plugin showing as 'Not Accessible' in vCenter can be attributed to DNS, Network, Firewall, Appliance certificate and configuration issues
Resolution
Follow the troubleshooting steps outlined below.
1. Check if the plugin status changes to OK from a different browser
TIP: Try 2 different browsers or incognito mode
2. Check if vCenter, SRM & VRMS are syncing with the same local or global NTP server
3. Use NSLOOKUP to check if DNS records are correctly configured for all the appliances (vCenter/SRM/VRMS)
C:\Users\admin>nslookup
Default Server: DC.vmware.com
Address : 10.X.X.X
> srmdr
Server : DC.vmware.com
Address: 10.X.X.X
Name : srmdr.vmware.com
Address: 10.X.X.X
> srmprod
Server : DC.vmware.com
Address: 10.X.X.X
Name : srmprod.vmware.com
Address: 10.X.X.X
> 10.X.X.X
Server : DC.vmware.com
Address: 10.X.X.X
Name : vrmsdr.vmware.com
Address: 10.X.X.X
> 10.X.X.X
Server : DC.vmware.com
Address: 10.X.X.X
Name : vrmsprod.vmware.com
Address: 10.X.X.X
4. PING & Port Connectivity Tests -
Network Ports for VMware Site Recovery
Services, Ports, and External Interfaces That the vSphere Replication Virtual Appliance Uses
A. Perform a PING test from vCenter to VRMS/SRM locally (intra-site)
B. Perform a Port connectivity test using the curl command.
Command: curl -v telnet://FQDN-OR-IP:Port#
Launch the vSphere Replication DR UI manually by entering this address in a browser - https://vrms-fqdn-or-ip/dr
Launch the Site Recovery Manager DR UI manually by entering this address in a browser - https://srm-fqdn-or-ip/dr
Depending on the errors you are seeing, perform a port connectivity test to check if the ports mentioned in the errors are open between the appliances (SRM & VRMS) using the curl command.
ERROR
Unable to retrieve pairs from extension server at https://srmdr.vmware.com:443/drserver/vcdr/vmomi/sdk. Unable to connect to Site Recovery Manager Server at https://srmdr.vmware.com:443/drserver/vcdr/vmomi/sdk. Reason: java.net.ConnectException: Timeout connecting to [srmdr.vmware.com/10.X.X.X:443]
Unable to connect to Site Recovery Manager Server at https://srmdr.vmware.com:443/drserver/vcdr/vmomi/sdk. Reason: java.net.ConnectException: Timeout connecting to [srmdr.vmware.com/10.X.X.X:443]
Operation ID: 911a886c-df20-432b-8c19-afc0d80f8a0e
2/12/25, 10:25:32 AM -0500
ERROR
Unable to retrieve pairs from extension server at https://srmprod.vmware.com:443/drserver/vcdr/vmomi/sdk.Unable to connect to Site Recovery Manager Server at https://srmprod.vmware.com:443/drserver/vcdr/vmomi/sdk. Reason: java.net.ConnectException: Timeout connecting to [srmprod.vmware.com/10.X.X.X:443]
Unable to connect to Site Recovery Manager Server at https://srmprod.vmware.com:443/drserver/vcdr/vmomi/sdk. Reason: java.net.ConnectException: Timeout connecting to [srmprod.vmware.com/10.X.X.X:443]
Operation ID: 911a886c-df20-432b-8c19-afc0d80f8a0e
2/12/25, 10:25:32 AM -0500
C. Perform an openssl test between the appliances (SRM & VRMS) locally (intra-site)
Command: openssl s_client -connect FQDN-OR-IP:Port#
5. Updating /etc/hosts file in the vCenter/SRM/VRMS appliance is recommended when there are DNS issues or there is no DNS server in the environment. You can update the hosts file to include vCenter, SRM & VRMS information from both the sites or the components that can't be reached via either appliances.
Format to update the hosts file:
10.X.X.X vrms.vmware.com vrms
10.X.X.X srm.vmware.com srm
10.X.X.X vCenter.vmware.com vCenter
NOTE: Registering the appliance using FQDN is the first preference. Register the appliance using IP address, when you have DNS issues.
6. Check Firewall Rules
Unblock the required ports by SRM & VRMS on your firewall.
If you are using NSX, add a rule to the distributed firewall to allow traffic between source and destination VMs
Additional Information
Log locations to check -
1. vCenter - /var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log
2. SRM/VRMS - localhost.log & catalina.log under H5ClientPlugin directory
Clearing the vSphere client cache and removing older plugins when Site Recovery plugin fails to download in vCenter (312655)
Feedback
