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

Forum Discussion

pmapp's avatar
pmapp
Aspirant
Oct 08, 2015
Solved

GS752TXS FP_COUNTER_TABLE Error

Morning All,

 

Switch: GS752TXS (running in a stack of 3 with 10gb DAC)

Firmware: 6.1.0.27

 

We are getting the following errors constantly:

 

<11> Oct 8 09:26:15 10.1.0.21-3 DRIVER[53846932]: broad_hpc_drv.c(4253) 7955209 %% unit 0 FP_COUNTER_TABLE entry 1146 parity error
<11> Oct 8 09:26:15 10.1.0.21-3 DRIVER[53846932]: broad_hpc_drv.c(4253) 7955208 %% _soc_xgs3_mem_dma: FP_COUNTER_TABLE.ipipe0 failed(NAK)
<11> Oct 8 09:26:13 10.1.0.21-3 DRIVER[53846932]: broad_hpc_drv.c(4253) 7955207 %% unit 0 FP_COUNTER_TABLE entry 1146 parity error
<11> Oct 8 09:26:13 10.1.0.21-3 DRIVER[53846932]: broad_hpc_drv.c(4253) 7955206 %% _soc_xgs3_mem_dma: FP_COUNTER_TABLE.ipipe0 failed(NAK)
<11> Oct 8 09:26:11 10.1.0.21-3 DRIVER[53846932]: broad_hpc_drv.c(4253) 7955205 %% unit 0 FP_COUNTER_TABLE entry 1146 parity error
<11> Oct 8 09:26:11 10.1.0.21-3 DRIVER[53846932]: broad_hpc_drv.c(4253) 7955204 %% _soc_xgs3_mem_dma: FP_COUNTER_TABLE.ipipe0 failed(NAK)
<11> Oct 8 09:26:09 10.1.0.21-3 DRIVER[53846932]: broad_hpc_drv.c(4253) 7955203 %% unit 0 FP_COUNTER_TABLE entry 1146 parity error
<11> Oct 8 09:26:09 10.1.0.21-3 DRIVER[53846932]: broad_hpc_drv.c(4253) 7955202 %% _soc_xgs3_mem_dma: FP_COUNTER_TABLE.ipipe0 failed(NAK)
<11> Oct 8 09:26:07 10.1.0.21-3 DRIVER[53846932]: broad_hpc_drv.c(4253) 7955201 %% unit 0 FP_COUNTER_TABLE entry 1146 parity error
<11> Oct 8 09:26:07 10.1.0.21-3 DRIVER[53846932]: broad_hpc_drv.c(4253) 7955200 %% _soc_xgs3_mem_dma: FP_COUNTER_TABLE.ipipe0 failed(NAK)
<11> Oct 8 09:26:05 10.1.0.21-3 DRIVER[53846932]: broad_hpc_drv.c(4253) 7955199 %% unit 0 FP_COUNTER_TABLE entry 1146 parity error
<11> Oct 8 09:26:05 10.1.0.21-3 DRIVER[53846932]: broad_hpc_drv.c(4253) 7955198 %% _soc_xgs3_mem_dma: FP_COUNTER_TABLE.ipipe0 failed(NAK)
<11> Oct 8 09:26:03 10.1.0.21-3 DRIVER[53846932]: broad_hpc_drv.c(4253) 7955197 %% unit 0 FP_COUNTER_TABLE entry 1146 parity error
<11> Oct 8 09:26:03 10.1.0.21-3 DRIVER[53846932]: broad_hpc_drv.c(4253) 7955196 %% _soc_xgs3_mem_dma: FP_COUNTER_TABLE.ipipe0 failed(NAK)
<11> Oct 8 09:26:01 10.1.0.21-3 DRIVER[53846932]: broad_hpc_drv.c(4253) 7955195 %% unit 0 FP_COUNTER_TABLE entry 1146 parity error
<11> Oct 8 09:26:01 10.1.0.21-3 DRIVER[53846932]: broad_hpc_drv.c(4253) 7955194 %% _soc_xgs3_mem_dma: FP_COUNTER_TABLE.ipipe0 failed(NAK)
<11> Oct 8 09:25:59 10.1.0.21-3 DRIVER[53846932]: broad_hpc_drv.c(4253) 7955193 %% unit 0 FP_COUNTER_TABLE entry 1146 parity error

I'm not sure when the errors started, but has been ongoing for a couple of months at least.

 

I'm unable to try a reboot as the stack is in a live environment.


Does anyone have any suggestions or input on the issue?  If any other info is required let me know.



Thanks

Troubleshooting
  • JohnRo's avatar
    JohnRo
    Oct 09, 2015

    Hello pmapp, 

     

    I don't believe it is common to get these kind of errors on switches. If you can, I suggest to just reboot the stack and see if the errors will continue. 

     

    Thanks, 

7 Replies

  • JohnRo's avatar
    JohnRo
    NETGEAR Employee Retired
    Oct 08, 2015

    Hi pmapp, 

     

    Welcome to the community! 

     

    I see you are getting some errors on your switches, let me see if I can help you with this. Upon checking, it appears that these might be DMA erors (Direct Memory Access) on the motherboard(s) on one of the switches. This can also be caused by adding another hardware or module.I have some questions for me to be able to help you further: 

     

    1. How old are the swicthes? 

    2. How long have they been stacked? 

    3. What changes did you make on your network before experiencing these errors? 

     

    Looking forward to your response. 

     

    Thanks, 

    • pmapp's avatar
      pmapp
      Aspirant
      Oct 09, 2015

      Hi JohnRo,

      Thanks for the reply....

       

      1. The switches are coming almost 3 years old.

      2. They have been stacked since day one.

      3. There have been no recent config changes, other than tagging\untagging ports for VLANS.

       

      Thanks for your help.

      • JohnRo's avatar
        JohnRo
        NETGEAR Employee Retired
        Oct 09, 2015

        Hello pmapp, 

         

        I don't believe it is common to get these kind of errors on switches. If you can, I suggest to just reboot the stack and see if the errors will continue. 

         

        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