VSC for VCSA 6.5

[thomasb82]

Hi guys,

as VMware is pushing more and more VCSA we want to migrate from vCenter 6 running on Windows to the VCSA 6.5

When will VSC be available for VCSA 6.5 (without the need of running it on another Windows machine)?

Thanks!

[mrc247]

Unfortunately the version 6.2.1P1D2 also has the "task label" problem. 😞

[jasonnash]

We are also running VSC 6.2.1P1D2 with the latest build of vCenter 6.5u1. We have the same issue with the labels. Do we know if it is Netapp or VMware we should be pushing on this one? We haven’t opened a ticket at present.

[mrc247]

It is definitely a NetApp problem. If you uninstall / unregister the VSC and restart the VCSA, the problem is gone.
I have written my NetApp Systems Engineer at NetApp Germany, hopefully he can pass it on to the development department.

[jasonnash]

Thanks. I have opened a ticket with Netapp. Case # 2006997878. I'll update if they come back with anything useful.

[mrc247]

That would be very nice if you could keep us informed.

Please note, every time you install a different VSC version, the problem is not there, only when the VCSA the first time reboots the problem arises.

When uninstalling it is exactly different around, the problem is after the deinstalltion only away when afterwards the VCSA is restarted.

Please excuse my google translated english. 😉

[florent_gilain]

Any news regarding this ?

[mrc247]

My NetApp Systems Engineer at NetApp Germany has said that I should open a case, so that there can be a solution.

That's what I did, case # 2007006851

Please also open a case and refer to the other two cases # 2007006851 and Case # 2006997878, so NetApp notes how many customers are affected, obviously they do not know the problem although it has already been discussed here in the thread for half a year.

[jasonnash]

I have now sent various logs off to Netapp as requested on the case but as of yet I havent had anything useful from them.

I also logged a case with VMware #17533454908. They highlighed the below entries in the vCenter wrapper.log but as of yet nothing further on this. The task labels are not causing us too much issue day to day but host profiles are almost unusable.  

wrapper.log
INFO | jvm 1 | 2017/08/10 17:17:53 | at java.lang.Thread.run(Thread.java:745)
INFO | jvm 1 | 2017/08/10 17:17:53 | Aug 10, 2017 5:17:53 PM com.vmware.vim25.ws.XmlGenDom fromXml
INFO | jvm 1 | 2017/08/10 17:17:53 | WARNING: ViJava XmlGenDom:failoverClusterManager
INFO | jvm 1 | 2017/08/10 17:17:53 | XmlGenDom: Encountered missing fieldvStorageObjectManager
INFO | jvm 1 | 2017/08/10 17:17:53 | java.lang.NoSuchFieldException: vStorageObjectManager
INFO | jvm 1 | 2017/08/10 17:17:53 | at java.lang.Class.getField(Class.java:1703)
INFO | jvm 1 | 2017/08/10 17:17:53 | at com.vmware.vim25.ws.XmlGenDom.fromXml(XmlGenDom.java:238)
INFO | jvm 1 | 2017/08/10 17:17:53 | at com.vmware.vim25.ws.XmlGenDom.fromXML(XmlGenDom.java:208)
INFO | jvm 1 | 2017/08/10 17:17:53 | at com.vmware.vim25.ws.XmlGenDom.fromXML(XmlGenDom.java:114)
INFO | jvm 1 | 2017/08/10 17:17:53 | at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:93)
INFO | jvm 1 | 2017/08/10 17:17:53 | at com.vmware.vim25.ws.VimStub.retrieveServiceContent(VimStub.java:1434)
INFO | jvm 1 | 2017/08/10 17:17:53 | at com.vmware.vim25.mo.ServiceInstance.init(ServiceInstance.java:175)
INFO | jvm 1 | 2017/08/10 17:17:53 | at com.vmware.vim25.mo.ServiceInstance.(ServiceInstance.java:99)
INFO | jvm 1 | 2017/08/10 17:17:53 | at com.vmware.vim25.mo.ServiceInstance.(ServiceInstance.java:90)
INFO | jvm 1 | 2017/08/10 17:17:53 | at com.netapp.nvpf.container.vsphere.ServiceInstanceManager.createServiceInstance(ServiceInstanceManager.java:142)
INFO | jvm 1 | 2017/08/10 17:17:53 | at com.netapp.nvpf.container.vsphere.ServiceInstanceManager.withServiceInstance(ServiceInstanceManager.java:52)
INFO | jvm 1 | 2017/08/10 17:17:53 | at com.netapp.nvpf.container.vsphere.ServiceInstanceProvider.withServiceInstance(ServiceInstanceProvider.java:73)
INFO | jvm 1 | 2017/08/10 17:17:53 | at com.netapp.nvpf.container.vsphere.ServiceInstanceProvider.withServiceInstance(ServiceInstanceProvider.java:90)
INFO | jvm 1 | 2017/08/10 17:17:53 | at com.netapp.nvpf.container.vsphere.ServiceInstanceProvider.withAdminServiceInstance(ServiceInstanceProvider.java:219)
INFO | jvm 1 | 2017/08/10 17:17:53 | at com.netapp.nvpf.container.vsphere.VSphereSessionManager.isActive(VSphereSessionManager.java:65)
INFO | jvm 1 | 2017/08/10 17:17:53 | at com.netapp.nvpf.container.vsphere.security.VSphereLoginService.isValidVsphereSession(VSphereLoginService.java:102)
INFO | jvm 1 | 2017/08/10 17:17:53 | at com.netapp.nvpf.container.vsphere.security.VSphereLoginService.login(VSphereLoginService.java:57)
INFO | jvm 1 | 2017/08/10 17:17:53 | at com.netapp.nvpf.container.vsphere.security.VSphereAuthenticator.validateRequest(VSphereAuthenticator.java:75)
INFO | jvm 1 | 2017/08/10 17:17:53 | at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:456)
INFO | jvm 1 | 2017/08/10 17:17:53 | at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:233)
INFO | jvm 1 | 2017/08/10 17:17:53 | at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1065)
INFO | jvm 1 | 2017/08/10 17:17:53 | at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:413)
INFO | jvm 1 | 2017/08/10 17:17:53 | at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:192)
INFO | jvm 1 | 2017/08/10 17:17:53 | at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:999)
INFO | jvm 1 | 2017/08/10 17:17:53 | at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)

