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

叠配置了mad,之后CPU之间达到90%,卡死

2022-03-22提问
  • 1关注
  • 1收藏,977浏览
粉丝:0人 关注:1人

问题描述:

<H3C>dis logbuffer reverse Log buffer: Enabled Max buffer size: 1024 Actual buffer size: 512 Dropped messages: 0 Overwritten messages: 0 Current messages: 169 %Mar 22 11:01:09:761 2022 H3C SHELL/6/SHELL_CMD: -Line=con0-IPAddr=**-User=**; Command is dis logbuffer %Mar 22 11:01:00:480 2022 H3C SHELL/6/SHELL_CMD: -Line=con0-IPAddr=**-User=**; Command is dis cpu-usage %Mar 22 11:00:57:122 2022 H3C SHELL/5/SHELL_LOGIN: Console logged in from con0. %Mar 22 11:00:48:605 2022 H3C IFNET/5/LINK_UPDOWN: Line protocol state on the interface Vlan-interface10 changed to down. %Mar 22 11:00:48:605 2022 H3C IFNET/3/PHY_UPDOWN: Physical state on the interface Vlan-interface10 changed to down. %Mar 22 11:00:46:557 2022 H3C DEV/3/BOARD_REMOVED: Board was removed from slot 2, type is H3C S6850. %Mar 22 11:00:46:554 2022 H3C HA/5/HA_STANDBY_TO_MASTER: Standby board in slot 1 changed to master. %Mar 22 11:00:46:553 2022 H3C LIPC/5/PORT_CHANGE: [!karp/1/897877] STCP: Node where the listening port number 1637 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:553 2022 H3C LIPC/5/PORT_CHANGE: [!karp/1/897877] STCP: Node where the listening port number 1638 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:553 2022 H3C LIPC/5/PORT_CHANGE: [!kspbm/1/897877] STCP: Node where the listening port number 1744 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:553 2022 H3C LIPC/5/PORT_CHANGE: [!kspbm/1/897877] STCP: Node where the listening port number 1745 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:552 2022 H3C LIPC/5/PORT_CHANGE: [!kfib/1/897876] STCP: Node where the listening port number 4255 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:552 2022 H3C LIPC/5/PORT_CHANGE: [!kfib/1/897876] STCP: Node where the listening port number 1646 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:552 2022 H3C LIPC/5/PORT_CHANGE: [!kfib/1/897876] STCP: Node where the listening port number 1655 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:552 2022 H3C LIPC/5/PORT_CHANGE: [!kTMFIB//897876] STCP: Node where the listening port number 1677 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:552 2022 H3C LIPC/5/PORT_CHANGE: [!kTMFIB//897876] STCP: Node where the listening port number 1678 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:552 2022 H3C LIPC/5/PORT_CHANGE: [!kmac/1/897876] STCP: Node where the listening port number 1782 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:552 2022 H3C LIPC/5/PORT_CHANGE: [!kmac/1/897876] STCP: Node where the listening port number 1783 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:552 2022 H3C LIPC/5/PORT_CHANGE: [!kmac/1/897876] STCP: Node where the listening port number 1784 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:552 2022 H3C LIPC/5/PORT_CHANGE: [!kmac/1/897876] STCP: Node where the listening port number 1715 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:552 2022 H3C LIPC/5/PORT_CHANGE: [!kmac/1/897876] STCP: Node where the listening port number 1663 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:552 2022 H3C LIPC/5/PORT_CHANGE: [!kmac/1/897876] STCP: Node where the listening port number 1844 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:552 2022 H3C LIPC/5/PORT_CHANGE: [!kmac/1/897876] STCP: Node where the listening port number 1664 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:552 2022 H3C LIPC/5/PORT_CHANGE: [!kwadj/1/897876] STCP: Node where the listening port number 1640 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:552 2022 H3C LIPC/5/PORT_CHANGE: [!kwadj/1/897876] STCP: Node where the listening port number 1641 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:552 2022 H3C LIPC/5/PORT_CHANGE: [!sock/1/897876] STCP: Node where the listening port number 1644 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:552 2022 H3C LIPC/5/PORT_CHANGE: [!sock/1/897876] STCP: Node where the listening port number 1643 (MDC:1 VRF:0) resides changed from LIP 16 to LIP 8. %Mar 22 11:00:46:552 2022 H3C STM/3/STM_LINK_DOWN: IRF port 1 went down. %Mar 22 11:00:35:731 2022 H3C CFGMAN/5/CFGMAN_EXIT_FROM_CONFIGURE: -Slot=2; -Line=con0-IPAddr=**-User=**; Exit from the system view or a feature view to the user view. %Mar 22 11:00:35:731 2022 H3C SHELL/6/SHELL_CMD: -Slot=2; -Line=con0-IPAddr=**-User=**; Command is qui %Mar 22 11:00:27:243 2022 H3C SHELL/6/SHELL_CMD: -Slot=2; -Line=con0-IPAddr=**-User=**; Command is dis cpu-usage %Mar 22 11:00:18:138 2022 H3C SHELL/6/SHELL_CMD: -Slot=2; -Line=con0-IPAddr=**-User=**; Command is dis cpu-usage %Mar 22 11:00:15:044 2022 H3C SHELL/6/SHELL_CMD: -Slot=2; -Line=con0-IPAddr=**-User=**; Command is qui %Mar 22 11:00:06:775 2022 H3C DIAG/4/CPU_MINOR_THRESHOLD: -Slot=2; CPU usage is in minor alarm state. CPU usage: 89% in last 1 minute. CPU usage thresholds: Minor: 80% Severe: 99% Process info: JID PID PRI State FDs HH:MM:SS CPU Name <H3C>%Mar 22 11:02:17:614 2022 H3C LLDP/5/LLDP_NEIGHBOR_AGE_OUT: Nearest bridge agent neighbor aged out on port Ten-GigabitEthernet1/0/50 (IfIndex 51), neighbor's chassis ID is 7e38-79f8-0100, port ID is Ten-GigabitEthernet2/0/51. %Mar 22 11:02:27:614 2022 H3C LLDP/5/LLDP_NEIGHBOR_AGE_OUT: Nearest bridge agent neighbor aged out on port GigabitEthernet1/0/1 (IfIndex 2), neighbor's chassis ID is 7e38-79f8-0100, port ID is GigabitEthernet2/0/1.

组网及组网描述:

配置mad之后,就卡死了。XG做堆叠线,GE做mad,两边端口stp已经关闭。

最佳答案

粉丝:17人 关注:0人

mad起来了吗?应该是没起来环了

[H3C]dis mad verbose Multi-active recovery state: No Excluded ports (user-configured): Excluded ports (system-configured): IRF physical interfaces: Ten-GigabitEthernet1/0/50 Ten-GigabitEthernet2/0/51 BFD MAD interfaces: Vlan-interface10 MAD ARP disabled. MAD ND disabled. MAD LACP disabled. MAD BFD enabled interface: Vlan-interface10 MAD status : Faulty Member ID MAD IP address Neighbor MAD status 1 192.168.1.1/24 2 Faulty 2 192.168.1.2/24 1 Faulty [H3C] [H3C]

迷途羔羊 发表时间:2022-03-22

mad 状态不是no吗?没起来啊

Theone_唯一 发表时间:2022-03-22
1 个回答
粉丝:30人 关注:0人

模拟器有这个问题的,建议用真机操作

编辑答案

你正在编辑答案

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

分享扩散:

提出建议

    +

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

确定

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

对根叔社区有害的内容

×

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

不规范转载

×

举报说明