In some cases (but sadly not all!) it may help to adjust a setting in Java.
#CONFIGURE SNMP ASA ASDM UPGRADE#
The recommended "fix" from Cisco is to upgrade to a newer version - which is really convenient for them since this requires an active support contract for the device in question (ie it costs money). Recent versions of Java seem to break the connection to older versions of the firmware. You could also view the logs, but I prefer the above, as it shows you the errors that occur during boot, as they occur. Many errors will result in an ASA that functions, just not as expected.
#CONFIGURE SNMP ASA ASDM UPDATE#
If there are corresponding versions of ASA and ASDM on there, update the config to use them - this will allow you to access ASDM and you can upgrade via that if necessary. If you don't have the files you expect in place, look at what is there. NB - you will see more files listed than this! You may see multiple version of the ASA and ASDM files, which is ok, but can cause problems if the config isn't quite right or a file is corrupt. Now you need to check what files are actually on the ASA: ASA# sh disk These should all match what is in your config, but if they don't then you would see problems as the loaded versions of ASA and ASDM have to match. This shows that the ASA is configured to use compatible versions of the ASA and ASDM images.Ĭheck which versions have loaded: ASA# sh bootvarĬurrent BOOT variable = disk0:/asa832-k8.binĭevice Manager image file, disk0:/asdm-633.bin Get to command line on your ASA and run the following commands and check they look similar to the following: ASA# sh run boot
0 kommentar(er)
