问

华三S1850-28P 出现异常日志导致下联交换机集体断网30秒，然后恢复

9小时前提问

0关注
0收藏，60浏览

Hinson Wong

Hinson Wong 零段

粉丝：0人关注：0人

问题描述：

华三S1850交换机作为一台汇聚交换机 G1/0/1口是接上联交换机S5130H-34C G1/0/24口 S1850交换机 G1/0/13 G1/0/14 G1/0/15 下接接入二层交换机每台接入层交换机都下联30台PC设备出现的问题是经常性断网一分钟然后恢复在故障发生时查看S1850交换机的日志如下显示请问是什么问题呢？求助

%Oct 14 13:48:40:880 2026 S1850-28P MSTP/5/MSTP_BPDU_RECEIVE_EXPIRY: Instance 0's port GigabitEthernet1/0/1 received no BPDU within the rcvdInfoWhile interval. Information of the port aged out. %Oct 14 13:49:23:616 2026 S1850-28P MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:23:871 2026 S1850-28P MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:23:872 2026 S1850-28P MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:23:872 2026 S1850-28P MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:23:872 2026 S1850-28P MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:23:872 2026 S1850-28P MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:23:873 2026 S1850-28P MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/3 has been set to discarding state. %Oct 14 13:49:23:873 2026 S1850-28P MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/4 has been set to discarding state. %Oct 14 13:49:23:873 2026 S1850-28P MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/5 has been set to discarding state. %Oct 14 13:49:23:874 2026 S1850-28P-2F(PE) MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/6 has been set to discarding state. %Oct 14 13:49:23:874 2026 S1850-28P MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/8 has been set to discarding state. %Oct 14 13:49:23:874 2026 S1850-28PMSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/9 has been set to discarding state. %Oct 14 13:49:23:875 2026 S1850-28P MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/10 has been set to discarding state. %Oct 14 13:49:23:875 2026 S1850-28PMSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/13 has been set to discarding state. %Oct 14 13:49:23:875 2026 S1850-28P MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/14 has been set to discarding state. %Oct 14 13:49:23:876 2026 S1850-28P MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/15 has been set to discarding state. %Oct 14 13:49:23:876 2026 S1850-28P MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/20 has been set to discarding state. %Oct 14 13:49:23:876 2026 S1850-28P MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/21 has been set to discarding state. %Oct 14 13:49:23:876 2026 S1850-28P MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/22 has been set to discarding state. %Oct 14 13:49:23:877 2026 S1850-28P- MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/23 has been set to discarding state. %Oct 14 13:49:23:877 2026 S1850-28PMSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/24 has been set to discarding state. %Oct 14 13:49:25:608 2026 S1850-28P MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:28:003 2026 S1850-28P MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:29:081 2026 S1850-28P MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:31:327 2026 S1850-28P MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change.

4 个回答

按时间按赞数

zhiliao_Gixe

zhiliao_Gixe 九段

粉丝：17人关注：9人

根据日志，S1850-28P 收到 MSTP BPDU 报文，说明网络中存在生成树拓扑变化或异常 BPDU 交互，导致下联交换机短暂断网。常见原因是生成树重新收敛或环路。
排查步骤：
1. 检查生成树状态和根桥：
在 S1850 上执行 display stp brief 和 display stp root，确认根桥是否为 S5130H-34C，且各端口转发状态正常。
若根桥频繁切换，说明上游或本机优先级配置不当。
2. 检查端口角色和状态变化：
执行 display stp abnormal-port 查看是否有端口频繁进入 Discarding/Learning 状态。
关注 G1/0/1 与 G1/0/13-15 的端口角色，确认是否因 BPDU 超时或配置错误导致重新选举。
3. 检查是否存在环路：
执行 display loopback-detection 确认是否启用环路检测。
在下联接入口执行 display mac-address 观察 MAC 漂移，若有漂移说明下联存在环路。
4. 检查 BPDU 保护配置：
在 S1850 下联端口（G1/0/13-15）执行 display stp bpdu-protection，若未启用，建议在接入端口配置 stp bpdu-protection 防止下联设备误发 BPDU 引发拓扑变更。
5. 查看详细日志：
执行 display logbuffer 获取完整日志，确认是否伴随端口 up/down 或 TC（拓扑变更）报文。
关键配置建议：
在 S1850 全局和上联口确保生成树模式一致（MSTP），并设置 S5130H-34C 为根桥（优先级 0 或 4096）。
下联端口配置为边缘端口：stp edged-port enable，并启用 stp bpdu-protection。
若确认无环路，可考虑在 S1850 下联端口禁用生成树（stp disable），但需谨慎评估。
若问题持续，建议抓取 BPDU 报文分析或升级 S1850 软件版本。

zhiliao_sEUyB

zhiliao_sEUyB 九段

粉丝：93人关注：11人

日志不全

STP状态老化

MSTP_BPDU_RECEIVE_EXPIRY

日志内容	Instance [UINT32]"s port [STRING] received no BPDU within the rcvdInfoWhile interval. Information of the port aged out.
参数解释	$1：生成树实例编号 $2：接口名
日志等级	5
举例	MSTP/5/MSTP_BPDU_RECEIVE_EXPIRY: Instance 0"s port GigabitEthernet 0/4/1 received no BPDU within the rcvdInfoWhile interval. Information of the port aged out.
日志说明	如果非指定端口在BPDU超时之前没有收到任何BPDU报文，端口状态会改变
处理建议	检查上行设备的STP状态及是否存在恶意攻击

回复Hinson Wong:

接入终端的端口配置下边缘接口

zhiliao_sEUyB 发表时间：9小时前 更多>>

%Oct 14 13:46:06:989 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:46:09:569 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:46:14:070 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:46:16:344 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:46:29:028 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:46:31:531 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:47:08:193 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:47:10:415 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:47:11:431 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:47:13:661 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:47:14:584 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:47:17:073 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:47:18:618 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:47:20:952 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:47:23:986 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:47:25:968 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:47:26:947 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:47:29:139 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:47:54:086 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:47:56:337 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:47:59:189 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:48:01:343 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:48:08:682 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:48:11:306 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:48:14:499 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:48:17:544 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:48:20:710 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:48:23:039 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:48:40:880 2026 S1850-28P-2F(PE) MSTP/5/MSTP_BPDU_RECEIVE_EXPIRY: Instance 0's port GigabitEthernet1/0/1 received no BPDU within the rcvdInfoWh ile interval. Information of the port aged out. %Oct 14 13:49:23:616 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:23:871 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:23:872 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:23:872 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:23:872 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:23:872 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:23:873 2026 S1850-28P-2F(PE) MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/3 has been set to discarding state. %Oct 14 13:49:23:873 2026 S1850-28P-2F(PE) MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/4 has been set to discarding state. %Oct 14 13:49:23:873 2026 S1850-28P-2F(PE) MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/5 has been set to discarding state. %Oct 14 13:49:23:874 2026 S1850-28P-2F(PE) MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/6 has been set to discarding state. %Oct 14 13:49:23:874 2026 S1850-28P-2F(PE) MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/8 has been set to discarding state. %Oct 14 13:49:23:874 2026 S1850-28P-2F(PE) MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/9 has been set to discarding state. %Oct 14 13:49:23:875 2026 S1850-28P-2F(PE) MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/10 has been set to discarding state. %Oct 14 13:49:23:875 2026 S1850-28P-2F(PE) MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/13 has been set to discarding state. %Oct 14 13:49:23:875 2026 S1850-28P-2F(PE) MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/14 has been set to discarding state. %Oct 14 13:49:23:876 2026 S1850-28P-2F(PE) MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/15 has been set to discarding state. %Oct 14 13:49:23:876 2026 S1850-28P-2F(PE) MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/20 has been set to discarding state. %Oct 14 13:49:23:876 2026 S1850-28P-2F(PE) MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/21 has been set to discarding state. %Oct 14 13:49:23:876 2026 S1850-28P-2F(PE) MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/22 has been set to discarding state. %Oct 14 13:49:23:877 2026 S1850-28P-2F(PE) MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/23 has been set to discarding state. %Oct 14 13:49:23:877 2026 S1850-28P-2F(PE) MSTP/6/MSTP_DISCARDING: Instance 0's port GigabitEthernet1/0/24 has been set to discarding state. %Oct 14 13:49:25:608 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:28:003 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:29:081 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:31:327 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:34:394 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:36:760 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:38:100 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:40:205 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:42:201 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:44:555 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:45:534 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:47:819 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:54:051 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change. %Oct 14 13:49:54:938 2026 S1850-28P-2F(PE) MSTP/6/MSTP_FORWARDING: Instance 0's port GigabitEthernet1/0/3 has been set to forwarding state. %Oct 14 13:49:54:938 2026 S1850-28P-2F(PE) MSTP/6/MSTP_FORWARDING: Instance 0's port GigabitEthernet1/0/4 has been set to forwarding state. [S1850-28P-2F(PE)]dis [S1850-28P-2F(PE)]display int [S1850-28P-2F(PE)]display interface br [S1850-28P-2F(PE)]display interface brief The brief information of interface(s) under route mode:

Hinson Wong 发表时间：9小时前

回复Hinson Wong:

。。

zhiliao_sEUyB 发表时间：9小时前

回复zhiliao_sEUyB:

S1850 G1/0/1口经常发生 %Oct 14 14:17:58:069 2026 S1850-28P-2F(PE) MSTP/6/MSTP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified of a topology change.

Hinson Wong 发表时间：9小时前

回复Hinson Wong:

接入终端的端口配置下边缘接口

zhiliao_sEUyB 发表时间：9小时前

IT小工

IT小工九段

粉丝：43人关注：2人

日志含义

MSTP/5/MSTP_BPDU_RECEIVE_EXPIRY: Instance 0's port GigabitEthernet1/0/1 received no BPDU

G1/0/1（S1850 上联 S5130H 的口）在 MSTP 老化时间内，收不到上游 S5130 发送的 BPDU 报文，BPDU 信息老化，MSTP 触发重新计算拓扑，产生 TC（拓扑变更），全网所有交换机清空 MAC 地址表，这就是下联全部 PC 断网 30~60 秒然后自动恢复的根本原因 **H3C。

TC 报文下发后，所有交换机 MAC 表清空，只能泛洪流量，业务中断；等 MAC 表重新学习完成，业务自动恢复。

故障根源（4 个可能性，按概率排序）

上联链路单向丢包 / 网线 / 光口问题（最高概率）网线 8 芯不全、水晶头差、端口双工协商异常，业务流量能通，但 BPDU 报文偶尔丢失。业务大流量时更容易丢 BPDU，触发 BPDU 超时。BPDU 是二层组播报文，优先级不高，拥塞时优先丢弃。
两端 MSTP 配置不一致 S5130H 和 S1850 的 MSTP 域名、修订级别、实例映射 VLAN 不一致，BPDU 被对端丢弃；或者一端 MSTP，另一端 RSTP/STP，digest 不匹配。
S5130H CPU 高 上游 S5130H 业务压力大，CPU 占用过高，来不及生成 / 发送 BPDU 报文，导致 S1850 收不到 BPDU。
S1850 或 S5130H 端口偶发硬件错误、CRC 错包 端口存在错包，BPDU 报文校验失败被丢弃。

补充日志：MSTP_NOTIFIED_TC 就是拓扑变更通知，收到 TC 就会清空 MAC 地址表，全网震荡断网。

现场排查命令（S1850 和 S5130H 都要执行）

查看 STP 端口 BPDU 收发统计，看是否有大量 BPDU 丢失

display stp bpdu-statistics

查看端口错误计数

display interface GigabitEthernet 1/0/1

关注 CRC error、runts、giants，只要有持续增长，就是链路质量问题。 3. 核对 MSTP 域配置（S5130H 与 S1850 两边必须完全一致）

display stp region-configuration

