pandrew Posted March 27, 2024 Добрый день, Коллеги! Есть маршрутизатор Huawei AR6140-16G4XG. Прошивка V300R019C10SPC300. Надо бы обновить да сайт хуавея при попытке скачать пишет maintaining. Выполняем ssh pandrew@172.17.1.200 Запрашивает пароль. Вводим пароль. ОТкрывается терминал. Все как ожидалось. Выполняем ssh pandrew@172.17.1.200 'display current-configuration' Запрашивает пароль. Вводим пароль. Зависает. Никакого вывода. Ждал долго. Из-за этого уже неделю не могу дописать скрипты управления оборудованием для карбон биллинга. ssh pandrew@172.17.1.200 'display current-configuration' Authenticated with partial success. pandrew@172.17.1.200's password: Write failed: Broken pipe У вас есть новая почта в /var/spool/mail/root [root@carbon ~]# ssh -vvv pandrew@172.17.1.200 'display current-configuration' OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to 172.17.1.200 [172.17.1.200] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/identity-cert type -1 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_rsa-cert type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: identity file /root/.ssh/id_dsa-cert type -1 debug1: identity file /root/.ssh/id_ecdsa type -1 debug1: identity file /root/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 2.0, remote software version HUAWEI-1.5 debug1: no match: HUAWEI-1.5 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug2: fd 3 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent debug3: Wrote 864 bytes for a total of 885 debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-dss-cert-v00@openssh.com,ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se debug2: kex_parse_kexinit: hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96 debug2: kex_parse_kexinit: hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96 debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1 debug2: kex_parse_kexinit: ecdsa-sha2-nistp256,ssh-rsa debug2: kex_parse_kexinit: aes256-ctr,aes192-ctr,aes128-ctr debug2: kex_parse_kexinit: aes256-ctr,aes192-ctr,aes128-ctr debug2: kex_parse_kexinit: hmac-sha2-256 debug2: kex_parse_kexinit: hmac-sha2-256 debug2: kex_parse_kexinit: none debug2: kex_parse_kexinit: none debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-sha2-256 debug1: kex: server->client aes128-ctr hmac-sha2-256 none debug2: mac_setup: found hmac-sha2-256 debug1: kex: client->server aes128-ctr hmac-sha2-256 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<4096<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug3: Wrote 24 bytes for a total of 909 debug2: dh_gen_key: priv key bits set: 250/512 debug2: bits set: 2078/4096 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: Wrote 528 bytes for a total of 1437 debug3: check_host_in_hostfile: host 172.17.1.200 filename /root/.ssh/known_hosts debug3: check_host_in_hostfile: host 172.17.1.200 filename /root/.ssh/known_hosts debug3: check_host_in_hostfile: match line 1 debug1: Host '172.17.1.200' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts:1 debug2: bits set: 2041/4096 debug1: ssh_rsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: Wrote 16 bytes for a total of 1453 debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug3: Wrote 64 bytes for a total of 1517 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /root/.ssh/identity ((nil)) debug2: key: /root/.ssh/id_rsa ((nil)) debug2: key: /root/.ssh/id_dsa ((nil)) debug2: key: /root/.ssh/id_ecdsa ((nil)) debug3: Wrote 80 bytes for a total of 1597 Authenticated with partial success. debug1: Authentications that can continue: password debug3: start over, passed a different list password debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_lookup password debug3: remaining preferred: ,gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_is_enabled password debug1: Next authentication method: password pandrew@172.17.1.200's password: debug3: packet_send2: adding 64 (len 60 padlen 4 extra_pad 64) debug2: we sent a password packet, wait for reply debug3: Wrote 160 bytes for a total of 1757 debug1: Authentication succeeded (password). debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug1: Entering interactive session. debug3: Wrote 80 bytes for a total of 1837 debug2: callback start debug2: client_session2_setup: id 0 debug1: Sending environment. debug3: Ignored env HOSTNAME debug3: Ignored env TERM debug3: Ignored env SHELL debug3: Ignored env HISTSIZE debug3: Ignored env SSH_CLIENT debug3: Ignored env SSH_TTY debug3: Ignored env USER debug3: Ignored env LS_COLORS debug3: Ignored env MAIL debug3: Ignored env PATH debug3: Ignored env PWD debug1: Sending env LANG = ru_RU.UTF-8 debug2: channel 0: request env confirm 0 debug3: Ignored env HISTCONTROL debug3: Ignored env SHLVL debug3: Ignored env HOME debug3: Ignored env LOGNAME debug3: Ignored env SSH_CONNECTION debug3: Ignored env LESSOPEN debug3: Ignored env HISTTIMEFORMAT debug3: Ignored env G_BROKEN_FILENAMES debug3: Ignored env _ debug1: Sending command: display current-configuration debug2: channel 0: request exec confirm 1 debug2: fd 3 setting TCP_NODELAY debug2: callback done debug2: channel 0: open confirm rwindow 131072 rmax 32768 debug3: Wrote 176 bytes for a total of 2013 Тут нажал Ctrl+C ^Cdebug3: Wrote 80 bytes for a total of 2093 debug1: channel 0: free: client-session, nchannels 1 debug3: channel 0: status: The following connections are open: #0 client-session (t4 r1 i0/0 o0/0 fd 4/5 cc -1) debug3: channel 0: close_fds r 4 w 5 e 6 Killed by signal 2. Коллеги, пожалуйста, подскажите в чем проблема. Вставить ник Quote Ответить с цитированием Share this post Link to post Share on other sites More sharing options...
alexgreat Posted March 27, 2024 <Huawei> system-view [Huawei] user-interface console 0 [Huawei-ui-console0] screen-length 0 Не? Там хуа ждёт нажатия пробела скорей всего. Вставить ник Quote Ответить с цитированием Share this post Link to post Share on other sites More sharing options...
azhur Posted March 27, 2024 Раз подключение по SSH, то наверно всё-таки vty а не con: user-interface vty 0 4 screen-length 0 Вставить ник Quote Ответить с цитированием Share this post Link to post Share on other sites More sharing options...
pandrew Posted March 27, 2024 Попробовал. Все равно huawei не отвечает. Коллеги, еще какие мысли? Вставить ник Quote Ответить с цитированием Share this post Link to post Share on other sites More sharing options...
alexgreat Posted March 27, 2024 @pandrew при обычном коннекте по SSH di cu стал выдавать весь конфиг разом? Вставить ник Quote Ответить с цитированием Share this post Link to post Share on other sites More sharing options...
pandrew Posted March 27, 2024 Если подключиться ssh pandrew@172.17.1.200 и ввести di cur то выводит конфиг постранично. Но ssh@172.17.1.200 'di cur' вообще ничего не выводит. Кстати, а eltex mes2428 в ответ на команду admin@172.17.1.22 'show vlan' выводит exec request failed on channel 0 Но в интерактивном режиме работает без проблем. Думается дело не пробелах и в постраничном выводе, а том что не выполняется exec request. Вставить ник Quote Ответить с цитированием Share this post Link to post Share on other sites More sharing options...