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

堆叠完后老是弹报文

1天前提问
  • 0关注
  • 0收藏,157浏览
粉丝:0人 关注:3人

问题描述:

H3C-Ten-GigabitEthernet1/0/0/17]%Dec 20 11:17:23:429 2024 H3C LAGG/6/LAGG_PORT_DISCARDING_STATE: Member port XGE1/0/0/17 of BAGG17 changed to the discarding state.

%Dec 20 11:17:23:438 2024 H3C LAGG/6/LAGG_INACTIVE_PHYSTATE: Member port XGE1/0/0/17 of aggregation group BAGG17 changed to the inactive state, because the physical or line protocol state of the port was down.

%Dec 20 11:17:23:447 2024 H3C DEV/2/INTERNALLINK_ALARM_OCCUR: Internal link alarm occurred. (PhysicalIndex=661, PhysicalName=Ten-GigabitEthernet1/0/0/17, RelativeResource=(bustype:mac link,sourceport:(chiptype:3,chassis:1,slot:0,chipid:0,portid:8)), ErrorCode=427001, Reason=MAC chip link failure.)

%Dec 20 11:17:23:448 2024 H3C STP/4/STP_DISPUTE: Instance 0's port Bridge-Aggregation17 received an inferior BPDU from a designated port which is in forwarding or learning state. The designated bridge ID contained in the BPDU is 32768.10b6-5e2a-59c0, and the designated port ID contained in the BPDU is 128.34.

%Dec 20 11:17:23:452 2024 H3C IFNET/3/PHY_UPDOWN: Physical state on the interface Ten-GigabitEthernet1/0/0/17 changed to down.

%Dec 20 11:17:23:453 2024 H3C STP/6/STP_DISCARDING: Instance 0's port Bridge-Aggregation17 has been set to discarding state.

%Dec 20 11:17:23:461 2024 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface Ten-GigabitEthernet1/0/0/17 changed to down.

%Dec 20 11:17:23:470 2024 H3C STP/6/STP_DISPUTE_RESTORATION: Instance 0's port Bridge-Aggregation17 exited the dispute state.

%Dec 20 11:17:23:469 2024 H3C DEV/2/INTERNALLINK_ALARM_OCCUR: Internal link alarm occurred. (PhysicalIndex=661, PhysicalName=Ten-GigabitEthernet1/0/0/17, RelativeResource=(interface:port down), ErrorCode=482002, Reason=The interface Physical state changed to down.)

%Dec 20 11:17:23:478 2024 H3C STP/6/STP_FORWARDING: Instance 0's port Bridge-Aggregation17 has been set to forwarding state.

 

[H3C-Ten-GigabitEthernet1/0/0/17]

[H3C-Ten-GigabitEthernet1/0/0/17]

[H3C-Ten-GigabitEthernet1/0/0/17]

[H3C-Ten-GigabitEthernet1/0/0/17]

[H3C-Ten-GigabitEthernet1/0/0/17]

[H3C-Ten-GigabitEthernet1/0/0/17]dis int bti%Dec 20 11:17:29:069 2024 H3C OPTMOD/4/OPTICAL_WARNING_OCCUR: Transceiver warning alarm occurred. (PhysicalIndex=661, PhysicalName=Ten-GigabitEthernet1/0/0/17, RelativeResource=(transceivertype:10G_BASE_LR_SFP,interface:Ten-GigabitEthernet1/0/0/17,lane:0), ErrorCode=600005, Reason=Transceiver Tx power is too low: CurrentValue = -36.96 dBm, Threshold = -11.25 dBm.)

%Dec 20 11:17:29:070 2024 H3C OPTMOD/4/OPTICAL_WARNING_OCCUR: Transceiver warning alarm occurred. (PhysicalIndex=661, PhysicalName=Ten-GigabitEthernet1/0/0/17, RelativeResource=(transceivertype:10G_BASE_LR_SFP,interface:Ten-GigabitEthernet1/0/0/17,lane:0), ErrorCode=600009, Reason=Transceiver bias current is too low: CurrentValue = 0.12 mA, Threshold =1.00 mA.)

                                                                                                                                                                                             

[H3C-Ten-GigabitEthernet1/0/0/17]                                                                                                                                                            

