ASDM without 3DES - Recovery wrong encryption license from remote

[Arturo Bianchi]

Hi,

following an incorrect license change, an appliance has lost its encryption protocols... after reboot it is not possible to access remotely via ssh to attempt a recovery:

ssh -1	Selected cipher type <unknown> not supported by server.
ssh -2	Protocol major versions differ: 2 vs. 1

so I just have to force access via ASDM or establish if it is possible to initialize a temporary SSL session in degradation! But at a first search of how to force java / asdm to connect the remote device I did not find anything interesting... why? Isn't it really possible to force ASDM to connect or did I miss some interesting article / solution?

Thanks!

73,
Arturo.

[Marvin Rhoads]

Your best path after having that situation is to connect via console and reapply a correct 3DES-AES license activation key.

As far as I know, ASDM (which uses the Java security modules) cannot be made to work with an ASA not having a valid 3DES-AES license active.