This started out as WFA inquiry but I can reproduce the problem with just PowerShell. I am attempting to create a new LIF after creating a new SVM. The issue seems to have to do with Routing-Groups which were depricated in ONTAP 8.3 and even more so in ONTAP 9.0. The New-NcNetInterface cmdlet has a -RoutingGroup parameter which I'm leaving off. ONTAP 9.0 seems to want or need it but I have no idea what to give it since there are no routing-groups in ONTAP 9.0. ONTAP 8.3.2 seems to still support the concept (i.e.; Get-NcNetInterface will return the routing-group attribute of a LIF with a name like the old d192.168.0.0/24) but ONTAP 9.0 returns nothing ... hence I do not have anything to feed the -RoutingGroup parameter. Here is my testing. Am I missing something?
PS C:> $psversiontable.PSVersion
Major Minor Build Revision ----- ----- ----- -------- 5 1 14393 693
PS C:> Get-NaToolkitVersion
Major Minor Build Revision ----- ----- ----- -------- 4 1 0 0
PS C:> PS C:> # First Against a 9.0 cluster (NOTE: the vserver is pre-existing at this point) PS C:> PS C:> Connect-NcController lt-stor.tnt.com -cred $cred
Name Address Vserver Version ---- ------- ------- ------- lt-stor.tnt.com 192.168.0.200 NetApp Release 9.0: Fri Aug 19 06:39:33 UTC 2016
PS C:> New-NcNetInterface -Name lt-dscdrtest004 -Vserver lt-dscdrtest004 -role data -node lt-stor-01 -Port e0d -Address 192.168.0.214 -Netmask 255.255.255.0 -DataProtocols @('cifs','nfs') New-NcNetInterface : Internal error. Routing group not found. Contact technical support for assistance. At line:1 char:1 + New-NcNetInterface -Name lt-dscdrtest004 -Vserver lt-dscdrtest004 -ro ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (lt-stor.tnt.com:NcController) [New-NcNetInterface], EAPIERROR + FullyQualifiedErrorId : ApiException,DataONTAP.C.PowerShell.SDK.Cmdlets.Net.NewNcNetInterface
PS C:> PS C:> PS C:> # Now Against an 8.3.2 cluster (NOTE: the vserver is pre-existing at this point) PS C:> PS C:> Connect-NcController hq-stor.tnt.com -cred $cred
Name Address Vserver Version ---- ------- ------- ------- hq-stor.tnt.com 192.168.0.120 NetApp Release 8.3.2: Tue Feb 23 23:35:06 UTC 2016
Good question, and no, there is no route (yet). I was thinking that would be done after creating the LIF since that is what some code Im looking at does (from a WFA command). But I re-tested creating a route before creating the LIF ... but it still complains about wanting a Routing-Group (or -RoutingGroup param). Maybe
Thanks Andrew ... could you do me a Get-NcNetRoute on that same system for comparison w/mine. I'm beginning to believe it could be a config issue. I had all this working w/8.3.2 and since I've introduced 9.0 in the mix I'm hitting this.
Also, on -NetMask versus -NetMaskLength ... I thought (possibly mistaken) -NetMaskLength was only for IPv6, so I set -NetMask (255.255.255.0) and either leave -NetMaskLength blank or pass 0 sometiems. I notice you just use -NetMaskLength 24 by itself ... in the IPv4 case does that get treated as 255.255.255.0?