cancel
Showing results for 
Search instead for 
Did you mean: 

EV cannot detect the data ontap version in creating new target server

lindaloo3
Level 3

Hi,

I have a new NetApp filerserver FAS2554.  It is running Ontap 8.2.2.  When I try to add it as a target fileserver into EV 10.0.4 CHF2, I get the error:

Could not detect the Data ONTAP version for the File Server.

Placeholders will not be supported for this File Server.

The EV service account is an administrator.  I am running Ontap 7mode.  Anyone else seen this issue?  

I will be upgrading to EV11 this weekend, but do not think this will help.

 

Thanks,

Linda

1 ACCEPTED SOLUTION

Accepted Solutions

JesusWept3
Level 6
Partner Accredited Certified

probably best thing to do is get a dtrace of MMC when you're attempting and see if its something obvious there, could possibly be just a silly firewall issue? i don't know. or could genuinely be a bug
Like if you look on that link, it references another hotfix that gave the same error when it was set to UNIX, so it could be an unusual setting thats causing it to fail etc

https://www.linkedin.com/in/alex-allen-turl-07370146

View solution in original post

4 REPLIES 4

JesusWept3
Level 6
Partner Accredited Certified

not an incredibly useful article, but have you seen this one?
http://www.symantec.com/business/support/index?page=content&id=TECH157833

https://www.linkedin.com/in/alex-allen-turl-07370146

lindaloo3
Level 3

I did see this link, it was just about the only one I could find, but we are not using a WAN accelerator.   Other things I tried were other Netapps we had that were on different versions of Ontap, and those worked.  I also tried upgrading this new NetApp, but still the error setting it up as a target persisted.

This weekend I will upgrade EV to 11 but I do not think this will matter.  The compatibility matrix listed Ontap 8.2.*  I have to migrate my EV FSA data to this new NetApp in two weeks, one way or another, so hopefully this issue can be fixed.

 

Thanks,

Linda

JesusWept3
Level 6
Partner Accredited Certified

probably best thing to do is get a dtrace of MMC when you're attempting and see if its something obvious there, could possibly be just a silly firewall issue? i don't know. or could genuinely be a bug
Like if you look on that link, it references another hotfix that gave the same error when it was set to UNIX, so it could be an unusual setting thats causing it to fail etc

https://www.linkedin.com/in/alex-allen-turl-07370146

View solution in original post

plaudone
Level 5
Employee Accredited Certified

Hi lindaloo3, 

Are you able to hit the c$ share on the target server by either FQDN or IP?