Replies: 1 comment
-
|
@lh7111 Harvest collects the following memory-related metrics: We also collect a counter related to opened files on a node, which might be helpful: node_cifs_open_files. Regarding the nblade CIFS memory you mentioned, we currently do not collect it. However, we could collect it via the ZapiPerf collector. These metrics are not available via REST at the moment, and we would need to reach out to ONTAP to add that support. Below is the ZapiPerf template if you want to try this out: name: NBladeCifs
query: nblade_cifs
object: nblade_cifs
counters:
- memory_budget_consumed_by_type
- memory_budget_consumed
- memory_budget_size
- node_name => node
export_options:
instance_keys:
- nodeRegarding the EMS messages |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I couldnt find anywhere in current version where netapp memory stats (or at least cifs memory stats) are tracked. Could we consider adding this if not already present?
We had a node crash due to CIFS session over-use (triggered by too many windows 10 clients rebooting) and memory depletion to zero causing a crash/core dump of node. It would have been great to see when/where the memory started to deplete.. and track it since the last ontap upgrade.. and also see "typical" usage over time.
to see memory usage in the cifs subsystem we use the below command, maybe there is the equivalent in rest api:
good example:
(see "memory_budget_consumed" and "Session" and "memory_budget_size" counters below..)
cluster::*> statistics show -node xxxx -object nblade_cifs -instance xxxx -counter memory_budget_consumed_by_type|memory_budget_consumed|memory_budget_size -raw
Object: nblade_cifs
Instance: xxxx
Start-time: 3/10/2025 09:07:47
End-time: 3/10/2025 09:07:47
Scope: xxxx
3 entries were displayed.
not so good example showing memory approaching 50% of limit.
compare: see "memory_budget_consumed" and "Session" ..
Counter Value
memory_budget_consumed 321239168
memory_budget_consumed_by_type -
Disk File 86064
Named Pipe File 3840
File Path 28768
Tree 57424
Session 320334864
Connection 290624
Path Cache 0
File Handle Cache 5376
Large Path 0
Home Directory 800
MS-RPC 107984
Share 54048
Callback 10752
Task 20384
Vserver State 310096
Path Map 0
Super User 0
SMB2 Command 28736
SpinNp Manager 3344
ID Manager 0
Resume Handle 0
Resume Point 0
MsRpcServer 560
Persistent Memory 0
Smb2 Utility 0
FlexGroup Path/MSID Cache 0
Accessed Path List 0
NameStr Objects 0
memory_budget_size 6990688419
later.. critical failure messages prior to reboot. OS was 9.15.1P7
Nblade.cifs.budgetAllocFailure: Memory Allocation failed for SMB2 Command. The CIFS subsystem on this node has exceeded its allotment of 6990688419 bytes of node memory.
Nblade.cifsMemExceeded: The CIFS subsystem on this node has exceeded its allotment of 6990688419 bytes of node memory with currently 551 memory allocation failures since boot time. This might result in unexpected CIFS application failures.
Netapp KB:
https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Unable_to_connect_to_CIFS_Shares_and_get_error_Nblade_cifsMemExceeded_in_ONTAP
also useful for rogue clients that open too many files per KB.
Beta Was this translation helpful? Give feedback.
All reactions