Forum Discussion

fainbrog's avatar
fainbrog
On our wavelength
4 months ago

16 consecutive T3 timeouts

Had a few short outages over the last few weeks, logs on the Hub5 show;

13-10-2024 20:48:10

critical

16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

13-10-2024 20:48:10

critical

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

13-10-2024 20:47:02

critical

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

Am running my own router behind the Hub5 (in the DMZ) and it doesn't register an outage in it's logs (which it would do if the Hub was switched off), but we defo have a short stall in connectivity at the time these entries show in the Hub5 log.

Are these kinds of errors something we should be concerned about? Service has been pretty rock-solid for years, other than at the start of first lockdown when there were local congestion issues causing speed issues.

  • Tudor's avatar
    Tudor
    Very Insightful Person

    We need a full set of stats to verify if there is an underlying problem.

      • Tudor's avatar
        Tudor
        Very Insightful Person

        How to get stats from a VM hub (no need to logon to the hub)

        Open a web browser and go to 192.168.0.1 router mode or 192.168.100.1 modem mode

        • Click on the “> Check router status” button
        • Click on the “Downstream” tab, copy the text and paste into your reply, do not take a screen shot
        • Click on the “Upstream” tab, copy the text and paste into your reply
        • Click on the “Networking” tab, copy the text and paste into your reply.
          • Do NOT post photos or screen shots they will be rejected as they contain MAC addresses. The board software will automatically change MAC addresses to **:** if done as above.