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

H3C 信息网巡检系统 SSH登录测试结果提示connection failed,108

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

问题描述:

在巡检管家version 1.0.1 添加设备后,通过SSH登录测试提示connection failed,108.

但能够确定SSH配置是没有问题的,因为通过终端去登录是正常的,但通过巡检管家去登录就报这个,目前我有5-6台H3C设备都出现这个问题。

开启调试后SSH登录信息如下:

通过终端SSH登录正常:

*Feb 11 11:43:45:046 2022 H3C3640 SSHS/7/EVENT: Kex strings(5): umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96

*Feb 11 11:43:45:046 2022 H3C3640 SSHS/7/EVENT: Kex strings(6): none,zlib@openssh.com,zlib

*Feb 11 11:43:45:046 2022 H3C3640 SSHS/7/EVENT: Kex strings(7): none,zlib@openssh.com,zlib

*Feb 11 11:43:45:046 2022 H3C3640 SSHS/7/EVENT: Kex strings(8):

*Feb 11 11:43:45:046 2022 H3C3640 SSHS/7/EVENT: Kex strings(9):

*Feb 11 11:43:45:047 2022 H3C3640 SSHS/7/EVENT: Kex: client->server, Encrypt: aes128-cbc, HMAC: hmac-sha1, Compress: none

*Feb 11 11:43:45:047 2022 H3C3640 SSHS/7/EVENT: Kex: server->client, Encrypt: aes128-cbc, HMAC: hmac-sha1, Compress: none

*Feb 11 11:43:45:050 2022 H3C3640 SSHS/7/EVENT: Expecting packet type 30.

*Feb 11 11:43:45:058 2022 H3C3640 SSHS/7/EVENT: Set new keys: mode=1

*Feb 11 11:43:45:059 2022 H3C3640 SSHS/7/EVENT: Expecting packet type 21.

*Feb 11 11:43:45:059 2022 H3C3640 SSHS/7/EVENT: Start new child 3905476.

*Feb 11 11:43:45:061 2022 H3C3640 SSHS/7/EVENT: Set new keys: mode=0

*Feb 11 11:43:45:061 2022 H3C3640 SSHS/7/EVENT: KEX done.

*Feb 11 11:43:45:062 2022 H3C3640 SSHS/7/EVENT: Received SSH2_MSG_SERVICE_REQUEST.

*Feb 11 11:43:45:063 2022 H3C3640 SSHS/7/EVENT: Received SSH2_MSG_USERAUTH_REQUEST.

*Feb 11 11:43:45:063 2022 H3C3640 SSHS/7/EVENT: Username: XXXX, service: ssh-connection, method: none

*Feb 11 11:43:45:064 2022 H3C3640 SSHS/7/EVENT: PAM: initializing for "XXXX", service:login, domain:

*Feb 11 11:43:45:145 2022 H3C3640 SSHS/7/EVENT: Try authentication method none.

*Feb 11 11:43:45:145 2022 H3C3640 SSHS/7/EVENT: Failed none for XXXX from 0.0.0.0 port 59877.

 

*Feb 11 11:43:45:145 2022 H3C3640 SSHS/7/EVENT: Get authentication methods: password

*Feb 11 11:43:45:647 2022 H3C3640 SSHS/7/EVENT: Received SSH2_MSG_USERAUTH_REQUEST.

*Feb 11 11:43:45:648 2022 H3C3640 SSHS/7/EVENT: Username: XXXX, service: ssh-connection, method: password

*Feb 11 11:43:45:648 2022 H3C3640 SSHS/7/EVENT: Try authentication method password.

*Feb 11 11:43:45:648 2022 H3C3640 SSHS/7/EVENT: Password authentication and authorization.

*Feb 11 11:43:45:654 2022 H3C3640 SSHS/7/EVENT: PAM: Get work directory cfa0:.

*Feb 11 11:43:45:654 2022 H3C3640 SSHS/7/EVENT: PAM: Get role list level-15,network-operator.

*Feb 11 11:43:45:654 2022 H3C3640 SSHS/7/EVENT: PAM: password authentication accepted for XXXX.

*Feb 11 11:43:45:654 2022 H3C3640 SSHS/7/EVENT: PAM: accounting.

*Feb 11 11:43:45:657 2022 H3C3640 SSHS/7/EVENT: PAM: account management : 0 (success)

%Feb 11 11:43:45:657 2022 H3C3640 SSHS/6/SSHS_LOG: Accepted password for XXXX from 0.0.0.0 port 59877.

 

*Feb 11 11:43:45:657 2022 H3C3640 SSHS/7/EVENT: Entering interactive session for SSH2.

*Feb 11 11:43:45:658 2022 H3C3640 SSHS/7/EVENT: Initiate server message dispatch, compatibility:1/0

