We recently upgraded one of our Cisco Guards from 6.0(10) to the latest version (6.1(2)) and now the following OID's do not appear to work/exist any longer:
The ability to graph these are critical due to the following bug:
CSCsc05116 - The Guard may stop functioning or start logging errors after reaching 100 percent anomaly detection engine memory utilization. Workaround: Use the show resources command in global mode to view the amount of anomaly detection engine memory currently being used by the Guard. Reducing the number of active zones may free up memory.
I thought that maybe they changed the way it is queried but was unsuccessful with anything else I tried (using the latest MIB).
I apologize if I have posted this in the wrong place.
There is a bug filed for this issue you have mentioned and the work around for this issue is that the Anomaly Detection memory should be freed by deactivating one or more zones, or alternatively by disabling several number of policies/services.
You can delete a specific service relating to a policy template.
To delete a service from a policy, enter the following at the policy template prompt:
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...