Forum Discussion

Pix_R's avatar
Pix_R
Level 5
2 years ago
Solved

Discovery of NetApp SVM from a new cluster (or established) on a newly created Collector.

What is the set_data_vserv_hash class used to process_vservers in Netapp and how do I set it or configured it?

I can swap a SVM already existing to the new collector but do not seem to be able to create / discovery from the cluster.

Ontapi system version is [9.8P18]
DI version is 6.3.1.14100


The syntax for the CLIs is unclear or nonfunctional as described.

(-e Query registry for security options

-l: get list of vfilers

-T : test connection with Cluster
-b : Get list of VServers.
-i <discovery option> {-v <vserver name>}: Get list of CMod Shares and NFS exports for all VServres
or for a specific VServer if -v is
provided.
Discovery options:
1: Full discovery for both CIFS shares and NFS exports.
2: Test discovery for both CIFS shares and NFS exports.
3: Full discovery for CIFS shares alone. 4: Test discovery for CIFS shares alone. 5: Full discovery for NFS exports alone. 6: Test discovery for NFS exports alone. Any other value results in full discovery of both CIFS & NFS. )

2023-07-17 15:21:46 ERROR: V-378-1318-1023: #{2688} [__parse: 1088] Bad option characher found
2023-07-17 15:21:46 ERROR: V-378-1318-1025: #{2688} [__parse: 1093] Bad option characher found
2023-07-17 15:21:46 ERROR: V-378-1318-1055: #{2688} [main: 1368] Error in parsing cmdline args
2023-07-17 15:21:46 INFO: V-378-1318-1058: #{2688} [main: 1382] netapp_util exit code: 1

 

Failure:


2023-07-17 14:58:07 INFO: V-378-1318-1029: #{7504} [__parse: 1206] filer: CLuster
2023-07-17 14:58:07 INFO: V-378-1318-1047: #{7504} [__doit: 1307] Operation code: NTAP_GET_CMOD_VSERVERS
2023-07-17 14:58:08 ERROR: V-378-1318-2077: #{7504} [open_cmod_conn: 2649] Error connecting to port 80 of filer CLuster. Err: Can't connect to host (err=10061)..
2023-07-17 14:58:08 WARNING: V-378-1318-2282: #{7504} [ntap_test_cmod_conn: 2706] Connection with cluster[CLuster] failed using transport type as HTTP. Now trying to connect cluster using transport type as HTTPS.
2023-07-17 14:58:08 INFO: V-378-1318-2238: #{7504} [open_cmod_conn: 2516] Transport style for filer CLuster is NA_SERVER_TRANSPORT_HTTPS i.e. secure connection.
2023-07-17 14:58:10 ERROR: V-378-1318-2077: #{7504} [open_cmod_conn: 2649] Error connecting to port 443 of filer CLuster. Err: Can't connect to host (err=10061)..
2023-07-17 14:58:10 ERROR: V-378-1318-2225: #{7504} [ntap_test_cmod_conn: 2743] Connection with cluster[CLuster] failed.


I suspect that perhaps the permissions granted to the user back when the environment was created have been locked down to read-only (RO) since and are interfering with proper discovery / hash creation.

Has any other customer seen this issue?

I do not think the support or Engineering are on this forum and we are left to our own devices So I'll likely open a support case while I monitor this thread.

 

Thanks
Pix.

  • Pix_R's avatar
    Pix_R
    2 years ago

    This has been confirmed to be fixed in 6.5.18000 of the Data Insight Application.

    It is not in the guides or Release Notes but Support / Engineering has closed the case.

  • meuhassan's avatar
    meuhassan
    Level 4
    2 years ago

    The set_data_vserv_hash class is used to process_vservers in Netapp. It is used to create a hash of the vservers on a cluster. This hash is used to track changes to the vservers and to ensure that the correct vservers are being discovered.

    To set or configure the set_data_vserv_hash class, you can use the following steps:

    1. Open the Netapp OnCommand System Manager.
    2. Click on the "Storage" tab.
    3. Click on the "Clusters" node.
    4. Right-click on the cluster that you want to configure the set_data_vserv_hash class for.
    5. Select the "Properties" option.
    6. Click on the "Advanced" tab.
    7. Scroll down to the "Data Vservers Hash" section.
    8. Enter the desired hash algorithm in the "Hash Algorithm" field.
    9. Enter the desired hash length in the "Hash Length" field.
    10. Click on the "OK" button.

    The set_data_vserv_hash class will now be configured for the cluster.

    The errors that you are seeing are likely due to the fact that the user that you are using to run the CLI does not have the correct permissions to connect to the cluster. You can check the permissions for the user by running the following command:

    ls -al /etc/netapp/auth.conf

    This command will show you the permissions for the auth.conf file. If the user that you are using to run the CLI does not have the correct permissions, you will need to change the permissions for the file.

    Once you have changed the permissions for the auth.conf file, you should be able to run the CLI without any errors.

    If you are still having problems, you can open a support case with NetApp. They will be able to help you troubleshoot the issue and get you up and running.

  • Pix_R's avatar
    Pix_R
    Level 5
    2 years ago

    Thanks meuhassan I was thinking more of how Veritas Data Insight reads, stores or references the hash to be able to communicate with the established SVM targets configured in the  environment. 

    We utilize a zeus like user to configure the policy and connection string and then the user is reduced to open being capable of turning the ontapi engine on or off and mounting the drives.

    There was an error since the NetApp vendor changed the queuing in a newer patch back in 2022 and Veritas released a patched version 6.3.1.14100 to coincide with this error and others appearing but still left the error unfazed in the code. 

     

    See: https://www.veritas.com/support/en_US/article.100052443

    High sustained latency after ONTAP upgrade to 9.7 P14 and above due to FPolicy EAGAIN

    Article: 100052443

    Last Published: 2022-06-16

    I currently am configured to connect under the 

    Cluster Management Interface Credentials

    Versus

    Cluster Management SSL Certificate

     

    Pix

  • Pix_R's avatar
    Pix_R
    Level 5
    2 years ago

    This has been confirmed to be fixed in 6.5.18000 of the Data Insight Application.

    It is not in the guides or Release Notes but Support / Engineering has closed the case.