Search
- Filter results by:
- View attachments
- https://kb.netapp.com/Cloud/Cloud_Volumes_ONTAP/How_to_Ping_in_NetApp_Cloud_Volumes_ONTAP_for_AzureApplies to NetApp Cloud Volumes ONTAP for Azure Description According to Microsoft's Azure documentation, the ICMP protocol is not permitted through the Azure load balancer, which will cause network p...Applies to NetApp Cloud Volumes ONTAP for Azure Description According to Microsoft's Azure documentation, the ICMP protocol is not permitted through the Azure load balancer, which will cause network pings to fail.
- https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Metrocluster_configuration-settings_connection_connect_command_returns_errormetrocluster configuration-settings connection connect command returns error Errors: Did not receive a "ping" response using the network addresses "xx.xx.xx.1" and "xx.xx.xx.2" on node "clusterA-01" i...metrocluster configuration-settings connection connect command returns error Errors: Did not receive a "ping" response using the network addresses "xx.xx.xx.1" and "xx.xx.xx.2" on node "clusterA-01" in cluster "clusterA". addresses "xx.xx.xx.1" and "xx.xx.xx.2" on node "clusterA-01" in addresses "xx.xx.xx.2" and "xx.xx.xx.1" on node "clusterA-02" in addresses "xx.xx.xx.3" and "xx.xx.xx.4" on node "clusterB-01" in Error: Did not receive a "ping" response using the network
- https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Ping_from_LIF_to_gateway_IP_address_fails_due_to_no_ARP_response_from_switchThis article describes the solution for when Ping from LIF to gateway IP address fails.
- https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/Only_one_port_is_responding_on_the_E-SeriesApplies to NetApp E-Series Issue After some switch maintenance only one iSCSI target port is responding to pings Other ports up however are not responding
- https://kb.netapp.com/Legacy/AltaVault/How_to_verify_network_connectivity_with_ping_and_traceroute_in_AltaVaultApplies to AltaVault (AVA) Description AltaVault deployments leverage multiple network interfaces, and the desired source interface needs to be specified when testing connectivity using ping, telnet, ...Applies to AltaVault (AVA) Description AltaVault deployments leverage multiple network interfaces, and the desired source interface needs to be specified when testing connectivity using ping, telnet, and traceroute By default, the primary interface will be used, unless the destination is on a local subnet, in which case, the packets/connection will be sourced from the interface, with the local address. Please note that many public cloud providers do not respond to ping requests.
- https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Download_of_firmware_image_fails_in_ONTAP_however_download_succeeds_with_node_at_LOADERDownloading a new ONTAP image or firmware file fails once a node boots up ONTAP, however it works as expected when downloading from the HTTP server at the LOADER prompt (prior to booting ONTAP on the ...Downloading a new ONTAP image or firmware file fails once a node boots up ONTAP, however it works as expected when downloading from the HTTP server at the LOADER prompt (prior to booting ONTAP on the node) NetApp Data ONTAP 9.5P12 <<<---ONTAP is booting here This procedure will replace existing Data ONTAP software with new software. What is the URL for the package? Verify that the network is properly configured, that the gateway is set
- https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/e0M_or_SP_are_link_up_but_cannot_be_accessedApplies to FAS / AFF systems Service Processor (SP) Baseboard Management Controller (BMC) Issue e0M or SP are link up, but cannot be accessed. Turning off and on the e0M port doesn't address the issue...Applies to FAS / AFF systems Service Processor (SP) Baseboard Management Controller (BMC) Issue e0M or SP are link up, but cannot be accessed. Turning off and on the e0M port doesn't address the issue Example: ::> network port modify -node node-01 -port e0M -up-admin false ::> network port modify -node node-01 -port e0M -up-admin true
- https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/ICMP_ping_responses_from_storage_system_occasionally_delayApplies to ONTAP 9 Issue ICMP ping responses from storage system occasionally delay Example: ip.addr == CLIENT_IP and ip.addr == STORAGE_IP 971 2022-11-10 17:36:29.125758 CLIENT_IP STORAGE_IP ICMP Ech...Applies to ONTAP 9 Issue ICMP ping responses from storage system occasionally delay Example: ip.addr == CLIENT_IP and ip.addr == STORAGE_IP 971 2022-11-10 17:36:29.125758 CLIENT_IP STORAGE_IP ICMP Echo (ping) request id=0x0001, seq=6580/46105, ttl=125 (reply in 973) 973 2022-11-10 17:36:29.457171 STORAGE_IP CLIENT_IP ICMP Echo (ping) reply id=0x0001, seq=6580/46105, ttl=64 (request in 971) Note: The packet trace is captured from storage system
- https://kb.netapp.com/hybrid/StorageGRID/Maintenance/Failed_to_sync_to_any_NTP_server_error_during_StorageGRID_installationApplies to NetApp StorageGRID 11.4 and higher NetApp StorageGRID Appliances Issue Not able to ping any IP on the StorageGRID Appliance Installer page (while this was previously possible) , when Storag...Applies to NetApp StorageGRID 11.4 and higher NetApp StorageGRID Appliances Issue Not able to ping any IP on the StorageGRID Appliance Installer page (while this was previously possible) , when StorageGRID installation fails on step 8 due to error: Error while generating the grid configuration. Failed to sync to any NTP server. Error: sntp 4.2.8p12@1.3728-0 (1) <ip address> no UCST response after 2 seconds
- https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/NFS_UDP_traffic_intermittently_drops_after_upgrade_to_ONTAP_9.2_or_newerMostly the issue is found after ONTAP is upgraded to 9.2 or later, the filer does not reply to every ICMP (ping) request even if it can be found in a packet trace. A strange behavior could be related ...Mostly the issue is found after ONTAP is upgraded to 9.2 or later, the filer does not reply to every ICMP (ping) request even if it can be found in a packet trace. A strange behavior could be related to multiple LIFs on the same port not responding at different times. This issue is affecting the NFS data transfer also if UDP is used as a transport layer causing a huge delay [root@centos-04 /]# mount -t nfs -o vers=3,proto=udp 10.128.242.45:/vol1_svm2 /mnt/vol1_svm2_ontap93
- https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Fails_to_ping_gateway_with_error_No_buffer_space_availableApplies to Intel 1/10 Gigabit Ethernet Controller IX4-T port Fails to ping gateway with error "No buffer space available" ping: sendto: No buffer space available Frame discards for transmit are increa...Applies to Intel 1/10 Gigabit Ethernet Controller IX4-T port Fails to ping gateway with error "No buffer space available" ping: sendto: No buffer space available Frame discards for transmit are increasing due to Queue overflow on the onboard Ten Gigabit Ethernet NIC port : ::> system node run -node <node_name> -command ifstat -a Total frames: 11845 | Frames/second: 0 | Total bytes: 1617k Total discards: 75581 | Queue overflow: 75581 | Multi/broadcast: 11350