VMware Cloud Community
chrsun02
Enthusiast
Enthusiast

VDP 6.1 can´t connect to vdp appliance inside vsphere web client

Hi,

I have depolyed VDP 6.1 and have it up and running. now im trying to connect to the appliance frpm vsphere Web client. After pressing connect the screen goes grey and nothing happens.

No error message no time out, just grayed out with timeglas not moving.

DNS is ok

account for vdp in vcenter ok

all services for appliance are ok

vcenter 5.5 ESXI 5.5

Regards

mgd

85 Replies
pascalsaul
Contributor
Contributor

Yes, been there done that 😕 I think these cases need to be escalated to engineering... Because back-ups ain't running also...

My case: 16959042704

Reply
0 Kudos
SavkoorSuhas
Expert
Expert

Little more info after testing:

1. I migrated my VDP network to vDS and it stays grayed out on connect in web client

2. Migrated the VDP networking to standard switch and it connected immediately.

Are we running distributed switches?

Suhas

If you found this or any other answer useful please consider the use of the Helpful or Correct buttons to award points.

Don't Backup. Go Forward!
Rubrik

pascalsaul
Contributor
Contributor

Correct, after switching to VSS I can connect to the appliance again...

During the upgrade to 6.2.1 I lost my back-upjob with attach existing disks method.

Now trying to create a new job for tonight...takes long for submitting the job? Still waiting or I'm not patient enough.

Well a little step further now... Now is the questing what is causing this behaviour Smiley Happy

Reply
0 Kudos
SavkoorSuhas
Expert
Expert

Backup job creation should be quick.

What is causing the behavior? That's a good question. Unfortunately I do not have the answer right away, let me dig in more into this.

Suhas

If you found this or any other answer useful please consider the use of the Helpful or Correct buttons to award points.

Don't Backup. Go Forward!
Rubrik

Reply
0 Kudos
RyanJMN
Enthusiast
Enthusiast

I recently ran into this issue with VDP webclient not loading at a customer of mine.  vCenter and PSC recently was updated to 6.0 U1.  I believe its a vCenter or PSC permission issue and not specifically a VDP issue.

We looked at the webclient vergo logs at the time attempting to open the VDP webclient.  Looks like the web client has an issue with com.vmware.vim.binding.vim.dvs.PortConnection which has to do with distributed switches.

[2016-04-06T17:50:42.280-05:00] [INFO ] http-bio-9443-exec-14 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint vdp-amf received request.

[2016-04-06T17:50:42.367-05:00] [INFO ] http-bio-9443-exec-14         org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint vdp-amf received request.

[2016-04-06T17:50:42.382-05:00] [ERROR] http-bio-9443-exec-14 Endpoint.AMF Cannot create class of type 'com.vmware.vim.binding.vim.dvs.PortConnection'.

  1. flex.messaging.MessageException: Cannot create class of type 'com.vmware.vim.binding.vim.dvs.PortConnection'. Type 'com.vmware.vim.binding.vim.dvs.PortConnection' not found.

at flex.messaging.util.ClassUtil.createClass(ClassUtil.java:70)

Moving VDP from distributed switches to standard switches did get it to work and the errors disappeared in the vergo log.  vCenter can still be connected to a distributed switch.  Backup jobs continued to work when the webclient would not load.

It looks similar to this KB https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=21252...  which is why I'm thinking its a vCenter or PSC permissions issue due to the upgrade.  At this point we will probably wait for VMWare support to resolve the issue because for us moving VDP to a standard switch is an alright work around.

We also have an odd behavior with some of the roles displaying differently.  For example there is a role called "inventorhyservice.tagging.taggingadmin" instead of "Tagging Admin".  Might be related.

Reply
0 Kudos
SavkoorSuhas
Expert
Expert

Informative. Let me get the analysis going and I can try correlating to what we are seeing in your virgo logging.

Suhas

If you found this or any other answer useful please consider the use of the Helpful or Correct buttons to award points.

Don't Backup. Go Forward!
Rubrik

Reply
0 Kudos
chadc1979
Enthusiast
Enthusiast

I am experiencing the exact same issue, figured I'd poke around here before submitting a ticket.

