NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

thomaskrampe's avatar
thomaskrampe
Aspirant
Jan 14, 2016

[FVS336GV3] ERROR: miiSwitchRegisterRead: Timeout at page

After a reboot of a FVS336Gv3 I see a lot of this errors. Slow logon to the webinterface will happen and after several minutes no WAN -DMZ or WAN - LAN access is possible. I have configured the FVS336 in NAT mode after a cable modem and have a /29 static public network.

 

[FVS336GV3]Wed Jan 13 12:30:21 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x1 addr 0x0
tcindex_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980
[FVS336GV3]Wed Jan 13 13:06:27 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] xt_TCPMSS: bad length (320 bytes)
out at page 0x1 addr 0x0
tcindex_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980
[FVS336GV3]Wed Jan 13 13:27:24 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x1 addr 0x0
tcindex_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980
[FVS336GV3]Wed Jan 13 14:45:13 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x21 addr 0x18
index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980
[FVS336GV3]Wed Jan 13 15:30:12 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x22 addr 0x0

index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980
[FVS336GV3]Wed Jan 13 15:32:29 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x20 addr 0x98
index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980
[FVS336GV3]Wed Jan 13 15:47:24 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x1 addr 0x0
8
index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980
[FVS336GV3]Wed Jan 13 15:52:29 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x24 addr 0xc0
index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980
[FVS336GV3]Wed Jan 13 16:07:31 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x24 addr 0x50
index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980
[FVS336GV3]Wed Jan 13 17:32:31 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x22 addr 0x14
index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980
[FVS336GV3]Wed Jan 13 18:07:35 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x22 addr 0x14
index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980
[FVS336GV3]Wed Jan 13 19:48:56 2016((GMT+0100)) [FVS336GV3][System][VIPSECURE] Could not find configuration for 66.240.236.119[1659]

[FVS336GV3]Wed Jan 13 20:12:34 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x1 addr 0x4
4
index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980
[FVS336GV3]Wed Jan 13 20:57:19 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x20 addr 0x94
index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980
[FVS336GV3]Wed Jan 13 21:02:23 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x20 addr 0x10
index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980
[FVS336GV3]Wed Jan 13 21:37:41 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] xt_TCPMSS: bad length (320 bytes)
out at page 0x20 addr 0x10
index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980
[FVS336GV3]Wed Jan 13 22:15:21 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x22 addr 0x14
index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980
[FVS336GV3]Wed Jan 13 22:27:22 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x1 addr 0x4
4
index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980
[FVS336GV3]Wed Jan 13 22:52:34 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x24 addr 0x98
index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980
[FVS336GV3]Wed Jan 13 22:57:31 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x23 addr 0x10
index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980

Any help?

Troubleshooting
Warranty & Contracts

3 Replies

  • DaneA's avatar
    DaneA
    NETGEAR Employee Retired
    Jan 14, 2016

    Hi thomaskrampe,

     

    Welcome to the community! :)

     

    Let us isolate the problem.  Kindly answer the questions below:

     

    a. Why did you reboot the FVS336Gv3?

    b. For how long did it took before the internet access came back when you lost internet access after doing a reboot?

    c. Did you happen to try to reboot the FVS336Gv3 again and does it show the same errors? 

    d. Does the problem happen all the time whenever you reboot the FVS336Gv3?

    e. Have you ever check if you have internet access by connecting a PC straight to the modem after you lost internet access through the FVS336Gv3 to isolate the problem?

    f. Did you modify any settings on the FVS336Gv3 recently before the problem occured?

    g. Are there any changes within your existing network before the problem occured?

    h. What is the current firmware version of your FVS336Gv3?

     

    I look forward to your response.

     

     

    Regards,

     

    DaneA
    NETGEAR Community Team

    • thomaskrampe's avatar
      thomaskrampe
      Aspirant
      Jan 14, 2016

      a. because it's done automatically every night

      b.after reboot (it takes up to 5 min.) internet access inbound (outbound there is no problem), then between 1 h und 2 h no inbound connection is possible

      c.again and again same result

      d. yes

      e. yes, no problem when I connect to the cable modem (but again no problem outbound)

      f. no just the base configuration

      g. nope, not as far as I know ;-)

      h. 

      Firmware Version:4.3.3-6

       

      The problem is only for WAN to DMZ or WAN to LAN connections. I have a /29 public static subnet which points to the DMZ port with a separated switch (no vlan) and another switch connected to the LAN port. I use the FW in NAT mode and have all available IP-Addresses under WAN1 Secondary addresses (except the addresses from the cable modem and the firewall). Also during nromal operation I have a lot of miiSwitchRegisterRead: Timeout error in the log file.

      • JohnRo's avatar
        JohnRo
        NETGEAR Employee Retired
        Jan 14, 2016

        Hello thomaskrape, 

         

        Can you try to uncheck "Block UDP Flood", see if this helps fix the issue. You can find this setting on Security>Firewall Rules>Attack Checks. You are already running on the latest firmware so I cannot say this is a firmware issue. 

         

        I hope this helps, let us know. 

         

        Thanks, 

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More