cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2874
Views
20
Helpful
4
Replies

CUCM & NTP Authentication

Hi everyone

Our network guys recently setup some new NTP servers that require authentication. I know you can configured the following on a router/switch to allow for this, but is there a way to configure this for CUCM? I'm running 8.6

 

 

ntp authentication-key 5 md5 **********

ntp authenticate

ntp trusted-key 5

ntp update-calendar

ntp server 1.1.1.1 key 5

 

2 Accepted Solutions

Accepted Solutions

Jaime Valencia
Cisco Employee
Cisco Employee

No, CUCM needs an NTP that has no authentication. All you get to configure regarding NTP, is the IP.

HTH

java

if this helps, please rate

View solution in original post

Nadav
Level 7
Level 7

Just adding to Jaime's response:  The fact that your NTP server has an authentication key in no way stops you from syncing CUCM with it, you will simply be synching to it unauthenticated. The authentication key is there to authenticate the ntp server, and not the clients.

There is only an issue if the client supplies an authentication string for a key to sync with the server, but the server doesn't have the same key with the same authentication string. See the following article for details:

http://www.ine.com/resources/ntp-authentication.htm

View solution in original post

4 Replies 4

Jaime Valencia
Cisco Employee
Cisco Employee

No, CUCM needs an NTP that has no authentication. All you get to configure regarding NTP, is the IP.

HTH

java

if this helps, please rate

[+5] to both of you for sharing good info.

I have been try to rate both but is not working.

wud try later.

 

regds,

aman

working now.

 

regds,

aman

Nadav
Level 7
Level 7

Just adding to Jaime's response:  The fact that your NTP server has an authentication key in no way stops you from syncing CUCM with it, you will simply be synching to it unauthenticated. The authentication key is there to authenticate the ntp server, and not the clients.

There is only an issue if the client supplies an authentication string for a key to sync with the server, but the server doesn't have the same key with the same authentication string. See the following article for details:

http://www.ine.com/resources/ntp-authentication.htm