I'm on vCenter 6.0 U2/ESXi 6.0 U2 and VDP 6.1.2, all VMs use 9.10.5 VMware Tools on HW Profile 11

If I switch to a Standard Switch things work but on a Distributed Switch the Web Client hangs on connecting, I have found I can create backup jobs against a vSAN datastore but not against a shared storage array. Not sure if local storage works!

Glad to see I'm not alone.

Reply
0 Kudos
pascalsaul
Contributor
Contributor

I can do everything with the VDP on the VSS except creating a simple back-upjob with 1 VM 😕

Showing the logs/reports, running a manual integrity check and deleting a restore point is not a problem. Rebooted the appliance twice allready.

Annoying...

Are there any logs for these actions? And where are they located on the VCS?

Reply
0 Kudos
cans
Contributor
Contributor

Feedback from VMware support: VDP 6.1.x doesn't work with Virtual Distributed Switch !

They were able to reproduce the bug.

Next step is to open a ticket to EMC support (since VDP is a EMC solution just rebranded by VMware) , but this might take time ... Smiley Sad

Perhaps if all of you guys open SR regarding this problem it will reduce the resolution time ?

Workaround is to use Standard vswitch but in my case this is very complicated since we have a full dvswitch environment (due to LACP usage).

Reply
0 Kudos
SavkoorSuhas
Expert
Expert

Yes.

vdr-server.log has these information.

Location: /usr/local/avamar/var/vdr/server_logs

It's going to look something like this for a successful create:

2016-04-15 18:55:47,371 INFO  [http-nio-8543-exec-10]-rest.BackupService: Create backup job qwerty

2016-04-15 18:55:47,387 INFO  [http-nio-8543-exec-10]-services.BackupJobManagementServiceWS: VCenterClient fqname="/192.168.1.1/192.168.1.1" name="192.168.1.1" cid="d03a58d99b282b9c7c6cb9c6367ff23394f0f014" os="N/A" ver="Unknown" init-time="2016-04-04 00:00:00.0 (1459708200000)" last-contact-time="2016-04-07 00:00:00.0 (1459967400000)" plugins=[] vcenter-port=443 vcenter-user="vsphere.local\Suhas"

2016-04-15 18:55:47,469 INFO  [http-nio-8543-exec-10]-job.JobServiceImpl: Setting the window start time: Fri Apr 15 20:00:08 IST 2016

2016-04-15 18:55:51,102 INFO  [http-nio-8543-exec-10]-ddr.DdrDatasetServiceImpl: Successfully Set DDR DatasetOptions (enabled=false, index=0) On Dataset "qwerty"

2016-04-15 18:55:51,102 INFO  [http-nio-8543-exec-10]-job.JobServiceImpl: Created Backup Dataset "qwerty"

2016-04-15 18:55:51,184 INFO  [http-nio-8543-exec-10]-services.BackupJobManagementServiceWS: Client  name=CentOS7 uuid=5039665b-4899-9c00-1695-e42ff9d4eda2 vcc=VCenterClient fqname="/192.168.1.1/192.168.1.1" name="192.168.1.1" cid="d03a58d99b282b9c7c6cb9c6367ff23394f0f014" os="N/A" ver="Unknown" init-time="2016-04-04 00:00:00.0" last-contact-time="2016-04-07 00:00:00.0" plugins=[] vcenter-port=443 vcenter-user="vsphere.local\Suhas" vmpath=[Protected_LUN] CentOS7/CentOS7.vmx guestid=centos64Guest guestfullname=CentOS 4/5/6/7 (64-bit)

2016-04-15 18:55:51,587 INFO  [http-nio-8543-exec-10]-services.BackupJobManagementServiceWS: Schedule: 0

is your backup create failing? If so does it display any error in GUI?

And what does vdr_server log state?

Suhas

If you found this or any other answer useful please consider the use of the Helpful or Correct buttons to award points.

Don't Backup. Go Forward!
Rubrik

Reply
0 Kudos
pascalsaul
Contributor
Contributor

Ah ok Suhas! Lohit just called me and also told me the protected clients need to be on the VSS to be able to create a back-up job. That's is working for me also but in our situation not doable Smiley Happy

