Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
600
Views
3
Helpful
5
Replies

CBS350-12XS - switch930c4b Problem

raoufsamir
Level 1
Level 1

‎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?!

21474788722024-Jan-17 13:52:13Warning%STP-W-PORTSTATUS: te1/0/7: STP status Blocking   
21474788732024-Jan-17 13:52:13Warning%STP-W-PORTSTATUS: te1/0/6: STP status Blocking   
21474788742024-Jan-17 13:52:13Warning%STP-W-PORTSTATUS: te1/0/5: STP status Blocking   
21474788752024-Jan-17 13:52:13Warning%STP-W-PORTSTATUS: te1/0/4: STP status Blocking   
21474788762024-Jan-17 13:52:13Warning%STP-W-PORTSTATUS: te1/0/3: STP status Blocking   
21474788772024-Jan-17 13:52:13Warning%STP-W-PORTSTATUS: te1/0/2: STP status Blocking   
21474788782024-Jan-17 13:50:46Informational%AAA-I-CONNECT: New https connection for user admin, source 172.17.9.34 destination 172.17.0.10 ACCEPTED   
21474788792024-Jan-17 13:43:59Warning%STP-W-PORTSTATUS: te1/0/5: STP status Forwarding   
21474788802024-Jan-17 13:43:59Warning%STP-W-PORTSTATUS: te1/0/7: STP status Forwarding   
21474788812024-Jan-17 13:43:59Warning%STP-W-PORTSTATUS: te1/0/4: STP status Forwarding   
21474788822024-Jan-17 13:43:59Warning%STP-W-PORTSTATUS: te1/0/3: STP status Forwarding   
21474788832024-Jan-17 13:43:59Warning%STP-W-PORTSTATUS: te1/0/6: STP status Forwarding   
21474788842024-Jan-17 13:43:59Warning%STP-W-PORTSTATUS: te1/0/8: STP status Forwarding   
21474788852024-Jan-17 13:43:59Warning%STP-W-PORTSTATUS: te1/0/9: STP status Forwarding   
21474788862024-Jan-17 13:43:59Warning%STP-W-PORTSTATUS: te1/0/2: STP status Forwarding   
21474788872024-Jan-17 13:43:59Warning%STP-W-PORTSTATUS: te1/0/9: STP status Blocking   
21474788882024-Jan-17 13:43:59Warning%STP-W-PORTSTATUS: te1/0/8: STP status Blocking   
21474788892024-Jan-17 13:43:59Warning%STP-W-PORTSTATUS: te1/0/7: STP status Blocking   
21474788902024-Jan-17 13:43:59Warning%STP-W-PORTSTATUS: te1/0/6: STP status Blocking   
21474788912024-Jan-17 13:43:59Warning%STP-W-PORTSTATUS: te1/0/5: STP status Blocking   
21474788922024-Jan-17 13:43:59Warning%STP-W-PORTSTATUS: te1/0/4: STP status Blocking   
21474788932024-Jan-17 13:43:59Warning%STP-W-PORTSTATUS: te1/0/3: STP status Blocking   
21474788942024-Jan-17 13:43:59Warning%STP-W-PORTSTATUS: te1/0/2: STP status Blocking   
21474788952024-Jan-17 12:21:18Warning%STP-W-PORTSTATUS: te1/0/2: STP status Forwarding   
21474788962024-Jan-17 12:21:18Warning%STP-W-PORTSTATUS: te1/0/7: STP status Forwarding   
21474788972024-Jan-17 12:21:18Warning%STP-W-PORTSTATUS: te1/0/4: STP status Forwarding   
21474788982024-Jan-17 12:21:18Warning%STP-W-PORTSTATUS: te1/0/3: STP status Forwarding   
21474788992024-Jan-17 12:21:18Warning%STP-W-PORTSTATUS: te1/0/5: STP status Forwarding   
21474789002024-Jan-17 12:21:18Warning%STP-W-PORTSTATUS: te1/0/6: STP status Forwarding   
21474789012024-Jan-17 12:21:18Warning%STP-W-PORTSTATUS: te1/0/8: STP status Forwarding   
21474789022024-Jan-17 12:21:18Warning%STP-W-PORTSTATUS: te1/0/9: STP status Forwarding   
21474789032024-Jan-17 12:21:18Warning%STP-W-PORTSTATUS: te1/0/1: STP status Forwarding   
21474789042024-Jan-17 12:21:18Warning%STP-W-PORTSTATUS: te1/0/9: STP status Blocking   
21474789052024-Jan-17 12:21:18Warning%STP-W-PORTSTATUS: te1/0/8: STP status Blocking   
21474789062024-Jan-17 12:21:18Warning%STP-W-PORTSTATUS: te1/0/7: STP status Blocking   
21474789072024-Jan-17 12:21:18Warning%STP-W-PORTSTATUS: te1/0/6: STP status Blocking   
21474789082024-Jan-17 12:21:18Warning%STP-W-PORTSTATUS: te1/0/5: STP status Blocking   
21474789092024-Jan-17 12:21:18Warning%STP-W-PORTSTATUS: te1/0/4: STP status Blocking   
21474789102024-Jan-17 12:21:18Warning%STP-W-PORTSTATUS: te1/0/3: STP status Blocking   
21474789112024-Jan-17 12:21:18Warning%STP-W-PORTSTATUS: te1/0/2: STP status Blocking   
21474789122024-Jan-17 12:21:17Informational%LINK-I-Up:  te1/0/1   
21474789132024-Jan-17 12:21:16Warning%LINK-W-Down:  te1/0/1   
21474789142024-Jan-17 12:21:16Informational%LINK-I-Up:  te1/0/1   
21474789152024-Jan-17 11:29:18Warning%LINK-W-Down:  te1/0/1   
21474789162024-Jan-17 11:23:54Warning%STP-W-PORTSTATUS: te1/0/5: STP status Forwarding   
21474789172024-Jan-17 11:23:51Informational%LINK-I-Up:  te1/0/5   
21474789182024-Jan-17 11:23:50Warning%LINK-W-Down:  te1/0/5   
21474789192024-Jan-17 11:23:48Informational%LINK-I-Up:  te1/0/5   
Labels:
0 Helpful
5 Replies 5

