Then in that case, likely hardware just doesn't have what it needs.
Again, I mention, in the past, it seemed the more expensive Cisco network equipment supported this, and less expensive equipment did not.
However, for this century's equipment, and as "same capability" hardware, over time, decreases in price, one could wonder why newer/current Cisco network equipment doesn't support this.
Only Cisco could answer that, but I wonder, if the thinking is, with Internet connectivity the "norm" and/or the capability to easily obtain a clock signal from GPS, who really "needs" such a feature, a booting system can likely have an accurate clock/calendar shortly after booting, or perhaps even while booting.
In ancient times, like last century, I remember many stand alone computer systems didn't have networks, and those that did, were a far cry from what we have today, for example, their WAN might only be dedicated p2p links with other same business sites. I.e. they did not acquire the current time/data automatically, you had to manually enter such when the system booted (such a PIA). Then, embedded battery powered calendars started to become the norm, and then the only problem was how such clocks would "drift" (see my earlier reply's "aside" comment) but if the system was within a minute or two of the correct time, you might only bother correcting it, twice a year, when and if you manually adjusted for daylight savings time (yea, once upon a time, that wasn't automatic, either [or leap years, or . . . -laugh).
All I can end is by saying - this wasn't a problem when using card punch machines, and if they were good enough for Herman (Hollerith), by cracky, you might not have this issue today! ; )
