Info on Impacts of Leap Second on your Cisco hardware
http://www.cisco.com/web/about/doing_business/leap-second.html#~ProductInformation
Consult your other vendors for impacts on non-Cisco equipment.
"... the leap second introduction is unlikely to represent a material event for Cisco products in our customers' networks."
All the same, I want TAC on the line on 30 June, JUST IN CASE. <-- what my boss' boss will likely say.
coming up next week, so what has anybody done to prepare?
still not clear on the concept, if my device is running NTP and querying the NTP server every few seconds, even, nothing should happen, even then wouldn't it be on the NTP Server to support the leap second, not necessarily on the client.
Looks like we get to find out the hard way.
And I pity anyone still using COBOL...
Eh... Didn't know that. Also, I fail to see the importance for most businesses. Or am I missing something?
On the plus side we dont have NTP setup yet on anything since we just got a time server purchased a couple months ago. So we backed off deploying NTP until after leap second.
Anything else that blows up sounds like it just needs a reboot. Yay!
This came up in my 1-on-1 today. Thanks, www.networking-forums.com, for being a great source for quality answers!
:tmyk:
Helpful bump to Ristau for this thread. Made me answer the question like a BOSS.
Sigh, I have (12) Cisco Nexus 5548's and (1) Cisco Nexus 7010 that I have to disable NTP on this Saturday, June 26th at the same time as I am doing other work. I literally just saw the 5K's mentioned on www.reddit.com/r/networking yesterday. I had asked a co-worker about this a while ago and was I told we don't have anything that would be affected. So very, very wrong.
Yeah, all Nexus seems to be impacted. Also CUCM and some Prime components.
I think it's only NTP time sources. but I could be wrong. I'm still not clear on how this affects the client end.
Nothing happened here
Our XR boxes didn't like it, but nothing major.
02:31:05.008 CEST: ntpd[262]: %IP-IP_NTP-5-SYNC_LOSS : Synchronization lost : X.Y.Z.W : The clock was stepped and needs to be resynced
02:31:05.008 CEST: ntpd[262]: %IP-IP_NTP-5-HP_CONN_LOST : High priority NTP peer connection lost - Stratum 2->15.
02:31:05.008 CEST: ntpd[262]: %IP-IP_NTP-5-ALL_CONN_LOST : All NTP peer connections failed.
02:34:27.374 CEST: ntpd[262]: %IP-IP_NTP-5-HP_CONN_RECOVERED : High priority NTP peer connection recovered - Stratum 15->2.
It caused us to briefly return to October 21, 1985. Some guy named Emmett Brown fixed our routers and we were able to get back to normal time.
:lol:
We had no issues and I added NTP back to our 5K & single 7K that I had it disabled on yesterday. Although according to a few posts I saw on Reddit yesterday, not all providers were so lucky.
Quote from: deanwebb on July 01, 2015, 06:06:19 PM
It caused us to briefly return to October 21, 1985.
1985 was a great year though...
One of our RSA servers was down yesterday, we blamed leap second.