ASA Configuration Troubleshooting

From DocWiki

(Difference between revisions)
Jump to: navigation, search
Line 3: Line 3:
'''Execute the following commands.'''
'''Execute the following commands.'''
-
ASA-Device(config)# logging enable
+
ASA-Device(config)# '''logging enable'''
-
ASA-Device(config)# logging console 6
+
ASA-Device(config)# '''logging console 6'''
-
ASA-Device# debug auto-update server
+
ASA-Device# '''debug auto-update server'''
-
ASA-Device# debug auto-update client
+
ASA-Device# '''debug auto-update client'''
 +
 
 +
 
 +
== Configuration not pushed due to java.lang.SecurityException: Device Authentication Failed. ==
 +
'''Check the following.'''
 +
 
 +
1. Check whether the ASA device is created on CE server.
 +
 
 +
2. if the device is created on CE side, then check the auto-update server cli on ASA to verify that the CLI is having correct username and password.
 +
 
 +
3. If you feel that the password is incorrect on either side, then re-sync the password on both the side by reconfiguring the auto-update server CLI on ASA device and by editing the device on CE side.

Revision as of 04:38, 3 May 2011

How to enable auto-update server logging on ASA device.

Execute the following commands.

ASA-Device(config)# logging enable

ASA-Device(config)# logging console 6

ASA-Device# debug auto-update server

ASA-Device# debug auto-update client


Configuration not pushed due to java.lang.SecurityException: Device Authentication Failed.

Check the following.

1. Check whether the ASA device is created on CE server.

2. if the device is created on CE side, then check the auto-update server cli on ASA to verify that the CLI is having correct username and password.

3. If you feel that the password is incorrect on either side, then re-sync the password on both the side by reconfiguring the auto-update server CLI on ASA device and by editing the device on CE side.

Rating: 0.0/5 (0 votes cast)

Personal tools