Unsolved
This post is more than 5 years old
2 Intern
•
522 Posts
0
2141
March 6th, 2015 14:00
RP4VMs Plugin Not Showing in Web Client
Hello,
Curious if anyone has any additional troubleshooting tasks to resolve a newly deployed RP4VM cluster not showing the plugin in the web client. I have done the following, but it doesn't show up and I see about "no connectivity to managed array . no Connectivity with registered storage"
- Rebooted vRPA nodes - RP Native GUI comes up OK (vcenter error is the only error displayed)
- Restarted Web Client several times - no dice
- Rebooted/Restarted vcenter services - no dice
- Port 7225 looks to be working
- Plugin shows in the Thick Client as available with no client side download/install needed
- I see iSCSI connectivity to the vRPA's from the ESX software HBA as OK
The issue is similar to this thread in case this got resolved: https://community.emc.com/thread/207261
Just scratching my head as to what it could be before I try to deploy the plugin manually....thanks. I'm gonna double back on the 7225 port just to make sure.
fadliz
153 Posts
0
March 6th, 2015 14:00
If the plugin is not getting pushed, it could be still network, check the Security guide for more ports.
Did you check the vCenter registration in CLi? Use get_storage. Also I assume DM completed without issues.
Sent from my iPhone
echolaughmk
2 Intern
•
522 Posts
0
March 6th, 2015 18:00
Hi Z,
Thanks for the reply. I feel like it is network as well, but cannot seem to pinpoint at the moment what it is complaining about. The get_vcenter_server_view shows all the right stuff in the CLI and the installation and discovery through DM with regards to vcenter credentials and discovery was without error - all checkmarks.
The get_storage command shows the managed array as the correct vcenter server and as registered storage so I think it looks OK from what I can tell. I've been told all ports are open, firewalls off to test, etc - is there a diagnostics command to validate what port/issue is the culprit perhaps? If I run a netstat on the VC server, the port is enabled to be open on the server, but doesn't seem to be listening which seems like more of an application issue possibly. The advanced test in the RP CLI that tests a source/destination IP and port seems to fail but even after enabling it on the vcenter server, it doesn;t seem to be started by vcenter though as the issue even after a reboot so I am not sure how it is related to the network port or what else to do to enable it since it seems it should be enabled.
Thanks!