2017-01-05 11:38 AM - edited 2017-01-06 08:08 AM
Recently I have installed an additional cluster machine into an existing backup cluster. We now have a total of 3 clusters. Cluster A is a filer that Snapvaults to Cluster B. I have added a new machine Cluster C into the setup for backup. Cluster B will Snapmirror to Cluster C. I have purchased and installed Snapmirror/vault licenses on all 3 machines. Everything is working nicely between A and B. I have setup the intracluster relationship between B and C and the relationship status is good between the new machines.
When I try to create a Snapmirror relationship between B and C after a long pause in the ONTAP 9 GUI reports "Snapmirror license is not available" warning in the GUI. I have double checked in the GUI my license for Snapmirror on all machines and they are installed correctly. Does this mean I require an additional Snapmirror license for the B and C clusters?
*Cluster A* -- Snapvault -- *Cluster B* -- Snapmirror -- *Cluster C*
Filer Backup node 1 Backup node 2
Solved! SEE THE SOLUTION
2017-01-11 09:19 PM
2017-01-12 11:18 AM
With the help of tech support we solved this. It turned out to be an MTU issue on the IC lif. Changing it to 1500 from 9000 solved the license availability error.
2017-07-05 03:00 AM
Hello guys, I had the same problem and I have resolved with change mtu from 9000 to 1500.The speed network port for our storage netapp is 1000Mb.
Thanks for your help.
2017-10-18 03:10 PM
I have two FAS2650 in different locations replicating to FAS2520 in another third location.
One of them fails when I try to create the protection relationship with the license error.
The unique difference between two storage is the ethernet connection.
I Explain that.
The replication port of one FAS is 1GB and the Destination FAS2520 is connected to a 100MB. In this case the create the protection relationship proccess works fine.
The replication port of second FAS is 10GB DAC type and the destination FAS2520 is the same as above. In this case the create protection relationship proccess fails with the license error.
2017-10-18 10:08 PM
I think it might be better to make a new post instead of replying to this one. In general, the port speed difference will not cause a license error.
I would suggest you run "system license show" on all three clusters and verify that there are snapmirror licenses installed for each node on each cluster - the system will let you install licenses for nodes not in the cluster, so if there is any mixup, the licenses may show but not be in effect.
2017-11-30 02:06 AM
We have all the snapmirror licenses in place and healthy.
We have all the intercluster lifs at 9000.
Any other suggestions?
This just started happening for us, was working just fine before.
2018-01-12 10:48 AM
We also bumped into another situation were we could talk to only one of the nodes on the source cluster. It turns out that it was a bug in 9.2.
Netapp Tech Support:
The error "snapmirror license not available" is due to an OnCommand/API bug. It occurs when an attempt to create a SnapMirror relationship within System Manager while having non-1500 MTUs set.
To resolve the issue, create and initialize the relationship on the destination cluster command-line and then you will be able to resume normal operations/management on the GUI moving forward.