Hi,
Do you think the following suggestion work for you?
Create a command that accepts the following input paramaters
- SourceCluster
- SourceVserver
- DestinationCluster
- DestinationVserver
The command would perform the following steps:
- Use the "Invoke-NcSystemApi" cmdlet to invoke the "route show -vserver $SourceVserver"
- Read the CLI output to variablize the destination, gateway and metric
- Use the "Invoke-NcSystemApi" cmdlet to invoke the "route create -vserver $DestinationVserver -destination $destination -gateway $gateway -metric $metric"
This way you wont have to create a datasource for providing the default route. In your workflow you would place the command after you have created the vserver.
Here is an example of using Invoke-NcSystemApi:
https://community.netapp.com/t5/Microsoft-Virtualization-Discussions/NetApp-PowerShell-Toolkit-4-5P1-released/td-p/138566/page/2
/Matt
If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.