thanks. obviously missed that. :P
↧
Re: 7MTT Snapmirror replication and network compression
↧
how to change the espsilon node using powershell cmdlets
Hi All,
I'm trying to automate the ontap upgrade process and i need to trasnfer the epsilon node to another node. I know we can use Invoke-NcSsh and then use the normal ontap command but i want to achive it using PS cmdlet so that i can use the previous varibales. I tried Set-Ncnode but there is no option to trasnfer the epsilon. Any help is highly appricaited.
Here is my code.
#ClusterName
$Cluster=Read-Host"Enter the cluster name to connect"
#credentials to connect the cluster
$creds=Get-Credential-UserName"admin"-MessageNull
foreach ($itemin$Cluster) {
Connect-NcController$item-Credential$creds}
$epsilonnode=Get-NcNode|where {$_.IsEpsilonNode -eq$true}
Write-Host"The Epsilon node is : $epsilonnode"
$nonepsilonnode= Get-NcNode|where {$_.IsEpsilonNode -eq$false}
$nonepsilonnode
Read-Host-Prompt"Press any key to continue"
$newepsilonnode=Read-Host-Prompt "Enter the node name to trasnfer the Epsilon :"
Write-Host"Trasnferring the Epsilon to $newepsilonnode ...."
↧
↧
Re: how to change the espsilon node using powershell cmdlets
Int ONTAP via CLI, I do not believe it is a one-step process.
You unset (make Epsilon FALSE) it from the node first.
Then Assign (make Epsilon TRUE) it to another node.
Hopefully that helps!
↧
Re: how to change the espsilon node using powershell cmdlets
Hi TMAC,
I am aware the steps in ONTAP CLI but I am looking for a powershell Cmdlet to achieve it.
I cannot use invoke-ncssh cmdlet followed by ontap cli commands because ontap cli doesn't accept $variables.
I want a Powershell cmdlet by using which I can change the epsilon assignments.
Thanks.
↧
ontap 9.5 - different Algorithms for Flash Cache and READS from SSD ? - did anyone notice a change
OK I noticed a change in the way NABOX , Graphana , Harvest displays metrics related to Flash Cache and READS from SSD after CDOT upgrade from 9.4X to 9.5X - 3 different clusters / 3 diff upgrate dates / all display same characteristics - so is it just the way NABOX charts these metrics now or was the Algorithms for Flash Cache and READS from SSD modified in 9.5X ? thanks.
NASI
successful 9.4P5 3/2/2019 3/2/2019 nasi-04 9.4P3 9.4P5 00:19:39 01:59:17
successful 9.5P1 4/7/2019 4/7/2019 nasi-04 9.4P5 9.5P1 09:20:48 10:59:42
NANW
successful 9.4P5 2/23/2019 2/23/2019 nanw-04 9.4P3 9.4P5 04:03:40 05:46:12
successful 9.5P1 3/16/2019 3/16/2019 nanw-04 9.4P5 9.5P1 01:16:28 03:35:24
NAFH
successful 9.4P5 3/2/2019 3/2/2019 nafh-04 9.4P3 9.4P5 00:32:41 02:14:18
successful 9.5P1 4/14/2019 4/14/2019 nafh-04 9.4P5 9.5P1 19:43:05 21:31:46
↧
↧
Re: ontap 9.5 - different Algorithms for Flash Cache and READS from SSD ? - did anyone notice a chan
Did you happen to update the SDK to 9.5 for NABOX?
↧
Re: ontap 9.5 - different Algorithms for Flash Cache and READS from SSD ? - did anyone notice a chan
Thanks TMAC - here are our versions on the NABOX side of the house
( BTW - we are using the NABOX ISO image )
NAbox 2.5 (2018-12-16).
NMSDK 9.4.
Harvest 1.4.
NMSDK 9.4.
Harvest 1.4.
↧
Re: ontap 9.5 - different Algorithms for Flash Cache and READS from SSD ? - did anyone notice a chan
yeah... update the SDK & the harvest versions. Both behind!
Up to you if you want to update the NABOX image itself!
↧
Re: ontap 9.5 - different Algorithms for Flash Cache and READS from SSD ? - did anyone notice a chan
OK Will do, thanks, will report back later.....
↧
↧
Re: ontap 9.5 - different Algorithms for Flash Cache and READS from SSD ? - did anyone notice a chan
TMAC - thanks for your help, thru this tread I was able to update the SDK componenet and the Harvest Component - so that was a plus 
- as far as the graphs related to " Flash Cache and READS from SSD" - it looks like the "scale" changed after the upgrade I mentioned - also I remember for the last 4 or 5 ONTAP versions the oncommand system manager displayed "flash cache" info for the AFF controllers when it should not have( AFF systems do not have "Flash Cache" cards ). So when all is said and done after the ONTAP upgrade to 9.5X the oncommand system manager DOES NOT display "flash cache" info for the AFF controllers and that is now correctly reflected in the NABOX charts / graphs.
pic before and after ONTAP upgrade ( we see stats from all 4 nodes - 2 AFF and 2 HYBRID )
pic after ONTAP upgrade ( we see stats from 2 nodes - only the 2 HYBRID )
↧
Why does the amount of available storage shown differ?
We have a FAS2620 running OnTap 9.5P3 set up with two aggregates, A and B. When I go to the Dashboard on the web page and look at cluster overview, it shows that A is 61% used, and B is 44% used. However when I go to the Aggregates page under storage, it shows that A is 91% used and B is 52% used.
Why is there such a disparity between the two displays and which one is likley to be correct?
↧
Re: Why does the amount of available storage shown differ?
I would guess maybe a bug/glitch in the GUI? can you post screenshots?
what's "aggr show" say?
↧
Re: Why does the amount of available storage shown differ?
Here's the dashboard:
And here's the aggregate tab:
show aggregate agrees with the information displayed on the aggregate tab. However there are a couple of strange things:
1) I deleted a volume that had 8TB of data... and only 2TB of available space showed up.
2) When I querey the volumes for physical space used, it is not equal to what I am seeing with show aggregate, it is equal to what I'm seeing with the dashboard.
↧
↧
Re: Why does the amount of available storage shown differ?
Re: the GUI displays it is odd. I checked a 9.1 lab filer i have and it's different too. not as much as yours though. I'll see if I can do some deeper digging.
1) Depends what the "used size" size is. "vol show -fields used"
2) It never will, there is metadata hanging around WAFL that will add additional space.
↧
not able to bring the volume online.
Hi All,
I am trying this code to bring the offline volumes to online state but i am seeing an error. Any help is much appriciated.
#Verify the volume state
$onlinevolumes = Get-NcVol
$onlinevolumes
if ($offlinevolumes = Get-NcVol |where {$_.State -ne "online"}) {
Write-Host "Volumes found which is/are not in online state, non online volumes are:$offlinevolumes"
$userresponse=Read-Host -Prompt "Press any to bring the volumes online"
Set-NcVol ($offlinevolumes |select Name) -Online }
Else {Read-Host -Prompt "No non online volumes found,press any key yo continue"}
-------------------------------------------------------------------------------------------------------------------
Here is the error:
Set-NcVol : Cannot convert 'System.Object[]' to the type 'System.String' required by parameter
'Name'. Specified method is not supported.
At line:13 char:11
+ Set-NcVol ($offlinevolumes |select Name) -Online }
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (
[Set-NcVol], ParameterBindingException
+ FullyQualifiedErrorId : CannotConvertArgument,DataONTAP.C.PowerShell.SDK.Cmdlets.Volume.Set
NcVol
↧
Re: not able to bring the volume online.
I think you will need to loop through each volume for the Set-NcVol command. That command is expecting a single volume, I believe. You also don't need '|select Name' as part of the command.
Something like...
foreach ($volume in $offlinevolumes) {
Set-NcVol $volume -online
}
↧
Re: not able to bring the volume online.
Thanks Sean.
You are right it needed a foreach loop.
↧
↧
wafl.readdir.expired: A READDIR file operation has expired for the directory associated with volume
Hello;
I am running 9.3P8. I have a volume that is 1.98TB with 12 million files.
I am getting the following error listed below. Quesitons: Is part of bug 1055262? How can I tell is this is a sparce file issue or a large directory issue? Would this impact permforance?
If this is a sparce file issue, would a volume move be to fix the problem?
Peggy
Error:
wafl.readdir.expired: A READDIR file operation has expired for the directory associated with volume BBBB/@vserver:82848f81-2b18-11e5-a0ee-00a0986a1129 Snapshot copy ID 0 and inode 21505.
This message occurs when a READDIR file operation has exceeded the timeout that it is allowed to run in WAFL(R). This can be the result of very large or sparse directories, and corrective action is recommended
Action:
You can find information specific to recent directories that have had READDIR file operations expire by using the 'diag' privilege nodeshell CLI command: "wafl readdir notice show" If a directory is indicated as sparse, it is recommended that you copy the contents of the directory to a new directory to remove the sparseness of the directory file. If a directory is not indicated as sparse and the directory is large, it is recommended that you reduce the size of the directory file by reducing the number of file entries in the directory.
↧
OnTAP Select Deploy Placement for a 2 node Cluster
Hello,
We will likely deploy our first OnTAP Select 2-node cluster soon at one of our small branch offices. The office in question will have a 2 node VMware cluster to run it on. I'm confused regarding where I should place the OnTAP Deploy VM. I know it is used as a witness. We could host it at our main headquarters, however there are occasional brief losses of connectivity between the offices that would cause an issue if there had to be an unplanned failover at the same time. If I understand correctly, I can't deploy it on one of the two existing hosts because it creates a SPOF. We aren't going to buy a server and stand up a new host just for this one VM. Any thoughts or suggestions? I'm especially interested in what others have done.
↧
Re: Automatic node referrals CIFS and support for Hyper-V
↧