Effective December 3, NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources.For accounts that did not pre-register (prior to Dec 3), access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity.To learn more, read the FAQ and watch the video.Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.
I believe this is a result of a documentation "bug".
There are two different versions of the API which the New-NcVolClone cmdlet consumes, one at the cluster level and one at the SVM level. The SVM level API uses the two parameters you're specifying (JunctionActive and JunctionPath), however the cluster level API does not. When doing a cross-SVM volume clone the cluster level API must be used.
Here is how I believe the parameter sets for the two versions of the API should work...
The documentation for the New-NcVolClone cmdlet also includes two parameters, CachingPolicy and Option, which have no equivelant in the ONTAP 9.3 ZAPI docs. This could mean a few things, the most likely is that those options existed in earlier versions of ZAPI and are still there for legacy reasons, but could also be some "magic" happening in the cmdlet to apply additional options to the volume after it's cloned for convenience. It could also simply be a(nother) documentation bug.
I'm going to create a bug for this issue. If you are willing to PM me your mailing address, I'm happy to send you some stickers as a "bug bounty" : )
Hope that helps.
If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO.