• 全部
  • 经验案例
  • 典型配置
  • 技术公告
  • FAQ
  • 漏洞说明
  • 全部
  • 全部
  • 大数据引擎
  • 知了引擎
产品线
搜索
取消
案例类型
发布者
是否解决
是否官方
时间
搜索引擎
匹配模式
高级搜索

S5560X-54C-EI 接口频繁震荡

11小时前提问
  • 0关注
  • 0收藏,39浏览
粉丝:0人 关注:0人

问题描述:

S5560X-54C-EI是带外管理交换机,接一台S6800-54QF设备。S5560X-54C-EI的0/0/38口接口S6800-54QF的M-GigabitEthernet0/0/0,最近几天互联接口频繁Up/Down,S5560X-54C-EI设备端已换过接口和网线测试,还是会出现接口Up/Down告警。

S5560X-54C-EI下的配置:

interface GigabitEthernet1/0/38

 port link-mode bridge

 port access vlan XXX

 stp edged-port

#

GigabitEthernet1/0/38

Current state: UP

Line protocol state: UP

IP packet frame type: Ethernet II, hardware address: 8c94-6a98-32c7

Description: GigabitEthernet1/0/38 Interface

Bandwidth: 1000000 kbps

Loopback is not set

Media type is twisted pair

Port hardware type is 1000_BASE_T

1000Mbps-speed mode, full-duplex mode

Link speed type is autonegotiation, link duplex type is autonegotiation

Flow-control is not enabled

Maximum frame length: 10000

Allow jumbo frames to pass

Broadcast max-ratio: 100%

Multicast max-ratio: 100%

Unicast max-ratio: 100%

PVID: 402

MDI type: Automdix

Port link-type: Access

 Tagged VLANs:   None

 Untagged VLANs: 402

Port priority: 0

Last link flapping: 0 hours 19 minutes 17 seconds

Last clearing of counters: Never

Current system time:2026-08-21 15:38:53 CST+08:00:00

Last time when physical state changed to up:2026-08-21 15:19:36 CST+08:00:00

Last time when physical state changed to down:2026-08-21 15:19:32 CST+08:00:00

 Peak input rate: 50775 bytes/sec, at 2026-08-21 09:03:16 

 Peak output rate: 3612 bytes/sec, at 2026-08-18 16:59:14 

 Last 300 seconds input: 0 packets/sec 52 bytes/sec 0%

 Last 300 seconds output: 3 packets/sec 345 bytes/sec 0%

 Input (total):  207786 packets, 65575801 bytes

134834 unicasts, 726 broadcasts, 72226 multicasts, 0 pauses

 Input (normal):  207786 packets, - bytes

134834 unicasts, 726 broadcasts, 72226 multicasts, 0 pauses

 Input:  0 input errors, 0 runts, 0 giants, 0 throttles

0 CRC, 0 frame, - overruns, 0 aborts

- ignored, - parity errors

 Output (total): 6254967 packets, 696797911 bytes

140079 unicasts, 21493 broadcasts, 6093395 multicasts, 0 pauses

 Output (normal): 6254967 packets, - bytes

140079 unicasts, 21493 broadcasts, 6093395 multicasts, 0 pauses

 Output: 0 output errors, - underruns, - buffer failures

0 aborts, 0 deferred, 0 collisions, 0 late collisions

0 lost carrier, - no carrier

IPv4 traffic statistics:

 Last 300 seconds input rate: 0 packets/sec, 0 bytes/sec

 Last 300 seconds output rate: 0 packets/sec, 0 bytes/sec

 Input: 0 packets, 0 bytes

 Output: 0 packets, 0 bytes

IPv6 traffic statistics:

 Last 300 seconds input rate: 0 packets/sec, 0 bytes/sec

 Last 300 seconds output rate: 0 packets/sec, 0 bytes/sec

 Input: 0 packets, 0 bytes

 Output: 0 packets, 0 bytes

%Aug 18 13:42:20:110 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 18 13:42:20:110 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 18 13:42:22:400 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 18 13:42:22:401 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 18 13:43:02:747 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 18 13:43:02:748 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 18 13:43:04:566 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 18 13:43:04:568 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 18 13:45:32:569 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 18 13:45:32:571 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 18 13:45:33:322 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 18 13:45:33:324 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 18 13:45:37:648 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 18 13:45:37:649 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 18 15:28:43:524 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 18 15:28:43:524 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 18 15:28:47:218 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 18 15:28:47:219 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 18 15:28:59:001 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 18 15:28:59:002 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 18 15:29:01:682 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 18 15:29:01:683 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 18 15:29:05:740 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 18 15:29:05:741 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 18 15:29:16:682 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 18 15:29:16:683 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 18 15:29:23:076 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 18 15:29:23:078 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 18 15:29:25:759 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 18 15:29:25:762 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 20 15:02:58:399 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 20 15:02:58:400 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 20 15:03:04:232 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 20 15:03:04:235 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 20 15:05:08:198 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 20 15:05:08:199 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 20 15:05:10:925 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 20 15:05:10:926 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 21 15:19:32:962 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 21 15:19:32:966 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to down.

