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

irf堆叠设备流量故障问题

2025-06-18提问
  • 0关注
  • 0收藏,392浏览
粉丝:0人 关注:1人

问题描述:

组网及组网描述:

拓扑图如上,上边两台交换机是核心交换机,做了irf堆叠;下面两台接入交换机也做了堆叠;核心与接入做了链路聚合连接。

现在问题是:将任意一台核心交换机关闭,pc就无法ping同路由了,请教什么原因,怎么调整

5 个回答
粉丝:101人 关注:1人

关键的上行组网情况为提供,无法判断

粉丝:116人 关注:9人

正常不会的。

检查下另一台设备日志情况,设备运行状态情况


%Jun 18 15:25:23:639 2025 H3C SHELL/5/SHELL_LOGIN: Console logged in from con1. %Jun 18 15:25:55:343 2025 H3C LAGG/6/LAGG_INACTIVE_PARTNER_KEY_WRONG: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the operational key of the peer port was different than the peer port for the reference port. %Jun 18 15:25:55:343 2025 H3C LAGG/6/LAGG_INACTIVE_RDIRHANDLE: Member port GE1/0/3 of aggregation group RAGG1 changed to the inactive state, because link-aggregation traffic redirection was triggered on the local port. %Jun 18 15:25:55:343 2025 H3C LAGG/6/LAGG_INACTIVE_RDIRHANDLE: Member port GE2/0/3 of aggregation group RAGG1 changed to the inactive state, because link-aggregation traffic redirection was triggered on the local port. %Jun 18 15:25:55:344 2025 H3C LAGG/6/LAGG_INACTIVE_RDIRHANDLE: Member port GE1/0/4 of aggregation group RAGG2 changed to the inactive state, because link-aggregation traffic redirection was triggered on the local port. %Jun 18 15:25:55:344 2025 H3C LAGG/6/LAGG_INACTIVE_RDIRHANDLE: Member port GE2/0/4 of aggregation group RAGG2 changed to the inactive state, because link-aggregation traffic redirection was triggered on the local port. %Jun 18 15:25:55:350 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet2/0/3 changed to down. %Jun 18 15:25:55:351 2025 H3C LAGG/6/LAGG_ACTIVE: Member port GE2/0/1 of aggregation group BAGG1 changed to the active state. %Jun 18 15:25:55:360 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/1 changed to down. %Jun 18 15:25:55:360 2025 H3C IFNET/3/PHY_UPDOWN: Physical state on the interface Bridge-Aggregation1 changed to down. %Jun 18 15:25:55:360 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface Bridge-Aggregation1 changed to down. %Jun 18 15:25:55:360 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/3 changed to down. %Jun 18 15:25:55:360 2025 H3C IFNET/3/PHY_UPDOWN: Physical state on the interface Route-Aggregation1 changed to down. %Jun 18 15:25:55:360 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface Route-Aggregation1 changed to down. %Jun 18 15:25:55:360 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/4 changed to down. %Jun 18 15:25:55:360 2025 H3C IFNET/3/PHY_UPDOWN: Physical state on the interface Route-Aggregation2 changed to down. %Jun 18 15:25:55:360 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface Route-Aggregation2 changed to down. %Jun 18 15:25:55:366 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet2/0/4 changed to down. %Jun 18 15:25:55:372 2025 H3C IFNET/3/PHY_UPDOWN: Physical state on the interface Bridge-Aggregation1 changed to up. %Jun 18 15:25:55:372 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface Bridge-Aggregation1 changed to up. %Jun 18 15:25:55:381 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet2/0/1 changed to up. %Jun 18 15:25:57:123 2025 H3C DEV/5/SYSTEM_REBOOT: System is rebooting now. %Jun 18 15:25:57:774 2025 H3C STP/5/STP_NOT_ROOT: The current switch is no longer the root of Instance 0. %Jun 18 15:25:57:775 2025 H3C STP/6/STP_DETECTED_TC: Instance 0's port Bridge-Aggregation1 detected a topology change. %Jun 18 15:25:57:780 2025 H3C STP/6/STP_NOTIFIED_TC: Instance 0's port Bridge-Aggregation1 was notified a topology change.

zhiliao_OF1dw7 发表时间:2025-06-18 更多>>

