Monday, March 18, 2019

NTP Authentication Stuck on .INIT.

Hey everyone,

For PCI compliance I needed to stand up NTP servers with Authentication. I was given two Red Hat boxes and I configured ntpd on each and set up the peer key and life was good. I then pointed a switch towards the new servers and I get either .INIT. or .AUTH. IF I just enter ntp server <IP of NTP1> it connects and works flawlessly as soon as I tell it to use key 1 it goes .INIT. and if I yank out ntp authenticate and put it back in it will go .AUTH.

I'm beyond perplexed at this point I have full connectivity between the switch and the servers. I thought maybe it was my key but I verified all that is good.

ntp authentication-key 1 md5 keysameonserverntp trusted-key 1ntp source vlan100ntp server x.x.x.10 key 1 preferntp server x.x.x.11 key 1ntp authenticate

Another interesting thing is when I debug ntp all I don't get ANYTHING (yes terminal monitor is on!) even when i remove and re-add servers I get no output whatsoever. The peers are running just fine authenticating to each other and the restrict is set to 10.0.0.0 255.0.0.0.0 as I don't want to have to manually input every single subnet.

Setting this up on a Cisco 3850 running 16.3.7 code. I'd love a second set of eyes on this as this is perplexing me to no end. Thank you for reading.

EDIT: I used the following resource to help me get things going
ntp with peering setup: Here



No comments:

Post a Comment