pieterh
VIP
VIP

‎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

raoufsamir
Level 1
Level 1
In response to pieterh

‎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?!

21474784572024-Jan-21 09:12:52Warning%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1.   
21474784582024-Jan-21 09:07:52Warning%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1.   
21474784592024-Jan-21 09:02:51Warning%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1.   
21474784602024-Jan-21 08:57:51Warning%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1.   
21474784612024-Jan-21 08:52:51Warning%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1.   
21474784622024-Jan-21 08:47:50Warning%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1.   
21474784632024-Jan-21 08:42:50Warning%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1.   
21474784642024-Jan-21 08:37:50Warning%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1.   
21474784652024-Jan-21 08:32:50Warning%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1.   
21474784662024-Jan-21 08:27:49Warning%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1.   
21474784672024-Jan-21 08:22:49Warning%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1.   
21474784682024-Jan-21 08:17:49Warning%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1.   
21474784692024-Jan-21 08:12:48Warning%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1.   
21474784702024-Jan-21 08:07:48Warning%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1.   
21474784712024-Jan-21 08:02:48Warning%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1.   
21474784722024-Jan-21 07:57:47Warning%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1.   
21474784732024-Jan-21 07:52:47Warning%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1.   
21474784742024-Jan-21 07:47:47Warning%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1.   
21474784752024-Jan-21 07:42:46Warning%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface te1/0/1.   

 

0 Helpful

pieterh
VIP
VIP
In response to raoufsamir

‎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 

liviu.gheorghe
Spotlight
Spotlight

‎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?

Regards, LG
*** Please Rate All Helpful Responses ***

raoufsamir
Level 1
Level 1

‎01-24-2024 12:33 AM

Thank you all for your help I'll check. 

0 Helpful
Customers Also Viewed These Support Documents
Review Cisco Networking for a $25 gift card