I'm trying to set up a pair of ASA 5510's in active/standby mode, and I've hit a bit of a problem. I've completed the following steps:
1. Out of the box, i've used the configure factory-default <ip-address> <subnet mask> to set an IP address on the management interface. I've plugged my laptop directly into the management port using a cross-over cable, and I can connect to the ASA using ASDM.
2. I then configured active/standby failover, and this appears to be working fine.
3. I then added a configuration via the CLI. This config is from a pair of PiX 515's that are being replaced. The config was generated using the PiX to ASA configuration converter available on cisco.com.
4. After adding this config, I can still access the ASA via ASDM, and everything appears to be fine. I saved the config to flash and powered down both ASA's.
5. Today, i've installed the ASA's on site. When I connect my laptop to the management interace using a cross-over cable, I can no longer connect using ASDM. when I try and use a web page with the address https://<ip-address>, I get the warning about using unsigned certificates, which I accept. I then get prompted for a username and password, which I have entered correctly. I then get a HTTP 404 - website not found message.
At first i thought it might be an access rule on the management interface, so I created a permit ip any any rule (for testing purposes) and applied it to the management interface, but this made no difference.
Can anyone point me in the right direction to fix this?
What version of ASA and ASDM software are you running?
Try enabling 'debug http' from the command line and then connecting to ASDM again. Does the output give any indication about what's happening? What page is the client trying to request that the ASA is responding with a 404 for?
Can you please provide the "show version" output from the ASA? This will provide the current software installed as well as the ASDM version. Perhaps there is a conflict with the software version on the ASA and the ASDM version.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...