Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 22 results
    • https://kb.netapp.com/on-prem/Switches/NetApp-KBs/How_to_collect_persistent_logging_from_CN1610_1601_switches
      Applies to CN1610 Log collection Description This article describes the procedure to collect persistent logging from CN1610/1601 switches. Persistent logging: System messages stored to local file Cont...Applies to CN1610 Log collection Description This article describes the procedure to collect persistent logging from CN1610/1601 switches. Persistent logging: System messages stored to local file Contents are preserved across a reboot Startup log and operational log: slog#.txt olog#.txt Retains current instance logs (slog0.txt and olog0.txt) and two previous instances
    • https://kb.netapp.com/Legacy/ONTAP/Clustered_Data_ONTAP_8/How_to_disable_aggregate_snapshots_in_Clustered_Data_ONTAP_8
      The default configuration for aggregate level snapshots in clustered Data ONTAP is as below: If the aggregate is becoming full, then Data ONTAP will automatically start deleting the snapshots, and no ...The default configuration for aggregate level snapshots in clustered Data ONTAP is as below: If the aggregate is becoming full, then Data ONTAP will automatically start deleting the snapshots, and no space will be reserved for the aggregate snapshots. Starting in Data ONTAP 8.3.1, you can no longer create aggregate Snapshot copies using the Data ONTAP command-line interface (CLI).
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/How_does_showmount_work_with_clustered_Data_ONTAP
      The showmount option allows NFS clients can use the showmount -e command to see a list of exports available on an NFS server vserver nfs modify -vserver <vserver> -showmount {enabled\disabled} In ONTA...The showmount option allows NFS clients can use the showmount -e command to see a list of exports available on an NFS server vserver nfs modify -vserver <vserver> -showmount {enabled\disabled} In ONTAP 9.6 and later, the paths displayed can be restricted to / only, use the following commands: vserver nfs modify -vserver <vserver> -showmount disabled After showmount is enabled, clients will be able to query data LIFs for export paths
    • https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/How_to_utilize_and_set_up_portsets_in_clustered_DATA_ONTAP_using_CLI
      After you bind a portset to an igroup, only paths to the LIFs inside the portset will be accessible to the host. (All LIFs will still be advertised in a SendTargets response, to limit the number of LI...After you bind a portset to an igroup, only paths to the LIFs inside the portset will be accessible to the host. (All LIFs will still be advertised in a SendTargets response, to limit the number of LIFs advertised, consider either on how Selective LUN Mapping (SLM) works or how to limit iSCSI initiator access to target portals.
    • https://kb.netapp.com/on-prem/ontap/DP/NDMP/NDMP-KBs/When_to_restart_the_NDMPD_service_in_Data_ONTAP
      The ndmpd start/stop command will also disable the NDMP services on all the vFiler units hosted on the node. The ndmpd terminate command terminates all the active NDMP sessions on the node and also ex...The ndmpd start/stop command will also disable the NDMP services on all the vFiler units hosted on the node. The ndmpd terminate command terminates all the active NDMP sessions on the node and also expires the NDMPD daemon. The system services ndmp terminate command terminates all the active sessions on the node and also expires the NDMPD daemon.
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/How_to_calculate_SnapMirror_or_SnapVault_throughput_for_performance
      To determine throughput, the fields to note are the Transfer Size and the Transfer Duration. The snapmirror show -instance command can be used to list the Last Transfer Size and Last Transfer Duration...To determine throughput, the fields to note are the Transfer Size and the Transfer Duration. The snapmirror show -instance command can be used to list the Last Transfer Size and Last Transfer Duration. This output will show you the Last Transfer Size and the Last Transfer Duration which you can use to calculate the last transfer throughput This output will show you the Last Transfer Size and the Last Transfer Duration which you can use to calculate the last transfer throughput.
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/How_to_use_the_snapmirror_restore_command
      Applies to ONTAP 9.x SnapMirror Description This article describes the procedure on how to use the "snapmirror restore" command.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/How_to_enable_SNMP_v3_in_clustered_Data_ONTAP
      This article includes instructions on enabling and configuring SNMP v3 in cluster mode and getting DFM to recognize SNMP v3 in clustered Data ONTAP. Please choose an authentication protocol (none, md5...This article includes instructions on enabling and configuring SNMP v3 in cluster mode and getting DFM to recognize SNMP v3 in clustered Data ONTAP. Please choose an authentication protocol (none, md5, sha) [none]: md5 Note: The Error below occurs when the Authentication type of the SNMP host does not match the type ( -authmethod) selected for the Enabled SNMPv3 user account created above: Note: SNMP v3 in DFM requires a username with a password (eight characters in length).
    • https://kb.netapp.com/Legacy/ONTAP/7Mode/How_to_configure_LIF_failover_destinations_in_Data_ONTAP_8.1_Cluster-Mode
      Applies to Clustered Data ONTAP 8.1 Description This article describes the procedure that should be followed to configure Logical Interface (LIF) failover destinations in Data ONTAP 8.1 and Data ONTAP...Applies to Clustered Data ONTAP 8.1 Description This article describes the procedure that should be followed to configure Logical Interface (LIF) failover destinations in Data ONTAP 8.1 and Data ONTAP 8.1.1 Cluster-Mode.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/How_to_determine_the_node_port_or_lif_to_which_a_client_should_be_connected
      In Data ONTAP Cluster-Mode, many clients can be connected to various nodes in a cluster for NAS access. There are scenarios where it might be useful to know the node, port, or lif to which a specific ...In Data ONTAP Cluster-Mode, many clients can be connected to various nodes in a cluster for NAS access. There are scenarios where it might be useful to know the node, port, or lif to which a specific client is connected. If a specific client has connectivity issues, it is necessary to determine the node on which you can run a packet trace. If a specific client is running an exceptional load, it might help to determine the lif to which it is connected for load balancing purposes.
    • https://kb.netapp.com/Legacy/ONTAP/7Mode/How_to_perform_64-bit_aggregate_conversion_using_CLI_in_Data_ONTAP_7-Mode_and_clustered_Data_ONTAP
      In order to have aggregates larger than 16 TB, convert a 32-bit aggregate to 64-bit; if this is not a requirement, there is no reason to convert a 32-bit aggregate to 64-bit. In all versions prior to ...In order to have aggregates larger than 16 TB, convert a 32-bit aggregate to 64-bit; if this is not a requirement, there is no reason to convert a 32-bit aggregate to 64-bit. In all versions prior to clustered Data ONTAP 8.2.1, 64-bit aggregate conversion is triggered by adding a single disk to an aggregate that is 16 TB; in 7MODE prior to 8.1.4P4, you must have enough disks to exceed 16 TB before you can upgrade the aggregate to 64 Bit.