What is the proper method for customers to submit feature requests?
The specific feature I'm interested in deals with multiple context mode, where it would be extremely useful to re-use certain configuration elements (names, object-groups, etc.) in multiple contexts. If you do this currently, you have to define them in each context where they will be used and, if/when they need to be edited, you have to do so in each context. I see a need for a feature where you could define names and object-groups in the admin context or system space, and use something like an "inherit" command in the other contexts to re-use these elements. Of course, you also need a mechanism to force the inherited elements to be updated, and associated acls recompiled, when the "master" instances are updated. So, if anyone from the product development team is listening ...
You will need to get in touch with your local Cisco SE and ask them to open a PERs request on your behalf which they can do and the right marketing contact will be assigned the request to consider for a future release.
What you want exists in Cisco Security Manager, which replaces VMS for managing PIX, ASA, IPS appliances, FWSM's, and IOS routers/firewalls. You can download it with a CCO login and use it for 90 days without a license key.
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...