Microsoft Virtualization Discussions

PSTK get-ncnetinterface doesn't return vserver for intercluster LIFs

ScottRem
836 Views

When running the PSTK cmdlet get-ncnetinterface from version 9.12.1 against an ONTAP 9.12 cluster, it leaves the vserver value null for intercluster LIFs.  I'm trying to set the intercluster interfaces to admin down, but set-ncnetinterface requires a value for vserver.  When I provide the value manually, taking it from what's displayed on the CLI, I get a rather vague error:  " WARNING: Record doesn't exist" for each intercluster LIF.

 

Here's the cluster output:

Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
----------- ---------- ---------- ------------------ ------------- ------- ----
gsdc-aut-ontap912-1
gsdc-aut-ontap912-1-01_inter1
up/up 10.216.51.169/24 gsdc-aut-ontap912-1-01
e0c true
gsdc-aut-ontap912-1-02_inter1
up/up 10.216.51.170/24 gsdc-aut-ontap912-1-02
e0c true

 

Here's the loop I'm running:

Get-NcNetInterface |% {
if ( $_.ServicePolicy -eq 'default-intercluster' ) {
Set-NcNetInterface -Controller $ClusterConnection -Vserver gsdc-aut-ontap912-1 -Name $_.InterfaceName -AdministrativeStatus down -Confirm:$false
$_.Vserver
}
}

Output for the vserver property is null.

 

All of this works just fine on ONTAP 9.7 which is before the introduction of the Service Policy property.  Regardless of how I run get-ncnetinterface, I get a null vserver property.  How can I run set-ncnetinterface without the required vserver parameter?  Even if I manually insert the vserver displayed on the command line, I get the error message mentioned above.

 

 

1 ACCEPTED SOLUTION

AmmarMhowwala
674 Views

Hello Scott,
I hope this message finds you well. I wanted to bring your attention to a situation regarding the Vserver property. In cases where the LIF is associated with the cluster level rather than the svm or data Vserver, the Vserver property tends to be null.

I believe it would be beneficial if, when modifying the LIF associated with the cluster level, the Vserver property is not to be made mandatory. Instead, having just the name of the LIF should sufficient, or there could be an option for an additional filter for the scope.

To address this concern, I plan to raise a burt to propose the implementation of these changes in the Set-NcNetInterface cmdlet. I anticipate that this adjustment will be included in the upcoming PSTK 9.14.1 release, providing a more user-friendly experience.

Thanks 

Ammar Mhowwala

View solution in original post

3 REPLIES 3

AmmarMhowwala
675 Views

Hello Scott,
I hope this message finds you well. I wanted to bring your attention to a situation regarding the Vserver property. In cases where the LIF is associated with the cluster level rather than the svm or data Vserver, the Vserver property tends to be null.

I believe it would be beneficial if, when modifying the LIF associated with the cluster level, the Vserver property is not to be made mandatory. Instead, having just the name of the LIF should sufficient, or there could be an option for an additional filter for the scope.

To address this concern, I plan to raise a burt to propose the implementation of these changes in the Set-NcNetInterface cmdlet. I anticipate that this adjustment will be included in the upcoming PSTK 9.14.1 release, providing a more user-friendly experience.

Thanks 

Ammar Mhowwala

ScottRem
638 Views

Hello Ammar,

Thank you for your prompt reply. I believe the modification to Set-NcNetInterface is what is needed. I would also like to see an option for Get-NcNetInterface to filter by service property as well. That’s not required as I can test that property but it would be a nice addition if that’s not too much to ask.

AmmarMhowwala
567 Views

Hello Scott,

I will incorporate the requested feature to the Get-NcNetInterface Cmdlet. You will be able to filter records using “ServicePolicy” property. I raised a burt for the same. This addition to the cmdlet will be available in the Pstk 9.14.1 release. 

Thanks

 Ammar Mhowwala

Public