X
NMS Prime
Stay informed. No spam. Just content. This is our promise.
I agree to the privacy terms. I can unsubscribe at any time.
X
Thank You!
X
NMS PRIME - Konferenz
Anzahl der Teilnehmer:
Datenschutz gelesen und akzeptiert
X
Vielen Dank!
X Sign up to comment and create new topics

Hello

 We noticed that CPE interrupts internet access for about 3 minutes while renewing the IP address (end of lease). There are no errors in the logs. In short, the lease is, for example, until 02/15/2021 18:00:00, logs at that time are correct, and communication starts on 02/15/2021 18:03:10. Is this problem only for me? Where can I look for the cause? Best wishes


Most Popular Post
There are no posts marked as being answered (liked) on this topic yet!!

6 Comments

  1. Hi,

    what is your current lease time set in the global config? Normally a client should renew the IP address after 50% of the lease time using DHCPREQUEST. Thus, there shouldn't be any outage and I haven't seen this problem yet. Can you see the requests after 50% of the lease time on the modem analysis page (log)?
    BR,

    Ole

  2. I have the default lease time (86400s). Yes, after 50%, the address is renewed. I will paste the logs below:

    CPE Logs
    Feb 17 14:08:20 nms dhcpd: DHCPACK on 91.xxx.xxx.xxx to 6c:3b:6b:xx:xx:xx (MikroTik) via 91.xxx.yyy.yyy
    Feb 17 14:08:20 nms dhcpd: DHCPREQUEST for 91.xxx.xxx.xxx from 6c:3b:6b:xx:xx:xx (MikroTik) via 91.xxx.yyy.yyy
    Feb 17 14:08:20 nms dhcpd: CPE 6c:3b:6b:xx:xx:xx of Modem c8:fb:26:xx:xx:xx is now ONLINE with IP 91.xxx.xxx.xxx
    Feb 17 02:08:19 nms dhcpd: DHCPACK on 91.xxx.xxx.xxx to 6c:3b:6b:xx:xx:xx (MikroTik) via 91.xxx.yyy.yyy
    Feb 17 02:08:19 nms dhcpd: DHCPREQUEST for 91.xxx.xxx.xxx from 6c:3b:6b:xx:xx:xx (MikroTik) via 91.xxx.yyy.yyy
    Feb 17 02:08:19 nms dhcpd: CPE 6c:3b:6b:xx:xx:xx of Modem c8:fb:26:xx:xx:xx is now ONLINE with IP 91.xxx.xxx.xxx
    Feb 16 14:08:19 nms dhcpd: DHCPACK on 91.xxx.xxx.xxx to 6c:3b:6b:xx:xx:xx (MikroTik) via 91.xxx.yyy.yyy
    Feb 16 14:08:19 nms dhcpd: DHCPREQUEST for 91.xxx.xxx.xxx from 6c:3b:6b:xx:xx:xx (MikroTik) via 91.xxx.yyy.yyy
    Feb 16 14:08:19 nms dhcpd: CPE 6c:3b:6b:xx:xx:xx of Modem c8:fb:26:xx:xx:xx is now ONLINE with IP 91.xxx.xxx.xxx
    Feb 16 02:08:18 nms dhcpd: DHCPACK on 91.xxx.xxx.xxx to 6c:3b:6b:xx:xx:xx (MikroTik) via 91.xxx.yyy.yyy
    Feb 16 02:08:18 nms dhcpd: DHCPREQUEST for 91.xxx.xxx.xxx from 6c:3b:6b:xx:xx:xx (MikroTik) via 91.xxx.yyy.yyy
    Feb 16 02:08:18 nms dhcpd: CPE 6c:3b:6b:xx:xx:xx of Modem c8:fb:26:xx:xx:xx is now ONLINE with IP 91.xxx.xxx.xxx
    Feb 15 14:08:17 nms dhcpd: DHCPACK on 91.xxx.xxx.xxx to 6c:3b:6b:xx:xx:xx (MikroTik) via 91.xxx.yyy.yyy
    Feb 15 14:08:17 nms dhcpd: DHCPREQUEST for 91.xxx.xxx.xxx from 6c:3b:6b:xx:xx:xx (MikroTik) via 91.xxx.yyy.yyy
    Feb 15 14:08:17 nms dhcpd: CPE 6c:3b:6b:xx:xx:xx of Modem c8:fb:26:xx:xx:xx is now ONLINE with IP 91.xxx.xxx.xxx
    Feb 15 02:08:17 nms dhcpd: DHCPACK on 91.xxx.xxx.xxx to 6c:3b:6b:xx:xx:xx (MikroTik) via 91.xxx.yyy.yyy
    Feb 15 02:08:17 nms dhcpd: DHCPREQUEST for 91.xxx.xxx.xxx from 6c:3b:6b:xx:xx:xx (MikroTik) via 91.xxx.yyy.yyy
    Feb 15 02:08:17 nms dhcpd: CPE 6c:3b:6b:xx:xx:xx of Modem c8:fb:26:xx:xx:xx is now ONLINE with IP 91.xxx.xxx.xxx
    Feb 14 14:08:16 nms dhcpd: DHCPACK on 91.xxx.xxx.xxx to 6c:3b:6b:xx:xx:xx (MikroTik) via 91.xxx.yyy.yyy
    Feb 14 14:08:16 nms dhcpd: DHCPREQUEST for 91.xxx.xxx.xxx from 6c:3b:6b:xx:xx:xx (MikroTik) via 91.xxx.yyy.yyy
    Feb 14 14:08:16 nms dhcpd: CPE 6c:3b:6b:xx:xx:xx of Modem c8:fb:26:xx:xx:xx is now ONLINE with IP 91.xxx.xxx.xxx
    Feb 14 14:04:42 nms dhcpd: DHCPACK on 91.xxx.xxx.xxx to 6c:3b:6b:xx:xx:xx (MikroTik) via 91.xxx.yyy.yyy
    Feb 14 14:04:42 nms dhcpd: DHCPREQUEST for 91.xxx.xxx.xxx from 6c:3b:6b:xx:xx:xx (MikroTik) via 91.xxx.yyy.yyy
    Feb 14 14:04:42 nms dhcpd: CPE 6c:3b:6b:xx:xx:xx of Modem c8:fb:26:xx:xx:xx is now ONLINE with IP 91.xxx.xxx.xxx

    analysis page (log)
    Feb 15 14:04:20 nms dhcpd: Added reverse map from 81.8.6.10.in-addr.arpa. to cm-101236.nmsprime.test.
    Feb 15 14:04:20 nms dhcpd: Added new forward map from cm-101236.nmsprime.test. to 10.6.8.81
    Feb 15 14:04:20 nms dhcpd: DHCPACK on 10.6.8.81 to c8:fb:26:xx:xx:xx via 10.7.255.254
    Feb 15 14:04:20 nms dhcpd: DHCPREQUEST for 10.6.8.81 from c8:fb:26:xx:xx:xx via 10.7.255.254
    Feb 15 02:04:19 nms dhcpd: Added reverse map from 81.8.6.10.in-addr.arpa. to cm-101236.nmsprime.test.
    Feb 15 02:04:19 nms dhcpd: Added new forward map from cm-101236.nmsprime.test. to 10.6.8.81
    Feb 15 02:04:19 nms dhcpd: DHCPACK on 10.6.8.81 to c8:fb:26:xx:xx:xx via 10.7.255.254
    Feb 15 02:04:19 nms dhcpd: DHCPREQUEST for 10.6.8.81 from c8:fb:26:xx:xx:xx via 10.7.255.254



    and ping from cpe:

    ?ro, 17 lut 2021, 14:08:19 CET: 64 bytes from 8.8.8.8: icmp_seq=946 ttl=116 time=19.4 ms
    ?ro, 17 lut 2021, 14:08:20 CET: 64 bytes from 8.8.8.8: icmp_seq=947 ttl=116 time=35.9 ms
    ?ro, 17 lut 2021, 14:08:21 CET: 64 bytes from 8.8.8.8: icmp_seq=948 ttl=116 time=19.3 ms
    ?ro, 17 lut 2021, 14:08:22 CET: 64 bytes from 8.8.8.8: icmp_seq=949 ttl=116 time=38.6 ms
    ?ro, 17 lut 2021, 14:08:23 CET: 64 bytes from 8.8.8.8: icmp_seq=950 ttl=116 time=35.2 ms
    ?ro, 17 lut 2021, 14:12:02 CET: 64 bytes from 8.8.8.8: icmp_seq=1166 ttl=116 time=21.3 ms
    ?ro, 17 lut 2021, 14:12:03 CET: 64 bytes from 8.8.8.8: icmp_seq=1167 ttl=116 time=19.6 ms
    ?ro, 17 lut 2021, 14:12:04 CET: 64 bytes from 8.8.8.8: icmp_seq=1168 ttl=116 time=20.5 ms
    ?ro, 17 lut 2021, 14:12:05 CET: 64 bytes from 8.8.8.8: icmp_seq=1169 ttl=116 time=16.5 ms
    ?ro, 17 lut 2021, 14:12:06 CET: 64 bytes from 8.8.8.8: icmp_seq=1170 ttl=116 time=20.2 ms


    I have no idea where to look for the reason

  3. I've never seen such an behaviour. To me it seems like a CPE issue. I would suggest looking at the logs of your MikroTik CPE and/or try to get in touch with MikroTik.

  4. Unfortunately, this is not MikroTik's fault, I connected another CPE and the situation is identical with Internet access, about 3-4 minutes. I'll see what else wireshark says.

  5. Yes, this would be interesting. Please let us know your findings.

  6. I don't know the reason, but it's back to normal. 1 ping has timed out and the rest are working fine.
    Thank you for your interest.
    greetings