WTF Is A Step Ticker? – Step Tickers. and Why They Matter

What is a “Step Ticker”

You know, it’s one of those little pedometer things you strap onto your hip and tracks how far you’ve walked. Ok, so it’s not that. At least not within the context of servers & virtualization. So what IS it? It’s a horribly named NTP (network time protocol) concept. Yup. That’s it. You were expecting at least two other paragraphs, no?

What does it do?

Hate to disappoint, this paragraph is going to be short too. A Step Ticker is basically a way to tell the NTP daemon to check a server or two, and correct time on startup, rather than relying on the time that was restored from the hardware.

This is meaningful, because often the hardware time has drifted. If you are running applications that are exceedingly time sensitive, like virtualization, you’ll of course want accurate time. So setting up Step Tickers is a “Good Idea”. So how do we do that?

Setting Up Step Tickers

I’ll show you how to do this on a single host, as well, that’s easy, and I’m lazy. To deploy in mass, you’ll likely want this as part of your kickstart process. If you don’t have automated builds, shame on you, but you should have it as part of your QC process then. As for scripting the change out to each host, that is best left to you, the reader (but can be done in PoSH with plink).

Enough rambling, open /etc/ntp/step-tickers and add some lines that look like this

0.vmware.pool.ntp.org
1.vmware.pool.ntp.org
2.vmware.pool.ntp.org

From here, save the file and restart ntp (service ntpd restart).

Questions? Drop a line in the comments.

Sources: Tripwire KB, VMware KB, and some random UseNet/Mailing list  post about ntpd.

Tagged as: ESX, ntp, time, Troubleshooting