ilter state is 'CTRL' (Normal Controlled Loop), drift is 0.000030140 s/s system poll interval is 64, last update was 376 sec ago. Another way to show that NTP is driving the system clock is with the show clock detail command: R1-PBX#sho clock detail 15:02:07.371 EST Tue Mar 1 2011 Time source is NTP Summer time starts 02:00:00 EST Sun Mar 13 2011 Summer time ends 02:00:00 EDT Sun Nov 6 2011 Sadly, my sophomoric side can no longer giggle at the abbreviated command show ntp ass, since the show ntp association command doesn't exist in NX-OS. In NX-OS, to show the status of NTP servers, use the show ntp peers command. Here, I have con- figured the same servers on a Nexus 7000: NX-7K-1(config)# sho ntp peers Peer IP Address Serv/Peer 132.163.4.102 Server (configured) 193.67.79.202 Server (configured) 152.1.58.124 Server (configured) 128.118.46.3 Server (configured) 129.6.15.29 Server (configured) 64.236.96.53 Server (configured) 208.184.49.9 Server (configured) The show ntp peer-status command will show more information regarding NTP peers. My output shows no connections, because Nexus 7000s were in a lab environment and I had no Internet access: NX-7K-1 (config)# sho ntp peer-status Total peers : 4 - selected for sync, + - peer mode (active), - peer mode (passive), = - polled in client mode remote local reach delay +132.163.4.102 0.0.0.0 0 0.00000 default =193.67.79.202 0.0.0.0 0.00000 default =152.1.58.124 0.0.0.0 0.00000 default Configuring NTP =128.118.46.3 0.0.0.0 0.00000 default =129.6.15.29 0.0.0.0 0.00000 default =64.236.96.53 0.0.0.0 0.00000 default =208.184.49.9 0.0.0.0 0.00000 default NTP Server To configure an IOS device to be an NTP server, enter the command ntp master: 5509(config)#ntp master When you're configuring an IOS device as an NTP server, it can take five minutes or more for the clock to become synchronized. You cannot force this process. On a device that has a calendar, you also need to enter the ntp update-calender command: 6509 (config)#ntp update-calendar To configure another device within t