VSC 4.0 Not Scanning (Optimization and Migration)

[#1]

Installed VSC 4.0 on vCenter 4 and while all other functions work correctly, the Optimization and Migration tab never scans any storage. Also, even after trying a manual scan, the storage says Last Scanned: Never.

Tried to uninstall, reinstall, several times.

[#2]

Still looking for a solution here. Tried several different servers and methods with the same results. We can see the filers and it is reading fine but will not scan properly for Optimization and Migration.

[#3]

is this one that your team handles or should the question get posted in the NetApp Support Community

[#4]

Ok, since I am new to the Netapp community, can you please guide me on which location I should post this in or where to proceed from here?

[#5]

Hi,

If Allan's team does not provide help, you can post your question in the NetApp Support Community where we have external and internal subject matter experts answering questions about SnapX products and software.  If you have a NOW login, this link enables you to engage them about this.

Mike

[#6]

Is mbrtools (mbrscan and mbralign) installed on the ESXi hosts? If not, you can do so using the following step-by-step reference http://www.unitek.com/training/netapp/blog/2011/12/install-mbrtools-esxi-server-2/.

[#7]

Hi Dustin

We faced the same issue in our environment, the issue was due to RBAC for the VSC role that we created. We changed the capablity to * (root access) to get this working.

The RBAC given for VSC2.0 is not working for this scan and we raised a case with Netapp and we are stil waiting for an answer

regards

Kumaresan

[#8]

Take a look at KB 2016839 and see if it helps.

[#9]

I had several issues with mbrtools.

#1 /opt/ontap disappears on reboot

fixed by placing the archive on one of my datastores and updating rc.local to extract every boot and change ownership of the extracted files so vpxuser owned the files

#2 on the san controller I had to set options httpd.admin.enable on

[#10]

The KB referenced in my earlier reply covers #2 in detail.