Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 4 results
    • https://kb.netapp.com/Support/csm-sam/Key_hand-off_information_for_CSO
      Applies to CSO Employees Description The table below is a quick reference guide that you can use to find quick solutions and support.
    • https://kb.netapp.com/Support/General_Support/Connection_to_remote_device_using_SSH_via_PuTTY_fails_with_GSSAPI_error
      Applies to PuTTY Kerberos (GSSAPI) Authentication Issue PuTTY connection to remote server via SSH fails PuTTY console display: Server refused our key PuTTY pop-up prompt: PuTTY Fatal Error No supporte...Applies to PuTTY Kerberos (GSSAPI) Authentication Issue PuTTY connection to remote server via SSH fails PuTTY console display: Server refused our key PuTTY pop-up prompt: PuTTY Fatal Error No supported authentication methods available(server sent: publickey,gssapi-keyex,gssapi-with-mic)
    • https://kb.netapp.com/Support/General_Support/How_to_troubleshoot_a_vulnerability_concern_for_a_NetApp_product
      Applies to Product Security Incident Response Team (PSIRT) DO NOT share this with the customer Use it to assist in troubleshooting suspected vulnerabilities Security and vulnerability cases should be ...Applies to Product Security Incident Response Team (PSIRT) DO NOT share this with the customer Use it to assist in troubleshooting suspected vulnerabilities Security and vulnerability cases should be treated with special care as security teams could force removal of software and/or equipment from the customer network. Do not admit that an undocumented vulnerability exists within NetApp code unless specifically directed to do so after confirming with PSIRT email (ng-psirt) or Security Kx.
    • https://kb.netapp.com/on-prem/ontap/Perf/Perf-KBs/How_to_detect_a_saturated_SAS_port_from_a_performance_perspective
      This article describes how to check if the SAS ports are being saturated and if extra latency is being introduced by the saturated SAS ports. Expected disk latency is usually hard to tell, it has to b...This article describes how to check if the SAS ports are being saturated and if extra latency is being introduced by the saturated SAS ports. Expected disk latency is usually hard to tell, it has to be based on the comparison with the disks in the same aggregate, or disks from other aggregates with a similar workload. The saturated SAS ports would add extra latency to the front-end operations, and it would be manifested as the disk layer latency.