I have a brand new ASA 5510 and started with the default configuration. (I'm pretty new to this)
The fundamental problem that I am facing is that I cannot get any interface other than management to come up after configuring with an IP, security level, name and the "no shut" command.
The interface is configured for auto speed/dup and physical links are good.
I applied a "permit any any" acl both in and out on the inside and outside, set security level of all interfaces to match and allowed traffic between them, and to the best of my knowledge established static nat between the inside interface IP and an IP on the same subnet as the outside interface.
At this point I'm not concerned with passing traffic, I'm just wondering what is the minimum configuration necessary to get an interface from down to up.
Bill, it is assume you have inside and outside interface connected to some sort of devices like an interneal swith for your inside interface and external switch for outside interface, is this the case? when you do " show interface " interface will show " down " until it is connected to something.
According to the configuration guide, as long as the speed and duplex are set for auto, mdi/mdx will be auto as well. That said, I have tried both crossover and straight through on both inside and out and both remain down.
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...