Leap second to be added in 2016

http://www.space.com/33361-leap-second-2016-atomic-clocks.html

A “leap second” will be added to the world’s official clocks on Dec. 31 at 23 hours, 59 minutes and 59 seconds Coordinated Universal Time (UTC), which corresponds to 6:59:59 p.m. EST; the clocks will read 23:59:60 before ticking over to midnight. The goal is to keep two different timescales in sync with each other.

So, why is this important to you as an ISP?
The trouble is that even as they use the leap second, UNIX and Linux define a day as something that is unvarying in length. “If a leap second happens, the operating system must somehow prevent the applications from knowing that it’s going on while still handling all the business of an operating system,” says Steve Allen, a programmer with California’s Lick Observatory.
Source:http://www.wired.com/2015/01/leap-second-rattle-internet-theres-plot-kill/

Many patches and fixes have been put in place to adjust for this in most Operating systems.  The concern, even a year after the last one, is software that has not been updated to account for dealing with leap seconds.

Helpful OSPF times

OSPF can be a mystery to some.  Understanding the default timeouts can be helpful in troubleshooting.  Some vendors change these times so it is very important to realize this stuff if you start mixing vendors in your OSPF domains.

10 Seconds
Default OSPF hello timer on broadcast and point-to-point links

30 Seconds
Default OSPF hello timer on nonbroadcast links

40 Seconds
Default OSPF hold timer on broadcast and point-to-point links

120 Seconds
Default OSPF hold timer on nonbroadcast links

30 Minutes
OSPF LSA refresh timer

60 Minutes
OSPF LSA expiration timer