[H3C-Ten-GigabitEthernet1/0/0/17]dis int br%Dec 20 11:17:39:949 2024 H3C IFNET/4/IF_EGRESS_DROP_RECOVER: -Chassis=2-Slot=0; Packet loss recovers in queue 2 of GigabitEthernet2/0/0/15.      

%Dec 20 11:17:39:953 2024 H3C IFNET/4/IF_BOARD_EGRESS_DROP_RECOVER: -Chassis=2-Slot=0; Packet loss recovers on chassis 2 slot 0.

ief

Brief information on interfaces in route mode:

 

 

 

c 20 11:22:43:264 2024 H3C IFNET/4/IF_EGRESS_DROP_RECOVER: -Chassis=2-Slot=0; Packet loss recovers in queue 2 of GigabitEthernet2/0/0/3.

%Dec 20 11:22:43:268 2024 H3C IFNET/4/IF_EGRESS_DROP_RECOVER: -Chassis=2-Slot=0; Packet loss recovers in queue 2 of GigabitEthernet2/0/0/5.

%Dec 20 11:22:43:271 2024 H3C IFNET/4/IF_EGRESS_DROP_RECOVER: -Chassis=2-Slot=0; Packet loss recovers in queue 2 of GigabitEthernet2/0/0/7.

%Dec 20 11:22:43:293 2024 H3C IFNET/4/IF_EGRESS_DROP_RECOVER: -Chassis=2-Slot=0; Packet loss recovers in queue 2 of GigabitEthernet2/0/0/9.

%Dec 20 11:22:43:298 2024 H3C IFNET/4/IF_EGRESS_DROP_RECOVER: -Chassis=2-Slot=0; Packet loss recovers in queue 2 of GigabitEthernet2/0/0/11.

%Dec 20 11:22:43:303 2024 H3C IFNET/4/IF_EGRESS_DROP_RECOVER: -Chassis=2-Slot=0; Packet loss recovers in queue 2 of GigabitEthernet2/0/0/13.

%Dec 20 11:22:43:307 2024 H3C IFNET/4/IF_EGRESS_DROP_RECOVER: -Chassis=2-Slot=0; Packet loss recovers in queue 2 of GigabitEthernet2/0/0/15.

%Dec 20 11:22:43:318 2024 H3C IFNET/4/IF_BOARD_EGRESS_DROP_RECOVER: -Chassis=2-Slot=0; Packet loss recovers on chassis 2 slot 0.

%Dec 20 11:22:43:898 2024 H3C IFNET/4/IF_EGRESS_DROP_RECOVER: Packet loss recovers in queue 2 of GigabitEthernet1/0/0/1.

%Dec 20 11:22:43:899 2024 H3C IFNET/4/IF_EGRESS_DROP_RECOVER: Packet loss recovers in queue 2 of GigabitEthernet1/0/0/3.

%Dec 20 11:22:43:900 2024 H3C IFNET/4/IF_EGRESS_DROP_RECOVER: Packet loss recovers in queue 2 of GigabitEthernet1/0/0/5.

%Dec 20 11:22:43:902 2024 H3C IFNET/4/IF_EGRESS_DROP_RECOVER: Packet loss recovers in queue 2 of GigabitEthernet1/0/0/7.

%Dec 20 11:22:43:908 2024 H3C IFNET/4/IF_EGRESS_DROP_RECOVER: Packet loss recovers in queue 2 of GigabitEthernet1/0/0/9.

%Dec 20 11:22:43:910 2024 H3C IFNET/4/IF_EGRESS_DROP_RECOVER: Packet loss recovers in queue 2 of GigabitEthernet1/0/0/11.

%Dec 20 11:22:43:911 2024 H3C IFNET/4/IF_EGRESS_DROP_RECOVER: Packet loss recovers in queue 2 of GigabitEthernet1/0/0

2 个回答
粉丝:237人 关注:8人

列队拥塞,跟堆叠关系不大

暂无评论

粉丝:0人 关注:0人

BridgeAggregation17  下面的接的设备应该有设备没配置生成树,产生次优bpdu了,检查一下,然后建议在核心上开根保护

暂无评论

编辑答案

你正在编辑答案

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

分享扩散:

提出建议

    +

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

确定

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

对根叔社区有害的内容

×

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

不规范转载

×

举报说明