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

Forum Discussion

robfantini's avatar
robfantini
Aspirant
Jan 21, 2018

stack and lag troubleshooting

Hello ,

 

 I have  3 m5300's stacked together.  One of the switches is normally off  as a cold spare. Code version = 10.0.0.53 for both switches.

 

We use lags to connect to  4 other netgear switches +  two proxmox clusters  [ 10 nodes] and a nfs system .

 

Yesterday I tested  rebooting the Management Unit [1]  in order to make sure fail over worked.    It did not.   in order to work properly every lagged switch and proxmox node had to be rebooted.   Prior to that there were limited / slow connections.

 

 the symptoms were :

1- very slow backups to nfs.   what should have taken 10 minutes took 2 hours.

2- network sluggishness

3- un able to connect to some systems.

and more.   we use zabbix and had 60 reports of service / connection issues.

 

Note this thread may take awhile to get to solved as tesitng can only be done off hours -   Saturday afternoon and Sunday morning.

 

Here is an example of a lag we use:

 

lag  9 goes to a  M4100-50-POE prosafe managed switch.     firmware version 10.0.2.26

Web page:

 hashmode [ for all lags ] = 3

 Stp mode Enable

Static mode disable

Link trap disable

 

(GSM7352Sv2) #show running-config interface lag 9

!Current Configuration:
!
interface lag 9
auto-voip protocol-based
description 'to mezz switch'
set igmp mrouter interface
dhcp l2relay
mtu 9216
vlan pvid 8
vlan participation auto 1
vlan participation include 8,20,25,40-41,70,80,90,199
vlan tagging 20,25,40-41,70,80,90,199
exit

 

 

On the m4100:

(M4100-50-POE) #show running-config interface lag 1

!Current Configuration:
!
interface lag 1
auto-voip protocol-based
mtu 9216
vlan participation include 8,20,25,40-41,70,80,90,199
vlan tagging 8,20,25,40-41,70,80,90,199
exit

If you have a suggestion to try to solve this, or would like to see more data please respond.

 

best regards.

 

 

 

 

4 Replies

  • regarding  link trap :  " Link Trap - Specify whether you want to have a trap sent when link status changes. The factory default is enable, which will cause the trap to be sent."

     

    Could someone tell me if that should be used in our case?     Or tried?

     

  • DaneA's avatar
    DaneA
    NETGEAR Employee Retired

    Hi robfantini,

     

    Have you tried to disconnect the LAG connections (4 other NETGEAR switches + 2 proxmox clusters  [10 nodes] & NFS system) to check if fail over will work fine once you reboot the Management Unit?  If not yet, kindly try it and observe.

     

    Also, you can try to disable Link Trap and see if it helps. 

     

    About the slow connections, try to configure Storm Control and check if it helps.  Kindly read pages 493-496 of the GSM7352Sv2 user manual here.  

     

     

    Regards,

     

    DaneA

    NETGEAR Community Team

    • robfantini's avatar
      robfantini
      Aspirant

      DaneA wrote:

      "Have you tried to disconnect the LAG connections (4 other NETGEAR switches + 2 proxmox clusters  [10 nodes] & NFS system) to check if fail over will work fine once you reboot the Management Unit?  If not yet, kindly try it and observe."

       

       Just retest that and  failover is quick.   no issue.

       

       

      "Also, you can try to disable Link Trap and see if it helps. "

      It already is disabled.

       

       

      "About the slow connections, try to configure Storm Control and check if it helps. 

      Kindly read pages 493-496 of the GSM7352Sv2 user manual here.  "

       

      OK just checked -

        Storm control Global Configuration:   was alread enabled and

      Broadcast Storm Control All  was already enabled.

       

       I have a question on Storm Control Interface Configuration:

       

       for ' Broadcast Storm Recovery Mode'    Should that be enabled?

       

       

       

       

       

      I'll do those next.  and will test rebooting the master switch on Saturday.

       

       

      Regards,

       

      DaneA

      NETGEAR Community Team


       

      • DaneA's avatar
        DaneA
        NETGEAR Employee Retired

        robfantini,

         

        Thanks for the feedback.  

         

        To isolate, leave Broadcast Storm Recovery Mode as disabled and observe what happens.  Then, set the threshold for the Broadcast Storm Recovery Level and try to enable Broadcast Storm Recovery Mode then observe again if it helps.

         

         

        Regards,

         

        DaneA

        NETGEAR Community Team

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