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

H3C S5560S频发出现远程桌面断开重连的现象

2022-02-24提问
  • 1关注
  • 1收藏,2998浏览
粉丝:0人 关注:1人

问题描述:


这是日志信息%Feb 24 14:01:07:645 2022 Core_SW SHELL/4/SHELL_CMD_MATCHFAIL: -User=comlan-IPAddr=192.168.13.60; Command dis arp | 0050-56a5-7501 in view shell failed to be matched. %Feb 24 13:58:49:797 2022 Core_SW LLDP/6/LLDP_CREATE_NEIGHBOR: -Slot=2; Nearest bridge agent neighbor created on port GigabitEthernet2/0/13 (IfIndex 76), neighbor's chassis ID is 0050-56a5-eda2, port ID is 0050-56a5-eda2. %Feb 24 13:58:49:794 2022 Core_SW LLDP/6/LLDP_DELETE_NEIGHBOR: -Slot=2; Nearest bridge agent neighbor deleted on port GigabitEthernet2/0/13 (IfIndex 76), neighbor's chassis ID is 0050-56a5-eda2, port ID is 0050-56a5-eda2. %Feb 24 13:57:47:251 2022 Core_SW SHELL/6/SHELL_CMD: -Line=vty0-IPAddr=192.168.13.60-User=comlan; Command is dis logbuffer reverse %Feb 24 13:57:30:365 2022 Core_SW SHELL/6/SHELL_CMD: -Line=vty0-IPAddr=192.168.13.60-User=comlan; Command is dis logbuffer %Feb 24 13:57:25:122 2022 Core_SW SHELL/5/SHELL_LOGIN: comlan logged in from 192.168.13.60. %Feb 24 13:57:23:526 2022 Core_SW SSHS/6/SSHS_CONNECT: SSH user comlan (IP: 192.168.13.60) connected to the server successfully. %Feb 24 13:57:22:481 2022 Core_SW SSHS/6/SSHS_AUTH_SUCCESS: SSH user comlan from 192.168.13.60 port 56646 passed password authentication. %Feb 24 13:08:57:409 2022 Core_SW DRVPLAT/4/SOFTCAR DROP: PktType=ARP, SrcMAC=ec8c-9aa2-de59, Dropped from interface=GigabitEthernet1/0/7 at Stage=1, StageCnt=433, TotalCnt=7336, MaxRateInterface=GigabitEthernet1/0/22. %Feb 24 11:45:21:467 2022 Core_SW SSHS/6/SSHS_DISCONNECT: SSH user comlan (IP: 192.168.13.60) disconnected from the server. %Feb 24 11:45:21:467 2022 Core_SW SSHS/6/SSHS_LOG: User comlan logged out from 192.168.13.60 port 53606. %Feb 24 11:45:21:321 2022 Core_SW SHELL/5/SHELL_LOGOUT: comlan logged out from 192.168.13.60. %Feb 24 11:28:25:731 2022 Core_SW SHELL/6/SHELL_CMD: -Line=vty0-IPAddr=192.168.13.60-User=comlan; Command is dis ip rou %Feb 24 11:28:23:104 2022 Core_SW SHELL/4/SHELL_CMD_MATCHFAIL: -User=comlan-IPAddr=192.168.13.60; Command dis ip r ou in view shell failed to be matched. %Feb 24 11:28:19:416 2022 Core_SW SHELL/6/SHELL_CMD: -Line=vty0-IPAddr=192.168.13.60-User=comlan; Command is dis ip int br %Feb 24 11:23:52:984 2022 Core_SW SHELL/6/SHELL_CMD: -Line=vty0-IPAddr=192.168.13.60-User=comlan; Command is dis ip int br %Feb 24 11:21:57:982 2022 Core_SW SHELL/6/SHELL_CMD: -Line=vty0-IPAddr=192.168.13.60-User=comlan; Command is dis arp 192.168.100.254 %Feb 24 11:15:13:919 2022 Core_SW SHELL/6/SHELL_CMD: -Line=vty0-IPAddr=192.168.13.60-User=comlan; Command is dis cu | in 192.168.12.54 %Feb 24 11:14:39:079 2022 Core_SW SHELL/6/SHELL_CMD: -Line=vty0-IPAddr=192.168.13.60-User=comlan; Command is dis ip ro %Feb 24 11:14:37:728 2022 Core_SW SHELL/4/SHELL_CMD_MATCHFAIL: -User=comlan-IPAddr=192.168.13.60; Command dis ip roou in view shell failed to be matched. %Feb 24 11:14:33:239 2022 Core_SW SHELL/5/SHELL_LOGIN: comlan logged in from 192.168.13.60. %Feb 24 11:14:31:454 2022 Core_SW SSHS/6/SSHS_CONNECT: SSH user comlan (IP: 192.168.13.60) connected to the server successfully. %Feb 24 11:14:30:384 2022 Core_SW SSHS/6/SSHS_AUTH_SUCCESS: SSH user comlan from 192.168.13.60 port 53606 passed password authentication. %Feb 24 11:13:01:603 2022 Core_SW SSHS/6/SSHS_DISCONNECT: SSH user comlan (IP: 192.168.13.60) disconnected from the server. %Feb 24 11:13:01:603 2022 Core_SW SSHS/6/SSHS_LOG: User comlan logged out from 192.168.13.60 port 52774. %Feb 24 11:13:01:529 2022 Core_SW SHELL/5/SHELL_LOGOUT: comlan logged out from 192.168.13.60. %Feb 24 11:02:01:143 2022 Core_SW SHELL/6/SHELL_CMD: -Line=vty0-IPAddr=192.168.13.60-User=comlan; Command is dis cu %Feb 24 11:01:58:127 2022 Core_SW SHELL/4/SHELL_CMD_MATCHFAIL: -User=comlan-IPAddr=192.168.13.60; Command dis uc in view shell failed to be matched. %Feb 24 11:01:56:538 2022 Core_SW SHELL/5/SHELL_LOGIN: comlan logged in from 192.168.13.60. %Feb 24 11:01:55:009 2022 Core_SW SSHS/6/SSHS_CONNECT: SSH user comlan (IP: 192.168.13.60) connected to the server successfully. %Feb 24 11:01:53:957 2022 Core_SW SSHS/6/SSHS_AUTH_SUCCESS: SSH user comlan from 192.168.13.60 port 52774 passed password authentication. %Feb 24 09:32:41:446 2022 Core_SW SSHS/6/SSHS_DISCONNECT: SSH user comlan (IP: 192.168.13.60) disconnected from the server. %Feb 24 09:32:41:446 2022 Core_SW SSHS/6/SSHS_LOG: User comlan logged out from 192.168.13.60 port 59179. %Feb 24 09:32:41:218 2022 Core_SW SHELL/5/SHELL_LOGOUT: comlan logged out from 192.168.13.60. %Feb 24 09:29:09:238 2022 Core_SW LLDP/6/LLDP_CREATE_NEIGHBOR: -Slot=2; Nearest bridge agent neighbor created on port GigabitEthernet2/0/13 (IfIndex 76), neighbor's chassis ID is 0050-56a5-7501, port ID is 0050-56a5-7501. %Feb 24 09:29:09:234 2022 Core_SW LLDP/6/LLDP_DELETE_NEIGHBOR: -Slot=2; Nearest bridge agent neighbor deleted on port GigabitEthernet2/0/13 (IfIndex 76), neighbor's chassis ID is 0050-56a5-7501, port ID is 0050-56a5-7501. %Feb 24 09:22:36:143 2022 Core_SW SHELL/6/SHELL_CMD: -Line=vty0-IPAddr=192.168.13.60-User=comlan; Command is dis logbuffer %Feb 24 09:20:31:277 2022 Core_SW DRVPLAT/4/SOFTCAR DROP: PktType=ARP, SrcMAC=ec8c-9aa2-de59, Dropped from interface=GigabitEthernet1/0/7 at Stage=1, StageCnt=139, TotalCnt=6903, MaxRateInterface=GigabitEthernet1/0/22. %Feb 24 09:13:27:141 2022 Core_SW SHELL/6/SHELL_CMD: -Line=vty0-IPAddr=192.168.13.60-User=comlan; Command is dis cu %Feb 24 09:13:16:157 2022 Core_SW SHELL/5/SHELL_LOGIN: comlan logged in from 192.168.13.60. %Feb 24 09:13:14:814 2022 Core_SW SSHS/6/SSHS_CONNECT: SSH user comlan (IP: 192.168.13.60) connected to the server successfully. %Feb 24 09:13:13:573 2022 Core_SW SSHS/6/SSHS_AUTH_SUCCESS: SSH user comlan from 192.168.13.60 port 59179 passed password authentication. %Feb 24 09:12:11:161 2022 Core_SW LLDP/6/LLDP_CREATE_NEIGHBOR: -Slot=2; Nearest bridge agent neighbor created on port GigabitEthernet2/0/13 (IfIndex 76), neighbor's chassis ID is 0050-56a5-7501, port ID is 0050-56a5-7501. %Feb 23 23:34:08:602 2022 Core_SW LLDP/6/LLDP_CREATE_NEIGHBOR: -Slot=2; Nearest bridge agent neighbor created on port GigabitEthernet2/0/13 (IfIndex 76), neighbor's chassis ID is 0050-56a5-eda2, port ID is 0050-56a5-eda2. %Feb 23 23:34:08:592 2022 Core_SW LLDP/6/LLDP_DELETE_NEIGHBOR: -Slot=2; Nearest bridge agent neighbor deleted on port GigabitEthernet2/0/13 (IfIndex 76), neighbor's chassis ID is 0050-56a5-eda2, port ID is 0050-56a5-eda2. %Feb 23 23:16:32:385 2022 Core_SW LLDP/6/LLDP_CREATE_NEIGHBOR: -Slot=2; Nearest bridge agent neighbor created on port GigabitEthernet2/0/13 (IfIndex 76), neighbor's chassis ID is 0050-56a5-eda2, port ID is 0050-56a5-eda2.