%Jun 18 15:25:23:639 2025 H3C SHELL/5/SHELL_LOGIN: Console logged in from con1. %Jun 18 15:25:55:343 2025 H3C LAGG/6/LAGG_INACTIVE_PARTNER_KEY_WRONG: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the operational key of the peer port was different than the peer port for the reference port. %Jun 18 15:25:55:343 2025 H3C LAGG/6/LAGG_INACTIVE_RDIRHANDLE: Member port GE1/0/3 of aggregation group RAGG1 changed to the inactive state, because link-aggregation traffic redirection was triggered on the local port. %Jun 18 15:25:55:343 2025 H3C LAGG/6/LAGG_INACTIVE_RDIRHANDLE: Member port GE2/0/3 of aggregation group RAGG1 changed to the inactive state, because link-aggregation traffic redirection was triggered on the local port. %Jun 18 15:25:55:344 2025 H3C LAGG/6/LAGG_INACTIVE_RDIRHANDLE: Member port GE1/0/4 of aggregation group RAGG2 changed to the inactive state, because link-aggregation traffic redirection was triggered on the local port. %Jun 18 15:25:55:344 2025 H3C LAGG/6/LAGG_INACTIVE_RDIRHANDLE: Member port GE2/0/4 of aggregation group RAGG2 changed to the inactive state, because link-aggregation traffic redirection was triggered on the local port. %Jun 18 15:25:55:350 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet2/0/3 changed to down. %Jun 18 15:25:55:351 2025 H3C LAGG/6/LAGG_ACTIVE: Member port GE2/0/1 of aggregation group BAGG1 changed to the active state. %Jun 18 15:25:55:360 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/1 changed to down. %Jun 18 15:25:55:360 2025 H3C IFNET/3/PHY_UPDOWN: Physical state on the interface Bridge-Aggregation1 changed to down. %Jun 18 15:25:55:360 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface Bridge-Aggregation1 changed to down. %Jun 18 15:25:55:360 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/3 changed to down. %Jun 18 15:25:55:360 2025 H3C IFNET/3/PHY_UPDOWN: Physical state on the interface Route-Aggregation1 changed to down. %Jun 18 15:25:55:360 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface Route-Aggregation1 changed to down. %Jun 18 15:25:55:360 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/4 changed to down. %Jun 18 15:25:55:360 2025 H3C IFNET/3/PHY_UPDOWN: Physical state on the interface Route-Aggregation2 changed to down. %Jun 18 15:25:55:360 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface Route-Aggregation2 changed to down. %Jun 18 15:25:55:366 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet2/0/4 changed to down. %Jun 18 15:25:55:372 2025 H3C IFNET/3/PHY_UPDOWN: Physical state on the interface Bridge-Aggregation1 changed to up. %Jun 18 15:25:55:372 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface Bridge-Aggregation1 changed to up. %Jun 18 15:25:55:381 2025 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet2/0/1 changed to up. %Jun 18 15:25:57:123 2025 H3C DEV/5/SYSTEM_REBOOT: System is rebooting now. %Jun 18 15:25:57:774 2025 H3C STP/5/STP_NOT_ROOT: The current switch is no longer the root of Instance 0. %Jun 18 15:25:57:775 2025 H3C STP/6/STP_DETECTED_TC: Instance 0's port Bridge-Aggregation1 detected a topology change. %Jun 18 15:25:57:780 2025 H3C STP/6/STP_NOTIFIED_TC: Instance 0's port Bridge-Aggregation1 was notified a topology change.

zhiliao_OF1dw7 发表时间:2025-06-18
粉丝:32人 关注:1人

检查一下生成树状态,交换机互联直接都做了端口聚合吗

是的,都做了端口聚合

zhiliao_OF1dw7 发表时间:2025-06-18 更多>>

是的,都做了端口聚合

zhiliao_OF1dw7 发表时间:2025-06-18
粉丝:0人 关注:1人

问题补充:测试将做了irf的设备,重启任意其中一台,另一台同样跟随重启,是模拟器BUG还是堆叠就这样?

粉丝:0人 关注:0人

异常现象,不是 IRF 的正常行为,大概率是模拟器 BUG 或配置异常引起的联动重启。  

编辑答案

你正在编辑答案

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

分享扩散:

提出建议

    +

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

确定

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

对根叔社区有害的内容

×

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

不规范转载

×

举报说明