MST 域名、修订级别、VLAN 映射必须一模一样。

查看上游 S5130H CPU 使用率

display cpu-usage

紧急防护配置（立刻部署，降低断网影响）

1、开启 TC 保护（抑制频繁 MAC 表刷新，缓解断网时长）

system-view
stp tc-protection
stp tc-protection threshold 5

作用：10 秒内最多只允许 5 次 MAC 表刷新，防止大量 TC 反复清空 MAC 表，减少业务中断时间H3C。

2、在上联 G1/0/1 开启环路保护（loop-protection，推荐）

G1/0/1 是 S1850 根端口，配置环路保护：当根端口持续收不到 BPDU，不会把端口自动变成指定端口，避免环路 + 拓扑震荡。

interface GigabitEthernet 1/0/1
 stp loop-protection

3、下联接入交换机端口配置边缘端口 + BPDU 保护

S1850 的 G1/0/13 G1/0/14 G1/0/15 下联接入交换机，如果下联接入交换机不再接其他交换机，可以设为边缘端口；下联是交换机不能配边缘端口。

interface GigabitEthernet 1/0/13
 stp edged-port enable
 stp bpdu-protection

定位测试方案

更换 S1850 G1/0/1 与 S5130H 之间网线，重做水晶头；如果是光电复用口，更换光模块 / 光纤。
两端端口强制速率双工 speed 1000 duplex full，关闭自动协商，排除协商抖动。
抓包：在 S5130H 的 G1/0/24 抓包，看是否持续发送 MSTP BPDU（每 2 秒 1 个），故障发生时 BPDU 是否中断。
临时替换上联端口：把 S1850 上联换到 S5130H 另一个空闲端口，观察故障是否还出现。
- 故障消失：原端口 / 网线问题
- 故障依旧：MSTP 域或上游 S5130H CPU 问题

组网建议

S1850 是二层接入汇聚，如果你的网络不存在冗余二层链路（没有双上行），可以直接全局关闭 MSTP，从根源杜绝 STP 拓扑震荡、TC 断网。

system-view
undo stp global enable

⚠️ 关闭 STP 前提：确认全网没有二层环路，关闭后如果存在环路会直接广播风暴瘫痪网络。

排查顺序总结

检查 G1/0/1 端口错包、网线、双工协商；
核对 S5130H 与 S1850 MSTP 域配置；
检查 S5130H CPU；
部署 stp loop-protection、stp tc-protection；
无冗余链路，确认无环路，直接关闭 MSTP 彻底解决震荡。

鸭鸭同学

鸭鸭同学一段

粉丝：0人关注：0人

你这就是stp到时间老化mstp收敛重新计算，时间就是几十秒也就是断网几十秒。

1、可以display stp brief查看根桥是不是都在核心。 2、确认下整个局域网使用的stp是不是都是mstp，别有些设备使用rstp有些使用mstp等。
3、网络存在环路。

回复鸭鸭同学:

二层没有配置边缘端口现在就是不知道是上联导致的还是终端设备一直up/down 导致tc报文增加从而导致断网

Hinson Wong 发表时间：7小时前 更多>>

根桥是在核心一个大的二层组网太乱了各种无管理的二层交换机应该一直在冲突

Hinson Wong 发表时间：9小时前

回复Hinson Wong:

确认傻瓜机就直接配置边缘端口吧。 stp edged-port stp bpdu-protection

鸭鸭同学发表时间：8小时前

回复鸭鸭同学:

已经s1850 14，15，16口下接二层傻瓜交换机已经配置边缘端口了还有一个就是二层下的终端经常出现up/down 的情况

Hinson Wong 发表时间：8小时前

你二层有配置边缘端口嘛，出现up/down问题，很有可能就是接了设备不是终端就会一直协商stp导致一直up/down。当然也可能是物理链路有问题。

鸭鸭同学发表时间：7小时前

回复鸭鸭同学:

二层没有配置边缘端口现在就是不知道是上联导致的还是终端设备一直up/down 导致tc报文增加从而导致断网

Hinson Wong 发表时间：7小时前