%Aug 21 15:19:36:108 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/38 changed to up.

%Aug 21 15:19:36:109 2026 SC-GDS-I06-MGT-H3CSW20 IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/38 changed to up.

S6800-54QF下的信息:

interface M-GigabitEthernet0/0/0

 ip binding vpn-instance Mgmt

 ip address 10.158.32.176 255.255.255.0

#

M-GigabitEthernet0/0/0

Current state: UP

Line protocol state: UP

Description: M-GigabitEthernet0/0/0 Interface

Bandwidth: 1000000 kbps

Maximum transmission unit: 1500

Internet address: 10.158.32.176/24 (Primary)

IP packet frame type: Ethernet II, hardware address: 28c9-7aa5-9828

IPv6 packet frame type: Ethernet II, hardware address: 28c9-7aa5-9828

Last link flapping: 17 hours 56 minutes 40 seconds

Last clearing of counters: Never

Current system time:2026-08-21 09:01:54 beijing+08:00:00

Last time when physical state changed to up:2026-08-20 15:05:14 beijing+08:00:00

Last time when physical state changed to down:2026-08-20 15:05:10 beijing+08:00:00

Media type is twisted pair, loopback not set

Port hardware type is 1000_BASE_T

1000Mbps-speed mode , full-duplex mode 

Link speed type is autonegotiation , Link duplex type is autonegotiation

input:   6167095 packets, 687838892 bytes

         21278 broadcasts,6025138 multicasts

input:   - input errors,- runts,- giants,- throttles,0 CRC

         - frame,- overruns,- aborts,- ignored,- parity errors

output:  170773 packets, - bytes

         725 broadcasts,71433 multicasts

output:  - output errors,- underruns,- buffer failures

         - aborts,- deferred,- collisions,- late collisions

         - lost carrier,- no carrier

%Aug 20 15:03:00:507 2026 SC-GDS-I06-YW-H3CSW16 IFNET/3/PHY_UPDOWN: Physical state on the interface M-GigabitEthernet0/0/0 changed to down.

%Aug 20 15:03:00:507 2026 SC-GDS-I06-YW-H3CSW16 IFNET/5/LINK_UPDOWN: Line protocol state on the interface M-GigabitEthernet0/0/0 changed to down.

%Aug 20 15:03:06:760 2026 SC-GDS-I06-YW-H3CSW16 IFNET/3/PHY_UPDOWN: Physical state on the interface M-GigabitEthernet0/0/0 changed to up.

%Aug 20 15:03:06:760 2026 SC-GDS-I06-YW-H3CSW16 IFNET/5/LINK_UPDOWN: Line protocol state on the interface M-GigabitEthernet0/0/0 changed to up.

%Aug 20 15:03:07:483 2026 SC-GDS-I06-YW-H3CSW16 LLDP/6/LLDP_CREATE_NEIGHBOR: Nearest bridge agent neighbor created on port M-GigabitEthernet0/0/0 (IfIndex 1611), neighbor's chassis ID is 8c94-6a98-3278, port ID is GigabitEthernet1/0/38.

%Aug 20 15:05:10:340 2026 SC-GDS-I06-YW-H3CSW16 IFNET/3/PHY_UPDOWN: Physical state on the interface M-GigabitEthernet0/0/0 changed to down.

%Aug 20 15:05:10:342 2026 SC-GDS-I06-YW-H3CSW16 IFNET/5/LINK_UPDOWN: Line protocol state on the interface M-GigabitEthernet0/0/0 changed to down.

%Aug 20 15:05:14:642 2026 SC-GDS-I06-YW-H3CSW16 IFNET/3/PHY_UPDOWN: Physical state on the interface M-GigabitEthernet0/0/0 changed to up.

%Aug 20 15:05:14:645 2026 SC-GDS-I06-YW-H3CSW16 IFNET/5/LINK_UPDOWN: Line protocol state on the interface M-GigabitEthernet0/0/0 changed to up.

5 个回答
粉丝:174人 关注:11人

收集诊断联系400分析吧 

粉丝:22人 关注:0人

这种可能是硬件故障,找400定位一下吧


粉丝:15人 关注:9人

排查步骤及命令
1. 检查两端接口协商参数
S5560X端:display interface GigabitEthernet 1/0/38 查看速率、双工模式,是否存在协商不一致、错包(CRC、帧错误);
S6800端带外网管口:display interface M-GigabitEthernet 0/0/0 核对协商模式,建议两端均设为自协商,或强制相同速率/双工(speed 1000、duplex full)。
2. 检查接口震荡日志与统计
S5560X端:display logbuffer | include GigabitEthernet1/0/38 查看Up/Down时间间隔、关联事件;display counters error interface GigabitEthernet 1/0/38 查看物理层错误计数,若持续增长大概率是链路硬件问题。
3. 替换验证链路硬件
已换S5560端接口和网线,需更换S6800端带外网管口(若有备用)、更换成品网线(排除水晶头压接问题),测试是否仍震荡。
4. 检查STP与端口配置
互联口配置stp edged-port会导致STP状态异常震荡,需删除:

