cancel
Showing results for 
Search instead for 
Did you mean: 
cancel

Who Me Too'd this topic

Did the NTP response format change between IOS 15.1M and 15.2M? Breaks Nagios check_ntp_peer plugin.

johndoe123
Level 1
Level 1

After upgading from 15.1M to 15.2M, I noticed the NTP response format has changed.  Is this normal?  Specifically, the following lines (reference timestamp, originator timestamp) are no longer present.

          Reference Timestamp:  1953852733.195985823 (2098/01/06 02:20:29)

          Originator Timestamp: 1717990245.454058468 (2090/07/17 04:59:01)          Reference Timestamp:  1953852733.195985823 (2098/01/06 02:20:29)
          Originator Timestamp: 1717990245.454058468 (2090/07/17 04:59:01)

I am using the nagios plugin check_ntp_peer plugin to monitor NTP on all my routers and this information is necessary to verify it has an appropriate and valid timesync to an upstream source.

For those with the nagios plugins, you can run the following to reproduce:  "/usr/lib64/nagios/plugins/check_ntp_peer -H 1.1.1.1 -vvv"  and it will respond erorr "

Server responded: >>>stratum=2, offset=, jitter= <<< parsing offset from peer d7c0: error: unable to read server offset response. NTP CRITICAL: Offset unknown|

" on 15.2M routers, but work fine on 15.1M routers.

NEW 15.2M4

                  

17:11:54.258547 IP (tos 0x0, ttl  64, id 33395, offset 0, flags [DF], proto: UDP (17), length: 64) 1.1.1.1.45468 > 2.2.2.2                                                                                                          .64.ntp: [bad udp cksum b682!] NTPv2, length 36
        Reserved, Leap indicator:  (0), Stratum 2, poll 0s, precision 2
        Root Delay: 0.842773, Root dispersion: 0.000320, Reference-ID: 115.116.114.97
          Reference Timestamp:  1953852716.435156255 (2098/01/06 02:20:12)
          Originator Timestamp: 1702112362.411933213 (2090/01/14 10:27:38) [|ntp]
17:11:54.273364 IP (tos 0x0, ttl 247, id 0, offset 0, flags [none], proto: UDP (17), length: 72) 2.2.2.2.64.ntp > 1.1.1.1.                                                                                                          45468: [udp sum ok] NTPv2, length 44
        Reserved, Leap indicator:  (0), Stratum 130, poll 0s, precision 2
        Root Delay: 38493.842773, Root dispersion: 0.000442, Reference-ID: 115.116.114.97
          Reference Timestamp:  1953852733.195985823 (2098/01/06 02:20:29)
          Originator Timestamp: 1717990245.454058408 (2090/07/17 04:59:01)
          Receive Timestamp:    1785295988.396274387 (2092/09/03 05:01:24) [|ntp]

OLD 15.1M


17:12:02.647131 IP (tos 0x0, ttl  64, id 41784, offset 0, flags [DF], proto: UDP (17), length: 64) 1.1.1.1.46484 > 10.100.21                                                                                                          .65.ntp: [bad udp cksum 747f!] NTPv2, length 36
        Reserved, Leap indicator:  (0), Stratum 2, poll 0s, precision 2
        Root Delay: 0.839965, Root dispersion: 0.000320, Reference-ID: 115.116.114.97
          Reference Timestamp:  1953852716.435156255 (2098/01/06 02:20:12)
          Originator Timestamp: 1702112362.411933213 (2090/01/14 10:27:38) [|ntp]
17:12:02.661759 IP (tos 0x0, ttl 247, id 0, offset 0, flags [none], proto: UDP (17), length: 80) 3.3.3.3.ntp > 1.1.1.1.                                                                                                          46484: [udp sum ok] NTPv2, length 52
        Reserved, Leap indicator:  (0), Stratum 130, poll 0s, precision 2
        Root Delay: 38484.839965, Root dispersion: 0.000610, Reference-ID: 115.116.114.97
          Reference Timestamp:  1953852733.195985823 (2098/01/06 02:20:29)
          Originator Timestamp: 1717990245.454058468 (2090/07/17 04:59:01)
          Receive Timestamp:    775107378.172369629 (2060/08/30 05:04:34)
          Transmit Timestamp:   1953785202.239016428 (2098/01/05 07:34:58)
            Originator - Receive Timestamp:  -942882867.281688868
            Originator - Transmit Timestamp: +235794956.784957945

Who Me Too'd this topic