Problem %LINK-Down %LINK-W-Up ports cisco sf350

[jmpatagonia]

Hello we are installed a Cisco SF350 new switch, and note that on "RAM Memory Log Table" appear frequently so many messages, like:

--------
Warning %STP-W-PORTSTATUS: fa24: STP status Forwarding
Informational %LINK-I-Up: fa24
Warning %LINK-W-Down: fa24
--------

allways from a differentt port. Happening on various ports but not on all ports. Whats this meaning ?

Active Firmware File: image_tesla_hybrid_2.5.8.12_release_cisco_signed.bin
Active Firmware Version: 2.5.8.12

Regards.

[Kasun Bandara]

Hi,

this means, your ports are flapping.

1. can be issue in physical cables

2. can be issue in port connectors on cable

3. can be issue with connected device's network port

better have a check on all cables and connectors

rate this and mark as answer if this resolved your concern

[Georg Pauwen]

Hello,

you are running the latest firmware, so upgrading is not an option. I think on the SF300 series, STP is enabled by default on all ports.

If these are access ports with user devices, you don't need to run STP at all on these ports. The link below has instructions on how to turn STP off oh ports.

https://www.cisco.com/c/en/us/support/docs/smb/switches/cisco-small-business-200-series-smart-switches/smb81-setup-spanning-tree-protocol-stp-on-a-interface-on-the-200-3.html

[balaji.bandi]

where is this port connected fa24 ? if this connected to end device make it as access port. also STP portfast ?

[jmpatagonia]

Hello all thanks for thew answers. The port 24 is connect to a pc whit Windows 7, but I can detect this problem on many ports, not at all, and this ports are repeatedly all times. I think the problem es a cable that connected to the PC, because remove the patchera in the middle and the problem continue. By I change the cable whit type A for a type B, may the problem round for this side ?

attach a log trace

2147483610 2021-Oct-12 11:25:46 Warning %STP-W-PORTSTATUS: fa6: STP status Forwarding
2147483611 2021-Oct-12 11:25:41 Informational %LINK-I-Up: fa6
2147483612 2021-Oct-12 11:25:40 Warning %LINK-W-Down: fa6
2147483613 2021-Oct-12 11:22:34 Warning %STP-W-PORTSTATUS: fa24: STP status Forwarding
2147483614 2021-Oct-12 11:22:29 Informational %LINK-I-Up: fa24
2147483615 2021-Oct-12 11:22:27 Warning %LINK-W-Down: fa24
2147483616 2021-Oct-12 11:16:20 Warning %STP-W-PORTSTATUS: fa6: STP status Forwarding
2147483617 2021-Oct-12 11:16:16 Informational %LINK-I-Up: fa6
2147483618 2021-Oct-12 11:16:14 Warning %LINK-W-Down: fa6
2147483619 2021-Oct-12 10:47:18 Warning %STP-W-PORTSTATUS: fa11: STP status Forwarding
2147483620 2021-Oct-12 10:47:13 Informational %LINK-I-Up: fa11
2147483621 2021-Oct-12 10:44:12 Warning %SNMP-W-SNMPAUTHFAIL: Access attempted by unauthorized NMS: 10.11.37.154
2147483622 2021-Oct-12 10:43:40 Warning %SNMP-W-SNMPAUTHFAIL: Access attempted by unauthorized NMS: 10.11.37.154
2147483623 2021-Oct-12 10:43:35 Warning %STP-W-PORTSTATUS: fa24: STP status Forwarding
2147483624 2021-Oct-12 10:43:31 Informational %LINK-I-Up: fa24
2147483625 2021-Oct-12 10:43:28 Warning %LINK-W-Down: fa24
2147483626 2021-Oct-12 10:40:15 Warning %STP-W-PORTSTATUS: fa24: STP status Forwarding
2147483627 2021-Oct-12 10:40:10 Informational %LINK-I-Up: fa24
2147483628 2021-Oct-12 10:40:09 Warning %LINK-W-Down: fa24
2147483629 2021-Oct-12 10:26:05 Warning %STP-W-PORTSTATUS: fa22: STP status Forwarding
2147483630 2021-Oct-12 10:26:00 Informational %LINK-I-Up: fa22
2147483631 2021-Oct-12 10:25:56 Warning %LINK-W-Down: fa22
2147483632 2021-Oct-12 10:20:48 Warning %STP-W-PORTSTATUS: fa22: STP status Forwarding
2147483633 2021-Oct-12 10:20:43 Informational %LINK-I-Up: fa22
2147483634 2021-Oct-12 10:20:41 Warning %LINK-W-Down: fa22
2147483635 2021-Oct-12 10:02:40 Warning %STP-W-PORTSTATUS: fa6: STP status Forwarding
2147483636 2021-Oct-12 10:02:35 Informational %LINK-I-Up: fa6
2147483637 2021-Oct-12 10:02:22 Warning %LINK-W-Down: fa6
2147483638 2021-Oct-12 09:20:32 Warning %SNMP-W-SNMPAUTHFAIL: Access attempted by unauthorized NMS: 10.11.37.156
2147483639 2021-Oct-12 09:12:52 Warning %STP-W-PORTSTATUS: fa18: STP status Forwarding
2147483640 2021-Oct-12 09:12:48 Informational %LINK-I-Up: fa18
2147483641 2021-Oct-12 08:44:06 Warning %STP-W-PORTSTATUS: fa6: STP status Forwarding
2147483642 2021-Oct-12 08:44:01 Informational %LINK-I-Up: fa6
2147483643 2021-Oct-12 08:42:35 Warning %LINK-W-Down: fa6

[jmpatagonia]

maybe can affect to this problem that some pc's are on T568A and others with T568B ? on the switch ?

[balaji.bandi]

Do you mean by changing the patch resolved?

[jmpatagonia]

Hello balaji.band, I try to change the patchcord by a crossover certificated patchcrod and the problem it seems to be diminish, can be ?

And also for trying to resolv I disable IPV6 on the windows client, we just use ipv4.

[balaji.bandi]

Thanks for sharing your views here.

[jmpatagonia]

OK for this moment we are try to changing the onboard nic of the PC for a new installed nic, we are trying differents thinks to figureout the problem. We see that when PC user flapping on the dhcp server have an entry requesting again ip.

I updating all testing that we try, to find the solution.

regards.