Problem solved, I was missing a route to the network where the NTP server resides.  It looks like there's no default routes configured on the data movers (new to storage, still learning!) and as a result the datamover couldn't reach the NTP server however the CS could without any problems.   "server_route server_2 -list" allowed me to see the default route list and I was able to add a default route with "server_route server_2 -add ..."
Like the title says.  As a very first step I tried to Stop, delete and re-add the NTP servers however I always see "Running, Disconnected".  To be honest it would be kind of strange to see "Running, Connected" since NTP is over UDP but that being said, "Running, Disconnected" doesn't seem right either.  I've already spoken with my network team and they confirmed UDP port 123 is open all the way between the storage and the NTP server.  Furthermore, I have another server on the same subnet which can successfully reach the NTP server and get corrections.  Stats look like this:  [nasadmin[NAME]-1-CS1 ~]$ server_date ALL timesvc stats ntp server_2 : Time synchronization statistics since start: hits= 0, misses= 0, first poll hit= 0, miss= 41 Last offset: 0 secs, 0 usecs Current State: Running, disconnected, interval= 60 Time sync hosts: XX.XX.XX.XX,  server_3 : Time synchronization statistics since start: hits= 0, misses= 0, first poll hit= 0, miss= 0 Last offset: 0 secs, 0 usecs Current State: Running, disconnected, interval= 60 Time sync hosts: XX,XX,XX,XX   I ran tcpdump -i eth3 -nnv udp and port 123  in a screen'd session and went through the stop/delete/start routine again and I didn't see any outbound UDP traffic.  TIA.
NS120: problems with NTP