Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Clock widget wrong on C40

I have a client who has an Sx20 and C40 on the same LAN pointed to the same NTP server, but only the SX20 is displaying the correct time.. the C40 is off by about 41 minutes.. I've tried other time servers, and upgrading the software (currently 7.0 2) but nothing will cure this.. i have disabled the NTP settings altogether, but my client would like for it to be rectified if possible.

Any ideas what could be happening?

 

Darren

  • TelePresence
34 REPLIES
VIP Green

Hi Darren,The usual cause of

Hi Darren,

The usual cause of this from what I have seen in my environments is that the device not actually talking to the NTP server, even though it is configured - possibly a firewall or other connectivity issue between that endpoint and the NTP server.  If you check the web interface on the codec Diagnostics - > Troubleshooting - you'll often see a NTP status error.

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

New Member

Wayne, I have checked the

Wayne, I have checked the troubleshooting page, and nothing in there mentions NTP.  Did you mean to look within a specific log file?  Can you advise which one if yes.

 

VIP Green

Might be a TC7.1.x thing.  It

Might be a TC7.1.x thing.  It's there on mine.  I've seen a couple recently have NTP problems and they showed there.

New Member

I have upgraded to TC7.1.1,

I have upgraded to TC7.1.1, and now Troubleshooting does show that the NTP is not configured correctly, but I do not see any difference from the SX20 on the same network. 

I have opened a ticket with Cisco TAC.

VIP Green

Give TC7.1.1 a few minutes -

Give TC7.1.1 a few minutes - I've seen many of mine report NTP issues on the Troubleshooting page upon first boot that then go away after a little while.  Check back on your codec after 5 or so minutes and re-run the diagnostics - you might see the error disappear if it is working (or in your case, if you've got an actual problem, maybe not).

Was there any difference setting your NTP Mode to "Manual" rather than "Auto"?

Do you have an AD server, or other time source on your network that you can point the endpoint to rather than the external Tandberg one?

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

 

New Member

SX10 standalone. 

SX10 standalone. 

On Static IP's 

Can ping all 3 NTP servers from the VC unit. 

DHCP off.

However, status is as below

xstat //ntp
*s NetworkServices NTP CurrentAddress: "45.125.255.53"
*s NetworkServices NTP Server 1 Address: "161.202.144.189"
*s NetworkServices NTP Server 2 Address: "139.59.15.228"
*s NetworkServices NTP Server 3 Address: "0.ntp.tandberg.com"
*s NetworkServices NTP Status: Discarded
** end

Pls advice. 

Any help here will be appreciated guys :) 

New Member

We have also seen some

We have also seen some stubborn endpoints that do not seem to want to to NTP sync...

We typically use the IP Gateway address as the NTP source

My understanding is that any Cisco IOS device (Router or Switch) that is "in NTP sync" can be used as an NTP source.  This arrangement keeps all the NTP chatter on the LAN rather than out on the Internet or to an NTP server in your data center, this also avoids the DNS issue..   we put the IPv4 IP Gateway address in as the NTP server and it works like a charm 

In our case we have Layer 2 Cisco 3750 switches in the comm closet and we know that our network team always sets these Layer 2 switches up for NTP sync.

Hope this helps

SCJ

Cisco Employee

Sometimes it's the simple

Sometimes it's the simple stuff...  is the NTP a remote LAN?  Are you sure the C40 has it's gateway and subnet properly defined?  IE: the c40 talks to local LANs fine, but not certain remote LANs?

 

It's gotta be NTP config settings, network settings in endpoint, or connectivity between.  Check for simple transpositions, etc

VIP Purple

If using a static IP on the

If using a static IP on the codec, people sometimes forget to put in static DNS addresses as well.  I should know, happened to us a few years ago.

1524
Views
0
Helpful
34
Replies