问

10508+收到TC报文后，没有向其它DP口扩散

2天前提问

0关注
0收藏，49浏览

zhiliao_H9EnVh

zhiliao_H9EnVh 零段

粉丝：0人关注：1人

问题描述：

核心*2+M-lag，下挂接入交换机

通过查看dis stp tc，Send方向计算为0，其它交换机也没有收到TC置位的BPDU，这是什么情况

<10508x_M>*Apr 1 15:35:41:721 2025 Core_10508x_M STP/7/TC: -MDC=1; TC event Receiving TC occurs on Instance 0's port8982(Bridge-Aggregation100) .
%Apr 1 15:35:41:721 2025 Core_10508x_M STP/6/STP_NOTIFIED_TC: -MDC=1; Instance 0's port Bridge-Aggregation100 was notified a topology change.
*Apr 1 15:35:43:693 2025 Core_10508x_M STP/7/TC: -MDC=1; TC event Sending TCA occurs on Instance 0's port8982(Bridge-Aggregation100) .

<s5130s>%Apr 1 15:35:41:706 2025 100JG-s5130s STP/6/STP_DETECTED_TC: Instance 0's port GigabitEthernet1/0/5 detected a topology change.
*Apr 1 15:35:41:707 2025 100JG-s5130s STP/7/TC: TC event Sending TC occurs on Instance 0's port632(Bridge-Aggregation1) .
*Apr 1 15:35:41:707 2025 100JG-s5130s STP/7/TC: TC event Sending TC occurs on Instance 0's port5(GigabitEthernet1/0/5) .
*Apr 1 15:35:43:695 2025 100JG-s5130s STP/7/TC: TC event Receiving TCA occurs on Instance 0's port632(Bridge-Aggregation1) .
*Apr 1 15:35:44:705 2025 100JG-s5130s STP/7/TC: TC event Sending TC occurs on Instance 0's port5(GigabitEthernet1/0/5) .
*Apr 1 15:35:44:705 2025 100JG-s5130s STP/7/TC: TC event TcWhile Expiring occurs on Instance 0's port5(GigabitEthernet1/0/5) .

[10508x_M]DIS STP interface Bridge-Aggregation 2
----[CIST][Port8971(Bridge-Aggregation2)][FORWARDING][M-LAG]----
Port protocol       : Enabled
Port role           : Designated Port (Boundary)
Port ID             : 128.8971
Port cost(Legacy)   : COnfig=auto, Active=18
Desg.bridge/port    : 0.80e4-5575-4420, 128.779
Port edged          : COnfig=disabled, Active=disabled
Port filter         : COnfig=default, Active=disabled
Point-to-Point      : COnfig=auto, Active=true
Transmit limit      : 10 packets/hello-time
TC-Restriction      : Disabled
Role-Restriction    : Disabled
Protection type     : COnfig=none, Active=none
MST BPDU format     : COnfig=auto, Active=802.1s
Port Config-
Digest-Snooping     : Disabled
Rapid transition    : True
Num of VLANs mapped : 10
Port times          : Hello 2s MaxAge 20s FwdDelay 15s MsgAge 0s RemHops 20
BPDU sent           : 6563284
          TCN: 0, Config: 0, RST: 0, MST: 6563284
BPDU received       : 41
          TCN: 0, Config: 0, RST: 0, MST: 41

4 个回答

按时间按赞数

zhiliao_sEUyB

zhiliao_sEUyB 九段

粉丝：133人关注：8人

根据日志及描述，核心交换机收到TC事件但接入交换机未发送/收到TC BPDU的可能原因如下：

1. **本地端口状态震荡**
核心的M-LAG聚合口Bridge-Aggregation100可能存在链路闪断（如光模块故障、光纤松动等），触发本地生成TC事件。由于M-LAG控制协议同步机制，可能未向下游发送TC BPDU。

2. **TC抑制机制生效**
检查核心交换机是否配置了`stp tc-restriction`命令，该功能会阻止TC报文向下游传播，导致接入交换机计数器未增长。

3. **M-LAG域内拓扑变化**
M-LAG双活设备间控制协议（如Keepalive链路）的交互可能触发生成树重新收敛，但变化被限制在M-LAG域内，未扩散到接入层。

**处理建议：**
- 执行 `display stp interface Bridge-Aggregation100` 检查核心聚合口角色及状态，确认是否处于根端口或指定端口
- 使用 `display interface Bridge-Aggregation100` 查看链路CRC错包、UP/DOWN历史记录
- 检查M-LAG配置：`display m-lag summary` 确认Peer-link状态，`m-lag mad exclude interface`是否包含聚合口
- 临时关闭TC限制功能观察现象：`undo stp tc-restriction`
- 启用STP调试日志：`debugging stp event tc` 实时跟踪TC事件来源

若排查后确认无物理链路问题，且TC事件为偶发现象，可判定为正常网络收敛行为，无需干预。若持续高频触发，需检查M-LAG Peer-link及跨设备聚合配置一致性。