would be helpful to see the full command. likely a typo.
The first disk you have oc.32 and probably should be 0c.32
(zero instead of the letter o)
or try
aggr create aggr_name -t raid_dp -T FC-AL -r 16 -n 32
(create an aggr using RAID-DP, type FCAL, 16 disks per raid group, use 32 disks, show-me but not not apply)
If you like the output, then drop the -n and run again.
Also, why not use the GUI?
Hi Donny,
I've updated my FAS Arrays during september as I said i my earlier post, but I observe the same issue, is there any other test I can do to debug the situation (or maybe au workaround with another cmdlet)?
thanks in advance,
FAS2620 in 9.5P7
powershell module : 9.6.0
powershell server : Windows 2012R2 (6.3.9600) or Windows 2016
regards
Sorry for the delay. On the larger than 1024GB volume, can you try to collect the volume size from Get-NcVol instead to see if that works:
Get-NcVol -Vserver <vserver> -Volume <volume> | fl TotalSize
It'll (theoretically) report the volume size in bytes, which should be a non-zero number. If that doesn't work, we can try to query it via the ZAPI call directly with Invoke-NcSystemApi and see if that yields any different output.
I'm trying to use the powershell toolkit to automate some snapshot procedures, and it works fine with a admin account, but I can't seem to find the correct permissions to get it to work. The role I have is
::> security login role show
Role Command/ Access
Vserver Name Directory Query Level
---------- ------------- --------- ----------------------------------- --------
nap-svm01 vmwsnapshotonly
DEFAULT none
version all
volume all
volume snapshot -volume *snap* all
and that doesn't work. I keep getting
New-NcSnapshot : not authorized for that command
At C:\Users\Downloads\oracle-snapshot.ps1:137 char:9
+ New-NcSnapshot $volume $volume$(get-date -f MM-dd-yyyy_HH_mm_ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (111.11.11.11:NcController) [New-NcSnapshot], EAPIPRIVILEGE
+ FullyQualifiedErrorId : ApiException,DataONTAP.C.PowerShell.SDK.Cmdlets.Snapshot.NewNcSnapshot
we have a NetApp 9.6P3 in production, needs to enable aggr encrption. how can we do it without downtime? Looks we have to empty aggregate before we can enable the encryption on an aggregate. we can LUNs presented to hosts from both aggregates on a HP pair.
thanks
Can I encrypt an existing volume in place with NAE in ONTAP 9.6?
Answer: No. You need to do one of the following options mentioned below in the kb.
if i remember right, on new version (forgot which), we can enable NVE without moving a volume. if this is true, can we enable all data vols with encryption and move root vols to parter's aggr, then we can enable encryption on aggr. is that possible?
thanks.
Hi Donny,
Thank you, this command works well.
What i'm trying to do initialy was a
Set-NcVolSize -NewSize <newSize> -Name <volname> -VserverContext <vservename>
but this command fail with the same behaviour as Get-NcVolSize
Do you also have a command to bypass this one?
thanks in advance
Yann
Try the following command on SSH.
security audit log show
To see what capability it's missing.
Yes, I think you are talking about - In-place encryption of existing volumes, feature introduced in ONTAP 9.3.
Procedure to transition an existing un-encrypted volume:
A) Prior to 9.3 = 'volume move' command
B) 9.3 later = 'volume encryption conversion start'
Some Kbs for referemce, hope it helps.
How to configure NetApp Volume Encryption
https://kb.netapp.com/app/answers/answer_view/a_id/1030618
Is it possible to tune the NetApp Volume Encryption conversion process?
https://kb.netapp.com/app/answers/answer_view/a_id/1086286
Considerations when using Netapp Volume Encryption (NVE)
https://kb.netapp.com/app/answers/answer_view/a_id/1074806
Difference:
Regarding 'root' vol :
There are two types in cDOT/ONTAP
1) Controller root vol (Aggregtates) = Not encrypted in both NAE & NVE
2) SVM root vol = encrpted in NVE only.
KB: 1086920 [To be honest, I will be more concern with data volumes]
Thanks!
We wanted to decommission nodes and LIF's homed onthese nodes. The problem is that some VMware NFS Datastores and also NFS file systems are using these LIF's/IP's, is there any way non-discruptively remove these LIF's/IP's?
My understanding is that we would be downtime to remount NFS datastores or file systems.
Thanks!
Hi lad,
Basically you are abble to move the lif from nodes to nodes wich is a non disruptive process. So if you found that you need to keep some lifs move them to another node.
BTW you can validate lif usage using the CLI: network connection active
Cheers !
dbenadib ,
There were concern with that approach: All network trafic will be going to these two nodes that I move these LIF's to, then it would cause unbalanced load.
So, from long run, it'd better to clean them up, and to avoid confusion. To remove them, there will be a downtime.
Make sense?
Can you clarify ?
How much node do you have in your cluster ?
Which kind of maintenance are you performing ?
wrote: dbenadib ,
There were concern with that approach: All network trafic will be going to these two nodes that I move these LIF's to, then it would cause unbalanced load.
So, from long run, it'd better to clean them up, and to avoid confusion. To remove them, there will be a downtime.
Make sense?
Try with Invoke-NcSystemApi like this:
$Volume = "<your volume>" $NewSize = "<desired size>" $Vserver = "<your SVM>" $Request = @" <volume-size><new-size>$NewSize</new-size><volume>$Volume</volume></volume-size> "@ Invoke-NcSystemApi -Request $Request -VserverContext $Vserver
I have total of 8 nodes in the cluster. Planning on replacing two of them by adding two new ones first, then take two out. In the end, there would be still 8 nodes.
Understood I can lif move all lif's to the other two nodes(HA) without interruption. However, as I said, move lif's will also move all connections along with NFS datastores and file systems , it will put a lot of loads to those two nodes, causing unbalanced load.
I am thinking to manuall umount those NFS's connecting to two nodes going away, and remount them to two new nodes. That will have service downtime.
Make sense?
I would do the following:
Add 2 new nodes (Cluster will have 10 Nodes)
Validate that new nodes are correctly connected to relvant network
Create intercluster lifs (if Snapmirror)
Move all volumes to the new HA Pair 1:1 (that way you will ensure the same level of performance)
Move / Rebalance all lifs to the new HA-Pair 1:1 (that way you will ensure the same level of performance)
Ensure that no volume reside in the old HA-Pair
Clean-up old nodes
remove intercluster lifs
delete aggregates
disable HA
Move Epsilon out of this HA Pair
Evict node by node
Your steps looks very well.
However, I have not sure an information with you: two new nodes have already added into the cluster, and now there are 10 nodes with new LIF's and new everything. Loads are already balanced across all 10 nodes.
Now, i just need to remove two old nodes. I can move all LIF's to the other nodes, which will cause unbalancing, and yet leave all old LIF's with old name convention (ex, nfs-lif-node1, nfs-lif-node2..) in the cluster forever, whereas node1 and node2 should be already gone. That is why I am thinking to take a downtime and remove all old lif's...
Make sense?
it makes sense.. the only issue with that is the downtime...
If you want to avoid downtime U have to migrate lifs. after lifs will be balanced across nodes (for better perf ensure that lif and volumes reside in the same node) and rename it according to your naming conv.
BR
Thank You Donny, your workaround is working.
any idea why both commandlet Get-NcVolSize an Set-NcVolSize will fail in my context?
thanks
Yann