While installing a new AFF A400 HA pair, you are unable to add an NTP server from another subnet. You are able to ping the NTP server from the new cluster.
In this scenario, what are two causes of this problem? (Choose two.)
While installing a new AFF A400 HA pair, you are unable to add an NTP server from another subnet. You are able to ping the NTP server from the new cluster.
In this scenario, what are two causes of this problem? (Choose two.)
If you are unable to add an NTP server from another subnet but can ping it from the new cluster, the possible causes include an incorrect gateway for the admin SVM or a firewall blocking port 123. The NTP server communication over port 123 must be enabled, and an incorrect gateway setting would prevent proper routing to the NTP server across different subnets. Other options like time skew and different IPspace configurations are less likely to be the cause given the ability to ping the server already.
The cluster time-service ntp server create command associates the cluster with an external network time server for time correction and adjustment by using the Network Time Protocol (NTP). The command resolves the time server host name to an IP address and performs several validation checks. If an error is detected during validation, it is reported. The validation checks performed by this command include the following: The NTP replies to an NTP query with the specified protocol version. The NTP reply indicates that the external time server is synchronized to another time server. The distance and dispersion of the NTP reply from the "root" or source clock are within the required limits.
Correct is B and C: can already ping ntp by IP so gateway is working, and cluster lif uses default ipspace by default
A and B : ping Ok from the cluster but not from SVM, change route SVM. B: Sure port 123 should be opened