Hello,
our environment is:
SAN Volume Controller Ver. 8.5.0.5 with 6 nodes.
Since for 5 days an error is reported:
Failed to synchronize cluster time to NTP server # Error Code = 2700
We check the availability of the NTP server, no issue also for testing with try another NTP IP server and same error.
SMTP email work without issue.
I have read to do a manual failover config node. When that happens the new config node will bind the Management cluster IP address to the new config node and should resolve the issue.
Anybody have this type of issue with SVC and NTP service?
What I'm thinking to try before made the failover of config node is simply change the cluster management IP address and then put it back the original IP address. Doing this will force an interface bind and refresh the routing decision.
As a last resort I will open a ticket at IBM.
Reference documentation at IBM:
Routing considerations for event notification and Network Time Protocol
The system supports the following protocols that make outbound connections:
- Email
- Simple Network Mail Protocol (SNMP)
- Syslog
- Network Time Protocol (NTP)
These protocols operate only on a port that is configured with a management IP address. When it is making outbound connections, the system uses the following routing decisions:
- If the destination IP address is in the same subnet as one of the management IP addresses, the system sends the packet immediately.
- If the destination IP address is not in the same subnet as either of the management IP addresses, the system sends the packet to the default gateway for Ethernet port 1.
- If the destination IP address is not in the same subnet as either of the management IP addresses and Ethernet port 1 is not connected to the Ethernet network, the system sends the packet to the default gateway for Ethernet port 2.
When you configure any of these protocols for event notifications, use these routing decisions to ensure that error notification works correctly if the network fails.
If you have any solution path let me know.
Yves
------------------------------
Yves Blackburn
------------------------------
#Storage#StorageAreaNetworks#PrimaryStorage