*Feb 11 11:43:45:658 2022 H3C3640 SSHS/7/EVENT: Received SSH2_MSG_CHANNEL_OPEN: ctype session, rchan 0, win 1048576, max 16384

*Feb 11 11:43:45:659 2022 H3C3640 SSHS/7/EVENT: Received session request.

*Feb 11 11:43:45:659 2022 H3C3640 SSHS/7/EVENT: Channel 0: new [server-session]

*Feb 11 11:43:45:659 2022 H3C3640 SSHS/7/EVENT: Session id 0 unused.

*Feb 11 11:43:45:659 2022 H3C3640 SSHS/7/EVENT: Session opened: session 0, link with channel 0

*Feb 11 11:43:45:660 2022 H3C3640 SSHS/7/EVENT: Received SSH2_MSG_CHANNEL_REQUEST: channel 0, request pty-req, reply 1

*Feb 11 11:43:45:661 2022 H3C3640 SSHS/7/EVENT: Channel request: user XXXX, service type 2 rtype:pty-req

*Feb 11 11:43:45:671 2022 H3C3640 SSHS/7/EVENT: Open pty: pseudo-terminal-master(35), pseudo-terminal-sub(34)

*Feb 11 11:43:45:672 2022 H3C3640 SSHS/7/EVENT: Received SSH2_MSG_CHANNEL_REQUEST: channel 0, request env, reply 0

*Feb 11 11:43:45:672 2022 H3C3640 SSHS/7/EVENT: Channel request: user XXXX, service type 2 rtype:env

*Feb 11 11:43:45:672 2022 H3C3640 SSHS/7/EVENT: Received SSH2_MSG_CHANNEL_REQUEST: channel 0, request shell, reply 1

*Feb 11 11:43:45:672 2022 H3C3640 SSHS/7/EVENT: Channel request: user XXXX, service type 2 rtype:shell

*Feb 11 11:43:45:674 2022 H3C3640 SSHS/7/EVENT: PAM: opening session.

*Feb 11 11:43:45:677 2022 H3C3640 SSHS/7/EVENT: Setup environment: user=XXXX, work directory=cfa0:

*Feb 11 11:43:45:678 2022 H3C3640 SSHS/7/EVENT: Get default work dir: cfa0:, return:0

%Feb 11 11:43:45:678 2022 H3C3640 SSHS/6/SSHS_CONNECT: SSH user XXXX (IP: 0.0.0.0) connected to the server successfully.

*Feb 11 11:43:45:686 2022 H3C3640 SSHS/7/EVENT: Channel 0: read_fd 37 is a TTY.

%Feb 11 11:43:45:846 2022 H3C3640 SHELL/5/SHELL_LOGIN: XXXX logged in from 0.0.0.0.




但是通过巡检系统去SSH 登录就不行

 

 

*Feb 11 11:44:53:465 2022 H3C3640 SSHS/7/EVENT: Connection from 1.1.1.1 port 13066

*Feb 11 11:44:53:467 2022 H3C3640 SSHS/7/EVENT: Client protocol version 2.0, client software version H3C-GatherTool

*Feb 11 11:44:53:467 2022 H3C3640 SSHS/7/EVENT: Enabling compatibility mode for protocol 2.0

*Feb 11 11:44:53:467 2022 H3C3640 SSHS/7/EVENT: Local version string SSH-2.0-Comware-7.1.059

*Feb 11 11:44:53:468 2022 H3C3640 SSHS/7/EVENT: Hostkey string is : ssh-rsa

*Feb 11 11:44:53:469 2022 H3C3640 SSHS/7/EVENT: Start new child 3905513.

*Feb 11 11:44:53:512 2022 H3C3640 SSHS/7/EVENT: Received SSH2_MSG_KEXINIT.

*Feb 11 11:44:53:512 2022 H3C3640 SSHS/7/EVENT: My proposal kex:

*Feb 11 11:44:53:512 2022 H3C3640 SSHS/7/EVENT: Kex strings(0): diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1

*Feb 11 11:44:53:512 2022 H3C3640 SSHS/7/EVENT: Kex strings(1): ssh-rsa

*Feb 11 11:44:53:512 2022 H3C3640 SSHS/7/EVENT: Kex strings(2): aes128-cbc,aes256-cbc,3des-cbc,des-cbc

*Feb 11 11:44:53:512 2022 H3C3640 SSHS/7/EVENT: Kex strings(3): aes128-cbc,aes256-cbc,3des-cbc,des-cbc

*Feb 11 11:44:53:512 2022 H3C3640 SSHS/7/EVENT: Kex strings(4): hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96

*Feb 11 11:44:53:512 2022 H3C3640 SSHS/7/EVENT: Kex strings(5): hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96

*Feb 11 11:44:53:512 2022 H3C3640 SSHS/7/EVENT: Kex strings(6): none,zlib,zlib@openssh.com

