I'm about configuring a Meinberg microSync timeserver that features "MRS" (Multi-Reference clock Source), but I could not find a good explanation what it really is (only Multi Reference Clock, but that didn't enlighten me), or how it works exactly.
For the IMS-TCR: IRIG Time Code Receiver and Generator Module Meinberg wrote:
The Meinberg MRS concept supports setting up a prioritized list of input sources that are used to synchronize the internal hardware clock of the IMS-TCR and then generate a large number of different output signals used by IMS I/O compatible cards to provide a user-defined selection of synchronization output signals by adding BPE, CPE or other IMS modules.
However I'm confused: My server has a GPS, and I can configure (among other possibilities that I don't have) one NTP server as additional reference (why not more than one?), and I can configure additional NTP servers that are not a "Reference" (in the MRS sense). As I understand it the "Reference" (MRS) will select the preferred GPS to adjust "the oscillator" when the GPS qualifies as a "sound source of time", and (given no further alternatives) it will select the specified reference NTP server if that qualifies as a "sound source of time" (You can define some criteria with each reference source).
So I wonder:
- What is the advantage of configuring an additional NTP server as "reference" for MRS, compared to configuring it as a "normal" time server?
- Normal NTP servers with a local reference clock adjust the local computer's software clock using NTP, while the reference clock has it's own oscillator that might be adjustable by hardware, probably configured by some external signal like DCF-77 or GPS. In contrast the MRS models seems to have only one oscillator (that is shared by the GPS and the "local computer", see photo). That makes it hard to understand how the clock the time server uses is tuned actually, and, maybe more important, how it can be monitored/verified.
Specifically I'm confused with the timekeeping when the reference is a GPS server on the LAN (the graph shows nanoseconds, obviously, so the adjustment steps are like 50ms):
So who can enlighten me?