I need to downgrade to the previous version now and wait for the bugfix. It's now at the EMC/VMWare engineering teams he said.

Reply
0 Kudos
SavkoorSuhas
Expert
Expert

Yes, just got the same validated in my lab and well as with the Open ticket with me.

Yes the following are seen in the virgo.log during the VDP connect when on vDS

[2016-04-15T14:08:15.093Z] [ERROR] http-bio-9090-exec-10         Endpoint.AMF                                                      Cannot create class of type 'com.vmware.vim.binding.vim.dvs.PortConnection'.

flex.messaging.MessageException: Cannot create class of type 'com.vmware.vim.binding.vim.dvs.PortConnection'. Type 'com.vmware.vim.binding.vim.dvs.PortConnection' not found.

        at flex.messaging.util.ClassUtil.createClass(ClassUtil.java:70)

        at flex.messaging.io.AbstractProxy.getClassFromClassName(AbstractProxy.java:87)

I also ran into issues creating backup job when VM is on vSS as well (Just for one VM)

The error: <backuperror>

And when I click "Show sources" in backup tab, it shows the ESXi host where the VM resides.

Unfortunately, no more workaround are available at the moment.

Suhas

If you found this or any other answer useful please consider the use of the Helpful or Correct buttons to award points.

Don't Backup. Go Forward!
Rubrik

Reply
0 Kudos
jo_strasser
Enthusiast
Enthusiast

Hi,

same here.

I can reproduce this issue.

VDP access through Web Client and Backup Job creation only will work if the VDP appliance and the VMs to backup are on a standard vswitch.

I will escalate this bug also to VMware.

Following versions are affected for me right now: VDP 6.1.1 and VDP 6.1.2.

Thanks JO



Johannes Strasser / SDDC Architect @ Porsche Informatik GmbH
Twitter: @jo_strasser
Reply
0 Kudos
pascalsaul
Contributor
Contributor

6.1.1.19 is working without a problem on a VDS here...

Reply
0 Kudos
jo_strasser
Enthusiast
Enthusiast

Which version of DVS are you using? 6.0?

Have you fresh deployed the appliance or done a downgrade?

Greets JO



Johannes Strasser / SDDC Architect @ Porsche Informatik GmbH
Twitter: @jo_strasser
Reply
0 Kudos
pascalsaul
Contributor
Contributor

I'm using 5.5...

I did a downgrade and a new deployment...

Reply
0 Kudos
Evato
Enthusiast
Enthusiast

Interesting scenario here...

vSphere 5.5 U2 with ESXi 5.5 U2 with vDS 5.1 and VDP 6.1.1 working fine

vSphere 5.5 U2 with ESXi 5.5 U2 with vDS 5.5 neither VDP 6.1.1 or 6.1.2 will connect via web client

Has anyone else reporting issues tried with a vDS 5.1 ?

Reply
0 Kudos
jo_strasser
Enthusiast
Enthusiast

I´ve tested vSphere 6.0U2 with VDP 6.1.2 on VDS 6.0 -- isn´t working

vSphere 6.0U2 with VDP 6.1.1 on VDS 6.0 - isn´t working

Looks like a dependence to newer versions of vDS (5.5 or newer)

Greets JO



Johannes Strasser / SDDC Architect @ Porsche Informatik GmbH
Twitter: @jo_strasser
Reply
0 Kudos
kencox
Contributor
Contributor

This scenario presented the same issue for me:

vSphere 6.0U2 with vDS 5.1 and VDP 6.1.2

As soon as I moved the VDP back to a local standard switch, the web client connects with no problem.  I attempted to create a backup job for a single VM ('testvm') which was still on the vDS and that just hung.  After moving 'testvm' to the same local standard switch, the backup job creation completed successfully.

Reply
0 Kudos
jo_strasser
Enthusiast
Enthusiast

Thanks fpr updating.

Please also create a VMware Support Ticket to get a quick and fast resolution for that.

Thanks JO!



Johannes Strasser / SDDC Architect @ Porsche Informatik GmbH
Twitter: @jo_strasser
Reply
0 Kudos