Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 13 results
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Takeover_not_possible_due_to_degraded_mode_mailbox_disks
      This KB provides the solution for Takeover not possible due to degraded mode (mailbox disks). It is linked to the Takeover not possible Resolution Guide.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/How_to_use_the_Volume_Recovery_Queue
      A volume delete request against a volume that has type RW or DP (as seen in volume show command output) causes that volume to be moved to a partially deleted state. By default, it is retained in a rec...A volume delete request against a volume that has type RW or DP (as seen in volume show command output) causes that volume to be moved to a partially deleted state. By default, it is retained in a recovery queue for at least 12 hours before being fully deleted.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Takeover_not_possible_due_to_interconnect_errors
      This KB provides the solution for Takeover not possible due to interconnect errors. It is linked to the Takeover not possible Resolution guide.
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Takeover_not_possible__disk_shelf_is_too_hot
      This KB provides the solution for Takeover not possible due to disk shelf being too hot. It is linked to the Takeover not possible Resolution Guide.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Takeover_not_possible_due_to_version_mismatch
      This KB provides the solution for Takeover not possible due to version mismatch. It is linked to the Takeover not possible Resolution Guide.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/How_to_manually_collect_logs_and_copy_files_from_an_ONTAP_storage_system
      /mroot/etc/crash is the location for core dump files, and the preferred location to store packet traces. Occasionally, the subset of logs supplied by AutoSupport might not satisfy troubleshooting requ.../mroot/etc/crash is the location for core dump files, and the preferred location to store packet traces. Occasionally, the subset of logs supplied by AutoSupport might not satisfy troubleshooting requirements and copying logs and files form the system is needed. This article describes methods for copying logs and files from an ONTAP storage system.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Network_interface_failover_policies_behavior_and_uses
      Failover Groups may be smaller than the broadcast domain, such as a failover group containing ports that have the same link speed within a broadcast domain. The failover targets for a LIF (the set of ...Failover Groups may be smaller than the broadcast domain, such as a failover group containing ports that have the same link speed within a broadcast domain. The failover targets for a LIF (the set of ports to which a LIF can failover) is determined by applying the LIF's failover policy to the LIF's failover group in the broadcast domain.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Takeover_not_possible_due_to_local_node_about_to_halt
      This KB provides the solution for Takeover not possible due to local node about to halt. It is linked to the Takeover not possible Resolution Guide.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Overview_of_ONTAP_Logs
      The audit log records the commands sent to the cluster, the user who is sending them, and the success or failure of the command. ONTAP logs management activities that are performed on the cluster, for...The audit log records the commands sent to the cluster, the user who is sending them, and the success or failure of the command. ONTAP logs management activities that are performed on the cluster, for example, what request was issued, the user who triggered the request, the user's access method, and the time of the request.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Takeover_not_possible_as_partner_node_halted_after_disabling_takeover
      This KB provides the solution for Takeover not possible as partner node halted after disabling takeover. It is linked to the Takeover not possible Resolution Guide.
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Takeover_not_possible_due_to_local_node_already_in_takeover_state
      This KB provides the solution for Takeover not possible due to local node already in takeover state. It is linked to the Takeover not possible Resolution Guide.