Subscribe
Accepted Solution

OnCommand Balance 4.2 not mapping Vsphere topology to Netapp controllers

Hi.

We are running an evaluation of Balance 4.2 in our enviroment at the moment.

 

However the discovery process is not mapping the vsphere datastores to volumes on the Netapp controllers. Is there any way to do this manually?

 

I have seen references in my searches to qtrees being an issue, however this was for version 3.6 and version 4.x apparently fully supports qtrees.

Our datastore mappings look like this:  Netappfiler-999:/vol/Volume_name/Qtree_name   - there is only one datastore/qtree per volume.

 

Any ideas?

 

Thanks

Colin G

Re: OnCommand Balance 4.2 not mapping Vsphere topology to Netapp controllers

Just to answer my own question... Its working now!

 

It was traced back to Vsphere using dns to mount datastores on the controllers.. once i added the correct dns suffix's into Balance, it started to work, even though Balance cant actually get to the storage networks.

 

Ta