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

H3C S3110-26TP-SI异常掉线

2023-02-03提问
  • 0关注
  • 0收藏,677浏览
粉丝:0人 关注:0人

问题描述:

H3C S3110-26TP-SI异常掉线,内网其他网段PING交换机,现象是一天不定时随机掉线2-3次,时间20-50秒,交换机没做过多配置,更换新交换机只做vlan和默认路由也出现异常,相同配置在H3C其他交换机没异常出现,光纤换了,跳线也换了,日志没有报错

# version 5.20.99, Release 1108 # sysname H3C # clock timezone Beijing add 08:00:00 # domain default enable system # ipv6 # telnet server enable # loopback-detection enable loopback-detection multi-port-mode enable loopback-detection interval-time 5 # password-recovery enable # vlan 1 # vlan 3 # vlan 7 # vlan 15 # vlan 17 to 21 # vlan 25 # vlan 50 # vlan 60 # domain system access-limit disable state active idle-cut disable self-service-url disable # user-group system group-attribute allow-guest # local-user admin password cipher $c$3$ZPD3aPWgUd3aM15ha7A/QNUwRVfRzZCC96Zw5Q== authorization-attribute level 3 service-type telnet service-type web # interface NULL0 # interface Vlan-interface1 # interface Vlan-interface18 ip address 192.168.18.8 255.255.255.0 # interface Ethernet1/0/1 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/2 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/3 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/4 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/5 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/6 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/7 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/8 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/9 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/10 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/11 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/12 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/13 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/14 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/15 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/16 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/17 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/18 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/19 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/20 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/21 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/22 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/23 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface Ethernet1/0/24 port access vlan 18 loopback-detection enable loopback-detection action shutdown # interface GigabitEthernet1/0/25 port link-type trunk port trunk permit vlan all combo enable copper # interface GigabitEthernet1/0/26 port link-type trunk port trunk permit vlan all # ip route-static 0.0.0.0 0.0.0.0 192.168.18.1 # undo info-center logfile enable # snmp-agent snmp-agent local-engineid 3830303036334132363531334238343546344 snmp-agent community read public snmp-agent sys-info version v2c v3 # load xml-configuration

组网及组网描述:


4 个回答
粉丝:10人 关注:7人

查看一下环路 dis stp brief

zhiliao_66mVhJ 知了小白
粉丝:0人 关注:0人

Password:
<H3C>dis stp bri
Protocol Status :disabled
Protocol Std. :IEEE 802.1s
Version :0
Bridge-Prio. :32768
MAC address :b845-f4bc-2088
Max age(s) :20
Forward delay(s) :15
Hello time(s) :2
Max hops :20
TC Snooping :disabled


%Feb 2 14:10:46:246 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/22 link status is UP. %Feb 2 16:18:38:570 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/22 link status is DOWN. %Feb 2 16:21:59:588 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/22 link status is UP. %Feb 2 16:22:02:518 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/22 link status is DOWN. %Feb 2 16:22:10:896 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/22 link status is UP. %Feb 2 22:17:10:798 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/23 link status is DOWN. %Feb 2 22:17:24:525 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/23 link status is UP. %Feb 3 06:53:12:028 2023 H3C SHELL/5/SHELL_LOGIN: VTY logged in from 192.168.7.145. %Feb 3 06:53:14:750 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis cu %Feb 3 06:53:18:690 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis log %Feb 3 06:55:16:418 2023 H3C SHELL/5/SHELL_LOGOUT: VTY logged out from 192.168.7.145. %Feb 3 10:00:18:351 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/23 link status is DOWN. %Feb 3 10:05:38:700 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/23 link status is UP. %Feb 3 10:06:44:128 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/23 link status is DOWN. %Feb 3 10:08:10:966 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/23 link status is UP. %Feb 3 10:39:52:554 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/23 link status is DOWN. %Feb 3 10:40:21:069 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/23 link status is UP. %Feb 3 11:23:17:536 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/23 link status is DOWN. %Feb 3 11:23:24:791 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/23 link status is UP. %Feb 3 11:45:30:090 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/13 link status is DOWN. %Feb 3 11:47:37:877 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/23 link status is DOWN. %Feb 3 11:47:46:595 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/16 link status is DOWN. %Feb 3 11:54:15:195 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/23 link status is UP. %Feb 3 11:54:15:665 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/16 link status is UP. %Feb 3 12:45:03:911 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/13 link status is UP. %Feb 3 12:59:12:255 2023 H3C SHELL/5/SHELL_LOGIN: VTY logged in from 192.168.7.145. %Feb 3 12:59:14:772 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis log %Feb 3 12:59:22:668 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis clo %Feb 3 13:00:17:661 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis int Ethernet 1/0/23 %Feb 3 13:01:12:378 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis clo %Feb 3 13:01:22:651 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis int Ethernet 1/0/16 %Feb 3 13:02:22:921 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis int Ethernet 1/0/13 %Feb 3 13:03:03:099 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis int Ethernet 1/0/13 %Feb 3 13:03:28:120 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis int Ethernet 1/0/16 %Feb 3 13:04:18:182 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis arp %Feb 3 13:06:48:411 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis int bri %Feb 3 13:07:06:121 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis cu %Feb 3 13:09:05:337 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis version %Feb 3 13:19:05:699 2023 H3C CFGMAN/5/CFGMAN_EXIT: Exit from configuration mode. %Feb 3 13:19:05:699 2023 H3C SHELL/5/SHELL_LOGOUT: VTY logged out from 192.168.7.145. %Feb 3 13:19:14:504 2023 H3C SC/6/SC_AAA_LAUNCH: -AAAType=AUTHEN-AAAScheme= local-Service=login-UserName=admin@system; AAA launched. %Feb 3 13:19:14:505 2023 H3C SC/6/SC_AAA_SUCCESS: -AAAType=AUTHEN-AAAScheme= local-Service=login-UserName=admin@system; AAA is successful. %Feb 3 13:19:14:505 2023 H3C SC/6/SC_AAA_LAUNCH: -AAAType=AUTHOR-AAAScheme= local-Service=login-UserName=admin@system; AAA launched. %Feb 3 13:19:14:505 2023 H3C SC/6/SC_AAA_SUCCESS: -AAAType=AUTHOR-AAAScheme= local-Service=login-UserName=admin@system; AAA is successful. %Feb 3 13:19:14:506 2023 H3C SC/6/SC_AAA_LAUNCH: -AAAType=ACCOUNT-AAAScheme= local-Service=login-UserName=admin@system; AAA launched. %Feb 3 13:19:14:507 2023 H3C SC/6/SC_AAA_SUCCESS: -AAAType=ACCOUNT-AAAScheme= local-Service=login-UserName=admin@system; AAA is successful. %Feb 3 13:19:14:516 2023 H3C WEB/4/WEBOPT_LOGIN_SUC: admin logged in from 192.168.7.145 %Feb 3 13:30:19:951 2023 H3C SHELL/5/SHELL_LOGIN: VTY logged in from 192.168.7.145. %Feb 3 13:30:23:417 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis cu %Feb 3 13:31:50:698 2023 H3C WEB/4/WEBOPT_LOGOUT: admin logged out from 192.168.7.145 %Feb 3 13:36:53:709 2023 H3C LPDETECT/5/LPDETECT_SHUTDOWN: Loopback exists on Ethernet1/0/7 and this interface is shut down. %Feb 3 13:36:53:731 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/7 link status is DOWN. %Feb 3 13:37:25:689 2023 H3C IFNET/3/LINK_UPDOWN: Ethernet1/0/7 link status is UP. %Feb 3 13:38:11:588 2023 H3C SHELL/5/SHELL_LOGOUT: VTY logged out from 192.168.7.145. %Feb 3 13:38:38:613 2023 H3C SHELL/5/SHELL_LOGINFAIL: TELNET user failed to log in from 192.168.7.145 on VTY0. %Feb 3 13:38:41:318 2023 H3C SHELL/5/SHELL_LOGIN: VTY logged in from 192.168.7.145. %Feb 3 13:38:47:099 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis stp bri %Feb 3 13:41:36:488 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis log %Feb 3 13:42:09:896 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis log %Feb 3 13:42:23:092 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis int Ethernet 1/0/7 %Feb 3 13:44:49:133 2023 H3C SHELL/6/SHELL_CMD: -Task=vt0-IPAddr=192.168.7.145-User=**; Command is dis log <H3C> 没什么异常报错,相同的配置在H3C S3110-10TP-SI上没有异常掉线出现