interface GigabitEthernet1/0/38
undo stp edged-port

同时确认两端VLAN配置匹配,S6800带外网管口为三层口时,S5560端access VLAN需与S6800管理口同网段。
5. 检查设备运行状态
display device 查看S5560X、S6800单板状态;display power 查看供电是否稳定,排除电源波动导致端口异常。

粉丝:28人 关注:2人

S5560X‑54C‑EI GigabitEthernet1/0/38 对接 S6800‑54QF M‑GigabitEthernet0/0/0 频繁物理层震荡
现象关键信息:
物理层反复 UP/DOWN,日志是 IFNET/3/PHY_UPDOWN,物理层直接 down,不是协议层震荡;
两端接口统计CRC、runts、giants 全部为 0,没有错包;
S5560X 侧已经更换物理端口、更换网线,故障依旧;
对端是 S6800‑54QF带外管理口 M‑GigabitEthernet0/0/0(CPU 板载管理网卡,不是业务交换芯片端口);
S5560X 端口配置:port link‑mode bridge、port access vlan 402、stp edged‑port;两端均为自动协商 1000M 全双工。
核心根因:S6800 M‑GE 带外管理口是 CPU 板载独立网卡,和业务芯片网口 PHY 硬件驱动逻辑不一样;千兆自动协商存在 PHY 兼容抖动,无 CRC 报错,直接物理层闪断。网线、端口更换只能排除业务口故障,不能解决 M‑GE 管理口 PHY 协商兼容问题。
注意:M‑GigabitEthernet不支持强制 speed 1000 duplex full(该管理口硬件限制,不能关闭 auto‑negotiation 强制千兆),只能降级强制 100M 全双工规避协商震荡。
排查步骤(按顺序执行)
步骤 1:先确认硬件交叉测试,定位故障归属
将 S6800 M‑GE0/0/0 直接接一台 PC 千兆网卡,长时间观察是否还会 up/down。
如果接 PC 也震荡:故障在 S6800 M‑GE 管理口本身;
如果接 PC 稳定不震荡:是 M‑GE 与 S5560X 业务口 PHY 自动协商兼容问题,需要配置降级。
步骤 2:规避方案(现场最有效)
⚠️S6800 M‑GigabitEthernet0/0/0 硬件限制:不支持关闭自协商强制 1000M 全双工,只能强制 100M 全双工。
两端同时强制 100M 全双工,关闭自动协商:
S5560X 侧(G1/0/38)
plaintext
interface GigabitEthernet 1/0/38
speed 100
duplex full
undo negotiation auto
save
S6800‑54QF 侧 M‑GigabitEthernet0/0/0
plaintext
interface M‑GigabitEthernet 0/0/0
speed 100
duplex full
undo negotiation auto
save
配置完成后观察 2‑4 小时,确认不再出现 PHY_UPDOWN。
带外管理流量很小,100M 带宽完全足够管理业务。
步骤 3:不希望降速到 100M 的备选方案
不要使用 S6800 的 M‑GE 带外管理口做带外互联,改用 S6800 业务板普通千兆电口做带外管理,业务芯片 PHY 与 S5560X 完全兼容,千兆自协商稳定。(推荐长期方案)
升级 S6800‑54QF 设备版本,部分版本优化 M‑GE 管理口 PHY 协商驱动,有可能改善,但不能保证根治。
步骤 4:排除次要风险点
S5560X 端口配置stp edged‑port,该特性是 STP 协议层面,不会造成物理层 PHY 直接 down,可以保留;
接口统计 0 错误,说明不是网线质量问题,你已经换过网线,不需要反复更换网线;
不是环路问题:环路只会导致协议层震荡,不会直接物理层 PHY down;
M‑GE 管理口属于 CPU 板载网卡,查看 S6800 设备环境,确认设备温度无高温告警:
plaintext
display environment
诊断命令收集
plaintext
#清零接口统计,后续观察是否产生错误包
reset counters interface GigabitEthernet 1/0/38
reset counters interface M‑GigabitEthernet 0/0/0

#查看M‑GE管理口硬件信息
display interface M‑GigabitEthernet 0/0/0
display environment
display version

粉丝:0人 关注:0人

不是哥们你开边缘端口能 不这样才怪咯  stp edged-port为啥要开这个你告诉我

建议复习下边缘端口的作用哈

鸭鸭同学 发表时间:8小时前 更多>>

建议复习下边缘端口的作用哈

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

编辑答案

你正在编辑答案

如果你要对问题或其他回答进行点评或询问,请使用评论功能。

分享扩散:

提出建议

    +

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

确定

亲~检测到您登陆的账号未在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. 您是谁?(身份证明材料,可以是身份证或护照等证件)
我们认为知名企业应该坦然接受公众讨论,对于答案中不准确的部分,我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

对根叔社区有害的内容

×

垃圾广告信息
色情、暴力、血腥等违反法律法规的内容
政治敏感
不规范转载 >
辱骂、歧视、挑衅等(不友善)
骚扰我
诱导投票

不规范转载

×

举报说明