cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1348
Views
10
Helpful
8
Replies

After "clear configure all" then re entering configuration I can't access ASDM

Tyler Durden
Level 1
Level 1

Hi Guy's

After running clear "configure all" to get my ASA5512 back to default, I then re entered my desired configuration and now I can't access the ASDM. I can access the website that gives me the HTTPS warning then a username/password box pop's up but i can't get  passed this. I also get a strange message re the "Privilege 15". The configuration I have is the same as a working ASA5512 at a different location so i'm at a loss to why I can't access this after a day of messing around. My configuration as follows;

 

interface GigabitEthernet0/5
description VLAN2
nameif VLAN2
security-level 90
ip address 10.0.2.1 255.255.255.0

!

http server enable
http 10.0.44.0 255.255.255.0 vlan44
http 10.0.2.0 255.255.255.0 VLAN2

username cisco password cisco privilege 15

 

I also tried adding the following as well

asdm image disk0:/asdm-713.bin

 

May worth a mention I cannot SSH to the ASA, It connects but will not authenticate. I've tried different PC's as well that already have ASDM Java installed and are known to work.

 

1 Accepted Solution

Accepted Solutions

I did the following and can now connect to the dedicated Management port.

 

interface Management0/0
management-only
nameif management
security-level 100
ip address 172.16.80.1 255.255.255.0
!
crypto key generate rsa modulus 1024
ssh 10.0.44.0 255.255.255.0 vlan44
ssh 172.16.80.0 255.255.255.0 management
asdm image flash:/asdm-713.bin
username XXXXX password XXXXXXXX privilege 15

View solution in original post

8 Replies 8

Hello @Tyler Durden

Ideally you should have console to the device before issue such command.

 But, sometimes it happens. We expect a behavior and the result is different.

 Long time ago I got in the similar issue and I could revert the situation send SNMP command to ASA from a Linux machine and the Default private community.

 

You probably will need to reconfigure local auth. 

 

-If I helped you somehow, please, rate it as useful.-

I've had console all along and I still have access to the console, I issued the command via console!

Have you tryied  to reconfigure local access credential ? 

Can you share show running-config?

 

 

-If I helped you somehow, please, rate it as useful.-

 

 

ASA Version 9.1(2)
!
hostname LAB-ASA-01
domain-name LAB.ACME.LOCAL
enable password 2KFQnbNIdI.2KYOU encrypted
names
!
interface GigabitEthernet0/0
channel-group 1 mode active
no nameif
no security-level
no ip address
!
interface GigabitEthernet0/1
channel-group 1 mode active
no nameif
no security-level
no ip address
!
interface GigabitEthernet0/2
shutdown
no nameif
no security-level
no ip address
!
interface GigabitEthernet0/3
shutdown
no nameif
no security-level
no ip address
!
interface GigabitEthernet0/4
shutdown
no nameif
no security-level
no ip address
!
interface GigabitEthernet0/5
description VLAN2
nameif VLAN2
security-level 90
ip address 10.0.2.1 255.255.255.0
!
interface Management0/0
management-only
shutdown
no nameif
no security-level
no ip address
!
interface Port-channel1
no nameif
security-level 90
no ip address
!
interface Port-channel1.11
description VLAN11
vlan 11
nameif vlan11
security-level 90
ip address 10.0.11.1 255.255.255.0
!
interface Port-channel1.22
description VLAN22
vlan 22
nameif vlan22
security-level 90
ip address 10.0.22.1 255.255.255.0
!
interface Port-channel1.44
description VLAN44
vlan 44
nameif vlan44
security-level 90
ip address 10.0.44.1 255.255.255.0
!
ftp mode passive
dns server-group DefaultDNS
domain-name LAB.ACME.LOCAL
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
pager lines 24
mtu VLAN2 1500
mtu vlan11 1500
mtu vlan22 1500
mtu vlan44 1500
icmp unreachable rate-limit 1 burst-size 1
icmp permit any VLAN2
icmp permit any vlan11
icmp permit any vlan22
icmp permit any vlan44
asdm image disk0:/asdm-713.bin
no asdm history enable
arp timeout 14400
no arp permit-nonconnected
timeout xlate 3:00:00
timeout pat-xlate 0:00:30
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
user-identity default-domain LOCAL
http server enable
http 10.0.44.0 255.255.255.0 vlan44
http 10.0.2.0 255.255.255.0 VLAN2
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart warmstart
crypto ipsec security-association pmtu-aging infinite
crypto ca trustpool policy
telnet timeout 5
ssh timeout 5
ssh key-exchange group dh-group1-sha1
console timeout 0
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
username cisco password 3USUcOPFUiMCO4Jk encrypted privilege 15
!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns preset_dns_map
parameters
message-length maximum client auto
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect esmtp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
inspect ip-options
!
service-policy global_policy global
prompt hostname context
no call-home reporting anonymous
Cryptochecksum:0d0eda56aed2c552947cd8b2fe4fc22d
: end
LAB-ASA-01#

Hi @Tyler Durden

 

Try this:

 

ssh 10.0.44.0 255.255.255.0 vlan44
ssh 10.0.2.0 255.255.255.0 VLAN2

aaa authentication ssh console LOCAL
aaa authentication http console LOCAL

Make sure the command  "asdm image disk0:/asdm-713.bin" is pointing to the right asdm image.

Let me know if you need any more help.

 

-If I helped you somehow, please, rate it as useful.-

 

mikael.lahtela
Level 4
Level 4
Hi,

You might be missing these commands:
aaa authentication ssh console LOCAL
aaa authentication http console LOCAL

br, Micke

I did the following and can now connect to the dedicated Management port.

 

interface Management0/0
management-only
nameif management
security-level 100
ip address 172.16.80.1 255.255.255.0
!
crypto key generate rsa modulus 1024
ssh 10.0.44.0 255.255.255.0 vlan44
ssh 172.16.80.0 255.255.255.0 management
asdm image flash:/asdm-713.bin
username XXXXX password XXXXXXXX privilege 15

Alright. If everything is o, so please, change the status to solved so that you ca help others find your solution.

 

 

 

 

 

-If I helped you somehow, please, rate it as useful.-

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card