Unsolved
6 Posts
0
388
January 1st, 2023 21:00
dell power connect 6248 switch
Dear Team,
please help below logs generate all the time with out topology change any solution kindly share.
SWITCH-1
<189> AUG 12 07:03:02 192.168.3.34-1 TRAPMGR[126181200]: traputil.c(610) 1 %% Spanning Tree Topology Change: 0, Unit: 1
<189> AUG 12 07:05:44 192.168.3.34-1 TRAPMGR[126181200]: traputil.c(610) 2 %% Spanning Tree Topology Change: 0, Unit: 1
<189> AUG 12 07:06:09 192.168.3.34-1 TRAPMGR[126181200]: traputil.c(610) 3 %% Spanning Tree Topology Change: 0, Unit: 1
<189> AUG 12 07:06:12 192.168.3.34-1 TRAPMGR[126181200]: traputil.c(610) 4 %% Spanning Tree Topology Change: 0, Unit: 1
<190> AUG 12 07:06:43 192.168.3.34-1 UNKN[105789488]: dot1s_txrx.c(188) 5 %% dot1sBpduReceive(): Discarding the BPDU, since it is an inalid BPDU type
<189> AUG 12 07:07:58 192.168.3.34-1 TRAPMGR[126181200]: traputil.c(610) 6 %% Spanning Tree Topology Change: 0, Unit: 1
<189> AUG 12 07:09:57 192.168.3.34-1 TRAPMGR[126181200]: traputil.c(610) 7 %% Spanning Tree Topology Change: 0, Unit: 1
<189> AUG 12 07:11:15 192.168.3.34-1 TRAPMGR[126181200]: traputil.c(610) 8 %% Spanning Tree Topology Change: 0, Unit: 1
<189> AUG 12 07:11:19 192.168.3.34-1 TRAPMGR[126181200]: traputil.c(610) 9 %% Spanning Tree Topology Change: 0, Unit: 1
<189> AUG 12 07:11:48 192.168.3.34-1 TRAPMGR[126181200]: traputil.c(610) 10 %% Spanning Tree Topology Change: 0, Unit: 1
<189> AUG 12 07:11:52 192.168.3.34-1 TRAPMGR[126181200]: traputil.c(610) 11 %% Spanning Tree Topology Change: 0, Unit: 1
<189> AUG 12 07:12:21 192.168.3.34-1 TRAPMGR[126181200]: traputil.c(610) 12 %% Spanning Tree Topology Change: 0, Unit: 1
<189> AUG 12 07:12:25 192.168.3.34-1 TRAPMGR[126181200]: traputil.c(610) 13 %% Spanning Tree Topology Change: 0, Unit: 1
<189> AUG 12 07:12:53 192.168.3.34-1 TRAPMGR[126181200]: traputil.c(610) 14 %% Spanning Tree Topology Change: 0, Unit: 1
<189> AUG 12 07:12:57 192.168.3.34-1 TRAPMGR[126181200]: traputil.c(610) 15 %% Spanning Tree Topology Change: 0, Unit: 1
<189> AUG 12 07:22:16 192.168.3.34-1 TRAPMGR[126181200]: traputil.c(610) 16 %% Spanning Tree Topology Change: 0, Unit: 1
<190> AUG 12 07:22:28 192.168.3.34-1 UNKN[105789488]: dot1s_txrx.c(188) 17 %% dot1sBpduReceive(): Discarding the BPDU, since it is an ivalid BPDU type
DiegoLopez
4 Operator
•
2.7K Posts
0
January 2nd, 2023 08:00
Hello @sbastia,
This log message "Discarding the BPDU, since it is an invalid BPDU type" specifies that an invalid spanning tree BPDU was received in an interface of the switch. The reasons for a BPDU to be classified as invalid are numerous.
One of the most common scenario is when the connected device sends a BPDU with a different forward delay. If there is enough CPU (Switch#show process cpu) you can:
1. Raise the logging level to debugging (Switch#config / Switch(config)#logging buffered 7)
2. Enable debugging for spanning tree. (Switch#debug spanning-tree receive)
3. Then check the log messages (Switch #show logging)
You should consider opening a ticket with support to have the logs checked and to input the commands and check the result.
Regards.