Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 11 results
    • Panic after syncmirror plex failure - PANIC MSG = Process mgwd unresponsive
      https://kb.netapp.com/Cloud/Cloud_Volumes_ONTAP/Panic_after_syncmirror_plex_failure_PANIC_MSG_Process_mgwd_unresponsive
      Applies to Cloud Volumes ONTAP (CVO) Amazon Web Services (AWS) Issue MGWD panic after losing access to several disks PANIC MSG = Process mgwd unresponsive for 839 seconds (mgwd startup: "(4341)") in p...Applies to Cloud Volumes ONTAP (CVO) Amazon Web Services (AWS) Issue MGWD panic after losing access to several disks PANIC MSG = Process mgwd unresponsive for 839 seconds (mgwd startup: "(4341)") in process nodewatchdog on release 9.8P1 (C)
    • Volume SnapMirror not replicating - No more snapshots available
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Volume_SnapMirror_not_replicating_No_more_snapshots_available
      Applies to ONTAP 9 SnapMirror Maximum allowed Snapshots Issue SnapMirror relationship is not replicating with error: Failed to create Snapshot copy [Snapshot] (Failed to create Snapshot copy [Snapshot...Applies to ONTAP 9 SnapMirror Maximum allowed Snapshots Issue SnapMirror relationship is not replicating with error: Failed to create Snapshot copy [Snapshot] (Failed to create Snapshot copy [Snapshot] on volume [Volume](No more snapshots available))
    • data readonly or not accessible on AWS S3 with error expired token
      https://kb.netapp.com/Cloud/Cloud_Volumes_ONTAP/data_readonly_or_not_accessible_on_AWS_S3_with_error_expired_token
      If you continue to receive this error, you can use the error code to search for help with this problem. 2021-05-03T12:49:18Z 123383070234567891 [4:0] CLOUD_BIN_ERR: object_store_config_check_connectio...If you continue to receive this error, you can use the error code to search for help with this problem. 2021-05-03T12:49:18Z 123383070234567891 [4:0] CLOUD_BIN_ERR: object_store_config_check_connection: HEAD failed for s3 handle 954 at try_count 1 with error 140 (Bad request) 2021-05-03T12:49:19Z 123383073567891234 [12:0] CLOUD_BIN_ERR: object_store_config_check_connection: PUT failed for s3 handle 954 at try_count 2 with error 42 (Expired token)
    • Cloud Manager not showing any volume and aggregate after changing CVO volume type to gp3 from AWS
      https://kb.netapp.com/Cloud/BlueXP/Cloud_Manager/Cloud_Manager_not_showing_any_volume_and_aggregate_after_changing_CVO_volume_type_to_gp3_from_AWS
      Applies to Cloud Manager AWS Cloud Volume ONTAP 9.6 and below (CVO) gp3 disks Issue Cloud Manager is not showing any volumes nor aggregates after changing CVO volume type to gp3 from AWS. Error an err...Applies to Cloud Manager AWS Cloud Volume ONTAP 9.6 and below (CVO) gp3 disks Issue Cloud Manager is not showing any volumes nor aggregates after changing CVO volume type to gp3 from AWS. Error an error occurred while retrieving aggregates from server appears when opening the Advanced allocation page.
    • AWS connector does not detect the correct CVO's license type
      https://kb.netapp.com/Cloud/BlueXP/Cloud_Manager/AWS_connector_does_not_detect_the_correct_CVO_s_license_type
      Applies to AWS Connector 3.9.5 Cloud Volume ONTAP 9.8 (CVO) CVO License Issue AWS connector does not detect the correct CVO's license type. Premium license is being detected instead of BYOL.
    • What ports needs to be opened in case of having an external OnPrem firewall between AWS Connector and CVO?
      https://kb.netapp.com/Cloud/BlueXP/Cloud_Manager/What_ports_needs_to_be_opened_in_case_of_having_an_external_OnPrem_firewall_between_AWS_Connector_and_CVO
      In case of external OnPrem firewall between the Connector and the CVO the below ports needs to be opened: HTTP 80 Mediator IP address from Connector IP address TCP 3000 Mediator IP address and ONTAP c...In case of external OnPrem firewall between the Connector and the CVO the below ports needs to be opened: HTTP 80 Mediator IP address from Connector IP address TCP 3000 Mediator IP address and ONTAP cluster management LIF from Connector IP address HTTPS 443 Connector IP address to ONTAP cluster management LIF HTTP 80 Mediator IP address to Connector IP address TCP 3000 Connector IP address to ONTAP cluster management LIF and Mediator IP address
    • How to enter Maintenance Mode in Cloud Volumes ONTAP on Amazon Web Services
      https://kb.netapp.com/Cloud/Cloud_Volumes_ONTAP/How_to_enter_Maintenance_Mode_in_Cloud_Volumes_ONTAP_on_Amazon_Web_Services
      Applies to ONTAP 9 Cloud Volumes ONTAP Amazon Web Services (CVO AWS) Description AWS does not allow users to console in and interact with the ONTAP CVO instance/virtual machine The instance/virtual ma...Applies to ONTAP 9 Cloud Volumes ONTAP Amazon Web Services (CVO AWS) Description AWS does not allow users to console in and interact with the ONTAP CVO instance/virtual machine The instance/virtual machine must be booted into ONTAP where network interfaces are initialized before a user can connect to manage it Entering maintenance mode may be required to fix disk ownership, recreate mailbox disks, or other activity
    • How to restore AWS CVO services in case of compromised credentials?
      https://kb.netapp.com/Cloud/Cloud_Volumes_ONTAP/How_to_restore_AWS_CVO_services_in_case_of_compromised_credentials
      Applies to Amazon Web Services (AWS) Cloud Volume ONTAP (CVO) Compromised Credentials Disaster Recovery (DR) Answer Use SnapMirror technology in order to Setup and Activate DR on CVO that is managed b...Applies to Amazon Web Services (AWS) Cloud Volume ONTAP (CVO) Compromised Credentials Disaster Recovery (DR) Answer Use SnapMirror technology in order to Setup and Activate DR on CVO that is managed by a different AWS account. Additional Information Replicating data between systems
    • IP gateway drops traffic for LIFs in Cloud Volumes (AWS)
      https://kb.netapp.com/Cloud/Cloud_Volumes_ONTAP/IP_gateway_drops_traffic_for_LIFs_in_Cloud_Volumes_AWS
      Applies to ONTAP 9 Cloud Volumes ONTAP AWS Issue Despite an otherwise correct configuration, the gateway in AWS does not respond to or pass traffic from a LIF which has not also been configured in the...Applies to ONTAP 9 Cloud Volumes ONTAP AWS Issue Despite an otherwise correct configuration, the gateway in AWS does not respond to or pass traffic from a LIF which has not also been configured in the EC2 instance
    • Cloud Volumes ONTAP instance does not boot due to disk reservation conflict
      https://kb.netapp.com/Cloud/Cloud_Volumes_ONTAP/Cloud_Volumes_ONTAP_instance_does_not_boot_due_to_disk_reservation_conflict
      During a Cloud Volumes ONTAP upgrade, the following is observed on the node in takeover during boot: cryptomod_fips: Crypto FIPS self-test: 'AES-128 ECB, AES-256 ECB' passed. cryptomod_fips: Crypto FI...During a Cloud Volumes ONTAP upgrade, the following is observed on the node in takeover during boot: cryptomod_fips: Crypto FIPS self-test: 'AES-128 ECB, AES-256 ECB' passed. cryptomod_fips: Crypto FIPS self-test: 'AES-128 CBC, AES-256 CBC' passed. cryptomod_fips: Crypto FIPS self-test: 'AES-128 GCM, AES-256 GCM' passed. From the up node, run interconnect status show in priv advanced mode ( set -privilege advanced ) to see if RDMA is in state down.
    • How to Change AWS CVO Root and Boot Disk Type
      https://kb.netapp.com/Cloud/Cloud_Volumes_ONTAP/How_to_Change_AWS_CVO_Root_and_Boot_Disk_Type
      Applies to Cloud Volumes ONTAP (CVO) BlueXP (Formerly Cloud Manager) Description This describes how to change the root and boot Cloud Volumes ONTAP disk type to a different supported disk type using t...Applies to Cloud Volumes ONTAP (CVO) BlueXP (Formerly Cloud Manager) Description This describes how to change the root and boot Cloud Volumes ONTAP disk type to a different supported disk type using the AWS cloud console.