I have not tried to do anything quite like this myself and perhaps someone who has will add their opinion. I believe that the real limitation would be the memory consumption on the ASA. As the low end box in the ASA product line I would question whether the ASA5505 was appropriate for an organization that wants to advertise 6k routes through the ASA. I would hope that either there might be a way to redesign so that the number of routes in the ASA was reduced, or that a firewall with more resources might be deployed.
I don't normally chime in with 'me too!' type posts, but in this case I have to as I agree entirely with Rick's post. Although the ASA 5505 is a great box it is really intended for SOHO type deployments.
In the event that the network topology really requires the advertisement of so many routes, I think that an ASA 5510 would be more appropriate.
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...