Hi,
thanks for your feedback. Sorry for late responds, See my answer to Florian.
I had the VIA logs downloaded but they weren't so helpfull, the same applies to log entries on the device and on Aruba Central.
I found in Config Audit the mismatch but weren't able to fix the problem. I even tried disaster recovery mode. It is a shame that there is now "Applied the cli command with force", I would have resolved the deadlock.
Markus
------------------------------
Markus Werner
------------------------------
Original Message:
Sent: Dec 03, 2020 01:27 AM
From: Veli-Matti Junkkari
Subject: Failed to establish secure connection: Code -8949
Hi Markus!
Please check VIA logs; gearbox icon => tab Logs. It will provide you a zip file from where you might find more insights about the issue.
------------------------------
gone fishing.
Original Message:
Sent: Nov 30, 2020 11:16 AM
From: Markus Werner
Subject: Failed to establish secure connection: Code -8949
Hi All,
in this April I setup VIA with Aruba Central (AC) Version 2.5.1 and Firmware 8.4.0.0-1.0.6.4_74274 (Aruba 7024 as VPNC).
Since a few days I try to reproduce this with AC 2.5.2 and FW 8.5.0.0-2.0.0.6_76205 (Aruba 7010 as VPNC)
I copied the orignal Config GROUP "VPNC-01" to "VPNC-02" and I double check the configuration (Diff against the running config and completly check on AC GUI).
I still get the Error "Failed to establish secure connection: Code -8949" on client side.
Any Ideas what I could check ?
Any Ideas how to debug this? Cause normal logging stays quite.
Is there a good background documentation about VIA? -> I not need the kind of Aruba Central Documentation -> I need to have a deeper understanding about how things work together.
with kind regards
Markus
------------------------------
Markus Werner
------------------------------