组网及组网描述:

ac旁挂核心,核心直连服务器,客户端通过无线访问服务器,核心做dhcp server,ap直连核心

组网大概:

 ac ---- 核心-----服务器


最佳答案

粉丝:10人 关注:0人

你这个日志格式乱完了,大概看了一下,有软件丢包

 %Feb 24 13:08:57:409 2022 Core_SW DRVPLAT/4/SOFTCAR DROP: PktType=ARP, SrcMAC=ec8c-9aa2-de59, Dropped from interface=GigabitEthernet1/0/7 at Stage=1, StageCnt=433, TotalCnt=7336, MaxRateInterface=GigabitEthernet1/0/22.   

类型是ARP,找一下内网是不是存在环路或者存在ARP攻击

应该没有环路,看设备cpu和内存都是正常范围的,这个日志每天都有rcMAC=ec8c-9aa2-de59, Dropped from interface=GigabitEthernet1/0/7 at Stage=1, StageCnt=433, TotalCnt=7336, MaxRateInterface=GigabitEthernet1/0/22.

迷途羔羊 发表时间:2022-02-24 更多>>

应该没有环路,看设备cpu和内存都是正常范围的,这个日志每天都有rcMAC=ec8c-9aa2-de59, Dropped from interface=GigabitEthernet1/0/7 at Stage=1, StageCnt=433, TotalCnt=7336, MaxRateInterface=GigabitEthernet1/0/22.

迷途羔羊 发表时间:2022-02-24
2 个回答
粉丝:3人 关注:0人

可以长ping测试下是不是网络正常的,有没有丢包的问题

长ping是正常的,没有丢包的现象。

迷途羔羊 发表时间:2022-02-24 更多>>

长ping是正常的,没有丢包的现象。

迷途羔羊 发表时间:2022-02-24
迷途羔羊 知了小白
粉丝:0人 关注:1人

频繁出现断开重连得现象,断开时客户端ping服务器是通的,无丢包现象

编辑答案

你正在编辑答案

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

分享扩散:

提出建议

    +

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

确定

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

对根叔社区有害的内容

×

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

不规范转载

×

举报说明