Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request for NAS connections and iscsi sessions counts metric #3136

Open
summertony15 opened this issue Sep 5, 2024 · 9 comments
Open
Assignees
Labels
24.11 customer feature New feature or request

Comments

@summertony15
Copy link

summertony15 commented Sep 5, 2024

Describe the solution you'd like
NetApp has the limitation of Maximum number of connection -- NAS per node,
Here is the HWU example: https://hwu.netapp.com/Controller/Index?platformTypeId=30310846&platform=29266985&os=34942206#none
截圖 2024-09-10 15 06 17
And here is the description: Maximum number of NAS (SMB and NFS) TCP connections that a node can support

Also, we have a maximum number of iSCSI sessions,
截圖 2024-09-10 15 51 12

We want to monitor these two value, in case they reach the limits.
I need both of them, thanks
Best to have both ZAPI and REST templates.

@summertony15 summertony15 added the feature New feature or request label Sep 5, 2024
@rahulguptajss
Copy link
Contributor

Discord discussion here

@cgrinds cgrinds added the 24.11 label Sep 5, 2024
@summertony15 summertony15 changed the title Feature request for NFSClients counts and iscsi sessions counts metric Feature request for NAS connections and iscsi sessions counts metric Sep 10, 2024
@summertony15
Copy link
Author

Update the request which needs two values mapping to the values shown in HWU as the description.

@rahulguptajss
Copy link
Contributor

@summertony15

Could you share the time taken and the number of records returned by the following commands in the relevant environment you want to track?

Make sure to replace USER, PASS, and CLUSTER_IP with the appropriate values.

  1. NFS Connected Clients (without records):

    curl -w "Total time: %{time_total}\n" -s -k -u USER:PASS 'https://CLUSTER_IP/api/protocols/nfs/connected-clients?return_records=false'
  2. NFS Connected Clients (with records):

    curl -w "Total time: %{time_total}\n" -s -k -u USER:PASS 'https://CLUSTER_IP/api/protocols/nfs/connected-clients?return_records=true&fields=client_ip,node.name,protocol,server_ip,svm.name,volume.name'
  3. iSCSI Sessions (without records):

    curl -w "Total time: %{time_total}\n" -s -k -u USER:PASS 'https://CLUSTER_IP/api/protocols/san/iscsi/sessions?return_records=false'
  4. iSCSI Sessions (with records):

    curl -w "Total time: %{time_total}\n" -s -k -u USER:PASS 'https://CLUSTER_IP/api/protocols/san/iscsi/sessions?return_records=true&fields=tsih,target_portal_group,initiator.name,isid,svm.name'

Thanks.

@summertony15
Copy link
Author

Hi @rahulguptajss
command1
command2

command3 command4

@rahulguptajss
Copy link
Contributor

Thanks @summertony15 . So, if we export NFS and iSCSI connection counts at the cluster level, will that be good?
CIFS (node_cifs_connections) is already present which includes all relevant protocols.

@summertony15
Copy link
Author

I think node level is better, since the limitation is by node.
We can count the cluster level, by sum up by each node

@rahulguptajss
Copy link
Contributor

Sure Thanks.

@rahulguptajss
Copy link
Contributor

ISCSI seems to be at svm level. I don't see any node information in API api/protocols/san/iscsi/sessions.

@rahulguptajss
Copy link
Contributor

@summertony15 Could you also run the commands shared in this comment on an ONTAP system with a large number of connections?

The reason for this request is that we want to measure the time taken for these calls.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
24.11 customer feature New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants