When NTP client and active modes are configured, Junos OS uses the client mode configuration.
Topology:
Server------MX1(ge-1/2/2/)------(ge-1/2/2)MX2 | | | | -----------------------------------------
Server------MX1(ge-1/2/2/)------(ge-1/2/2)MX2
-----------------------------------------
When active mode (peer mode) is configured on MX2, it will synchronize the time from MX1:
MX1# show system ntp server 202.118.1.47; MX1# show interfaces ge-1/2/2 unit 0 { family inet { address 12.1.1.1/24; } } MX2# show system ntp peer 12.1.1.1; <--------------- MX2# show interfaces ge-1/2/2 unit 0 { family inet { address 12.1.1.2/24; } } MX2# run show ntp status status=0644 leap_none, sync_ntp, 4 events, event_peer/strat_chg, version="ntpd 4.2.0-a Fri Aug 18 17:37:29 2017 (1)", processor="powerpc", system="JUNOS16.1R5.7", leap=00, stratum=3, precision=-18, rootdelay=44.621, rootdispersion=963.650, peer=45508, refid=12.1.1.1, reftime=de4724dc.0ab26fdc Mon, Mar 5 2018 2:07:24.041, poll=4, clock=de4725da.74bfd07e Mon, Mar 5 2018 2:11:38.456, state=2, offset=0.065, frequency=2.863, jitter=0.134, stability=0.008
When active and client mode is configured on MX2, it will synchronize the time from the server:
MX2# show system ntp peer 12.1.1.1; <------- active mode server 202.118.1.47; <------- added client mode MX2# run show ntp status status=0644 leap_none, sync_ntp, 4 events, event_peer/strat_chg, version="ntpd 4.2.0-a Fri Aug 18 17:37:29 2017 (1)", processor="powerpc", system="JUNOS16.1R5.7", leap=00, stratum=2, precision=-18, rootdelay=44.470, rootdispersion=190.309, peer=54765, refid=202.118.1.47, reftime=de4726fe.5189c840 Mon, Mar 5 2018 2:16:30.318, poll=6, clock=de472740.220c3820 Mon, Mar 5 2018 2:17:36.132, state=4, offset=-1.675, frequency=2.834, jitter=0.079, stability=0.005
This is the expected behavior when both modes are configured.