NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
GS752TPP - STP is disabling/blocking several ports
I have a client using a GS752TPPv3 with firmware 6.1.0.10 in an AV system environment. I generally use the M4300/M4200 line up but this model was approved by Wyrestorm for NHD100 series and the budget did not allow for an AV Line switch.
It has been working fine for probably a year with no changes to topology or devices attached. Suddenly ports are becoming disabled and we do not know why. Can someone take a look at the log below and see if anything stands out? I can send the Tech Support log.
<182>1 2022-01-01T00:00:46.686Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet12 moving from Blocking to Forwarding
<182>1 2022-01-01T00:00:46.686Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet11 moving from Blocking to Forwarding
<182>1 2022-01-01T00:00:46.686Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet10 moving from Blocking to Forwarding
<182>1 2022-01-01T00:00:46.686Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet9 moving from Blocking to Forwarding
<182>1 2022-01-01T00:00:46.685Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet8 moving from Blocking to Forwarding
<182>1 2022-01-01T00:00:45.646Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet46 moving from Blocking to Forwarding
<182>1 2022-01-01T00:00:45.646Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet32 moving from Blocking to Forwarding
<182>1 2022-01-01T00:00:45.645Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet7 moving from Blocking to Forwarding
<182>1 2022-01-01T00:00:45.645Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet6 moving from Blocking to Forwarding
<182>1 2022-01-01T00:00:44.605Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet23 moving from Blocking to Forwarding
<182>1 2022-01-01T00:00:44.596Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet12 moving from Disabled to Blocking
<182>1 2022-01-01T00:00:44.595Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet11 moving from Disabled to Blocking
<182>1 2022-01-01T00:00:44.595Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet10 moving from Disabled to Blocking
<182>1 2022-01-01T00:00:43.380Z 192.168.2.253-1 SYSTEM-6-SNMP_TRAPFULL sal_snmp.c(526) %% SNMP notify message is full
<182>1 2022-01-01T00:00:43.379Z 192.168.2.253-1 SYSTEM-6-SNMP_TRAPFULL sal_snmp.c(526) %% SNMP notify message is full
<182>1 2022-01-01T00:00:43.376Z 192.168.2.253-1 SYSTEM-6-SNMP_TRAPFULL sal_snmp.c(526) %% SNMP notify message is full
<182>1 2022-01-01T00:00:43.113Z 192.168.2.253-1 SYSTEM-6-SNMP_TRAPFULL sal_snmp.c(526) %% SNMP notify message is full
<182>1 2022-01-01T00:00:43.075Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet10 moving from Blocking to Disabled
<182>1 2022-01-01T00:00:43.075Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet8 moving from Disabled to Blocking
<182>1 2022-01-01T00:00:43.014Z 192.168.2.253-1 SYSTEM-6-SNMP_TRAPFULL sal_snmp.c(526) %% SNMP notify message is full
<182>1 2022-01-01T00:00:43.815Z 192.168.2.253-1 SYSTEM-6-SNMP_TRAPFULL sal_snmp.c(526) %% SNMP notify message is full
<182>1 2022-01-01T00:00:43.813Z 192.168.2.253-1 SYSTEM-6-SNMP_TRAPFULL sal_snmp.c(526) %% SNMP notify message is full
<182>1 2022-01-01T00:00:43.556Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet8 moving from Blocking to Disabled
<182>1 2022-01-01T00:00:43.556Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet7 moving from Disabled to Blocking
<182>1 2022-01-01T00:00:42.336Z 192.168.2.253-1 SYSTEM-6-SNMP_TRAPFULL sal_snmp.c(526) %% SNMP notify message is full
<182>1 2022-01-01T00:00:42.334Z 192.168.2.253-1 SYSTEM-6-SNMP_TRAPFULL sal_snmp.c(526) %% SNMP notify message is full
<182>1 2022-01-01T00:00:42.295Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet7 moving from Blocking to Disabled
<182>1 2022-01-01T00:00:42.295Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet6 moving from Disabled to Blocking
<182>1 2022-01-01T00:00:42.135Z 192.168.2.253-1 SYSTEM-6-SNMP_TRAPFULL sal_snmp.c(526) %% SNMP notify message is full
<182>1 2022-01-01T00:00:42.133Z 192.168.2.253-1 SYSTEM-6-SNMP_TRAPFULL sal_snmp.c(526) %% SNMP notify message is full
<182>1 2022-01-01T00:00:42.038Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet46 moving from Disabled to Blocking
<182>1 2022-01-01T00:00:42.038Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet32 moving from Disabled to Blocking
<182>1 2022-01-01T00:00:42.037Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet6 moving from Blocking to Disabled
<182>1 2022-01-01T00:00:42.827Z 192.168.2.253-1 SYSTEM-6-SNMP_TRAPFULL sal_snmp.c(526) %% SNMP notify message is full
<182>1 2022-01-01T00:00:42.826Z 192.168.2.253-1 SYSTEM-6-SNMP_TRAPFULL sal_snmp.c(526) %% SNMP notify message is full
<182>1 2022-01-01T00:00:42.817Z 192.168.2.253-1 SYSTEM-6-SNMP_TRAPFULL sal_snmp.c(526) %% SNMP notify message is full
<182>1 2022-01-01T00:00:42.516Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet36 moving from Blocking to Forwarding
<182>1 2022-01-01T00:00:42.516Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet32 moving from Blocking to Disabled
<182>1 2022-01-01T00:00:42.516Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet5 moving from Blocking to Forwarding
<182>1 2022-01-01T00:00:42.516Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet4 moving from Blocking to Forwarding
<182>1 2022-01-01T00:00:42.516Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet3 moving from Blocking to Forwarding
<182>1 2022-01-01T00:00:42.516Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet2 moving from Blocking to Forwarding
<182>1 2022-01-01T00:00:42.515Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet1 moving from Blocking to Forwarding
<182>1 2022-01-01T00:00:42.491Z 192.168.2.253-1 SYSTEM-6-SNMP_TRAPFULL sal_snmp.c(526) %% SNMP notify message is full
<182>1 2022-01-01T00:00:41.249Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet46 moving from Blocking to Disabled
<182>1 2022-01-01T00:00:41.249Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet23 moving from Disabled to Blocking
<182>1 2022-01-01T00:00:41.248Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet10 moving from Disabled to Blocking
<182>1 2022-01-01T00:00:41.241Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet9 moving from Disabled to Blocking
<182>1 2022-01-01T00:00:41.226Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet8 moving from Disabled to Blocking
<182>1 2022-01-01T00:00:41.226Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet7 moving from Disabled to Blocking
<182>1 2022-01-01T00:00:41.225Z 192.168.2.253-1 STP-6-PORT_STATE proto_stp.c(834) %% Port GigabitEthernet6 moving from Disabled to Blocking1 Reply
nmarques wrote:
I have a client using a GS752TPPv3 with firmware 6.1.0.10 in an AV system environment. I generally use the M4300/M4200 line up but this model was approved by Wyrestorm for NHD100 series and the budget did not allow for an AV Line switch.
This short ~5 seconds are looking like a port of the start-up on an network with STP and/or RSTP configured. At the end, all ports are forwarding (unless I oversee one or very few ports).
Provide a topology and a list of devices involved.
Does the problem re-appear -later- after the boot and STP negotiation finished successfully?
Are there other devices on that network participating on STP/RSTP, e.g. another switch, router, other devices?
Regarding to the mentioned Wyrestorm NHD100 Series, I guess one or a few transmitters and many more receivers - and the system is using either unicast or ideally multicast (that would be using ICMP Multicast where the VLAN(s) must be configured accordingly) for the video feeds - not that you don't know this already. That's why the GS752TPPv3 is considered to be used on such a network.
nmarques wrote:
It has been working fine for probably a year with no changes to topology or devices attached. Suddenly ports are becoming disabled and we do not know why. Can someone take a look at the log below and see if anything stands out? I can send the Tech Support log.
Please avoid sharing tech support files with random people on the Internet, since it can contain customer personal, proprietary and site information details - this is mainly for Netgear Support purposes. Share it on demand only with Netgear Support.
Regards,
-Kurt.
(not on behalf of Netgear)
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