[mrc247]

After weeks I received a feedback from netapp:

Dear customer ,

please try to clear the browser cache (or to use different browsers) or reset the user profile (or try from a different station) and see if you still have some strange display of the labels.

are they kidding me???  

[navion]

VSC 7.0 finally released, but they completely remove backup and restore feature, so you should install SnapCenter before upgrading.

Download:

http://mysupport.netapp.com/NOW/download/software/vsc_win/7.0/

Release Notes:

https://library.netapp.com/ecm/ecm_get_file/ECMLP2771656

[Marco79]

So now I need  SnapCenter to run my backup jobs?

[mrc247]

Thank you for the modest comment that the VSC 7.0 has appeared.

Unfortunately, I have a problem to import the Virtual Appliance.

I get the error message "ovf-descriptor is not available". 😞

What is an ovf descriptor? So far I had never problems to import an .ova file.

EDIT:

it's been dealt with

[mrc247]

Unfortunately I have to report that the "task description label" problem with the version 7.0 was not fixed. 😞

After I had uninstalled the VSC 6.2.1P1, I rebooted the VCSA, after which the problem was gone.
Then I installed the VSC 7.0 and I have already been happy that the problem was gone.
Now I have again the VCSA rebooted and suddenly the problem exists again. 😞

[MrJake]

It looks like the this VASA appliance contains VSC functions now as well.

http://mysupport.netapp.com/NOW/download/software/vasa_cdot/7.0/

[jasonnash]

So far I've had the same response from them. VMware support are going on a Webex this week but I'm unsure they will be able to resolve.

[jasonnash]

Latest update from VMware as below.

'We suspect that this issue is due to compatibility between VCSA 6.5u1 and  Netapp plugin.'

Is everyone else with this issue running 6.5u1?

[mrc247]

I can confirm the problem exists at both 6.5 and 6.5U1

[binaryred]

Yep, Running 6.5u1 here as well and seeing the problem.

[jasonnash]

Netapp have confirmed (under case no. 2006997878) that they can now reproduce this issue. As we know the workaround is to unregister VSC, reboot and then re-register VSC. All is then fine until you next restart.

[mrc247]

I quoted you and sent it to my case owner. Perhaps they can use synergies.

[GovtGeeks]

All --

Were you experiencing these .Label errors before VSC was installed? When I upgraded from vCSA 6.0 to 6.5 upgrade I had the same issue. The workaround that fixed my issue was logging in as the administrator@vsphere.local user... Have you all tried that yet? I'm not noticing any issues w/ the wrapper issue w/ VSC 7.0 and vCenter 6.5 like you guys are, just figured I would offer this suggestion...