Hi,
Thanks for your reply. I've tried this:
1: tried from different machines (all windows OS'es however) with bitvise or putty, from different subnets
2: once your're in, you stay in until the idle timer runs out; no disconnects before that. then sometimes you can connect again but mostly the issue returns
3: i have a serial connection to one of the switches now, when I try to access another one from there:
Aruba8320-DC1-1# ping aruba8320-dc1-2
PING aruba8320-dc1-2.<domain> (192.168.255.42) 100(128) bytes of data.
108 bytes from 192.168.255.42: icmp_seq=1 ttl=64 time=0.215 ms
108 bytes from 192.168.255.42: icmp_seq=2 ttl=64 time=0.257 ms
108 bytes from 192.168.255.42: icmp_seq=3 ttl=64 time=0.250 ms
108 bytes from 192.168.255.42: icmp_seq=4 ttl=64 time=0.255 ms
108 bytes from 192.168.255.42: icmp_seq=5 ttl=64 time=0.269 ms
--- aruba8320-dc1-2.<domain> ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4076ms
rtt min/avg/max/mdev = 0.215/0.249/0.269/0.020 ms
Aruba8320-DC1-1# ssh aruba8320-dc1-2
kex_exchange_identification: read: Connection reset by peer
Aruba8320-DC1-1# ssh 192.168.255.42
kex_exchange_identification: read: Connection reset by peer
Kind regards
------------------------------
Kris Vervisch
------------------------------
Original Message:
Sent: Feb 03, 2021 08:00 AM
From: R-Air R-Head
Subject: SSH connection abort
We have a similar setup and use local/remote ssh extensively.
Disclaimer: I am an aoscx noob.
Forcing different symptoms to cause us to think out of the box:
1. Try another remote client and OS to see if SSH break symptoms are identical.
2. If your customer has the knowledge, have them locally SSH to one of the 8320's and try to force a prolonged SSH session.
3. If you SSH to one 8320 and then from the first 8320, SSH to a second 8320, do any of the connections break in a similar manner?
------------------------------
R-Air
------------------------------