Cisco IOS NTP: "show ntp associations" versus "show ntp status"

Question

what is the difference of the commands "show ntp ass det" and "show ntp status" ?
these commands differs on the referenced time source.
switch#sh ntp ass detail
Load for five secs: 17%/4%; one minute: 20%; five minutes: 20%
Time source is NTP, 10:45:15.469 MET Tue Feb 4 2014
10.1.5.4 configured, ipv4, sane, valid, stratum 2
ref ID 154.71.99.39   , time D69B3383.9D414772 (10:38:11.614 MET Tue Feb 4 2014)
our mode client, peer mode server, our poll intvl 1024, peer poll intvl 1024
root delay 0.38 msec, root disp 5.93, reach 377, sync dist 11.77
delay 0.84 msec, offset 0.3778 msec, dispersion 1.06, jitter 0.97 msec
precision 2**21, version 4
assoc id 26601, assoc name 10.1.5.4
assoc in packets 12339, assoc out packets 12361, assoc error packets 28
org time 00000000.00000000 (01:00:00.000 MET Mon Jan 1 1900)
rec time D69B347C.4ACDE42A (10:42:20.292 MET Tue Feb 4 2014)
xmt time D69B347C.4ACDE42A (10:42:20.292 MET Tue Feb 4 2014)
filtdelay =     0.88    0.87    0.85    0.90    0.84    0.90    0.89    0.87
filtoffset =    0.31    0.31    0.32    0.28    0.37    0.32    0.25    0.31
filterror =     0.97    1.00    1.03    1.06    1.09    1.12    1.15    1.18
minpoll = 6, maxpoll = 10
FD8C:2208:32F7:8EA::5 configured, ipv6, our_master, sane, valid, stratum 1
ref ID .PPS., time D69B318B.92FDD88A (10:29:47.574 MET Tue Feb 4 2014)
our mode client, peer mode server, our poll intvl 1024, peer poll intvl 1024
root delay 0.00 msec, root disp 0.42, reach 377, sync dist 17.18
c4507r01#show ntp status
Load for five secs: 19%/4%; one minute: 20%; five minutes: 20%
Time source is NTP, 10:42:03.441 MET Tue Feb 4 2014
Clock is synchronized, stratum 2, reference is 81.201.114.7
nominal freq is 250.0000 Hz, actual freq is 249.9987 Hz, precision is 2**10
ntp uptime is 752342800 (1/100 of seconds), resolution is 4016
reference time is D69B2950.47571873 (09:54:40.278 MET Tue Feb 4 2014)
clock offset is 0.9771 msec, root delay is 0.94 msec
root dispersion is 47.43 msec, peer dispersion is 1.03 msec
loopfilter state is 'CTRL' (Normal Controlled Loop), drift is 0.000005068 s/s
system poll interval is 1024, last update was 2881 sec ago.
switch#sh ntp associations
Load for five secs: 18%/4%; one minute: 20%; five minutes: 20%
Time source is NTP, 10:53:12.750 MET Tue Feb 4 2014
  address         ref clock       st   when   poll reach  delay  offset   disp
+~10.1.5.4      154.71.99.39     2    690   1024   377  0.848   0.377  1.069
*~FD8C:2208:32F7:8EA::5
                  .PPS.            1    400   1024   377  0.931   0.892  1.007
* sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured

Answer 1

Its hard to find expert on switches/IOS on the Network Management Forum, which is for NMS applications.
You should post this thread on Switching community of CSC forum.
Though, what i can suggest is to use SNTP.  Certain low-end Cisco devices only support SNTP. SNTP is a simplified, client-only version of NTP. SNTP can only receive the time from NTP servers and cannot be used to provide time services to other systems. SNTP typically provides time within 100 milliseconds of the accurate time. In addition, SNTP does not authenticate traffic, although you can configure extended access lists to provide some protection. An SNTP client is more vulnerable to misbehaving servers than an NTP client and should only be used in situations where strong authentication is not required.
SNTP may not be much of an alternative because it is not widely supported in software.
You can use command # sntp server. SNTP generally is supported on those platforms that do not provide support for NTP.
Device (config)# sntp server {address | hostname} [version number]
For more clarification post this to Lan Switching and Routing section.
-Thanks
Vinod
**Rating Encourages contributors, and its really free. **