NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform.
You will still be able to view content, but posting and replying will be temporarily disabled.
To learn more, please review the information in this blog post.

Microsoft Virtualization Discussions

get-ncsnapmirror not working?

James_Castro
7,095 Views

anyone else seeing this?  am i missing something here?  this should be pretty straight forward right?

 

Get-NcSnapmirror | Where-Object {$_.RelationshipType -eq "load_sharing"}

 

Get-NcSnapmirror : Object reference not set to an instance of an object.

 

+ Get-NcSnapmirror | Where-Object {$_.RelationshipType -eq "load_sharing"}

+ ~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidOperation: (10.x.x.x:NcController) [Get-NcSnapmirror], NullReferenceException

+ FullyQualifiedErrorId : ApiException,DataONTAP.C.PowerShell.SDK.Cmdlets.Snapmirror.GetNcSnapmirror

 

6 REPLIES 6

JGPSHNTAP
7,086 Views

That command works fine

jpulk
7,078 Views

Another approach to this could be to have the cluster only reply with the load sharing mirrors by sumbitting the request with the query as shown below:

 

C:\PS>$query = Get-NcSnapmirror -Template
$query.RelationshipType = "load_sharing"
Get-NcSnapmirror -Query $query


Using an advanced query, get all load-sharing SnapMirror relationships.

 

SourceLocation DestinationLocation Status MirrorState
-------------- ------------------- ------ -----------
VxeRubble://costea01/vol1_LS1 VxeRubble://costea01/vol1_LS2 idle snapmirrored

 

Example taken from the Toolkit Help file.

JGPSHNTAP
7,070 Views

^^

This is old method and imho, not prefered method, by building a template.. The OP, has the correct way in my mind..

JGPSHNTAP
7,069 Views

What version of PS are you running and what version of toolkit version and Ontap

 

I'm running 

PS 3

Toolkit version: 3.3.0.65

ontap 8.3.1GA

James_Castro
7,067 Views

I think I know what the issue is.  The particular cluster I am runnin gthis on happens to be a very "busy" one.  comand works fine on other less busy clusters.  I believe the zapi is timing out even though i adjust the number of retries.  Thanks

JGPSHNTAP
7,051 Views

extended you https timeout on your connect command

 

$global:currentncontroller | select * 

 

Look for timoutmsec

 

 

Public