*Feb 11 11:44:53:512 2022 H3C3640 SSHS/7/EVENT: Kex strings(7): none,zlib,zlib@openssh.com

*Feb 11 11:44:53:512 2022 H3C3640 SSHS/7/EVENT: Kex strings(8):

*Feb 11 11:44:53:512 2022 H3C3640 SSHS/7/EVENT: Kex strings(9):

*Feb 11 11:44:53:512 2022 H3C3640 SSHS/7/EVENT: Peer proposal kex:

*Feb 11 11:44:53:513 2022 H3C3640 SSHS/7/EVENT: Kex strings(0): diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1

*Feb 11 11:44:53:513 2022 H3C3640 SSHS/7/EVENT: Kex strings(1): ssh-rsa

*Feb 11 11:44:53:513 2022 H3C3640 SSHS/7/EVENT: Kex strings(2): aes128-cbc,3des-cbc,des-cbc

*Feb 11 11:44:53:513 2022 H3C3640 SSHS/7/EVENT: Kex strings(3): aes128-cbc,3des-cbc,des-cbc

*Feb 11 11:44:53:513 2022 H3C3640 SSHS/7/EVENT: Kex strings(4): hmac-sha1-96,hmac-sha1,hmac-md5,hmac-md5-96

*Feb 11 11:44:53:513 2022 H3C3640 SSHS/7/EVENT: Kex strings(5): hmac-sha1-96,hmac-sha1,hmac-md5,hmac-md5-96

*Feb 11 11:44:53:513 2022 H3C3640 SSHS/7/EVENT: Kex strings(6): none

*Feb 11 11:44:53:513 2022 H3C3640 SSHS/7/EVENT: Kex strings(7): none

*Feb 11 11:44:53:513 2022 H3C3640 SSHS/7/EVENT: Kex strings(8):

*Feb 11 11:44:53:513 2022 H3C3640 SSHS/7/EVENT: Kex strings(9):

*Feb 11 11:44:53:513 2022 H3C3640 SSHS/7/EVENT: Kex: client->server, Encrypt: aes128-cbc, HMAC: hmac-sha1-96, Compress: none

*Feb 11 11:44:53:513 2022 H3C3640 SSHS/7/EVENT: Kex: server->client, Encrypt: aes128-cbc, HMAC: hmac-sha1-96, Compress: none

%Feb 11 11:44:53:562 2022 H3C3640 SSHS/6/SSHS_LOG: Connection closed by 1.1.1.1.



最佳答案

已采纳
粉丝:11人 关注:4人

是不是SSH版本太低了?巡检管家应该支持SSH 2.0以上的版本。

我的巡检管家版本version1.0.1.我查看了下几台交换机的SSH版本都是2.0,我添加了ssh 兼容后就能登录成功了。

zhiliao_hVXKMb 发表时间:2022-02-11
1 个回答
粉丝:3人 关注:0人

格式有问题   手动加上呢

编辑答案

你正在编辑答案

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

分享扩散:

提出建议

    +

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

确定

亲~检测到您登陆的账号未在http://hclhub.h3c.com进行注册

注册后可访问此模块

跳转hclhub

你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作

举报

×

侵犯我的权益 >
对根叔社区有害的内容 >
辱骂、歧视、挑衅等(不友善)

侵犯我的权益

×

泄露了我的隐私 >
侵犯了我企业的权益 >
抄袭了我的内容 >
诽谤我 >
辱骂、歧视、挑衅等(不友善)
骚扰我

泄露了我的隐私

×

您好,当您发现根叔知了上有泄漏您隐私的内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到zhiliao@h3c.com 邮箱,我们会尽快处理。
  • 1. 您认为哪些内容泄露了您的隐私?(请在邮件中列出您举报的内容、链接地址,并给出简短的说明)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)

侵犯了我企业的权益

×

您好,当您发现根叔知了上有关于您企业的造谣与诽谤、商业侵权等内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到 zhiliao@h3c.com 邮箱,我们会在审核后尽快给您答复。
  • 1. 您举报的内容是什么?(请在邮件中列出您举报的内容和链接地址)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)
  • 3. 是哪家企业?(营业执照,单位登记证明等证件)
  • 4. 您与该企业的关系是?(您是企业法人或被授权人,需提供企业委托授权书)
我们认为知名企业应该坦然接受公众讨论,对于答案中不准确的部分,我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

抄袭了我的内容

×

原文链接或出处

诽谤我

×

您好,当您发现根叔知了上有诽谤您的内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到zhiliao@h3c.com 邮箱,我们会尽快处理。
  • 1. 您举报的内容以及侵犯了您什么权益?(请在邮件中列出您举报的内容、链接地址,并给出简短的说明)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)
我们认为知名企业应该坦然接受公众讨论,对于答案中不准确的部分,我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

对根叔社区有害的内容

×

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

不规范转载

×

举报说明