Test connectivity to Google Cloud NetApp Volumes

This page describes how to test connectivity to NetApp Volumes.

Using the ping command to test connectivity through routers and firewalls is a standard industry practice. The ping command and other network tools, such as traceroute, use the ICMP protocol.

The service responds to ICMP on the following interfaces or IP addresses:

  • All NFS or SMB IP addresses of Standard, Premium, and Extreme service levels.

  • All intercluster IP addresses of Standard, Premium, and Extreme service levels. Intercluster IPs are used for SnapMirror-based features, such as volume migration and external replication.

  • Flex Unified intercluster IP addresses.

The service doesn't respond to ICMP on the following interfaces or IP addresses:

  • All Flex File pools IP addresses

  • All Flex Unified pools IP addresses, except intercluster IP addresses

To test connectivity to a service IP that doesn't respond to ICMP, connect to a service TCP port instead to verify that it's open. You can use this method as an alternative to ping.

On Linux clients, run the following CLI command:

timeout 2 bash -c '/dev/tcp/VOLUME_IP/PORT && echo Port is open || echo Port is closed' || echo Connection timeout

On Windows clients, run the following PowerShell command:

Test-NetConnection -ComputerName VOLUME_IP -Port PORT

Replace the following information:

  • VOLUME_IP: the NetApp Volumes IP address you want to connect to.

  • PORT: specify a service port number. For example, common ports include 2049/TCP for NFS, 445/TCP for SMB, 3260/TCP for iSCSI, and 11104/TCP for SnapMirror-based services, such as volume migration and external replication.

What's next

Known issues and limitations.