肯定都是新的,包装上都是近期生产的 Slot 1: DEVICE_NAME : S3110-26TP-SI DEVICE_SERIAL_NUMBER : 219801A0L49219Q00049 MAC_ADDRESS : B845-F4BC-2088 MANUFACTURING_DATE : 2021-09 VENDOR_NAME : H3C

zhiliao_66mVhJ 发表时间:2023-02-03 更多>>

换了新交换机,但还是旧配置。也会出现同样的问题是吗

奔跑的小马 发表时间:2023-02-03

是的

zhiliao_66mVhJ 发表时间:2023-02-03

新的交换机是v7的吗 dis stp brief,可能v5的查看dis stp brief命令不太一样

奔跑的小马 发表时间:2023-02-03

交换机几年了呀

奔跑的小马 发表时间:2023-02-03

都是2022年的新机器

zhiliao_66mVhJ 发表时间:2023-02-03

version 5.20.99, v5的设备是那个型号的呀

奔跑的小马 发表时间:2023-02-03

2台的版本一样 H3C Switch S3110-26TP-SI 软件版本 5.20.99 Release 1108 Comware Software, Version 5.20.99, Release 1108 Copyright (c) 2004-2017 New H3C Technologies Co., Ltd. All rights reserved. H3C S3110-10TP-SI uptime is 17 weeks, 6 days, 6 hours, 9 minutes

zhiliao_66mVhJ 发表时间:2023-02-03

2台的版本一样,区别就是接口数量

zhiliao_66mVhJ 发表时间:2023-02-03

我看你说相同的配置在H3C S3110-10TP-SI上没有异常掉线出现,在36TP上异常掉线是吗

奔跑的小马 发表时间:2023-02-03

是的

zhiliao_66mVhJ 发表时间:2023-02-03

感觉是36TP的有点老了。dis dev man查看多少年的

奔跑的小马 发表时间:2023-02-03

肯定都是新的,包装上都是近期生产的 Slot 1: DEVICE_NAME : S3110-26TP-SI DEVICE_SERIAL_NUMBER : 219801A0L49219Q00049 MAC_ADDRESS : B845-F4BC-2088 MANUFACTURING_DATE : 2021-09 VENDOR_NAME : H3C

zhiliao_66mVhJ 发表时间:2023-02-03
粉丝:167人 关注:1人

日志看下,display logbuffer


您好,请知:

异常掉线,以下是排查要点,请参考:

1、检查设备的接线是否有问题。

2、检查是否有可能存在环路。

3、检查设备的CPU、内存、端口利用率是否高。

4、dis logbuffer re检查设备是否有异常的日志。


编辑答案

你正在编辑答案

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

分享扩散:

提出建议

    +

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

确定

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

对根叔社区有害的内容

×

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

不规范转载

×

举报说明