08-28-2007 05:11 AM - edited 03-11-2019 04:03 AM
Hi all,
I'm having a weird problem, probably a bug, with my ASA 5520 running version 8.0(2) and ASDM 6.0(2)
In a factory default configuration with normal ASDM access I put the attached config on the Firewall.
After I save and reboot the Firewall I get the following message during the reboot:
Could not start admin
I check the config and I realize that the http server section is like this:
http server enable
http 10.99.250.0 255.255.255.0 WAN
It lost one line and I cannot get through ASDM from anywhere to the Firewall. Even from the WAN interface.
I try to activate the HTTP server and I get the following:
ciscoasa(config)# no http server enable
ciscoasa(config)# no http 10.99.250.0 255.255.255.0 WAN
ciscoasa(config)# no http 192.168.1.0 255.255.255.0 management
ciscoasa(config)#
ciscoasa(config)#
ciscoasa(config)# http 10.99.250.0 255.255.255.0 WAN
WARNING: http server is not yet enabled to allow ASDM access.
ciscoasa(config)# http 192.168.1.0 255.255.255.0 management
WARNING: http server is not yet enabled to allow ASDM access.
ciscoasa(config)# http server enable
Could not start admin
After some trial and error I was able to put it back to work after taking out 3 VLAN interfaces. This configuration has 17 VLAN interfaces.
Some bug is preventing the HTTP Server to start if there are more than 14 VLAN interfaces configured on the ASA running this version because I don't have this kind of problem running this config in version 7.
Anyone having the same problem?
08-28-2007 06:06 AM
Go into Configuration -- > Properties --> DNS
Add rule there.. instead of NO and NO.
Regards,
Dharmesh Purohit
08-28-2007 06:49 AM
Hi Dharmesh,
Can you explain this, please?
In ASDM 6.0 I don't have the path like you are telling me.
And what DNS has to do with influencing the HTTP Server depending on the number of configured VLAN interfaces?
Thanks in advance.
11-21-2007 09:55 AM
I am having the same problem and my engineer recommended that I upgrade to 8.0.3. Don't bother, it doesn't help. I upgraded on Sunday, and by Monday, I had the same problem again.
Apparently, it is a known bug and will be resolved in 8.1.1. I don't know of an ETA on 8.1.1, though.
See the following link:
11-22-2007 02:42 AM
Yesterday I've upgraded the firewall to 8.0.3 and the problem didn't happen again. Let's see if it keeps that way.
I've followed the tek-tips link you've posted and I really had the management interface on HTTP Server but I don't think that was my real problem.
My issue was really the number of VLAN interfaces configured. If I reached a certain number of VLAN interfaces the HTTP admin would stop working after a reboot.
Version 8.0.3 seems to have solved my issue.
Let's see how long we will have to wait for version 8.1.1 to solve your problem.
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: