You might encounter network issues in Snap Creator such as authorization failures. You should be aware of these issues and know how to troubleshoot them.
Unless you use host equiv, the storage system name from the hostname command on the controller should be the same as what was entered in the Snap Creator configuration file.
Do not use a fully qualified domain name (FQDN) when the host name of a storage system is abbreviated.
Ensure that the IP resolution matches the name that you specified. If there is a mismatch, correct it by using host equiv on the storage system.
To enable host equiv, perform the following steps:
The storage controller name defined in the Snap Creator configuration parameter VOLUMES must match the storage controller name in the NetApp Management Console data protection capability. If the storage controller names do not match, you can use the operating system host file to force the storage controller names to match.
If there is a firewall between the host that is running Snap Creator and your storage system, ensure that you have bi-directional access control lists (ACLs) open for 80, 443, or both.
To use HTTPS (443) for Linux, Solaris, or AIX, install the openssl libraries, which are required to use SSL.
If Snap Creator Agent is running, the port on which the Agent is running must be open. Ensure that the return traffic from the storage system can go to the system that is running Snap Creator, at least on the non-privileged ports.
In Snap Creator Framework you can disable SSLV3 in the host and the storage system:
jdk.tls.disabledAlgorithms=sslv3
The java.security file is located under the path: /java/jre/lib/security/
TLSv1 Enabled: true
SSLv3 Enabled: false
SSLv2 Enabled: false
If you use NAT, ensure that the source/destination IP addresses are not changed in the Transmission Control Protocol (TCP) packet. The host and storage systems need to know who they are communicating with. Presenting a firewall IP instead of the actual host or controller IP might cause problems.