编辑答案

分享扩散:

➤

网站相关: 关于我们; 服务条款; 隐私政策; 帮助中心; 经验与权限; 积分规则

联系我们: 联系我们; 建议反馈

常用链接: 标杆的神器下载

关注我们: H3C官网; 新华三服务公众号; 安仔远程运维服务; 新华三商城

内容许可: 除特别说明外，用户内容均可采用知识共享署名-相同方式共享3.0中国大陆许可协议进行许可

本图标版权归新华三集团所有，仅限本社区使用，切勿用做商业目的，违者必究

浙ICP备09064986号-1 浙公网安备 33010802004416号

✖

亲~登录后才可以操作哦!

确定

✖

亲~检测到您登陆的账号未在http://hclhub.h3c.com进行注册

注册后可访问此模块

跳转hclhub

✖

你的邮箱还未认证，请认证邮箱或绑定手机后进行当前操作

✖

侵犯我的权益 >

对根叔社区有害的内容 >

辱骂、歧视、挑衅等（不友善）

侵犯我的权益

泄露了我的隐私 >

侵犯了我企业的权益 >

抄袭了我的内容 >

诽谤我 >

辱骂、歧视、挑衅等（不友善）

骚扰我

泄露了我的隐私

您好，当您发现根叔知了上有泄漏您隐私的内容时，您可以向根叔知了进行举报。请您把以下内容通过邮件发送到pub.zhiliao@h3c.com 邮箱，我们会尽快处理。

1. 您认为哪些内容泄露了您的隐私？（请在邮件中列出您举报的内容、链接地址，并给出简短的说明）
2. 您是谁？（身份证明材料，可以是身份证或护照等证件）

侵犯了我企业的权益

您好，当您发现根叔知了上有关于您企业的造谣与诽谤、商业侵权等内容时，您可以向根叔知了进行举报。请您把以下内容通过邮件发送到 pub.zhiliao@h3c.com 邮箱，我们会在审核后尽快给您答复。

1. 您举报的内容是什么？（请在邮件中列出您举报的内容和链接地址）
2. 您是谁？（身份证明材料，可以是身份证或护照等证件）
3. 是哪家企业？（营业执照，单位登记证明等证件）
4. 您与该企业的关系是？（您是企业法人或被授权人，需提供企业委托授权书）

我们认为知名企业应该坦然接受公众讨论，对于答案中不准确的部分，我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

抄袭了我的内容

原文链接或出处

诽谤我

您好，当您发现根叔知了上有诽谤您的内容时，您可以向根叔知了进行举报。请您把以下内容通过邮件发送到pub.zhiliao@h3c.com 邮箱，我们会尽快处理。

1. 您举报的内容以及侵犯了您什么权益？（请在邮件中列出您举报的内容、链接地址，并给出简短的说明）
2. 您是谁？（身份证明材料，可以是身份证或护照等证件）

我们认为知名企业应该坦然接受公众讨论，对于答案中不准确的部分，我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

对根叔社区有害的内容

垃圾广告信息

色情、暴力、血腥等违反法律法规的内容

政治敏感

不规范转载 >

辱骂、歧视、挑衅等（不友善）

骚扰我

诱导投票

不规范转载

举报说明

产品线		搜索取消
案例类型
发布者
是否解决
是否官方
时间
搜索引擎
匹配模式	默认策略匹配全词匹配整句

华三S1850-28P 出现异常日志导致下联交换机集体断网30秒，然后恢复

问题描述：

MSTP_BPDU_RECEIVE_EXPIRY

日志含义

故障根源（4 个可能性，按概率排序）

现场排查命令（S1850 和 S5130H 都要执行）

紧急防护配置（立刻部署，降低断网影响）

1、开启 TC 保护（抑制频繁 MAC 表刷新，缓解断网时长）

2、在上联 G1/0/1 开启环路保护（loop-protection，推荐）

3、下联接入交换机端口配置边缘端口 + BPDU 保护

定位测试方案

组网建议

排查顺序总结

编辑答案

提出建议