I have a cisco router with NTP server installed and many servers/PCs time follow exactly as the one on the Cisco Router, however none of the HP2524 switches do. The switches are running the latest patch F_05_17 I see the option is SNTP and I tried that however it does not change the time/date to make it the same as the one on the cisco router. Suggestion?
Make sure you set it to use unicast and give it the IP address of the Cisco NTP server. See page 196 in the release notes. http://www.hp.com/rnd/support/manuals/23xx_25xx.htm Or just go into config mode and type:
timesync sntp sntp unicast sntp server A.B.C.D
where A.B.C.D is the IP address of the Cisco. Cisco usually uses version 3 as a default so the 2524's default should be OK. Do sh sntp when you get out of config mode to see that it took.
On the cisco sh ntp a det will show you the version among a hundred other things.
You might try changing the date and time on the 2524 to be within 3 minutes behind the Cisco. Then see if it syncs up. A lot of the NTP stuff doesn't like to work if the time interval is too big.
Ron's right on the nose. I'll add a note that I've discovered after setting up quite a few 2524's exactly the same way. It seems that the switch won't update its time from the Cisco time server until the next time update interval occurs after you input the time value (I set it to 9999 seconds, about 2 and a quarter hours). If you go back and check the switch after the time value you entered elapses, it should be in sync with the Cisco.
IP Address Protocol Version -------------- ---------------- 192.168.0.1 3
from the Cisco RTR... m-2611-01>sh clock Load for five secs: 1%/0%; one minute: 0%; five minutes: 0% Time source is NTP, 11:47:10.394 cst Mon Oct 13 2003
11:47:10.394 cst Mon Oct 13 2003
I have an Cisco ACL that tells me when it gets matched & the HP2424 is making request of it and receiving them.
However, the time seems to allways be off 3-4 min. At 1st I did not change the time, so then I put it to within @ 3-4 min to see if it would catch up and it has not.
Turning on some debug on the Cisco side... 031369: Oct 13 11:54:00.130 cst: NTP: rcv packet from 192.168.1.4 to 192.168.0.1 on Loopback0: 031370: Oct 13 11:54:00.130 cst: leap 0, mode 3, version 3, stratum 0, ppoll 1 031371: Oct 13 11:54:00.134 cst: rtdel 0000 (0.000), rtdsp 0000 (0.000), refid 00000000 (0.0.0.0) 031372: Oct 13 11:54:00.134 cst: ref 00000000.00000000 (19:00:00.000 CST Thu Dec 31 1899) 031373: Oct 13 11:54:00.134 cst: org 00000000.00000000 (19:00:00.000 CST Thu Dec 31 1899) 031374: Oct 13 11:54:00.134 cst: rec 00000000.00000000 (19:00:00.000 CST Thu Dec 31 1899) 031375: Oct 13 11:54:00.134 cst: xmt 00000000.00000000 (19:00:00.000 CST Thu Dec 31 1899) 031376: Oct 13 11:54:00.134 cst: inp C3354918.2209DDEE (11:54:00.132 cst Mon Oct 13 2003)
