01-17-2024 05:22 AM
HI Dears,
I have purchased Cisco CBS350-12XS - switch930c4b one 2 months ago, but i noticed the following log notifications also some ports flapping for seconds every some hours, could any one advice, why this problems happened also the solution?!
2147478872 | 2024-Jan-17 13:52:13 | Warning | %STP-W-PORTSTATUS: te1/0/7: STP status Blocking |
2147478873 | 2024-Jan-17 13:52:13 | Warning | %STP-W-PORTSTATUS: te1/0/6: STP status Blocking |
2147478874 | 2024-Jan-17 13:52:13 | Warning | %STP-W-PORTSTATUS: te1/0/5: STP status Blocking |
2147478875 | 2024-Jan-17 13:52:13 | Warning | %STP-W-PORTSTATUS: te1/0/4: STP status Blocking |
2147478876 | 2024-Jan-17 13:52:13 | Warning | %STP-W-PORTSTATUS: te1/0/3: STP status Blocking |
2147478877 | 2024-Jan-17 13:52:13 | Warning | %STP-W-PORTSTATUS: te1/0/2: STP status Blocking |
2147478878 | 2024-Jan-17 13:50:46 | Informational | %AAA-I-CONNECT: New https connection for user admin, source 172.17.9.34 destination 172.17.0.10 ACCEPTED |
2147478879 | 2024-Jan-17 13:43:59 | Warning | %STP-W-PORTSTATUS: te1/0/5: STP status Forwarding |
2147478880 | 2024-Jan-17 13:43:59 | Warning | %STP-W-PORTSTATUS: te1/0/7: STP status Forwarding |
2147478881 | 2024-Jan-17 13:43:59 | Warning | %STP-W-PORTSTATUS: te1/0/4: STP status Forwarding |
2147478882 | 2024-Jan-17 13:43:59 | Warning | %STP-W-PORTSTATUS: te1/0/3: STP status Forwarding |
2147478883 | 2024-Jan-17 13:43:59 | Warning | %STP-W-PORTSTATUS: te1/0/6: STP status Forwarding |
2147478884 | 2024-Jan-17 13:43:59 | Warning | %STP-W-PORTSTATUS: te1/0/8: STP status Forwarding |
2147478885 | 2024-Jan-17 13:43:59 | Warning | %STP-W-PORTSTATUS: te1/0/9: STP status Forwarding |
2147478886 | 2024-Jan-17 13:43:59 | Warning | %STP-W-PORTSTATUS: te1/0/2: STP status Forwarding |
2147478887 | 2024-Jan-17 13:43:59 | Warning | %STP-W-PORTSTATUS: te1/0/9: STP status Blocking |
2147478888 | 2024-Jan-17 13:43:59 | Warning | %STP-W-PORTSTATUS: te1/0/8: STP status Blocking |
2147478889 | 2024-Jan-17 13:43:59 | Warning | %STP-W-PORTSTATUS: te1/0/7: STP status Blocking |
2147478890 | 2024-Jan-17 13:43:59 | Warning | %STP-W-PORTSTATUS: te1/0/6: STP status Blocking |
2147478891 | 2024-Jan-17 13:43:59 | Warning | %STP-W-PORTSTATUS: te1/0/5: STP status Blocking |
2147478892 | 2024-Jan-17 13:43:59 | Warning | %STP-W-PORTSTATUS: te1/0/4: STP status Blocking |
2147478893 | 2024-Jan-17 13:43:59 | Warning | %STP-W-PORTSTATUS: te1/0/3: STP status Blocking |
2147478894 | 2024-Jan-17 13:43:59 | Warning | %STP-W-PORTSTATUS: te1/0/2: STP status Blocking |
2147478895 | 2024-Jan-17 12:21:18 | Warning | %STP-W-PORTSTATUS: te1/0/2: STP status Forwarding |
2147478896 | 2024-Jan-17 12:21:18 | Warning | %STP-W-PORTSTATUS: te1/0/7: STP status Forwarding |
2147478897 | 2024-Jan-17 12:21:18 | Warning | %STP-W-PORTSTATUS: te1/0/4: STP status Forwarding |
2147478898 | 2024-Jan-17 12:21:18 | Warning | %STP-W-PORTSTATUS: te1/0/3: STP status Forwarding |
2147478899 | 2024-Jan-17 12:21:18 | Warning | %STP-W-PORTSTATUS: te1/0/5: STP status Forwarding |
2147478900 | 2024-Jan-17 12:21:18 | Warning | %STP-W-PORTSTATUS: te1/0/6: STP status Forwarding |
2147478901 | 2024-Jan-17 12:21:18 | Warning | %STP-W-PORTSTATUS: te1/0/8: STP status Forwarding |
2147478902 | 2024-Jan-17 12:21:18 | Warning | %STP-W-PORTSTATUS: te1/0/9: STP status Forwarding |
2147478903 | 2024-Jan-17 12:21:18 | Warning | %STP-W-PORTSTATUS: te1/0/1: STP status Forwarding |
2147478904 | 2024-Jan-17 12:21:18 | Warning | %STP-W-PORTSTATUS: te1/0/9: STP status Blocking |
2147478905 | 2024-Jan-17 12:21:18 | Warning | %STP-W-PORTSTATUS: te1/0/8: STP status Blocking |
2147478906 | 2024-Jan-17 12:21:18 | Warning | %STP-W-PORTSTATUS: te1/0/7: STP status Blocking |
2147478907 | 2024-Jan-17 12:21:18 | Warning | %STP-W-PORTSTATUS: te1/0/6: STP status Blocking |
2147478908 | 2024-Jan-17 12:21:18 | Warning | %STP-W-PORTSTATUS: te1/0/5: STP status Blocking |
2147478909 | 2024-Jan-17 12:21:18 | Warning | %STP-W-PORTSTATUS: te1/0/4: STP status Blocking |
2147478910 | 2024-Jan-17 12:21:18 | Warning | %STP-W-PORTSTATUS: te1/0/3: STP status Blocking |
2147478911 | 2024-Jan-17 12:21:18 | Warning | %STP-W-PORTSTATUS: te1/0/2: STP status Blocking |
2147478912 | 2024-Jan-17 12:21:17 | Informational | %LINK-I-Up: te1/0/1 |
2147478913 | 2024-Jan-17 12:21:16 | Warning | %LINK-W-Down: te1/0/1 |
2147478914 | 2024-Jan-17 12:21:16 | Informational | %LINK-I-Up: te1/0/1 |
2147478915 | 2024-Jan-17 11:29:18 | Warning | %LINK-W-Down: te1/0/1 |
2147478916 | 2024-Jan-17 11:23:54 | Warning | %STP-W-PORTSTATUS: te1/0/5: STP status Forwarding |
2147478917 | 2024-Jan-17 11:23:51 | Informational | %LINK-I-Up: te1/0/5 |
2147478918 | 2024-Jan-17 11:23:50 | Warning | %LINK-W-Down: te1/0/5 |
2147478919 | 2024-Jan-17 11:23:48 | Informational | %LINK-I-Up: te1/0/5 |
01-18-2024 06:44 AM
%STP -> refers to "spanning-tree" detection
this is a mechanism to prevent loops in your network
=> somehow you created a loop in your network
special packets (BPDU's) are sent out from your switch , pass some other device and come back to the same switch
- check your cabling
- pay attention multiple links from device-1 to device-2, they may need extra configuration
- configure ports where only clients or hosts are connected as "access port"
if not, the switch periodically checks if there is a switch connected which triggers spanning-tree re-calculation
01-20-2024 11:28 PM
Hi Pieterh,
thank you for your reply, i need to inform you that the problem disappearing for sevral days and then appear again without any change in our network, i think if there is a loop the warning messages must appear permentaily until this loop is removed, is it right?
on the other hand, I found the following alerts suddenly appears without doing any changes 2 days ago until now, do you have any advice?!
2147478457 | 2024-Jan-21 09:12:52 | Warning | %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1. |
2147478458 | 2024-Jan-21 09:07:52 | Warning | %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1. |
2147478459 | 2024-Jan-21 09:02:51 | Warning | %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1. |
2147478460 | 2024-Jan-21 08:57:51 | Warning | %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1. |
2147478461 | 2024-Jan-21 08:52:51 | Warning | %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1. |
2147478462 | 2024-Jan-21 08:47:50 | Warning | %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1. |
2147478463 | 2024-Jan-21 08:42:50 | Warning | %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1. |
2147478464 | 2024-Jan-21 08:37:50 | Warning | %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1. |
2147478465 | 2024-Jan-21 08:32:50 | Warning | %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1. |
2147478466 | 2024-Jan-21 08:27:49 | Warning | %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1. |
2147478467 | 2024-Jan-21 08:22:49 | Warning | %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1. |
2147478468 | 2024-Jan-21 08:17:49 | Warning | %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1. |
2147478469 | 2024-Jan-21 08:12:48 | Warning | %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1. |
2147478470 | 2024-Jan-21 08:07:48 | Warning | %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1. |
2147478471 | 2024-Jan-21 08:02:48 | Warning | %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1. |
2147478472 | 2024-Jan-21 07:57:47 | Warning | %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1. |
2147478473 | 2024-Jan-21 07:52:47 | Warning | %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1. |
2147478474 | 2024-Jan-21 07:47:47 | Warning | %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1. |
2147478475 | 2024-Jan-21 07:42:46 | Warning | %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1. |
01-22-2024 12:15 AM
Hi there,
it depends on what you call a change in your network
without proper configuration , just connecting /disconnecting / rebooting a connected PC can initiate the spanning-tree detection
about the mismatch logging
I agree with @liviu.gheorghe you need to check the configuration on both ends of the connection
either use auto <-> auto or fixed <-> fixed
do not use auto <-> fixed because the negotiation may end with a falsely detected speed or duplex
as this is about a TenGig interface , most times you do not want this to fallback!
and TenGig connections most of the times are full-duplex
so set it fixed for an existing/permanent connection (auto as log as you are testing new connections)
sometimes when there is an intermediate network (provider) you cannot always avoid these messages
you speed/duplex needs to match that of the provider equipment, but CDP detects the settings of your equipment on the other side of the provider link. if this don't match, CDP keeps complaining
=> your provider needs to take care both ends of the link are configured the same
01-21-2024 02:28 AM
Hello @raoufsamir ,
The messages in your last post, %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1 , are indicating that you seem to not have the same duplex setting on interface Te 1/0/1 from the CBS 350 switch and the other end of that link.
Can you also share a topology diagram in order to better understand the network which the CBS 350 activates?
Also, have you looked on the other switches that are connected to the CBS 350 if there are similar STP messages in their logs?
01-24-2024 12:33 AM
Thank you all for your help I'll check.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide