If this was right after a signature config change then it can take the Analysis Engine 15 to 45 minutes to rebuild its cache tables (depends on type of sensor and sensor load). You should also check to make sure the Analysis Engine is still running by looking at the status line in the cli "show version" command output.
If it is not running then reboot the sensor. After reboot check to see if Analysis Engine is ready for updating by using the "show int sensing" cli command. When you get a non-err response then the sensor is ready to be upgraded.
I have checked all my sensors components r running including Main Application & Analysis engine but surprisingly, when i give the command sh int sensing, i observed that the sensor displayed the message "no active virtual sensor". please suggest me what r the things to b done inorder to update the remote sensor(4235) having current signature 4.1-4-S67 which needs to upgraded to 4.1-5.
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...